Speedboat — Trial Evaluation
Use this at the end of a 4–6 week trial to decide: continue, adjust, expand, or stop.
Trial Summary
| Field | Value |
|---|---|
| Team | |
| Trial dates | |
| Team size | |
| Product partner | |
| Facilitator / owner | |
| Recommendation | Continue / Adjust / Expand / Stop |
One-paragraph conclusion
Write the shortest honest summary you can.
What changed, what evidence matters most, and what you recommend next.
1. Primary Indicators
These decide whether the trial worked.
| Indicator | Baseline | End of trial | Direction | Evidence / notes |
|---|---|---|---|---|
| Cadence and mix of Landings | Better / Flat / Worse | |||
| Time from roadmap idea to credible demo | Better / Flat / Worse | |||
| Quality and sustainability | Better / Flat / Worse | Escaped defects, rollback rate, support load, focus |
Call
- What improved materially?
- What stayed flat?
- What got worse?
- Is there enough evidence to continue?
2. Diagnostic Signals
Use your Landing Log, Weekly Snapshots, and board data.
| Signal | Target / question | What happened? |
|---|---|---|
| WIP held within limits | Mostly stayed within Preview 3 / Build 3 | |
| Preview decisions | Every active Preview got a Friday decision | |
| Started vs Landed ratio | Moving closer to 1.0 | |
| Run visibility | Reactive and proactive Run were visible | |
| Preview kill rate | Non-zero |
Landing summary
| Week | Customer | Business | Platform | Decision | Total | Run % (est.) |
|---|---|---|---|---|---|---|
| W1 | ||||||
| W2 | ||||||
| W3 | ||||||
| W4 | ||||||
| W5 | ||||||
| W6 |
What the diagnostics suggest
- Where did the model help most?
- Where did it create friction?
- What patterns showed up repeatedly?
3. Team Feedback
Summarise the Team Survey here.
| Question area | Score / signal | Notes |
|---|---|---|
| Model clarity | ||
| Ceremony usefulness | ||
| Focus and WIP | ||
| Preview vs Build clarity | ||
| Friday pressure | ||
| Overall recommendation |
Themes
- What did the team like most?
- What caused confusion or resistance?
- Did anyone feel the process created unhelpful pressure?
4. Product / Stakeholder Feedback
Capture direct feedback from Product, Sales, leadership, or other stakeholders.
| Stakeholder | What improved? | What did not? | Recommendation |
|---|---|---|---|
| Product | |||
| Sales / GTM | |||
| Engineering leadership |
5. Keep / Change / Drop
| Keep | Change | Drop |
|---|---|---|
Use this to separate the model itself from your local implementation details.
6. Final Recommendation
Choose one and explain why.
Continue
The model is working as-is well enough to keep running.
Adjust
The model is promising, but needs specific changes before continuing.
Expand
The model worked well enough to extend to another team or larger scope.
Stop
The model did not improve outcomes enough to justify continuing.
Decision note
What exactly are you deciding, and what will happen next?
- Decision:
- Effective date:
- Owner:
- Follow-up actions: