Architecture & software engineering
Architecture review & decision-record programme
An independent review returning the risks in priority order, plus the decision-record practice that stops the same argument recurring.
2–4 weeksTypical duration
The problem this solves
Your architecture is the sum of decisions nobody wrote down, and the same debates return every quarter.
What you receive
Artefacts you can hold, and that you can accept or refuse — never a list of activities.
- A written architecture assessment, grounded in a read of the code rather than of the diagrams
- The risk register, ranked, each with its failure mode and its cost to address
- A decision-record practice installed, with the first records written with your team
- A target architecture, with the migration sequenced
Also in architecture & software engineering
Domain-driven service design
Bounded contexts, service boundaries and contracts derived from the business rather than from the current database.
Legacy modernisation
Incremental strangler migration with the old and the new running side by side and proven equivalent before the switch.
Platform engineering for product teams
The internal developer platform, the golden paths and the templates that make the right thing the easy thing.