When people are unsure who can approve a change or settle a disagreement, even routine work can stall. The fix is not to involve everyone in every choice. It is to make decision responsibilities visible, match authority to the work, and agree on what happens when a decision needs help. These practical steps can help your team make sound choices without unnecessary handoffs, repeated discussions, or last-minute surprises.
Sort decisions by impact
Start by listing recurring decisions that affect delivery, customers, staff, or spending. Examples might include changing a work process, approving an exception, adjusting a schedule, or committing to a supplier. Group decisions by their likely impact and reversibility. A low-risk choice that is easy to undo can usually sit close to the work; a decision with wider or harder-to-reverse effects may need additional review.
Avoid creating a lengthy approval process for every possible scenario. Focus first on decisions that regularly cause delays, confusion, or disagreement. For each one, note what information is needed and which teams or roles are affected. This gives you a manageable starting point and helps distinguish genuine oversight needs from habits that add steps without improving the decision.
Name one accountable owner
Give each recurring decision a clearly identified owner: the person responsible for making the call and communicating it. Contributors can provide expertise, affected teams can flag practical impacts, and an approver can confirm a required boundary. But make clear which role has the final decision. If accountability is shared vaguely across a group, people may wait for someone else to act.
Write responsibilities in plain language, using role names rather than relying only on individual names. For example: “The service lead decides routine workflow changes after consulting the affected team; changes to customer commitments go to the department head.” Include any limits, such as spending authority, safety requirements, or policy rules. Review the assignments when roles or responsibilities change.
Set useful input and time limits
Specify who needs to be consulted and what kind of input they should provide. Ask for relevant facts, risks, and likely effects—not approval from every person who might have an opinion. The decision owner should share the question, the options under consideration, and a response deadline. This lets contributors focus their feedback and helps prevent consultation from becoming an open-ended discussion.
Agree on what happens if someone does not respond by the deadline. Depending on the decision, the owner might proceed using the information available, extend the deadline, or pause because a required safety or compliance check is missing. State the rule in advance. Keep a short record of the decision, the reason, and any follow-up actions so people can act from the same understanding.
Make escalation predictable
An escalation path should explain when to raise an issue, who receives it, and what information to bring. Common triggers include a conflict between team priorities, a decision beyond the owner’s authority, a serious risk, or a missed deadline that affects other work. Direct the issue to the next appropriate role, not automatically to the most senior person. This keeps routine decisions moving and reserves higher-level attention for matters that need it.
Set a response expectation that fits the urgency and risk. When escalating, summarize the decision needed, the options considered, the impact of waiting, and the recommended next step. If the designated contact is unavailable, identify a backup. Review escalations periodically: repeated referrals may point to unclear authority, missing guidance, or a decision owner who needs more context or support.
Clear decision ownership does not remove discussion; it gives discussion a useful purpose and a clear endpoint. Start with a few decisions that regularly slow work, assign owners, define the input required, and document when to escalate. Test the approach with your team and adjust it where handoffs remain unclear. Top End Organisational Design can help you review how responsibilities fit together.