01
Decisions recorded
The chosen route, rejected options, constraint and owner remain visible.
HOW I WORK / EVIDENCE TO OWNERSHIP
A clear route from the current problem to a system your team can run.
Good architecture has to survive implementation, migration, failure and handover. Evidence, decisions, delivery and ownership stay connected throughout the engagement.
01 / DELIVERY PATH
Five stages, adapted to the work.
A small assessment may stop after the roadmap. A full build can run through every stage. The stage changes; the standard does not.
| Stage | Question | Output | Ready to continue when |
|---|---|---|---|
| Assess | What is true now, what is failing and what must change? | Current-state record, risks, scope and success measures. | Scope, priorities and decision owner agreed. |
| Architect | Which target state is defensible? | Target architecture, policy model and recorded decisions. | Target and constraints approved. |
| Implement | How does the design reach production safely? | Configuration, integrations, pilots, migration and communications. | Approved production state reached. |
| Stabilise | Is the result dependable under normal operation? | Closed defects, owned exceptions and useful operational checks. | Known issues and residual risks recorded. |
| Hand over | Can the internal team operate and change it? | Runbooks, knowledge transfer, ownership and closure evidence. | Named owners can run the system without project memory. |
02 / CONTROLLED CHANGE
Test the route before increasing the blast radius.
02
Representative pilots
Normal users, privileged paths, exceptions and recovery are exercised before broad rollout.
03
Evidence gates
Entry criteria and expected evidence determine whether the next wave proceeds.
04
Executable rollback
Trigger, authority, mechanics and recovery verification are written before the window.
03 / WHAT THE WORK NEEDS
Useful access and timely decisions.
The work moves quickly when the current configuration, system owners and decision-makers are available.
- 01
A named decision owner
- 02
Access to system owners, configuration and evidence
- 03
Representative pilot users, devices and applications
- 04
Approved change windows and communications
- 05
The future internal operators present before handover
04 / WHAT REMAINS
The internal team owns the result.
The exact handover depends on the engagement, but configuration, decisions and unresolved risks should never disappear with project memory.
- 01Current-state and target-state architecture
- 02Decision record
- 03Tested configuration
- 04Migration and acceptance evidence
- 05Exception and open-risk register
- 06Operator runbooks
- 07Ownership matrix
- 08Knowledge-transfer record
If the system works only while I am present, the delivery is not complete.
START WITH WHAT IS TRUE NOW