Process Is Your Lowest Checkup Score. Here's Your Next 90 Days

Key Takeaway

A low Process Component™ score on the Checkup does not get fixed by documenting harder. It gets fixed by triage: list your 6-10 core processes, rank each by pain when done wrong and by how much it lives in one head, and build the worst offender first. For a company running on EOS®, two to four processes documented, followed, and measured is a quarter well spent, and it moves the Checkup score more than ten drafts nobody opens.

What a Low Process Checkup Score Actually Means Operationally

A low Process score on the Checkup means the business runs on individual habits instead of a company way. Customers get a different experience depending on who handles them, quality depends on who shows up, new hires take months to ramp because training is shadowing, and critical knowledge lives in a few heads that could resign tomorrow.

Walk through those four, because your first target process is hiding inside them:

• Inconsistent customer experience. Your best people deliver one version of the company; everyone else delivers their own. In home-service and agency businesses this is the classic pattern: the experience depends on which technician or account manager the customer drew, and the owner personally rescues the misses.
• Quality depends on who shows up. Output is great when your strongest operator is on the job and wobbles when they are on vacation. That is not a people problem; it is the absence of a process anyone else could follow.
• Training drags. Onboarding means shadowing whoever has time, so every new hire learns a slightly degraded copy of their trainer while managers stay stuck re-explaining instead of leading.
• Key-person risk. Somewhere in your company there is a person who does not just run a process. They are the process. If they leave, the process leaves with them.

Here is the part worth sitting with: the Checkup score is your own leadership team reporting these symptoms anonymously. Nobody rates Process at 40 percent because the documentation folder looks thin. They rate it low because they are living these four problems every week.

One more read worth taking before you plan anything: the spread between leaders on the Checkup, not just the average. If one of you scored Process a seven and another a two, you do not agree on how work actually gets done, and that disagreement belongs on the issues list by name before any documenting starts.

Why You Should Not Start by Documenting

Do not open a blank template and start writing. The instinct after a bad Process score is to launch a documentation blitz, and that instinct is why the Checkup score stays low. Start by listing your 6-10 core processes and triaging them, because one process done and followed beats ten drafted and ignored.

The blitz is how the classic failed Process Rock happens: leadership sets "document our core processes" as a Rock, every department head opens a doc, and the quarter ends with ten half-drafts, nothing trained, nothing followed. If that Rock has already died at your company once or twice, read why your Process Rock keeps failing before you set it again.

The right first move is one working meeting to name the list. Your core processes are the handful of things the business does over and over to make money and keep its promises: how you market, sell, deliver, hire and onboard, invoice and collect. Naming all 6-10 takes about an hour if you resist the urge to describe them.

That list is your entire week-one deliverable. Do not write a single procedure until it exists, because the list is what turns "fix Process" from a mountain into a queue.

The Two-Axis Triage That Picks Your First Process

Score each core process on two axes: how much pain the business feels when it is done wrong, and how much of it lives in one person's head. Rate both high, medium, or low. The process that scores highest on both axes is your first build. Everything else waits its turn.

Both axes are gut calls your leadership team can make today.

Pain when done wrong is the visible axis. Rework, refunds, apology calls, missed handoffs, late jobs, the owner pulled in to rescue outcomes. If a process going sideways shows up on your issues list within a week, it is high pain.

Lives in one head is the quiet axis. The test: if that person handed in two weeks notice this afternoon, could anyone else run the process by Friday? If the honest answer is no, that is concentrated risk, whether or not it has burned you yet.

The high-high square is remarkably predictable by industry. In trades and home-service companies it is almost always estimating or job handoff. In agencies it is client onboarding. In distribution it is quoting and purchasing. Different businesses, same shape: the process that makes the money runs through one irreplaceable head.

The same two axes work outside EOS; the longer method is in what processes to document first.

Your Next 90 Days, Week by Week

The 90-day plan has three phases: weeks 1 and 2 to identify and prioritize at your leadership Level 10 Meeting™, weeks 3 through 10 to build one process at a time in working sessions, and weeks 11 through 13 to package everything and train the team against it.

If those phases sound familiar, they should. EOS Worldwide's free 3-Step Process Documenter™ prescribes the same arc: identify, document, package. This plan is that arc with a calendar, a triage order, and named roles attached, which is exactly what the download leaves out.

Notice the altitude: this plan produces two to four finished processes, not ten. Finished means documented, trained, and measured. A finished process changes how the company runs and how the next Checkup reads; a draft changes nothing.

Weeks 1 and 2: Identify and Prioritize at the L10

Put a 90-minute working block on the calendar in week one. You can run it inside your L10 if you protect the time, but most teams do better with a separate session and a two-minute report back at the L10.

The deliverables coming out of weeks 1 and 2:

• The named list of your 6-10 core processes, in the plain language your team already uses.
• A triage rating for each one, straight from the two-axis table above.
• Your first three targets, in order.
• For each target, a process owner and a pen-holder.

Two Jobs, Two People

The process owner is the person who does the work and talks. The pen-holder is the person who writes. Assign both jobs to one person and you get the blank-page problem: an expert who cannot start writing, or a writer who does not know the work. Split them, every time.

And set the Rock language while you are in the room: not "document our core processes" but "processes one and two documented, trained, and on the Scorecard." That is a Rock you can actually IDS when it slips.

Weeks 3 Through 10: One Process at a Time

Run a two-week cycle per process. Session one, 60 to 90 minutes: the process owner talks through the work start to finish, real examples on the screen, while the pen-holder captures the major steps. Session two, a week later and half as long: the team reads the draft against reality and fixes what the first pass missed. Then it is done. Not perfect. Done.

Hold the altitude. EOS asks for the 20/80 version: the 20 percent of the steps that produce 80 percent of the outcome. That is a 1-3 page document with the major steps and a handful of bullets under each, not a 40-page manual. If your pen-holder wants a starting structure, steal our process documentation template.

The Homework Trap

The working session is the method. The moment documentation gets assigned as homework between meetings, you have rebuilt the exact Rock that failed last quarter. Nobody writes processes alone at 4pm on a Friday. The pen moves inside the session or it does not move.

At that cadence, eight weeks yields four finished processes; slip a cycle and you land at three. Either number transforms the component and the next Checkup with it, because you are not documenting alphabetically. You are removing your biggest operational threats in order.

Weeks 11 Through 13: Package and Train

Packaging means one home, one format, findable in two clicks. The tool you already have is fine to start. Software stores processes; it does not extract them, so do not let a platform evaluation eat the back half of your quarter.

Then train against the document, thirty minutes per process: the process owner walks the team through it, the team pokes holes, and the pen-holder fixes the draft in the room. From that day forward the document is the answer: "great question, what does the process say?" If the document cannot answer, it gets updated the same week. That is how it stays alive.

How to Make the Process Score Move by the Next Checkup

Wire every documented process to a number on your Scorecard. Followed By All™ is a measurement claim, not a feeling, and the FBA checklist is simple: train the team on the process, measure it with a weekly number, manage to it through LMA, and update it when reality changes.

Run each finished process through the four steps:

1. Train. Everyone who touches the process gets trained against the document, not the tribal version. New hires learn from the document on day one, which is the moment training stops dragging.
2. Measure. Every core process gets one Scorecard number a human can report weekly: days to first deliverable for onboarding, percent of invoices collected inside terms for collections. If you cannot name the number, you have not decided what the process is for.
3. Manage. This is LMA. Leaders hold their people accountable to the process, and a drop in the measurable becomes an issue on the list, not a private frustration.
4. Update. When reality changes, the document changes the same week. A stale process document teaches the team to distrust all of them.

Do this and the next Checkup takes care of itself. Your leadership team answers the Process questions differently because they watch processes being followed and measured every week, not because anyone coached the score. Chasing the Checkup number without the behaviors just gets you a dishonest 65. The full playbook is in how to actually measure Followed By All.

What If Your Team Has Zero Capacity for This?

If your leadership team genuinely cannot free up the hours, stop pretending next quarter will be different and make the outsource decision honestly. The work splits cleanly: your people supply the knowledge in short interviews, and an outside pen-holder does the extraction, drafting, and packaging. Buying capacity is not cheating.

Run the honest test first: how many quarters in a row has Process been your lowest Checkup score? If the answer is two or more, the constraint is capacity, not commitment, and recommitting harder at the next quarterly does not change the math.

Only your team can supply the knowledge, decide what counts as core, and follow the processes once they exist. Everything else transfers: interviewing, drafting, formatting, packaging, training materials. Your process owner talks for an hour per process; someone else does the rest.

You would never hand payroll to a department head as a side project, and extraction is the same kind of specialized work: part interviewing, part distilling, part knowing what altitude to write at. It is also the business The Systems Effect is in, so weigh our bias, then read our honest breakdown of documenting your core processes yourself versus hiring it done, including when you should keep it in-house.

Frequently Asked Questions

We run on EOS and our Process Component score is 40 percent. Everything else is above 80. What should we do this quarter?

Do not set a Rock to document everything. Spend the first two weeks listing your 6-10 core processes and triaging them by pain and key-person dependence at your leadership L10. Then build one process at a time in working sessions for eight weeks, and use the final three to package and train. Two to four processes documented, followed, and measured will move the Checkup score more than ten drafts nobody opens.

What does a low Process score on the Organizational Checkup actually mean?

It means the company runs on individual habits instead of one agreed way. Operationally that shows up as an inconsistent customer experience, quality that depends on who is working that day, slow training because new hires learn by shadowing, and key-person risk because critical knowledge lives in a few heads. The Checkup score is your own leadership team reporting those symptoms.

How many core processes should we document in one quarter?

Two to four, done properly, is a realistic quarter for a leadership team that is also running the business. EOS says most companies have 6-10 core processes total, but trying to document all of them in 90 days is exactly the overreach that kills Process Rocks. Pick the highest-pain, most head-dependent process first and work down the triage list.

How do we make the Process score move by the next Organizational Checkup?

Change what your leadership team observes, and the Checkup score follows. Each documented process needs a Scorecard measurable, a trained team, and a manager holding people to it through LMA. When leaders see processes being followed and measured every week, they answer the Checkup questions differently. Chasing the number without the behaviors just produces a dishonest score.

Can we fix the Process Component without an EOS Implementer?

Yes. An implementer facilitates the framework; the Process Component is execution work either way, and most implementers will tell you they do not hold the pen. What you need is extraction and packaging capacity: someone who interviews the people doing the work, drafts at the 20/80 altitude, and packages the result. That can be an internal pen-holder or an outside partner.