Asking for a change, the sponsor names the few exact behaviors it requires, who does what differently next Monday, so agreement is easy to give and hard to drift away from.
An example
Complaint scores at a hotel group had not moved in the year its vice president of operations spent telling forty properties to improve guest recovery. Every general manager agreed, and each did something different. For the next push, she wrote three behaviors on one page. Any front desk agent could comp up to $75 without a manager's approval when a guest complained. Every complaint went into the property system before the end of the shift. The general manager called each guest whose complaint was logged within twenty-four hours. The page went to every property with a start date two weeks out, and front desk leads were trained on a thirty-minute call. Within a quarter, logged complaints rose threefold, because agents were now recording them, and repeat complaints from the same guest fell by a third.
Why it works
Goals like better service or more accountability are easy to endorse and hard to act on, and people who agree to a vague change each read it their own way, which looks like resistance. Naming the few exact behaviors, who does what differently and from when, makes agreement easier to give and to keep, and takes away the ambiguity that resistance hides in. It depends on choosing behaviors that really drive the result, few enough to remember, and on checking that they happen.
The thinking behind it
Chip Heath and Dan Heath Switch: How to Change Things When Change Is Hard (2010), by Chip and Dan Heath, advises scripting the critical moves, because ambiguity breeds resistance: people who agree with a vague goal each do something different, which looks like reluctance. Three exact behaviors with a start date remove the ambiguity, so agreement turns into action that can be checked.
When it fits
Changes that have stalled at the level of agreement are the target: everyone supports the goal and nothing moves. You need enough knowledge of the work to pick the behaviors that matter, the authority or influence to ask for them, and a way to see whether they happen.
How to use it well
Translate the goal into the two or three behaviors that most drive it, and ask the people who do the work which ones those are.
- Write each as an action: who does what, when, and how often.
- Remove whatever stands in the way, such as an approval step or a missing tool.
- Set a start date and say how you will check.
- Look closely at the first two weeks and fix what does not work.
Keep the list short. Five behaviors read as a program, and three get done.
What it costs and where it backfires
Scripts can miss the point: the wrong behaviors, done exactly, will not move the result, and people will rightly say they did what was asked. Detailed instructions can also feel like distrust to experienced staff, so leave room for judgment around the script. Once the behaviors turn into a checklist audited for compliance, people start doing them mechanically.
When it is used on you
Test whether a short list of exact behaviors will deliver the goal in your setting. If one will not, say so specifically and propose a substitute that will, with the reason. Agreeing and then doing something else will be visible this time.