A Business Analyst (BA) is the person who sits between the people who have a problem and the people who build a solution. Their job is to understand what a business truly needs, describe it clearly, and make sure the solution that gets built actually solves the real problem.
That sounds simple. It is not. Most failed projects do not fail because the technology was wrong — they fail because nobody correctly understood what was needed in the first place. The BA exists to prevent exactly that failure.
What a BA actually does, day to day
The work varies by organisation, but almost every BA spends their time on a cycle of five activities:
- Eliciting — drawing out what people need through interviews, workshops, and observation. Note the word "eliciting" rather than "gathering." Requirements are rarely lying around to be collected; they have to be drawn out, because people often cannot articulate what they need until the right questions are asked.
- Analysing — making sense of what was heard, spotting conflicts, gaps, and assumptions, and organising it into something coherent.
- Documenting — writing it down clearly enough that a developer, a tester, and a business sponsor all understand the same thing.
- Communicating — acting as translator between business language and technical language, in both directions.
- Validating — checking that what is being built matches what was needed, before it is too late to change cheaply.
Why organisations need a BA
Imagine a company says "we need a new system to handle customer complaints." Without a BA, the development team builds what they think that means. Six months later, it is delivered — and it turns out the real problem was that complaints were getting lost between departments, not that the software was slow. The wrong problem was solved at great cost.
A BA prevents this by digging beneath the stated request to the underlying need. The stated request was "a new system." The real need was "complaints should never get lost." Those lead to very different solutions.
What a BA is not
A BA is not a project manager (who manages time, budget, and people), not a developer (who builds the solution), and not a tester (who verifies it works) — though a BA works closely with all three and, in smaller organisations, sometimes wears several of these hats at once.