Who owns workflows.
Most workflow problems are not design problems. They are ownership problems. A well-designed workflow with no owner degrades inside a few months. This lesson defines the four ownership roles every workflow needs, who in your business should fill each one, and the failure mode that appears when any of them is missing.
The four roles every workflow needs.
The sponsor. The person at the executive level who cares whether the workflow works. They do not run it. They decide that it matters, fund the work to build it, and remove blockers when something needs to change.
The designer. The person who maps the workflow, names the stages, defines the handoffs, and writes the version that the business actually uses. The designer revises it when something is not working.
The operators. The people who run individual stages. They execute the work. They are not the designers and they are not expected to be.
The maintainer. The person accountable for keeping the workflow current as the business changes. They review it, update it, and retire it when it stops fitting.
One person can hold more than one role. The mistake is assuming the roles do not exist. Every workflow has them, whether or not you have assigned them.
The MD's role.
The MD is almost always the sponsor. They decide that the workflow is worth building. They allocate budget and time to the work. They back the COO or the designer when the workflow requires the team to change how they work.
The MD is not the designer and they are not the operator. When the MD is also the operator, the workflow has not been built yet. It is still in the MD's head, and the business cannot run it without them.
The most useful thing an MD can do for a workflow is sponsor it clearly, then stay out of the design and execution. The second most useful thing is to refuse to be the operator. If you keep being pulled into a stage, that is a signal the ownership is not yet assigned, not a reason to keep stepping in.
The COO or Ops Director's role.
The COO is usually the designer and the maintainer. They are accountable for whether workflows exist, whether they are being followed, and whether they still fit the business. They are the senior person closest to how the work actually flows.
If the business does not have a COO or equivalent, this role defaults to the MD, and that is one of the most common reasons workflows never get built. The MD does not have time to design them, so they stay informal, and the business pays the cost.
In businesses without a dedicated COO, the design role can be temporarily filled by an external partner or an internal senior hire. The maintainer role cannot. Someone inside the business has to own keeping the workflows current. Otherwise they age out and the operation drifts back to where it started.
The team's role.
Operators execute stages. They are not designers, and they should not be asked to be. The most common ownership failure in operations is asking the team to design their own workflow alongside doing the work. They will optimise for their own stage, not the system. The result is a workflow that runs well at each stage and fails at every handoff.
Operators are essential to the design process as input. They know what actually happens, where the work gets stuck, which steps everyone quietly skips, and what the unwritten rules are. The designer's job is to extract that knowledge and shape it into a workflow the team can run. The team's job is to give honest input and then run the result.
Treat the team as the source of truth for current state, and as the testers of any new version. Do not treat them as the people responsible for the design.
The four failure modes.
No sponsor. The workflow exists on paper, but no one at the executive level cares whether it is followed. It gets ignored the first time someone is busy, and it never recovers.
No designer. The workflow drifts. Stages move around informally. Different team members do the same step differently. Nobody is accountable for writing down the current version, so there is no current version.
No operators. Stages exist but ownership is unclear. Work stalls because everyone assumes someone else has it. The workflow looks fine on paper and runs poorly in practice.
No maintainer. The workflow is built and runs well for six months, then stops fitting the business. New product, new client type, new system. The workflow does not update. It ages, and the operation works around it instead of through it.
Before building a workflow, name who is filling each of these roles. If you cannot, build the role first.