The 20/80 Rule in Practice: What the 20% Actually Looks Like (Real Examples)

Document the 20 percent of steps that produce 80 percent of the results. Everyone repeats the rule. Here it is, three times over, at the correct altitude.

The 20/80 rule in EOS® says to document the 20 percent of a core process, the major steps, that produce 80 percent of the results, on one to three pages. Everyone repeats the instruction. Almost nobody shows a finished example, so owners nod along, open a blank page, and stall. Below are three complete core processes at true 20/80 altitude: sales, client onboarding, and hiring, each a generic composite drawn from patterns across our client documentation work.

What the 20/80 Rule in EOS Actually Instructs

The 20/80 rule instructs you to document the 20 percent of each core process that produces 80 percent of the results: the major steps, in order, with a short standard under each. Not the keystrokes, not the scripts. Six to ten steps, one to three pages, per core process.

One clarification, because it is the most common misreading of the rule: the 20 percent refers to the steps inside each core process, not to a subset of your processes. You still document all 6 to 10 core processes. Each one just gets captured at the depth of its vital few steps, the ones that drive 80 percent of the results.

The rule lives in step two of the 3-Step Process Documenter™: identify your core processes, document each at 20/80, then package them and get them Followed By All™ (FBA). It exists because the Process Component™ is where companies running on EOS stall hardest. In Traction, Gino Wickman calls Process the most neglected of the Six Key Components, and the reason is almost always altitude: leaders either write everything down and drown, or write four vague bullets and quit. We cover the full component, and the 80 percent strength bar, in our guide to the EOS Process Component.

Here is the part everyone misses: 20/80 is not about having less detail. It is about where detail lives. The screenshots and scripts your team genuinely needs do not go away. They move one layer down, into SOPs and checklists hanging off individual steps. The core process is the skeleton, written for two readers: the new hire who needs to navigate, and the leader who needs the whole machine at a glance. We made the general argument in our piece on 80/20 process documentation. EOS just gives the principle a number, a page count, and a quarterly cadence.

The Test: Does a Step Make the 20 Percent?

A step belongs in the 20 percent if it passes at least one of three tests: the outcome breaks when it is skipped, a new hire needs it to navigate, or leadership needs it to spot where work stalls. Fail all three, and the step moves down a layer or disappears.

Handoffs and decision points pass almost every time, which is why they anchor the examples below. Wherever work changes hands or the path forks is where processes stall. Tool clicks, phrasing, and formatting preferences fail every time, and all of it belongs a layer down.

Example 1: A Sales Process for a Service Business

Here is a complete sales core process at 20/80 altitude: seven steps on one page, each a verb with a one-line standard. It is a generic composite built from patterns across the sales processes we have documented for service businesses, and it is attributed to no single client.

1. Capture the lead.Every inquiry lands in the CRM the same day it arrives, tagged with its source.
2. Qualify within one business day.A 15-minute call scored against the written fit criteria, with a fast, kind no for anyone who fails.
3. Book discovery before hanging up.The qualifying call ends with a meeting on the calendar, not a promise to circle back.
4. Run the discovery meeting.Scope the problem, the budget range, the timeline, and everyone who touches the decision.
5. Send the proposal within two business days.Built from the standard template and priced from the current rate sheet, no freelancing.
6. Follow up on the set cadence.Scheduled touches until the answer is a yes, a no, or a dated future conversation.
7. Close and hand off.A signed agreement triggers the client onboarding process, with a written handoff note to delivery.

Notice what is missing: no talk tracks, no objection handling, no CRM screenshots. All of that exists one layer down. A new salesperson can walk this page on day one; the owner can find where deals pile up in one glance. That is the 20/80 altitude doing its job. And when the process goes live, one number from it goes on the Scorecard, proposals sent within two business days is the usual pick, so following it stays visible every single week.

Example 2: A Client Onboarding Process

This client onboarding core process runs eight steps on about a page and a half, at the same 20/80 altitude. It is another generic composite, drawn from patterns across the onboarding processes we have documented and attributed to no client. Onboarding deserves special care at this altitude because nearly every step is a handoff.

1. Trigger: deal marked Closed Won.Onboarding starts the moment the deal closes; the account manager owns it from here.
2. Take the sales handoff within one business day.What was promised, what the client actually wants, and any sensitive context on record.
3. Send the welcome and book the kickoff.Welcome email out the same day, kickoff call on the calendar within five business days.
4. Run the kickoff call.Goals, timeline, points of contact, and exactly what the client owes you by when.
5. Set up the account.Folder built, access granted, billing live, and the project plan drafted before any work begins.
6. Deliver a visible win inside 30 days.One agreed early deliverable, because client confidence decays fast in silence.
7. Hold the 30-day check-in.Expectations versus reality in the client's own words, logged where leadership can see it.
8. Transition to steady-state delivery.Recurring cadence set, onboarding closed out, and the delivery team fully briefed.

The Zoom-In: What Hangs Beneath Step 4

Step 4 says "Run the kickoff call" and gives it one line. That is all the core process should say. But the account manager running her first kickoff needs more than a line, and this is the layering move. Beneath step 4 hang two artifacts:

Layer	The Artifact	What Lives There
Core process (this page)	Step 4: Run the kickoff call	The what and the when, in one line, visible to leadership every quarter.
SOP	"Run a Client Kickoff Call," one to two pages	The how: agenda, talk track for awkward moments, what gets sent within 24 hours, edge cases.
Checklist	Kickoff checklist inside the project tool	The runtime: boxes ticked for every client, every time, with no rereading required.

One altitude per artifact, each written for its reader. When your ops manager says the team needs more detail than 20/80 allows, they are right about the team and wrong about the document. The detail belongs beneath the step, not inside it. We unpacked the full stack in core process vs SOP vs checklist, and our three complete SOP examples include a client onboarding SOP that sits one layer beneath a step exactly like this one.

Example 3: A Hiring Process

The hiring core process below is eight steps on roughly one page, a generic composite of the hiring processes we have documented across service and trades businesses, attributed to no named client. Hiring is the process owners over-document most, because every step feels weighty and none feel safe to leave out.

1. Define the seat.Roles, measurables, and compensation range approved in writing before anything gets posted.
2. Post and source.The ad goes live on the standard channels the same week, and the referral ask goes out to the team.
3. Screen against the must-haves.Applications scored on the written criteria, and the shortlist gets a 20-minute phone screen.
4. Run the skills interview.The hiring manager digs into track record plus one work sample relevant to the seat.
5. Run the values and GWC™ interview.A second leader tests core values fit and whether they get it, want it, and have capacity.
6. Check references before any offer talk.Two references minimum, called rather than emailed, with notes logged.
7. Make the offer.Verbal first, written within 24 hours, with the start date and 90-day expectations attached.
8. Hand off to onboarding.A signed offer letter triggers the new-hire onboarding process, with a named owner.

Eight steps at 20/80 carry an entire hiring function. The scorecards, reference call script, and offer letter template are all real, all one layer down, reachable from the step they serve.

The Three Ways People Break the Rule

Teams break the 20/80 rule in three predictable ways: writing the 80 percent because thorough feels responsible, writing bullet fragments too vague for anyone to follow, and documenting the process they wish they ran instead of the one they actually run. Each failure kills the document in a different way.

1. Writing the 80 Percent Because It Feels Thorough

This is the ops manager who took the Rock seriously and produced 40 pages. The work ethic is admirable. The artifact is a wall. Nobody opens 40 pages mid-task, no leadership team re-reads them quarterly, and the document goes stale within a month. Length reads as rigor while it functions as burial. The tell: if a core process cannot be read aloud at a leadership meeting in five minutes, it is an SOP library wearing the wrong name.

2. Writing Fragments So Vague Nobody Can Follow Them

The opposite failure: a slide that says Market. Sell. Deliver. Invoice. It passes the page-count test and fails every other one. A new hire cannot navigate four nouns, leadership cannot spot a stall inside a single word, and you cannot measure whether a word is followed, which kills FBA before it starts. The 20/80 bar for each step: a verb plus the one standard that makes it real. "Qualify within one business day against the written fit criteria" can be checked. "Sales" cannot.

3. Documenting the Aspirational Process Instead of the Real One

The sneakiest break: the document describes the company you wish you ran. The QA review nobody performs. The CRM hygiene nobody keeps. The weekly check-in that has happened twice, ever. It feels like vision while you write it. Your team reads it as fiction, and quietly files everything around it as fiction too.

How to Distill a 40-Page Doc Back to 20/80

To compress an overgrown process document back to a 20/80 skeleton, extract the verbs, keep the decision points and handoffs at the top layer, and push everything else down into SOPs and checklists. Nothing is wasted. The 40 pages stop pretending to be a core process and become the raw material for the layers beneath one.

1. Extract the verbs.Read the document once and pull out every sentence where somebody actually does something. List the actions in order and ignore everything else.
2. Cluster the verbs into 6 to 10 major steps.Related actions collapse into one step named for its outcome. Forty micro-actions usually hide seven real steps.
3. Keep every decision point and handoff.Anywhere the path forks or work changes hands stays at the top layer. Stalls live at handoffs, and leadership needs to see them.
4. Push everything else down a layer.Screenshots, scripts, settings, and field-by-field instructions become SOPs and checklists linked from the step they serve.
5. Test at both altitudes.A new hire should navigate from the top page alone. Leadership should find a stall in ten seconds. If either fails, adjust.

This is usually what being stuck on step two of the Process Documenter looks like: not a lack of effort, but a document that grew past the 20/80 altitude where anyone could use it. If that is where your team stalled, here is why teams get stuck on step 2.

Keeping 20/80 Docs Alive

A 20/80 document stays alive through two disciplines: a quarterly review, where each process owner confirms or corrects the document, and the Update discipline, where the document changes the same week the process does. Skip both, and the document drifts back into fiction within two quarters.

The quarterly review is where 20/80 quietly pays for itself. Reviewing a two-page process takes fifteen minutes: a document leadership can actually re-read is a document that can stay true. Give every core process one owner, put the review on the quarterly agenda, and ask one question per process: is this still how we do it?

The Update discipline covers the weeks in between: change the process, change the document the same week, and announce it rather than bury it. Then wire each process to a number your Scorecard already watches, so following it is visible instead of assumed. That is the whole art of FBA, and we covered how to measure Followed By All without becoming the process police separately.

That is 20/80 in practice: a handful of short documents at the right altitude, layered artifacts beneath them, and two small disciplines that keep them true. One to three pages, not 123.

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.