I have watched an automation discussion become very precise about distance while remaining vague about work. The proposed robot route is measured carefully. Its expected journeys are counted, and the time per mission receives attention. People who cross that route appear mainly as interruptions to the machine. Their own tasks, waiting and changes of direction are harder to see in the project account, so the apparent precision can hide an incomplete question.
The remedy is not to assume that a longer robot route is better. It is to recognise that the warehouse contains several kinds of movement with legitimate purposes. Replenishment, picking, supervision, maintenance and breaks do not become less important because only one of them produces a machine-generated mission record. I want the investment discussion to explain how these activities fit together and where the proposed arrangement asks one group to carry inconvenience for another.
In our six-robot investigation, four observation days under the original layout and four under a revised route gave us a useful disagreement to examine. Average completed replenishment missions moved from 286 to 274, while the median observed pedestrian wait at the examined crossing moved from twenty-eight to nine seconds. These were selected observations, with the limitations of that design. They did not produce a universal conversion between robot output and human time, but they made a previously neglected consequence discussable.
### Whose movement is visible?
The first version of an automation proposal often inherits the measures that are easiest to obtain from the equipment. That is understandable. A supplier can explain distance, mission completion and operating status with confidence. The warehouse, however, is buying a contribution to its service. The equipment's record is one source of evidence about that contribution, not a complete description of everyone affected by the layout.
I ask the team to walk the proposed area with people who use it for different reasons. A replenishment colleague may notice a queue that does not appear during a quiet demonstration. A supervisor may explain why staff cross at a particular point instead of following the route assumed on the drawing. These observations should inform the design before the team tries to decide whether a reported inconvenience is statistically important. They help identify what needs to be measured in the first place.
This is also a question of language. If every pedestrian encounter is described as an obstacle to robot performance, the account has already chosen its preferred user. I would rather name the two activities and examine their relationship. Sometimes a change in scheduling helps; sometimes the physical route needs to change. The useful answer depends on the workplace and the service requirement, with appropriate specialist review, rather than a general preference for either people or machines.
Performance observations must remain separate from the installation's safety assessment. A reduction in waiting does not demonstrate that a crossing is safe, and a period without an incident cannot settle that question. I expect the responsible specialists to examine the actual arrangement. My role as CTO is to ensure that the investment and design process gives them a clear problem and sufficient opportunity to address it, not to replace their judgement with a favourable throughput chart.
### Give the crossing an owner
Shared space can become nobody's responsibility when the project is divided by equipment package. The robot supplier delivers a functioning system, facilities maintains the building and operations runs the shift. A troublesome crossing sits between those remits. Each team may have met its immediate obligation while the combined arrangement still asks staff to absorb an avoidable difficulty. The project needs an owner for that relationship, with authority to bring the relevant decisions together.
That owner should be able to change the proposal, not merely collect comments. If procurement has already fixed the route and installation date, consultation risks becoming an explanation of why nothing can move. I prefer an early layout review with alternatives still open and the cost of each visible. A longer route might need more equipment or accept fewer missions. Keeping that cost explicit makes the resulting choice more credible than presenting worker involvement as something without consequences.
In our investigation, we accepted the lower observed mission count for the next operating stage. We still had to examine whether the replenishment requirement could be met. The decision did not mean that robot productivity no longer mattered. It meant that a higher count at one point was insufficient justification when the arrangement imposed a waiting burden elsewhere. Operations and engineering needed one account of the resulting work, rather than separate claims of local efficiency.
I would also preserve disagreement after the first layout decision. People learn how a space behaves over time, and a new product mix or staffing pattern can expose a different interaction. A review route should exist for those findings. That does not mean repeatedly reopening every settled choice; it means distinguishing a preference from new operating evidence and giving the latter a practical path to someone who can decide what to do with it.
### A different definition of useful space
Floor space is usually visible as a cost, while room for people to move can look like unused capacity. This can make a tightly packed design appear financially disciplined before its operating demands are understood. I want the account to show why a space exists. A route, waiting area or access point may support work that is easy to overlook when attention rests on the equipment footprint. Its usefulness should be argued through the service, not defended as an unexplained allowance.
The same discipline applies to claims about staff benefit. A shorter observed wait at one crossing is a bounded finding. It does not establish a whole-shift labour saving, a health outcome or a universal improvement in employee experience. People may use the released time in different ways, and other constraints remain. I prefer a modest claim that can guide the next decision to a large benefit statement that detaches the number from the activity actually examined.
For leaders describing automation work publicly, this creates a richer account than a list of machines installed. Explain whose work was affected, which measures were missing, who argued for the original plan and what changed in the decision. The authority in the story comes from recognising competing demands and resolving them responsibly. It does not require the machine to have failed or the final layout to be perfect.
I want a warehouse technology programme to leave behind a workplace that its people can explain. They should know why a route takes the path it does, what service it supports and how to raise a new difficulty. The shortest line on a drawing may still be the right choice, but it should earn that choice within the whole working day. Distance is a useful measurement; it is not, by itself, a definition of good engineering.