Retrospectives and FigJam: like peanut butter and jelly
summary
Three concrete moves: set up a reusable FigJam board way ahead of time so people add notes during the project, use an established framework like 4L (Liked Learned Lacked Longed for) to balance praise and root causes, then make change happen by categorizing patterns, duplicate your FigJam board and pick two or three prioritized actions. Example outcome: secure test accounts and phones, run a QA party/bug bash, assign an owner and timeline, track status in FigJam so retros actually produce results.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:00The importance of starting early
- 4:28Use an establish framework
- 11:08Make it actionable
- 13:21Creating an action plan
- 17:46Elevate authentic feedback
- 19:22In summary
- 20:44Closing
related talks
25mShort stories from the making of FigJam
44mRun fun and engaging workshops with FigJam
32mRetrospectives
24mCollaborative creativity
21mEstablishing early evangelists: from sentiment gathering to strategic roadmapping
31mLive design critique with the Figma design team
56mESSENTIALS - Retrospectives: Shifting Towards Value
30mNoRetrospectives