There is no monthly steering committee and no status deck. There is one 15-minute standup a day, customer and TRANXACT together, in front of the countdown board and the live tenant — and decisions are made the same day, because overnight waits are the enemy of the clock.
Two named owners
| Role | Side | Owns |
|---|---|---|
| Countdown Owner | Customer | Same-day authority on scope; signs the Fit Ledger and the go / no-go |
| Flight Lead | TRANXACT — the AI Deployment Orchestrator | Runs the board and the standup; protects the date |
| Ledger Architect | TRANXACT | Configuration design, integrations, Fit Ledger patterns |
| Data Migration Conductor | TRANXACT | Migration Cockpit, mocks, reconciliation, cutover runbook |
| Autonomous Operations Pilot | TRANXACT | Tenant, SSO, environments, dry-run and go-live operations |
| AI Adoption Navigator | TRANXACT | Queues, ASK, coaching in the flow, adoption and change |
| Key users — one per process | Customer | Discover by doing, validate configuration, run the rehearsal |
| Finance controller and data owners | Customer | Cleanse data; sign reconciliations and opening balances |
The Countdown Owner must be able to make scope calls the same day without escalation. If that person does not exist, the countdown should not start.
The RACI in one line
The Countdown Owner is Accountable for everything. Responsibility moves with the work: the Flight Lead and Ledger Architect for the Fit Ledger, the Ledger Architect and key users for configuration, the Migration Conductor for mocks and reconciliation, the Flight Lead, Conductor and Ops Pilot together for the runbook and dry run, the Adoption Navigator and key users for adoption and change and for the rehearsal.
- Same time every working day, T-0 included; both owners present or delegated in writing.
- No slides: the board, the Fit Ledger and the tenant only; decisions logged in the Toolkit’s Countdown Board sheet.
- Problem-solving moves to a named break-out afterwards — the standup records the scope call and its owner, nothing more.
- After go-live it becomes the hypercare standup on yesterday’s exceptions.
The Fit Ledger replaces the requirements document
One public line per gap found on a screen: what is on screen, what is needed, the decision, the configuration pattern or wave, and the owner. Once the Countdown Owner signs a decision it is not reopened; a change of mind becomes a new line with a new date.
Rule 3 applies at the second question: if it needs code, the answer is a configuration pattern, T-Plus, or an honest no — the extension framework, never the countdown. A gap that cannot be configured and rehearsed before T-3 goes to T-Plus automatically, unless the Countdown Owner drops something else to make room.
The countdown board
One page for everyone: working days to go-live, the next gate, percent complete and a line of status per workstream, and the Fit Ledger totals. It is mirrored from the Project Plans dashboard, so days left come from the go-live date and status rolls up from every source-system plan.
Calderwood at T-12: 64 Fit Ledger lines — 41 configure now, 15 T-Plus, 8 not needed. Testing is at 55% because integration tests start at T-10; the board shows it in red, and the standup records who owns clearing it rather than debating it.
Try it At T-9 the finance team asks to reopen FL-004 — the legacy "daily cash v7" report, signed off as Not needed at T-20. What happens?
The signed line is not reopened. If the need is real, it becomes a new Fit Ledger line with today’s date and goes through triage: with T-3 so close, the likely outcomes are that the dashboard still covers it, or it goes to T-Plus — unless the Countdown Owner drops something else to make room.