Six documents for one fictional retail transformation. Charter, SteerCo deck, dashboard, risk log, Friday memo, value model. Same numbers throughout, same story throughout, so you can see how a portfolio hangs together in practice rather than in the abstract.
Fictional. Around 500 stores across Canada, roughly $8B in annual revenue, catalog spanning apparel, homewares, and seasonal. In August 2025 the board approved Project North Star. Thirty-six months, five workstreams, roughly $200M in capex. Modernize store technology. Unify the customer data platform. Accelerate the supply chain. Rebuild loyalty. Re-platform merchant tools.
The program is running Amber at month 14. Two workstreams on plan, two slipping, one blocked on a decision the Executive Committee has already deferred twice. Below is the pack the TMO would put in front of leadership this week.
Every workstream in the portfolio has a charter. What we're doing, why, who owns it, and how we'll know we succeeded, on one page. Written once, referenced every time a scope debate starts.
The decisions live on slide 2. Before status, before the walkthrough, before the RAG chart. If the room only has time for one slide, that's the one people should be reading.
Every workstream on one page. RAG broken out by schedule, scope, budget, and benefits. A program on plan for schedule but off plan for benefits is not green. Rolling those into a single dot hides the trade-off the sponsor needs to see.
| ID | Risk / Dependency | Workstream | P | I | Owner | Status |
|---|---|---|---|---|---|---|
| R-08 | Legacy loyalty sunset undecided. CDP + Loyalty blocked. | Loyalty | H | H | CMO | Escalated |
| R-11 | Rural connectivity below spec. 80 stores affected. | Store Tech | H | M | SVP Ops | Escalated |
| R-14 | CDP vendor API delivery slippage | CDP | M | H | VP Data | Mitigating |
| R-17 | Field change fatigue. Wave 1 velocity risk. | Store Tech | M | M | Dir OCM | Mitigating |
| R-19 | Finance / TMO benefits reporting misalignment | Portfolio | L | M | TMO Lead | Open |
| D-04 | DC3 automation → mobile POS inventory feed | Supply / Store Tech | L | M | VP Supply | On track |
| D-07 | CDP customer records → Loyalty cutover data | CDP / Loyalty | H | H | VP Data | At risk |
| R-22 | Merchant tools SME availability, Q1 gap | Merchant | M | M | VP Merch | Open |
| R-25 | Payment gateway migration adjacency | Store Tech | L | H | CTO | Mitigating |
| R-06 | WMS cutover contingency plan | Supply Chain | L | L | VP Supply | Closed |
Risks and cross-workstream dependencies in the same log. Probability and impact are separate columns. "Critical" by itself doesn't help anyone. Every open item has a named owner and a date by which it needs to be resolved.
One to two pages, sent Friday morning, read Sunday night. Four minutes if you skim. The point is to land Monday's discussion on the decisions on the table, not on the status recap. If the memo doesn't shape a decision, we don't send it.
| Workstream | Plan NPV | Forecast | Actual YTD | Variance | Confidence |
|---|---|---|---|---|---|
| Store Technology Refresh | $62.0M | $66.0M | $12.4M | +$4.0M | High |
| Unified Customer Data Platform | $38.0M | $32.0M | $4.1M | –$6.0M | Med |
| Supply Chain Velocity | $44.0M | $46.0M | $22.0M | +$2.0M | High |
| Digital Loyalty Reboot | $22.0M | $18.0M | $5.5M | –$4.0M | Med |
| Merchant Tools Modernization | $14.0M | $10.0M | $3.0M | –$4.0M | Low |
| Portfolio | $180.0M | $172.0M | $47.0M | –$8.0M | Med |
The one view Finance and TMO have to agree on before anything else. Plan is the baseline signed by the board. Forecast is current best estimate. Actuals are cash that's already hit the P&L, or the run rate. Leadership reads the variance column first.
You can copy a template. You can't copy the reasoning behind it. Six choices I made on the artifacts above, and the thinking on each.
The most common failure I've seen in transformation reporting is a deck that arrives at the ask on slide 38. Executives are always short on time. The decision doesn't get any better for coming after the RAG chart. If the room ends early, at least the decision still got made.
The fastest way to lose an executive audience is to hold NPV flat when everyone in the room knows the story is more complicated. Naming the $8M erosion, alongside the $6M pickup from Store Tech, earns the permission you'll need for the harder asks later. Once someone catches you padding a forecast, they read the next one differently.
One dot hides the trade-off the sponsor needs to see. Splitting the dimensions makes it visible. "We can pull schedule green by pushing scope amber. Do you want that?" That's the conversation the TMO exists to force.
Naming a specific VP or SVP does two things. It forces a real accountability conversation at intake. And it means the risk log is escalation-ready by default. When R-08 goes red, the SteerCo already knows who's answering the question.
Executives triage on Sunday night. A five-pager gets three pages skimmed. Two pages, decisions on top, everything else linked out. The purpose is to make Monday sharper, not to prove the TMO did the work.
These artifacts would look substantially the same at any $5–20B retailer partway through a transformation. Using a real name would trade signal for the impression of endorsement, and nobody wins from that.