Agility Doesn’t Come From Tools

Ten years ago, the teams I supported with my clients all worked full-time in the office. Before COVID, you could always tell when an agile transformation was underway when teams put up large Kanban boards across any wall they could find. Along with walls covered in multi-coloured sticky notes and painter’s tape, teams had rolling whiteboards they moved with them from room to room as they discussed and sketched their work.

These physical Kanban boards were part of a team’s identity. For most teams, it was their first time building a physical system like that. No two boards looked alike, and they were always a bit crooked. Every once in a while you’d see a team tear down a whole section of their board and start building the outline of a new system using tape; they’d rewrite headings and update policies.

At the start of these transformations, discussions focused on the boards and how they worked; but over time and across many iterations, the board faded away, and the discussions shifted to the team’s work.

Every morning, the team gathered around their wall for their stand-up meetings, and throughout the day, you would see small groups walk up to the boards to discuss progress, blockers, due dates, and backlogs. Instead of weekly status reports or presentations, stakeholders and executives would visit the boards, see the work, and talk with the teams.

These physical boards were a scaffold the team used to come together around their work, and that helped them evolve their ways of working.

But since COVID, remote work, hybrid, and hoteling have increased teams’ reliance on digital tooling. When digital tools replace the wall, they reduce the collaborative behaviours teams need to support agility.

How Tools Took Over

When physical co-location disappeared, teams lost the shared gathering space the physical wall provided. As teams suddenly all went remote, they became highly dependent on their enterprise project management tools.

Even if teams are working co-located today, six years later, that impact persists. Over the past six years, these tools have increasingly dictated the shape of the work itself. For many teams, work is now strictly either Epic-shaped, User Story-shaped, or Task-shaped.

Rather than serving as lightweight record-keeping systems, tools are increasingly becoming the main focal point of every ritual and ceremony. Teams fill in mandatory fields, link work items, update statuses, and follow strict workflow schemes.

This tool-driven dynamic inverts the Agile Manifesto’s first value into “processes and tools over individuals and interactions.”

Standardization and the Erosion of Initiative

When organizations want certainty, especially in a low-trust environment, they turn to standardized processes that support consistency and reporting. Standard procedures help guarantee predictable outcomes in routine scenarios, and they demand less cognitive effort, judgment, and decision-making from the team.

The long-term cost of standardization is that it erodes the incentive for people to adapt as circumstances change. Follow the procedure, and you’re safe; exercise judgment and the risk increases. Even if management later urges them to “take initiative,” the standardized options remain, and following the playbook keeps you safe from potential risk or scrutiny.

Standardized routines might help a company survive an immediate crisis, but they weaken its capacity for adaptive behaviour later. You cannot hand people a rigid set of procedures while telling them to “take initiative” and expect both. When a standard procedure clashes with human judgment, the process wins. Not because standard procedure are better, but because following the rulebook shields the individual from blame if things go wrong.

Agility Doesn’t Need Tools

Many teams that have only experienced this post-COVID version of agile have been given the wrong idea of agility. Agility does not depend on tools, complex software platforms, or formal frameworks. Scrum, SAFe, Kanban, prescribed ceremonies, story points, and certified roles do not create agility. Agility is an emergent property. Any team can achieve it without spending money on software if they try to adapt and continuously work according to a few foundational principles:

• Direct Conversation: Make direct, real-time communication the primary method of alignment, of planning, and of work. Documents, tickets, and dashboards exist only to support conversations, not replace them.
• Continuous Customer & User Feedback: Engage directly with the people who use your product early and often. Collect feedback continuously as you build.
• Trust and Distributed Decision-Making: Push decision-making authority to the people closest to the work. Agility requires trusting teams and empowering them be self-directing.
• Small Batches and Low Work-in-Progress: Focus on finishing work, not starting it. Keep work small, limit how much work is in flight simultaneously, shorten feedback loops, and eliminate dependencies.
• An Experimental, Adaptable Attitude: Treat your processes as work-in-progress, not fixed. Inspect how you work, experiment, and continuously adjust. The way you work should be flexible.

None of this requires Jira, new tools, or complicated platforms.

Placeholders for Conversation

In the era of physical Kanban boards, the goal was never to create the “best” board. It was to create an environment where people could talk to each other, solve problems collaboratively, and continuously improve both their work and their process.

If your team’s day-to-day work feels bogged down by administrative overhead and ticket hygiene, remember that in agile, artifacts are just placeholders for conversations.

Strip away the complexity and focus on the real conditions that create agility: human conversation, rapid feedback, small steps, and true autonomy.