Operations · Long-form essay
The Work Between the Work
How work actually moves through an organization — and what happens in the spaces between.
Sometimes the official process looks linear.The real path rarely is.
A request comes in.
Someone reviews it.
A decision is made.
The work moves forward.
The outcome is delivered.
At least, that is how the process may appear on paper.
Follow the same piece of work through the organization, however, and another story often emerges.
Someone has to clarify what was meant.
Someone realizes information is missing.
A decision waits because ownership is unclear.
A conversation happens outside the system.
A person remembers something the process does not.
Work moves backward before it can move forward.
A handoff requires interpretation.
Someone follows up.
Someone checks.
Someone quietly connects two pieces that were never fully connected by design.
None of this may appear on the process map. Yet it is often where operations actually happens.
Operations is not simply the work being done. It is everything that allows the work to move.
Operations is more than efficiency
Operations is often described through efficiency, productivity, processes, systems and optimization. All of those matter. But they are not the whole story.
Operations is the architecture through which intention becomes coordinated action.
It is how information travels.
How decisions are made.
How responsibilities connect.
How priorities become work.
How one person’s output becomes another person’s input.
How exceptions are handled.
How knowledge survives beyond the person who currently holds it.
And how people know what to do when reality does not follow the procedure.
A process can look efficient on paper and still be exhausting to navigate. A sophisticated tool can exist while critical information continues to travel through memory. Roles can be documented while ownership remains ambiguous. A workflow can technically function while depending on one person to continually keep it functioning.
Operational health cannot be understood only by asking, “Is the work getting done?”
We also need to ask: What does it take for the work to get done?
The work between the work
Every visible step contains spaces around it.
Handoffs.
Dependencies.
Decisions.
Waiting.
Clarification.
Interpretation.
Coordination.
Exceptions.
These spaces are easy to overlook because they rarely belong neatly to one task or one person. Yet friction often accumulates there.
A task may take fifteen minutes to complete but wait three days for a decision. A form may take five minutes to process but require four conversations to obtain the right information. Two teams may each perform their responsibilities efficiently while the handoff between them repeatedly fails. A system may automate a step while leaving the ambiguity surrounding that step untouched.
When we focus only on individual tasks, these problems can remain invisible. Everyone appears busy. The work eventually gets done. The organization continues functioning.
But underneath that apparent functionality, people may be spending enormous amounts of energy simply helping work find its way through the system.
That is the work between the work.
When people become the process
Over more than 25 years working inside operations, one pattern I have seen repeatedly is that capable people compensate.
They remember.
They remind.
They follow up.
They translate.
They anticipate.
They reconcile conflicting information.
They know which person to ask.
They know which exception is normal.
They know what the procedure says — and what actually has to happen.
Often, these behaviours are interpreted as commitment, experience or simply being good at the job. Frequently they are. But they can also conceal something important.
When a process depends on someone remembering, chasing, translating or rescuing, part of the process is living inside a person.
That creates operational vulnerability. If that person is away, work slows. If they leave, knowledge leaves with them. If demand increases, their invisible workload increases with it. If the organization redesigns the process without understanding what that person has quietly been compensating for, the new process may reproduce the same problem in a different form.
This does not mean every informal action is a failure. Human judgment will always matter. Healthy operations should leave room for judgment, adaptation and discretion.
The question is whether people are using judgment within a functioning system or continually compensating for what the system has failed to provide.
Those are very different conditions.
Efficiency is not the same as flow
We often try to improve operations by making individual activities faster.
Reduce the number of clicks.
Automate the task.
Shorten the meeting.
Create the template.
Add the software.
Remove a step.
Sometimes that is exactly what is needed. But a faster task does not necessarily create better flow.
Imagine five steps in a process. Step one takes less time. Step two is automated. Step three has a new template. Step four has a dashboard. Step five has an AI assistant.
Yet between those steps, people are still waiting for decisions, interpreting unclear expectations, searching for context and correcting information that did not travel with the work.
Every individual step may have become more efficient. The journey has not.
Efficiency asks how quickly a task can be completed. Flow asks what the work encounters on its way through the organization.
Operations does not happen inside isolated tasks. It happens across the journey.
Technology can accelerate clarity — or confusion
Technology can improve that journey enormously. Automation can remove repetitive work. AI can support analysis, drafting and information retrieval. Shared systems can create visibility. Workflow tools can strengthen ownership and coordination.
But technology does not automatically resolve operational ambiguity.
Automating an unclear process can make confusion travel faster. Another communication channel can increase access while fragmenting context. A dashboard can create visibility without creating ownership. AI can accelerate output without answering whether the work should be done that way in the first place.
The question is not simply, “What can we automate?”
What are we trying to make easier, clearer or more reliable — and for whom?
Tools work best when they support an understood system rather than compensate for one that has never been fully examined.
What silence can tell us about operations
This is where Silenciology™ becomes useful operationally.
Not every broken process generates a complaint. People adapt.
They create workarounds.
They stop questioning an unnecessary step because “that’s how it has always been done.”
They maintain private spreadsheets.
They develop unofficial communication channels.
They learn who really makes the decision.
They stop documenting an issue because previous attempts changed nothing.
They quietly absorb extra work because explaining the problem feels harder than solving it themselves.
Eventually, the workaround becomes normal. And because the work still gets done, the organization may never recognize the workaround as information.
But it is information.
A workaround is often a clue.
It may point toward unclear ownership, missing context, a broken handoff, a decision bottleneck, an unrealistic expectation, or a process that exists on paper but not in practice.
Silenciology™ asks us not to judge these behaviours too quickly, but to become curious about what they may be revealing.
People · Process · Purpose are present in every workflow
Operations may appear to belong primarily to Process, but no process exists independently of People or Purpose.
People bring judgment, knowledge, relationships and experience to the work.
Process provides the pathways, responsibilities and rhythms through which that work moves.
Purpose helps determine why the work exists, what matters and which outcomes deserve attention.
When one becomes disconnected from the others, operations begins to compensate.
A process designed without enough regard for People may technically function while exhausting those using it. People working without sufficient Process may become highly capable improvisers while the organization grows increasingly dependent on individual memory and effort. Process without clear Purpose can make an organization extremely efficient at completing work that no longer creates enough value.
Operational alignment is therefore not simply about making Process better. It is about designing the conditions in which People, Process and Purpose can work together.
The real process is the one people actually use
One of the most revealing things an organization can do is follow a single piece of work from beginning to end.
Not through the SOP.
Not through the policy.
Not through the workflow someone believes exists.
Follow the actual work.
Where does it begin?
Who touches it?
Where does information come from?
Where does it wait?
Where does someone have to ask?
Where does it travel backward?
Where is a decision required?
Where does context disappear?
Where does someone step in to prevent something from dropping?
Where does work leave the official system and enter email, chat, a notebook, a spreadsheet or someone’s memory?
And perhaps most importantly:
Where is the system relying on human effort that nobody has recognized as part of the process?
The purpose of looking this closely is not to eliminate every detour. Real organizations are human systems. There will always be exceptions, judgment, relationships and adaptation.
The goal is not perfect linearity. The goal is to understand what the work is asking of the organization — and of the people carrying it.
To understand the system, follow the work
Healthy operations does not mean everything moves faster.
Sometimes the healthiest change is removing a step.
Sometimes it is clarifying a decision.
Sometimes it is slowing something down.
Sometimes it is giving someone greater authority.
Sometimes it is documenting knowledge.
Sometimes it is connecting two people who have been working around one another.
Sometimes it is asking why the work exists at all.
And sometimes the first improvement is simply seeing what is already happening.
Because the process an organization describes and the process its people experience are not always the same.
The space between them is worth paying attention to.
That is often where friction lives.
Where invisible effort accumulates.
Where people compensate.
Where valuable information remains unspoken.
And where some of the most meaningful opportunities for operational improvement can be found.
To understand the system, follow the work.