A night shift supervisor at a warehouse once told me about the longest ten minutes of her year. An automated guided vehicle kept stopping at the same junction, orders were stacking up, and four people stood around the charging bay offering theories. The technician thought it was a sensor setting. The operations manager thought it was a layout problem. The vendor’s remote engineer was on a call and could not say. Nobody had been told who was allowed to change the route configuration. Stories like this one explain why teams running robots keep asking the same practical questions about decision rights, and this FAQ answers the most common ones in plain terms.
Why do robotics operations need decision rights spelled out?
Because robots sit at an awkward crossing of responsibilities. Maintenance, operations, software, safety and often an outside supplier all touch the same machines. Each group has a reasonable claim on a decision about when to change a setting, when to pause a fleet or when to roll out an update. When those claims overlap and nobody has written down who closes the question, the default is delay, which in a warehouse or factory means idle equipment and tired people.
What is the difference between an owner, someone consulted and someone informed?
The owner makes the call. People consulted know something that could change the answer, such as the technician who understands the sensor behaviour or the planner who knows the shipping schedule. People informed are affected by the outcome, such as the next shift, but are not asked to weigh in beforehand. Keeping these three groups distinct keeps conversations short. A common slip is to treat everyone as consulted, which turns a quick decision into a long meeting.
Who should own a routine change, like adjusting a route or a speed limit?
Usually the operations lead on the shift, inside a boundary the team has agreed in writing. The boundary matters: a modest adjustment within defined limits can be decided on the spot, while a change outside those limits goes up a rung. Write the boundary in a language the whole shift can read, with examples, so that nobody has to guess whether their situation qualifies.
What about bigger changes, such as a software update or a new layout?
These deserve a short consultation window and a named owner who is not the person doing the work. A sensible pattern is for the operations manager to own the decision after consulting the technician, the safety representative and the vendor contact within an agreed number of days. The owner then writes down the outcome and the reason. The deadline should reflect the real calendar, for example the next quiet period, so that nobody can say there was no time to think and nobody can say there was too much.
For a sense of how flexible modern machines have become and why configuration choices keep multiplying, see this look at how robots are moving from single-purpose tasks to flexible work. More flexibility means more choices, and more choices mean more need for clear owners.
Which rule should we use: consensus, majority or owner-decides?
For operational questions, owner-decides-after-consulting is usually the best default. Consensus can stall a floor that needs an answer by morning, and majority voting is awkward when the group includes people with very different expertise; a vote of three operators should not outweigh a safety engineer’s specific concern. Reserve consensus for rules that bind everyone, such as shift handover practice. State the rule in the same message that names the owner.
Does naming an owner weaken safety culture?
It strengthens it when done carefully. A named owner has a personal reason to ask whether the safety representative has been consulted and whether the rollback path exists. Meanwhile, the right to stop work should remain with every person on the floor, regardless of who owns the wider decision. Writing this down, so that stopping a machine never requires permission, is a separate and important principle, and it works alongside decision ownership rather than against it. Teams planning how their fleets are laid out will find useful background in this broad introduction to automated vehicles in warehouses.
What happens when the owner is off shift?
Name a deputy for every owner, and say so in the same note. Robots do not keep office hours, and a decision that can only be made by someone asleep at home is not really owned by anyone. The deputy follows the same rule and the same boundary, and the handover message at the end of each shift records which decisions are open and who holds them. It is a small habit, but it removes the most common gap in round-the-clock operations.
What should we write down?
- The question, in one sentence.
- The owner and the deadline.
- The rule used and who was consulted.
- The decision and the main reason it was chosen.
- A date to review how it went.
Keep it on a single page near the shift handover notes. Technicians arriving on a new shift can then see at a glance what was decided and why, without having to chase anyone.
How do we handle the vendor?
Treat the vendor as consulted, not as owner, unless a contract says otherwise. Their knowledge of the equipment is valuable, but the operational consequences land on your floor, so the decision should be owned by someone on your side. Agree a response time with the vendor in advance, and note in the decision record when the vendor’s input arrived. This makes disagreements about delays far easier to resolve afterwards.
Is this idea useful outside the warehouse?
Very much so. Think of a family getting ready for a relative’s planned treatment overseas. Dates, paperwork and money all need a keeper, and the household can spend weeks circling until one is named. BestHeartSurgery is a website that presents background on destinations, hospitals and related services to those families, and it makes clear that it is informational and not a treatment provider. Reading is a good first step, and naming a coordinator is the second.
Where should a team start?
Begin with the last time something stopped and people stood around. Ask: who could have decided, and did they know it? Then write a three-line statement for that kind of event, naming the owner, the people to ask and the time limit. Post it where the team gathers. The supervisor in my opening story did exactly that after her long night, and the next time the vehicle stalled at the junction, the answer came in under two minutes. Nobody had to be clever; they only had to know whose call it was.
