Improvement Follow Up

Improvement Follow Up is the recurring practice of checking, at each subsequent retrospective or at defined intervals in between, whether previously formed action items were actually completed, whether experiments produced the results their hypotheses predicted, and whether the underlying friction they targeted was genuinely reduced. It is the verification stage that closes the loop opened by Improvement Action Formation and Improvement Action Ownership, and without it a team has no reliable way of knowing whether its retrospectives are producing lasting change or merely generating well-intentioned lists that quietly go unexecuted.

Why Follow Up Is Not Optional

Commitments Without Verification Tend to Erode Silently

An action item that is never revisited after the session in which it was formed effectively becomes optional in practice, regardless of how firmly it was agreed to at the time, since there is no point at which the team confirms whether it actually happened. Follow up closes this gap by making completion, or the lack of it, visible and discussed.

Follow Up Is What Distinguishes Genuine Improvement From Repeated Good Intentions

A team can hold consistently engaging, well-facilitated retrospectives that reliably identify real problems and propose sensible actions, and still fail to improve over time if none of those actions are checked for follow-through; the discipline of the reflection itself does not guarantee the discipline of the resulting execution.

What Follow Up Examines

Whether the Action Was Actually Completed

The most basic question follow up answers is simply whether the committed action was carried out within its agreed timeframe, distinguishing clearly between completed, in progress, and not started, rather than allowing ambiguous status to persist unexamined.

Whether an Experiment's Hypothesis Was Supported

For actions structured as experiments under Improvement Experiment Design, follow up specifically reviews the evidence gathered during the trial period against the original hypothesis, reaching an explicit decision to adopt, adjust, or discontinue the tested change.

Whether the Original Friction Was Actually Reduced

Beyond confirming that an action was completed, follow up asks the more important question of whether the friction or problem that motivated the action has genuinely diminished, since it is possible for an action to be executed exactly as planned without producing the intended real-world effect.

Structuring the Follow-Up Process

Reviewing Prior Actions at the Start of Each Retrospective

As introduced in Retrospective Preparation, checking on the status of previous commitments is typically the first substantive activity of a new retrospective, ensuring that the session begins grounded in the team's actual recent history rather than starting fresh as though the prior session's conclusions did not exist.

Distinguishing Between Types of Non-Completion

When an action was not completed, follow up distinguishes between different underlying reasons, such as the owner being blocked by something outside their control, the action turning out to be less important than initially believed, or simple lack of follow-through, since each of these calls for a different response from the team.

Carrying Unresolved Actions Forward Deliberately

An incomplete action is not automatically abandoned; the team makes an explicit decision to either recommit to it with adjusted scope or timeframe, or to consciously drop it, rather than letting it fade out of view through repeated silent deferral.

A Follow-Up Review Cycle

The cycle feeds directly back into the same retrospective structure it belongs to, meaning follow up is not a separate, occasional audit but an integrated part of every regular retrospective session.

Measuring the Effectiveness of Follow Up

Action Completion Rate Over Time

Tracking the proportion of action items completed within their agreed timeframe across successive retrospectives, as introduced in Improvement Action Ownership, gives the team a longitudinal signal of whether follow-through is improving, stable, or declining.

Recurrence of Previously Addressed Friction

Follow up also tracks whether friction points believed to have been resolved by a prior action reappear in later retrospectives, which, if frequent, suggests that completed actions are not producing their intended lasting effect even when nominally executed as planned.

Common Pitfalls

Reviewing Status Without Discussing Why

Simply marking an action as completed or not completed, without exploring the reasons behind incomplete items, misses the opportunity to learn something about the team's actual capacity or the action's original feasibility that could improve how future actions are formed.

Letting Follow Up Become a Perfunctory Formality

When status review is rushed through as a quick checklist rather than genuinely discussed, the team loses the chance to catch patterns, such as a particular type of action repeatedly failing to get done, that would otherwise inform how future improvements are designed and assigned.

Losing Track of Actions Across Many Retrospectives

Without a consistent, accessible record connecting each action back to the retrospective that produced it, as maintained through the tracking practices described in Improvement Action Formation, follow up becomes increasingly difficult to sustain as the number of past actions accumulates over the life of a project.