The last slide of a retrospective deck. Three lessons stack vertically, and inside each block type size alone separates "what we did → what we learned → what we will do next". A faint line carries the action we actually took, the largest text carries the lesson it taught, and a final line marked with an accent bar carries the behaviour to change. It is set with rules and typographic hierarchy rather than card faces or a table, so it reads as a judgement rather than a summary.
🔗 Markdown URL
https://getdeck.co/api/md/closing-lessons-learned--cobalt-grid.md?lang=en&key=YOUR_KEYFetching your key...
⚡ MCP install command
Client
claude mcp add --transport http getdeck https://getdeck.co/api/mcp --header "Authorization: Bearer gd_..."
Fetching your key...
Paste this into your terminal to connect your local AI agent to getdeck.
Best for: Project close-out retrospectives, wrapping a quarterly or annual review, postmortem conclusions, sharing the standards a failure produced
Use: When a project or quarter has ended and the deck should close on what the work taught you and what you will change, rather than on a recap of what you did. Use it for a close-out retrospective, a postmortem conclusion, or the last slide of a quarterly or annual review. It fits when the lessons reduce to two or three and each one can be said in a single sentence.
Avoid: Use closing-bento-recap for a summary that regroups the talk’s key points, closing-action-plan-checklist for action items with owners and due dates, closing-journey-milestone for a journey running from past into a future vision, and closing-decision-frame when you are asking for a decision between options. Use feature-benefit-ledger for a two-column mapping of features to benefits. Past four lessons none of them reads as a sentence, so group them back down to three.
Based on the currently selected theme Cobalt Grid. Switching the theme in the sidebar updates this section too.
Not used in any deck template yet.