Silicon Valley Startup Sprint Retrospective

Silicon Valley Startup Sprint retrospective format

Shipped & Won

What did we ship that created value this sprint?

Start with the wins: features shipped, milestones hit and small experiments that paid off. Ask the team to think like founders measuring traction. What moved the needle for the product or the customer? Invite quieter members to share small wins too.

What Slowed Us Down

What blockers or friction killed our velocity?

Here the team names the bottlenecks, dependencies and distractions that drained momentum. Treat them as drag on the system, not anyone's fault. Look for patterns that recur across sprints, since fixing one of those often pays off most, and ask why each issue happened.

What We Learned

What new insight or validated learning did we gain?

This area records what the team learned this sprint about customers, the product or how you work. Frame each point as a hypothesis: what did we assume, and what did the data tell us? Writing the lessons down means each sprint builds on the last.

Pivot or Persevere

What should we double down on, change, or cut?

This is the founder's decision point. Based on what you shipped, learned and struggled with, where do you go next? Push the team to make clear calls: persevere on what's working, pivot where the data says so and kill what isn't earning its keep. Give each decision an owner so the next sprint starts with a direction.

When to use this retrospective

• At the end of a product sprint, when you want a quick review that looks forward.
• For startup teams, founders and innovation teams who want to move fast and stay focused on customers.
• When the team faces a decision about whether to pivot, persevere or cut a piece of work.
• When your retrospectives have become routine and a build-measure-learn framing would change the conversation.

Suggested icebreaker questions

• If your team were a startup pitching at a demo day, what would your one-line elevator pitch be?
• Which famous tech founder's mindset would you want to channel for this sprint, and why?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

• Set the tone up front: this is about learning fast, not assigning blame. People share more when it's safe to be wrong.
• Use hypothesis language: what did we assume, and what did the results actually show?
• Timebox each topic to keep the pace up. A short list of real points beats an exhaustive one.
• In Pivot or Persevere, push for clear decisions with owners, not vague intentions.
• Use anonymous input in TeamRetro so the loudest voice doesn't decide the wins and the calls.
• Track recurring blockers across sprints to find the problems worth a bigger fix.

Frequently asked questions