Story 3: Agility vs actual planning
Agility is everywhere. Everyone wants to be quick, adaptable, and ready to pivot. The concept is appealing – respond to change, learn fast, and adjust on the go. We create flexibility in areas that don’t need it. Sometimes, we know what needs to be done from the start.
In those cases, accurate upfront scoping – not agility – is the key to achieving high-quality outcomes. A young leader frustrated with her team’s declining quality of project outcomes told me: “We’re trying to be agile, but it feels like we’re just circling the priorities, never landing on them.” The team was too focused on agility. “Are you ensuring your team has clear guidance from the beginning?” I asked. “Or are they constantly having to guess what’s most important?”
Her team simply needed to work confidently from a well-laid plan. They became more engaged and performed better once she committed to giving clear, upfront guidance and introduced flexibility only where necessary.
Agility is valuable when the project’s goals aren’t clear from the outset. For instance, if you’re developing an innovative product in a rapidly changing market, an agile approach allows you to test ideas, collect customer feedback, and adjust without committing resources prematurely. However, when the goal is well-defined and stable, upfront planning leads to better results. In highly regulated industries like healthcare or manufacturing, for example, there’s little room for changing requirements on the fly.
A clear plan avoids unnecessary revisions and allows the team to focus entirely on execution. In such cases, “agility” can create chaos by encouraging unnecessary or inappropriate changes.
The takeaway
Don’t let agility replace good planning. Agility is powerful when navigating unknowns but is not a substitute for clarity. The real question is not, “How can we be agile?” but “Do we need agility here, or do we need scope specificity?” In projects with clear goals, upfront planning will consistently outperform agile methods.