Tech Waves logo
Business analysis

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.

The business analysis journey

Six steps, every engagement

Big or small, every piece of work follows the same path. The depth changes. The order doesn't.

  1. 1

    Discover & plan

    What problem are we solving, and for whom?

    You getProblem statement, stakeholder map, BA plan

  2. 2

    Understand today (As-Is)

    How does work really happen now?

    You getCurrent process maps, pain points, data

  3. 3

    Design tomorrow (To-Be)

    What should it look like, and why is it better?

    You getFuture process, options, gap analysis

  4. 4

    Define requirements

    What exactly must the solution do?

    You getPrioritised requirements, user stories, acceptance criteria

  5. 5

    Deliver & test

    Are we building the right thing, the right way?

    You getBacklog support, traceability, UAT plan and results

  6. 6

    Transition & measure

    Are people using it, and did it pay off?

    You getTraining, cut-over plan, benefits tracking

"An hour spent planning saves a week of rework."The idea behind every engagement: get clarity early, when changes are cheap.
As-Is to To-Be

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:

AS-IS · today Request sentby email Details typed intoa spreadsheet Chase approvalsby phone and email Re-keyed intothe system ⚠ No single record⚠ Errors and duplicates⚠ Days of waiting, no visibility⚠ Same data entered twice TO-BE · future Online requestform Rules check therequest automatically Approval workflowwith reminders Saved once, flowsto the system ✓ One source of truth✓ Fewer errors✓ Status visible to everyone✓ Enter once, use everywhere

The gap between the two rows is the change: new form, business rules, workflow and an integration. That gap list becomes the scope.

Process modelling

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.

Business ownerProcurementGovernance & IT × Request newsupplierSend riskquestionnaireDetailed securityreviewApprove and setup supplierHigh risk? YesNo StartEnd

Example: supplier onboarding with a risk check. Each lane is a role, so hand-offs and delays are easy to spot.

Start event
What kicks it off
Task
A piece of work
Gateway
A decision point
End event
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

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

TypeAnswers
BusinessWhy are we doing this? What outcome do we need?
StakeholderWhat does each group need from the change?
FunctionalWhat must the solution do?
Non-functionalHow well? Security, performance, access, privacy.
TransitionWhat 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 criteria
Given 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

MustNot live without it
ShouldImportant, can wait briefly
CouldNice if time allows
Won'tNot this release
RACI matrix

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.

ActivitySponsorBusiness ownerBusiness analystProject managerDelivery teamEnd users
Approve scope and business caseARCCII
Map the current process (As-Is)IARIIC
Design the future process (To-Be)IARCCC
Write and prioritise requirementsIARCCC
Build and configure the solutionICCARI
User acceptance testingIARCCR
Go-live decisionARCRCI
Track benefits after go-liveARCIIC
RResponsible: does the workAAccountable: owns the outcomeCConsulted: gives inputIInformed: kept up to date
Business analysis toolkit

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.

StepInputsTechniquesToolsOutputs
1. Discover & planBusiness goals, strategy, problem reportsStakeholder analysis, interviews, problem framingMiro, Confluence, ExcelProblem statement, stakeholder map, BA plan
2. As-IsProcedures, system data, staff knowledgeWorkshops, observation, process mapping, root cause analysisVisio, Lucid, MiroCurrent process maps, pain points
3. To-BePain points, goals, constraintsBPMN, options analysis, gap analysis, SWOTVisio, Lucid, Power BIFuture process, recommended option, gap list
4. RequirementsGap list, policies, standardsUser stories, use cases, MoSCoW, data modellingJira, Confluence, ExcelPrioritised requirements, acceptance criteria
5. Deliver & testRequirements, solution designBacklog refinement, traceability, UAT planningJira, Azure DevOps, ExcelTraceability matrix, test scenarios, UAT sign-off
6. Transition & measureTested solution, data, usersData migration, training, benefits trackingPower BI, SQL, Power QueryCut-over plan, training material, benefits report
Case study

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. 1

    Discover & plan

    Agreed the problem with procurement, IT and governance: supplier risk was checked inconsistently, and often too late.

  2. 2

    Understand today

    Mapped how suppliers were being assessed. Found different forms, unclear ownership and no single record.

  3. 3

    Design tomorrow

    Designed a risk-tiered process: low-risk suppliers move quickly, high-risk suppliers get a deeper review.

  4. 4

    Define requirements

    Set out the questions, scoring rules, roles and approvals the platform had to support.

  5. 5

    Deliver & test

    Configured and refined the workflow in the council's risk platform and tested it with real scenarios.

  6. 6

    Transition & measure

    Coached staff to run the process themselves and handed over clear guidance.

The result: vendor risk is now part of everyday business, not a one-off exercise, with clear ownership and an audit trail.
Why it matters

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.

"Measure twice, cut once."An old carpenter's rule that applies just as well to technology projects.

Planning a change?

Let's talk about where you are now and where you need to be.

Get in touchSee more case studies
Scroll to Top
×