The risk in a technology rollout is often a sequence problem: the right action done too late can be almost as ineffective as the wrong action. The purpose here is helping people orient, decide and act while the situation is moving. Change leadership is the work of helping people understand, test and adopt new behavior while the organization continues operating.
Three mistakes that make this harder
1. Assuming launch equals implementation
This often looks efficient at first. In a technology rollout, it usually removes information you needed to make a better second move. Replace it with create feedback loops from implementation.
2. Communicating only the benefits
The correction is not “try harder.” Use acknowledge losses as well as benefits and set a clear point at which you will reassess rather than continuing automatically.
3. Treating resistance as ignorance
When this appears, the useful cue is change fatigue expressed as cynicism. Respond before the pattern becomes the whole situation.
A replacement routine
- Prepare: create feedback loops from implementation.
- Notice: local workarounds that reveal design problems.
- Act: identify the few behaviors that must change.
- Check: adoption of target behaviors.
- Recover: if the first move fails, separate what is decided from what is still open.
Example language
Try: “What changes in your day-to-day work is…” If the situation changes, use: “The concern I am hearing is…” The language should reduce ambiguity, not win an argument.
How to know the replacement is better
Compare three attempts. If adoption of target behaviors improves but time to resolve implementation blockers gets worse, you may have solved the wrong problem. Keep the trade-off visible.
Separate the technical problem from the pressure problem
Ask two questions about a technology rollout: what would a competent solution require in calm conditions, and what changes once pressure rises? The first question identifies task knowledge; the second identifies performance interference. Use acknowledge losses as well as benefits for the task side and explain the case for change in concrete terms for the pressure side. Mixing the two can lead to more information-gathering when the real issue is execution.
A useful reset question
When local workarounds that reveal design problems appears, ask: “What is the next observable behavior that protects the objective?” That question is often more useful than analysing the whole situation. If the answer is unclear, use This part is decided; this part is still open to input. to make the next step explicit and then review feedback-to-decision cycle time after the attempt.
Plan the recovery before you need it
Write down what you will do if the first move is clumsy, ignored or interrupted. A recovery plan can be as simple as restating the objective, asking one clarifying question, pausing to check the facts, or naming a constraint. The value is not sophistication; it is availability. When pressure is high, a prepared second move prevents one imperfect moment from controlling the rest of the situation. Applied to a technology rollout, keep the review tied to change leadership rather than turning it into a broad judgment about ability. Write one observation from the attempt, one decision you would repeat, and one change for the next comparable situation. If you cannot name those three items, the review is probably still too general. The purpose is to leave the situation with a usable next experiment, not a longer explanation of why it was difficult.
Questions people ask
What should I measure after a technology rollout?
Choose evidence close to execution. Track adoption of target behaviors and time to resolve implementation blockers for three comparable attempts before deciding whether the approach is working.
What if I forget the technique in the moment?
Shorten it. Put create feedback loops from implementation into the environment before the event and use one sentence such as “What changes in your day-to-day work is…” rather than trying to remember a full framework.
What if another person makes the situation harder?
Keep the boundary between influence and control clear. You can use acknowledge losses as well as benefits, state the relevant constraint, and decide whether to continue, pause, renegotiate or escalate.