Westrum’s Organisational Cultural Typologies

“Culture Eats Strategy for Breakfast”

A statement famously (but erroneously) attributed to Peter Drucker, which essentially means that however much you work on your strategy, you ultimately cannot ignore the “people factor”. It is people that execute your strategy and it is through people that it will succeed or fail.

People Create Culture

The most important aspect for any organisation is people and how they interact. Not strategy, not processes, not operations, and not even finance. An organisation is built of relationships between people (plus some processes, and software) and people create culture. If strategy consists of the rules of the game, culture will determine how the game is played. Culture is how people behave and communicate.

Psychological safety is often an emergent property of great organisational culture, but that doesn’t mean you can’t explicitly and purposefully work towards it and state that one of your goals for the organisation is to possess a great degree of psychological safety. Indeed, the first step in an intelligent journey to build psychological safety is often stating your goal and asking for help in getting there.

Psychological Safety and Culture

I’ve previously written about how to measure psychological safety, but measuring culture can be more challenging. Following his work in 1991 on technologies and disasters, Dr. Ron Westrum wrote in 2003 about The Typologies of Organisational Cultures that reflect how information flows through an organisation. He wrote: “organisational culture bears a predictive relationship with safety and that particular kinds of organisational culture improve safety…” That is to say, because information flow is influential and indicative of other aspects of culture, it can be used to predict how organisations or parts of them will behave when problems arise.

Westrum was focussed on real-world safety measures in the realm of healthcare and aviation, but in our technology world we should strive to adopt the same diligent approach to safety for the sake not just of the products we build but for the humans on our teams as well.

Culture is the almost intangible aspect of an organisation that so often reflects the CEO’s personality or the stance of the board members. As Westrum states:

“Culture is shaped by the preoccupations of management.”

For example, if management, particularly senior management, are most concerned about exposure to risk, the organisational culture will reflect that, with processes and checks in place to ensure risk is reduced wherever possible; this usually results in a decreased focus on innovation, lower speed to market, and a low appetite for change.

In 2015, Jez Humble, Joanne Molesky, and Barry O’Reilly wrote the book “Lean Enterprise: How High Performance Organizations Innovate at Scale”, which highlighted how critical culture is to performance, and highlighted Westrum’s Typology model. “Instead of creating controls to compensate for pathological cultures, the solution is to create a culture in which people take responsibility for the consequences of their actions.

The 2016 state of DevOps Report also showed that Generative, performance-oriented cultures improve software delivery performance, alongside market share, productivity and profitability.

Westrum’s Typologies subsequently appeared in Nicole Forsgren’s book “Accelerate” in 2018, where she was able to show that generative cultures were associated with improved software delivery performance (the four Accelerate Metrics) and other organisational capabilities for learning.

Westrum’s Organisational Typologies

See the table below for Westrum’s organisational typology model of Pathological, Bureaucratic, or Generative (Westrum had previously used “calculative” but later decided that bureaucratic was better interpreted by people in organisations). Each column describes a broad cultural typology and six aspects of those cultures. It is clear from the table that the Generative culture that Westrum describes is a broadly psychologically safe culture where team members cooperate, share their fears, admit failure and continually improve.

Pathological Bureaucratic Generative
Power oriented Rule oriented Performance oriented
Low cooperation Modest cooperation High cooperation
Messengers “shot” Messengers neglected Messengers trained
Responsibilities shirked Narrow responsibilities Risks are shared
Bridging discouraged Bridging tolerated Bridging encouraged
Failure leads to scapegoating Failure leads to justice Failure leads to inquiry
Novelty crushed Novelty leads to problems Novelty implemented

The Westrum organisational typology model: How organizations process information ( Ron Westrum, “A typology of organisation culture),” BMJ Quality & Safety 13, no. 2 (2004), doi:10.1136/qshc.2003.009522.)

By surveying people across the organisation, you can establish the broad typology in which your organisational culture sits, and identify measures to improve. Ask respondents to rate their agreement on a 1-5 scale (1 being not at all, 5 being complete agreement) with the below statements:

  • On my team, information is actively sought.
  • On my team, failures are learning opportunities, and messengers of them are not punished.
  • On my team, responsibilities are shared.
  • On my team, cross-functional collaboration is encouraged and rewarded.
  • On my team, failure causes enquiry.
  • On my team, new ideas are welcomed.

These 6 statements are from Dr Nicole Forsgren’s research into high performing teams at DORA.

Each of these statements align with a row in the table above, so by collecting and analysing the average scores, you can quantitatively determine where your organisation resides in Westrum’s Typologies. Analyse the standard deviation of the scores to determine both the range of scores and the degree of statistical significance of the results.

Average these scores for your summative Westrum’s Typology score. Close to zero suggests your culture is towards “Pathological”, 2-3 suggests Bureaucratic, and 4-5 suggests a Generative culture:

The individual statement scores suggest areas for improvement. For example, if your score for statement 4 is particularly low, investigate and employ practices to improve collaboration between different functional teams, ask teams what challenges they face in communication and collaboration, and facilitate informal gatherings or events where people in different teams can get to know each other.

Intra-Organisational Psychological Safety

Ron Westrum describes a culture of “safety” in Generative organisations, and it’s easy to see how psychological safety is both increased in, and fundamental to, Generative cultures. Amy Edmondson, in 2008, described “Learning Organisations” in her paper “Is yours a learning organization?” and similarly suggested an assessment framework to measure how well a company learns and how adeptly it refines its strategies and processes.

There are many ways to improve the psychological safety of your team and your organisation, but sometimes as a leader, your influence may not extend very far outside of your team, and as a result, you may decide to build a high-performing, psychologically safe team within an environment of much lower psychological safety. This is admirable, and most likely the best course of action, but it is one of the most difficult places to put yourself as a leader.

Consider the “safety gradient” between your team boundary and the wider organisation. In a pathological or bureaucratic organisation, with varying degrees of toxic culture, that safety gradient is steep, and can be very hard to maintain as the strong leader of a high performing team. You may elect as your strategy to lead by example from within the organisation, and hope that your high-performing, psychologically safe team highlights good practice, and combined with a degree of evangelicalism and support, you can change the culture from “bottom-up”, not “top-down”.

This can work, and it will certainly be rewarding if you succeed, but a more effective strategy may be to build your effective team whilst lobbying, persuading and influencing senior management with hard data and a business case for psychological safety that demonstrates the competitive advantage that it can bring.

Create Psychological Safety

Take a look at my Psychological Safety Action pack, with a ready-made business case and background information, workshops and templates, to give yourself a shortcut to influencing and build a high performance, psychologically safe, and Generative organisational culture.

For any further information on how to build high performing organisations and teams, get in touch at tom@tomgeraghty.co.uk.

Three Simple Psychological Safety Exercises

It’s a long and worthwhile journey to build high levels of psychological safety in your team, and much of the hard work involves excellent leadership, clarity of direction, effective support, vulnerability, curiosity and much more.

However there are some simple exercises that you can carry out with your teams that directly build psychological safety. See below for four effective exercises and practices to build psychological safety, cohesion and performance.

1 – Run a Values and Behaviours Workshop

Workshop with your team to establish and refine the main values that all members of your team endorse. From these values, extrapolate the behaviours, with your team members, that reflect these values and help the team work together to achieve their goals.

For example, “blamelessness” could be one of your team values, and a behaviour that reflects this could be “Taking collective responsibility for mistakes.”

Sharing common expectations of behaviour is fundamental for psychological safety in a team.

As a result of carrying out this Values and Behaviours workshop:

  • Team members understand what is expected of them and others.
  • Team cohesion and performance improves.
  • The team are aligned to the values of the organisation.
  • Boundaries regarding acceptable behaviours are agreed.
  • The degree of psychological safety of team members increases.

2 – Hold a “Fear Conversation”

Whilst psychological safety is not about existential or external threats, it is very much about being able to show vulnerability and emotion. This exercise encourages that behaviour and builds psychological safety by making openness a norm for the team. It also provides some actionable outcomes to deal with real-world risks and threats.

On a white board or flip chart, create three columns – one for “Fear”, one for “Mitigations” and one for “Target State”.

In the fear column, write down some of the fears that you and team members possess in the team, such as “missing deadlines” or “making mistakes”. Ask everyone to contribute, but make sure that as the team leader, you go first.

Then, as a team, come up mitigations to these fears, which consist of practical things team members can do to reduce the risk of the fears becoming real. Or, in case those fears are inevitable, instead write down ways that the impact can be reduced.

Finally, discuss and write down your “Target State” – this is your team’s utopia, where “everyone can make mistakes without fear of repercussions” or “we never miss a deadline”. This helps the team cohere around common goals and aspirations, which are essential to building psychological safety.

3 – Run Retrospectives

Carrying out regular retrospectives to find the systemic root cause of failures, problems or mistakes is one of the most valuable things you can do as a leader in your journey to building psychological safety.

Ensure that any retrospective is given enough time and is carried out in an appropriate setting. Team members need to feel able to be honest and as vulnerable as possible, so carry it out in a non-public area and certainly don’t record it if you’re carrying out over a video call.

Highlight, discuss, and deep dive into the things that went well, the things you need to change as a team, any lessons learned or anything still to be discovered.

Identifying root causes of failure without apportioning blame is crucial to psychological safety, because team members need to know that they can take intelligent risks without fear of repercussions, humiliation or punishment.

For more detailed guides in the above workshops, along with templates and examples, download the psychological safety Action Pack.

Psychological Safety and Digital Transformation: WB40 podcast

wb40 blocky

Matt Ballantine and Chris Weston were kind enough to invite me onto the WB40 podcast for this episode discussing psychological safety and digital transformation.

We discussed the key concepts and history of psychological safety, from the lack of safety culture that ultimately caused the Chernobyl disaster, to Amy Edmondson’s research into high performing clinical teams. We covered how to engage with your team about how to build psychological safety in the workplace, and how it doesn’t just result in feeling good, but with the right environment, results in truly greater performance and higher delivery, particularly when leaders take into account the four stages of psychological safety.

If you’re interested in psychological safety and how it relates to DevOps and software development or how Conway’s law and cognitive load dovetail into improving psychological safety, and the quality of the services or products your team delivers, give it a listen.

Strategically, psychological safety must be at the heart  of any organisational transformation or evolution, since it remains the single most crucial aspect of any high performing team; and only high performing teams will provide the competitive advantage required for real success.

If you’re interested in measuring, building, and maintaining psychological safety in your team, download my workshop and action pack, full of guides, plans, tools and resources to elevate and empower your teams.

 

 

Psychological Safety Action Pack: Workshops and Resources

building and maintaining psychological safety for your team

Do you want to improve the performance, velocity, engagement and ultimately, happiness of your teams and your organisation?

This is a complete Psychological Safety Action Pack containing background information, a business case, six-month planner, measurement tools, workshops, exercises, checklists, posters and templates to work on with your teams!

Already used by successful organisations around the world, you can apply these tools and techniques to build psychological safety in your team and across your organisation.

download now

Whether you’re new to leadership, taking on a new team, or working with a long-established group, this will help you take your people and your leadership skills to high-performance and happiness. Designed for novices and experts alike, the resources are easy-to-use and customisable for your situation.

Remote psychological safety

The Psychological Safety Action Pack consists of twenty individual resources, together with links to further reading and useful information.

Through three phases of work: Planning, Implementation, and Reflection, the Psychological Safety action pack contains all the resources and workshop materials you’ll need to unleash the potential of your team.

Tuckmans model of team performance

Download the tool kit via instant digital download. You will also receive a link via email to re-download should you need to.

The pack contains:

  • An introduction to psychological safety
  • A business case template
  • Planning templates,
  • Survey tools to measure psychological safety
  • Targeted actions and checklists resulting from the survey
  • Specific resources for remote teams
  • Three different workshops with guides and resources
  • Retrospective templates
  • Self-reflection and improvement guides
  • Posters
  • Background information
  • Links to further resources

If you work for a charity or non-profit organisation, email psychsafety@tomgeraghty.co.uk from your organisation email account to receive the Action Pack free of charge.

The Action Pack will be delivered as a compressed zip file (under 10MB) and a link to download the pack will also be sent to your registered email address.

Download the action pack now.

Thanks to Chris Wilkinson (https://unexampled.co.uk/) for his excellent work in turning my workshop template sketches and vague poster ideas into reality.

Measuring Psychological Safety in your Team

measuring psychological safety

We know psychological safety is crucial for high performance teams, and particularly so for technical delivery teams. Innovation is so critical for creating products that delight customers and serve critical business needs, and psychological safety is a fundamental enabler of innovation.

Below are ten questions that you can ask yourself or your teams to determine the level of psychological safety in your team. Rate agreement with the below statements on a scale of 1 – 5. 5 being “completely agree” and 1 being “completely disagree”.

When carrying this exercise out with your team, perform the survey anonymously – if it’s possible that your team are psychologically unsafe, they will be more likely to be honest if the survey is anonymous. If the team are very psychologically safe, then it won’t matter if the survey is anonymous or not.

It is also important to allow for qualitative, verbose feedback for each question as well, because that verbose feedback will facilitate and clarify some of the actions that you may need to take in order to improve these scores.

  1. On this team, I understand what is expected of me.
  2. We value outcomes more than outputs or inputs, and nobody needs to “look busy”.
  3. If I make a mistake on this team, it is never held against me.
  4. When something goes wrong, we work as a team to find the systemic cause.
  5. All members of this team feel able to bring up problems and tough issues.
  6. Members of this team never reject others for being different and nobody is left out.
  7. It is safe for me to take a risk on this team.
  8. It is easy for me to ask other members of this team for help.
  9. Nobody on this team would deliberately act in a way that undermines my efforts.
  10. Working with members of this team, my unique skills and talents are valued and utilised.

To explain the context behind each question:

1 – On this team, I understand what is expected of me.

It is essential that team members understand what is expected of them in terms of delivery (speed, quality, cost, and other factors) and behaviour (everything from dress code and punctuality to coding standards) to foster psychological safety. Ensure tasks are clear and well defined, behaviour expectations are explicit, and negative behaviours are dealt with.

2 – We value outcomes more than outputs or inputs, and nobody needs to “look busy”.

Outcomes (such as revenue generated or satisfied customers) matter more than outputs (emails sent, lines of code written, or meetings attended). If the team focus on what truly matters to the business, they are safe to make decisions that can improve outcomes, even if those decisions reduce output. The ideal is a team that possesses enough psychological safety to decide not to do something that could make them look good in the eyes of others, but doesn’t deliver outcomes for the business.

3 – If I make a mistake on this team, it is never held against me.

A psychologically safe team will never blame a member of the team for a genuine mistake if their intentions were good. Indeed, by enabling mistakes to be made without a fear of blame, you enable innovation and risk taking that can drive your organisation ahead of the competition. Utilise systems thinking and DevOps approaches to prevent mistakes before they happen or mitigate the impact of mistakes when they do.

4 – When something goes wrong, we work as a team to find the systemic cause.

Related to the previous point but important enough to warrant its own question, a system of discovering the root causes of mistakes and failures means that not only do team members feel able to take risks without being blamed, but every single “failure” is an opportunity for learning and improvement. By building psychological safety through these retrospective exercises, everyone on the team gets to learn from mistakes, meaning mistakes are a gift, not a threat.

5 – All members of this team feel able to bring up problems and tough issues.

In a psychologically safe team, all members of the team are able to bring up problems and tough issues, ranging from personal struggles to concerns about other (even senior) members of the team. This psychological safety is crucial for allowing both vulnerability to show when you’re struggling and need help, and courage to raise difficult topics.

6 – Members of this team never reject others for being different and nobody is left out.

Evidence shows that diversity in a team results in higher quality products and happier team members, but diversity in itself is not enough: it is crucial that team members are all included in decision making and delivering results. To facilitate psychological safety (and high performance) every member of the team needs to be invested in the decisions made and the outcomes generated. This is particularly crucial for remote and distributed teams, where it is more difficult to see if a team member is becoming disengaged.

7 – It is safe for me to take a risk on this team.

Mistakes happen unintentionally, but risks are about taking actions that might not work, or may have unintended consequences. Psychological safety provides the framework for positive risk-taking, enabling innovation and ultimately, competitive advantage.

8 – It is easy for me to ask other members of this team for help.

In psychologically unsafe teams, team members try to hide their perceived weaknesses or vulnerabilities, which prevents them from asking for help. In a psychologically safe team, members prioritise the team goals over individual goals. Helping others helps achieve the team goal, and because team members feel safe to ask for that help, psychologically safe teams achieve more of their goals than unsafe teams.

9 – Nobody on this team would deliberately act in a way that undermines my efforts. 

In an unsafe team, members compete with each other to achieve their individual goals, and may even undermine other team members if it could benefit them or it is perceived that doing so may elevate their “rank” within the team or organisation. In a psychologically safe team, that counter-productive competition doesn’t exist, and the success of the team is more important looking good in the eyes of others.

10 – Working with members of this team, my unique skills and talents are valued and utilised.

We all bring our own unique experience, skills and knowledge to the teams that we’re in, but we also bring our own prejudices and biases. In a psychologically safe team where members are valued for being their true selves, biases are less likely to manifest. Indeed, team members may feel safe enough to identify, raise, and discuss their own biases or those of other team members. By doing so, we provide space for each individual to maximise their potential from utilising their own unique skills and talents.

Regularly Measuring Psychological Safety

By measuring the degree of psychological safety on your team, you can begin to build your own unique strategy for developing and maintaining it. For instance, this may involve running more regular retrospectives or by workshopping the team’s values and behaviours.

Measurement is only a tiny part of the process. Download a complete Psychological Safety Action Pack full of workshops, tools, resources, and posters to help you measure, build, and maintain Psychological Safety in your teams.

Remember to be patient: this is a journey, not a destination, and work on your own psychological safety too. You can’t effectively help others if you don’t look after yourself.

Take this survey for yourself.