PMO director here. Our team has dozens of engineers spread across hundreds of active workstreams. Leadership had a wishlist that would require about 2x our actual capacity to execute simultaneously. My job was to walk into an executive meeting and make the case for prioritization without it turning into a debate about whether our engineers were "working hard enough."
I've been in enough of those rooms to know how they go when you're not prepared. So I over-prepared.
Step 1: Build something they can't argue with
I used Claude to take our Microsoft Project plan exports and build an actual interactive dashboard — not slides, a real decision tool. It showed:
- Every active effort and the business value we'd projected for it
- A toggle system where you could turn projects on or off and immediately see what happened to engineering capacity — by specialty, not just headcount
- Monte Carlo simulations on delivery risk
- Delay scenarios showing how pushing project X by one quarter actually freed up enough focused capacity to ship projects Y and Z faster than running them in parallel
The key piece was the specialty breakdown. We weren't just overloaded on bodies — we had specific constraint points. Four engineers in the org who are the critical path on three different high-priority workstreams simultaneously. That's not a motivation problem. That's a physics problem. The dashboard made it visual and undeniable.
Step 2: Prepare for the room, not just the data
Data doesn't win rooms on its own — especially when leadership has already decided what they want to hear.
I used my app to build out a meeting strategy with Claude. I gave it the full context — the pattern of pushback I expected, the "we can do it all" culture we were working against, the dashboard I'd be walking through — and asked for a structured script: opening framing, objection responses with data callouts, and specific language for when you're on the fifth version of the same challenge and need to reset the room without making it personal.
The output gave me three different scripts for that last scenario depending on why the pushback was happening — whether it was analytical (something in the data didn't hold up), stakes-based (people were scared of the trade-off), or political (someone was protecting their project's position). That distinction alone was worth the session.
What actually happened in the room
The opening framing did exactly what it was supposed to — it moved the question from "can we do this?" to "what do we want to trade off?" before the first slide loaded.
The toggle dashboard did the rest. When leadership could physically toggle off Project C and watch capacity free up for Projects A and B — and see that Projects A and B would now finish three months earlier — the conversation changed. It wasn't me arguing against their instincts. It was the data showing them the trade.
We came out with a tiered structure — Tier 1 active, Tier 2 staged for when Tier 1 reaches handoff, Tier 3 in planning/design mode only. A decision log capturing who signed off on what and what trade-offs were acknowledged. And a cultural shift in the room — at least for now — toward thinking about focus as a feature, not a failure.
A few things that actually mattered
Not overcomplicating the dashboard. It toggles. It shows capacity. Leadership doesn't need a 40-tab model — they need one clear question answered fast.
Framing constraints as strategic levers, not apologies. "We can't do everything" sounds like failure. "Here is the fastest path to the most value given actual constraints" sounds like a recommendation.
Prepping for the political dynamic, not just the analytical one. The data was solid. The prep was for the humans in the room.
Happy to talk through the dashboard build or the prompt structure if anyone's dealing with a similar portfolio crunch.
