When every PM manages differently, you're the one reading between the lines.
You know which PMs are on top of things and which aren't. The problem is you can't see it from the project data — because the data isn't structured the same way across engagements. This isn't a PM problem. It's a missing operating layer.
The problems aren't hidden. They're just not visible in the right format.
No shared reporting format
Each PM reports the way they've always reported. Status updates exist across five different formats, three different tools, and varying levels of detail. Comparing project health means doing the translation yourself each week.
Risks surface after the client does
By the time a risk gets raised formally, the client is already aware something's off. Not because PMs are hiding things — because there's no consistent structure for surfacing concerns before they become client conversations.
PM maturity is uneven
Some PMs own risk well. Others wait to be asked. You know who's who, but the current setup doesn't give the junior ones a clear structure to follow — so the gap keeps showing up in different projects.
Reporting creates work, not clarity
Updates go out every week. Nobody's sure what they mean. Leadership asks follow-up questions that the update should have already answered. The effort is there. The signal isn't.
This is not a review of your PMs. It's a review of the system they're working in.
PMs working without a shared operating rhythm will always look inconsistent — even capable ones. The goal isn't to identify who's struggling. It's to build the structure that makes inconsistency visible and fixable, instead of something you have to personally compensate for.
I work with PMs as a peer, not as an auditor. The diagnostic and what follows from it is framed that way from day one.
PM sessions are framed as working check-ins, not performance conversations
Changes to reporting format happen with PMs, not around them
Findings go to you first — you decide how they get shared with leadership
The goal is a structure that makes your job easier, not a report that creates more work
Five things that get fixed in the first engagement.
PM reporting rhythm
A shared reporting format that all PMs use — same sections, same language, same cadence. Not a template that gets ignored. A format built around what you actually need to see, tested with your PMs before it becomes the standard.
Risk review structure
A weekly risk log that doesn't depend on individual PM judgment about what counts as a risk. Named risks, severity, owner, and last action — across all active projects, in one place.
Scope control
A lightweight process for flagging unapproved changes before they accumulate. Not a bureaucratic approval chain — a consistent check that stops small scope additions from quietly stacking up across engagements.
PM check-ins
Regular working sessions with each PM — not to review their performance, but to calibrate how they're applying the shared format, what's unclear, and where they need more support. Most PMs find this useful rather than threatening.
Leadership summary
A monthly summary of portfolio health, current risks, and what needs a leadership decision. Written for a founder or CEO — not a consultant report, not a data dump. Short enough to actually get read.
Before and after a shared operating rhythm.
Before
Six different status report formats across the PM team. Leadership reads four before sending follow-up questions.
Risks get flagged in standup notes, Slack threads, or not at all until they land in a client call.
Scope changes agreed informally. Nobody tracks them systematically until margin shows up wrong at month end.
Head of Delivery spends Monday mornings piecing together portfolio health from multiple sources.
After
One format, same sections, every project. Status is comparable across the portfolio without translation.
Weekly risk log with named owners. Risks are either addressed or escalated — not left floating in channels.
Unapproved scope changes flagged before they stack. Budget drift visible in real time, not at invoice.
One leadership summary lands Friday. Takes 10 minutes to read. No follow-up questions needed.
Two weeks of diagnostic before anything else changes.
The first two weeks are a review of your current setup: how PMs report, how risks get tracked, where scope discipline is working and where it isn't. You get a written summary of findings and specific quick wins before committing to any ongoing engagement.
If the picture is cleaner than expected, I'll say so directly. The diagnostic doesn't exist to sell a longer engagement — it exists to find out whether one is warranted.
Review whether this would work with your PM team.
Tell me about your PM setup — how many, how they currently report, and what's been most frustrating to diagnose. If there's a fit, we start with the 2-week diagnostic. If there isn't, I'll say so on the call.