Your Programme Has Owners. Does It Have Decision-Makers?

Why clear ownership is not enough and how decision rights and guardrails keep complex programmes moving

The first real disagreement on a programme rarely happens in the steering committee. More often, it happens on a Wednesday afternoon between two perfectly capable people. Both think the decision is theirs. Or, perhaps worse, both think it belongs to the other person.

Where it gets complicated

We spend a lot of time at the start of programmes agreeing the destination, the workstreams and who is accountable for delivering them. That matters, but being responsible for the work is not the same as having the right to make the decisions that come with it. That distinction can create a surprising amount of friction.

Think about some of the decisions that start to appear once a programme gets moving. Can a critical dependency slip? Who can agree a change in scope that impacts three different teams? Can a launch-readiness gate be moved? What happens when global and affiliate priorities conflict?

These decisions often sit between teams, functions and reporting lines. In pharma and biotech, that can mean navigating across Development, Medical, Commercial, Manufacturing, Global, Regional and Affiliate organisations.

The more boundaries a programme crosses, the easier it becomes for an important decision to belong to nobody by default. And when that happens, things slow down.

Not necessarily because people are avoiding decisions. Often, they genuinely do not know who has the authority to make them, whose views need to be considered, or how far they can go before they need to escalate.

Start with the decisions, not just the workstreams

Before the work really gets underway, it is worth getting programme leaders into a room and deciding not just, “Who owns each workstream?” but “What are the important decisions we already know we are going to have to make?”.

Ask each workstream lead which decisions they expect to face in the first few months that they cannot make alone. Pool those decisions, remove the duplicates and focus on the ones that are likely to matter early. For each one, try to identify a single decision owner. A person, rather than a function, team or committee. Then be clear about who needs to contribute before the decision is made and who needs to know afterwards. Being consulted is not the same as having a vote, and making that distinction explicit can save a great deal of later frustration. It is also worth testing whether the person named can actually make the decision stick. Do they have the authority? Do they control the budget or resources affected? Will the people impacted recognise that the decision sits with them?

Putting someone’s name in a box does not automatically give them the power to act.

You cannot define every decision in advance

This is where decision-rights exercises can become too rigid. No programme can predict every decision it will need to make. New evidence emerges, priorities shift, timelines move and the shape of the programme itself changes. So alongside defining the decisions you can foresee, leaders also need to agree the guardrails or guiding principles that will help teams make the decisions you cannot yet see.

These might include principles such as:

  • decisions should sit as close as possible to the people with the best information

  • teams can act within agreed budget and risk thresholds without escalation

  • patient impact, safety or regulatory risk always outweighs speed

  • enterprise value should take precedence where local optimisation creates downstream cost or complexity

  • decisions that affect multiple functions must include those functions early, not after the fact

  • where evidence is incomplete, teams should be clear about the assumption they are making and when it will be revisited

The exact principles will differ from programme to programme, but the point is the same. If you cannot define the future decision, you can still define how you want people to think about it. That gives teams something to work from when the answer is not obvious.

Define the boundaries, not just the owner

For some decisions, the most useful question is not simply “Who decides?” but “Within what boundaries can they decide?” For example, a workstream lead may have authority to change sequencing, but not overall scope. A regional leader may be able to adapt implementation locally, but not change the underlying strategic intent. A programme team may be able to absorb a small budget increase, but anything above an agreed threshold needs escalation. These boundaries matter because they create confidence. Without them, people either escalate too much or take risks they were never really empowered to take. With them, teams can move faster because they know where their freedom starts and stops.

Agree what happens when a decision stalls

Even with clear decision rights, some decisions will get stuck. That is normal. What matters is agreeing in advance what happens next. “Take it to the steering committee” is not particularly helpful if the committee does not meet for another three weeks. Instead, agree a named escalation point and a timeframe. If the decision cannot be made within two days, who does it go to? If two functions remain split, who breaks the tie? If the decision exceeds an agreed risk or budget threshold, who steps in?

The aim is not to create more governance. It is to stop governance becoming the reason nothing moves.

A few useful watch-outs for leaders:

There are some phrases that should make your ears prick up.

  • “I thought they were deciding that.”

  • “We’ll need to take that to the committee.”

  • “I’m accountable for it, but I don’t actually control the budget.”

Or perhaps the simplest one: ask “Who decides?” and listen to how the answer begins. If it starts with “Well… it depends…”, there is probably some work to do. The same is true if two people immediately look at each other, or if the answer names a committee rather than a person. Those are often early signals that the programme has responsibility mapped, but not decision-making clarity.

What good looks like

The goal is not to eliminate disagreement.

In fact, working through decision rights often surfaces disagreements between senior people much earlier than they otherwise would. That can feel uncomfortable, but disagreement before the programme starts is considerably cheaper than disagreement once 50 people are already moving. Clear decision rights give teams something incredibly valuable during complex transformation: the confidence to move. So people understand who can decide, whose voice needs to be heard, where the boundaries are and what principles to use when the unexpected arrives. Removing one area of ambiguity in a swirl of uncertainty.

Next
Next

A Better Pitch Is Not Commercial Readiness