Decision Rights: Why Australian Projects Stall When Nobody Knows Who Has the Final Say

Get In Touch

Related Posts

Decision Rights: Why Australian Projects Stall When Nobody Knows Who Has the Final Say

Decision rights are the reason a simple approval can drift across four weeks and three meetings. Picture the scene. The steering committee agenda lists “approve preferred vendor” for the third week running. Everyone in the room has an opinion. Several people nod. Somebody says, “Let’s take that offline.” Nobody actually decides, because nobody is quite sure whose decision it is.

This is the decision rights problem, and it quietly stalls projects across Australian businesses, government agencies and not-for-profits every day. It rarely looks like a crisis. It looks like polite delay. This guide explains what decision rights are, why they go missing, what the delay costs, and how business analysts and project teams can fix it with clear roles, simple tools and a decision log that people actually use.

Decision rights diagram showing input, recommend, decide and perform roles with one named decider

What Are Decision Rights?

Decision rights describe who has the authority to make, approve, veto or influence a particular decision. They answer a deceptively simple question: when this decision needs to be made, whose call is it?

That’s different from responsibility. Many people can be responsible for doing the work, and many more can have a strong view. But the authority to decide belongs to specific roles, and the clearest arrangements give each important decision one named decider. When the arrangements are clear, people know when to contribute, when to step back and when to escalate. When they’re not, every decision becomes a negotiation.

What the Decision Rights Problem Looks Like on a Real Project

Unclear ownership of decisions rarely announces itself. Instead, it shows up as familiar frustrations:

  • Decisions are made in a meeting, then quietly reopened a week later.
  • Requirements sit in review for weeks because nobody will sign them off.
  • Scope keeps growing because each stakeholder can add something and nobody can say no.
  • Teams wait for approval from someone who doesn’t believe the decision is theirs.
  • People escalate by emailing a senior executive, bypassing the agreed process.
  • The project plan says a decision is due, but nobody can name who owns it.

If a few of those sound familiar, you have a decision rights problem rather than a people problem. The individuals are usually capable. The structure around them is unclear.

Why Decision Rights Go Missing

1. Governance is built around reporting, not deciding

Many project governance structures are good at collecting status updates and poor at assigning authority. Committees meet, review progress and note risks, but the question of who can actually approve a change is left vague.

2. Business and IT each assume the other will decide

On technology projects, the business expects IT to choose the solution while IT expects the business to define the need. Without agreed authority, a gap opens in the middle, and it’s often the business analyst who notices it first.

3. Consensus quietly replaces a decision

Many organisations value collaboration, and that’s healthy. But consensus can slide into a situation where a decision needs everybody’s agreement and so never happens. Consultation should inform a decision, not become a veto for everyone who was consulted.

4. Sponsors change or stay too distant

When a sponsor moves on, the authority they carried can vanish overnight. Even when the sponsor stays, they may be too far from the detail to decide, and too busy to delegate clearly.

5. Agile roles exist on paper but not in practice

In Scrum, the product owner is meant to make decisions about the product backlog, and the Scrum Guide is explicit that the wider organisation should respect those decisions. In reality, product owners are often overruled or second-guessed, which leaves the team unsure who to listen to.

6. Unwritten rules decide instead

When formal authority is unclear, informal power fills the gap. The loudest voice, the longest-serving manager or the person with the best relationship with the executive ends up deciding. That might work some of the time, but it’s unpredictable and impossible to hold accountable.

The Real Cost of Unclear Decision Rights

Slow decisions feel harmless in the moment, but they add up:

  • Every unmade decision holds up the work that depends on it.
  • Decisions made by the wrong person get reversed, and the work done in between is wasted.
  • Scope creep. Without a clear gatekeeper, requests keep arriving and expanding the project.
  • Budget pressure. Longer timelines and rework consume money quickly.
  • Team frustration. Capable people lose motivation when they can’t get a straight answer.
  • Weak traceability. If nobody can say who approved what, audits and post-project reviews become difficult.

There’s also a quieter cost: decision fatigue. When people have to renegotiate every choice, energy goes into politics rather than delivery.

Why Business Analysts Are Well Placed to Fix It

Business analysis sits between stakeholders, and that gives analysts a clear view of who needs to decide what. A business analyst already runs stakeholder analysis, documents requirements, manages change requests and chases sign-off. Making decision rights explicit is a natural extension of that work.

The professional body IIBA describes business analysis as enabling change by defining needs and recommending solutions, and that is hard to do when nobody can approve the solution. A good analyst makes the question visible early: who decides this, and by when? Analysts who build this habit become far more valuable to project managers and sponsors, because they remove the quiet blockers that stall delivery.

Decision Rights Frameworks Compared

You don’t need to invent your own method. Several well-known tools help clarify who decides, and each suits different situations:

Framework What the letters mean Best for, and a watch-out
RACI Responsible, Accountable, Consulted, Informed Clarifying who does the work and who is accountable. Watch out: it doesn’t always say who makes the call, and teams can label too many people as “consulted”.
RAPID Recommend, Agree, Perform, Input, Decide Important or contested decisions where authority needs to be explicit. Watch out: it can feel heavy for small, everyday choices.
DACI Driver, Approver, Contributors, Informed Project and product teams that want one driver and one approver per decision. Watch out: it only works if the approver really has the authority.

A RACI matrix is the most widely recognised and is often the easiest starting point. The best framework is the one your people will actually use. What matters is that every important decision has one clear decider.

How to Clarify Decision Rights: A Practical Plan

Here is a step-by-step approach any project team can apply, whether you’re running a small change or a large program:

  1. List the decisions that really matter. You don’t need to map every choice. Start with decisions that affect scope, budget, timeline, risk and key requirements.
  2. Name one decider for each. Shared authority sounds fair, but it usually means nobody is accountable. One name per decision keeps things moving.
  3. Separate roles clearly. Distinguish who recommends, who gives input, who decides and who carries it out. The same person doesn’t need to do all four.
  4. Set deadlines and an escalation path. Agree how long a decision can take and what happens if it stalls. A deadline turns “we’ll get to it” into a commitment.
  5. Record decisions in a decision log. Capture what was decided, by whom, when and why. This protects the team from later disputes.
  6. Make requirements approval explicit. Specify who signs off requirements and what “approved” means, so documents don’t sit in review forever.
  7. Agree the rules for reopening decisions. A decision shouldn’t be reversed without new information and the decider’s agreement.
  8. Share the arrangement widely. The arrangement only works when everyone knows it. Publish the matrix and refer to it in meetings.
  9. Review at each stage gate. Roles change as projects mature, so revisit who decides at key milestones.

What a Good Decision Log Looks Like

A decision log doesn’t need to be fancy. A simple table, kept up to date and visible to the team, is often enough. Here’s a practical layout:

Field What to record
Decision A clear, one-line statement of what was decided.
Context Why the decision was needed and what it affects.
Options considered The main alternatives, so people can see the thinking.
Decider The named person who had the final say.
Date and reason When it was made and the main reason behind it.
Review date When, if ever, the decision should be revisited.

Warning Signs Your Project Has a Decision Rights Problem

  • The same topic appears on the agenda meeting after meeting.
  • Nobody can name who approves a specific change.
  • People say “I’m happy either way, it’s up to someone else”.
  • Approvals arrive from unexpected senior people late in the process.
  • Team members avoid raising issues because they don’t know where they will land.
  • Previous decisions are regularly challenged or reversed.

Business Analyst Skills That Help Clarify Who Decides

Facilitating clear decisions takes practical techniques: stakeholder analysis, structured requirements, process modelling and confident communication. Our business analysis courses are designed to build those skills:

You can compare all options on our business analyst courses page. If you’re weighing up which certification suits your career, our guides are a good place to start: read the Business Analyst Course Australia career guide, see whether the BCS Business Analysis Techniques certification is worth it, and find out whether the AgileBA Foundation certification is worth it.

Business Analyst Courses Across Australia: Online, In-House and In Person

Clarity about who decides comes from skilled people who share the same techniques, so it helps when your team trains together. Choose your city below, or ask about live virtual online and in-house options:

You can also see the full locations page, learn more about us, or contact our team on 1300 649 299 to find the right course for you or your organisation.

Frequently Asked Questions About Decision Rights

What are decision rights?

Decision rights define who has the authority to make, approve, veto or influence specific decisions. Clear authority means everyone knows who has the final say, so decisions are made on time and don’t get reopened without good reason.

Who has the final say on a project?

It depends on the decision. The sponsor usually decides on funding and strategic direction, the project manager on delivery matters, and the product owner or business owner on requirements and priorities. The key is to agree and document it, so there is no guessing.

What is the difference between RACI and RAPID?

RACI mainly clarifies who is responsible, accountable, consulted and informed for tasks and deliverables. RAPID focuses on a specific decision, separating who recommends, who agrees, who provides input, who decides and who performs. RAPID is often better for important, contested decisions.

How do you decide who should make a decision?

Look for the person who holds the accountability for the outcome, has the right information and can act on the result. Where possible, place the decision as close to the information as is sensible, and escalate only when it exceeds that person’s authority.

What is a decision log?

A decision log is a simple record of important project decisions, including what was decided, who decided, when, why and what alternatives were considered. It prevents confusion and gives teams something to point to when questions come up later.

How can a business analyst help with decision rights?

Business analysts identify stakeholders, clarify who must approve requirements, document decisions and surface the unclear points early. Their position between the business and delivery teams makes them well suited to making decision rights visible.

Final Thoughts on Decision Rights

Most stalled projects don’t lack effort or intelligence. They lack clarity about who decides. When decision rights are clear, meetings get shorter, requirements get approved, scope stays under control and good people can get on with the work. It’s one of the simplest and most overlooked improvements a project team can make.

If you’d like to build the skills to bring that clarity to your projects, explore our business analyst courses in Australia or speak with a course advisor today.

Scroll to Top