Mark-to-market your program, not your slide deck
At 16:59, the desk stops telling stories. It prints the book. P&L sits there, indifferent to confidence and good intentions.
Many digital programs run the opposite way. The deck stays green until the week the project hits the wall. Then everyone “discovers” the dependency, the missing decision, the unowned interface, the test gap.
If you run a board-timeline implementation with an overloaded team and a vendor that expects you to speak their language, treat the program like a trading book: mark it to reality, every week.
Green status is not a control
Green status usually means tasks ticked, meetings held, risks “monitored.” None of that proves an operable workflow, a stable integration, or a reconciled number.
In commodity terms, that’s “100% hedged” without positions, confirmations, or a valuation method.
You don’t need more updates. You need a close.
Replace the deck with a one-page Truth Pack
Drop the 12-slide confidence deck. Bring one page that answers the only questions that matter.
1) What is the finish line, in operational terms?
Not “UAT complete.” Not “Phase 2 done.”
Name 3–5 workflows the business runs end-to-end (trade capture → risk → confirmation → settlement). Define “operable” for each.
2) What is the critical path to that finish line?
List the next five milestones only. If a milestone does not move the date, it’s noise.
3) What evidence exists right now?
For each milestone, list the artefact. Examples:
- Working demo (live or recorded)
- Test results (pass/fail, not commentary)
- Interface proof (message in, message out, reconciliation shown)
- Runbook excerpt (support owner, “normal” vs “incident”)
4) Where is variance, and why?
Circle the gap between plan and reality in red.
One line: “We are X days behind on Y because Z.”
5) What decisions unblock the next 7 days?
Decision, owner, deadline. No “TBD.”
That’s the pack. One page. One conversation. Real progress.
Treat progress like P&L, not promises
A trading book moves on numbers. Your program does too.
Run a weekly delivery close:
- Earned progress: verified deliverables that operate end-to-end
- Burn: cost and time consumed
- Exposure: open risks on the critical path
- Liquidity: team capacity to absorb change without breaking
This is not extra governance. This is fewer meetings and better decisions.
The political benefit nobody admits
A truth pack does something else: it removes ambiguity.
Vendors stop hiding behind language. Evidence speaks.
IT stops carrying translation alone. The pack forces clarity.
Sponsors stop getting surprised. Variance shows up early, while fixes stay cheap.
Teams breathe. Work narrows to what moves the date.
That’s the shift. A one-page truth pack replaces green status.
Two common failure modes and how to handle them
Failure mode 1: The vendor “agrees” but keeps presenting slides.
Fix: refuse discussion without artefacts. No demo, no milestone.
Failure mode 2: The room treats variance as blame.
Fix: frame variance as exposure. Ask, “What action reduces exposure by Friday?”
A practical next step
If your deck stays green but your gut says otherwise, start with the Project Health Check to expose the real critical path, surface variance, and lock next actions with owners and dates.

