Your warehouse runs on one person. Everyone pays for it.

Every ANZ ops team has one person who "knows the system."

They know which screens to ignore. Which fields the software overwrites silently. Which report finance actually trusts. Which workaround to use before stocktake.

When they are out, the operation grinds. Stock counts drift. Dispatch slows. Finance reconciles by hand.

They are treated as the star employee. They are not. They are the receipt for what the software cost the business, and so is the team around them.

Indispensable looks like an asset. It is a cage.

Three things happen to the person who becomes the system champion:

They never fully take leave. Their phone rings on Saturday because dispatch missed a manifest. They check email on holiday because the carrier portal is acting up and no one else remembers the workaround. The role does not have an off switch.

They cannot be promoted. Every conversation about moving them up ends the same way: "but who would run the system?" Their job description becomes permanent. Their career ceiling is the platform they were hired to use, not the role they were hired to grow into.

They stop teaching the workarounds. The second they hand off the tribal knowledge, the workaround breaks or someone else gets blamed when it does. So the knowledge stays concentrated. The software rewards them for hoarding it, and the team learns to ask before trying.

It looks like an asset to the business. It feels like a cage to the person inside it.

What it does to the team around them

The team does not get to grow.

New starters stop asking how the system works. The answer is always "ask [name]." They learn the operation by proxy, not by competence. They never own a workflow. They relay one.

Supervisors stop challenging the platform. If only one person can interpret it, the platform's failures get filed under "how the system is." Nobody escalates because the path of least resistance is to keep calling the champion.

Junior ops staff who could become senior do not. Their ceiling is not "operations manager." It is "whoever knows the system better than them." Most of them leave for a role where the platform does not require an interpreter, and they take the institutional memory they were starting to build with them.

That is the culture cost. The business is not just running on one person. It is teaching everyone else not to try.

What it costs the operation

The business pays the rest of the bill.

• Sick day: stock counts drift because the reorder report needs interpretation.
• Annual leave: dispatch slows by a day because no one else can pull the carrier manifest.
• Resignation: three months of process archaeology before the team operates at the same speed again.

Bad software does not just hurt the champion and the team. It quietly puts the whole operation one person away from disruption, and one resignation away from a culture that has to be rebuilt from scratch.

Why ANZ teams cannot absorb this

Enterprise can. They have redundant headcount, a managed-services partner, and a four-week notice period to engineer a handover.

A 30-to-300-staff ANZ operator does not. Every role is load-bearing. The champion is also the ops manager. The ops manager is also doing supplier calls, audit prep, and Friday afternoon stocktake. There is no second person ready to learn the system, because the system was not built to be learned twice, and there is no one with the spare hours to be the second.

What software is supposed to do

Software's job is to remove the need for a champion.

• Each role sees the screens that match their work: pickers see picks, packers see packs, supervisors see exceptions, finance sees what they need to invoice against.
• Workflow is visible to the team that runs it. Handoffs are obvious. The next action is on the screen, not in someone else's head.
• Exceptions are surfaced, not hunted.
• The operator's notebook of tribal knowledge becomes redundant.

When that happens, the team operates without translation. The champion gets to stop being one. New starters get a path to grow into. The business stops paying twice: once in salary, once in the team it failed to develop.

How to spot champion-dependence in your culture

Seven questions worth answering honestly:

• Who do you call when stock counts are wrong on Friday at 4pm?
• Can a new starter pick orders in week one without a buddy?
• If your senior ops person took a two-week holiday tomorrow, would dispatch slow down?
• Is there a workflow your team does not run unless one specific person is in the office?
• Does the same person also build the side-spreadsheets the team actually uses?
• Does your team default to "ask [name]" instead of trying the system first?
• Has anyone left in the last year because they could not see a path to grow into a senior ops role?

More than two yes answers is a system signal, not a staffing strength.

Where OpsUI fits

OpsUI is built so the team does not need a translator. Role-scoped screens. Clear handoffs. Exceptions on the page. Pricing on the page.

The point is not to demote the champion. It is to free them: to do the work that does require a human, and to let everyone else grow into the work that does not.

If your operation runs on one person, the cost is not on the org chart. It is on the platform, and it is on the team you keep losing because the platform never let them become senior.