Walk into a company that's a couple of years into EOS and you'll usually find a lot going right. There's an Accountability Chart on the wall, Rocks get set every quarter, and the Level 10 Meeting starts on time. Then you ask about the EOS Process Component, and the room goes quiet. Somebody points at a shared drive. Somebody else admits that three of the core processes are "basically documented." This is where an otherwise healthy company stalls, and it stalls in almost exactly the same spot every time.
I've watched it happen in more businesses than I can count. The Process Component isn't hard because leaders are lazy or don't get it. It's hard because of what it actually asks for, and because almost nobody in the building owns the part that matters most.
The EOS Process Component has two halves, and teams forget one
The requirement reads simple: identify your handful of core processes, then get them Documented and Followed By All. Two conditions joined by a small word. Most teams treat that "and" like a rounding error. They pour their effort into the first condition and almost none into the second.
Documenting feels like progress. You can schedule it, assign it, and check a box the moment a file exists. Following is messier. It means a person who's done the job their own way for six years now does it the agreed way, on a busy Tuesday, when nobody's watching. A saved document doesn't make that happen. Documentation stores knowledge. It doesn't transfer it.
A library full of books doesn't teach anyone to read. A shared drive full of processes doesn't teach anyone how the work is really done.
Documented is the starting line, not the finish
Here's the trap. The day the last process gets written up, it feels like the Process Component is done. The box goes green in your V/TO. But writing the process and running on the process are two entirely different achievements, and the gap between them is where most of the value hides.
A binder full of accurate procedures that nobody opens changes nothing about how your company actually operates. You've spent real hours producing a record of how the work should go, and your Tuesday still looks exactly like it did before. The document isn't the result. Behavior is the result.
Nobody actually owns the follow-through
This is the structural piece almost everyone misses. In a typical rollout, "get the processes documented" gets assigned to someone with a due date. "Get the processes followed" gets assigned to no one. It drifts between the Integrator, the department heads, and whoever wrote the doc, which means it belongs to everybody, and a job that belongs to everybody belongs to nobody.
Compare that to any part of your business that works. It has an owner, a number, and a rhythm. Follow-through on your core processes usually has none of those. So it doesn't happen, not because your people are difficult, but because you never actually gave the work a home.
It's a process problem, not a people problem
When the agreed way isn't getting followed, the reflex is to look for who to blame. Resist it. W. Edwards Deming spent a career studying why organizations fail to perform and landed on a number worth memorizing: roughly 80 percent of the time, when something goes wrong, the root cause is the process, not the person.
That flips the whole exercise. If a process isn't being followed, the useful question isn't "who's ignoring this?" It's "why is the right way harder to follow than the old way?" Maybe it lives two logins deep. Maybe it's three pages of text nobody reads under pressure. Maybe it was never really taught, just posted. Fix the system and the behavior follows. Blame the people and you'll be having the same conversation next quarter.
I saw this with a client whose new intake process kept getting skipped. The owner was ready to start writing people up. It turned out the form lived on a system half the team couldn't reach from the floor, so following it meant walking to a desk. We moved it to their phones, and adoption went from a weekly fight to a non-event inside a week. Same people. Different system. That's Deming's point made physical.
How to actually get to Followed By All
Closing the gap is less about better documents and more about transfer. A few things move the needle:
- Give each core process a single owner who's accountable for adoption, not just for the doc existing.
- Make the process short and visual. A ninety-second video of your best person doing the work beats three pages nobody reads.
- Put it where the work happens, so people can pull it up in the moment they need it instead of studying it in advance.
- Pick one number the process is supposed to move, and watch whether it moves.
That last point is the tell. If following the process doesn't change a number you care about, either you're measuring the wrong thing or the process wasn't worth documenting. Both are useful to find out.
If your Process Component has been stuck on "documented" for a while, the fix isn't more writing. Our Process page is a good place to see how to organize the handful of processes that matter, and PlaybookBuilder was built to handle the second half, turning a documented process into one that's genuinely followed. If you want a specific person made accountable for that transfer, that's what a certified process owner does. Start there, and the box goes green for real.
Jon LoDuca
founder
PlaybookBuilder
