EOS (Entrepreneurial Operating System)

Definition
A complete framework for running a smaller company, built around six components: vision, people, data, issues, process and traction.

Why it matters

Most owners invent their own way to set goals, run meetings and hold people to account. That works at five people and tends to break at twenty, when the owner can no longer be in every conversation. EOS replaces improvisation with the same routine every week. The value is less the vocabulary than the discipline: a short list of priorities, one meeting slot that never moves, and a habit of raising problems before they grow.

How to apply it

  • Write a one-page vision stating where the company is going and how progress is measured.
  • Draw the Accountability Chart: one owner for each function, and no function without one.
  • Set Rocks, the few priorities that matter most this quarter, and give each one a single owner.
  • Track five to fifteen numbers on a Scorecard that is reviewed every week.
  • Run the Level 10 Meeting weekly, and work through the issues list with IDS.

What it is

EOS was set out by Gino Wickman in his book Traction. It gives an owner-run company a fixed set of tools instead of a homemade system. Each of the six components has its own tools: a one-page plan for vision, an accountability chart for people, a weekly scorecard for data, a list for issues, documented core processes, and quarterly priorities and a weekly meeting for traction.

Common mistakes

  • Adopting the vocabulary without the discipline. A weekly meeting that is skipped when work is busy is not EOS.
  • Setting too many Rocks, so nothing moves.
  • Treating it as software. EOS is a way of working, and a whiteboard or a spreadsheet is enough to start.
Worked example

Suppose a company of thirty people, run by its owner, holds a weekly meeting that drifts into firefighting. Priorities change every month, and nobody can say who owns the hiring plan. The owner adopts the EOS components one at a time. The team writes a one-page vision, names one owner for each function and sets three quarterly priorities, each with a single owner.

Five numbers go on a weekly scorecard, and the issues list is worked through in every meeting. The scorecard and the meeting routine run in Bloom Growth OS, which brings scorecard, meetings, goals and issues onto one platform. After a quarter the meetings end on time, and the same two issues stop coming back.

Tools in the example

Some links are affiliate links: we may earn a commission at no cost to you. It never decides a ranking. How we work with partners

  1. Article

    Operating Cadence

    The wider rhythm of meetings and reviews, of which EOS is one version.

  2. Article

    Objectives and Key Results (OKRs)

    Another way to set and review goals.