Retrospectives Template

Diagnose process issues and align on high-impact continuous improvements.

Quick Facts

Best ForContinuous Improvement & Sprint Reviews
Time Required30–45 mins
Participants3–10 team members
Typical OutputAn actionable list of process updates with assigned owners.

What is a Retrospectives?

A Starfish Retrospective is a post-sprint reflection framework that goes beyond binary feedback to help teams keep, stop, start, amplify, or scale back activities.

When to use it

Use it at the end of every sprint, after releasing a major product feature, or when team throughput is slowing down due to operational friction.

How to complete the Retrospectives

Have the team silently brainstorm feedback across 5 categories: Keep Doing, Less Of, More Of, Stop Doing, and Start Doing. Group similar items, vote on the highest-priority topics, and assign owners to action items.

Why use an interactive Retrospectives template?

Post-it notes get lost and status reviews feel repetitive. Methodiq automates silent reflection, clusters cards dynamically, and tracks action item completion directly in your workspace.

Multiplayer Canvas

Collaborate live with your team on a shared, infinitely flexible workspace.

AI Facilitation

Medi guides you with context-aware prompts and captures findings automatically.

Actionable Plan

Exit the session with real tasks, assignees, and next steps documented.

Guiding Questions

Start Doing

  • What new experiments or processes should we introduce in the next sprint?
  • What tools or behaviors can solve current roadblocks?

Stop Doing

  • What activities are wasting team time without adding value?
  • What friction points should we eliminate immediately?

Keep Doing

  • What worked exceptionally well during this sprint?
  • What practices must we protect and maintain?

More Of

  • What processes are working but should be scaled up or done more frequently?
  • Where can we amplify our efforts for higher impact?

Less Of

  • What practices are useful but currently taking up too much time?
  • Where should we reduce our focus or scale back?

Real-world Examples

A retrospective held after releasing a feature response to a key competitor's launch.

Start Doing

Monitoring rival public changelogs weekly
Pre-sprint competitive gaps audit

Stop Doing

Rushing code without QA review under competitor pressure
Relying on assumptions about rival pricing strategies

Keep Doing

Cross-functional marketing and tech alignment check-ins
Customer success feedback tag systems

More Of

Prototyping core UI variations early
Customer research interviews on rival features

Less Of

Scope creep during emergency feature releases
Duplicate bug reports across teams

Ready to start?

Run a free interactive session.