Core Processes are your company’s “Way” — the handful of processes that represent how you consistently deliver value to customers and run your business. In the EOS methodology, these are the 20% of processes that drive 80% of your business results.
According to EOS principles, most businesses have 5-7 core processes that fall into these categories:
Marketing Process: How you generate awareness and leads
Sales Process: How you convert prospects to customers
Operations/Delivery Process: How you fulfill your product or service
Accounting Process: How you manage financial operations
Human Resources Process: How you hire, develop, and retain people
Customer Retention Process: How you keep customers happy and loyal
Why EOS Core Process Documentation Works
The EOS approach succeeds where other methods fail because of its:
Simplicity: Focus on core processes, not every minor task
Visual Format: Easy-to-follow documentation that anyone can understand
Integration: Links to your EOS Rocks, Scorecard, and Accountability Chart
Practical Application: Designed by operators for operators, not consultants
Core Process vs Subprocess
Strety allows you to create both distinct EOS process types:
Core Processes: The 5–10 high-level, essential workflows that define how a business operates and are documented using the 20/80 rule to ensure consistency.
Subprocess: A specific, detailed SOP (standard operating procedure), nested within a Core Process that provides the step-by-step checklists in how to perform those tasks/responsibilities
How to Create a New Core Processes
Core Processes are almost always created within your Leadership team space. Once created, you can share processes into additional team spaces for added visibility & access
To create a new Core Process click Create
You can start from scratch or use one of our 6 pre-built templates as a starting point
Give your Core Process a Title, Description, and Owner and click Create
How to Add Subprocesses, Steps, & Substeps
Core Processes are broken down into subprocesses & steps
Subprocesses represent a handful of high level groups or categories that make up your Core Process.
Steps represent the tasks or responsibilities associated with each Subprocess. Think of these as a task checklist
Subprocess Phases & Definitions
The following (3) phases makeup EOS's Three-Step Process Documenter designed to provide a simple, standardized approach to systemize your business
1) Identify: List all major workflows (typically 5–12) that define how the business operates - the 20% that creates 80% of the results. In this phase, you're simply identifying those critical processes
2) Document & Simplify: In this phase, you're beginning to build out the steps in your processes so it can be followed and practiced by every member of your organization
3) Package: Create a visual process document that is easy to find, easy to follow, and easy to use. In this phase, you publish your process so that you can begin to use it to train others
EOS uses the FBA Checklist (Followed By All) to ensure existing processes are effective, current, and followed by everyone. Here are the 4 phases of the FBA Checklist
1) FBA: Train: Train everyone on the steps & substeps of your process
2) FBA: Measure: Track & measure compliance and performance using the Scorecard
3) FBA: Manage: Manage your team to ensure adherence to processes
4) FBA: Update: Keep your process updated with any changes to process
How to Publish a Core Process
When you're ready to make a Core Process visible to your entire organization, you can click Publish
Only Account Owners & Admins can publish a Core Process
Publishing a process saves a snapshot of the process under your Company tab's The [your org name] Way section.
In this section you'll see all published processes that everyone in your organization can view
How to Share Core Processes with Additional Team Spaces
Use the Spaces shared with feature and provide additional teams the ability to edit, update, and comment on your Core Processes
How to Link Rocks & Measurables to Core Processes
It's expected to have Rocks associated with Core Processes. Common examples include:
Documenting Processes: A primary quarterly rock is often to document 5-15 steps of a vital process (e.g., hiring, billing) for consistency.
Improving Processes: Rocks meant to "fix" or update broken or inefficient core processes identified in the company's V/TO™ (Vision/Traction Organizer).
Each Core Process should also have measurable outcomes that become metrics on your weekly EOS Scorecard, creating accountability and visibility
Click on the (+) sign at the top of your Core Processes to link Rocks and/or Measurables to your Core Processes
Click Manage to view the associated items
How to Rename the Core Processes Display Name
Out of the box, we display your published Core Processes under the Company tab as The [Company Name] Way.
To edit the display name of your published Core Processes, click into the The [Company Name] Way folder and click into the page's header to enable editing:
Update the title of the page
And you'll see the new name reflected in the Company tab
Supplemental Resources
Want to learn more? Check out these relevant Core Process resources from Strety's Blog
EOS Core Process: Step-by-Step Guide + Free Templates: Learn what Core Processes are, why they are important, and how to implement them throughout your organization + best practices & templates!
How to Document your Processes in Strety by Lisa Gonzalez (Watch): Lisa Gonzalez is the co-author of the book Process: How Discipline and Consistency Will Set You and your Business Free. Watch as she introduces how to use Strety's process tool document core processes
Core Process Best Practices
Below are a handful of examples of common implementation mistakes. Using Strety to document your processes will help you avoid:
1. Over-Complicating EOS Core Process Documentation
Problem: Creating complex flowcharts instead of simple EOS format
Solution: Follow EOS Three-Step Process Documenter
Best Practice: If it takes more than 10 minutes to understand, simplify
2. Ignoring EOS Tool Integration
Problem: Treating core processes as separate from EOS implementation
Solution: Connect every process to Scorecard metrics and Rocks
Best Practice: Every EOS core process should have measurable outcomes
3. Wrong EOS Core Process Focus
Problem: Documenting too many processes instead of focusing on core
Solution: Strictly limit to 5-7 most important processes
Best Practice: Use 80/20 rule religiously — core processes drive most results
4. Lack of EOS Core Process Accountability
Problem: Creating processes without clear ownership or follow-through
Solution: Assign owners from Accountability Chart and track in Level 10s
Best Practice: Include process performance in People Analyzer reviews.