What the Process Component Is in EOS
EOS® describes six key components that every business has to get strong: Vision, People, Data, Issues, Process, and Traction. The Process component is about one thing: deciding the right way to do the work that matters most, writing it down simply, and making sure everyone actually does it that way.
That sounds obvious, yet most growing companies run on tribal knowledge. Each salesperson qualifies leads a little differently. Each project manager has a personal onboarding routine for new clients. The results depend on who happens to be doing the work, and every new hire learns the job by shadowing whoever has time. When the business is small, that works. As it grows, the inconsistency shows up as rework, customer complaints, and leaders pulled back into the details.
Strengthening the Process component gives you three things:
- Consistency. Customers get the same experience no matter who serves them.
- Scalability. New people can be trained against a clear standard instead of a moving target.
- Freedom for leaders. When the core of the business runs the same way every time, the leadership team can spend its time on the Vision and Traction work instead of firefighting.
Many teams take on this component after the other tools are in place, often with their EOS Implementer guiding a dedicated session on it. Whether you work with an Implementer or self-implement, the work itself follows the same steps.
Step 1: Identify Your Core Processes
A core process is one of the handful of major workflows that define how your company operates. Most companies end up with somewhere between five and ten. Fewer than that usually means you are lumping unrelated work together; many more usually means you are listing sub-processes or individual tasks.
Common core processes
The names vary by company, but most lists include some version of these:
| Core process | What it covers | Typical owner (seat) |
|---|---|---|
| People / HR | Recruiting, hiring, onboarding, reviews, and exits | Integrator or HR lead |
| Marketing | How you attract and nurture prospects | Marketing lead |
| Sales | How a prospect becomes a customer | Sales lead |
| Operations / Delivery | How you produce and deliver your product or service | Operations lead |
| Accounting / Finance | Billing, collections, payables, and reporting | Finance lead |
| Customer Retention | How you keep, support, and grow existing customers | Customer success lead |
The owner column matters. Each core process should map to a seat on your Accountability Chart, and the person in that seat owns documenting the process, keeping it current, and making sure it is followed.
Name them consistently
Agree on one name for each process and use it everywhere: in meetings, in training, in your documentation. If the leadership team calls the same process "onboarding," "kickoff," and "implementation" depending on who is talking, people will assume these are three different things. A single, shared name is a small step that removes a surprising amount of confusion.
Draw the big picture first
Before documenting any detail, sketch how the core processes connect. Marketing hands leads to Sales, Sales hands new customers to Operations, Operations hands finished work to Accounting for billing, and Customer Retention keeps the relationship going. Seeing the handoffs on one page shows you where things most often fall through the cracks.
Step 2: Document Each Process at the 20/80 Level
The most common mistake in process work is over-documenting. A forty-page operations manual is impressive and almost never read. EOS instead asks you to capture the 20 percent of steps that produce 80 percent of the results, the major steps and the few critical details within them.
A simple documentation template
For each core process, capture:
- Purpose. One or two sentences on why the process exists and what a good outcome looks like.
- Owner. The seat accountable for the process.
- Major steps. Usually somewhere between five and fifteen, written as short action statements.
- Key details under each step. Only the points that, if missed, would cause a real problem.
- Measurables. One or two numbers that tell you whether the process is working.
- Tools and systems. The software, forms, or templates used along the way.
What 20/80 looks like in practice
Take a hypothetical sales process for a small professional services firm. A 20/80 version might have six steps: qualify the inquiry, hold a discovery call, send a written proposal within a set number of business days, follow up on a fixed schedule, hold a decision call, and hand off to delivery with a completed kickoff form. Under "send a written proposal," the key details might be "use the current proposal template" and "include the scope, timeline, and investment sections." That is enough for a new salesperson to follow, without dictating every email they write.
A useful test: if your best person read the document, would they say "yes, that is how we do it" without needing to add anything important? If so, you have the right level of detail.
Keep the writing plain
Write for the newest person on the team. Use short sentences, active verbs, and the vocabulary your people actually use. Checklists and simple diagrams often work better than paragraphs. If a step needs a long explanation, link to a separate how-to rather than burying it in the core process.
Step 3: Get Every Process Followed by All
A documented process that nobody follows is just a document. EOS uses the phrase Followed by All, often shortened to FBA, to describe the real goal: every person who touches the process does it the agreed way.
Train against the documented process
Make the core process the backbone of training. New hires learn the process from the document, then practice it with their manager. Existing team members review it when it changes. The document becomes the shared standard everyone is measured against.
Measure whether it is being followed
Pick a measurable for each process and put it where the leadership team sees it every week. A proposal turnaround time, an onboarding checklist completion rate, or days to collect an invoice can all go on your Scorecard. When the number drifts, it is an early signal that the process is not being followed, or that it needs to change.
Use the Issues List when something breaks
When a process is not working, treat it as an issue, not a personal failing. Add it to the Issues List, identify the real cause, discuss it, and solve it. Sometimes the fix is retraining. Sometimes the process itself is wrong and needs to be updated. Either way, the solution becomes part of the documented process so the improvement sticks.
Connect it to managing people
Following the core processes is part of every role. If someone repeatedly works around a process after being trained on it, that is a conversation for their manager, using the same tools you use to assess fit and performance, such as the People Analyzer.
Keeping Processes Alive
Processes decay. Software changes, customers change, and teams find better ways to work. Build in a light review cycle:
- Quarterly: each owner skims their process and flags anything outdated.
- When a recurring issue shows up: update the process as part of solving it.
- When a key person changes seats: review the processes they owned before the handoff.
Many teams tie the quarterly review to their quarterly planning session, so process updates sit alongside Rocks and other priorities. If documenting or updating a process is a significant project, it can become a Rock itself.
A Process Component Checklist
Use this as a quick health check for your leadership team:
- You have agreed on your core processes, typically five to ten, with one shared name for each.
- Every core process has an owner whose seat appears on the Accountability Chart.
- Each process is documented at the 20/80 level, with a purpose, major steps, and key details.
- Every process has at least one measurable the leadership team can see.
- New hires are trained on the relevant core processes during onboarding.
- Process problems are raised on the Issues List and solved, not worked around.
- Owners review their processes at least quarterly.
If you can say yes to all seven, your Process component is in strong shape. If not, the gaps tell you where to focus next quarter.
How GoalCadence Supports the Process Component
GoalCadence gives your team one place to keep core processes next to the rest of your EOS tools. The visual process builder lets you document each step with text, images, videos, and checklists, and core process templates for sales, marketing, operations, finance, HR, and customer service give you a starting point. Each process has an assigned owner, version control shows who changed what and when, and adherence tracking with checklists and completion tracking helps you see where a process breaks down. You can also reference processes from onboarding checklists so new hires train against the current version.
If you work with an EOS Implementer, they can join your GoalCadence account free on every plan and work directly in the same processes your team uses between sessions. See pricing for plan details, or read What Is EOS for an overview of how all the components fit together.