Services
Team Course Free Bootcamp Enterprise: Advising One-Day Workshop EOS Implementer Tools EOS
Resources
Calculator Free Chapter Subscribe Order Process! Free Guides & Tools
Learn
Streamline Your Operations Maximize Profitability Build a Winning Team Blog
About
Speaking Events Testimonials Media

Can You Self-Implement the EOS Process Component?

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

Self-implement the EOS® Process Component one quarter at a time. Make your first core process a Rock, write it as an outline of its sub-processes, then package, train, measure and manage one or two of those sub-processes. Self-implementers rarely stall on documenting. They stall on getting processes Followed By All.

I'm Lisa Gonzalez, Certified EOS Implementer® and co-author of Process!, the book in the official Traction® Library on this component. Before I became an Implementer, I self-implemented EOS in our own residential remodeling company. We made it more complicated than it was meant to be. Here is the simpler path.

Why do self-implementers underestimate the Process Component?

Process is the component self-implementers most often leave for last. Brian Dosal, CEO of Strety, self-implemented EOS for more than ten years at BrightGauge and Strety. Looking back, he named the Process Component his biggest gap (Strety, 2026).

The reason is simple. Vision, People and the weekly meeting show results fast. Process pays off over quarters, so it waits. Meanwhile the business keeps depending on the people who carry the work in their heads.

What does a one-quarter plan look like?

Treat your first core process as a Rock. Your Integrator owns the plan. Take one step a week for eight weeks, check the results in week 9, and keep the rest as buffer.

  1. Week 1, Commit. The leadership team decides together, out loud, that this gets done. The first core process becomes a Rock.
  2. Week 2, Identify. Each leader lists your most important, repeatable processes. Compare the lists and agree on your handful. Process! puts that at five to twelve.
  3. Week 3, Document and Simplify. Write the core process as an outline of its sub-processes, the 20% that drives 80% of the results. Show it to the people who do the work, revise it, and get the leadership team's approval. Then pick the one or two sub-processes you'll roll out this quarter.
  4. Week 4, Package. Package those sub-processes where your team already works, with clear names and owners.
  5. Week 5, Train. Teach them to everyone who touches them, then have people teach them back.
  6. Week 6, Measure. Put one number on your Scorecard that shows they're being followed.
  7. Week 7, Manage. Give them a standing spot in your weekly Level 10 Meeting™.
  8. Week 8, Update. Set the update rhythm: at least once a year, and any time the team grows, people turn over or results stall.
  9. Week 9, check the results. Retake the self-assessment and pick the next sub-processes.

Weeks 10 to 13 are buffer. A real quarter always needs some.

Train, Measure, Manage and Update are the FBA Checklist, one week each. They are where most self-implementers stall.

Our book puts the whole journey, every core process documented and followed, at nine to twelve months (Process!, Ch. 3 and 4). One quarter gets your first core process outlined and one or two of its sub-processes followed.

Where do self-implementers get stuck?

Rarely on documentation. Almost always on Followed By All. I cover the most common mistakes in What Is the EOS Process Component? Three more show up when nobody outside the company is watching.

  • Nobody asks at the Quarterly. Without an outside voice, "is it being followed?" never gets asked.
  • The Integrator does it alone. Process becomes one person's project instead of the leadership team's decision.
  • The process never reaches the Scorecard. If no number tracks it, nobody knows whether it's followed until a customer tells you.

With or without an EOS Implementer, what changes?

The tools are the same. EOS is built so a leadership team can run it on its own. An EOS Implementer® adds an outside view, the right sequence, and someone who holds the leadership team to it. If you work with an Implementer, use this plan between sessions. If you self-implement, use it as your Process Component guide.

When should a self-implementer bring in an EOS Implementer?

  • The leadership team isn't aligned on whether process matters.
  • The same process issue sits on your Issues List two quarters running.
  • You want help across all six components, not just Process.

In any of those cases, here is how to choose an EOS Implementer.

Frequently asked questions

Can you self-implement the EOS Process Component?
Yes. The Process Component runs on simple tools any leadership team can use: the 3-Step Process Documenter and the FBA Checklist. What self-implementers usually lack is follow-through, not tools. Treat your first core process as a Rock, give the plan to your Integrator, and put one number on your Scorecard.

Where do self-implementers get stuck on the Process Component?
On getting processes Followed By All. Documenting feels like progress, so teams stop there. The process gets written, nobody gets trained on it, nothing measures it, and within a quarter people are back to their own way. Training, one weekly number and a standing spot in your Level 10 Meeting fix most of it.

How long does it take to self-implement the Process Component?
Plan on one quarter for your first core process: the outline approved and one or two of its sub-processes rolled out. Process! puts the full journey, every core process documented and followed, at nine to twelve months. Teams that try to document everything at once usually take longer, because nothing gets followed while everything is being written.

Who should own the Process Component when you self-implement?
The Integrator. The Integrator holds the leadership team to the plan, tracks the Rock and keeps the weekly number on the Scorecard. Each core process also gets its own owner, usually the leader whose team runs it. The leadership team still reviews and approves every core process together.

Do you need an EOS Implementer to strengthen the Process Component?
No. Many companies strengthen it on their own with the book and the tools. An EOS Implementer speeds it up with an outside view and accountability. If you work with one, use this plan between sessions. If you don't, use it as your guide and bring in help when you stall.

When should a self-implementer hire an EOS Implementer?
When the leadership team isn't aligned, when the same process issue keeps returning to your Issues List, or when you want help across all six components. Those are signs an outside view will pay for itself.

Is there a self-paced way to work through the Process Component?
Yes. Process Success: Get Your Processes Followed By All is a self-paced workshop built from the book Process! It walks a leadership team through one core process and its first sub-processes in one quarter, about twenty minutes a week, with one action each week. Teams use it on their own or alongside an EOS Implementer.

Related guides

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