When it comes to retrospectives, KPT (Keep / Problem / Try) is the standard, but I wanted to come up with a framework full of my own originality, so I'm writing down this idea.
bmf Framework
bmf = Build / Miss / Focus is a retrospective framework composed of these initials. While maintaining a three-frame structure similar to KPT, it is designed to guide thinking in the order of "visualizing achievements," "highlighting failures," and "clarifying the next focus area."
| Item | Description | Intent |
|---|---|---|
| B: Build (Achievements) | A section to list what was achieved, progressed, or improved during the period. | To verbalize achievements, extract self-efficacy, and reproducible practices. |
| M: Miss (Failures) | A section to list events that did not go as planned, obstacles, oversights, and unmet goals. | To share problem recognition and ensure opportunities for prevention and improvement. |
| F: Focus (Next Focus) | A section to narrow down themes and actions to focus on in the next cycle. | To increase execution probability through selection and focus without overusing Try. |
Why bmf Instead of KPT
The biggest advantage of KPT is its simplicity and widespread use. However, when put into practice, the following issues often arise:
- Excessive Try — A large number of "things that should be done" emerge, burying priorities.
- Temperature Difference Between Keep and Problem — Keep becomes superficial, leading to a bias towards listing Problems.
- Burden of Continuous Tracking — Reflection on Try is not sufficiently conducted.
bmf is an improvement proposal based on the following design principles to address this situation.
- Principle A: Prioritize verbalizing achievements. Cultivate a culture of extracting and reusing success factors.
- Principle B: List issues uncensored, but don't end with enumeration. Create a safe space to expose issues with the premise of selecting focus areas later.
- Principle C: Replace Try with "Focus" and emphasize quality over quantity. Carefully select items to be addressed in the next cycle.
These three principles aim to shorten the distance from "retrospective to execution" with bmf.
Implementation Procedure
Conduct it in the same procedure as KPT.
- Review the results of the previous retrospective.
- Conduct the current retrospective.
- Review the results of the current retrospective.
Feel free to arrange the method, such as setting time for writing or grouping the items written down.
Tips for bmf
Build (Achievements)
- Writing "actions to be replicated" and "knowledge that can be systematized" is more valuable than the number of completed tasks or speed.
- Record not only individual achievements but also results born from team collaboration.
Miss (Failures)
- Separating events (What) and impacts (So What) makes analysis easier.
- Emotional logs (frustration, being stuck) can also be hints, so keep them short and don't discard them.
Focus (Next Focus)
- Including a "not to do this term" rejection list increases transparency in decision-making.
- Write actions and outcomes as a set (e.g., "Review SLA 24h" → "30% reduction in PR stagnation median").
Pitfalls and Countermeasures When Introducing
| Pitfall | Symptoms | Countermeasures |
|---|---|---|
| Too Few Builds | Starts in a negative mode, lowering morale | Implement a facilitation measure to read out achievement logs just before. |
| Miss Turns into a Blame Game | Focusing on people instead of phenomena, compromising psychological safety | Rule: Describe events and processes, not individual names. |
| Too Many Focuses | Becomes superficial and not executed | Set limits or determine priorities. |
| Forgetting Follow-up | Missing review of previous Focus results | Make a status review of the previous session mandatory in the first 5 minutes each time. |
Template
Below is an example template for conducting it in text form.
# bmf Retrospective / YYYY-MM-DD to YYYY-MM-DD
Participants:
Facilitator:
## Build (Achievements)
-
-
## Miss (Failures)
-
-
## Focus (Next Focus)
- [ ] Theme:
- Purpose:
- Outcome Indicator:
- Owner:
- Deadline:
---
### Follow-up on Previous Focus (when applicable)
- Theme A: Achievement / Impressions
- Theme B: Achievement / Impressions
Conclusion
It's best to choose the optimal framework according to the purpose, but continuing to use one framework can lead to being bound by its constraints or losing sight of changes due to familiarity.
Why not try bmf to gain new stimulation?
