Konstantin “Stan” Ponomarev · konstantin.ponomarev@ohmymail.net · (645) 205 7472
Context
How the work connected.
Background and context
Subsidiaries were running their own technology and organizational projects, but lacked a common registry and a consistent route to central expertise. I co-designed a project-office model around managed decentralization.
Full central control would slow local decisions. Complete independence made duplicated work, architectural conflict and unaddressed competency gaps hard to see.
The decision, illustrated
Add the support the local team is missing.
- Independent
- The local team owns delivery.
- Targeted support
- Add the specific competencies that are missing.
- Full project team
- Bring a complete project capability where required.
Three support modes in the proposed operating model. The pilot was approved; the illustration does not claim rollout to every subsidiary.
- governing principles
- 7
- project types in scope
- 4
- pilot approved
- 1
Judgment
Balancing local authority with shared support.
The central trade-off
Local independence supported execution, while a shared registry and common methods supported portfolio visibility. Three support modes let subsidiaries retain ownership and request the capability they lacked.
- 01
Offer support in proportion to the need.
Defined three routes: independent execution, access to specific competencies, or a full project team. Local business units could match the engagement to their delivery capability.
- 02
Keep the business accountable.
The principles retained business ownership of budgets and linked staffing to local needs. A corporate program leader could not unilaterally block a local project.
- 03
Share the minimum governance foundation.
Combined local autonomy with common methodology, a shared project registry and integration with the portfolio cycle. Steering review and a pilot created a path to refine the model.
Outcome
What was designed and approved.
- The model defined three engagement modes and seven governing principles.
- A pilot was approved in December 2019.
- The refined model was prepared for rollout in early 2020.
Responsibility
My role and the scope of this case.
I co-led operating-model design and steering preparation with other leaders. The documented milestones establish model design and pilot approval, not a completed rollout across all subsidiaries or measured enterprise-wide savings.
Hiring for similar responsibilities?
Discuss a rolehttps://www.ponomarevkk.com/work/subsidiary-pmo/