· Executive Leadership  · 3 min read

Cloud adoption and organisation culture

Understanding the ability of an organisation to adapt to cross functional level changes

Understanding the ability of an organisation to adapt to cross functional level changes

I have the fine opportunity to work with multiple large enterprises to help them get started with their journey on cloud. Typically the ones that are very early in the journey take one of the few possible starting points:

  • They have a specific use-case for their business objectives and want to see if cloud can help address it.
  • Alt; They endlessly evaluate cloud providers without a specific goal in mind - this is mostly to bring themselves up to speed with what’s latest in the cloud space

However, whichever route they tend to take, it’s interesting how some organisations just get on with adoption while others just don’t seem to make a huge amount of progress despite the number of interactions.

I did wonder what sort of frame of reference could we look at an organisation with - in order to better understand how we could help the slow/never starters to make progress as they fundamentally believe it was the right thing to do but just struggled because of the way their organisation was structured.

Reading the State of devops report for 2018 I spotted a theory around measuring the culture of an organisation which seems to have a direct correlation to how quickly they adopt changes. Using cloud is one of those fundamental shifts as well that impacts a big chunk of the organisation not just IT.

Nicole and her team mentions an academic paper written by Ron Westrum, an American sociologist who originally published in Quality and Safety in Health Care, an international peer-reviewed journal for health professionals, “A Typology of Organisational Cultures”.

Interestingly she uses this culture typology approach to evaulate the rate of adoption of devops but I assume it could equally be applicable to identify cultural shift required to support the changes required for cloud adoption.

What is ‘westrum typology’ then?

It is a grouping, around the way organisations function, especially based on the focus of management and the response of the workforce to the focus. It can be used by organisations as a pulse check to see if there are aspects of the culture that need more focus than others.

The typology identifies three different categories

  • Pathological - characterized by large amounts of fear and threat. People often hoard information for political reasons or distort to make themselves look better
  • Bureaucratic - protect departments. Maintain their turf, insist on their own rules and follow them
  • Generative - focus on the mission - everything is subordinate to good performance.

Interestingly while an organisation fits in an overall bucket - each department has its own culture and interestingly sometimes, its culture also varies based on the leadership at the point in time. Identifying and addressing areas, moving aspects of the culture left to right would help with:

  • Organisational performance overall
  • Strong predictor of job satisfaction and initiative taking
  • High trust - generative culture for a safe working environment to try out new ideas (e.g. changing the way things have fundamentally worked)

Perhaps with frameworks like GCAF we should also look at the culture maturity framework as well that can help organisations build a roadmap aligned to initiatives that require cross functional change.

How has cloud adoption been for your organisation? I would love to hear more about the real challenges that you have encountered and how you approached to get them addressed.

Share:
Back to Blog

Related Posts

View All Posts »
Emerging Tech Projects - Avoid these common pitfalls.

Emerging Tech Projects - Avoid these common pitfalls.

Some ideas on what to watchout for enterprise when starting new projects using emerging technology. This post talks about aspects of scoping, ownership and technology changes. Most of it is obvious but less commonly

Part I - Why do large enterprises need a Chief AI Officer?

Part I - Why do large enterprises need a Chief AI Officer?

Having spoken to a lot of organisations keen on adopting AI at scale - the pattern for systems eventually breaking down is consistent. In this post I make a case for a role of a Chief AI Officer and also talk about how they can be most effective.

The theory behind Technical Debt

The theory behind Technical Debt

Technical debt is not new, This weekend I went down the trail to read-up on its impact due to the increased throughput of code generation thanks to AI. Turns out AI code generation is a double-edged sword. Lightning-fast code creation can mask underlying architectural flaws, poor naming, and inadequate testing. Often creating more of the uncoordinated code.The right approach? Thoughtful AI integration that learns from existing code-bases, not blindly generating new code.

Three Phases of Generative AI Development

Three Phases of Generative AI Development

We are practically in year two of generative AI being in mainstream. Organisations are still figuring out a path to production where they can align the user delight with total cost of ownership along with getting a sizeable return on investment. This post talks about the pattern very prevalent to arrive at the outcome.