Konstantin “Stan” Ponomarev · konstantin.ponomarev@ohmymail.net · (645) 205 7472
Context
How the work connected.
Background and context
Survey teams, seismic interpreters and geological specialists needed usable information for exploration decisions. I led delivery through five direct-report PMs and three shared-pool PMs. Engineers and domain specialists owned detailed design; I connected priorities, dependencies and commitments.
An attractive idea could still depend on immature technology, unavailable specialists or vulnerable software components. Funding every idea would spread capacity across work with very different prospects of reaching useful operation.
The decision, illustrated
Stopping work also required follow-through.
- Weigh the case
- Compare value, strategic importance and technology maturity.
- Choose the route
- Take continue, defer or stop decisions to the appropriate authority.
- Follow through
- Confirm the funding decision and the actual specialist transition.
Branches are decision options, not project proportions. Twenty projects over six years and fifteen products in use are different counts.
- five direct reports; three shared pool
- 8 PMs
- initiatives stopped after reassessment
- 5
- products reported in use
- 15
Judgment
Choose what to continue. Follow through on the decision.
The central trade-off
Potential value had to justify further time, cost and technical uncertainty. Stopping selected work reduced scope and released resources, but required separate approval and follow-through for funding and people.
- 01
Make the continuation decision explicit.
I compared expected economic effect, strategic importance and technology maturity, then deferred and reassessed uncertain work. I recommended five stops at different points; the Head of Geology approved them. One platform stopped in planning because all three factors remained weak. I had kept it in planning too long, creating repeated planning work and extra PM workload. I then required earlier explicit continue, defer or stop decisions.
- 02
Follow the money and people through to their destinations.
I compared project-level continuation costs with program-level allocation options. Before recommending moves, I reconciled PM inputs, the resource plan and resource-manager confirmations. The steering committee approved internal redistribution and the proposed portfolio return separately; the investment committee approved the returned amount and budget-baseline change. PMs and resource managers coordinated specialist moves. I kept each move open until the receiving side confirmed the actual transfer.
- 03
Respond to the dependency without confusing replacement with shutdown.
When software-license restrictions became an active issue, I escalated scope and funding implications while technical teams owned replacement design. Further dependent development ended and a replacement initiative began, while useful legacy functionality remained in service. Fortnightly PM reviews, quarterly planning and monthly forecasts connected the transition to delivery commitments.
Outcome
Changed scope. Products in use. Delivery completed.
- Twenty projects were managed over the six-year period; this is not a simultaneous-project count. Five initiatives were stopped after separate reviews and approvals.
- Remaining funds were redistributed within the program or returned to the portfolio. Specialists moved to other program projects or the shared pool; no cash-savings amount is claimed.
- Fifteen products were reported in use. A 2024 survey-platform example included more than 1,000 historical survey projects migrated and use by five external contractor organizations.
- In 2025, we completed the program components, confirmed benefits and passed an audit. This is my confirmed delivery account; final benefit amounts and audit particulars are not stated here.
Responsibility
My role and the scope of this case.
I led the PMs and prepared recommendations; business and investment authorities retained approval rights. Teams built the products and specialists owned technical decisions. Project, product and migration counts describe different populations. The program’s long-term benefit forecast is not presented as realized savings, and resource reassignment is not treated as a cash saving.
Hiring for similar responsibilities?
Discuss a rolehttps://www.ponomarevkk.com/work/cognitive-geology/