Balancing uncertainty, small teams, and the true purpose of agility
Agile has become the universal rallying cry for anyone looking to speed up projects, innovate faster, and “be more flexible.” But beneath the buzzwords, many teams end up doing Agile in name only — following a checklist of stand-ups, sprints, and ceremonies — while missing the real heart of agility.
In reality, agility matters most in highly uncertain environments, where you are still trying to discover what needs to be done and how. If your team already has clarity on outcomes, methods, and measurable results, you might not need the overhead of small Agile teams. A traditional, more structured approach could be enough. As one popular saying goes:
If you already know exactly what you need to do, then do it. If you don’t, be agile.
Below, we’ll explore why Agile makes sense (and when), dig into real-world examples — including some outside software — and share tips on how to avoid the trap of “doing Agile all wrong.” Along the way, a few quotes, some inspiring, some funny, to keep things interesting.
The core insight: it’s about the unknowns
High uncertainty
- Countless unknowns — in product design, customer needs, external factors — mean you can’t foresee all requirements up front.
- Agile thrives here because it lets you experiment, fail fast, and iterate quickly.
- Small, nimble teams can adapt on the fly, acting like explorers charting unknown territory.
Low uncertainty
- The destination and the path are relatively well understood (think of building a known product feature or running a standard operational process).
- You may not need constant iteration and daily pivots; careful planning and steady execution can suffice.
In the words of Winston Churchill:
To improve is to change; to be perfect is to change often.
When the terrain is uncertain, frequent change is your competitive edge. When the path is clear, sometimes staying the course is just fine.
Agile as an adverb, not a noun
Agile isn’t a thing you install. It is a way — an adverb — of approaching work. You apply it where it makes sense.
- Selective adoption. Don’t enforce stand-ups everywhere. Use them in uncertain, fast-moving projects where real-time alignment matters.
- Context matters. The more unknowns you have, the more you benefit from short cycles of build–measure–learn.
It is funny how many organizations say, “We’re Agile now,” while meticulously documenting 200 pages of “Agile processes.” As one project manager joked:
Our definition of “Agile” is doing twice the work in half the time… after writing four times the documentation.
Why small teams (usually) win at high uncertainty
1. Faster decisions
- Fewer approval layers, fewer communication bottlenecks.
- When the unexpected arises (and it will, in uncertain projects), small teams can pivot quickly.
2. Tighter alignment
- Everyone knows who is doing what, and it is easy to adjust tasks in response to real-time feedback.
- This collective awareness is crucial when you are discovering the path as you walk it.
3. Shared knowledge
- In a small group, expertise flows more freely. If one person learns something crucial, the entire team adapts almost immediately.
- “I only need to tell two people about the new findings” is a lot simpler than making a formal presentation to a 50-person department.
Agility is like a seatbelt — you don’t realize you need it until you’re already in a crash. — Anonymous Scrum Master (with a sense of humor)
Real-world examples (not just software)
1. Startup food truck
- High uncertainty: what menu items resonate best, which locations draw the biggest crowds, when are the peak times?
- Agile approach: each day the truck tries new specials and watches sales trends. They pivot to what sells, drop what doesn’t, and refine their approach week by week.
2. Marketing campaign
- High uncertainty: a marketing team isn’t sure which channel (social media, influencer partnerships, or traditional ads) will yield the best ROI for a new product launch.
- Agile approach: they run small experiments on each channel, gather data quickly, and double down on the winning strategies while dropping or refining the underperforming ones.
3. Medical research
- High uncertainty: early-stage drug research involves unknown interactions, side effects, and efficacy.
- Agile approach: researchers run rapid, iterative experiments — adjusting formulations, dosing, or delivery methods — based on early results. They don’t wait years to compile one giant study; they learn and adapt in sprints.
4. Event planning
- High uncertainty: a non-profit is planning its first major charity gala. It doesn’t know the best venue, target donation levels, or attendee interest.
- Agile approach: they invite a small pilot group to test-run event activities, gather feedback, and tweak the program before going big.
The only truly Agile teams are children’s soccer teams. They pivot on a dime, adjust strategy every two seconds, and still everyone ends up having fun. — A coach who’d rather be a Scrum Master
The trap: over-agilizing everything
1. Forcing Agile where it is not needed
- If processes are known and stable, a heavy Agile process just adds unnecessary rituals and overhead.
- Example: if your finance department is closing the books with the same formula every month, a two-week sprint and daily stand-ups are overkill.
2. Treating frameworks as gospel
- Scrum, Kanban, and SAFe are frameworks, not holy commandments.
- Rigid adherence — rather than thoughtful adaptation — leads to the dreaded “zombie Agile.”
3. Ignoring the mindset
- You can run as many sprints as you like, but if your culture punishes experimentation or stifles open communication, you are not really agile.
- “Agile in name, waterfall in spirit” is all too common.
How to avoid the trap
1. Start with a decision on uncertainty
Ask: how uncertain is the problem space or outcome? If it is highly uncertain, small Agile teams can shine. If it is not, don’t force it.
2. Form small, focused teams for high-risk areas
Where unknowns are big and stakes are high, empower a small, cross-functional team. Give them clear goals but let them find the path.
3. Adopt agility where it adds the most value
Use agility (small experiments, iterative learning) where you genuinely need discovery. Stick to a more traditional approach in areas that are routine and predictable.
4. Cultivate a culture of learning
Encourage reflection, honest retrospectives, and open dialogue about what went wrong or right. “Celebrate failure as data,” because that is what fuels adaptation.
5. Balance oversight with empowerment
Leadership should set a clear vision and offer support. Micromanagement kills agility; total hands-off absence kills direction. Find the sweet spot.
When it comes to uncertainty, think of your team like a jazz band — improvise together, listen closely, and don’t be afraid to change the tune when the music calls for it. — A CEO who moonlights as a saxophonist
Conclusion
Agile isn’t a silver bullet — it is a purposeful way of tackling complex, uncertain challenges. When you are swimming in unknowns, small, empowered teams that iterate quickly, learn fast, and pivot on real-time feedback can be the difference between success and stagnation. Conversely, if your path is well-lit and the steps are clear, a leaner, more traditional approach might be enough.
So instead of trying to “do Agile” everywhere, focus on being agile — in the right places, for the right reasons, with the right people. Let small teams experiment and discover in areas of high uncertainty. Keep it simple and structured where you already know the outcome. And never forget:
Agile is an adverb, not a noun. It is a way of doing things better when you don’t yet know what better looks like.
Now go forth, find out what you don’t know, and let true agility guide you there.
For some inspiration, watch one of the founders of the Agile Manifesto speaking out: Dave Thomas, back in 2015, called it out loud. Unfortunately, you’re probably still stuck.