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

Your front door and build case

How requests come in, who answers, and the case for the first thing worth paying for.

This is how requests come into your loop, and the case for the first thing worth paying for. The person who runs the loop announces the front door to everyone. The case and its proof plan go to the leadership team's quarterly meeting, where builds are funded inside the spending ceiling.

Anything still missing is flagged below, with a link back to the lesson where you add it.

Your front door and build case: 0 of 13 parts done0%
Where things are raised →Who answers →Uses classified →Case: value →Case: running cost →Case: people →Case: risk →Case: options →Proof: stage 1: the sandbox →Proof: stage 2: the live trial →Proof: works, fair, safe →Proof: who checks the evidence →Proof: kept or killed →
Front door and build case · The Deployment Framework

Your organisation

Your first 90 days with AI

The front door
Set up your front door in lesson 1.
Adopt it
The default for something someone already made. The maker gets credit. If it's shared, it goes to Own.
Park it
It goes on the friction list, with a status everyone can see.
Build it
Only once redesign and the approved tools have been ruled out. It goes to the one-page case.
When you raise something
The work, never the person. Where it waits, piles up or gets redone. Anything you've already made, so you get the credit.
Measured
Days from raising something to its first answer. The median, and the split of adopt, park and build, every two weeks. A median over 10 working days counts against the framework.
Uses classified: shared and stakes
None classified yet. Run your uses through the two questions
The one-page case
Value
Not set yet. Add it
Cost
Not set yet. Add it
People
Not set yet. Add it
Risk
Not set yet. Add it
Option
Not set yet. Add it
The proof plan
Stage 1: sandbox
Not set yet. Add it
Stage 2: live trial
Not set yet. Add it
It has to show
Not set yet. Add it
Evidence checked by
Not set yet. Add it
Kept or killed
Not set yet. Add it
Runs the loop
Sponsor
Date
Your output

Get the print-ready front door and build case

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

  • Print or save as PDF, ready for the quarterly meeting
  • Copy as text for your own documents
  • The checklist for opening the door and funding the case

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

Two kinds of thing now need an owner. Anything the front door adopts that's shared, and anything the live trial keeps. Module 7 gives each of them an owner and a backup who can stop it, an off switch and a tested way to undo it, and a review date in the calendar. It also sets up the three meetings that keep the whole loop turning, including the quarterly one where your case gets its answer.

In a pilot, Deployment Labs can act as the builder of record if you don't have one, working from the same case and proof plan. If you'd like help, book a call and bring this page.

Finished this lesson?

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

← Previous
Two-stage proof
Next lesson →
Owners and backups