Quick Wins
Faith doesn't sustain change; proof does. Ship a visible result in weeks, not quarters, and watch skeptics turn curious.
Nobody sustains a change initiative on faith. People need proof that the new way of working actually works, and they need it early. A quick win is a visible, unambiguous result that lands within weeks, not quarters. A team that cuts its deployment cycle from two weeks to two days. A group that runs its first real experiment and kills a feature before wasting a quarter building it. These results do more for momentum than any slide deck.
Internal success stories resonate stronger than anything a consultant can bring. When a team down the hall ships something faster or catches a problem earlier because they changed how they work, that proves to everyone else, “Hey, this may work around here.” That peer credibility is what moves people from skeptical to curious. The guiding coalition should be actively hunting for these stories and amplifying them. For them, these stories carry the added benefit of proving strategies are sound and potentially scalable to other parts of their org.
Design your first test and learn experiments to produce quick wins deliberately. Every cycle of iterative strategy development should target at least one result that’s concrete enough to point at. If you can’t show progress, you can’t create the space for the next round of change.
Resources
- Guiding Coalition — the group responsible for surfacing and amplifying quick wins
- Creating Space — without capacity, teams never get to the wins
- Iterative Strategy Development — the feedback loop that turns wins into strategy
Knowledge