A Procedure Nobody Can Find Might as Well Not Exist

A correct procedure that's hard to reach gets ignored just as often as a bad one. Here's how to put instructions where the work actually happens, and why linking beats copying every time.

A business owner spends a weekend building a beautiful, detailed guide to how her team handles a recurring, complicated task: every step, every judgment call, every exception, organized and easy to follow. She's proud of it, and she should be. Then she saves it in a personal folder on her own computer, because it's valuable and she doesn't want it edited by accident. The team member covering that task while she's out doesn't dig through her computer to find it. She guesses, based on what she remembers, and gets it close enough most days. The guide is excellent. It is also completely disconnected from the one place it needed to be: open on the covering team member's screen, in the middle of the actual work.

This is the failure mode that swallows more good procedures than bad writing ever does. The instructions are correct. The instructions are also nowhere near the work, and a procedure that isn't near the work might as well not exist, because nobody interrupts what they're doing to go hunt one down.

The solution sounds almost too simple to be real, and it's still the one that matters most: put the procedure where the work already happens. Concretely, that means connecting each procedure to the specific task it supports, so whenever someone is assigned that task, the procedure shows up with it instead of waiting somewhere to be found.

For a business running jobs through a scheduling tool, that's a link to the onboarding procedure sitting right inside the task the moment it's created, not buried in a personal folder three levels deep. For a team that still tracks its work on paper, it's a printed checklist clipped to the file, not a binder in a back office. For a small office that closes out deposits every week, it's the procedure sitting in the same drawer as the deposit slips, not in a policy folder nobody opens between closings. None of this requires new technology. It requires moving the instruction six feet closer to the person who needs it.

There's a related question that comes up almost every time someone starts connecting procedures to tasks this way: why not paste the whole procedure directly into the task itself, so nothing needs a click? It feels more convenient, and for a single task, it is. The problem shows up the first time the procedure changes.

Say a business onboards two hundred new clients a year, and each one gets its own copy of the procedure pasted directly into the task. The day a step in the process changes, or the company adjusts its pricing structure, someone has to track down every copy still in progress and update it by hand, or accept that half the team is working from an outdated version and doesn't know it. Multiply that across every procedure the business runs, and the result is a slow-motion mess: dozens of near-identical copies, quietly drifting apart from each other, none of them fully trustworthy anymore.

Link to the procedure instead of copying it in, and there's exactly one version, ever. Update it once, and every job that references it, past, present, and future, points at the current version automatically. It costs the person doing the work one extra click to open a link instead of reading text already in front of them. That small bit of friction is worth trading for never again wondering which copy is the real one.

This is also where the trust problem from a couple of posts back quietly resolves itself. A procedure that's one click away, and current because there's only one copy of it anywhere, stops being something people write off as outdated, since keeping it current no longer means chasing down copies scattered across two hundred old work orders. Proximity and trust turn out to be the same fix wearing two different names.

One more piece of scoping matters here, about the task that carries a procedure rather than the procedure's own steps. When you connect a procedure to a task, size that task to roughly one work session for one person, somewhere in the twenty-to-ninety-minute range most people can hold focus for. A big, multi-day job like preparing a full client proposal shouldn't live as a single task with one procedure attached. Break it into the pieces that actually happen in separate sittings, initial research, drafting, client walkthrough, and give each of those its own task, linked to whichever procedure covers that specific piece. This is the last post's advice about step sizing, applied one level up, to the tasks that carry the procedures around.

None of this requires new software or throwing out whatever system already runs your team's day. It requires treating a procedure as a fixture that lives exactly where the work happens: updated in place, referenced instead of duplicated, and close enough that using it costs less effort than skipping it. Get that part right, and the procedures that survive contact with a real Tuesday are the ones nobody had to think twice about opening.