Every EOS® team hits a moment where they check the Process box and feel good about it. The core processes are named, they're written down, they live in a shared drive, and everyone at the table nods. Six weeks later the business runs exactly the way it always did. That gap has a name inside EOS, and it's the half almost nobody finishes: Followed By All.
The uncomfortable part is this. Documented is not the finish line. It feels like the finish line because it's the part you can see, cross off, and hold up in a Level 10 Meeting. But a document sitting in a folder has never once changed how a single person does their job. Adoption is the point. If the number you cared about didn't move, the process didn't take, no matter how clean the write-up looks.
I've watched leadership teams spend a full quarter documenting every core process, celebrate at the offsite, and run the exact same business in January that they ran in September. The binder was thicker. Nothing else was different. That's the trap, and it snares disciplined teams more often than lazy ones, because disciplined teams are the ones who actually finish the documentation and mistake it for the goal.
Followed By All is a different job than documented
Writing a process and getting a process adopted are two separate skills, and most teams only staff the first one. Someone sits down, captures the steps, formats it nicely, and calls it done. Then they're genuinely surprised when the team keeps working the old way. They shouldn't be. Nobody got trained. Nobody reinforced anything. Nobody checked. The write-up was an artifact, not a change in behavior.
The behavior change is the whole game. It's the part where the person who does the work actually does it the agreed-on way, on a Tuesday, when no one's watching, under a little pressure. That doesn't happen because a file exists somewhere. It happens because you taught it, put it in front of people where the work actually happens, and confirmed it stuck.
A process nobody follows isn't a process. It's a document with good intentions.
Why documented feels like the finish line
Documenting is satisfying in a way adoption never is. You produce a thing. You can point at it. Your V/TO says Process, and now there's a folder that proves you did Process. So the team exhales and moves on to the next Rock.
But documenting is the easy 20 percent, and adoption is the hard 80 percent that no one budgeted for. The reason this trips up smart teams isn't laziness. It's that the reward for writing something down arrives immediately, and the reward for getting it followed shows up months later, if you bother to look. Most people take the fast reward and never come back.
Put the process where the work happens
People don't go hunting for a document before they do a task. They do the task the way they remember it. So if your process lives two logins deep in a drive nobody opens, you've built a beautiful thing in a room no one enters.
Getting to adoption means the process shows up at the moment of the work, not in an archive you hope people visit. That usually means capturing it as short, watchable video from the person who does it best, then pushing it to the team right where they'll use it. When the guidance is where the hands are, following it stops being a chore and starts being the path of least resistance.
Measure whether the number moved
Here's the test that separates a real process from a filed one. Pick the number the process was supposed to change before you roll it out. Ramp time for a new hire. Error rate on an order. Days to close a deal. Then, a few weeks after you push it, look. Did the number move?
If it did, congratulations, you actually changed something. If it didn't, you learned that documented and adopted are not the same word, which is the most valuable lesson the Process Component has to teach. W. Edwards Deming spent a career pointing out that when work goes sideways, roughly 80 percent of the time the root cause is the process, not the person. You can't fix an 80 percent problem with a file nobody reads. You fix it by closing the loop: capture it, teach it, put it in the flow of work, and measure whether the needle moved.
What Followed By All really asks of you
Followed By All is the standard EOS holds you to on purpose, because it's the only version of Process that's worth anything. Documented is a starting line dressed up as a finish line. The finish line is a team that runs the same play the same way without you standing over them, and a number that proves it. Anything short of that is a file, and files don't run companies. People running the play do.
This is exactly what we built PlaybookBuilder to do, and it's why we're the officially licensed Process partner of EOS Worldwide. If you want the deeper walkthrough, see how we think about Process, take a look at the platform that pushes guidance into the flow of work, or explore certifying the person who'll own adoption. Documented is a start. Followed By All is the goal.
Jon LoDuca
founder
PlaybookBuilder
