What does an established 'old school' organisation need to do , to make change, prepare, or even think about implementing agile?

An established organization is likely to have a deeply entrenched culture and strongly defined processes. Before discussing what that kind of organization needs to do to even consider implementing Agile, it is worth addressing a common source of confusion: the word "Agile" itself is often overused, and it can mean different things to different people, including some very capable ones.

It is entirely fair to describe an approach as agile in the everyday sense of the word. What we are discussing here is Agile the methodology, sometimes referred to as New Ways of Working. It is an intricate, nuanced discipline with its own processes and guidelines. Done well, it drives down costs, improves performance, strengthens customer outcomes, and lifts both employee and business morale.

Moving to an Agile way of working challenges the people and the systems operating within a culture of established norms and defined processes. So it helps to start by reframing what "Agile" means in this context. At its core, Agile is a mindset. It is a way of thinking that differs fundamentally from traditional organizational and management approaches. Tools change and frameworks continue to evolve, but the constant is a need for flexibility, since change is simply a norm of human progress. That flexibility is what Agile is built around.

Agile methodology begins and ends with an Agile mindset.

Our consultants around the world regularly compare notes on what established organizations should do to begin this kind of change. The reflections below draw on that collective experience.

Why Do It?

The first step is to stop thinking in terms of "implementing" Agile. Agile for its own sake is almost always destined to fail. Instead, an organization should consider why it needs to change, by examining where its biggest problems or opportunities lie. This is best done through an external diagnosis, one not clouded by the organization's own internal lens.

Doing this uncovers areas that, if addressed, would have a significant positive impact on the organization. This might be employee engagement, a lack of prioritization, misalignment across teams, or some combination of factors. Once that view has been established, the next question is how to measure the impact of change. Perhaps it is an increase in revenue, or improvement in employee retention. With targeted areas identified and a way to measure impact, the organization can begin defining what it actually needs to do, whether that means redesigning how the organization works or getting closer to the customer.

Attempting change is difficult, so an organization has to be clear on why it is worth the effort. Without a compelling reason to change, people will not come along for the journey. There also needs to be a reason to act now. Without a clear catalyst, it is easy to keep waiting for a moment that never quite arrives; tomorrow never comes.

This change imperative needs to be communicated clearly and simply, since everyone needs to share the same understanding. Overcomplicating the message causes confusion, and insincerity breeds suspicion and rumor. The goal is to focus on fixing the things that will have real impact, in a way tailored to the organization's specific context, rather than implementing a model that was never designed to fit.

It also helps to look outward: understanding how peer organizations have changed their operating rhythms, and what benefit that has delivered, can be a valuable input, as can insight from relevant industry bodies.

Ultimately, Agile is about a shift in mindset. Agile ways of working require leadership buy-in, a genuine shift in thinking, and the right processes and tools. Without all three moving together, meaningful change is nearly impossible.

Leadership Buy-In

Agile starts and stops at the top. The decision to implement Agile needs to come from the top, with full commitment from the executive team to the change that is about to happen. Alignment and endorsement from the leadership team is critical to the success of any Agile rollout. Employees need to see a consistent message from leadership about how the organization will operate and how Agile supports its broader strategy and vision.

It is worth pausing here to consider what "leadership" actually looks like in your organization. Senior executives and the C-suite are often the easier group to bring on board. It is frontline leaders, the middle managers who directly supervise line employees, who are typically harder to win over, and whose support matters just as much.

BCG research on diversity and inclusion in the workplace found that even when the executive team is fully committed, employees working under a less engaged direct manager are far less likely to feel welcome and included, and are considerably more likely to leave for another job. While that research focused on D&I specifically, it illustrates a broader point that applies directly to Agile transformation: frontline leaders have an outsized influence on how change actually lands. Securing buy-in from leaders at every level, executive and frontline alike, is essential.

OKRs, or What's the Plan?

Without a clear picture of where the organization is heading, it is unreasonable to expect others to follow in good faith. Sharing the future vision brings people into the journey, giving them the chance to consider how they might be part of what comes next.

If the goal is genuine new ways of working rather than simply checking a box and calling the organization "Agile," a clear vision, defined goals, and a visible roadmap are essential. In practice, this often means setting OKRs, mapping them across the quarter, and placing them on a roadmap so the team can see what the period ahead looks like. From there, work is broken into small, manageable increments, and the team is trained in its new ways of working.

A Shift in Mindset

Leadership buy-in brings with it a shift in mindset, both for leaders and for employees more broadly. As employees begin to see the benefits of new ways of working through pilot teams and visible leadership actions, that mindset shift starts to take hold and spread through the organization. Communication is key to sustaining it.

Frontline leaders, the middle managers with the most direct influence on day-to-day employee experience, are particularly critical when it comes to implementing large-scale cultural change. Once the shift begins, it travels through the organization, but only if communication keeps pace.

Implementing Agile, like any significant change program, requires people to redefine their role and identity within the organization. That is a substantial ask, and it requires giving something in order to get something back. People need timely information and, often, coaching to help them navigate the transition. The plan needs to address how decision-making, work breakdown, and operating rhythms will change across the organization. This is achieved by designing new ways of working and supporting people as they build new behaviors and habits that underpin an Agile culture.

As the transformation matures, the shift in mindset becomes visible across the organization, from leadership through frontline managers to every employee. It changes how problems are approached and how products are brought to market.

Agile Processes and Tools

Begin with a Pilot Team

To introduce new ways of working, an organization needs to empower a team to drive the process forward. This is best done through a pilot team whose work is externally visible and whose success can be measured.

Agile transformations generally follow one of two paths. The first is a top-down, "big bang" approach: prepared and executed in one significant move, often taking months or years to plan, and requiring real determination and leadership commitment to shift the organization to new ways of working all at once. This path is achievable, but relatively risky, since it leaves little room to test and learn before adjusting the operating model to the organization's specifics.

In our experience, a bottom-up path tends to work better for Agile transformation. After an initial readiness assessment, one or more pilot teams are launched to create "pockets of Agile," or lighthouse projects. As those teams begin working and running retrospectives, adjustments naturally follow, whether to cadence, ceremonies, artifacts, or even terminology. These refinements allow more teams to adopt new ways of working effectively and often produce strong results early on.

Training the pilot team properly is essential to ensuring an effective cascade through the rest of the organization. This is a test-and-learn exercise, supported by Agile coaching from the outset. Giving the team room to build new skills while solving genuine organizational problems allows the wider business to see different ways of working in action and observe real results. Being open and transparent about outcomes, including where the team fell short, what was learned, and what would change before wider rollout, builds credibility for the transformation. Making the pilot team's workspace visible and interactive, so others can visit, ask questions, and see the artifacts in use, helps build momentum and interest across the organization.

Real Transformation Creates Value Beyond IT

Transformation creates lasting value when it changes underlying culture and values, and that takes dedication and sustained effort. Many organizations fail to recognize the value of Agile beyond IT, which is typically where these journeys begin. The benefits at that stage are visible, but tension between IT and the rest of the business often persists. The natural next step is to invite parts of the business that work closely with IT into cross-functional teams.

Typically, the parts of the business involved in developing products and processes come on board at this stage, and many organizations stop there, leaving the rest of the business and support functions out of the transformation. As long as that gap exists, the full benefits of new ways of working remain out of reach.

Extending new ways of working to the remaining business and support functions is a step worth taking. The fact that these areas do not develop products or run projects directly is not a reason to leave them out of the transformation. With some adjustment to methods, tools, and collaboration models, every unit begins to speak the same customer-focused language, and a genuinely Agile organization starts to emerge.

At this stage, new mechanisms and tools for alignment (such as OKRs and quarterly business reviews) and for autonomy (such as portfolio design with clear accountabilities and supporting leadership behaviors) are tested and refined. This allows the operating model to be adjusted to the organization's specific needs before scaling further, while the early success of pilot teams builds interest and buy-in across the rest of the business by showing what "good" looks like in practice.

No Time Like the Present

Organizations that feel weighed down by legacy processes are best served by simply beginning. Start with the why, do the diligence, bring in the right expertise, and set up a pilot team to get moving.

Where AI Fits into Agile Transformation

The fundamentals of Agile transformation, mindset, leadership commitment, and disciplined new ways of working, have not changed. What has changed is the toolkit available to support them, and AI is increasingly part of that toolkit. Used well, AI reduces friction in the mechanics of Agile delivery and amplifies the impact of sound practice; it does not replace the judgment and discipline that good transformation still depends on.

In practice, this shows up in several tangible ways. AI can synthesize retrospective feedback across many teams to surface patterns leadership might otherwise miss, helping distinguish a one-off issue from a systemic one. It can scan a backlog for recurring themes or duplicated effort, giving teams a clearer view of where their work is actually concentrated. For distributed teams, AI-supported asynchronous stand-ups help maintain daily alignment across time zones without adding meeting load. On the leadership side, predictive analytics can flag delivery or capacity risk earlier in a quarter, and sentiment analysis across team communications can give leaders an early read on morale during a transformation, well before it shows up in formal engagement surveys.

The organizations getting the most from this are the ones that treat AI as an amplifier of Agile discipline, not a shortcut around it. A pilot team with strong retrospective habits will get more out of AI-supported synthesis than one without; a leadership team already committed to transparent communication will get more value from sentiment insights than one that isn't. AI raises the ceiling on what good Agile practice can achieve. It does not lower the bar for the fundamentals discussed above.

ADAPTOVATE thanks our consultants across Melbourne, Sydney, Warsaw, and the US who contributed their perspectives to this piece.