Definition
A team retrospective is a planned look at how a team has worked across a period and across all its work, separate from what that work achieved. The tutorial on running a marketing team retrospective frames it as one question in two halves, what helped the work and what got in its way, ending in a small number of changes the team will try. It is not a results review, a complaints session or a performance discussion.
The word retrospective is used for several kinds of looking back. In this sense it means a team, or a process, examining its own way of working. A campaign can hit every target while the team behind it works badly, and the retrospective is where that shows; whether the campaign met its brief is a question for a post-mortem.
From evidence to causes
A retrospective that runs on memory tends to follow whoever speaks loudest. The tutorial starts instead from evidence: the work system's record of what was requested, finished, blocked and reworked during the period, the calendar of meetings the team held, and private notes each person writes in advance about specific moments when the work went well or badly.
Points are grouped into themes, and the biggest themes are those with the most work affected, not those argued about most. Each is then traced back with repeated questions of why, and the chain stops at a process, a rule, a check or a habit. When an answer names a person, the next question is why the way the team works allowed it. That blameless stance is practical rather than polite: a cause located in a person cannot be fixed by changing the process, and blame teaches people to hide problems.
In practice: owned changes checked next time
The output is deliberately small. The team chooses one or two changes it controls, writes each as a testable expectation, gives it an owner, the evidence that will be read and a date, normally the next retrospective, and puts it in the work system like any other task. The following retrospective opens by reading those changes back and deciding to keep, adjust or drop each one. That check is what makes the session an improvement loop rather than a place to vent.
Retrospectives fit into existing rhythms rather than adding a new one. The quarterly marketing planning playbook separates its own look back at the quarter's results from a review of how the team itself worked, which belongs in a team retrospective. The product launch playbook ends with a short retrospective on the launch process, asking which gates were useful and where the timeline slipped, and feeds the lessons into the playbook for next time.
A travel agency traces late brochure copy to a single approver
Frindisk Travel Agency's quarterly retrospective started from the work board: of 14 brochure and landing page jobs in the quarter, 9 went to print or live late, by an average of 6 working days. Private notes from the 7-person team pointed the same way, and grouping them produced one dominant theme. Asking why traced it past the copywriters, past the designers and into the approval step: every piece of copy waited for sign-off from the head of product, who travelled for 3 weeks of the quarter. The change chosen was a named deputy approver for routine brochure copy, with the head of product keeping price and destination claims. At the next retrospective, 2 of 12 jobs had slipped, and the team kept the change.
Related terms
A retrospective often reaches for the team's records. The Decision LogA running record, one row per decision, of what changed and why, what was expected, who decided and when the result will be checked. shows what was decided during the period and why, which helps separate a poor decision from a sound one that met bad luck. The Change LogA dated record of changes made to tracking, accounts, reports, lists or rules, with who made each and why, so later movements in the figures can be traced. dates changes to tracking, accounts and rules, and explains shifts the team might otherwise misread. When a theme traces back to approvals, the Approval MatrixA table that says which reviews each type of marketing work needs, such as legal, brand or budget, and who gives each, matched to the risk of the work. is usually where the change lands, by altering who reviews which kind of work or adding a deputy.
Common confusions
- A retrospective is a campaign post-mortem. A post-mortem closes one campaign against its brief. A retrospective looks at how the team worked across the period, whatever the results, and the two are best kept apart.
- It is a chance to air grievances. Points come with an example from the period, and causes stop at processes, rules and habits. Concerns about one person's work go to that person's one-to-one, not the room.
- More changes mean more improvement. A long list competes with the work, so none of it happens. One or two changes with an owner and a date are the point.
- The session is finished when the meeting ends. Its value shows only at the next retrospective, when each change is checked and kept, adjusted or dropped.
