The meeting was productive. The problem was identified, possible solutions were discussed, and everyone agreed. Four weeks later: nothing has changed. The team knows what needs to be done. So why isn't it happening?
Jeffrey Pfeffer and Robert Sutton systematically examined this phenomenon in their 2000 book The Knowing-Doing Gap, identifying patterns that are recognizable in almost every organization.
Why the gap exists: the 5 main reasons
Talk replaces action
Meetings, workshops, presentations: They feel like progress. But they aren't. Pfeffer & Sutton call this “talk as a substitute for action.” When people spend a lot of time planning, they feel as though they've done something without actually doing it.
Fear of consequences
If you act, you can fail. If you plan, you stay in the safe zone. In organizations that punish mistakes, employees would rather not act than risk acting incorrectly.
Memory instead of process
Many companies rely on individual memory instead of systematic processes. If something isn't captured in the system, it only happens if the right person happens to remember it.
Too many priorities
When everything is urgent, nothing is urgent. Organizations with 15 strategic priorities don't have a single real priority, and they act accordingly.
Internal bureaucracy and politics
Good ideas die in the approval process. When too many people can say no and nobody has to say yes, what happens? Nothing.
The manager's role in the gap
Managers aren't passive observers of this gap. They're often the deciding factor, in both directions.
Managers who widen the gap:
- Ask for plans and concepts but don't reward execution
- Punish mistakes, even when they result from taking bold action
- Give vague approvals that nobody understands as a mandate to act
- Change priorities before the previous task has been completed
- Don't know the answer themselves and hide that behind process
Managers who close the gap:
- Don't ask, “What's the plan?” but “What did you actually do today?”
- Reward experimentation, even when it fails
- Make execution an explicit expectation, not an implicit one
- Define no more than 3 real priorities per quarter
- Lead by example: They do what they say
“Knowing what to do is not enough; the challenge for managers is to figure out how to do what they know needs to be done.” — Jeffrey Pfeffer & Robert Sutton, 1999
What managers can do
From “What are you planning?” to “What have you done?”
The simplest shift: Make meetings about execution, not planning.
Introduce an amnesty for failure
Make it explicit: People who act and fail won't be punished. People who don't act, however, will be.
Make action visible
What was actually implemented last week? Public visibility creates accountability.
Lead from the front
The strongest message a manager can send: I do what I expect you to do.
The Knowing-Doing Gap isn't an employee problem. It's an organizational and leadership problem. Teams that know what to do but still don't act have learned that acting is riskier than planning. Changing that doesn't require another framework. It requires a manager who acts.
Sources: Pfeffer & Sutton (1999), Knowing “What” to Do Is Not Enough: Turning Knowledge into Action, California Management Review 42(1) · Pfeffer & Sutton (2000), The Knowing-Doing Gap, Harvard Business School Press.
Published June 2026