My approach
Structured analysis.Solutions that get built.
A method in five steps, from the need through to production: understand, design, document, support, and speed things up with AI without handing it the decision.
01Understand & scope
Understand beforeyou specify.
A request is not a solution yet. I start from what exists, the As-Is, I challenge the need, I measure the gaps against the target, and I fix a scope before moving on to design.
Business request
- Problem
- Context
- Objective
- Constraints
& challenge
Clarified need
- Real objectives
- Defined scope
- Gaps identified
- Known constraints
- Ready to design
“A need properly understood saves months of rework later.”
Business & IT view
Understanding what exists today, the objectives and the constraints.
Challenging the need
Asking the right questions, and rephrasing when needed.
Scoping & prioritising
Identifying the impacts, the dependencies and the value.
02Design & document
Documentation designedto be used.
I build structured documentation where every element has a role, an identifier and links to the rest. The need first, the solution after: functional requirements, business rules, processes, screens, data. A base that is clear, consistent, usable by every stakeholder and ready for sign-off.
Structured approach
Built on established practice (IREB and the like).
Everything has an ID
Every requirement, rule and screen carries a unique identifier.
One coherent whole
Every element is linked to the others, and kept in step.
Easy to maintain
One change propagates everywhere in the documentation.
03Traceability & delivery
Nothing is lostfrom need to go-live.
Documentation that stays connected, from the business need through to production, so the picture stays clear and the impact of every change can be measured.
Less risk
Impacts spotted early
More efficiency
Fewer rounds of back and forth
One single view
Readable by everyone
Traceability, an example
BR-012
Business need
FR-034
Functional requirement
RLE-008
Business rule
UI-011
Screen
TC-027
Test case
Linked automatically
Impacts visible as soon as something changes
If the business rule changes, AI identifies the requirements, screens and tests it affects.
Time savedDocumentation ready for delivery. Readable by the businessusable by ITverifiable by testinguseful to Change & Run. IT and non-IT impacts identified from the design stage.
04Supporting the analysts
Building a shared standardfor the documentation.
I help teams adopt the standards, templates and practices that produce documentation which is clear, consistent and built to last.
Teams that need less help, analysis that comes faster, projects that keep moving.
Clear standards
Templates, conventions and a sign-off process
Coaching on the ground
Growing skills, with concrete feedback
AI built in
Drafting, checking, reviews and summaries
Results that last
Documentation that stays usable and maintainable
05Accelerate with AI
AI speeds the method up.It does not replace it.
Rigorous documentation is what makes AI useful at every step: challenging the needs, proposing requirements, detecting impacts, generating tests and keeping the documentation consistent. The analyst stays at the centre of the decisions.
AI across the whole cycle
Understand
Questions & grey areas
Challenges the need, spots what goes unsaid
Design
Requirements & consistency
Structures requirements, checks their logic
Trace
Impacts & blind spots
Finds everything a change touches
Test
Tests & coverage
Drafts the tests, spots the gaps
Maintain
Linked updates
Carries every change through
“AI speeds the analysis up. The structure keeps it safe. The analyst decides.”
Less time copying things over, more time analysing
06Let's talk
Start with your context.
A project, a question, a complex transformation? Let’s talk it through.