Every EOS ® Implementer has seen the same pattern. The Focus Day goes well. The Vision/Traction Organizer is taking shape. The Leadership Team is locked in on the Six Key Components. Then you get to the Process Component™ and watch the wind run out of the sails.
This drop doesn’t come from disagreement in the Leadership Team but rather when someone in the room asks the practical question: how are we actually going to document this, and who has time to do it?
Without a tool that makes documentation fast, findable, and trainable, Core Processes stay on a flip chart. They don’t make it to Followed By All. The Process Component™ becomes the Component the Integrator quietly stops scoring against.
This guide is for Implementers who want to close that gap with their clients. It walks through where Whale fits at every beat of the EOS rhythm, three Whale-specific use cases for an EOS engagement, and how the Whale Partner Program rewards Implementers for the recommendation they were going to make anyway.
Why the Process Component™ is where most EOS engagements stall
W. Edwards Deming put it bluntly decades ago: “94% of business problems result from faulty processes, not people.” EOS gives Leadership Teams the framework to identify those processes. What it doesn’t give them is the tooling.
The gap shows up in three predictable ways:
Most clients leave a Process Component™ working session with a list of named Core Processes and an honest commitment to document them. Six weeks later, three are half-documented in a Google Doc nobody can find, two live in someone’s head, and the rest haven’t been started. The pattern Whale calls process paralysis takes hold: the task of documenting everything is so daunting that nothing gets documented.
When documentation does happen, it usually lands somewhere nobody looks. SharePoint folders, dusty wikis, an inaccessible Notion workspace. Findability is the silent killer of Core Process adoption and the biggest barrier to “Followed by All”.
Even when processes exist and can be found, there’s no mechanism to train against them. Reading a 12-step SOP once does not make a new hire competent. Without assignment, assessment, and review intervals, documentation is a museum exhibit, not a working asset.
The good news: the fix is operational, not philosophical. With the right tool wired into the EOS rhythm, the Process Component™ becomes the Component your clients are most proud of.
What an Implementer needs from a process documentation tool
Implementers don’t sell software. You sell the framework and the discipline. But you do recommend tools to your clients, and the tool you recommend for the Process Component™ has to clear five bars:
-
Fast to capture. Most operators won’t write SOPs from scratch. They’ll record themselves doing the work once if the tool turns that recording into a draft SOP automatically.
-
Faster than asking a colleague. If a team member can’t get to the right SOP in under ten seconds, they will interrupt someone. The compound cost of those interruptions is what process documentation is supposed to remove.
-
Trains, not just publishes. Reading a process once is not the same as being competent in it. Read assignments, quizzes, and training flows turn documentation into onboarding infrastructure.
-
Lightweight enough to honor the 80-20 rule. EOS is clear: focus on the 20% that drives 80% of the outcome. A tool that pushes clients to document everything will collapse under its own weight.
-
A single source of truth. The whole point of the Process Component™ is that the company runs on a shared playbook. If processes live in five places, they live nowhere.
Whale was built around those five requirements. Video-to-SOP and Step Recorder do the fast capture. Alice, the integrated AI assistant, is the findability layer. Training Flows and AI-Generated Quizzes handle training. Expert Review Intervals keep documentation alive. And the platform itself, by design, is the single source of truth.
Fitting a Whale in your EOS rhythm
The mistake most Implementers make is treating documentation as a one-off project. The pattern that actually works is wiring documentation into the EOS rhythm itself. Here is what that looks like at each beat.
Focus Day and Vision Building
By the end of Focus Day, the Leadership Team has named the Core Processes. The natural next step is setting up the structure that will hold them. This is the moment to introduce Whale: open the workspace, create a folder per Core Process, and demonstrate Video-to-SOP on a single live example so the team sees how fast documentation can actually be.
The Implementer move here is small but compounding. Instead of leaving with a flip chart, the team leaves with the bones of their Process Component™ already in the platform they’ll use to fill it in.
Annual
The Annual session is when the Leadership Team revisits the V/TO and sets the rocks for the next 90 days. This is the right time to nominate documentation as a Rock for the Integrator or a Leadership Team member, in line with the approach Whale’s own Lisa Steingold has written about in The Rock You Need to Document Your Processes.
A Process Documentation Rock typically covers three to five Core Processes per quarter. Not all of them. Not none of them. The 80-20 rule applied to documentation itself: the Core Processes most exposed to staff turnover or growth pressure get documented first.
Quarterly Pulsing
Each Quarterly is where the Leadership Team reviews progress against the Rock and adjusts. With Whale, Pulsing on the Process Component™ stops being an opinion exercise. Whale’s reporting shows which SOPs have been read, by whom, and when. Expert Review Intervals flag processes that are due a review.
The Integrator goes into the Quarterly with hard data: documentation coverage, completion rates, and review status. The Leadership Team can make decisions about resourcing the next quarter’s Rock with real evidence.
Weekly L10 ® and IDS
The Level 10 ® Meeting is where the Process Component™ proves itself. When the same Issue keeps appearing on the Issues List week after week, the root cause is almost always a missing or unclear process.
The pattern: identify the Issue in IDS, document the corrected process in Whale during or right after the meeting, assign a read to the affected team members, and move the Issue off the list. The next time the Issue arises, the team has a documented answer rather than a debate.
This loop is where the Process Component™ stops being a quarterly project and becomes part of how the business runs every week.
Three EOS-specific use cases for Whale
Beyond the rhythm, three practical use cases come up in almost every EOS engagement.
Documenting Core Processes. The 20% that runs the business. Whale’s Video-to-SOP turns a 15-minute screen recording into a structured first-draft SOP, which is typically the difference between a process getting documented this quarter or never. Bain & Company research suggests companies that systemize their operations grow 2-3x faster than peers; the Process Component™ is where that compounding starts.
Onboarding new hires. Gallup data shows employees who clearly understand their role and responsibilities are 23% more likely to stay with their company. Training Flows in Whale let new hires move through assigned SOPs in a structured sequence, with AI-generated quizzes confirming comprehension. Onboarding becomes a 30-day plan, not a six-month wait for the new hire to learn through osmosis.
Quarterly process review tied to IDS. The Issues that recur are diagnostic. Whale gives the Leadership Team a way to close the loop: document the fix, train the team, and stop the same Issue from reappearing on the list two months later.
How to get started
Two steps:
-
Try Whale with your next client. See how Whale works in this short video, then open a free workspace during your next Focus Day or Annual and document one Core Process live with the team. The fastest way to know whether Whale fits is to use it on real work.
-
Apply to the partner program. The application takes about 60 seconds. From there your Partner Manager is there to help you along every step of the way.
The Process Component™ is the Component most clients struggle with most. With the right tool wired into the rhythm, it can become the Component they’re most proud of and the one that compounds the value of the rest of your work.
Related reading on EOS and Whale
- How to Strengthen Process in EOS (And Why You Should) by Bram Billiet
- The Rock You Need to Document Your Processes by Lisa Steingold
- How to Systemize Business Process by Bram Billiet
- Whale for Companies Running on EOS
- EOS-aligned process templates
