The six pillars of operational risk with Flow and Handoff Risk, Pillar 3, highlighted in amber as the focus of the post.

Where Work Goes to Die in a Growing Factory

July 08, 20264 min read

Custom HTML/CSS/JavaScript

It is Tuesday morning. A job left the floor on Friday, everything in order. Now it is sitting on a bench, untouched. Nobody lost it. Nobody refused to pick it up. It crossed a boundary between two people, and that is where it stopped.

That boundary is where work goes to die.

Most managers look at a stalled job and ask a people question. Who dropped this? The honest version is usually different.

Work does not disappear because of bad people. It disappears because the boundary between them has no specification.

In a growing factory, these boundaries multiply. New staff, new shifts, new departments. Each one is a potential gap where undesigned handoffs can stall work, lose information, and quietly erode margin.

This is Flow and Handoff Risk, one of six domains where operational risk builds as a UK manufacturing business grows. It is one of the hardest to see, because it does not live with any one person. It lives in the space between them.

Where Work Actually Disappears

Work does not usually go missing because someone was careless. It disappears at the exact point where responsibility shifts.

The end of a shift and the start of the next. The moment a job leaves the production floor and goes to despatch. The point where a customer query needs to move from the person who took the call to the person who can resolve it.

Every one of those transitions is a potential disappearing point. In a small business, these handoffs are held together by conversation, relationship and habit. People know what to do because they have done it together long enough.

Growth breaks that. Add people, add shifts, add departments, and the informal relationships that held the handoffs together stop scaling. The work still needs to move. The system for moving it has not kept up.

The hardest handoffs to find are the ones that almost always work. Because when they fail, it looks like an exception rather than a gap in the design.

Three Signs You Have a Handoff Problem

These three symptoms tend to appear together. Separately, each can look like a one-off. Together, they point to the same root cause.

Work re-emerges at the wrong stage. A job turns up in despatch that should have gone through an inspection. A customer receives an answer based on information from three weeks ago. The work moved, but it skipped something in transit.

The same clarifications keep travelling upstream. If the same questions come back two or three times on the same job, the handoff specification is incomplete. The person receiving the work does not know what they have been given, so they ask.

Your most experienced people carry the bridges. If the informal system that holds your handoffs together depends on one or two individuals who understand both sides of the boundary, you have a knowledge dependency sitting on top of a process gap.

None of these are signs that your team is underperforming. They are signs that the boundary itself is underdefined.

Why the Fix Is Not a People Fix

The instinct when work stalls at a boundary is to speak to the people around it. That usually produces short-term improvement and medium-term recurrence.

The boundary does not change when the conversation ends. The next person, or the next shift, or the next team, will produce the same stall at the same point.

The fix is in the design of the boundary. What does a complete handoff look like? What information must travel with the work? Who confirms receipt? What triggers the next stage?

When those questions are answered in writing and made visible to everyone who crosses that boundary, the handoff becomes a standard. Standards can be maintained by anyone, not just the people who remember the original conversation.

That is the difference between a process improvement and a people conversation.

Starting to Reduce Flow and Handoff Risk

The starting point is identifying which handoffs in your business are currently held together by habit rather than design.

Walk a job from start to finish. Note every point where it crosses a person, team or shift boundary. For each crossing, ask: is there a written specification for what a complete handoff looks like, or is it assumed?

The gaps you find are where your Flow and Handoff Risk is concentrated.

At Simpleris, the starting point is usually a structured process mapping exercise that makes these boundaries visible, followed by a handoff design for the highest-risk transitions. You can also take the free Operational Risk Assessment below to see how your business scores across all six domains, including Flow and Handoff Risk.

Custom HTML/CSS/JavaScript

Martin Cable is the founder of Simpleris Consultancy. He has spent more than 20 years in UK manufacturing and engineering operations and works with owner-led businesses to reduce operational risk across six domains.

This article is part of the Beyond the Founder series on operational risk in growing UK manufacturing businesses.

Martin Cable

Martin Cable

I help founders of scaling tech and manufacturing SMEs identify and reduce the operational risk that quietly stalls growth. I specialise in turning individual heroics into resilient, predictable systems, so the business depends on how it works, not on who is in the room. My mission is to help leaders build businesses that run with precision, giving them the freedom to lead the future rather than managing the day-to-day.

LinkedIn logo icon
Back to Blog