Nov 27, 2023 · 25m · founders-journal
How to Use EOS (Entrepreneurial Operating System) to Run & Scale Your Business
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode of Founder's Journal, host Alex Lieberman and serial entrepreneur Michael Girdley deliver a comprehensive breakdown of the Entrepreneurial Operating System (EOS), exploring its core tools, implementation strategies, and advantages over alternative business frameworks.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Alex holds 33.3% of the talking time here. How this is scored →
speaking balance: gold is Alex, purple is the guest (3 minute bins)
Michael forcefully dismisses OKRs as bottom-up chaos and ridicules using Google as a benchmark, arguing that Google could give employees crayons and still succeed because of its money-printing monopoly.
Hardest push from Alex ▶ 9:14 Alex presses Girdley for concrete examples from ScalePathAlex directs Michael away from high-level generalizations by asking him specifically how he implemented the one-page strategic plan in his business ScalePath.
Biggest teaching moment ▶ 4:48 Girdley's breakdown of CEO training and operating frameworksMichael educates listeners on how most business books offer theoretical feel-good advice rather than tactical operating mechanics, explaining how modern business operating systems codify universal best practices.
Alex holds their own ▶ 19:23 Alex's synthesis on abstractable operating principlesAlex demonstrates deep mastery by summarizing how operating frameworks eliminate the need to reinvent the wheel, prompting Michael to praise him and suggest he should teach the concept.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Alex as informed peer | Guest teaching | Guest disagreement | Alex pushing back | Why |
|---|---|---|---|---|---|---|
| Discovering EOS and Comparing Business Operating Frameworks | 4 | 3 | 1 | 0 | Alex explains how Morning Brew used Traction to scale from 20 to 300 employees and prompts Michael on why he favors EOS over other systems. Michael explains that most operating systems share core concepts, comparing them to picking a CRM. | |
| Core EOS Overview and the One-Page Business Plan | 4 | 6 | 1 | 0 | Michael delivers a masterclass on EOS, noting that 80% of business tastes like chicken and outlining the one-page strategic plan. Alex pushes Michael to provide concrete examples from his business ScalePath. | |
| Setting Ninety-Day Rocks and Driving Prioritization | 4 | 5 | 2 | 0 | Alex asks about setting 90-day rocks and goal ownership. Michael details the SMART goal criteria, single ownership rules, and EOS's strict limit of three to seven annual priorities. | |
| Mastering the Meeting Pulse and the IDS Problem-Solving Framework | 4 | 5 | 1 | 0 | Michael introduces the meeting cadence and the IDS (Identify, Discuss, Solve) framework, using a warehouse manager example. Alex chimes in to help define the acronym. | |
| Accountability Charts and Evaluating Personnel with GWC | 5 | 5 | 1 | 0 | Alex asks about seat evaluation and remembers the core elements of GWC. Michael expands on GWC (Gets it, Wants it, Capacity to do it) and contrasts accountability charts with standard org charts. | |
| Scorecards, Documented Processes, and Systematizing Company Health | 6 | 4 | 1 | 0 | Michael touches on scorecards and documenting processes. Alex provides an articulate synthesis on why abstracting operating principles helps founders stack the deck in their favor, earning direct praise from Michael. | |
| Critiquing OKRs and the Superiority of Top-Down Alignment | 5 | 4 | 6 | 0 | Michael delivers a spirited critique of OKRs as bottom-up chaos, pointing out Google's unique monopoly profits. Alex reinforces the argument by distinguishing correlation from causation. | |
| Practical Guide to Implementing EOS and Recommended Resources | 3 | 4 | 1 | 0 | Alex asks how an early-stage founder should begin implementing EOS. Michael advises self-implementing using the book until reaching 25 to 30 employees before hiring outside consultants. |