Psychological Safety in High Performing Teams – Digital Lincoln Meetup April 2020

This is a recording of a webinar I did for the meetup group Digital Lincoln on the 28th April 2020.

Psychological Safety in High Performing and Distributed Teams

Safety isn’t just necessary in order to prevent disasters, it’s also crucial to building and maintaining high performance teams and organisations.

Building high performing software requires high performing teams, in which team members need to feel able to express their creativity, talents and skills without self-censoring, self-silencing, or fear of failure. In this talk, Tom introduces the latest research in high performance technology teams, and provides actionable concepts to help you build and elevate your team, whether co-located or distributed and remote.

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.

Find out about Psychological Safety and Information Security, and more here about high performing design teams who utilise psychological safety.

Tom is an expert in transforming team performance. A “veteran technology team builder” according to Computing Magazine, Over his 15 years as a technology leader, he has come to believe that culture trumps strategy, and happiness precedes success.

Tom is currently the Head of Technology at MoreNiche in Nottingham, CTO of Ydentity, an identity protection startup, and a management consultant for Q5. Outside of work, Tom is a yoga teacher and mountain biker.

https://www.crowdcast.io/e/missile-destroyers

Team Topologies, Psychological Safety and Digital Transformation at MoreNiche

 

MoreNiche is a highly successful performance and affiliate marketing agency based in Nottingham, UK. Founded by CEO Andy Slack in 2002, the company has weathered dramatic market shifts and recessions to become a successful, durable and high-energy organisation. After a structural change in April 2019, Andy decided it was time for a reboot, and wanted to create a values-driven, innovative organisation that was a great place to work as well as being highly successful in an ever more competitive marketplace.

To assist us on this journey, the key MoreNiche values were distilled through a series of workshops and collaborative work:

  • We Rewrite the Rules
  • We are Radically Inclusive
  • We are Team Shaped  
  • We Keep it Simple  
  • We Evolve or Die

Alongside using these values to help us on our journey, it was clear that the “old” ways of working weren’t going to get us there, and so the MoreNiche “Team of Teams” concept grew from Andy’s concept of a highly autonomous, flat team structure that burns the ships of traditional hierarchies and command-control management. 

Whilst teams at MoreNiche used to be aligned around functions, they’re now aligned towards value streams and goals, such as particular brands or projects. This reduces dependencies outside the teams, meaning team members can decide and act more autonomously, without having to go outside the team, and this improves flow, delivery and quality. Team members can join and leave teams when and if they can add value to the team. 

Cognitive Load

Teams are limited to seven members, with exceptions occasionally permitted if necessary, and people may be on a maximum of three teams at any one time. This way, team members do not over-commit themselves and increase their cognitive load or workload to a point where they feel their performance would be affected. 

Each team has a leader, and they understand how much time and effort is committed by everyone and thus can plan accordingly. Roles are defined within a team to ensure that the team possesses the skills required to execute 99% of the work required, and only occasionally will need to go outside the team for assistance. We’re very aware that team members, including team leaders, cannot contribute effectively if the cognitive load is too great, so the remit of team roles is sized appropriately.

Great Product Ownership is essential to delivering great value to customers, and to our business, so we also put a lot of effort into measuring business value and prioritising work based upon knowing what’s truly important. This is delivered by quarterly planning sessions across teams where the priorities are established, and any constraints, dependencies or risks are identified. Every objective possesses a “confidence” score as well as business value, and this confidence score is updated and communicated regularly, meaning that problems can be identified and resolved quickly, and team members feel safe in highlighting a concern that may impact delivery.

Cross-functional, stream-aligned teams

MoreNiche value-stream aligned teams are fully cross functional – people from almost every function are represented, so that decisions can be made quickly and actions can be taken inside the team without often having to pull in outside expertise or dependencies. Where certain technological dependencies exist, the “Enabling” team type in the Team Topologies model is represented in MoreNiche by teams such as SRE (Site Reliability Engineering), who’s members are also members of value-stream teams but in addition possess their own backlog of work focussed on reliability, monitoring, pipelines and cost control. This SRE team also takes on some of the characteristics of the Platform Team type, largely because the size and shape of the organisation doesn’t warrant a dedicated platform team.

As with any organisation, there are areas where multiple people across multiple teams share a common interest, skillset, or expertise. At MoreNiche, we call these groups Tribes, which facilitate innovation and knowledge sharing across the various stream-aligned teams.

Being “Radically Inclusive” is one of MoreNiche’s core values, and not only are MoreNiche teams truly cross-functional, but a great deal of our team members are remote, so the teams value effective and high-cadence communication. Some teams have daily stand ups, some asynchronous stand ups via slack, and some rely on weekly video calls. Whatever the method, good communication is essential.

Some teams work in sprint-like periods of focussed time, some with a continuous kanban style of work, and some simply use basic to-do lists. It really depends on what the team needs – one of our values is “Keep It Simple”, so we don’t add complication where it’s not required. 

Experimentation

 

Another one of MoreNiche’s values is “Evolve or Die”, which means everything we do is an experiment. So everything from the planning process, the tools we use, the marketing campaigns or the technology we build is all subject to review and retrospective. If we do something and don’t check in to see if it’s working, how do we know that we’re spending time and money on the right things? Of course, it’s also necessary to allow processes to mature, and people to learn, improve, and build expertise, so some of those experiments may be months long while some may be just hours long. In that vein, our entire operating model is subject to review, improvement and change, so by the time you read this, it’ll certainly be out of date.

 

We’re crucially aware of team dynamic models like Tuckman’s forming-storming-norming-performing, and of course we’re always striving towards performing. However, getting there takes time, practice and patience, so when people join a team, we ask that they commit to a minimum period. In the same vein, we want people to stay at MoreNiche for the long term, so providing pathways for career progression and recognition are important. Conversely, if someone leaves, we’re glad to have been part of their journey, and we offer a return ticket back, should their career path cross our way again.

Psychological Safety

 

We know that psychological safety is critical for building high performing teams, so we’re adopting practices and skilling up team members and leaders to understand what roles they can play in increasing psychological safety in the teams that they’re in, or indeed in teams they’re not in. We want people to not only perform, but enjoy their work too. High performing teams aren’t happy because they’re high performing, they’re high performing because they’re happy.

We’re learning so much from this process, and more importantly, we’re having a lot of fun whilst doing it! If you’d like to find out more, get in touch.

 

 

Psychological Safety and High Performing Teams – Links and Resources

Safety isn’t just necessary in order to prevent disasters such as Chernobyl or Amagasaki, it’s also crucial to building and maintaining high performance teams and organisations.

Building high performing software requires high performing teams, in which team members possess psychological safety, and can express their creativity, talents and skills without self-censoring, self-silencing, or fear of failure. This is called psychological safety, and is the foundation for all high performing teams.

Find out more about psychological safety here, sign up to the newsletter, download the action pack, or even join the community!

In this talk “Missile Destroyers, Supercomputers and Chernobyl“, I introduce the latest research in high performance technology teams, and provides actionable concepts to help you build and elevate your team.

building and maintaining psychological safety for your team

To measure, build and maintain psychological safety in your own teams, download the complete Psychological Safety Action Pack – full of workshops, tools, resources, and posters to help you measure, build, and maintain Psychological Safety in your workplace.

See below for various resources and useful information about psychological safety and high performing teams.

Psychological safety in technology teams – Computing Magazine

Psychological safety in high performing teams google slide deck

The DORA State of DevOps 2019 report

Google’s research on effective teams

Grace Hopper Biography

Psychological Safety and Learning Behavior in Work Teams – Amy Edmondson, Administrative Science Quarterly

The cause of the Chernobyl accident – Ukrainian Nuclear Society

The Tuckman model of team stages

Tim Clark DEI

Take the psychological safety assessment, or provide it to your teams.

Baseline data of psychological safety scores

Resilience Engineering, DevOps and Psychological safety

Digital Lincoln – psychological safety and high performing teams – my 45-minute webinar meetup recording.

The State of DevOps Report 2019 – A Summary

Every year or so since 2013, Puppet have carried out their “State of DevOps” report that attempts to gather, aggregate and analyse progress across the technology industry, backed by data and statistical analysis. In 2019, both Puppet and Google researched and released their own State Of DevOps Reports.

Here is a summary of the findings from both 2019 State of DevOps Reports.

(More detail to come shortly!)

  1. 2019 – Puppet:
    1. Doing DevOps well enables you to do security well.
    2. Integrating security deeply into the software delivery lifecycle makes teams more than twice as confident of their security posture.
    3. Integrating security throughout the software delivery lifecycle leads to positive outcomes.
    4. Security integration is messy, especially in the middle stages of evolution.

     

  2. 2019 – Google:
    1. The industry continues to improve, particularly among the elite performers.
    2. The best strategies for scaling DevOps in organisations focus on structural solutions that build community, including Communities of Practice.
    3. Cloud continues to be a differentiator for elite performers and drives high performance.
    4. To support productivity, organisations can foster a culture of psychological safety and make smart investments in tooling, information search, and reducing technical debt through flexible, extensible, and viewable systems.
    5. Heavyweight change approval processes, such as change approval boards, negatively impact speed and stability. In contrast, having a clearly understood process for changes drives speed and stability, as well as reductions in burnout.

 

 

Anonymous feedback can destroy psychological safety

Feedback sucks. Advice is better.

In most cases, feedback sucks. It really does.

Unless the person delivering the feedback is highly empathetic, has lots of free time, is highly skilled and is in the proper position to provide it, and the person receiving it is in the right frame of mind, open to feedback, confident, mature and in a safe place, it’s probably going to be uncomfortable at best or at worst, devastating.

Delivering feedback is hard. In my experience managing teams over a couple of decades, I’ve seen it done so badly that it verges on abuse (in fact, on occasion it certainly was abuse), and despite my best efforts, I’ve have delivered feedback so badly that the relationship took months to recover. I’ve learned from those experiences, and now I’m better, but certainly not perfect.

But ultimately it is important to give and receive feedback if we want to get better at the things we care about. Given how incredibly hard it is to deliver feedback in person, why would we facilitate anonymous feedback?

A misguided solution.

Anonymous feedback is often presented as a solution to problems including unequal power dynamics, bias, fear, or a lack of candour. In reality, anonymous feedback masks or even exacerbates those problems. Great leadership and management solves, or should solve, those problems.

Anonymity reinforces the idea that it’s not safe to speak up. It’s mistaken for objectivity. It presumes that the people who receive it will interpret it exactly as it was intended.

Feedback must be contextual. It must also be actionable, otherwise why provide it?

Conversations matter.

The reason we deliver feedback in person is because it demands a discussion; for example, imagine someone wishes to give you feedback on the way I behaved in a meeting because you came across as aggressive and intolerant. You’d certainly want to know, but you would also want them to know that an hour before that meeting, you’d received some upsetting family news and were struggling to deal with it. That conversational feedback then provides a channel for an open and frank discussion, and an opportunity to support each other.

If that same feedback was delivered anonymously, not only is your theoretical self having a tough time with family problems, but now (in your head, for that is where we all reside) you’re overly aggressive, intolerant, and failing in your role.

Feedback must be actionable.

Anonymous feedback is incredibly difficult to act upon, and can breed a sense of frustration, fear, and resentment, particularly in small teams and organisations.

All feedback must be a conversation. And in order to have a conversation, you must be able to converse with the other party.

You may work in a high-trust, low-politic environment. Or you may believe that you do, since rarely is this truly the case. If you believe that you do, check your privilege. Are you experienced, senior, well paid, white, cis, male, able-bodied or neurotypical? Chances are, for those that are not in those categories, the degree of trust and safety they feel may be somewhat lower, and the impact of feedback considerably greater.

Unconscious bias

There are numerous biases in effect when it comes to feedback and indeed all interpersonal relationships, particularly in the workplace. For example, women are often perceived as more aggressive than men when demonstrating the same behaviour, due to an unconscious bias that women should be more feminine.

Anonymous feedback, rather than removing that bias, enables it, and feeds it, because a woman receiving anonymous feedback that she should “be less aggressive” is forced to accept it as objective, when it’s actually less likely to be the case.

Bias affects everyone. A man may receive feedback suggesting he should be less softly spoken in meetings, an introvert may be told they should speak up more, or (and this happens a lot) a young woman may be told to smile more.

Motivations

Consider the motivations for someone providing anonymous feedback. One reason might be that they genuinely want you to be better, and they already think you’re great, so they’re giving you a chance to excel even more. That’s the only good reason for feedback. All others, including power-plays, envy, bias, inexperience, or simple misunderstanding of the situation, are terrible reasons, and will only have a negative impact on the team.

The point is that when providing feedback, even if your intentions are pure, you will not be aware of your unconscious bias, and working through those biases is that is something that only a conversation can facilitate.

Dialogue.

In every single 1-1 you have with a team member, ask what you can do better, what more or less you could be doing, or what, if anything you could change in you interactions with team members. This regular, light-touch, conversational cadence provides a safe space for feedback. And even if in 99% of the sessions, there is no feedback to give, it ensures that when there is some feedback required, it comes easily, and isn’t a difficult process.

Anonymity encourages poor leadership.

Anonymous feedback processes also provide a get-out, an excuse, for poor leadership and avoiding conversations where feedback is requested or proffered. The thinking may be “I no longer need to ask what more I can do or how I can be better, since we have regular anonymous feedback instead.” This is dangerous, and leads to a general degradation of good leadership practices.

For these reasons, I never provide or accept anonymous feedback. I will always, instead, have a conversation.

Culture.

If you’re tempted to use anonymous surveys and feedback, ask yourself why you feel that anonymity is required, and address the underlying issues. A truly great culture doesn’t require anonymity, and an organisation without a great culture is not maximising the potential of the people within it.