How Do You Strengthen the EOS Process Component?

By Lisa Gonzalez, Certified EOS Implementer® and co-author of Process! (The EOS Mastery Series). Updated October 3, 2026.

You strengthen the EOS® Process Component one core process at a time. Commit as a leadership team, identify your five to twelve core processes, and document and simplify each as an outline of its sub-processes. Then package, train, measure, manage and update those sub-processes. The teams I work with roll out one or two sub-processes per quarter.

I'm Lisa Gonzalez, Certified EOS Implementer® and co-author of Process!, the book in the official Traction® Library on this component. I've taught it in hundreds of sessions with leadership teams. Here are the eight steps, in order.

Why is Process usually the weakest component?

EOS Worldwide puts it plainly: a weak Process Component shows up as inconsistent quality, training challenges and key-person dependency. It can be fixed. Process! reports that more than ten thousand companies have strengthened their Process Component (Ch. 2).

Across hundreds of workshops and consulting engagements, I consistently see 5 to 10% of profit leaking out through process gaps. Most leadership teams build Vision, People and their meeting rhythm first. Process gets left for last, and the leak keeps running.

"Many teams stop at getting their processes documented, when 80% of the heavy lifting in Process is getting it Followed By All." Lisa Gonzalez, co-author of Process!

What are the eight steps?

Commit. The leadership team decides together that process gets done, and makes the first core process a priority.
Identify. Agree on your handful of core processes, five to twelve, and give each one a name and an owner.
Document and Simplify. Write the core process as an outline of its sub-processes, the 20% that drives 80% of the results. Our book says one to five pages. Less is more. If you land at no greater than three, you're doing great. The leadership team reviews and approves it.
Package. Package the sub-processes, SOPs and procedures underneath it, where your team already works, in a format people will actually open.
Train. Teach it person to person, then have them teach it back.
Measure. Track one number on your Scorecard that shows the process is being followed.
Manage. Leaders hold the standard in the weekly meeting. When a step gets skipped, the closest leader says so, kindly and quickly.
Update. When the team grows, people turn over, or results hit a ceiling, change the process, stamp the new version and retrain. Do it at least once a year.

The core process itself isn't much to roll out. It's an outline for the work ahead. The sub-processes, SOPs and procedures underneath it are what get packaged, trained, measured, managed and updated. In the teams I work with, that means one or two sub-processes rolled out per quarter.

Steps 5 through 8 are the FBA Checklist. That's where most teams stall.

What does one quarter look like?

Make your first core process a Rock and take one step a week. Commit, Identify, Document and Simplify, Package, Train, Measure, Manage and Update each get their own week. Week 9 checks the results. Weeks 10 to 13 are buffer, because a real quarter always needs some. By the end, your core process outline is approved and your first one or two sub-processes are rolled out.

Our book puts the whole journey, every core process, at nine to twelve months (Process!, Ch. 3 and 4). Self-implementing? Here is the full one-quarter plan for self-implementing teams.

When isn't this the right approach?

The leadership team hasn't committed. Start with step 1. Nothing after it sticks without it.
Your list runs past twelve. You're documenting sub-processes, not core processes.
Someone wants a 40-page manual. That's a sign of fear, not rigor. Nobody reads it.

Frequently asked questions

How long does it take to strengthen the EOS Process Component?
Plan on one quarter for your first core process: the outline approved and one or two of its sub-processes rolled out. That's the pace I see in the teams I work with. Process! puts the full journey, every core process documented and followed, at nine to twelve months. After that, the work is upkeep.

What's the difference between a core process and a sub-process?
A core process is the outline: one of your five to twelve most important, repeatable ways of doing business, written as a list of its sub-processes. The sub-processes, SOPs and procedures hold the detail. They're what get packaged, trained, measured, managed and updated, one or two per quarter in the teams I work with.

What EOS tools strengthen the Process Component?
Two. The 3-Step Process Documenter covers Identify, Document and Simplify, and Package. The FBA Checklist covers Train, Measure, Manage and Update. Process! adds Commit at the front, because nothing sticks until the leadership team decides together. Those are the eight steps.

Can you strengthen the Process Component without an EOS Implementer?
Yes. The tools are the same either way. Self-implementers usually stall on getting processes followed, not on documenting them, so give the plan to your Integrator and put one number on your Scorecard. Here is the full plan for self-implementing teams.

Should strengthening the Process Component be a Rock?
Yes, one core process at a time. A Rock gives it an owner, a deadline and a weekly check in your Level 10 Meeting™. Making "document all our processes" a single Rock usually fails, because it's too big to finish in a quarter.

Why is the Process Component the weakest component in most companies?
Because it pays off slowly. Vision, People and the weekly meeting show results within weeks. Process pays off over quarters, so it gets left for last. Meanwhile the business keeps depending on whoever carries the work in their head, and that leak shows up in profit.

How do you know your Process Component is strong?
Two tests. Your core processes are documented, simplified and approved by the leadership team. And everyone follows them, which you can see in a number on your Scorecard rather than a feeling. EOS calls the second test Followed By All. Most companies pass the first and fail the second.

What does Followed By All mean?
Followed By All, or FBA, means everyone in the company consistently follows your documented core processes. It's the second half of the Process Component and the harder one. The FBA Checklist gets you there: train, measure, manage, update.

Related guides

Ready to start? Process Success: Get Your Processes Followed By All walks your leadership team through all eight steps, one step a week. Follow this, and your processes get followed. Book a discovery call.