This event was part of the Reimagining Agility initiative. See even more information and content from the initiative here.
The following is an AI summary of the event.
Overview
The discussion focused on why Agile still matters 25 years after the Manifesto and what “Reimagining Agility” is trying to do: not replace the Manifesto, but extend agility beyond teams and software into leadership, governance, funding, and enterprise decision-making under uncertainty. The panelists returned repeatedly to a core claim: the problem Agile responds to, uncertainty in complex systems, has not gone away and in many organizations it has intensified.
Why Agile Still Comes Up 25 Years Later
The panelists argued that Agile remains relevant because uncertainty, interdependencies, and coordination complexity have increased. They suggested Agile “wins” at the team level often expose the next constraints elsewhere in the organization, such as governance, decision rights, and how strategy becomes execution. In that sense, the conversation has shifted from “Agile teams” to “Agile businesses.”
The Gap Between Agile Practices and Agile Intent
A major theme was the difference between doing Agile rituals and practicing Agile thinking. The discussion criticized “Agile theater” and cargo-cult adoption where teams run ceremonies but do not meaningfully learn, adapt, or change decisions. The panelists framed this as mistaking process compliance for an effective response to uncertainty. They also pointed to an industry incentive problem: it’s easier to sell “recipes” than to build real capability and judgment, but recipes stop working as conditions change.
Why “Agile” Sometimes Triggers Pushback
The panelists noted that in some organizations, the word “Agile” itself now creates resistance. One practical suggestion was to lead with business outcomes and plain language (speed, adaptability, learning, growth) rather than Agile branding or framework jargon, especially when speaking with executives.
Remote Work Changed the Unit of Work
The discussion made a distinction between distributed teams and distributed individuals. Distributed teams can still behave like teams, while “everyone remote, everyone alone” changes how decisions get made and how information moves. The panelists argued that technology did not recreate the informal, ad hoc interactions teams relied on, and some teams only discovered how much they depended on in-room decision-making once the room disappeared.
What Remote Work Tends to Erode
The panelists emphasized losses that are hard to replicate remotely: serendipity, overheard context, quick offers of help, and social cohesion. They described a drift from collective ownership toward individual optimization, and suggested that weaker team identity can reduce retention, particularly for people onboarded fully at a distance.
What Helps Remote Work Succeed
The discussion treated remote collaboration as workable but not automatic. Remote-native organizations were described as more successful because their systems, expectations, and hiring fit remote work. For others, the shift required new habits: intentional communication, stronger async discipline, and periodic in-person time for certain kinds of conversations. Hybrid arrangements were framed as a pragmatic compromise when organizations want both focus and “accidental” communication.
AI, Enterprise Design, and the Coordination Problem
AI was discussed as both an accelerator and a risk multiplier. The panelists argued that AI tends to amplify what already exists: disciplined engineering practices can benefit, while weak foundations get worse faster. They also suggested that enterprise agility may depend on reducing coordination costs, not increasing communication. Architectural approaches like clear interfaces and modular systems were used as examples of how organizations can enable parallel work without constant cross-team coordination.
Responsibility and Guardrails for AI Use
The panelists connected AI adoption back to long-standing Agile concerns: engineering discipline, technical excellence, and guardrails that keep humans accountable for outcomes. They emphasized keeping humans “in the loop” and resisting a single-minded focus on speed or productivity that crowds out quality, ethics, and long-term sustainability.
Making Change More Likely to Succeed
When the discussion turned to improving change outcomes, the panelists stressed learning over dogma. They suggested treating change as experimentation where possible, reducing overconfidence in big plans, and focusing on visible learning and results rather than transformation hype. They also challenged the idea of transformation as a program with a finish line, arguing that continuous adaptation should be treated as an operating capability, not a temporary initiative.
Psychological Safety Includes Leaders
One distinct point was that psychological safety is usually discussed as a team issue, but leaders often operate in environments that feel unsafe, with pressure from above, below, and outside. The panelists suggested this can lead leaders to overstate certainty, avoid admitting mistakes, and push large, premature decisions instead of smaller, reversible steps.
Judgment Over Metrics
Near the end, the discussion emphasized judgment as the scarce skill, especially as AI accelerates execution. The panelists criticized proxy metrics that distort behavior (velocity was referenced, and “productivity” was raised as a similar risk in the AI era). They argued that ethics and judgment will matter more, not less, as tools become more capable.
Hopeful Notes
The panelists expressed hope in the continued durability of Agile values and in the number of people still showing up for these conversations. They also pointed to AI-enabled advances in fields like biotech as examples of meaningful outcomes, while acknowledging ethical tensions around access and cost. The event closed with an invitation to continue the work through Reimagining Agility workshops focused on real organizational “wicked problems.”
