What Is Standard Work? Turning Three Ways of Working Into One

Standard work is the one agreed way a repeatable task gets done: the sequence of steps, the decision points inside them, and the result it has to produce. It is not a suggestion and not a document. It is the decision that, out of the three ways your team does this job today, this is the one everybody uses.

What is standard work?

Standard work is the current best known way to do a repeatable task, agreed by the people who actually do it and written down so it can be taught, followed, and improved.

The term comes out of lean manufacturing, where it meant the pace, the sequence, and what had to be on hand to finish without stopping. In a service business it is the same three questions: how long, in what order, and with what in front of you.

The word "current" is carrying weight there. Standard work is not permanent and not perfect. It is the best version anyone in the building can demonstrate today, held in place until somebody proves a better one.

Standard work vs an SOP: the difference in one sentence

Standard work is the agreement; the SOP is the paperwork that records the agreement.

You can have an SOP with no standard behind it, and that is what we walk into most often: a procedure written by someone who does not do the job, while three people carry on doing it three ways. If the vocabulary is the sticking point, settle the difference between a process, a procedure, and a policy first.

The distinction gets practical when you decide what to write and where.

That last row is why the layers stay separate. One residential cleaning COO had her process docs, training, and software how-tos in a single document, so every time the vendor moved a button the whole thing went stale. Keeping the click by click layer in a separate work instruction means a screen change costs one page, not your standard.

Three people, three versions, and nobody knows

The clearest example came from a nonprofit's largest department, at the retro after a wave of SOP work. Because every member of the team was interviewed, not just the lead, people heard colleagues describe the same process out loud for the first time. "I did not really know that you were doing that" is the line that triggered the group agreeing on one documented way.

Nobody was hiding anything. They had each been taught by a different person at a different time.

Variation does not announce itself, because everybody involved believes they are doing it the normal way.

The cost stays invisible until somebody stands inside the process. One owner covered payables himself for a few weeks after a key employee left and found 500 to 800 dollars leaking every week from skipped audits and missed deductions. Up to 10,000 dollars a month, just because the process was not followed, which makes it a system problem rather than a people problem.

How do you set the standard when everyone does it differently?

You do not put it to a vote. Watch the versions being run, pick the one carrying the most volume, and let the people running the others tune it. Negotiating from scratch with the whole team buys three months of meetings and a document nobody owns.

1. Zoom out first. Map the business at about 1.5x, enough to see the departments and the handoffs, then go deep one area at a time.
2. Follow the volume. Start with the market or department carrying most of the work. The version that survives the highest volume is already stress tested.
3. Pick one person. Not a committee. Score candidates on whether they want in, will schedule the time, and set a good example. Title does not equal fit: pick the galvanizer.
4. Race to 80 percent. One expert and one facilitator get a draft most of the way there quickly. Perfection at this stage costs weeks and buys nothing.
5. Capture the decision points. Get the purpose, the judgment calls, and the step by step from the person doing the work. Forks are where undocumented processes break.

When two versions both work, the one carrying the most volume becomes the standard. The peer group then tears that draft apart, which is the point: the people who tune a standard defend it. One group we studied ended up with 20 advocates instead of one author. It helps to know how to run a process mapping session people do not dread before you book that session.

Pick the model, then explain it to the rest

Once the model is set, everyone else gets the standard explained rather than announced. An electrical contractor's board advisor warned that a finished operating system handed down from above lands like Moses coming down from the mountain: here comes the boss again while we are trying to do our day job.

His fix took twenty minutes. Give everybody a sticky pad, ask them to write the behaviors they admire in their best peers, then keep, kill, and combine as a group. The owner still decides, but the team's fingerprints are on it.

Do the same with a standard. Show the other teams the model and change what genuinely breaks in their context. That is the shortest path to getting your team to actually follow the SOPs, because people defend what they helped shape.

Model first has a real cost worth naming. The teams that did not build the standard inherit one shaped by somebody else's context, some of their objections will be correct, and you will spend a round or two amending it. Standardizing is also the wrong move on work that changes every quarter: write down the decision rule there and leave the steps alone.

Make the standard visible where the work happens

A standard that lives in somebody's speech is not a standard. On one call we watched a revenue target per van move from 4,000 to 6,000 mid conversation, with no document anywhere carrying either number. Another company runs on twenty plus group chat threads as its source of truth, so the standard is in there somewhere and nobody can find it twice.

Owners keep asking us how to get people to stop having to remember the process. Stop making memory the mechanism. Put the standard into the tool where the work happens, organized by role, so the next step sits on the screen the person is already looking at.

Standard work is not scripting people

The objection arrives almost every time, usually from the owner: my people are not executives, why would they care about any of this. They do not have to care about systems in the abstract. Simplify one person's process, take the friction out, and the bandwidth to care appears on its own.

There is a deeper point underneath it. Two people can follow the identical SOP, one gets it right every time and the other cannot, and the difference is never in the steps. It is ten or twelve principles running quietly in the good one's head.

Standard work does not take the thinking away from your team, it takes the remembering away.

Standard work standardizes the sequence, not the judgment. That is why the decision points matter: you write down what the right call looks like at each fork, which hands people better judgment instead of removing theirs.

---

The first process to standardize

Pick the one that runs most often and touches the most people, not the one that annoys you most. Assign minutes to every step, multiply by frequency, then by headcount, and the case writes itself. Shave three or four minutes off a task 70 people run daily and it pays for itself in 90 days instead of a year.

Start where things are already close to working, so the first standard is a fast, low risk win. If you cannot tell where the work piles up, find the bottleneck in your business first. At The Systems Effect we interview the people who run the work and turn what they say into the SOPs, maps, and training that hold a standard in place, and the pattern rarely changes: the standard already exists in one person's habits.

Do one thing this week. Ask three people who run the same task to walk you through it separately, and write down every place their accounts diverge. That list is your first standard.

Frequently Asked Questions

What is standard work in simple terms?

Standard work is the one agreed way a repeatable task gets done, including the order of the steps and the judgment calls inside them. It is the decision that one of the ways a job is done today becomes the way everybody uses. It changes when someone proves a better one.

What is the difference between standard work and an SOP?

Standard work is the agreement about how a task will be done; the SOP is the document that records it. You can have an SOP with no standard behind it, which is what happens when someone writes a procedure half the team ignores. A quick test: if two people can both point at the same SOP and still run the job differently, you have a document and no standard.

How do you standardize a process when everyone does it differently?

Do not run a committee to negotiate it. Watch the versions being run, choose the one carrying the most volume, and have one strong practitioner build a draft to roughly 80 percent. Then let the peers running the other versions tear it apart, which turns critics into advocates.

Does standardizing work make employees robots?

No, because standard work standardizes the sequence, not the judgment. The decision points get documented as what a good call looks like at each fork, which gives people better judgment rather than removing it. Simplifying somebody's process is what frees up the attention to care.

Which process should you standardize first?

Start with the process that runs most often and involves the most people, because minutes per step multiplied by frequency and headcount is where the money is. Prefer an area already close to working, so the first standard is a fast, visible win.