I have usually thought of an assessment as a one-time intervention. We define a reference model, collect evidence, judge the current state and identify improvements. The result is a snapshot. That is useful for diagnosis.
But it is not enough when the purpose is improvement. Once change begins, the subject of the assessment starts to move. Practices change. Responsibilities shift. New evidence appears. Some improvements work, others do not. New weaknesses become visible. The original assessment gradually becomes a description of a state that no longer exists.
An assessment may be a snapshot. Assessment should be a recurring capability.
The first assessment establishes a baseline
A thorough initial assessment remains valuable. It clarifies:
- what is being assessed;
- what good looks like;
- the current state;
- important strengths, weaknesses and risks;
- priorities for improvement.
Without that baseline, improvement can become a collection of disconnected actions. But the baseline is only the beginning.
Improvement creates new evidence
Every improvement action is also a hypothesis. We expect that changing a process, role, tool, structure or behaviour will lead to a better result.
That expectation should be tested. Did the change actually happen? Did behaviour improve, or only documentation? Did the intended result appear? Did the improvement create new problems elsewhere?
Without reassessment, these questions are often answered through impressions or completion reports.
But completing an improvement is not the same as achieving improvement. Reassessment brings the organisation back to evidence.
Reassessment does not mean repeating everything
Continuous assessment does not require a full formal assessment every sprint or every month. That would quickly become bureaucratic. Reassessment can happen at different depths. A lightweight review may examine recent evidence and a few critical indicators. A periodic deeper assessment may revisit the complete reference model. A major change, failure or shift in context may trigger an earlier reassessment.
The principle is simple:
Reassess often enough to learn whether improvement is actually happening.
The reference model may also change
Reassessment is not merely updating a score against a fixed model. As understanding improves, the definition of good may also evolve. Some expectations may prove irrelevant. New capabilities may become important. The organisation may discover that its original target state was incomplete or misguided.
Reassessment should therefore ask two questions:
Are we moving closer to what we defined as good?
And:
Is our definition of good still the right one?
From report to improvement loop
A static assessment often ends with findings and recommendations.
A continuous assessment process closes the loop:
reference model
→ evidence
→ judgement
→ decision
→ improvement
→ new evidence
→ reassessment
The assessment should therefore identify not only what needs to improve, but also:
- what evidence will show progress;
- when reassessment will occur;
- what should trigger an earlier review;
- which assumptions remain uncertain.
Assessment then becomes part of the improvement system rather than an event before improvement begins.
The real purpose of reassessment
The purpose is not to prove that the plan was followed. It is to discover whether the plan was right. Reassessment helps the organisation detect ineffective improvements early, adapt priorities, expose unintended consequences and remain focused on outcomes rather than activity.
An assessment tells us where we are. Reassessment tells us whether we are actually moving—and whether we are still moving in the right direction.