MENTAL MODEL · M6625

Future, Lessons, Accomplishments, Problem Areas

TechnicalmediumSoftware Engineering

Included

Updated 2026-08-22

Loading revision record…

INTRODUCTION

English translation pending.

CORE DEFINITION

FLAP is a team retrospective framework with four dimensions. Future captures new approaches the team wants to try next period. Lessons records what was learned from the period just ended. Accomplishments names the results and progress achieved. Problem areas identifies unresolved challenges. Its design counters two common retrospective failures: sessions that become complaint lists with no acknowledgment of progress, and sessions that report only successes and bury problems. Requiring all four dimensions keeps the review balanced and ensures the discussion ends with a forward commitment rather than only a backward assessment. The framework assumes enough psychological safety to name problems honestly.

SCAFFOLDING EFFECT

psychology

Reduce cognitive load

- Use four-column capture: collect inputs into Future, Lessons, Accomplishments, and Problem areas separately. - Use balance check: verify that both achievements and problems appear before discussing any of them. - Use forward conversion: turn at least one Future item into an owned action with a date.

anchor

Anchor fast decisions

Retrospectives fail in two directions: teams that only air problems lose morale and stop attending, and teams that only celebrate miss the defects that accumulate. Structuring the discussion into four separate dimensions prevents either default from taking over, because each category must be filled. Naming accomplishments also preserves the confidence needed to raise problems honestly, which improves the quality of the problem list. The Future dimension then converts the session's output into commitments, so the retrospective changes behavior instead of ending as a discussion.

MINIMUM ACTION

In progress 0/1

Practice this model in one real situation:

Collect input under each of the four dimensions before discussing any of them. 2. Review accomplishments first to establish what worked. 3. Review lessons and problem areas without assigning blame. 4. Convert the strongest Future idea into an action with an owner and a date. 5. Revisit the actions at the start of the next retrospective.

Check to track your progress (stored locally)

Learning progress0%

account_treeGenealogyexpand_more

menu_bookReferencesexpand_more

Source support: Explicit

link
en.wikipedia.orghttps://en.wikipedia.org/wiki/Retrospective#Agile_software_developmentZH · Explicit
verified

RELATED MODELS