One program, end to end.
Every number below is a row in one real workbook. Nothing is rounded up, and nothing is a mockup.
Halden Industrial
SAP ECC → S/4HANA
123 outcomes
5 departments
24 complete
22 with no owner
Go live 22 March 2027, off hypercare 20 April · read 15 September 2026
One of thirteen
ERP Carve-out M&A EHR
Core banking CRM HCM Data platform
Data centre exit Identity Endpoint
Digital and AI or your own +7 more
I Builds
II Knows
III Runs
IV Reports
V Proves
VI Lands
Agentic AI, on one workbook. It does all six of these at once and never
stops. You read them one at a time.
Showing every panel . See it as
a sponsor ,
a program manager ,
a workstream lead or
PMO .
Showing what sees — in this act.
Show every panel
ACT I It builds
Four answers in. A whole program out.
Week one · the conversation
Six weeks of workshops. Stale the week after.
One conversation, not six weeks of workshops. It stays true because people answer.
ForProgram manager
5
departments
15
process areas
123
outcomes
0 rows written to a Google Sheet you own
Week one · the names
Your tracker has an owner column. It has never asked anybody anything.
Every outcome has a role. Every role has a person. It asks them.
ForProgram manager Workstream lead
People · Halden Industrial
RO
Ruth Okonjo Order Management lead
owns 30
NB
Nadia Belhaj Finance systems
owns 29
SF
Sam Ferreira Manufacturing lead
owns 25
TV
Tomas Vidal Procurement lead
owns 17
GL
Greg Lund Sponsor
escalation
—
IT and Data no person in any of its roles
22 unowned
Not an empty cell — the issue the
agent opened . Twenty-two outcomes, nobody to ask.
ACT II It knows
Ask it anything. The answer is arithmetic, not opinion.
Any morning · you open it
“Where are we?” costs your team two days a fortnight to answer.
ForEveryone
Four lines, and the working behind each. The last one is a finding nobody asked for.
Halden Industrial, this morning.
Read out of your workbook. Nothing here was typed by a person.
Nothing moved since 15 Sep 2026. No date changed, nothing new was found,
and nothing that was fixed has come back.
The window
10 Feb 2027 to 21 Mar 2027
The 123 outcomes
22 with no owner, 20% complete
The pipeline
3 stages, 0 of 0 through them
Capacity
IT and Data has work coming and nobody to do it.
⚠
IT and Data has work coming and nobody to do it. 480 hours are forecast
against IT and Data DEP-005, peaking in February 2027 , and no
person is named in any of its roles. Nothing here can start until somebody is.
By month
By team
Per person
208 Aug
212 Sep
460 Dec
820 Jan
520 Feb
108 Mar
Sized, dated work by month. The tallest is where the program is tightest, and
it belongs to nobody .
What is open against me?
What changed since yesterday?
What will I be asked on Friday?
Any morning · the shape of it
Where the work is behind, and who you can ask about it.
ForSponsor Program manager
Sorted by distance from their own plan, each against its owner. Two have none.
Order Management
30 outcomes · 3 complete
6 past their date
RO Ruth Okonjo
Finance
29 outcomes · 4 complete
4 past their date
— No owner named
Manufacturing
25 outcomes · 6 complete
4 past their date
SF Sam Ferreira
IT and Data
22 outcomes · 4 complete
2 past their date
— No owner named
Procurement
17 outcomes · 7 complete
2 past their date
TV Tomas Vidal
Two of five have nobody to ask. Eighteen outcomes are past their date and none is done — while twenty-four that were never
due are.
The day a date moves
Everything holds dependencies. Nothing tells your sponsor what they cost.
One date moves. It walks the chain and says what go live now costs.
ForSponsor Program manager
Milestones · finish to start, no lag
Data ready
11 Feb
Build done
19 Feb
Ready to test
4 Mar
Training done
18 Mar
Go live
22 Mar
Hypercare done
20 Apr
Data ready slipped 14 days. All five behind it moved, go live is
now 5 April, and the program does not come off hypercare
until 4 May.
ACT III It runs
Between Thursday and Thursday, with nobody logged in.
02:14, Tuesday
Nothing happens between meetings except decay.
It re-dates, chases and escalates. You were asleep.
ForProgram manager
HeyPM Nobody asked for this. You were asleep.
02:14 Tuesday
02:14
Re-dated three milestones behind Data ready — go live now 5 Apr
03:40
Chased four owners who did not answer Monday
05:02
Escalated the legacy retirement date to Greg Lund — 31 days
unanswered
07:58
Sent five briefs, each one only what is theirs
You were asleep for all of it.
07:58, every weekday
Status is somebody’s job. That is the problem.
Each person is asked only what is theirs. Which is why they answer.
ForProgram manager Workstream lead
HeyPM Nobody asked for this. 07:58, every weekday.
07:58 Halden Industrial
168 rows read · 5 people · 6 milestones
RO
Ruth Okonjo 3 open
NB
Nadia Belhaj answered
Proposed from her answer
Mark “Quote configuration runs end to end” complete — evidence
attached.
Not yet
Yes, apply
Tuesday · nobody answered
Nobody logs in. The owner still owns it.
Three levels, on a clock, run by the agent instead of by you on a Friday.
ForSponsor Program manager Workstream lead
Escalation path · an Order Management outcome
Level 1
Ruth Okonjo — ownerAsked Monday. Chased Tuesday.
Level 2
Department leader is Ruth againCollapsed — never the same person twice.
Level 3
Greg Lund — sponsorReached Wednesday, with what was asked and when.
The owner still owns it. Not
answering is now visible, dated, and on its way to their
sponsor .
Tuesday · the ladder came back empty
A name you cannot escalate to.
A tracker cannot raise this. It does not know an owner column ends in an inbox.
ForProgram manager PMO & assurance
HeyPM Nobody asked. The ladder came back empty.
Detection · NO_ESCALATION_PATH
Critical
Nobody to tell
Twenty-two outcomes in IT and Data resolve to no person at level one, so there is
nothing to escalate.
22 outcomes 0 contactable
An unanswered ask would sit there, and nobody
would be late. It is the same twenty-two that go
untrained.
ACT IV It reports
The one document nobody has time to build properly.
Thursday · the number you are asked
Ahead of plan, and late on everything that was due.
ForSponsor PMO & assurance
Both halves are true at once. A percentage complete tells you only the first.
The plan said, by today
0 of 123
Wanted finished by 15 September.
Complete today
0 of 123
Signed off, evidence attached.
The gap
+4.9pts
Six ahead. On any dashboard, this is green.
Except that all eighteen outcomes the
plan wanted by today are still open — and all twenty-four that are finished
were never due yet.
The team has been working on the wrong twenty-four. The percentage is the same either way.
Thursday · the fortnight behind you
Two weeks, on one line.
ForSponsor PMO & assurance
Five things moved, each with who moved it and why. Ordered, not remembered.
2 Sep
Data ready moved 14 days
The extract is not ready.
Ruth Okonjo
2 Sep
Three milestones re-dated
Go live 22 Mar → 5 Apr.
agent
5 Sep
Nobody to tell, raised critical
22 outcomes uncontactable.
agent
12 Sep
Quote configuration signed off
Evidence attached, then approved.
Nadia Belhaj
15 Sep
Legacy retirement escalated
31 days open. Sent to the sponsor.
agent
Three of the five were the agent.
The other two are people answering by name.
Thursday · the first ask
What we need from you.
One open decision, with an age on it so nobody can let it drift again.
ForSponsor
Decisions still open · 1
Decision · open
The retirement date for the legacy order system
Everything behind Legacy retirement is planned against an answer nobody has given.
31 days unanswered
The age is the point. A decision log
says it is open. This says what it has cost.
Thursday · the second
What we have signed up to.
On this program, the commitment is the finding.
ForSponsor PMO & assurance
Committed before 29 September
Nothing.
No outcome is dated between 15 September and 7 December.
Sep —
Oct —
Nov —
Dec 26 due
Jan 42 due
Eleven weeks, and a go live in March.
Nobody plans that.
06:00 Thursday · before anyone is in
The most expensive document in your program is retyped every fortnight.
Nine of the thirteen are panels you just read. The pack is the workbook.
ForSponsor PMO & assurance
06:00 on the day
Halden Industrial
Where we are, and what we need from you
What each answer costs
The program, planned against actual
The gate is Data ready, on 11 Feb
What moved in the last fortnight
What you were asked last time
The departments behind, and who owns them
The schedule, and where we are on it
Committed before the next committee
Appendix: every department
13 slides · built from 168
rows at 06:00, nobody asked
ACT V It proves
Everything above is what it does. This is whether you can check it.
All the way through
A RAID log is where problems go to be forgotten.
Risks, decisions, fit gaps, the process map. Each against a name and an age.
ForProgram manager PMO & assurance
RAID Fit gaps
Current → future
Decision
The retirement date for the legacy order system
Open 31 days. Everything behind Legacy retirement is planned against an
answer nobody has given.
Risk
One person carries Order Management with no cover
Ruth Okonjo is the only person who can answer, and there is nobody named to
escalate to.
Issue
Finance has no owner
The department resolves to no person, so escalation from it stops at one
level.
Scope of Legacy retirement is not agreed
High severity, left under review since discovery. Nothing downstream can be
dated until it is dispositioned.
Under review · 31 days
Today
Quote raised in the legacy system
Discount approved over email
Re-keyed into order entry
After go live
Quote configured in S/4HANA
Discount hits the approval rule
No re-key — step removed
Set on day one, tuned all year
A tool enforces your workflow. It does not know your trade.
Fifty-five rules off real programs, in a tab, tuned to yours.
ForPMO & assurance
Delivery Rules · a tab in your workbook
IT baseline Package
Custom build Migration
Data platform Transformation
BR-003
Design after requirements Precedence · 0 days lag
BR-004
Build after design sign-off Build cannot start — Design has no
sign-off attached
BR-011
No date moves inside 10 days of go live Freeze
0 rules, six profiles, all of them yours to tune
Six months later
You can audit what changed. You cannot audit why.
Every write carries its reason and who approved it.
ForSponsor PMO & assurance
Agent Log · Halden Industrial
2 Sep
Data ready moved, 11 Feb → 25 Feb
Owner confirmed the extract is not ready
Ruth Okonjo
2 Sep
Three milestones re-dated behind it
BR-002 · finish to start, no lag — go live now 5 Apr
agent
5 Sep
Critical raised: nobody to tell
IT and Data resolves to no person at level one
agent
12 Sep
Quote configuration marked complete
Test evidence attached, then approved
Nadia Belhaj
None of it was typed as a status. Every line is a record, and every one opens.
ACT VI It lands
Go live is not the end. Adopted is.
Four days before go live
Marked done. Nobody can say who turned up.
A rule in your own workbook refuses it, because attendance is a row, not a tick.
ForSponsor Program manager Workstream lead
Training complete · due 18 Mar 2027
212 people in scope
Completed, with a row against their name148
Invited, did not attend41
Never invited to anything23
BR-023 · EVIDENCE GATE
Training complete cannot be marked done.
Sixty-four people have no completed attendance row. Go live is four days later.
The twenty-three never invited sit in
the two departments with nobody named . Same hole,
twice.
Go live, plus twenty days
Your program ends. The thing you built has to keep working.
The log unlocks at go live. The workbook runs the twenty days nobody staffs.
ForSponsor Program manager PMO & assurance
Hypercare Log · day 4 of 20
Critical
Cash application not posting to the ledger In Progress
High
Credit check times out at volume Open
Medium
Tax determination wrong on interstate orders Resolved
20 Apr
Hypercare closesBR-011 · follows go live, twenty working days
+20 days
Benefits measuredBR-012 · measuring benefits during hypercare measures
noise
Always on
Lessons LearnedOpen from day one, not written from memory at the end
Every program ends with a folder nobody opens again. This one still answers.
Back
Next
What good looks like
Six things become true.
Not features — conditions. On a program run this way they hold, and on one that
is not, every single one of them fails in the same week.
I The plan exists inside a week , and it is the same plan everybody is
working to. It builds
II “Where are we?” has an answer , not a two-day exercise
and a guess. It knows
III Nobody chases anybody. Silence is visible, dated, and on its way
to a sponsor. It runs
IV The pack writes itself at six, from the rows as they stand, and
the asks have ages on them. It reports
V Six months later you can open any change and see who approved it
and why. It proves
VI Go live is not the end of the measuring — training is gated
and hypercare is staffed. It lands
See it on a program as messy as yours.
Twenty to pick from, each with something genuinely wrong in it. Your own copy and
the live agent on it for a week.