Sample frameDay 336·Operations · Standards

Everyone on your team already knows how to do it. That isn't the same as everyone doing it the same way.

Operations.

Standard Work

5 min read·Apply by lunch

The question

Take the process your business runs most often — the onboarding, the client handover, the monthly close — and ask whether two of your people, working it on the same day, would produce the same thing in the same order. If the honest answer is no, you haven't got a process; you've got several, and you're paying to run all of them.

The idea

In complex work, most failure isn't ignorance. It's the unreliable application of what everybody already knows, which is why the fix is usually duller than the problem. Peter Pronovost, a critical care physician at Johns Hopkins, wrote down five steps for putting a line into a patient's chest: wash your hands, clean the skin with chlorhexidine, drape the patient fully and gown up, avoid the femoral site where you can, and pull the line the moment it isn't needed. Every doctor already knew all five, which is precisely why nobody had written them down. Rolled out across intensive care units in Michigan, the results published in the New England Journal of Medicine in 2006 showed the median rate of catheter-related bloodstream infection falling from 2.7 per thousand catheter-days to zero within three months, and holding there eighteen months on. Atul Gawande built The Checklist Manifesto (2009) on the same evidence. The trap is hearing 'write it down' as bureaucracy: standard work isn't a binder and it isn't a rulebook, it's a short, dull, checkable statement of the current best-known way of running one step. And that is what makes it your baseline for method — without it, a team that gets better can't tell you whether the way the work is done actually changed, or the month was simply easier.

The framework

01
The list is written by the people who do the work, not for them.
A standard handed down from a manager describes how the work is imagined; a standard written by the three people who actually run the step describes how it's done. Only one of those is a baseline. Put the people who do the job in a room, have them walk the step aloud, and write what they say — including the two workarounds nobody has ever mentioned to you. You'll find they disagree on at least one thing, and that disagreement is the whole point: the argument about which way is better is the first improvement the exercise buys you.
02
Read-do, or do-confirm?
Gawande borrowed the distinction from aviation, where checklists have been designed with care ever since a Boeing prototype crashed in 1935 and the response was a list rather than more training. A read-do list is worked line by line as you go, which suits rare, high-stakes sequences nobody performs often enough to remember. A do-confirm list is worked at a pause point after the task, checking the known steps happened, which suits frequent work. Choosing the wrong type is why most standards get ignored: nobody will read lines aloud for something they do six times a day.
03
The killer items, and nothing else.
The instinct once you start writing is to capture everything, and a standard that captures everything gets used by nobody. Pronovost's list had five items. Aviation checklists run to a handful of lines per phase of flight. Keep only the steps that are both easy to miss under pressure and expensive when missed — the killer items — and let the rest live in training or in a longer reference nobody consults mid-task. If it doesn't fit on one page you've written a manual, and manuals sit in drawers.
04
Date the standard, and expect it to be beaten by the end of the quarter.
Standard work is explicitly the current best-known way, which means it carries a date and an owner and is written to be replaced. Without one there's no baseline for method: a team with no standard that gets faster can't tell you whether anybody changed how the work is done. So put the date at the top, name the person who holds it, and treat every improvement as a rewrite rather than a memo. A standard nobody has revised in a year is either perfect or ignored, and it isn't perfect.

Members only · 4 principles + template + AI mentor

364 more frameworks are waiting.

Standard Work is Day 1 of 365. One framework every morning for a year — across strategy, sales, negotiation, leadership, and more.

$1 /day

Billed $365/yr · cancel any time

365 frameworks

12 topics · templates · AI mentor

Reserve your place — $365/yr →

One payment a year · the whole library · no auto-renewal.

More Operations frameworks

All 24 operations frameworks →