Module 8 · Lesson 5 of 5 · 10 min

Your day-90 readout

The loop scored honestly, the freed time followed, and the next loop named.

This is the readout for your first loop. It scores the loop against the prediction you locked on day 14, follows the freed time, records what was kept, fixed and retired, and names the next bottleneck. Write it in the week after day 90, and share it with your sponsor.

Its first line is fixed. If anything on the pre-set list counts against the framework, the readout says so there, before anything that supports it. Most of the readout fills itself in from the earlier modules. A few numbers no earlier lesson captured go in the form below. Anything still missing is flagged, with a link back to where you add it.

Your readout: 0 of 11 parts done0%

Bottleneck scored →Improve's exit →The aim's outcome →Conversion ledger →Truth-telling →Front door →Keep, fix or retire →Role grid →Incidents and changes →Rework →Next bottleneck →

Organisation name

BuildThe numbers no earlier lesson captured

The aim

Your goal from module 1. Not set yet →

Day 0

—

Day 90

Rework

Items sent back, corrected or redone at the bottleneck and the step after it, day 0 against day 90.

Truth-telling

AI tools found by monitoring, or by expense and single sign-on records, and how many were also disclosed. Then the pulse question ‘Do you believe the disclosure promise?’, as % yes.

Tools foundAlso disclosedTrust, day 0%Trust, day 90%

The front door

Median working days from raising something to its first answer, and how answers split. The service level is 10 working days. Not set yet →

Median daysAdoptParkBuild

The role grid

On day 90, each cell marked done, partly or not done. The share done, and which cells were never filled.

Cells done%Never filled

Incidents

How many went through stop, tell, fix, learn, and what was learned. No names.

CountWhat was learned

Changes

Anything changed after the prediction was locked on day 14, and why. The original is still scored.

Anything that makes it inconclusive?

Inconclusive is recorded as inconclusive, never as a success.

The window was cut short
The organisation changed in the middle of the loop
A measure couldn't be collected

Pulse surveys and disclosure counts are only ever reported as totals. No names anywhere in the readout.

Day-90 readout · The Deployment Framework

Your organisation

Your first 90 days with AI

First line

Nothing on the pre-set list counts against the framework. 8 of 8 checks have no number yet.

Verdict

Inconclusive

Not everything was measured: 8 of 8 checks have no number. Recorded as inconclusive, not as a success.

Next bottleneck not named yet. Add it

Set day 0 to see loop 2's dates. Add it

1 · The bottleneck

Predicted against actual: Not set yet. Add it
The early dip: Not set yet. Add it
Improve's exit: Not set yet. Add it

2 · The aim

Goal: Not set yet. Add it
Day 0 to day 90: Not set yet. Add it

3 · Where freed time went

The conversion ledger is empty. Add it

4 · Truth-telling

Disclosure against telemetry: Not set yet. Add it
Trust in the disclosure promise: Not set yet. Add it

5 · The front door

First answers: Not set yet. Add it

6 · Build and Own

Nothing reviewed yet. Add it

7 · The role grid

Cells done: Not set yet. Add it

8 · Incidents

Count and lessons: Not set yet. Add it

9 · Changes

After day 14: Not set yet. Add it

10 · Verdict

Not measured: The bottleneck hasn't been scored.
Not measured: The aim's outcome at day 90 isn't recorded.
Not measured: Disclosure against telemetry isn't recorded.
Not measured: The pulse survey's trust question isn't recorded.
Not measured: The conversion ledger is empty.
Not measured: The front door's response time isn't recorded.
Not measured: There's no AI list to check owners against.
Not measured: Rework at the bottleneck isn't recorded.

Inconclusive. Not everything was measured: 8 of 8 checks have no number. Recorded as inconclusive, not as a success.

The next loop

Next bottleneck: Not set yet. Add it
Loop 2: Not set yet. Add it
Quarterly meeting: Not set yet. Add it

Leads the bottleneck

Runs the loop

Sponsor

What happens next

Day 91 is day 1 of the next loop. The moves are the same, and so are the forms. The leadership team confirms the next bottleneck at the quarterly meeting. The person who leads it writes the prediction and locks it by day 14, as you did in module 4. Then improve the work around it, take anything worth paying for to the front door, give whatever runs an owner and a review date, and score it again on day 90.

Print or save this readout before you start. Your answers live in this browser, and the next loop's answers replace this one's, so the readout is your record of loop one. Each loop gets easier: the guardrails are in place, the AI list is started, the meetings are in the calendar, and the friction list is already full of candidates.

Your first 90 days with AI · complete

You've run one full loop.

An aim and four promises. Guardrails before day 0, and the AI already in use brought into the open. One bottleneck, a prediction written down first, and the work improved around it. A front door, owners and review dates. And today, the loop scored honestly.

Loop 2 starts on day 91.

Want a second pair of hands for the next one? Deployment Labs runs this loop with leadership teams as a guided pilot, using the same forms.

Book a call

Finished this lesson?

Mark it complete. Your answers are already saved in this browser.

← Previous

Naming the next bottleneck

Module 8 done →

Back to the course · 46 min module

Your day-90 readout

Your organisation

Get the print-ready readout

What happens next

You've run one full loop.