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 streamline 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 is a comprehensive team reflection framework that examines four key areas: Future considerations, Lessons learned, Accomplishments, and Problem areas. This balanced approach helps teams celebrate successes while addressing challenges and planning ahead. By structuring discussion around these four dimensions, teams can effectively analyze their performance, extract valuable insights from their experiences, and create actionable plans for improvement. The framework encourages both forward-thinking and reflection on past events, making it particularly valuable for teams looking to maintain continuous improvement. The FLAP format creates a safe space for open dialogue about both achievements and challenges, while maintaining a strong focus on future growth and development. This makes it especially useful for teams who want to maintain momentum while addressing obstacles in their path.

FLAP Retrospective Format

Future considerations

What direction do we want to take?

Guide the team in exploring upcoming opportunities and challenges. Encourage specific, actionable ideas rather than vague aspirations. Help the team prioritize initiatives and create concrete next steps.

Lessons learned

What have our experiences taught us?

Focus on extracting meaningful insights from both successes and failures. Encourage participants to think about cause-and-effect relationships and identify patterns in their experiences. Help the team translate lessons into actionable improvements.

Accomplishments

What are we proud of?

Create an environment where team members feel comfortable sharing their successes. Encourage recognition of both individual and team achievements. Help connect accomplishments to their positive impact on the team, project, or organization.

Problem areas

What have we struggled with?

Maintain a blame-free environment while discussing challenges. Focus on identifying systemic issues rather than individual mistakes. Guide the team toward finding constructive solutions rather than dwelling on problems.

When to use this retrospective

  • When you want to balance reflection on past performance with future planning
  • After completing a significant project milestone or release
  • When the team needs to address ongoing challenges while maintaining motivation
  • During quarterly reviews to assess 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?

Ideas and tips for your retrospective meeting

  • Start with Accomplishments to build positive energy before addressing challenges
  • Use dot voting to prioritize which items to discuss in detail
  • Ensure Future considerations are translated into specific, actionable items
  • Keep a parking lot for discussions that need to be continued outside the retrospective
  • Document lessons learned in a shared knowledge base for future reference
  • Set time boxes for each quadrant to maintain balanced discussion

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