Implementing EOS and Achieving Your Vision with Dean Breyley

Gray MacKenzie welcomes Dean Breyley, a Certified EOS Implementer and Community Leader at Grow or Die, to explore what separates successful EOS implementations from those that stall out. Dean’s journey started as a marketing agency owner who discovered EOS through Gino Wickman’s book “Traction” and was so transformed by the experience that he became a professional implementer.

Why Some Teams Succeed and Others Struggle

Dean is blunt about the primary reason EOS implementations fail: “If this stuff doesn’t work, it’s the people, it’s always the people.” The EOS framework itself is straightforward. The tools are well-documented. The process is proven across thousands of companies. When it does not produce results, the root cause is almost always a lack of commitment and discipline from the leadership team.

This does not mean the leadership team is bad - it means they have not fully committed to the level of transparency and accountability that EOS demands. Some leaders love the idea of a structured operating system but resist the reality of weekly scorecards that expose underperformance, quarterly rocks that demand completion, and L10 meetings that surface uncomfortable issues. Dean’s role as an implementer often involves helping leaders bridge the gap between wanting EOS and truly embracing it.

The Six Components and Root Cause Diagnosis

EOS organizes a business around six key components: Vision, People, Data, Process, Issues, and Traction. Dean explains that most business problems, regardless of how they present on the surface, trace back to root causes in three areas: process, data, and people. Everything else is typically a symptom.

When an agency is struggling with client retention, for example, the temptation is to look at the retention metric in isolation. But the root cause might be a process issue (inconsistent onboarding), a data issue (no leading indicators to flag at-risk accounts), or a people issue (the wrong person managing client relationships). EOS provides the diagnostic framework to trace symptoms back to their actual causes and address them at the root level.

Building Effective Scorecards

A significant portion of the conversation focuses on the EOS scorecard - the weekly snapshot of business health. Dean is emphatic that scorecards should measure leading indicators, not lagging ones. The question a good scorecard answers is “Did we have a good week?” - not “How did last quarter go?”

For agencies, this means tracking metrics like new qualified leads entering the pipeline, client check-in meetings completed, utilization rates, and project milestones hit - not just monthly revenue or quarterly growth. Leading indicators give teams the ability to course-correct in real time rather than discovering problems after they have already impacted results.

Dean recommends keeping the scorecard focused: five to fifteen key numbers that paint a complete picture of business health. Adding too many metrics dilutes attention and makes the weekly review a data dump rather than a management tool.

Setting Rocks That Actually Get Done

Rocks - the quarterly priorities that drive the business forward - are where Dean sees the most common implementation mistakes. Most teams set too many rocks, define them too vaguely, and fail to honestly assess whether they can actually be completed in 90 days.

Dean’s guidance is to limit company-level rocks to three. Each rock needs a clear definition of “done” that is measurable and binary - it is either complete or it is not. Aspirational language like “improve client satisfaction” does not qualify. A proper rock looks more like “implement NPS survey across all active accounts and complete first round of responses by March 31.”

Rocks cascade from the company level down through departments to individual contributors. Each person should carry three to seven personal rocks that align with the company’s quarterly priorities. This cascade ensures that every team member’s quarterly work connects directly to the company’s most important objectives.

Structure Before People

One of Dean’s most counterintuitive recommendations is to design the accountability chart for where the company wants to be in six to twelve months - not where it is today. This means defining seats, roles, and success metrics for a future organizational structure, then hiring the right people into those defined seats.

The alternative - retrofitting an organizational chart around the people you already have - leads to compromises that compound over time. Roles get shaped around individual strengths rather than business needs. Gaps get papered over rather than filled. The result is an organization that works well enough in the short term but creates increasing friction as it scales.

Dean emphasizes using the GWC framework (Get it, Want it, Capacity for it) to evaluate whether people are in the right seats. All three criteria must be met. Someone who gets the role and has the capacity but does not genuinely want it will eventually become disengaged. Someone who wants it and gets it but lacks the capacity will hit a ceiling that frustrates everyone.

Resources Mentioned

• Dean Breyley on LinkedIn - Certified EOS Implementer
• Grow or Die - Dean’s EOS implementation practice
• EOS Worldwide - Entrepreneurial Operating System resources
• Traction by Gino Wickman - The foundational EOS book
• ZenPilot EOS + ClickUp - Running EOS inside ClickUp