From problem to working solution
Most projects that go wrong don't fail at the build. They fail earlier: an unclear problem, the wrong people in the room, or requirements nobody agreed on. Business analysis fixes that. Here is how I do it, the tools I use and what you get at each step.
Six steps, every engagement
Big or small, every piece of work follows the same path. The depth changes. The order doesn't.
- 1
Discover & plan
What problem are we solving, and for whom?
You getProblem statement, stakeholder map, BA plan
- 2
Understand today (As-Is)
How does work really happen now?
You getCurrent process maps, pain points, data
- 3
Design tomorrow (To-Be)
What should it look like, and why is it better?
You getFuture process, options, gap analysis
- 4
Define requirements
What exactly must the solution do?
You getPrioritised requirements, user stories, acceptance criteria
- 5
Deliver & test
Are we building the right thing, the right way?
You getBacklog support, traceability, UAT plan and results
- 6
Transition & measure
Are people using it, and did it pay off?
You getTraining, cut-over plan, benefits tracking
See the problem, then design the fix
Before changing anything, I map how work happens today and where it hurts. Then we design the future process together and agree what has to change to get there. A simple example:
The gap between the two rows is the change: new form, business rules, workflow and an integration. That gap list becomes the scope.
BPMN: one picture everyone understands
BPMN 2.0 (Business Process Model and Notation) is the international standard for drawing processes. It shows who does what, in what order, and where decisions happen. Business people can read it, and developers can build from it.
Example: supplier onboarding with a risk check. Each lane is a role, so hand-offs and delays are easy to spot.
What kicks it off
A piece of work
A decision point
The outcome
Other notations I use, depending on the audience
Swimlane flowcharts
A lighter version of BPMN for workshops and quick reviews with business teams.
UML use cases
Who uses the system and what they need it to do. Great for scoping a new platform.
Customer journey maps
The experience from the customer's side, with the moments that matter and where it breaks.
SIPOC & value streams
A one-page view of suppliers, inputs, process, outputs and customers. Handy at the start.
Data flow & context diagrams
Where data comes from, where it goes and which systems talk to each other.
Capability maps
What the organisation needs to be able to do, used to plan investment and spot overlaps.
Requirements that can be built and tested
A good requirement is clear, agreed, testable and traceable back to a business need. I write them at the level the project needs, from high-level business requirements to detailed user stories.
Types of requirements
| Type | Answers |
|---|---|
| Business | Why are we doing this? What outcome do we need? |
| Stakeholder | What does each group need from the change? |
| Functional | What must the solution do? |
| Non-functional | How well? Security, performance, access, privacy. |
| Transition | What is needed to move across? Data, training, cut-over. |
Example user story
As a procurement officer I want new suppliers to get a risk score automatically so that high-risk suppliers are reviewed before we sign.
Acceptance criteriaGiven a supplier answers "yes" to handling personal data, when the questionnaire is submitted, then the supplier is flagged high risk and sent to Governance for review.
Prioritising with MoSCoW
Who does what, agreed up front
Confusion about roles slows projects down more than technology does. A RACI matrix settles it early: for each activity, one person is Accountable, and everyone knows whether they do the work, give input or just need to be kept informed.
| Activity | Sponsor | Business owner | Business analyst | Project manager | Delivery team | End users |
|---|---|---|---|---|---|---|
| Approve scope and business case | A | R | C | C | I | I |
| Map the current process (As-Is) | I | A | R | I | I | C |
| Design the future process (To-Be) | I | A | R | C | C | C |
| Write and prioritise requirements | I | A | R | C | C | C |
| Build and configure the solution | I | C | C | A | R | I |
| User acceptance testing | I | A | R | C | C | R |
| Go-live decision | A | R | C | R | C | I |
| Track benefits after go-live | A | R | C | I | I | C |
Inputs, techniques, tools and outputs
Good practice based on the BABOK® Guide, applied in a practical way. Here is what goes into each step and what comes out of it.
| Step | Inputs | Techniques | Tools | Outputs |
|---|---|---|---|---|
| 1. Discover & plan | Business goals, strategy, problem reports | Stakeholder analysis, interviews, problem framing | Miro, Confluence, Excel | Problem statement, stakeholder map, BA plan |
| 2. As-Is | Procedures, system data, staff knowledge | Workshops, observation, process mapping, root cause analysis | Visio, Lucid, Miro | Current process maps, pain points |
| 3. To-Be | Pain points, goals, constraints | BPMN, options analysis, gap analysis, SWOT | Visio, Lucid, Power BI | Future process, recommended option, gap list |
| 4. Requirements | Gap list, policies, standards | User stories, use cases, MoSCoW, data modelling | Jira, Confluence, Excel | Prioritised requirements, acceptance criteria |
| 5. Deliver & test | Requirements, solution design | Backlog refinement, traceability, UAT planning | Jira, Azure DevOps, Excel | Traceability matrix, test scenarios, UAT sign-off |
| 6. Transition & measure | Tested solution, data, users | Data migration, training, benefits tracking | Power BI, SQL, Power Query | Cut-over plan, training material, benefits report |
The journey in practice: third-party risk at a council
A local government client needed a consistent way to understand the security and privacy risk that comes with its suppliers. Details are kept high level to respect client confidentiality.
- 1
Discover & plan
Agreed the problem with procurement, IT and governance: supplier risk was checked inconsistently, and often too late.
- 2
Understand today
Mapped how suppliers were being assessed. Found different forms, unclear ownership and no single record.
- 3
Design tomorrow
Designed a risk-tiered process: low-risk suppliers move quickly, high-risk suppliers get a deeper review.
- 4
Define requirements
Set out the questions, scoring rules, roles and approvals the platform had to support.
- 5
Deliver & test
Configured and refined the workflow in the council's risk platform and tested it with real scenarios.
- 6
Transition & measure
Coached staff to run the process themselves and handed over clear guidance.
How business analysis helps your organisation
Less rework
Problems are found on paper, where they are cheap to fix, not after go-live.
Better decisions
Options are compared on evidence, so leaders know what they are paying for and why.
Everyone on the same page
Shared diagrams and agreed requirements stop the "that's not what we asked for" moment.
Lower risk
Security, privacy and compliance needs are built in from the start, not bolted on.
Smoother adoption
Users are involved early, so the new way of working actually sticks.
Benefits you can measure
Clear goals at the start mean you can show the return at the end.
Planning a change?
Let's talk about where you are now and where you need to be.
Get in touchSee more case studies