If your team still needs permission to book a routine courier, ask what "autonomy" means in practice.
In 2007, the BBC reported that Toyota worker Laura Wilshire spotted a problem with a Camry's seatbelt fitting. She pulled the andon cord, the line stopped, and colleagues helped fix it. Keeping production moving mattered. So did correcting the fault before it moved further down the line.
Toyota's description of the system pairs the worker's authority with support: the cord alerts a team leader. If the issue cannot be resolved within the workstation's allotted time, the line pauses.
For office teams, the limits and response times will differ. The key lesson is to define the decision and the path to support it.
For one recurring decision, write down four things:
- Result: What outcome or standard must we protect?
- Authority: What can the person decide without approval?
- Escalation: When should they ask for help, who responds, and how quickly?
- Review: When will we examine the decisions and adjust the rules?
For a courier booking, that could mean approved suppliers and a spending limit, with exceptions going to a named approver. Review costs and missed deliveries each week.
Those answers make autonomy usable. People have room to act and a clear route to help.
Write those four down before adding another check-in.
Which decision could your team own this week without waiting for permission?
