The tests have passed. Approval is recorded. Access works. The guide has been handed over.
On Monday morning, the team still returns to the old spreadsheet.
Every project update may be accurate. The system can be technically complete without having a stable place in the work.
There is no contradiction. Different conditions have been compressed into one word: done.
Five statements describe five states
Tested means the system works under the agreed test conditions.
Approved means an accountable owner has accepted the intended use.
Handed over means access, knowledge, documentation, and responsibility have reached the people who need them.
Used means real cases move through the new process repeatedly.
Effective means the intended result has started to change.
None of these states proves the next one. A successful test does not prove adoption. Approval does not prove a usable handover. Handover does not prove impact.
Green status is easiest inside the project
Testing can be scheduled. Approval can be documented. Handover can be placed on a plan.
Use happens elsewhere. It happens under time pressure, with exceptions, competing priorities, and habits that predate the new system.
Impact sits one step further away. It is not demonstrated by the availability of a feature. It appears when the work becomes more reliable, faster, clearer, or otherwise closer to the intended outcome.
When every state is represented by one green field, the transition into operations disappears from view.
Each state needs its own evidence
A useful status does more than name a conclusion. It points to the evidence that supports it.
Testing needs a reproducible result.
Approval needs a recorded decision and a named owner.
Handover needs a practical check. Can the intended users gain access, complete the task, and recognize an exception?
Use needs observation across real cases.
Effectiveness needs evidence of change in the intended outcome. The strength of that evidence should match the decision being made. A correlation alone does not establish cause.
This turns status reporting into an operational control.
Introduction begins after handover
Handover may close the technical delivery. It opens the operational phase.
Questions now emerge from real work. Exceptions reveal missing rules. Responsibilities are tested. The process needs correction until it holds under ordinary conditions.
This is not administrative work left over after the project. It is where a solution becomes a working practice.
Separating the states makes that work visible. It shows what is complete, what must still be observed, and where ownership has not yet taken hold.
Complete describes the system. In use describes the work. Effective describes the result.
Patrick Thole, Disruption Dynamics, Zürich
disruption-dynamics.ch