A few weeks ago I wrote about why Agile misses the point. Several readers asked the same question:
Okay—but what can teams actually do?
That’s a fair challenge.
It’s easy to diagnose where communication thins out and value disconnects from the work. It’s harder to explain how teams regain clarity once that drift has already started.
If there’s one thing I’ve learned, it’s this:
Clarity is never a single thing — it’s a system.
When teams lose sight of value, it’s rarely because one meeting went poorly or one priority shifted. It’s usually because multiple avenues of clarity have drifted at the same time: purpose, scope, framing, decision-making. When that happens, behavior changes. Compliance increases. Questions decrease. Technical shortcuts start to appear.
So what actually helps?
1. Slow down just enough to restore meaning
Priority shifts are inevitable. What breaks teams isn’t change — it’s change without shared understanding.
Before breaking work down into tasks, pause and ask:
- What problem are we actually trying to solve?
- Why does this matter now?
- What happens if we don’t do this?
This isn’t about adding ceremony. It’s about restoring shared context before asking for commitment.
When teams understand the “why,” they can adapt without losing momentum.
When they don’t, context switching becomes a silent tax. Technical quality erodes. Debt accumulates quietly as people try to keep up with the shifting what.
Clarity protects both the team and the product.
2. Diagnose the scope before prescribing the fix
Sometimes confusion lives in a single handoff or team dynamic. Sometimes it’s showing up across multiple streams. Treating a local issue like a cultural one creates unnecessary disruption. Treating a systemic issue like a one-off conversation lets it fester.
Clarity around scope shapes the response. Without it, teams pull the wrong levers — adding process when the issue is trust, or coaching individuals when the problem is structural.
Before fixing, ask: where does this actually live?
A real pattern I’ve seen
A product initiative was moving quickly. The priority had executive visibility, and the timeline was aggressive. Engineers raised concerns early about long-term maintainability, but the framing of the conversation was around speed and delivery.
From leadership’s perspective, the issue was execution risk. From engineering’s perspective, it was sustainability and quality.
Instead of clarifying the scope of the tension — local execution concern or broader strategic tradeoff — the team added more checkpoints and reporting.
Velocity didn’t improve. Frustration increased. Technical debt accumulated.
The breakthrough didn’t come from tightening process. It came from reframing the discussion:
- Is this a short-term experiment with acceptable debt?
- Or is this a foundational investment that requires durability?
Once that scope was clarified, the team could consciously choose tradeoffs. Tension didn’t disappear, but it became intentional instead of reactive.
That shift restored trust more than any ceremony adjustment ever could.
3. Make value explicit before asking for commitment
Teams don’t resist work because they dislike effort. They resist committing to work they don’t believe in or fully understand.
If value is assumed rather than discussed, alignment becomes fragile. The moment pressure increases, it fractures.
Instead of moving directly to estimates or delivery dates, create space for value to be articulated clearly:
- What outcome are we trying to influence?
- How will we know if this mattered?
- What tradeoffs are we accepting?
When value is explicit, commitment becomes meaningful. When it’s vague, compliance replaces ownership.
4. Treat risk-raising as contribution, not obstruction
Another pattern that shows up when clarity drifts is silence. Not agreement — silence.
Meetings happen. Tickets move. But people stop pushing back.
Often that’s not disengagement in the traditional sense. It’s a signal that people don’t believe raising concerns will change anything.
If teams are going to stay engaged, they need to know that surfacing risks is part of building value, not slowing it down.
Trust is built less by agreement and more by being heard.
5. Restore agency where you can
Sometimes the “what” is constrained. A priority must move. A commitment has already been made. Strategy has shifted.
Even then, teams usually have room to influence the “how.”
Inviting teams into decisions about implementation, sequencing, and risk mitigation restores a sense of agency. And agency is often what reconnects people to value.
You don’t rebuild trust by insisting the work matters. You rebuild it by giving people meaningful influence over how the work is approached.
When Agile feels heavy, the instinct is often to adjust the framework. Add structure. Add checkpoints. Tighten accountability.
But when shared understanding drifts, more process rarely helps.
Clarity does.
Clarity of purpose.
Clarity of scope.
Clarity of framing.
Clarity of decision-making.
When those reinforce each other, teams don’t just move faster — they move with conviction.
And conviction is what protects quality, strengthens trust, and keeps value connected to the work.
Agile doesn’t fail when frameworks are imperfect.
It fails when clarity erodes.
Protect that system, and the rest gets lighter.
Want the Experiment-Driven Agile Retrospective Toolkit?
If you’d like the Toolkit, reach out and I’ll send details (what’s included, pricing, and how teams use it). Or subscribe for new posts and updates.