Scripts for addressing resistance in huddles and 1-on-1s
Change creates resistance. That is normal. What matters is how leaders address it.
The goal is not to shut down concerns. It is to reframe them constructively.
Select your role to see the appropriate script:
I've heard this concern, and I want to address it directly. This is not the HIP way. This is how every successful company scales. Jim Collins studied thousands of companies. Verne Harnish built Scaling Up from the same research. Andy Grove ran Intel with these principles. These are not HIP inventions. They are patterns that show up everywhere great companies grow. HIP went through this transition already. They learned hard lessons. We get to benefit from that experience without making the same mistakes. The question is not "Is this the HIP way?" The question is "Does this help us do better work and grow sustainably?" I believe it does. That is why we are doing it.
Key Points:
FRAMEWORK
Before responding, make sure you understand the real concern. Often the stated objection is not the real fear.
Acknowledge the feeling before offering a different perspective. People need to feel heard.
Reference Collins, Harnish, Grove, and other respected sources. This is not about HIP. It is about proven principles.
Vague concerns are hard to address. Ask 'What specifically worries you?' to get to actionable feedback.
Make clear that this is iterative. If something is not working, it will be fixed. This is not dogma.
How you talk about this matters. If you sound uncertain, your team will be uncertain. Own the message.
LANGUAGE
Use This Language
Avoid This Language
Your language signals your belief. If you sound like you are complying rather than leading, your team will resist rather than adopt.