When capable people keep returning to the familiar play, look at what the workplace makes easier, safer, faster, or less costly.
You can teach a better way of working, make the expected behavior clear, give people a practical play, and still watch them return to what they have always done.
When that happens, the easiest explanation is resistance. People do not want to change. They lack discipline. They need more coaching. Perhaps they did not understand the training.
Sometimes that diagnosis is correct.
But before asking people to try harder, look at what happens when they actually try the new response. Does it make their work easier or harder? Does their manager support the judgment they were encouraged to use? Do the measures, approval rules, information, workload, and consequences make the new response reasonable—or make the familiar response safer?
A workplace can say one thing and teach another.
Sometimes the employee is not refusing the new behavior. The system is paying them—in speed, safety, approval, certainty, or fewer headaches—to keep the old one.
Consider what happened to Mara.
Mara tried the new play
Mara had been working on a recurring problem with Joel, one of her analysts. Whenever Joel reached a difficult decision, he tended to bring the work back to her. Under deadline pressure, Mara usually solved the problem herself.
The report got finished, but Joel learned that difficult work could be returned to his manager.
Mara decided to change her response. When Joel brought a blocked task, she stopped taking it automatically. Instead, she asked what decision he needed to make, what reasonable options he saw, and which one he recommended. Joel remained responsible for the work while Mara provided support where judgment was genuinely needed.
The new play began to work.
Then Joel made a reasonable decision and got one detail wrong.
Later that day, Mara’s director called her.
“Why didn’t you check this before he sent it?”
Mara explained that Joel had worked inside the boundary they had agreed.
Her director frowned. “You’re still accountable. I don’t want surprises like this again.”
Nobody told Mara to stop developing Joel. Nobody cancelled the new play. The organization could continue saying that supervisors should delegate, build ownership, and develop people.
But the next time Joel brought uncertain work, Mara faced a very different calculation.
She could call the new play again and risk another conversation with her director.
Or she could take the work back and protect herself.
The workplace had just taught her which response was safer.
People learn the real rule from what happens next
Organizations communicate through policies, competency models, values, training, and leadership messages. They also communicate through consequences.
Those consequences are often the stronger teacher.
Tell employees to make decisions closer to the customer, then question them every time they act without approval, and permission-seeking becomes sensible.
Tell supervisors to develop people, then treat every reasonable employee mistake as evidence that the supervisor lost control, and rescuing work becomes safer.
Tell teams to collaborate, then reward almost entirely for individual output, and people will learn what the organization actually counts.
None of this requires cynicism. People simply notice patterns. They watch what gets praised, what gets questioned, which mistakes are tolerated, which decisions create trouble, and which behaviors reduce friction today.
The written rule is part of the system. The repeated consequence is often the stronger part.
That is why a familiar response can survive even when people understand the strategy and genuinely want to behave differently.
Before blaming the system, make sure the play had a fair chance
There is an important caution here.
When people do not use a new response consistently, do not immediately conclude that the culture is broken or the system is fighting them. A Minimum Lovable Play is still a bet. The play itself may be awkward. The cue may be weak. People may not have enough information or authority. Another supporting play may need to happen earlier.
This is where Put the Play Into a Real Work Rhythm becomes useful. A play needs a recognizable moment, a cue that helps people call it, enough support to make it usable, and real repetitions from which people can learn.
Imagine a hotel that wants front-desk employees to greet arriving guests by name. The arrival play may be simple: smile as the guest approaches, greet the guest by name, then offer the welcome refreshment.
But suppose employees receive the arrivals list too late or have never heard unfamiliar names pronounced. Repeating “Remember to greet guests by name” will not solve the problem. The arrival play depends on an earlier preparation play.
The failure is not necessarily resistance.
Before redesigning policies, incentives, or culture, ask whether the new response was actually usable in the moment.
Could people recognize when to use it? Was the cue visible? Did they have the needed information and authority? Was an upstream dependency missing? Did they get enough repetitions to learn what worked and what did not?
If those conditions are weak, strengthen them first.
But when capable people have a usable play and the familiar response still keeps winning, the system deserves closer examination.
The familiar response is often being paid
When leaders hear the word reward, they may think of bonuses, commissions, or formal incentives.
The workplace pays for behavior in many other currencies.
A familiar response may buy speed. Mara can finish Joel’s report herself in ten minutes instead of coaching him through the decision.
It may buy safety. An employee who escalates an unusual customer request cannot easily be accused later of exceeding authority.
It may buy approval. A team member who agrees with the senior leader avoids the discomfort of challenging an idea in front of everyone.
It may buy certainty. Following an old procedure feels defensible even when another response would serve the customer better.
And sometimes it simply buys fewer headaches today. Passing the problem to another department may be easier than coordinating a solution across three teams.
The immediate payoff is real.
So is the delayed cost.
Mara saves time now and strengthens dependency later. An employee protects themselves through escalation and the customer waits longer. A team avoids conflict during a meeting and spends the next three days working out who actually owns the decision.
Weak routines often survive because the person making the choice experiences the immediate benefit while the organization absorbs the later cost.
Follow the consequence, not only the policy
If you want to understand why a behavior keeps returning, watch what happens after someone uses the response you say you want.
Suppose a frontline employee resolves a routine customer request inside the decision boundary you gave them. Does the manager support that judgment when the result is reasonable but imperfect? Or does the manager say, “Next time, check with me first”?
Suppose a project employee surfaces a risk early. Does the team examine the evidence, or does the person learn that bringing bad news creates embarrassment?
Suppose a supervisor keeps ownership with an employee instead of taking difficult work back. When the employee makes a learning mistake, does the supervisor receive support—or a warning that control would have been safer?
These reactions become operating instructions.
Some signals are formal: approval limits, performance measures, software permissions, staffing rules, incentives, reporting structures, and access to information.
Others may never appear in a policy manual. A manager’s face when somebody brings bad news is a signal. Who gets praised in meetings is a signal. Which mistakes trigger public questioning is a signal. What leaders ask about every Friday is a signal.
People learn what matters by watching what the organization repeatedly protects.
Sometimes the problem sits upstream
A play can be perfectly reasonable and still depend on something that happens earlier.
Suppose customer-service employees are expected to resolve routine exceptions without unnecessary escalation. They understand the play and want to use it, but the customer history needed to make the decision is accessible only to supervisors.
The problem is not confidence.
The decision play depends on an upstream information play.
Or suppose supervisors are expected to delegate more responsibility, but assignments reach them so close to the deadline that employees have no room to think, try, recover, or ask for help. Under those conditions, taking the work back may be the only reliable way to protect the deadline.
The delegation play may not be the main problem. The planning rhythm is.
This is why a system problem does not automatically require a large organizational redesign. Sometimes another moment needs its own supporting play. Sometimes information must arrive earlier. Sometimes a manager response needs to change. Sometimes authority needs to move closer to the work.
When a play repeatedly becomes difficult to use, look upstream before adding more pressure downstream.
When the play keeps losing, diagnose the break
A Minimum Lovable Play is beta. Failure to use it is information.
Suppose a new response had twenty clear opportunities during the week but was called only twice.
Do not begin by defending the play.
Look at what happened.
Perhaps people did not recognize the moment. Perhaps the play was too cumbersome. The boundary may have been unclear. The first person who used it may have been publicly questioned. The workload may have made the familiar response much faster. Or the old behavior may still offer a stronger immediate payoff.
The important question is not whether the people or the system are “at fault.” The question is where the execution chain is breaking.
If the play is weak, improve the play. If people cannot recognize the moment, improve the cue. If capability is missing, coach and practise. If information or authority is missing, strengthen the condition. If the workplace repeatedly punishes the desired response, change the signal that keeps making the familiar response rational.
When a play fails to travel, do not defend the play. Diagnose the break.
Separate capability from conditions
One useful test is to ask:
Would another capable person probably struggle under the same conditions?
If every supervisor delays feedback because performance information arrives two weeks late, another feedback workshop will not solve the timing problem.
If frontline employees keep escalating the same routine exception because two policies contradict each other, confidence training will not create a safe decision boundary.
But suppose the play is clear, the needed information is available, peers use it successfully, the manager supports reasonable judgment, and one employee still repeatedly avoids the response. Capability, motivation, or individual judgment may genuinely be closer to the problem.
Good diagnosis protects both sides.
It prevents organizations from blaming people for design failures. It also prevents “the system” from becoming a convenient explanation for every individual performance problem.
The aim is not to excuse behavior.
It is to locate the intervention where it has the best chance of changing what happens next.
Change the condition closest to the break
Once leaders discover that the environment is reinforcing the old response, the temptation is to make the problem large.
Launch a culture transformation.
Rewrite the performance system.
Redesign the organization.
Create another enterprise initiative.
Sometimes large change is necessary. Often the first useful move is smaller.
If Mara keeps rescuing work because analysts bring difficult decisions too close to the deadline, move the checkback earlier.
If employees keep escalating because one authority boundary is unclear, make that boundary visible.
If hotel staff hesitate to greet arriving guests by name because they do not know how to pronounce the names, build the preparation play before arrival.
If managers ask for bad news early but react defensively whenever someone provides it, work on that manager response before creating another reporting process.
Start as close as possible to the recurring break.
A small change can be powerful when it removes the reason the familiar response keeps winning.
Use the System Scan
Take one recurring situation where people know the desired response but keep returning to the familiar one. Follow what actually happens rather than beginning with a long list of organizational problems.
1. Name the play you want
What different response are people trying to use, and what nearby result is it supposed to help move?
If that is still vague, sharpen the play first.
2. Follow what happens when someone tries it
What consequence follows?
What does the manager do? What information is missing? What approval appears? What happens to workload, risk, customer response, or accountability?
Often the real signal becomes visible only after someone attempts the new response.
3. Ask what the familiar response buys
Why is the old play still attractive?
Does it create speed, safety, approval, certainty, lower effort, or protection from blame?
Do not mock the old response. Understand what useful function it is performing for the person.
4. Find the condition creating that advantage
Now inspect the work around the moment.
The condition might be an approval rule, performance measure, missing tool, late information, unclear boundary, manager reaction, workload pattern, incentive, handoff, or upstream play.
You do not need to scan the entire organization if one nearby condition explains most of the behavior.
5. Change the smallest credible condition
Give the different play a fairer chance.
Remove a step. Move information earlier. Clarify authority. Change a manager prompt. Adjust a measure. Build an upstream play.
Treat this intervention as another bet rather than a permanent solution declared in advance.
6. Watch the next repetitions
Return to real work.
Does the play appear more often? Is it easier to use? Does the familiar response weaken? Does something nearby begin moving differently?
If not, the evidence may be telling you that you changed the wrong condition.
Adjust again.
Make good judgment easier, not automatic
Removing friction does not mean removing responsibility.
A strong system should not make every decision automatic. People still need to think. Frontline employees still need judgment. Supervisors still need to coach. Managers still need to make difficult calls.
The purpose of system design is to stop forcing capable people to fight the organization whenever they try to use the behavior the organization says it wants.
That is different from making work effortless.
Good execution creates enough clarity, information, authority, support, and feedback that responsible judgment has a fair chance to operate.
Watch what changes after the next attempt
You do not need to wait for a major business result before learning whether the environment is becoming more supportive.
Listen for fewer statements such as, “I know what I’m supposed to do, but the process won’t let me.”
Watch whether routine decisions remain closer to the work. See whether managers rescue less often, employees bring recommendations rather than only problems, and information begins arriving before the critical moment instead of after it.
The new response should also survive ordinary pressure better. If it disappears the moment workload rises or the manager stops reminding everyone, the condition may still be too fragile.
And if the pattern does not improve, do not protect the original diagnosis. Learn from that too.
Perhaps the play itself needs another redesign. Perhaps a different condition is doing more of the work than you thought.
The goal is not to prove that your system diagnosis was correct.
The goal is to make the critical moment contribute more reliably to something that matters.
Make one conflicting signal visible
Choose one play your team says it wants but struggles to use consistently.
Watch the next few real occurrences.
What happens when somebody actually tries the new response? What consequence follows? What does the familiar response buy instead? Which rule, manager reaction, information gap, measure, workload pattern, or upstream routine gives the old play its advantage?
Find one conflicting signal.
Change the smallest condition closest to that break.
Then watch the next repetitions.
Do not begin with:
“How do we make people try harder?”
Begin with:
“What are we still teaching them to do?”
If people have the play but still lack a clear field in which they can make decisions, Give People Boundaries They Can Act Within can help make the win, decision space, red lines, and checkback visible.
If the problem appears after meetings, assignments, or handoffs because everyone agreed but the next movement has no clear owner, continue with Make Ownership Visible Before Work Leaves the Room.
And if the new response has not yet been built into the moment where people need to call it, revisit Put the Play Into a Real Work Rhythm.
For the larger execution system connecting strategic choices, critical moments, behavior, plays, working rhythms, system support, ownership, evidence, and learning, explore Make Execution Daily.
Do not make the new play fight the workplace forever. Find what keeps paying for the familiar response, change the condition closest to the break, and let the next few repetitions tell you whether the new play now has a fair chance to work.