Back to Blog

How to Spark Change with Agile Coaching, Part 2: Scaling Change

Adaptiveness to change is what makes companies future-proof, but on the other hand, ongoing change is extremely difficult to grasp on the individual and organizational levels. Eventually, everything will click into place once new ways of working have been implemented and scaled into use beyond the teams that first experimented with them.

This blog post concludes our two-part series that focuses on overcoming some of the hurdles commonly witnessed when initiating cultural change in an organization. Read the first post here.

Change demands effort and focus. When people are given the liberty to experiment and adopt new tools and ways of working, it will eventually sprout new ways of thinking. This was our guiding philosophy as we joined forces with Accountor’s SME cluster and set out to implement new ways of working for their Product Development teams.

The first steps along the way – covered in more detail in part one of this blog series – were acquiring executive buy-in, building a tight-knit team, and adopting a culture that embraces experimentation.

Finding the right mindset to keep the change alive

In order to keep the change going and evolving, our next challenge was to figure out how to support both individuals and the entire organization to change after the program ended.

In addition to new tools and ways of working, we focused heavily on understanding and challenging the underlying assumptions that control the ways we think and act. When it comes to change, it is all about shifting the mindset. As one participant put it:

“I am here to code! My attitude towards Agile Coaching was very skeptical in the beginning. However, I am positively impressed by what we have learned as a team through coaching, and by how we were able to improve our ways of working.”

A few months after the coaching sessions had ended, we were positively amazed by the attitude of continuous development, the learning mindset they had adopted, as well as the ongoing experiments the teams were running.

Agile is never ready. You have to keep using it and working with it all the time to keep developing as a team and as an organization.


Four steps from experimentation to scaling impact

Change is difficult to master, and people easily slide back to their old habits. Whenever new ways of working stick after the initial steps and change is steadily being driven driven forward by in-house teams – that’s a win in our books.

In an autonomous organization utopia, employees would plan and implement the next steps themselves, but in today’s corporate reality, the challenges and required changes can be complex and extend throughout the organization’s entire structure. So, finally, we had to figure out the necessary larger-scale steps to take after the Agile Coaching Program has ended.

This is what we eventually arrived at:

  1. Identify your influencers and let them drive the change. When scaling change, it is essential that the same teams that have worked their way through the program retain ownership of the change, drive it forward, and continuously develop their ways of working. Ideally, these people should serve as the forerunners that support and drive the change in the rest of the organization.

  2. Create and use new tools to guide the way. As a concrete outcome of the cooperation, we co-created an Agile Playbook that gathered all the experiments, materials, theories and practices in Lean and Agile in the context of Accountor’s SME cluster. Since the process of creating the Playbook was co-creative, it was already owned by the participants and left to them for further development. In this case, the Playbook serves as collaborative living documentation for the whole organization, and is available for everyone to comment and modify online. This Playbook guides the way in larger-scale change.

  3. Use what you’ve learned to scale towards the next iteration. The CSA and Agile Coaching sessions with the participating teams yielded tons of insights and experiences on what their challenges were, and what worked in this context. Over the next months and years, these learnings should be actively used and scaled to the entire Product Development as well as the organization beyond that.

  4. Focus on removing obstacles. Start dealing with the structural issues that blocked the way towards change for the pioneering teams. These issues will vary from organization to organization, and untangling them will require a great deal of direction, ambition and commitment from leadership. The high level obstacles we encounter are issues such as how Product Development is organized, how budgeting is done, how targets are set, and how people are rewarded.

Change needs to happen in two directions: bottom-up, by spreading from teams to the rest of the organization, and top-down, with executive support and commitment. Ultimately, in order to successfully transform culture, shaping ways of working is not enough – change needs to affect the entire organization, starting with daily operations, structures, and metrics.

Luckily, not everything has to happen at once – we can experiment and make change happen as we learn what really works.


  • Portrait of Anna-Mari Fagerström
    Anna-Mari Fagerström
    Principal Advisor Strategy & Culture
  • Portrait of Juha Männikkö
    Juha Männikkö
    Tech Principal
  • Portrait of Timo Into
    Timo Into
    Head of People Operations, Accountor Finago Product Development