Friday — The Landing

Duration: 30 minutes Facilitator: Rotates weekly When: End of the week (Friday by default; shift to match your working week)

Purpose

Show what landed, decide every active Preview, and capture learning. This is the heartbeat of Speedboat: the moment where progress becomes visible and decisions get made.

A Landing is a meaningful outcome: something reached a real beneficiary, or new evidence changed what happens next.

Before the Meeting (Facilitator, 10 min prep)

Review the board — what moved to Landed this week?
List every active Preview that needs a decision
Pull up the Landing Log (ready to update live)
Note any reactive Run that hit the team this week

Script

Time	Activity	Detail
0–10 min	Landings	Walk each landed item. For each: what landed, who benefited, what type, and what changed? Update the Landing Log live.
10–20 min	Preview Decisions	For every active Preview: Kill / Park / Continue / Promote. No Preview leaves without a decision. If promoting, assign a Code-Reuse Label. If killing/parking, state what we learned. Max one continuation per Preview (no indefinite “continue”).
20–25 min	Learning	What did we learn this week? What should we adjust next week? One or two points, not a full Learning Review.
25–30 min	Run Check	What reactive work hit us? Was it expected? Should any of it generate proactive Run work to prevent recurrence?

The Landing captures tactical learning. Use the separate Learning Review every 4 weeks for a wider look at whether the model, WIP limits, and Landing mix are working.

When you note WIP in the weekly snapshot, count meaningful work items, not individual tickets or subtasks.

Outputs

Landing Log updated with this week’s Landings
Every Preview has a recorded decision + rationale
Promoted Previews have a Code-Reuse Label assigned
Board is clean: nothing in limbo going into the weekend
Weekly Snapshot ready to post (see template below)

Preview Decision Framework

Decision	When to use	What happens next
Kill	Idea disproven, not viable, not valuable enough	Log the learning. Card → Killed.
Park	Interesting but not now — timing, capacity, or dependency issue	Log why. Card → Parked. Revisit in Route Planning.
Continue	Needs ≤1 more week to reach a decision point	Set a new timebox. This is the LAST continuation — next Friday it must be killed, parked, or promoted.
Promote	Validated and worth building properly	Assign Code-Reuse Label. Create Build card. Preview card → Promoted.

Landing Log Entry (fill in for each Landing)

Field	Value
Date
Title
Landing Type	Customer / Business / Platform / Decision
Beneficiary	Who specifically benefits?
Outcome	What changed? What’s true now that wasn’t before?
Source	Promoted Preview / Roadmap / Customer need / Run
Notes	Anything else worth recording

Weekly Snapshot (post to team channel after the meeting)

**Week [N] Snapshot**
🟢 Landed: [list items + landing type]
🔵 Preview decisions: [item → kill/park/continue/promote]
🔴 Didn't land (intended but missed): [item + why]
⚙️ Run: X% reactive, Y% proactive
📊 WIP: N Preview, N Build
💡 Key learning: [one line]

Anti-Patterns

Don’t demo work without stating beneficiary and outcome. Do answer who benefited and what changed for every Landing.
Don’t let Previews continue indefinitely. Do allow one continuation at most, then make a hard decision next Friday.
Don’t skip the learning question. Do capture at least one sentence so the week compounds.
Don’t treat The Landing as a performance review. Do keep it about the work, not the individuals.
Don’t try to do a full process review in five minutes. Do capture tactical learning here and save wider model questions for the Learning Review.
Don’t rush through to end early. Do use the full 30 minutes; this is where Speedboat generates value.
Don’t forget to update the Landing Log. Do log the work if you want it to count as landed.