Speedboat — Monthly Stakeholder Summary

Prepare this every 4 weeks for leadership, Product, Sales, and adjacent stakeholders.

Use the Landing Log and the last 4 Weekly Snapshots as inputs. Keep it short. This is not a status report and not a roadmap deck.

The goal is to answer three questions:

What landed in the last 4 weeks?
What does the landing mix tell us?
What is likely coming next?

Draft it before the 4-week Learning Review so the team can look back at delivered outcomes and use that evidence in the discussion.

Template

📍 Speedboat — Monthly Stakeholder Summary
   [Team name] — [Date range]

1. WHAT LANDED IN THE LAST 4 WEEKS?
   • [Outcome] — [Landing Type] — [one-line beneficiary/outcome]
   • [Outcome] — [Landing Type] — [one-line beneficiary/outcome]
   • [Outcome] — [Landing Type] — [one-line beneficiary/outcome]

2. WHAT DOES THE LANDING MIX TELL US?
   Customer: [N]
   Business: [N]
   Platform: [N]
   Decision: [N]

   [2–4 sentence readout.
   What pattern do we see?
   Is the mix healthy for this period?
   What trade-offs or learning matter most?]

3. WHAT IS LIKELY COMING NEXT?
   • [Likely next focus area or Landing]
   • [Likely next focus area or Landing]
   • [Known risk, dependency, or uncertainty if relevant]

Tips

Derive, don’t rewrite. Pull from the Landing Log and Weekly Snapshots rather than creating a new reporting burden.
Lead with outcomes. Stakeholders care more about what changed than about internal activity.
Show the mix, not just the highlights. The balance between Customer, Business, Platform, and Decision Landings tells an important story.
Use “likely” on purpose. This is not a commitment document. It should show direction and shaping, not false precision.
Keep it to one screen if possible. If it gets long, you are adding more detail than stakeholders need.