The EOS Process Component: Why It's the Most Neglected of the Six (and How to Get It to 80%)

Most EOS® companies score the Process Component™ lowest on the Organizational Checkup. Here is what it actually asks for, why it stays weak while everything else gets healthy, and a realistic two-quarter path to 80%.

What Is the Process Component in EOS?

The Process Component is one of the Six Key Components of the EOS model. It asks one question: are your core processes identified, documented, simplified, and Followed By All? In practice the Process Component means three things: name the 6 to 10 core processes that make up your unique way of doing business, document each at a high level, and get every person in the company following them.

The Process Component is what EOS means when it talks about your company's Way: the handful of processes that, run consistently by everyone, produce your results without you standing over them. Not hundreds of procedures. Not a wiki. Six to ten named processes, written down at the level a smart new hire could follow, and actually followed.

Here is how the Process Component sits alongside the other five, and why it behaves differently than all of them:

Component	What it asks	What keeps it honest
Vision	Everyone knows where the company is going and how it gets there. Lives in the V/TO™	Quarterly and annual planning sessions
People	Right people, right seats, run through the Accountability Chart	People Analyzer, quarterly conversations
Data	A handful of numbers that tell you the truth every week	The Scorecard, reviewed weekly
Issues	Problems get named and solved, not managed around	IDS at the weekly Level 10 Meeting™
Process	Your 6 to 10 core processes, documented and Followed By All	Nothing. No weekly ritual touches it.
Traction	Priorities become Rocks and get done	Rock reviews at every L10 and every quarterly

Look at that last column. Five components have a built-in enforcement mechanism. The Process Component is the only one the operating system never checks on. That single design fact explains most of what follows in this article.

EOS even hands you the instructions: a free tool called the 3-Step Process Documenter™, plus an 80% strength target on the Organizational Checkup. The instructions are not the problem. The execution is.

Why Wickman Calls Process the Most Neglected Component

In Traction, Gino Wickman calls the Process Component the most neglected of the Six Key Components. The reason is structural: every other component has a ritual that forces attention on a weekly or quarterly cadence. The Process Component has no ritual. Nothing in the EOS operating rhythm breaks when documentation doesn't happen.

Think about what keeps the other five healthy. The Scorecard gets reviewed because the Level 10 Meeting starts with it, every single week. Rocks get reviewed the same way. Issues get IDSed weekly. The V/TO gets pulled apart twice a year whether you feel like it or not. The system polices those components for you.

The Process Component has no enforcement. If your core processes go undocumented for another quarter, no meeting gets awkward, no number turns red, nobody notices. The pain is real, but it's diffuse: a botched handoff here, a new hire trained on folklore there. It never concentrates into a single moment that forces action.

There's a second reason, and it's less comfortable. Strengthening the other components feels like leadership work. Setting vision, restructuring seats, choosing Rocks: that's what Visionaries and Integrators signed up for. Documenting how invoicing works feels like homework. So it gets delegated downward, bumped weekly, and rediscovered every ninety days when the Checkup comes back.

The problem is common enough that it eventually got its own book: Process! (2022), by Mike Paton and Lisa González, is devoted entirely to the Process Component. Components that companies handle on their own do not get books written about them.

EOS Worldwide says more than 280,000 companies run on EOS. Whatever the precise number, the pattern inside them is consistent: the Process Component is the score that makes the room go quiet. If your latest Checkup just did exactly that, we wrote a dedicated plan for that moment: Process is your lowest Checkup score. Here's your next 90 days.

What a Weak Process Component Actually Costs

A weak Process Component shows up as three recurring taxes: inconsistency (every person runs their own version of the work), key-person dependency (critical knowledge lives in one head), and training drag (every new hire learns by shadowing, so ramp time and quality depend entirely on who they happened to shadow).

Inconsistency is the visible one. Across our client work in home services, staffing, construction, and agencies, the shape is identical: every estimator prices a little differently, every recruiter qualifies a little differently, every project manager onboards clients a little differently. Your customers get a different company depending on who picks up the phone. You can't fix quality, and you can't scale, when there is no "the way" to improve.

Key-person dependency is the dangerous one. When the process lives in someone's head instead of on paper, that person is the process. They can't be promoted cleanly, they can't take three weeks off, and if they leave, the process leaves in the same car. This is the tribal knowledge problem, and EOS companies are not immune to it just because the Accountability Chart looks tidy.

Training drag is the silent one. Without documented processes, your real training system is shadowing. New hires inherit the habits, shortcuts, and workarounds of whoever trained them, then pass those on to the next hire. Ramp times stretch, and your best operators lose hours every week re-explaining things a document should have answered.

The 3-Step Process Documenter: The Whole Playbook in Three Moves

EOS gives you the 3-Step Process Documenter: identify your core processes and agree on their names as a leadership team, document and simplify each one at the 20/80 level (the 20% of steps that produce 80% of the outcomes), then package them and train everyone to follow them.

1. Identify your 6 to 10 core processes. The leadership team lists them and agrees on what each one is called. A typical set: the HR process (hiring through exit), the marketing process, the sales process, one or more operations processes (however your company makes and delivers what it sells), the accounting process, and the customer retention process. The naming step matters more than it sounds; you cannot hold people accountable to a process nobody can name. If you want help choosing the starting order, here's what to document first.
2. Document each one at 20/80. One to three pages per process. Major steps as headers, a few bullets under each, capturing the 20% of detail that drives 80% of the outcome. Not a novel, not a legal document, not a screenshot-by-screenshot manual. If you're not sure what that actually looks like on paper, we published real examples of the 20/80 rule in practice.
3. Package and roll out. Consistent format, one place everyone can find, and a training pass so every person learns the documented version, not the folklore version. This is where the Process Component stops being a documentation project and becomes an operating habit.

Three steps. Simple on paper. And yet companies sit stuck on step 2 for a year or more, which is why we wrote a whole piece on why teams stall on the 3-Step Process Documenter. The tool is fine. The tool was never the constraint.

What Followed By All Means (and Why It's the Real Finish Line)

Followed By All means every person in the company actually runs the documented core processes, not just the people who wrote them. Documentation is not the goal of the Process Component; FBA is the finish line, and getting there takes four disciplines: Train, Measure, Manage (LMA), and Update. A binder nobody opens scores the same as no binder at all.

Train. Everyone learns the documented version of the process, including your veterans. This is the step most companies skip, because training tenured people on "how we do things" feels redundant. It isn't. If the veterans keep running the tribal version, the new hires will too, and the document dies in a folder.

Measure. Wire each core process to a number on the Scorecard that only stays green when the process is followed. If following the process isn't visible in a number, it doesn't exist. This is the single highest-leverage move in the whole Process Component, and we break down exactly how to do it in how to actually measure FBA.

Manage (LMA). Leaders hold people accountable to the process through normal leadership, management, and accountability conversations, not through surveillance. The habit that changes everything is small: when someone asks how to handle a situation, the answer becomes "great question, what does the process say?"

Update. Processes drift. A quarterly review keeps the documents true, which keeps the team trusting them. Here's the uncomfortable corollary: if nobody opens the docs, the docs are usually wrong or written at the wrong altitude. Fix the artifact before you blame the team. We covered that failure mode in depth in why your SOPs collect dust.

Why Companies Stall: The Rock-Failure Loop

The pattern is nearly universal: leadership sets a "document our core processes" Rock, assigns it to a department head, and the quarter ends with the Rock at 20% done. The Rock fails for one of three reasons: no dedicated pen-holder, the wrong altitude, or no extraction method.

Reason 1: Nobody holds the pen

Documentation is a job, not a Rock. The people who know the processes best are your busiest operators, and writing loses to revenue every single week. Assign the Rock to your ops leader and you've scheduled thirteen consecutive weeks of "I'll get to it this weekend." The fix is not a more motivated owner. It's separating the roles: the process owner talks, a named pen-holder writes. If your leadership team has watched this exact Rock die more than once, read why your Process Rock keeps failing before you set it again.

Reason 2: The wrong altitude

Half of stuck teams write too much: the ops manager produces 40 pages of SOP-level detail for one process, burns out, and never starts the second. The other half write too little: three vague bullets that answer nothing. Both miss the altitude the Process Component actually asks for. Core processes, SOPs, and checklists are layers, not rivals: the core process is the one-to-three-page skeleton, SOPs hang off individual steps for the roles that need the how, and checklists are the runtime artifact. We untangle the three in core process vs SOP vs checklist.

Reason 3: No extraction method

Handing someone a blank template is not a method. Pulling a process out of a person's head is a craft: asking the right questions, catching the decision points they skip because they're unconscious of them, and distilling forty minutes of talking into a page and a half. Most companies assign that craft as a side project to someone who has never done it, then act surprised when the Rock produces meeting notes instead of processes.

How to Get the Process Component to 80%: A Realistic Two-Quarter Path

You can take the Process Component from your lowest score to genuinely strong in two quarters. Quarter one: identify and prioritize your 6 to 10 core processes, then document the three or four highest-pain ones. Quarter two: finish the rest and wire Followed By All into your Scorecard and meeting rhythm.

1. Week 1: List and prioritize. One leadership session. Name your 6 to 10 core processes, then score each on two axes: how much pain when it's done wrong, and how much it depends on one person's head. The process that's high on both goes first. One process documented and followed beats ten drafted and ignored.
2. Quarter 1: Run weekly working sessions. One process per session, 45 to 60 minutes. The process owner talks; a named pen-holder writes, distills, and brings a draft back before the next session. Nobody documents alone at their desk, ever. By the end of the quarter you have your three or four highest-pain processes at 20/80.
3. Quarter 1: Approve at the leadership level. Each draft gets reviewed at the L10 or a dedicated session. Approve and move; do not wordsmith forever. A good-enough process that ships this quarter outperforms a perfect one that never does.
4. Quarter 2: Finish the set. Same cadence, remaining processes. This is also when you load everything into your platform of choice, in one consistent format.
5. Quarter 2: Wire FBA. Train the whole company against the documents, put one measurable per core process on the Scorecard, and add a quarterly update review so the docs stay alive.
6. Every quarter after: Maintain. The Checkup score holds because the system now polices the Process Component the way it already polices Data and Traction: with numbers and a cadence.

Notice the software shows up in quarter two, not week one. Software solves storage and delivery, not extraction. Buy the platform before the processes are out of people's heads and you get an empty shelf with a monthly invoice. When you're ready to compare platforms, we ranked them for this exact use case in the best process software for EOS companies. For what it's worth, PlaybookBuilder describes itself as the Process software used by EOS Corporate.

And if you're running EOS without an implementer, none of this changes. The working structure is identical; you just facilitate it yourself. We wrote the self-implementer's version here: building the Process Component without an implementer.

When to Get Outside Help (and When Not To)

Do it yourself when someone on your team has real capacity and real writing craft to hold the pen. Get help with the Process Component when the same Rock has failed for two or more quarters, when your processes live in the heads of your busiest people, or when the deadline is real: a sale, a scale-up, a key person leaving.

Be clear-eyed about who can and can't help. Your implementer facilitates the framework; documentation is execution work, and most implementers will tell you straight out that they don't do it for you. Software stores what you write; it doesn't extract what your people know. The gap between "we know what to do" and "it's done" is filled by exactly one thing: somebody with the time and the craft to sit with your process owners and hold the pen.

The honest test is the same one you already apply everywhere else in the business. You would never assign payroll to a department head as a side Rock. Specialized, high-consequence work goes to people who do it every day. Process extraction is that kind of work; it just doesn't look like it, because everyone technically knows how to type.

We wrote a full, honest breakdown of the decision, including the cases where DIY genuinely wins, in document your core processes yourself or hire it done. Read that before you commit another quarter either way.

EOS® and related marks are trademarks of EOS Worldwide. The Systems Effect is an independent company and is not affiliated with or endorsed by EOS Worldwide.