The first 90 days: a turnaround playbook for new PMO leaders.
A phased plan for taking over a struggling portfolio — what to do first, what to leave alone, and how to earn the authority to fix the rest.
PulsePMO IQ · Playbook for incoming PMO and transformation leaders
Taking over an existing PMO is a different problem than building one from scratch. The instinct on day one is to fix everything you can see wrong — the reporting, the committee cadence, the RACI — all at once. That instinct is usually a mistake. Move too fast and you break commitments already in flight before you understand why they were made. Move too slowly and the organization concludes nothing is going to change. This playbook lays out a sequence that works for most turnarounds: assess without disrupting, stabilize the highest-risk items, then institutionalize the changes that make the improvement durable.
Assess
Stabilize
Institutionalize
Days 1–30: Assess
Goal: understand the real state of the portfolio before changing anything in it.
Inventory every active commitment.
Every project, every vendor contract, every capital commitment currently open — in one list, regardless of how many separate systems it currently lives in.
Interview every project owner individually, not in a group setting.
Ask what they'd fix if they had the authority. Group settings produce consensus answers; individual conversations produce the real list.
Find the shadow processes.
Every struggling PMO has at least one workaround — a spreadsheet someone maintains because the official system doesn't capture something that matters. Find these before you retire anything.
Identify the two or three highest-risk items and say nothing publicly yet.
You need runway to verify before you commit to a fix in front of the organization.
Do not cancel or restructure anything in this phase.
Changes made before you have credibility read as arbitrary, even when they're correct.
Presenting a full turnaround plan at the 30-day mark to demonstrate momentum. A plan built on 30 days of assessment is usually missing at least one load-bearing piece of context that a project owner could have told you about, had you asked a second time.
Days 31–60: Stabilize
Goal: fix the highest-risk items you found, and put minimum-viable visibility in place for everything else.
Address the highest-risk item first, visibly.
A single credible fix — a vendor over-commitment resolved, a stalled decision unblocked — does more for your authority than any process change.
Get every active project's status into one system of record.
Not a new process yet, just visibility: consolidate what exists today, even if it's imperfect, before designing what should replace it.
Re-open the highest-value shadow process as the interim standard.
If a spreadsheet someone built is genuinely more accurate than the official report, use it publicly until you've built something better — don't force premature adoption of a broken system.
Set one recurring touchpoint with your steering committee.
Even biweekly is enough at this stage — the point is establishing the cadence before you change what happens in it.
Days 61–90: Institutionalize
Goal: replace the fixes that were manual in phase two with a structure that holds without you personally driving it.
Formalize intake scoring for new demand only.
Apply it going forward; don't retrofit it onto projects already in flight, which erodes trust in the new process before it's proven itself.
Publish the RACI you've been operating on informally.
By this point you know where the real ownership gaps are — make the model explicit rather than carrying it in your head.
Retire the manual status assembly once the system of record is trustworthy enough to replace it in a steerco meeting.
This is usually the single biggest time recovery in the whole 90 days.
Set the metrics you'll be judged on next quarter, and share them upward before you're asked.
Controlling the definition of success is easier in month three than after month six.
Command center, demand pipeline, and the decision queue — in the product tour.
This playbook reflects general turnaround practice patterns and is not specific to any named customer or engagement.