FLAP Retrospective

Review lessons, wins and problems, then plan what's next

Try this retrospective live

Future considerations

What direction do we want to take?

We should implement automated testing to reduce manual QA time
I'd like to explore using AI tools to speed up our documentation process
Let's schedule regular knowledge sharing sessions starting next sprint
Lessons learned

What have our experiences taught us?

Early stakeholder involvement prevents late-stage requirement changes
Pair programming really helped reduce our bug count
Daily stand-ups are more effective when we use video
Accomplishments

What are we proud of?

Successfully launched the new feature with zero critical bugs
Improved our test coverage from 65% to 85%
Received great feedback from clients on the new UI
Problem areas

What have we struggled with?

Communication breaks down when team members work remotely
Our deployment pipeline is becoming a bottleneck
We're spending too much time in meetings

What is the FLAP Retrospective?

The FLAP retrospective covers four areas: Future considerations, Lessons learned, Accomplishments and Problem areas. Three of them look back at what happened and one looks ahead, so your team celebrates what went well and deals with what didn't before it plans the next stretch of work. Each quadrant has a job. Accomplishments is for the wins people are proud of. Problem areas is for what the team struggled with. Lessons learned asks what those experiences taught you, and Future considerations turns them into specific next steps. Moving from what happened to what it means keeps the discussion from ending as a list of complaints. FLAP works well after a milestone or release, or at a quarterly review, when you want one meeting that covers both reflection and planning. Start with Accomplishments to give the conversation some energy, then work around to the future.

FLAP retrospective format

Future considerations

What direction do we want to take?

Explore the opportunities and challenges coming up. Push for specific ideas instead of vague hopes, help the team decide which matter most, and turn those into concrete next steps.

Lessons learned

What have our experiences taught us?

Ask what the team's successes and failures taught you. Look for cause and effect and for patterns that keep repeating, then turn each lesson into something you'll do differently.

Accomplishments

What are we proud of?

Make it easy for people to share what they're proud of, from individual wins to team achievements. Ask what difference each one made to the team, the project or your customers.

Problem areas

What have we struggled with?

Keep the discussion blame-free. Look for problems in the system, not individual mistakes, and steer the team toward fixes instead of dwelling on what went wrong.

When to use this retrospective

  • When you want one session that covers both looking back and planning ahead
  • After a significant project milestone or release
  • When the team needs to tackle ongoing problems without losing sight of what's going well
  • At a quarterly review, to check progress and plan improvements

Suggested icebreaker questions

  • What's one thing you learned last week that surprised you?
  • If you could instantly master one new skill, what would it be and why?

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

Ideas and tips for your retrospective meeting

  • Start with Accomplishments so the team has some energy before it gets to the problems
  • Use dot voting to choose which items to discuss in detail
  • Turn each Future consideration you keep into a specific action with an owner
  • Keep a parking lot for discussions that need to continue after the retrospective
  • Record lessons learned in a shared space so later projects can use them
  • Timebox each quadrant so no single one takes over

Frequently asked questions

What does FLAP stand for in a retrospective?
FLAP stands for Future considerations, Lessons learned, Accomplishments and Problem areas. They're the four quadrants your team fills in during the retrospective.
How do you run a FLAP retrospective?
Give everyone a few minutes to add ideas to each quadrant privately, starting with Accomplishments. Group similar ideas, vote on what to discuss, and finish by turning the top Future considerations into actions with owners.
When should a team use the FLAP retrospective?
Use it after a milestone or release, or at a quarterly review, when you want to look back at the work and set direction in the same session.
How long does a FLAP retrospective take?
Plan for 45–60 minutes. Give each quadrant its own timebox and save the last part of the meeting for agreeing on actions.
How is the FLAP retrospective different from the 4Ls retrospective?
The 4Ls asks what your team Liked, Learned, Lacked and Longed for. FLAP covers similar ground, but its Future considerations quadrant asks for concrete next steps, where Longed for collects wishes.

Related templates

ESVP Retrospective

Check how bought-in the team is before the retro starts

What Went Well Retrospective

The classic two-column retro: what went well and what didn't

Four Ls Retrospective

Reflect on what your team Liked, Learned, Lacked and Longed for

What? So What? Now What? Retrospective

Go from what happened to what you'll do next.

Ready to run this retrospective?Try this retrospective live