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, capture learning. This is the heartbeat of Speedboat — the moment where progress becomes visible and decisions get made.

A Landing is not a queue of work. It is the moment completed work becomes visible in terms of beneficiary and outcome.

---

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 shipped, who benefits, what type, 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 & Retro	What did we learn this week? What would we do differently? One or two points, not a full retro.
25–30 min	Run Check	What reactive work hit us? Was it expected? Should any of it generate proactive Run work to prevent recurrence?

---

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	✅ Do
Demo without stating beneficiary and outcome	Every Landing answers: who benefited and what changed?
Let Previews “continue” indefinitely	One continuation max. Next Friday is a hard decision.
Skip the learning question	Even one sentence makes the week’s work compound
Treat it as a performance review	This is about the work, not judging individuals
Rush through to end early	The Landing is where Speedboat generates its value — give it the full 30 minutes
Forget to update the Landing Log	If it’s not logged, it didn’t land (for measurement purposes)