Accomplishing Organizational Transformation

This content is syndicated from George Dinwiddie's blog by George Dinwiddie. To view the original post in full, click here.

Scaling Agile across the Enterprise attracts a lot of attention these days. There are a number of models suggesting ways to organize Agile development inside a sizable organization with a lot of teams. I suspect that all of these models share the same basic flaw—that you can do something the same way across a large enterprise. Even if your policy manual says exactly how to do something, people are people and there will be variations in understanding and execution. And how does a team self-organize in a prescribed manner?

Beyond that, there’s the problem of getting from current state to a future state that resembles the model. It does not work to “install” a new way of working across a large system composed of people and their interactions. Some people suggest starting the transformation with management, as that’s the “highest leverage point” and the “system’s major influencers.” Others suggest starting with the teams, because without competence at building reliable software (or other systems) in short cycles of small steps, you’re not going to get the benefits of Agile Software Development. I don’t think that either of these starting points work.

“When we try to pick out anything by itself, we find it hitched to everything else in the Universe” — John Muir

In an organization, everything has influence throughout the organization. That influence is muddled in with a million other influences. While it’s true that upper management is charged with making the “big decisions,” when they’re candid they’ll admit that they have less control over how things happen than they’d like. They’re not even aware of all the things going on. It’s far too complicated for one, or even a small group of brains.

Organizations are self-regulating toward maintaining the status quo. When you try to change one part, to the extent it’s connected to other parts, it resists the change because of the influences of the other parts. To the extent it’s insulated from the other parts, it changes more easily but has less influence on the other parts. It’s a dynamic balance, ever-changing but quite robust.

Given this, how do you institute change in an organization?

I think you have to start with multiple levels, simultaneously. Every relationship in the organization is an equation that has to be solved. All of these equations are inter-related, and they have to be solved simultaneously. Each influences the others.

When trying to help an organization change, I start with every point where I might have influence. With each person who will engage in conversation, I try to understand what are their personal goals within the organization. I help them develop their own vision of the transformed organization. I offer alternative actions that they might not have considered. I urge them to have influence with those whom they have a relationship. I try to light a little fire of hope and change for the better.

And I try to light these fires in every place I can—among the development teams, the first line managers, the directors, and as far up the chain as I can reach. When there are important constituencies outside my direct reach, I encourage others to reach out to those constituencies. Or I ask them to bring us together, so I can have direct conversation. When working with other coaches, I depend on them to reach people that I have failed to reach.

These many small fires can result in major changes. Simultaneous changes in multiple parts of the organization can breed powerful synergies. The change goes in a direction influenced by the energies of the people engaged in the change. It’s not under any one person’s control, but shaped by the collective vision, action, and engagement of all.

Leave a Reply

What is 9 + 10 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”