The Retrospective
5 min read · 4 principles · apply it by lunch
Morning. Most teams learn by accident. The good ones put it in the calendar.
When something went wrong for your team last month — the slipped deadline, the messy launch, the handover that dropped — did anything about how you work actually change, or did everyone privately note it and move on; and if you can already name the problem that will recur, why haven’t you scheduled the hour that fixes it?
The retrospective comes out of agile software practice, where teams shipping every fortnight discovered they could not afford to learn only from post-mortems — by the time a failure was big enough to examine, ten smaller lessons had already evaporated. So they made learning a scheduled event: at the end of every cycle the team sits down and answers three questions — what went well, what did not, what do we change — and every change leaves the room with one owner and a date. The mechanism matters more than the format. Most teams reflect only when something breaks, which means their rate of improvement is set by their rate of disaster. And the trap inside the ritual itself is the therapy session: an hour of honest venting that produces warm feelings, zero decisions, and the identical conversation next month.
The Retrospective is Day 44 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee