2-Week Delivery Diagnostic
Find out where delivery control is weak before committing to a longer engagement. Two weeks. A clear picture of your risks, your PM setup, and where the gaps are — with a plain recommendation on whether to continue.
Right for you if any of these sounds familiar.
You had a client escalation recently and aren't sure why it wasn't caught earlier.
You're considering a fractional or full-time Head of Delivery but want to see the actual gaps before committing.
You need internal buy-in before approving a longer engagement. The diagnostic gives you a document to share.
Delivery feels unstable but you can't point to exactly what's wrong. The diagnostic names it.
Six areas examined in the first two weeks.
Project health reporting
How status is reported across projects. Whether what leadership sees matches what's actually happening on each engagement.
Risk visibility
Whether risks are being surfaced before they become client calls. Who owns them, how they're tracked, and whether the process holds up under pressure.
Scope & margin signals
Where budget drift is happening. How scope changes are reviewed and approved — or not — across active projects.
Escalation routines
How escalations are handled when they happen. Whether the process is documented or improvised each time. Who gets involved and when.
PM consistency
How each PM manages reporting, client communication, and risk ownership. Where they're consistent, where they're not, and what that costs leadership visibility.
Leadership decision points
Where leadership gets pulled in because the delivery process isn't handling it. What decisions belong at which level — and what's blocking that from working.
Five documents at the end of week 2.
Diagnostic findings
A plain summary of what I saw: what's working, what's not, and how confident I am in each assessment. Written for the founder or Head of Delivery, not a consultant audience.
Risk map
Current risks across your active projects, categorized by severity and ownership. Not a template — an actual picture of what's exposed right now and who should be handling each item.
PM & reporting observations
How your PMs are managing delivery. Where they're consistent, where they're not, and what that means for your ability to see project health clearly at a leadership level.
Quick wins
Three to five things you can act on without waiting for a longer engagement — changes to reporting, escalation handling, or risk tracking that improve visibility immediately.
Continue / stop recommendation
My honest read on whether a longer engagement makes sense. If the gaps are smaller than expected, or the fit isn't there, I'll say so directly. This isn't a sales pitch at the end of week 2.
If the findings aren't useful — you stop. No invoice.
The diagnostic is part of the first month. If what I surface by end of week 2 isn't useful enough to justify continuing — the risk picture is clearer than you expected, or the fit just isn't there — you stop.
No invoice for the rest of the month. No pressure to continue. That's not a marketing promise. It's how I avoid wasting your time and mine on an engagement that doesn't fit.
Start with a 20-minute fit call.
Tell me about your project load and PM setup. If the diagnostic makes sense for where you are, we start. If it doesn't, I'll say so on the call.