EOS implementer Walt Brown on teams, trust, and the seven critical needs

Executive overview

Most EOS implementations focus on tools and cadence — but Walt Brown argues the real measure of success is whether employees feel bought in, included, trusted, and engaged. He spent a decade noticing that even well-run EOS companies struggled with accountability clarity, and traced it back to a gap between having the right seats and defining the actual roles inside them.

The accountability chart only works when roles — not just seats — are defined with precision, and employees can honestly accept the promises the organisation is making to them.

Walt's entrepreneurial path

• Grew up watching business owners on his street; wanted that life from an early age.
• Spent four years as an Ernst & Young auditor to learn how companies work from the inside.
• Launched a mail-order sailing catalog in 1986; grew it into four companies over 20 years.
• Core business model: bring European brands (Musto, Dubarry, Tactic) into the US and build distribution.
• Structured later deals with income-statement sharing and a clear buyout trigger — after getting cut out as a middleman on the first one.
• Sold to a family office; used proceeds to fund angel investments via the Blue Ocean Fishing Club.
• Turned around a failing wastewater startup at investors' request, then got fired by his board — including close friends.

Route into EOS

• Ran a TAB franchise in Raleigh-Durham after hearing a peer describe it at a sailing industry meeting.
• Built the practice to 48 CEOs across four boards within months of selling his catalog business.
• Saw a recurring pattern: clients had good strategic advice but couldn't execute.
• Got cold-called from Detroit by Don Tinney, who found him on page nine of Google for "business coaches Raleigh."
• Took nine clients through EOS immediately; then 27 more. Sold his TAB practice to go EOS full-time.
• Restarted his EOS practice from scratch after being fired from the turnaround — Don Tinney brought him back.

The seven critical needs framework

• Employees unconsciously score their experience against seven questions: belong, believe, accountable, measured, heard, developed, balanced.
• Belong and believe are the cornerstones; accountable, measured, heard, developed, and balanced build on top.
• Walt developed the framework by running focus groups with Millennials across his client base — testing why EOS companies were breaking the generational engagement stereotype.
• Influenced by Gallup's employee engagement and strengths work (trained in 2006) and by years of high-level competitive team sailing.
• Companies that run EOS well and communicate it as a commitment to these seven needs score significantly higher on employee buy-in.

The BITE index

• BITE = Buy-in, Inclusion, Trust, Engagement — measured via a seven-question survey scored like an NPS.
• Baseline score before EOS: ~42. After a solid EOS implementation: 62–70. When teams are told EOS exists specifically to honour the seven critical needs: 80–82.
• Walt uses BITE as his primary measure of implementation effectiveness — separate from the EOS organisational checkup, which measures tool adoption rather than human alignment.
• A high BITE score correlates with companies becoming genuinely self-managing.

Roles vs seats in the accountability chart

• Seats and roles are not the same thing — conflating them is a persistent source of accountability drift.
• Surveying employees on accountability shows scores that look healthy early, then quietly erode over time.
• That pattern prompted a deeper investigation into what employees actually need to confidently say they understand and accept their accountability.
• Walt has built software on knowledge-graph technology to help teams surface and define all roles explicitly — not just the org-chart boxes.
• Clear role definition is what enables mastery, autonomy, and purpose (aligns with Daniel Pink's Drive).

The one nugget: promise-making as an operating system

• EOS is fundamentally a promise-making, promise-accepting, and promise-keeping methodology.
• A promise is meaningless if the other party hasn't accepted it — it's a two-party deal.
• Organisations promise employees a specific culture, direction, and set of accountabilities. Employees either genuinely accept that promise or they don't.
• If someone can't accept the promise, the right move is to make them available to the marketplace — not to hold them or pretend alignment exists.
• Get clear on what you're promising yourself first. Then promise the people around you. Then verify honest acceptance.