Why does my team wait out every change until I give up?
You push. They nod. Then nothing moves. The old line returns — we have always done it this way. You push harder. Still nothing. You are not tired from the work. You are tired from doing it alone, again. This is not stubbornness. It is arithmetic. Every change that stalled long enough to outlast your patience taught your team one lesson: wait, and it passes. You did not mean to teach this. But you did, one retreat at a time. The fix is not more force. Force is what you have already tried. What you need now is proof — proof that waiting no longer wins. That proof is built by what you do next, not by what you announce in a meeting.
They resist because waiting has worked before. Every time you backed down, you taught them that stillness pays. This is not their flaw — it is the result you built. You cannot demand courage from a team you trained to expect your retreat. Change what you reward, then hold your ground.
What changes unlock by starting
- You stop treating resistance as a personal insult and start treating it as a pattern to break
- Your team sees, through your actions, that waiting no longer works
- You push fewer changes, but the ones you push actually land
- You spend less energy managing hurt feelings and more energy managing outcomes