6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article explores why having a plan often leads to failure, while the process of planning fosters adaptability and teamwork. It highlights lessons learned from two contrasting projects, emphasizing the importance of shared understanding, decision-making frameworks, and the need for flexibility.
If you do, here's more
Plans often become irrelevant shortly after they're created, but the process of planning is essential for successful execution. The author shares insights from launching a CRM overhaul at a previous job. They found that the plan itself was less important than the collective effort of planning. By involving pilot groups of salespeople early on, the team gathered real-time feedback, which helped them secure leadership approval and achieve strong adoption. Throughout the process, they constantly adjusted their priorities and features based on what they learned.
The article highlights common pitfalls in planning, illustrated by a failed dropdown feature. Despite extensive discussions, the team neglected to establish a shared understanding of the project's goals and user needs. The result was a feature that no one used. Effective planning creates a shared vocabulary, decision scaffolding, and forces difficult conversations that can surface conflicts before they hinder progress.
The author introduces a "Plan to Pivot" approach, emphasizing the importance of explicitly naming assumptions that must hold true for a project to succeed. They recommend setting decision points instead of strict deadlines, allowing teams to reassess their strategies based on real feedback. By planning in smaller, manageable chunks, teams can remain flexible and responsive to new information. This method contrasts with trying to lock in every detail from the start, which can lead to rigidity and failure.
Questions about this article
No questions yet.