When introducing change in your organisation, sometimes the impact of that change may not be so obvious. Without doubt it holds true that the more changes you work on and introduce the more you understanding the ripple effects of the change you are introducing. This why impacts are more broader than the behavioural change that is required. The broader the net the easier it is to enact the required change activities to support those who need it and to address the changes required. 

Connected thinking is necessary to develop and will develop over time if you learn from implementing change. A combination of various contracts in my career in various industries, introducing various changes built my ability to think differently about change impacts. There was a sense of similarity but also a respect for the connectedness in organisations which mean that the connection points were to be identified and included in change plans.

This is in sync with the concept of the butterfly effect....

Organisational agility is not just about changing, it is about changing FAST! But how do you develop organisational agility at speed?

To transform the ways of working and achieve true agility you need a Transformation program which is focused on delivering the change. Key elements of this program would include the following:

1) Land on an agreed definition. This is important more than ever, as everyone has different ideas about what AGILITY means or looks like. Agreeing on a shared vision will assist bring it to life. Define AGILITY in real terms. Even more importantly it is always good to have measurable outcomes lined up with AGILITY. Does this mean delivering on continuous improvement projects faster? Does it mean improving customer satisfaction rates in two areas that relate specifically to agility? And then what are the success measures across the organisation. You can define them and create an 'agility' rating or dashboard showing progress across the organisation. Remember...

Technology change is one of the reason's that the disciplines of project management and change management exist in the first place. And what we mean by that is that technology failures are the reason why both disciplines are in place. Both the project discipline and the change discipline have been changing and adjusting to the growing realisation that bridges need to be built between technology delivery areas and business areas. Agile ways of working were a blend of discipline at speed. Yet there continue to be tech failures delivered and remediated. Why? Well if you have worked on or experienced poorly designed and delivered technology solutions, (as I have) then themes begin to appear.

Following are some key themes for you to reflect upon for your digital change and whether these are being approached in the right way. Here are some 'Must DO's': 

1) Be sure to explore the problem enough, before deciding technology is the solution. Many, many times, there is a shiny piece...