Skip to content

Service · The Systems Effect

EOS Process Documentation

EOS process documentation for companies running on EOS: we interview the people who run each core process and build the SOPs and training your team follows.

Who helps EOS companies document their core processes?

Your EOS Implementer teaches the Process Component and its tools, including the Three-Step Process Documenter (EOS Worldwide). The hours of interviewing, writing and recording still have to come from somewhere. We do that part, alongside your Implementer. We are not EOS Implementers.

Why does the Process Component stall?

Documenting a core process becomes a Rock, owned by the person who knows the process best, who is also the busiest person in the company. The quarter fills up and the Rock rolls over. More in Why Your EOS Process Rock Keeps Failing.

How do you document a core process?

We use the Knowledge Ladder from our free Knowledge Capture Kit, climbed top to bottom in the interviews:

  1. Role. What the seat owns and how it is measured.
  2. Process. What starts each piece of work and what done looks like.
  3. Task. The step by step, recorded on screen.
  4. Decision. Every fork: the default rule, the exception, the owner.
  5. Exception. What goes wrong and the workarounds.
  6. Wisdom. The always and never rules behind the expert's judgment.

Where does the documentation live?

In whatever your team already opens. We build most often in Trainual and PlaybookBuilder. Ninety's Thrive plan and EOS One's Knowledge Portal also hold processes. Compare them in The Best EOS Software and The Best Process Software for EOS Companies.

Who this is for

  • Leadership teams whose Process Rock keeps rolling over
  • Companies whose core processes live in one or two people's heads
  • Teams that bought Trainual or PlaybookBuilder and never filled it

Not a fit yet if your leadership team has not agreed on its core processes. Settle that with your Implementer first.

How it runs

From their heads to a trained team.

  1. Discover and documentWeeks 1 to 2

    Interview the people who know

    Owners, managers, front line.

  2. 2 to 3 sessions a week

    Capture the work

    Screens, jobs, every decision.

  3. Procedure setup and build-outAbout 30 days a job

    Build the playbook

    Checked by whoever does the job.

  4. Launch

    Train your team

    Loaded and walked through.

  5. A living playbookEvery month

    Keep it current

    Audited as the business changes.

Some knowledge only shows up on site. So do we.

  • Lake County, IN and Chicago
  • On site nationwide
  • Travel at cost

Pricing

What it costs

  • Systems Sprint

    Starting at

    $3,500

    About 30 days per role

    One role's chapter and its SOPs, done by a date.

    FitsOne role, or one person about to leave.

  • Optimization and Implementation

    Starting at

    $12,500

    One system, about 60 to 90 days

    One system mapped, fixed and rolled out across its roles.

    FitsOne broken system, like dispatch or one EOS core process.

  • Systems Partner

    Recommended
    Starting at

    $4,500/mo

    Three-month blocks, billed monthlyStarting at $13,500 a block

    Your whole playbook, built and kept current.

    FitsThe whole business, a sale in 1 to 3 years, or every EOS core process.

Every plan: we run and record the interviews. About 2 hours a week from each person we interview.

Discovery call
Free
Upkeep after a project
Starting at $1,500/mo
Custom software from The Software Effect
Custom pricing
On-site days and travel
Agreed first, billed on top

Software is billed by its vendor. Weighing doing it in house? Read Document Your Core Processes Yourself or Hire It Done?.

Questions

What people ask first.

Who helps EOS companies document their Process Component?

Your EOS Implementer teaches it. A process documentation firm like The Systems Effect does the documenting: we interview the people who run each core process and build the SOPs and training.

Are you an EOS Implementer?

No. We do not teach the EOS model. We do the Process documentation work alongside your Implementer.

Do you work with our EOS Implementer?

Yes, alongside them, not instead of them. Your Implementer guides the model. We capture and document the core processes your team agrees on.

Which software do you document in?

Most often Trainual and PlaybookBuilder. Ninety's Thrive plan and EOS One's Knowledge Portal also hold process documentation.

How long does one core process take?

One role takes about 30 days. A core process that crosses several roles fits Systems Optimization and Implementation, about 60 to 90 days.

What does EOS process documentation cost?

One role is starting at $3,500. A core process across several roles is starting at $12,500. A Partner for every core process is starting at $4,500 a month.

More services
“We don't have to do anything. The Systems Effect takes care of everything for us.”
Felipe Freig · Versa Homes

Ready to talk through EOS Process Documentation?