This episode takes a different format: rapid-fire answers to real EOS questions from teams in the field.
Three questions. Three common friction points. And practical answers that apply whether you’re a team of one or a growing organization trying to gain traction.
EOS issues list: why teams struggle (and how to fix it)
One of the most common challenges:
teams not using the issues list effectively—especially outside the leadership team.
The root problem is usually not discipline. It’s understanding.
Many team members don’t know:
- what qualifies as an “issue”
- when to bring something up
- where to put it vs. solving it immediately
Reframe the issues list: it’s not just for “problems”
A simple shift helps unlock adoption:
The issues list is just
the team’s list, and it should include:
- FYIs (things the team should know)
- Input requests (I need help or perspective)
- Problems to solve (true issues)
- Clarification needs (I don’t understand this)
When teams see it this way, participation increases quickly.
Stop solving everything in real time
Another common blocker: teams solve too much during the week.
Instead:
- ask: “Can this wait for the issues list?”
- push non-urgent items to L10
- let the whole team benefit from the discussion
Two things happen:
- You reduce unnecessary meetings
- Many “urgent” issues disappear on their own
Leadership sets the tone
If leaders consistently say:
“Put it on the issues list”
…the behavior sticks.
And most importantly:
every team member needs a place to raise issues.
That’s what builds trust and engagement.
EOS for a team of one: how to actually use it
A second question: Can EOS work for a company of one?
Short answer:
yes—and it may be even more valuable early on.
Start with your personal 10-year target
Before anything else, define:
- what you want your life to look like in 10 years
- what role the business plays in that outcome
This becomes your anchor.
From there:
- define a 3-year picture
- set a 1-year goal (often revenue early on)
- work in
90-day cycles
The power of 90-day cycles
For early-stage founders, 90 days does two things:
- creates
focus
- allows
experimentation without chaos
You can test ideas, iterate, and still stay aligned to a longer-term direction.
Use the tools simply
Even as a solo operator, you can run EOS tools:
- a personal
scorecard
- a running
issues list
- rocks (priorities) every 90 days
- a weekly review cadence
The goal is not perfection. It’s momentum with structure.
What to expect when your company starts EOS
The third question: “My company just started EOS—what’s happening?”
This is where confusion (and sometimes skepticism) shows up.
Why companies adopt EOS
Most organizations turn to EOS for three reasons:
- Lack of alignment
Teams are busy, but unclear on direction - Lack of traction
Goals are set, but not consistently achieved - Team health issues
Unspoken problems, low trust, unclear ownership
EOS addresses all three through a simple, shared system.
What EOS actually brings
When implemented well, EOS creates:
- clarity (where we’re going)
- alignment (how we’ll get there)
- accountability (who owns what)
- visibility (what’s working vs. not)
It also introduces:
- a shared language
- structured problem-solving
- consistent meeting rhythms
Why it can feel confusing at first
Early in rollout, leadership teams often work
ahead of the rest of the company.
That’s intentional.
They’re building:
- the vision
- the structure
- the foundation
Before rolling it out broadly.
But without communication, this can feel like:
- “something happening behind closed doors”
- unclear expectations
- cultural change without context
What leaders need to do
Leaders should:
- communicate early and often
- explain the “why”
- bring teams into the process as soon as possible
Because EOS is not about control.
It’s about:
- building a healthy team
- creating shared direction
- giving everyone clarity on how to win
Final takeaway: simplicity, consistency, and shared ownership
Across all three questions, the theme is consistent:
- Don’t overcomplicate EOS
- Use the tools as intended
- Build habits, not perfection
- Create space for everyone to contribute
Whether it’s:
- using the issues list correctly
- running EOS as a solo founder
- or rolling it out across a team
The goal is the same:
Clarity. Alignment. Momentum.
Built one 90-day cycle at a time.
