Everything Has an Operation

Not just factories.

Whenever work moves from a beginning to an end, an operation exists.

When people hear the word operations, they often picture factories, warehouses, conveyor belts, and production lines. Those are certainly operations. They are not the only ones.

An operation exists whenever work moves through a series of steps to produce an outcome. It does not matter whether the final result is a physical product, a service, a decision, or an experience.

Operations are everywhere

A hospital admitting a patient has an operation. A restaurant serving dinner has an operation. A university processing applications has an operation. An airline boarding passengers has an operation.

A government issuing passports has an operation. A software company releasing an update has an operation. A farm harvesting vegetables has an operation. A theatre preparing for opening night has an operation.

Even a family getting children ready for school every morning follows an operation. Different outcomes. The same underlying idea.

Watching the same structure repeat: three completely different operations

A restaurant's dinner service has an entry point the same way every operation does: an order lands the moment a server keys it in.

From there it moves through defined ownership. The kitchen takes ownership of production. The expediter takes ownership of coordinating dishes that have to arrive at the table together. The server takes ownership of delivery. Nobody performs someone else's step, and every handoff is a moment where responsibility formally changes hands.

Decisions get made constantly and at specific points: which order fires first, whether a dish is ready to leave the pass, when a table's meal is officially complete. None of that is improvised in a functioning kitchen — it's the same execution logic as any other operation, just moving at high speed.

Completion is recognized clearly too: a plate served, a table cleared, a check settled. The meal is the product. Getting it there and knowing when it's done is the operation.

A theatre preparing for opening night runs on the same underlying shape, over a much longer timescale.

Work enters the moment a script is chosen and a production date is set. From there it moves through sequential ownership: the director owns interpretation, the designers own the physical world of the production, the stage manager owns coordinating everyone once rehearsals begin, the cast owns performance.

Decisions accumulate along the way — blocking choices, technical cues, when a scene is "done" in rehearsal versus ready for an audience — each one made by whoever currently owns that part of the process. A missed handoff here doesn't cause a delayed order. It threatens an entire performance in front of a paying audience on a fixed date that cannot move.

Completion is unambiguous: the curtain rises on opening night, and everything that happened before that moment was the operation getting the work there.

A family getting children out the door for school runs the identical structure at a much smaller scale, with no title attached to any of it.

Work enters the moment an alarm goes off. Ownership still exists, even though nobody calls it that — one parent owns breakfast, another owns making sure backpacks and permission slips are actually in the bag, a child owns getting dressed. Handoffs happen constantly: whoever finishes first checks on whoever's behind.

Decisions get made in real time — is there enough time for cereal or does it have to be something eaten in the car, does a forgotten library book get retrieved or left behind. Completion is recognized the moment everyone is out the door and the car pulls away on schedule.

None of these three examples share an industry, a product, or a customer. All three share the exact same operational bones: an entry point, defined ownership, decisions made at specific junctures, and a recognizable moment of completion. That repetition is the actual argument — the structure is the same whether the outcome is a dinner, a performance, or a functioning morning.

The output changes. The structure does not.

One organisation produces bread. Another produces software. Another produces medical care. Another produces legal decisions. Another produces live performances.

Although the work itself is completely different, every operation still has work entering the system, moving through a sequence of activities, and eventually reaching some form of completion.

The subject changes. The operational challenge remains remarkably similar.

Every operation answers the same questions

Where does the work begin? Who owns the first step? What information must travel with it? Where are decisions made? How does responsibility move between people? What happens when something unexpected occurs? How do we know the work is finished?

These questions exist whether the operation builds aircraft or schedules medical appointments.

Operations connect people

Very little work is completed entirely by one person. Information moves. Materials move. Requests move. Responsibility moves. Every movement creates a relationship between one step and the next.

The operation is the structure that holds those relationships together.

Invisible operations are still operations

Some operations are easy to see. You can watch products moving along a production line. Others exist almost entirely through information. Nothing physical travels, but the work still moves through the exact same structure.

A customer support ticket shows this clearly. Work enters the moment a customer submits a complaint or a question — no product changes hands, nothing gets shipped, but a piece of work has entered a system all the same.

Ownership moves from there just as concretely as it would on a factory floor. A first-line agent owns triage, deciding whether the issue is simple enough to resolve immediately or needs to go further. If it escalates, a specialist owns investigation — pulling account history, reproducing an error, checking what actually happened. If a fix requires a policy exception or a refund, someone else owns that approval.

Decisions get made at each of those junctures the same way they do anywhere else: is this ticket resolved or does it need escalation, is the proposed fix acceptable, is the customer's issue actually the one they originally described or something different underneath it.

Completion is recognized clearly too — a resolution is logged, the customer confirms the issue is fixed, or a fixed number of days pass with no further reply and the ticket closes on its own.

An insurance claim and a planning application follow the identical shape: a submission enters, ownership passes between reviewers and specialists, decisions accumulate at defined points, and completion is marked the moment an approval, denial, or payout is issued.

Nothing physical ever moved in any of these. The operation was just as real as the one on the factory floor — it just left no visible trail of boxes or conveyor belts behind it.

Operations are about movement, not industry

It is easy to think operations belong only to manufacturing because factories make the movement of work visible. But every organisation has work that must be received, understood, coordinated, completed, and delivered.

The operation is simply the path that work follows while that happens. Whether the final result is a meal, a passport, a diagnosis, a parcel, a concert, a lesson, or a software release makes surprisingly little difference. The work still has to move.

Seeing operations changes how you see organisations

Once you begin recognising operations, they become difficult to ignore. You stop seeing isolated tasks. You begin seeing connected systems.

You notice where work enters, where it waits, where responsibility changes hands, where decisions are made, and where the entire flow depends on one critical step.

The organisation has not changed. Only the way you understand it has.