90-day structured framework for rebuilding a PMO that has lost sponsor confidence. From activity reporting to outcome control — with governance gates that enforce accountability.
| Phase | Focus | Duration | Gate | Status |
|---|---|---|---|---|
| Phase 1 | Diagnostic & baseline | Weeks 1–4 | Pass/Fail | Cleared |
| Phase 2 | Architecture installation | Weeks 5–8 | Pass/Fail | In progress |
| Phase 3 | Outcome control & cadence lock | Weeks 9–12 | Pass/Fail | Pending |
Each phase has pass/fail criteria. Advancing without clearing the gate replicates the accountability gap the rebuild is designed to fix.
A complete implementation playbook — not a methodology deck
This playbook is designed for operators who need to rebuild a PMO that has lost credibility.
One playbook. Two license types.
| Without this playbook | With this playbook |
|---|---|
| PMO rebuild starts with a blank page and no structure | 90-day framework with week-by-week milestones from Day 1 |
| New processes installed on top of undocumented old ones | Phase 1 diagnostic documents current state before anything changes |
| PMO reports activity — "we had 12 meetings" — not outcomes | Governance gates enforce outcome delivery, not activity volume |
| Sponsor loses confidence because visibility never improves | Structured sponsor reporting cadence built into every phase |
The playbook works for both scenarios. If you are building from scratch, Phase 1 is faster (less legacy to document), but Phases 2 and 3 apply identically. The governance architecture does not depend on a prior PMO existing.
No. The playbook runs on email, Excel, and a shared drive. Do not delay the rebuild for tool procurement. Phase 2 identifies tool needs, but the architecture activates before tools are selected.
The gate criteria are binary — pass or fail. If you fail a gate, you stay in the current phase until the criteria are met. This is by design. Advancing without clearing the gate replicates the accountability gap the rebuild is fixing.
Phases can be compressed if you have dedicated resources and minimal legacy complexity. 60 days is possible for a small, focused team. Below 60 days risks installing architecture that does not stick.
A former Big-4 consultant and Managing Director who rebuilt PMO functions at PE-backed industrial platforms. The framework reflects real rebuild deployments under PE sponsor oversight — not academic methodology.
3 phases. 12 weeks. Governance gates enforced. Deploy on Day 1.