What it is: The Process component of EOS is about identifying, documenting, and consistently following the small set of core workflows that drive your business.
Why it matters: When your key processes are clear, owned, and followed by everyone, your business stops depending on individuals and starts running as a system.
What “done” looks like: 5 to 12 core processes documented at the right level, each with one clear owner, trained across the team, and improved over time.
What are core processes in EOS®?
Most companies think they have processes.
What they actually have is tribal knowledge.
“Ask Sarah how we do invoicing.”
“Tom usually handles that part.”
“I think marketing did something similar last year.”
That works when you have ten people. It breaks the moment you try to scale.
We learned this firsthand building FAQs about the EOS® process at teamwork.com. As the company grew from a small team to over 300 people, every new hire asked the same question: “How do we actually do this here?” Sales had one way of qualifying leads. Customer success had a different approach to onboarding clients. Marketing campaigns were run differently every time, depending on who was involved. Nobody was doing anything wrong. There just wasn’t one agreed way.
Once we documented our core processes, things changed fast. New hires ramped up quicker. Mistakes dropped. Teams stopped reinventing the wheel every week. That experience shaped everything we built into the Process component at Success.co.
Core processes are the small set of repeatable, company-critical workflows that consistently deliver value. Most cross departments and often touch the customer experience directly. They should be clear enough to teach and simple enough for anyone in the right seat to follow.
What core processes are not:
Rare situations that only happen once or twice a year
Long, detailed SOPs that read like a training manual
Brain dumps of tribal knowledge that only one person understands
Complex process maps with dozens of branches and decision trees
How many EOS® core processes do you need?
Most companies need a handful of core processes, not a huge library. The right range is usually between 5 and 12, depending on the complexity of the business. The exact number matters less than the discipline behind it. Too few and things stay unclear. Too many and you end up with a document graveyard no one reads or updates.
At Success.co, we landed on six core processes for our own operation: Sales, Marketing, Onboarding, Customer Success, Product, and Finance. Each one crosses seats and functions. Each has a single Champion who owns it. That’s the standard we built into the Process feature, because it’s what actually worked for us.
Typical core processes for most EOS® companies include:
Sales process
Marketing process
Operations / delivery process
Customer onboarding process
Finance process
People / HR process
The EOS® 3-step process documenter
This is the part many teams get wrong. Process documentation should be a leadership responsibility, not a side project. It fails when no one truly owns it, when it’s written at the wrong altitude, or when the team is never trained on it. Here’s how to do it right.
Step 1: Identify the 20% that drives 80%
The goal is to document the smallest version of each process that still produces consistent outcomes. Before you write a single step, scope it correctly:
Define start and end boundaries: What triggers the process? What does “done” look like?
Name the owner: One person, even if many people execute steps within it.
Agree on success criteria: If you can’t define done, you’ll document forever.
Cut the noise: If it’s rare or only relevant once a year, it’s an exception, not part of the core process.
When we built the Process feature, our first prototype included branching workflows, nested sub-processes, and complex approval chains. We scrapped the whole thing. We came back to a principle we believe in deeply: simple software that everyone uses is far better than complex software that only a few people touch. The same logic applies to process documentation itself.
Step 2: Document it in 5 to 15 high-level steps
This is where teams either keep it simple or make it too complicated. The right level of detail feels clear and practical:
Each step starts with an action word: collect, confirm, approve, send, review, record.
Every step can be explained in a sentence or two.
A capable person should be able to follow the process without needing extra meetings to interpret it.
If your process has more than 15 steps, you’re writing a detailed SOP rather than a core process. That’s your signal to split it up or move up a level of abstraction.
In Success.co, when you add a new process you give it a title, assign a Champion, and set the audience (which teams or seats need to read it). You can attach images, embedded videos, files, and links to each step, but the discipline is always: key steps only. The built-in AI integration is genuinely useful here. Describe your process in a sentence or two and you get a structured draft in seconds - which you then edit to match how your company actually works.
Step 3: Package, communicate, and make it the way we do things
A documented process that is not trained and reinforced is just a file sitting somewhere. For it to actually work:
Train the team when the process is first created.
Reinforce it quarterly: reference it in your L10 meetings when relevant issues come up.
Revisit it any time recurring issues start to appear.
Keep it in one clear place where everyone can find it without hunting through old email threads.
Make updates simple and owned, the Champion should update it, not a committee.
Here’s what this looks like in practice. Imagine your customer onboarding process has five steps:
Sales hands the customer over with a completed handover note.
Customer Success schedules the kickoff call within 24 hours.
Implementation checklist completed by Day 7.
Customer activated and hitting first milestone by Day 14.
30-day check-in scheduled and completed.
When that’s documented and every customer-facing team member has read and confirmed it, every customer gets the same great experience. Not five different versions depending on who’s handling the account that week.
This is where the Success.co Process feature earns its keep. Every time a process is updated, everyone who needs to read it is notified and their read status resets.
The Followed by All view shows you real-time adoption across the team: overall stats, team read status, and which processes are most engaged with. It turns “we wrote it down” into “we can prove people have read and are following it.”
Validated by the people who wrote the book
We shared the Process feature with Mike Paton and Lisa González, authors of the "Process!" book before launching. Their verdict? Enthusiastic approval. Try it yourself and see why it passed the toughest test.
EOS® process documentation template
Use this template to document your core processes at the right level. The goal is clarity and usability, not comprehensiveness.
Process name e.g. Sales Process, Hiring & Onboarding
Owner / Champion One person accountable for this process
Purpose One sentence: what this process is designed to deliver
Start / Trigger What event kicks this process off?
End / Success criteria How do you know it's done correctly?
Steps (5–15) List each step starting with an action verb
KPIs / Scorecard measurables The numbers this process should move
Revision date / Change log Date last updated and what changed
EOS® process documentation example
These examples show what “finished” looks like. The right version for your company will reflect your industry, systems, and risk tolerance - but the altitude should feel like this.
Process name: Hiring and Onboarding
Owner: Head of People (or assigned HR Process Champion)
Purpose: Consistently hire the right people and onboard them to productivity
Start / Trigger: Approved headcount or role opens
End / Success criteria: New hire completes onboarding and meets 90-day expectations
Steps:
Confirm role need, success profile, and scorecard expectations.
Draft or update job description with outcomes, not just duties.
Post role and activate sourcing channels.
Screen applicants against must-haves (skills, values fit, baseline requirements).
Conduct structured interviews using consistent questions and scoring.
Complete reference checks and any required background steps.
Make offer, confirm start date, and document compensation terms.
Prepare onboarding plan: access, tools, training schedule, first-week outcomes.
Run Day 1 onboarding: culture, expectations, role clarity.
Complete role training milestones in the first two weeks and confirm early wins.
Conduct 30/60/90-day check-ins tied to the role scorecard.
Confirm 90-day success and agree on next development plan.
Measurables:
Time-to-fill (role open to accepted offer)
90-day retention rate
Onboarding completion rate by Day 14
New hire 30-day productivity milestone hit rate
Common EOS® process mistakes and how to fix them
Most EOS® struggles are not unique. The same patterns show up again and again - and once you can name the problem, you can correct it quickly.
1. Treating EOS® as a meeting cadence, not a system
Symptom: Great sessions, no change in weekly behaviour.
Why it happens: The team confuses attendance with execution. Showing up to the L10™ feels like doing EOS®.
Fix: Tie every meeting output to ownership and deadlines. Every IDS™ resolution should produce a Rock™, a To-Do, or a process update. In Success.co, the meeting tool captures these in real time so nothing falls through the cracks.
2. Documenting processes before the foundations are solid
Symptom: Beautiful docs, low usage, quiet resentment.
Why it happens: The team tries to standardise before roles, priorities, and expectations are clear.
Fix: Get your Accountability Chart™ right and stick to a steady 90-day Rock™ cadence first. Then document the processes that keep showing up on your Issues list. Processes built to solve real, recurring problems get used. Processes built in a documentation sprint often don’t.
3. Documenting at the wrong altitude
Symptom: 30-step procedures no one trains on or follows.
Why it happens: Teams confuse core processes with SOPs. They write everything they know rather than the key steps a capable person needs.
Fix: Keep each process to 5–15 clear steps. If you need more detail, put it in training materials or link to an external tool like Playbook Builder. The core process in Success.co stays clean. The depth lives elsewhere.
4. No true process ownership
Symptom: Everyone owns it means nobody maintains it.
Why it happens: Ownership feels political or uncomfortable to assign clearly.
Fix: Assign one Champion per process. In Success.co you can link the Champion directly to a seat on the Accountability Chart™ - which makes it a role expectation, not a favour. The Champion is responsible for keeping it accurate, training the team, and improving it over time.
5. Quarterly sessions becoming status updates
Symptom: Lots of reporting, few decisions, the same issues recurring.
Why it happens: Leaders avoid conflict and substitute updates for solving.
Fix: Timebox the updates section. Spend most of your Quarterly time on IDS™ - identifying root causes, making real decisions, and resetting Rocks™. If a process keeps generating issues, that’s your signal to update it before the next quarter.
Run your EOS® Process the right way
Success.co is an officially licensed EOS® platform built to help leadership teams run EOS® in one place. It brings your V/TO™, L10 Meetings™, Rocks™, Scorecards, Accountability Chart™, and Process documentation together so your team always knows what matters, who owns what, and how the work gets done.
The Process feature completed the full EOS® toolset inside Success.co in January 2026. It was built from scratch twice - the first version was too complex. We rebuilt it around simplicity and adoption, listened to the Process! book, and had Mike Paton and Lisa González validate the result. Every feature reflects a deliberate choice: keep it simple enough that everyone will actually use it.
Key Process features in Success.co:
Visual process library with filters by team, seat, Champion, and status
Followed by All tracking - see who has read each process in real time
Version history with change tracking
Link processes to Scorecard measurables
Built-in AI to draft, simplify, or improve any process
Printable process books with cover page and table of contents
Full MCP connector for ChatGPT and Claude - ask AI to query your processes directly
Ready to take the friction out of your EOS® process?
Success.co brings your vision, meetings, priorities, and accountability into one tool your team will actually use. Try the Process feature free, no setup required.
How to get Follow-by-all with Success.co
Documenting your processes is only half the battle. The step that most teams skip - and where EOS® implementations most commonly fall down - is actually getting every person in the business to read, understand, and follow those processes.
A process that lives in a document no one reads might as well not exist. Leadership can do all the right work to document and simplify, but if there’s no way to track whether the team has engaged with that work, accountability disappears and old habits return.
Success.co makes this easy. The Follow-by-all tracking feature gives leaders a real-time view of who has read each process across the entire organisation. You can see adoption at a glance, drill down by team or individual, and spot exactly where the gaps are - without chasing people manually or relying on gut feel. When a new process is published or an existing one is updated, the system resets read status so nothing slips through the cracks.
Overall adoption stats
Team read status
Most read processes
Filters by team and individual
FAQs about the EOS® process
How many core processes should we document?
Most companies land between 5 and 12, depending on how complex the business is. Start with the processes that cause the most problems when they’re done wrong. You can always add more later, but starting with too many is a common reason teams abandon the exercise entirely.
How often should core processes be reviewed?
At minimum, revisit them quarterly or any time recurring issues start to appear. If a process keeps generating items on your Issues list, that’s a direct signal it needs to be updated. In Success.co, you can link processes to specific Scorecard measurables — so a dip in a number can trigger a direct review of the process that’s supposed to drive it.
Who should own the core processes?
Each process needs one clear Champion, typically the person in the leadership seat most closely tied to that area of the business. That person is responsible for keeping the process accurate, training the team on it, and improving it over time. In Success.co, the Champion is displayed on every process view and linked to the relevant seat on the Accountability Chart™.
What if our team already has SOPs - do we start over?
No. Your existing SOPs can often become the detail layer that sits behind a core process. The core process in Success.co captures the 5–15 key steps and links out to the deeper SOP for anyone who needs it. This approach, which we recommend alongside tools like Playbook Builder for teams that need advanced documentation, keeps the core process clean while preserving the depth elsewhere.
