Stage 10 of 10 · Operate and improve
Improve
What did we learn, and where does each change go?
- Purpose
- Review, triage and route changes.
- Defining artefact
- Improvement log, change requests
- Exit gate
- Changes accepted into the next release
- Failure it prevents
- The same flaw reaching cohort after cohort
Improve reviews what the cohort taught, triages it, and routes each change back into the lifecycle. Without this stage the same flaw reaches cohort after cohort.
What happens
- Run post-use validation: review assessment practice and results after delivery.
- Triage findings from delivery signals, complaints, appeals and validation into an improvement log.
- Turn accepted findings into change requests that re-enter the lifecycle. Where each one re-enters is an open question (below).
- Review curriculum debt: what has been patched, what has aged, what was kept because it was compliant rather than good.
- When the standard itself is revised, follow every affected artefact through the traceability links and route the work back through the gates.
At the gate, ask
- Which changes go into the next release, and which wait?
- Can each change be traced to the evidence that prompted it?
- Is curriculum debt shrinking, steady or growing?
Where a change should re-enter is still an open question: always at Architect, or at the earliest stage it affects?