Deployment Labs
Module 7 · Lesson 5 of 5 · 8 min

Your owners, review dates and meetings

Who owns what, when each thing is reviewed, and the meetings, ready for the calendar.

This is the page each function leader signs for the items in their area. It lists everything shared or high-stakes that runs, who owns it, who can stop it, whether the undo has been tested and when it's next reviewed. Then it puts the loop's clock in the calendar: the three meetings and the two service levels.

Anything still missing is flagged below, with a link back to the lesson where you add it. An orphan on this page is the one thing that should never reach day 90.

Your ownership plan: 0 of 10 parts done0%
Items to own →Owners and backups →Off switches and undos →Undos tested →Review dates →Weekly meeting →Quarterly session →Annual review →Front door →Day 0, for the bottleneck checks →
Ownership plan · The Deployment Framework

Your organisation

Your first 90 days with AI

The rule we keep
Everything shared or high-stakes that runs has an owner, a backup who can stop it, and a review date.
0
Items
0
Owned
0
Orphans
0
Undos tested
The ownership register
Nothing listed yet. Add it
The review calendar
No review dates yet. Add it

Each review takes fifteen minutes: still used, still safe, still worth what it costs? Three yeses, keep it and set a new date. Any no, fix it or retire it.

The three meetings
Weekly
Mondays at 09:30. Every team, 20 minutes.The friction list and its statuses · Problems with AI output · Reviews coming due
Quarterly
Not set yet. Add it
Annually
Not set yet. Add it
The two service levels
Front door
Not set yet. Add it
Bottleneck check
The bottleneck lead checks the handoffs between teams every two weeks during the first loop, then monthly.
Function leader
Runs the loop
Date
Your output

Get the print-ready ownership plan

Your details unlock printing, saving as PDF and copying the ownership plan. A copy comes to Deployment Labs so we can help if you want it.

  • Print or save as PDF, ready for each function leader
  • Copy the register as text
  • A calendar file with every meeting and review date

Taking the course with your leadership team? Use the same team code, and your answers can be compared when we talk.

By continuing, you agree to receive emails from Deployment Labs about this course and related resources. You can unsubscribe at any time. Privacy policy

What happens next

Day 90 is the first quarterly session, and it's module 8. You'll score the loop against the prediction you wrote down in module 4, follow the freed time to where it actually went, and make a keep, fix or retire call on everything that ran this loop, using the owners and review dates on this page. Then you'll name the next bottleneck, because fixing one always exposes the next.

Owning what runs is the step most easily skipped, and a pilot tests it hard: a shared or high-stakes item running with no owner counts against the framework. If you'd like help running it, Deployment Labs runs this first loop with leadership teams as a guided pilot. Book a call and bring this page. Or go on to module 8: Day 90.

Finished this lesson?

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

← Previous
The three meetings
Next lesson →
Scoring against your prediction