There is a phrase I hear surprisingly often in EOS® sessions:
“Yep, we know that.”
We know we should review the Scorecard every week. We know our Rocks need attention. We know the Level 10 Meeting® agenda. We know that Issue has been sitting there for months. We know we need to have that conversation.
Great.
But are you actually doing it?
Because knowing something & consistently doing it are two very different things.
And in business, the gap between the two can become very expensive.
Most Leadership Teams Do Not Have a Knowledge Problem
I work with plenty of intelligent, experienced leadership teams.
They have read the books, attended workshops, learnt about strategy & spent years developing as leaders. Ask them what needs improving in their business & they can often tell you immediately.
The problem is rarely that they do not know enough.
The problem is execution.
That is why another management book, strategy day or clever framework does not necessarily change anything. You can understand exactly what good leadership looks like & still fail to practise it consistently.
In fact, familiarity can sometimes make things worse.
Once we have heard an idea enough times, we start treating our understanding of it as though it were the same thing as doing it.
We know accountability matters.
We know priorities need focus.
We know difficult Issues need to be addressed.
But knowledge only creates value when it changes behaviour.
“We Know” Can Become an Excuse
Whenever somebody tells me, “We know that,” my next question is usually:
“Are you doing it?”
That is often a much more revealing conversation.
Take the Scorecard.
A leadership team may understand perfectly well that it should contain useful weekly measurables. Yet some of the numbers are not updated, goals are unclear & the same measurable has been off track for a month without becoming an Issue.
The team understands the concept.
But operationally, it is not really using the tool.
The same thing happens with Rocks.
Everyone knows they represent the most important priorities for the quarter. Yet halfway through the 90 days, somebody admits they have barely looked at their Rock since Quarterly Planning.
Again, knowledge is not the problem.
Discipline is.
Having the Tools Is Not the Same as Mastering Them
This is one of the traps businesses can fall into after running EOS for a while.
The tools become familiar.
And familiarity can quietly turn into complacency.
A leadership team tells me:
“We’ve done the Accountability Chart®.”
Fine. But when was it last properly reviewed? Does it still reflect the structure the business needs now, or is it describing the company as it looked 18 months ago?
Or
“We run Level 10 Meetings.”
Do you? Or do you have a 90-minute weekly meeting where the agenda has gradually disappeared, updates take too long & most of the real Issues never get properly solved?
The same applies to IDS®.
A team may understand Identify, Discuss & Solve, but that does not necessarily mean it is getting to root causes. If the same Issue keeps returning three weeks later, the team may have had a good discussion without actually solving anything.
There is a significant difference between possessing a tool & mastering it.
Mastery shows up in behaviour.
Drift Happens Quietly
The gap between knowing & doing rarely appears as one enormous failure.
It is usually much quieter.
A Rock slips because something urgent came up.
A To-Do gets carried over for another week.
A Scorecard number remains off track but nobody raises it as an Issue.
A difficult conversation is delayed because this week does not feel like the right time.
A process is bypassed because the shortcut is faster.
Nothing terrible happens immediately, so the compromise feels harmless.
Then it happens again.
And again.
Eventually, the leadership team starts wondering why the business is not getting the Traction it expected.
Usually, there has not been one dramatic breakdown.
There has been an accumulation of small disciplines that everybody knew mattered but gradually stopped doing consistently.
That is how businesses drift.
EOS Is Simple. That Does Not Mean It Is Easy.
One of the things I like most about EOS is that the tools themselves are not especially complicated.
But simple & easy are not the same thing.
It is simple to agree that a Rock will be completed within 90 days. It becomes harder when customers, new opportunities & normal business demands start fighting for attention.
It is simple to put a measurable on the Scorecard. It is harder to confront what that number is telling you when it has been off track for several consecutive weeks.
It is simple to put the real Issue on the Issues List. It becomes considerably harder when the real Issue is a person sitting across the table from you.
Understanding the tool is usually the easy part.
Using it properly when it becomes inconvenient or uncomfortable is where discipline starts to matter.
The Real Test Happens When Business Gets Busy
Almost any leadership team can follow a system when things are calm.
The real test is what happens when pressure increases.
- Does the Level 10 Meeting get cancelled because everyone is too busy?
- Do Rocks become secondary because customer work feels more urgent?
- Does somebody stop following an agreed Core Process because a shortcut seems faster?
- Does an off-track Scorecard number get ignored because there are bigger fires today?
Those are exactly the moments when the disciplines matter most.
You do not really need an operating system when everything is running perfectly.
You need it when things are not.
Yet busy periods are often when businesses start abandoning the very disciplines that would help them stay focused.
The meeting can wait.
The Rock can wait.
The process can bend this once.
But if the system is only followed when everybody has plenty of time, it is not really a system.
It is a nice idea.
Do Not Add More When the Problem Is Consistency
When execution begins slipping, leadership teams often respond by adding something.
Another meeting.
Another report.
Another tool.
Another planning session.
Another layer of accountability.
But more complexity rarely fixes a consistency problem.
Often, the better answer is to return to the fundamentals & ask where the discipline has slipped.
- Are we reviewing the Scorecard every week & responding when something is off track?
- Are we calling Rocks honestly on track or off track?
- Are To-Dos being completed when we said they would be?
- Are we following the Level 10 Meeting agenda rather than allowing the meeting to evolve into whatever feels useful that week?
- Are uncomfortable Issues actually making it onto the Issues List?
- Are we using IDS® to solve the root cause rather than creating another workaround?
- And when the leadership team agrees to something, are we actually doing it?
None of those questions is revolutionary.
That is rather the point.
Consistency Is What Creates Traction
Businesses are rarely transformed because the leadership team discovers one more clever idea.
They change when people consistently do the things they already know matter.
That may sound less exciting than launching another initiative, but it is far more powerful.
A useful operating system creates rhythm. It helps make important disciplines less dependent on memory, mood, motivation or how busy the week happens to be.
But the system cannot create that discipline for you.
The leadership team still has to follow through.
So the next time someone around the table says:
“We know.”
Do not end the conversation there.
Ask
“Are we doing it?”
Then look at the evidence.
Because the gap between what your leadership team knows & what it consistently does may tell you far more about what is holding the business back than another strategy session ever will.
If your leadership team understands the EOS tools but is not getting the Traction you expected, it may be time to look at how consistently those tools are actually being used.