Developing an Agile Mindset: How to Cultivate Flexibility in Organizational Change

Agile started life as an approach to uncertainty, it then became a range of methodologies and rules for working iteratively and incrementally. Now, I think there is a more mature approach, recognising that agility doesn’t need lots of rules, it needs a willingness to be flexible in the face of constant change. It is a way of thinking and behaving. 

As the author of the Agile Change Management handbook and acting as Chief Examiner for the APMG-International Agile Change Management certifications, I have seen that the organisations that succeed with agile change management are not the ones with the best frameworks. They are the ones where people have developed an agile mindset.

What Is an Agile Mindset? Definition and Key Characteristics

My agile mindset definition is simple: it is a set of beliefs about how work should be done that lets people respond to change with an open mind, willingly questioning if the scope of the change is right, seeking out inter-dependencies with other work, being curious about the impact of the change and how progress and achievement can be tracked and proven. 

An agile mindset expects uncertainty and keeps checking if what we think is known is really true or if it is an assumption that makes things feel more stable than they really are. This mindset celebrates tailoring how we do things to our current circumstances. Rigidly following a single method is the opposite of the flexibility we associate with agile.

When I help clients define agile mindset characteristics, I start with these beliefs:

• Delivering something on time is better than delivering everything late.
• Feedback is a source of useful ideas, not a criticism.
• Changing what we create as we learn is a success, not a failure of the original design.
• The voice of the customer is always worth listening to.
• Everyone is responsible for having an opinion about improvements.
• Teams are made up of experts who can be trusted to organise their own work.

These beliefs have a lot in common with a growth mindset. They assume that we get better through iterative loops of trying, learning and improving, which is the essence of continuous improvement.

Why Agile Mindsets Matter in Organisational Change

The volume of change we are dealing with has transformed. Gartner has reported that the number of enterprise-wide changes affecting the average employee at the same time has risen from 2 to 10 since 2016. Traditional, linear change management models were never designed for this. They treat each change as a separate event, but that is not how any of us experience change at work.

This is why I developed agile change management. It brings agile principles together with models of behavioural change, so that we manage the tangible change (the new system, product or process) alongside the behavioural change (the new skills, routines and habits people need to use it). We take small steps, review our progress in the light of everything else that has changed, and decide on the next most valuable step. It is benefits-led, not requirements-led which means we do the work that gives us the greatest improvements and advantages, not blindly follow a list of things that should be included, just because they are on the list!

Change agility depends on this agile mindset, which is a mixture of our values, beliefs and priorities. Without it, people experience every iteration as yet another disruption. With it, they see each cycle as a chance to realise benefits early. There is a neuroscience reason too. Small cycles of change give the brain the certainty and frequent achievements it craves, which reduces stress and frees up the energy we need for new ideas.

Core Examples of an Agile Mindset in the Workplace

Agile mindset examples are easiest to spot when something unexpected happens. This is how fixed and agile behaviours differ in situations I see every week:

Situation	Fixed mindset response	Agile mindset response
The scope changes suddenly	“We can’t keep moving the goalposts.” Everything goes through formal change control.	Re-prioritise: what is the most valuable thing we can deliver now?
A manager has a new idea every day	Try to action every idea immediately.	Agree criteria that show which ideas matter most, and hold the rest on an ideas board.
A sponsor asks for a detailed end-to-end plan	Produce a Gantt chart that implies a certainty nobody has.	Share a visual roadmap with a clear end goal, and plan only the next iteration in detail.
A release gets poor feedback	Look for someone to blame.	Ask what we have learned, and build it into the next version.

Here is a real-life example from one of the learners on my Agile Change course. She worked for a manager who constantly came up with new ideas and expected them to be actioned straight away, forgetting how much work was already in progress. After the course, she took him through the prioritisation criteria. Together they agreed how to judge every new idea, and the lower-priority ones now wait on an ideas board until their time comes. 

Another delegate, a team leader, went straight back to his team and turned their messy group of projects into a single backlog. It transformed how easily they could explain their work to senior leaders.

How to Cultivate an Agile Mindset Across Your Teams

An agile mindset grows in the right agile environment. When clients ask me what an agile environment is, I describe the cultural and operational conditions that make it safe to adapt. These are the five I focus on.

Build psychological safety

Experimentation is at the heart of agile, and nobody experiments if they fear the consequences of failure. Run blameless reviews. When something goes wrong, ask how we got here and how we avoid it next time, not whose fault it was.

Set clear boundaries of authority

Empowerment does not happen spontaneously, and it is not always obvious how much power someone has. I always encourage leaders to be explicit, using examples to illustrate the subjects and situations that team members are empowered to deal with on their own, and which “hot buttons” need to be escalated to senior leaders for immediate action. Frustration levels can get very high when this is not done, because senior managers are frustrated if too much is escalated and anxious if too little is escalated, whilst team members find the uncertainty is stressful as they second guess whether they should act or ask for permission first.

Organise collaboration

I define collaboration as the organised sharing of activities and information. Cross-functional collaboration is vital because so much of our workflows from upstream to downstream, as we use common systems and data to complete our work. However, it is not always obvious who is involved in a complete end to end workflow, so we need to invest time in finding this out. Once we know all the players involved, we can agree how to share information, track progress and take decisions with your colleagues.

Make the work visible

A visual roadmap showing proportionally that some iterations are longer than others, clearly identifying the outcomes to be achieved for each iteration and how the outcome is broken into smaller pieces assigned to sprints within each iteration gives everyone vital information about what needs to happen and when. Our brains process visual images far more easily than words, and ticking off each sprint as it finishes and each outcome as it is achieved are small moments that keep everyone motivated to do more.

Close every loop with reflection and celebration

The pressure we are under to cope with high volumes of work mean we are too quick to move onto the next thing, missing an important opportunity to not only celebrate our achievements, but also to create for ourselves a clear understanding of where we are now. With every change we make, we are building a new way of working, and collecting changes together as a new baseline of accepted working practices gives us stability to take the next leap forward. 

The Implementation Gap: Why Reading About Mindsets Won’t Change Behaviour

Here is the uncomfortable truth. Reading about an agile mindset, including this article, will not change workplace behaviour. Neither will motivational posters or a one-off workshop. This is the knowing-doing gap. Everyone agrees that feedback is valuable until their own work is criticised, and everyone supports empowerment until a decision goes a way they would not have chosen.

None of us change our beliefs and values overnight. A lasting behavioural shift comes from practising new techniques again and again on real work, with support. The skills needed to navigate continuous change do not develop by themselves, and a single training day is no match for a challenge that is permanent.

I see the same gap at organisational level. Many agile implementations have made organisations very good at creating new things, but not at helping the business adopt them without destabilising day-to-day work. Closing that gap takes people who can lead others through change, not just deliver it.

Bridging the Gap: Developing Accredited Agile Change Agents and Coaches

The organisations I work with that close this gap give specific people the role of turning agility into everyday habits and governance. These practitioners translate abstract principles into practical action. They scope and prioritise the change, build the roadmap, coach their colleagues and keep everyone focused on the benefits.

This is why I worked with APMG-International to create two accredited certifications.

Agile Change Agent gives you the techniques to apply agile concepts to scoping, planning and prioritising both tangible and behavioural change, including how to build and manage an agile change roadmap. It has been adopted by organisations as diverse as utility companies, airlines and charities, hospital groups, tech start-ups in one country 2500 schools who use this approach to constantly challenge their curriculum. Agile Change Management is used by organisations of every size across Europe, the UK, the US, Australia and New Zealand.

Become an Accredited Agile Change Agent

Agile Change Coach is built on the 43 practical techniques in the second edition of my Agile Change Management handbook. It uses neuroscience and positive psychology to help you coach people from their first awareness of a change through to adopting new ways of working, with techniques for resilience, positivity, participation and celebration. In the last 10 years I have helped thousands of people improve their ability to motivate and persuade themselves and their colleagues to change how they work.

Explore the Agile Change Coach Certification

Both certifications carry APMG accreditation, and once you have a qualification, nobody can ever take it away from you. If you want your organisation to develop a genuine agile mindset, start by developing the people who will lead it.