Cape Town, South Africa – [12 May 2026]
“The business changed their mind.”
“Stakeholders were vague.”
“We only found the gaps once delivery started.”
Most delivery teams have heard some version of this. Sometimes it is true. Priorities do shift. Stakeholders do contradict themselves. Pressure does expose issues that were not obvious at the start.
But those explanations have become a little too convenient.
They often describe what became visible late, not what was weak early.
When delivery slows down, scope starts moving, defects increase, change control piles up, or teams end up rewriting something that was already approved, the problem often begins further upstream. Not because someone was careless, or because stakeholders should arrive perfectly formed, but because the requirement was never strong enough to support the decision that followed.
That is why bad requirements should not be treated as a narrow BA issue or a documentation problem. They are a business risk. They affect decision quality, delivery confidence, cost, timelines, and the organisation’s ability to manage change well.
The familiar complaint is only part of the story
It is easy to blame stakeholder vagueness when delivery starts to wobble. But in most organisations, stakeholders do not arrive with perfect clarity. Business language is often messy. Priorities compete. People discover what they really mean by talking, testing, and seeing consequences.
That is normal.
The real question is whether the requirement was ever strong enough to carry the commitment placed on it.
Was it clear enough to be interpreted consistently? Specific enough to be tested properly? Connected clearly enough to the intended business outcome? Traceable enough to survive challenge when scope, design, or delivery questions appeared? Or did the team move forward because the requirement had been discussed, written down, and approved, while important ambiguity still sat inside it?
That distinction matters. Once a weak requirement moves into design, build, test, and change control, the organisation has already accepted avoidable uncertainty into delivery.
Signed off is not the same as decision-ready
This is one of the most common misunderstandings in change work.
A signed-off requirement can still be vague. It can still be incomplete. It can still leave too much open to interpretation. It can still be weakly validated. Yet many teams treat approval as proof that the requirement is ready.
It is not.
Sign-off means someone agreed to what was in front of them. It does not prove that the requirement is strong enough to design from, build from, test from, or manage against with confidence.
That is why so much rework feels surprising when it should not. A requirement is approved. Delivery starts. Then the questions come. What exactly does this mean? Which exception matters? What outcome is this meant to protect? Why does testing expose a gap nobody dealt with earlier? Why is this now being raised through change control if it was supposedly already agreed?
The requirement did not suddenly become weak. It was weak before the project committed to it.
Decision-ready is the real standard. Not merely captured. Not merely discussed. Not merely signed off. Strong enough for people to commit against with open eyes.
Weak requirements do not fail in one moment
They fail in stages.
A term is too broad. A condition is assumed rather than defined. A business rule is implied but not made explicit. Validation is treated as a meeting instead of a discipline. Traceability is seen as overhead. The link between the requirement and the intended outcome becomes thin.
Then delivery starts, and the cost starts moving.
Design teams interpret meaning for themselves. Developers fill in gaps. Testers raise defects that are really unresolved requirement questions. Sponsors ask why something that was approved is suddenly back in discussion. Scope change begins to climb, not always because the business has changed its mind, but because the requirement was not solid enough when the team first moved on it.
This is where organisations often fool themselves. They think they are moving fast because the requirement was written, reviewed, and approved quickly. In reality, they may simply be carrying risk forward and charging interest on it later.
A stronger requirements quality bar changes that.
It does not require perfection. It requires discipline. A requirement should be clear enough, testable enough, traceable enough, and validated enough to reduce avoidable surprises before they become delivery problems.
This is not only a BA problem
Business analysts have a central role here. They are often best placed to challenge ambiguity, expose assumptions, tighten language, connect requirements to outcomes, and raise the quality bar before commitment hardens.
But this cannot be framed as a BA-only issue.
The quality of requirements is shaped by the wider organisation: what sponsors are willing to approve, what delivery leaders are willing to push through, what product owners accept into scope, what technology teams inherit without challenge, and what management chooses to examine before delivery begins.
That is why accountability here should be constructive, not accusatory.
This is not about blaming stakeholders for being vague. It is not about blaming Business Analysts for not writing perfectly. It is about recognising that requirements quality is a shared business discipline. When it is weak, the effects travel far beyond the BA team. They show up in missed expectations, rework, delays, defects, frustrated teams, and more expensive change.
A better question to ask earlier
Organisations do not reduce avoidable rework by getting better at blaming “the business” once things go wrong.
They reduce it by asking a better question earlier:
Is this requirement genuinely strong enough for people to commit against?
Not just readable. Not just approved. Strong enough to support design, delivery, testing, and change with confidence.
That is the real test.
Because bad requirements are not just a BA problem.
They are a business risk.
Media Contact:
Media Team
Business Change Academy
Email: media@businesschange.academmy
Website: https://www.businesschange.academy


