My approach
Structured analysis.Solutions that get built.
A five-step method, from the initial need to production: understand, design, document, support and accelerate with AI without letting it make the decisions.
01Understand & scope
Understand beforeyou specify.
A request is not yet a solution. I start from what exists today (the As-Is), challenge the need, measure the gap against the target and agree the scope before design begins.
Business request
- Problem
- Context
- Objective
- Constraints
& challenge
Clarified need
- True objectives
- Defined scope
- Identified gaps
- Known constraints
- Ready for 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 impacts, dependencies and value.
02Design & document
Documentation designedto be used.
I build structured documentation where every element has a role, an identifier and links to the rest. Needs first, then the solution: functional requirements, business rules, processes, screens, data. A foundation that is clear, consistent, usable by every stakeholder and ready for sign-off.
Structured approach
Built on established practice (IREB and similar).
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 sync.
Easy to maintain
One change propagates right through the documentation.
03Traceability & delivery
Nothing is lostfrom need to go-live.
Connected documentation, from business need to production, so the picture stays clear and the impact of every change can be measured.
Less risk
Impacts spotted early
More efficiency
Less back-and-forth
A single view
Readable by everyone
Traceability in practice
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 every requirement, screen and test affected.
Time savedDocumentation ready for delivery. Readable by the businessusable by ITverifiable by test teamsuseful to Change & Run. IT and non-IT impacts identified as early as design.
04Supporting analysts
Building a shared standardfor documentation.
I help teams adopt standards, templates and practices, so the documentation they produce is clear, consistent and holds up over time.
More autonomous teams, faster analysis, projects that keep moving.
Clear standards
Templates, conventions and a sign-off process
Coaching on the ground
Skills development and practical feedback
AI built in
Drafting, checking, reviewing and summarising
Results that last
Documentation that stays usable and maintainable
05Accelerate with AI
AI speeds up the method.It does not replace it.
Rigorous documentation is what makes AI useful at every step: challenging the need, proposing requirements, spotting impacts, generating tests and keeping the documentation consistent. The analyst remains in charge of every decision.
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 up the analysis. Structure makes it safe. The analyst decides.”
Less time re-keying, more time analysing
06Let's talk
Start with your context.
A project, a question, a complex transformation? Let's discuss it.