When to formalise a workflow.
Not every piece of work needs a workflow. Building one too early wastes effort and locks in the wrong shape. Leaving it too late costs money and quietly limits the size of the business. This lesson covers the four signals that a piece of work is ready to be formalised, the three signals that it is not, and what ready to formalise actually looks like in practice.
Signal one. Volume has crossed a threshold.
A piece of work that happens once a month can live in someone's head. A piece of work that happens five times a week cannot. When frequency increases to the point where the work is happening in parallel rather than in sequence, the workflow needs to exist outside any single person.
The threshold is different for different kinds of work, but the pattern is consistent. Two or three things in flight at once is the moment informal coordination stops working. People lose track. Status gets reconstructed by asking. Things slip because nobody can hold the full picture in mind.
If you are starting to hear the phrase, what is the status of, more than once a week for the same kind of work, the volume has crossed the threshold.
Signal two. The same error keeps happening.
If the same mistake keeps recurring, it is not a people problem. It is a missing step problem. The work expects the operator to remember something that is not written down, or to spot something that is not obvious, and people do not remember or notice the same things consistently.
Formalising the workflow makes the step explicit so it cannot be skipped. The error rate drops, not because the team got better, but because the workflow stopped relying on memory to prevent the mistake.
When you find yourself having the same conversation with the team for the third time, the workflow needs the step that conversation keeps adding.
Signal three. The team is scaling.
Adding the third or fifth person who runs the same kind of work without formalising it guarantees inconsistency. Each new hire learns from whoever happens to train them, and inherits that person's idiosyncrasies. Six months in, you have three or five subtly different versions of the same work and no way to standardise.
Formalise before you scale. The right moment is when you can see the next hire coming, not when they have already started. The workflow is the training document. It is how the new person becomes productive in weeks rather than months.
If you are about to hire someone whose job description is functionally identical to someone already in the team, that is the signal.
Signal four. There is a single point of failure.
If the work cannot happen when one specific person is on leave, the workflow does not exist. The work has been encapsulated in that person. They are the workflow.
Formalising it is how you de-risk the business. The risk is not just that the person leaves. It is that they are unavailable for two weeks and the business slows down measurably during that time. Holiday cover becomes a crisis, sick leave becomes a backlog.
For any piece of work where one person being unavailable causes the work to stop, the workflow needs to be extracted from them and written down. This is the formalisation that has the biggest immediate effect on operational resilience.
When not to formalise.
There are three cases where building a workflow is the wrong call.
The work is one-off. If you have done this kind of thing once, formalising it is premature. You do not know what the variation looks like yet. Formalise the second time you do it, or the third if you can afford to wait.
The volume is genuinely low. If the work happens twice a quarter and runs smoothly when it does, the cost of building a workflow can exceed the cost of continuing to do it informally. Reassess if frequency changes.
The underlying activity is still being figured out. If you are not sure yet what good looks like for this work, formalising it locks in the wrong answer. Wait until the team broadly agrees on the shape before writing it down.
The honest version of this is that most businesses err in the other direction. They wait too long, not too little.
What ready to formalise looks like.
Four conditions, all true at once.
The work has run enough times that the variation is understood. You know what the common path looks like and you know the main exceptions.
The team broadly agrees on what good looks like for each stage. Not perfectly, but enough that you can write it down without immediately having to argue about it.
There is at least one person who has the institutional knowledge that needs to be captured. The workflow exists in their head, even if it does not exist anywhere else.
The cost of not having a workflow is measurable, not theoretical. You can name a specific time it caused a problem, a specific bottleneck it creates each week, or a specific hire whose productivity it will affect.
If all four are true, formalise. If three are true, get the fourth, then formalise. If fewer than three are true, wait, and watch.