Starfish Retrospective

Identify areas for improvement and growth in a structured way.

Use this template in TeamRetro

Start

What new practices or initiatives should we start?

We should start having weekly check-in meetings to improve communication.
Let's start using a project management tool to better track tasks and deadlines.
I think we need to start involving stakeholders earlier in the process.
More of

What existing strengths should we do more of?

We should have more brainstorming sessions to generate innovative ideas.
Let's do more pair programming to share knowledge and catch issues early.
I think we need more frequent client check-ins to ensure we're meeting their needs.
Continue

What positive aspects should we continue?

We should continue our daily stand-up meetings to stay aligned.
Let's keep using the code review process – it's really helped improve quality.
The team building activities have been great for morale, so we should continue those.
Less of

What areas need to be scaled back or reduced?

We need to have less meetings that don't have a clear agenda or purpose.
Let's spend less time on low-priority tasks and focus on critical deliverables.
I think we should have less context switching between multiple projects.
Stop

What unproductive practices should we stop?

We should stop working overtime – it's leading to burnout and mistakes.
Let's stop relying on outdated tools and upgrade our tech stack.
I think we need to stop making decisions without considering all stakeholder perspectives.

What is the Starfish retrospective?

The Starfish retrospective is a technique developed by Patrick Kua to help teams reflect on varying degrees of actions and activities rather than simply the traditional what went well or what did not go well. The five key areas explored are: 1. Start: New practices or initiatives to begin. 2. More of: Existing strengths to amplify. 3. Continue: Positive aspects to maintain. 4. Less of: Areas that need scaling back. 5. Stop: Unproductive or detrimental activities to discontinue. By categorizing feedback into these actionable sections, teams can easily pinpoint growth opportunities and develop a clear plan for the next iteration. The Starfish retrospective promotes open discussion, continuous improvement, and team alignment.

Starfish retrospective format

Start

What new practices or initiatives should we start?

Encourage the team to think creatively about untapped opportunities.

More of

What existing strengths should we do more of?

Highlight the team's positive attributes and successful approaches.

Continue

What positive aspects should we continue?

Reinforce the practices that are working well for the team.

Less of

What areas need to be scaled back or reduced?

Identify areas of overemphasis or inefficient use of resources.

Stop

What unproductive practices should we stop?

Encourage the team to let go of habits or processes that are no longer serving them.

When to use this retrospective

  • At the end of a project or major milestone to identify areas for improvement in the next phase.
  • During a process review to optimize workflows and eliminate inefficiencies.
  • After a team restructuring or change in leadership to realign and set new goals.
  • Periodically (e.g., quarterly) to maintain a culture of continuous learning and growth.

Suggested icebreaker questions

  • If our team was a type of fish, what kind would we be and why?
  • What's one thing you've learned recently that has made you more effective at work?

Ideas and tips for your retrospective meeting

  • Encourage open and honest feedback by creating a safe, judgment-free environment.
  • Assign a dedicated facilitator to guide the discussion and ensure all voices are heard.
  • Focus on actionable items rather than dwelling on past mistakes or assigning blame.
  • Prioritize the most impactful items and create a clear action plan for addressing them.
  • Follow up on action items in subsequent meetings to ensure accountability and progress.

New to retrospectives? Read our guide on how to run a retrospective →

Related templates

Four Ls Retrospective

A structured reflection using Liked, Learned, Lacked, and Longed for categories to analyze sprint performance

What? So What? Now What? Retrospective

A structured reflection framework for systematic problem analysis and action planning

Agile Retrospective

A structured way to reflect on the past sprint and identify improvements.

Start Stop Retrospective

Retrospective Idea - A focused retrospective for clear, actionable team improvements