Start with the behaviour that matters
A modernisation plan needs to make business rules, dependencies and open questions explicit. My approach starts with defining the intended behaviour and agreeing acceptance criteria before expanding implementation.
A workflow for controlled progress
I use a specification-led approach to connect requirements, implementation tasks and verification. The scope and checks should fit the system and the team.
- UnderstandIdentify behaviour, constraints and open questions.
- SpecifyAgree requirements and acceptance criteria.
- PlanDefine bounded tasks and dependencies.
- ImplementWork in increments that can be reviewed.
- VerifyCheck results against the agreed criteria.
Give agents a clear working environment
I help teams define the context, reusable instructions, tool access and task boundaries for AI-assisted work. The workflow should make it clear when an agent can proceed and when a person needs to resolve a question or approve a decision.
Define verification before scaling up
For a modernisation engagement, I would agree checks such as:
- Acceptance tests for the required business behaviour.
- Comparison with existing behaviour where it provides a reliable reference.
- Integration checks and human review of unresolved differences.
The aim is to give the team evidence for deciding whether an increment is ready and what needs attention next.
This page describes a consulting approach, rather than a specific client engagement or its results.