Organisations can have full backlogs, detailed requirements and busy delivery teams and still make poor change decisions. The difference lies in whether business analysis is being treated as a collection of tasks or developed as a deliberate organisational capability.
Many organisations do not lack business analysis activity.
They lack business analysis capability.
Requirements are gathered. Workshops are held. Notes are circulated. Backlogs are updated. User stories are written. Process maps are produced.
All of this work can be useful. But none of it, on its own, tells us whether the organisation has understood the real problem, involved the right stakeholders, tested its assumptions or made a well-informed change decision.
That distinction matters.
A team can become very efficient at processing requests while still moving quickly towards the wrong answer. It can deliver what was asked for, on time and to specification, and still fail to achieve the intended business outcome.
Business analysis should therefore be understood as more than support for decisions that have already been made.
It is a capability that helps organisations decide what change is needed in the first place.
Activity can look like capability
The problem is not requirements documents, workshops or backlogs.
The problem begins when completing them becomes the definition of business analysis.
Consider a stakeholder who asks for a new dashboard.
A task-focused response might be to capture the requested fields, clarify the layout, document the requirement and move it into delivery.
A capability-led response goes further.
What decision is this dashboard supposed to improve? What is making that decision difficult today? Who actually needs the information? Is the underlying problem poor visibility, unreliable data, a broken process or unclear accountability? Is a dashboard even the most appropriate response?
The requested dashboard may still turn out to be the right answer.
But now it is an informed answer rather than an assumption.
That is the difference between capturing a request and investigating the need behind it.
The risk of reducing business analysis to support work
When business analysis becomes order-taking, organisations can end up solving symptoms rather than causes.
A request arrives with a proposed solution already attached, and the work begins from there. The question becomes, “What do you need us to build?” rather than, “What are we actually trying to improve?”
That narrows the conversation too early.
Strong business analysis creates space to investigate the business situation, understand root causes and consider alternative ways of achieving the desired outcome before committing to one solution.
The same problem appears in stakeholder engagement.
Inviting people to a workshop does not mean stakeholders are aligned.
The most vocal person in the room may not represent everyone affected by the change. Important perspectives may be missing. Competing priorities may remain hidden. A decision that appears settled in the meeting may unravel later when someone with significant influence challenges it.
Business analysis brings more deliberate thinking to this work: who has an interest in the change, who can influence it, who will be affected by it and where competing needs need to be surfaced and negotiated.
Requirements present a similar challenge.
A requirement is not automatically valuable simply because somebody requested it.
Requirements need to be elicited, evidenced, challenged and refined before they are documented, agreed and managed. They need to make sense in the context of strategy, business priorities, technical constraints and the value the organisation is trying to create.
A well-maintained backlog is not proof that an organisation understands the problem it is trying to solve.
What business analysis capability actually looks like
Business analysis becomes more valuable when it is seen across the whole journey of change rather than confined to requirements definition.
Early in an initiative, that may mean understanding organisational context, strategic drivers and the reason change is needed.
It may then involve investigating the current situation, uncovering root causes and shaping feasible options.
As the change develops, business analysis can help define the processes, roles, information and technology required, clarify requirements and support decisions about what should be delivered.
Its contribution does not necessarily end when delivery begins.
There is also a role in supporting implementation, understanding the impact on people and operations, and examining whether the expected benefits have actually been realised.
Across that life cycle, several capabilities remain important: framing the problem clearly, understanding stakeholders, evaluating options, improving the quality of requirements and maintaining a focus on the business outcome.
The strongest business analysis practice does not simply make delivery administration easier.
It improves the quality of the decisions that determine what should be delivered in the first place.
Templates cannot replace judgment
This is also why improving business analysis capability is not simply a matter of providing more templates.
Templates and techniques have their place. They give people structure and help create consistency.
But the technique is only as useful as the thinking behind it.
A process map can document an inefficient process perfectly without anyone questioning why the process works that way.
A workshop can follow an excellent agenda while allowing the most senior participant to dominate the discussion.
A backlog can be meticulously maintained while becoming little more than a queue of untested solution requests.
Business analysis capability depends on more than knowing which template or technique to use.”
It requires the personal qualities to listen, question, facilitate, communicate, influence and negotiate. It requires enough business knowledge to understand the organisation, its customers, priorities and constraints. And it requires professional techniques that can be selected and adapted to the situation rather than applied mechanically.
A capability is not a collection of forms.
It is the ability to combine judgment, knowledge and technique to improve a real business situation.
The leadership test
This does not mean every organisation needs a large business analysis team, or that every piece of change requires somebody with the formal title of business analyst.
Business analysis capability may sit within product, technology, transformation, operations or a dedicated practice.
The more useful leadership question is whether the capability exists where important change decisions are being made.
Leaders can test this by asking:
- Are people brought into initiatives early enough to investigate the problem, or only after a solution has effectively been chosen?
- Do teams have permission to challenge requests and investigate root causes, or are they expected to translate requests directly into delivery items?
- Are stakeholder differences identified and managed early, or discovered later through resistance and scope churn?
- Are decision-makers shown realistic options, impacts, risks, constraints and benefits, or mainly the preferred solution?
- After implementation, does anyone examine whether the change achieved the intended business outcome?
If the answer to these questions consistently points towards task execution, the issue is unlikely to be solved by adding another template.
It is a capability question.
Leaders need to create the conditions for people to analyse properly: access to business context, evidence and decision-makers; enough time to investigate and validate; and opportunities to develop judgment through standards, mentoring, feedback and deliberate practice.
Business analysis needs to be treated as capability
The point is not to have the tidiest templates, the largest backlog or the busiest delivery calendar.
Visible activity is not the same thing as effective analysis.
What matters is whether the organisation is making space for the disciplined work of understanding the problem, challenging assumptions, aligning stakeholders, evaluating options and connecting delivery to the business outcome it is meant to achieve.
Business analysis is not a support function that begins once somebody has decided what to build.
It is a professional capability that helps organisations decide what change is needed, why it matters and how best to pursue it.
Where is business analysis in your organisation still being treated as a set of tasks rather than a professional capability?
Share
Editorial contacts