Followed By All: How to Actually Measure FBA (Without Becoming the Process Police)

You documented the core processes. Nobody follows them. The fix is not another speech about accountability. It is one number per process on your Scorecard.

Key Takeaway

Followed By All™ (FBA) is a measurement problem, not a motivation problem. If following a core process is not visible as a number on your Scorecard, it does not exist. Wire each of your 6 to 10 core processes to one measurable, train people on the documented version, manage to the number with LMA™, and update the docs every quarter. That is the entire system.

What Followed By All Actually Means in EOS

Followed By All is the EOS standard that every person in your company consistently follows the documented core processes. Not most people, not the ones who wrote them, and not just when someone is watching. EOS is explicit that FBA does not demand robotic perfection on every step every time. It demands that the documented way is the default way. It is the third and hardest step of the Process Component: identify your core processes, document them, get them followed by all.

Most EOS companies stop one step short. The core processes get identified, somebody grinds out the documentation after the Rock rolls over once or twice, the docs land in a shared drive, and everyone exhales. Then nothing changes about how the work actually happens. Documented is not FBA.

Gino Wickman calls Process the most neglected of the Six Key Components in Traction, and FBA is the specific spot where it dies: the gap between a finished document and a changed behavior. The Organizational Checkup wants every component at 80 percent strength, and the FBA questions are usually where the Process score bleeds out.

Here is the reframe: FBA is not a motivation problem you solve with speeches. It is a measurement problem you solve on the Scorecard. Your team is not lazy or defiant. They work inside whatever system is visible, and right now the tribal version is the only one anyone can see. The rest of the Process Component works the same way: make the invisible visible, then manage it.

Why Nobody Follows Your Documented Processes

Nobody follows your documented processes because nothing in your operating system makes following them visible. A documented process that nobody measures is a prop: it lets the leadership team feel like the Process Component is handled while the real work drifts back to tribal habits within weeks. The operating rule is blunt: FBA lives or dies on the Scorecard, because if following the process is not visible there, it does not exist.

This happens because documentation feels like a finish line. The Rock said document our core processes, the docs exist, done. But a document by itself is potential energy. Measurement converts it into behavior, because it is the only way anyone can see whether the document and reality still match.

Run this test in your next Level 10 Meeting™: ask whether the team is following the sales process. You will get nods. Now imagine a Scorecard line instead: percentage of new deals this week with every pipeline stage completed. Nods are opinions. The number is the truth, and nobody had to hover over a desk to get it.

That is also the honest answer to the micromanagement fear around FBA. The alternative to measurement is not trust. It is policing: spot checks, drive-by questions, a manager rereading everyone's work. Measurement is what lets you stop all of that. One shared number per process, visible to everyone, reviewed weekly. No surveillance required.

The FBA Checklist: Train, Measure, Manage, Update

Getting to FBA takes four repeating moves, and they come straight from the EOS toolbox as the FBA Checklist: train everyone on the documented version, measure adherence with one number per process, manage to that number through LMA, and update the document when reality changes. EOS names the four steps. What it does not hand you is the mechanics, so here they are with the specifics filled in. Skip any one of the four and FBA decays back to tribal knowledge within a quarter.

Train: Everyone Learns the Documented Version

Training against the doc means the document is the curriculum, not a suggestion the trainer glances at beforehand. If your best rep trains new hires from memory, you now have two processes: the documented one and the taught one. The taught one wins every time, and the doc starts drifting toward fiction on day one.

This goes for tenured people too. When a process is first documented or materially updated, everyone who touches it gets trained on the change. Short session, walk the doc together, done. Nobody can ever claim there is a version of the process they never saw.

Measure: One Number Per Process

Every core process gets exactly one measurable on the Scorecard, owned by the seat that runs the process, reported weekly. Not five metrics. One. Adherence shows up in three forms: compliance (the steps were run), frequency (they were run every time), and outcome quality (they produced the standard). Pick whichever is hardest to fake for that process; the next section shows how. What matters here is that the number exists at all, because the moment it appears on the Scorecard, FBA stops being a matter of opinion.

Manage: LMA, Not Enforcement

This is just LMA doing its normal job. The number gets read out in the weekly L10 like every other Scorecard line. On track, move on, ten seconds. Off track, it drops to the issues list and gets IDSed. The discussion is why the number missed, never who to blame. Sometimes that means retraining. Just as often the process itself is broken, which is exactly what you want surfaced.

Update: The Doc Tracks Reality

A core process document is a living artifact with a named owner, a version date, and a quarterly review. When reality changes and the doc does not, every stale step teaches people to trust the documentation a little less. The Update step gets its own section below, because it is the one everybody skips.

How to Pick One Scorecard Measurable Per Core Process

Pick one leading indicator per core process, and pick one that only stays green when people actually follow the documented steps. You are not measuring outcomes here; the rest of your Scorecard does that. You are measuring adherence: error rate, rework, checklist completion, ramp time. If the number can look good while people freelance, it is the wrong number for FBA.

A good FBA measurable passes four tests:

• It moves weekly. A quarterly number cannot be managed in a weekly meeting.
• One seat owns it. A number owned by everyone is owned by no one.
• It is hard to fake without following the process. Checklist completion, error rates, and rework are difficult to game quietly.
• It measures the process, not a person. You are diagnosing the system, not building a case against whoever had a rough week.

Here is what that looks like across the core processes most companies land on. These are generic examples to steal, not prescriptions:

Notice these are leading indicators. Revenue tells you the sales process worked eventually. Stage completion tells you this week whether it is being run. When people improvise steps, rework climbs long before customers complain. And ramp time is the sleeper: if every hire needs months of shadowing, the process still lives in someone's head.

If your processes live in process software instead of a folder of PDFs, some of this FBA data comes free: checklist completion, read receipts, quiz scores after retraining. We broke down the best process software for EOS companies if you are shopping.

The Police Trap

If you catch yourself spot-checking individuals, running surprise audits, or building a fifteen-metric adherence dashboard, you have replaced measurement with surveillance. One number per process, reviewed weekly as a team, keeps the conversation about the process. The moment it becomes about catching people, FBA goes underground.

The Culture Move: "Great Question. What Does the Process Say?"

The fastest cultural signal that FBA is real is how leaders answer questions. When someone asks how to handle a situation the process already covers, the answer is: great question, what does the process say? Answer from memory instead and you just taught the whole team that the doc is optional, including for you.

This is the cheapest, highest-leverage habit in the FBA toolkit, and it costs nothing but ego. Route questions through the doc and you transfer authority from yourself to the system. Owners feel this one directly: the questions finally stop coming to you.

The Script

Team member: "Hey, how should I handle this?" You: "Great question. What does the process say?" Them: "It doesn't cover this." You: "Then we just found this week's update. What did you run into?" Ten seconds, and the artifact gets stronger either way.

The line does two jobs. If the doc answers the question, that person checks it first next time. If it does not, you just found an update, and the asker helps fix it. There is a whole playbook on getting your team to follow documentation, but this single sentence is the spine of it.

One warning: the move only works if leadership follows the processes too. The fastest way to kill FBA is a Visionary who treats every documented process as a suggestion. Your team does not follow what the doc says. They follow what you do.

The Diagnostic Flip: If Nobody Opens the Doc, the Doc Is Wrong

When FBA is low across the whole team, the problem is almost never the team. A document nobody opens is wrong, out of date, or written at the wrong altitude. Fix the artifact before you blame the people, because you cannot manage anyone to a standard that does not match reality.

Before you manage anyone harder, run three checks on the artifact itself:

1. Is it accurate? Hand it to your best performer and ask what is wrong with it. If they laugh at step four, the doc is fiction and everyone already knows it.
2. Is it at the right altitude? EOS asks for 6 to 10 core processes documented at 20/80: the 20 percent of steps that produce 80 percent of the outcome, a few pages at most. If your ops manager produced a 40-page manual, nobody will open it, and honestly, nobody should. That is an SOP library pretending to be a core process, and it belongs one layer down. What 20/80 actually looks like on the page is its own conversation.
3. Is it findable? If reaching the doc takes more clicks than asking a coworker takes seconds, the coworker wins. Three clicks or fewer from wherever the work happens.

We see the same pattern across trades and service businesses over and over: the team that ignored the bloated manual follows a tight two-page rebuild of the same process without a single accountability conversation. The behavior was never the bottleneck. The artifact was.

How Often Should You Update Core Processes? Quarterly, on the Rhythm You Already Run

Core processes get reviewed on the same quarterly rhythm as everything else in EOS. Each process owner brings their document and its Scorecard measurable to the quarterly session, confirms the doc still matches reality, and logs what changed. Between quarters, any process issue that hits the issues list triggers a spot update.

The quarterly review is not a documentation project. Per process, it is about fifteen minutes:

1. Reread the doc against reality. The process owner checks it against how the work actually happened this quarter, not how it was supposed to happen.
2. Check the measurable. On track all quarter, drifting, or chronically off? A chronically red FBA number usually means the doc is wrong, not the team.
3. Log the changes. Update the steps, bump the version date, and flag whether the change is material.
4. Retrain on the delta. Material changes get a short walkthrough with everyone who runs the process. Nothing changed, nobody retrains.
5. Review at the leadership level. The leadership team spot-approves changes in the quarterly session and the cycle restarts.

Two refinements once the rhythm is stable. When an FBA measurable holds its goal for two straight quarters, the process is habit: rotate that Scorecard slot to your next weakest process so the Scorecard stays lean. And any process issue solved in the weekly L10 ends with someone updating the doc, because solving the issue without touching the doc just schedules it again for next quarter.

Stale docs are the silent killer of the whole FBA system, worse than no docs, because they actively teach your team that the documentation lies. We wrote a full guide to keeping procedures current, but the EOS-native version is simple: doc reviews ride the quarterly rhythm you already run. No new meetings.

Frequently Asked Questions

How do EOS companies measure Followed By All without micromanaging?

By measuring the process, not the person. Each core process gets one Scorecard number that only stays on track when the documented steps are followed: error rate, rework, checklist completion, ramp time. Managers manage to the number in the weekly meeting and drop misses to the issues list. Nobody audits individuals. The number surfaces drift, and the conversation stays about the process.

What does Followed By All mean in EOS?

Followed By All is the EOS standard that every person in the company consistently follows the documented core processes. It is the third step of strengthening the Process Component, after identifying your 6 to 10 core processes and documenting them at the 20/80 level. Documented but not followed does not count, and the Organizational Checkup treats a component as strong at 80 percent or better.

What should go on the Scorecard to track process adoption?

One measurable per core process, weekly, owned by a seat. Good candidates are leading indicators of adherence: percentage of deals with every pipeline stage completed, onboarding checklist completion, rework rate, invoices sent within three days, new hire ramp time. The test is simple: could this number look good while people ignore the doc? If yes, pick a different number.

What if nobody ever opens our process documents?

Treat it as a diagnostic, not a discipline problem. A doc nobody opens is usually wrong, stale, or at the wrong altitude, like a 40-page manual where EOS asks for a 1 to 3 page core process. Verify it matches how your best person actually works, cut it to 20/80, make it findable in under three clicks, then retrain. Adoption follows accuracy.

How often should we update our core processes?

Review every core process once a quarter, on the same rhythm as your quarterly session and Rocks. The process owner confirms the document still matches reality and logs any changes. Between quarters, update immediately whenever a process issue gets solved in your weekly meeting, then retrain on the delta. A dated version note on each doc keeps trust high.