FLAP retrospective: Future, Lessons, Accomplishments, Problems

Look back at what you achieved and what hurt, pull out the lessons, and turn them into the decisions your next phase needs. FLAP is a retrospective and a planning warm-up in one session.

Future considerations

Decisions or bets we need to make next

Lessons learned

Takeaways worth carrying forward

Accomplishments

Outcomes we’re proud of

Problem areas

Pain points to resolve soon

Use this template — it's free

What a FLAP retrospective is

FLAP stands for Future considerations, Lessons learned, Accomplishments, Problem areas. Two columns look back at the period you are reviewing: what the team achieved and where it is still in pain. One distills that experience into takeaways. And one looks forward: the decisions and bets the team has to make next.

Most retrospectives end with action items that repair the last sprint. FLAP ends with decisions about the next phase. It blends a retrospective with a futurespective, so the evidence from the past is still fresh when the team talks about what to do next.

Why that combination works:

• Lessons get their own column. In most formats a lesson hides inside a problem card. FLAP asks people to state the takeaway itself: "fixed-scope quarterly roadmaps don't survive the first customer escalation" instead of "the Q3 roadmap was a mess".
• The future column is for decisions, not tasks. "Native mobile app or keep the web wrapper?" "Do we keep supporting the old API?" Questions like these are usually settled by default, because nobody puts them on an agenda. FLAP puts them on the board while the team still remembers why they matter.
• Accomplishments restore perspective. After a long phase, people remember the last two weeks of pain. Listing outcomes reminds everyone what the period actually produced, and gives you a clear story to tell stakeholders.
• It is easy to read from outside. A manager or a partner team can follow a FLAP board without any context, which makes the results easy to bring into planning.

When to use it, and when not to

FLAP is built for boundaries — the moments between one phase of work and the next:

• at the end of a quarter, a release cycle or a project phase, right before planning;
• at a handover, when a product moves to another team or people rotate off a project;
• after a pilot or a first version, when the team has to decide whether and how to continue;
• at a milestone in a long project, to check the plan against what you have learned so far;
• before a strategy or roadmap meeting, so the planning starts from evidence rather than opinion.

Pick something else when:

• It is a regular sprint retro. Two weeks rarely produce real bets about the future, and the Future column fills with backlog items. For routine sprints, the KPT retrospective is faster and more focused.
• The next phase is already decided elsewhere. If the team has no say over what comes next, the Future column becomes a list of frustrations. Focus on learning with the 4Ls retrospective instead.
• You need to agree on a goal first. FLAP assumes the team knows where it is heading. If it does not, start with the Sailboat and its island.

The four columns

The ProstoRetro board shows the columns in FLAP order: Future considerations, Lessons learned, Accomplishments and Problem areas. Here is what belongs in each, with cards from a product team at the end of a quarter.

Future considerations: decisions and bets ahead

Decisions or bets the team needs to make next. The test: it is a question with more than one possible answer, and someone has to choose. A plain task ("update the onboarding docs") is not a future consideration — it is an action item. Phrase cards as a question or as an explicit bet.

• Do we keep supporting API v1 after the spring release?
• Bet: one more quarter on self-serve onboarding before we add a sales-assisted flow
• Should the mobile app move to a two-week release train?
• Hire a second QA engineer, or put that time into test automation?

Lessons learned: takeaways to carry forward

Insights worth keeping. The test: would it change how you do things next time? If yes, it is a lesson. If it only describes what happened, it is an accomplishment or a problem. Good lessons read like rules of thumb the team could hand to a new colleague.

• A clickable prototype shown to five customers settled more arguments than any spec
• When two teams share a service, one of them has to own it on paper
• Feature flags let us ship on the agreed date even when one part slipped
• Migration estimates were only right when the people doing the work made them

Accomplishments: outcomes to be proud of

Results, not activity. "Held twelve user interviews" is activity; "found out why new users drop off after day two" is an outcome. Ask people to include the effect where they can — numbers, a customer reaction, a problem that is gone.

• Search results load in under a second, down from three
• Moved every customer to the new login without a single lockout
• Onboarding completion up from 48% to 61%
• The support backlog is under fifty tickets for the first time this year

Problem areas: pain to resolve soon

Pain points that are still open and still costing you. The test against a lesson: if the problem is solved and you know why, the insight belongs in Lessons learned. Encourage people to name an area rather than a single incident — that is what makes problems useful for planning.

• Releases: every one still depends on a manual check by one person
• Requirements from sales arrive as screenshots in chat threads
• Three teams share one test environment, and it is broken most mornings
• On-call: the same three alerts wake someone up every week

Use this template — it's free

A 60-minute FLAP agenda

For a team of five to nine people reviewing a quarter or a project phase.

1. Warm-up, 4 minutes. One question to get people talking — pick one from our icebreaker questions.
2. Set the frame, 3 minutes. Name the period under review and the decision point ahead: "the last quarter; planning is next Tuesday". It tells people how far back to look and how far forward to think.
3. Silent writing, 10 minutes. Cards in all four columns. Cards stay hidden from others until writing ends, so each person's view of the period is their own.
4. Grouping, 7 minutes. Merge duplicates and place each lesson next to the problem or accomplishment it came from. ProstoRetro can suggest groups and names for them; keep what fits and undo the rest.
5. Voting, 5 minutes. Ask people to vote for what the next phase most needs to settle. Steer the votes toward problems and future considerations: accomplishments rarely need a decision.
6. Discussion, 22 minutes. Accomplishments first, briefly (3 minutes). Then the top problems and the lessons attached to them (10 minutes). Then the top future considerations (9 minutes), using what was just said as evidence.
7. Decisions and owners, 6 minutes. Each future consideration is either decided now or given an owner and a date by which it will be decided. Write both as action items.
8. Close, 3 minutes. Read back the decisions and open questions, and agree what goes to the planning meeting.

A FLAP session has more moving parts than a sprint retro, so a timer helps. Give the board a meeting length when you create it, and ProstoRetro allocates the time across phases and topics and runs each timer for you.

Remote facilitation tips

• Collect cards over the whole period. Nobody remembers week three of a quarter during a one-hour call. Open a permanent board — an infinite room — at the start of the quarter and let people add accomplishments and lessons as they happen. Cards stay hidden until the meeting starts.
• Put the evidence on the cards. Cards can carry images, so paste the chart behind an accomplishment or the screenshot of a recurring alert. It saves a minute of explanation per card.
• Poll before you debate a bet. For the biggest future consideration, run an anonymous single-choice poll first. If the team already agrees, you save ten minutes; if it is split, you know where the discussion has to go.
• Invite the decision makers for the last part. When the room is open to anyone with the link, a product lead or a stakeholder can join for the future considerations with just a name, no account needed.
• Bring the summary to planning. After the retro, ProstoRetro produces a summary page, can write an AI summary of the session and emails the summary to participants who signed in. That record is the input your planning meeting needs.

Variations

The handover FLAP

When a product or a component changes hands, run FLAP with both teams. The outgoing team fills accomplishments, lessons and problem areas; the future considerations are written together, and they become the receiving team's first decisions. It is a quicker way to transfer context than a long handover document nobody reads.

FLAP before quarterly planning

Schedule FLAP a few days before planning, not on the same day. The team has time to research the open future considerations, and the planning meeting starts with decisions half-made.

Personal FLAP

The four questions work for one person too: a self-review before a performance conversation, or the end of a year. Accomplishments and lessons give you the story; future considerations give you the questions to bring to your manager.

FLAP with Shout-outs

FLAP has no column for thanks, and a long phase usually deserves some. Add a fifth column for shout-outs as a custom template in ProstoRetro — custom templates take up to five columns with your own descriptions and colors. If thanks matter more than decisions this time, run the WRAP retrospective instead: appreciations have a full column there.

Common mistakes

• Accomplishments as a status report. A list of closed tickets is not an outcome. Ask "what is different now because of this?"
• Platitudes as lessons. "Communication is important" teaches nothing. Ask what exactly the team would do differently, and write that down.
• A Future column full of backlog items. Tasks belong in action items. Keep this column for choices that shape the next phase.
• Problems with no lesson attached. If a problem area keeps coming back and no lesson ever comes out of it, the team is describing pain instead of understanding it.
• Decisions with no owner or date. An open bet without a name next to it gets decided by default, usually the least deliberate way possible.
• Using FLAP every sprint. It is a format for boundaries. Run it every sprint and it turns into a heavier version of a normal retro.

FAQ

What does FLAP stand for?

Future considerations, Lessons learned, Accomplishments and Problem areas: the decisions ahead, the takeaways worth keeping, the outcomes you are proud of and the pain still to resolve.

When should you run a FLAP retrospective?

At the end of a quarter, a project phase or a release cycle, ideally a few days before planning. It also suits handovers and the end of a pilot.

What is the difference between FLAP and 4Ls?

Both give lessons their own column. 4Ls looks back at what the team liked, learned, lacked and longed for; FLAP adds a forward-looking column for the decisions and bets the next phase needs.

How long does a FLAP retrospective take?

Plan an hour for a team of five to nine, as in the agenda above. For a large project or a handover between two teams, allow 90 minutes.

Can I run a FLAP retrospective online for free?

Yes. The FLAP template is built into ProstoRetro, which costs nothing, and the summary page it leaves behind is a ready input for planning. See how to run a great retro for a tour of the app, or explore the other retrospective templates.