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.

 

 

Why the UK Porn Block is an Awful Idea

From 15 July 2019, the UK’s age verification system for online pornography will become mandatory. Here’s why it’s a terrible idea.

  1. It actually doesn’t block much porn at all. It only applies to commercial porn, which you need a credit card to access anyway, and children generally don’t have credit cards. It doesn’t apply to porn on social media, free sites, or P2P sharing, which is much easier to access.
  2. It will likely do more harm than good. It may provide many parents with a false sense of security that their children can no longer access porn online, resulting in a lower emphasis being placed on parents properly managing their childrens’ internet access. Parental controls on home wifi, home computers, and mobile devices are widely available and relatively easy to use.
  3. It plays into the hands of the big commercial porn providers. The main age verification system (AgeID) is owned by the same company that runs the most popular and lucrative porn websites in the world. The largest porn company in the world is being tasked with controlling access to porn. Already, some smaller businesses in the realms of ethical porn and feminist porn have shut down because implementation of this system is too expensive for them. If we’re going to have porn on the internet (and who are we kidding, there will always be porn on the internet), do we want it controlled by one big US firm?
  4. It has serious privacy implications. The age verification systems will contain the personal information and erotica browsing history for every adult who’s ever wished to access online porn from July onwards. If (or more realistically, when) this database is breached, it will be a treasure trove for identity thieves and blackmailers.
  5. It just won’t work. Technologically, it’s easy to bypass the system. Because it only applies to the UK, a simple VPN to break out to a different country will easily and cheaply circumvent most controls. At the same time, as has been seen in China, India and other authoritarian regions, consumers simply switch to other channels, such as torrenting, social media, newsgroups (yes, they’re still a thing), and the dark web.
  6. It’s based on flawed evidence. Whilst there’s anecdotal evidence that children “stumble across” online porn, there’s very little evidence that they access commercial porn sites, particularly when parents make some effort to manage internet access. The main study cited as the catalyst for the Act “found” that “almost a tenth of all 12- to 13-year-olds thought they were “addicted” to pornography”, and was carried out by OnePoll, the same people who generate such hard-hitting research as “German men are the world’s worst lovers” and “Fifty percent of British adults think Mount Everest is in the UK“. There is evidence that children access porn online, and some evidence that it’s harmful, and some that it isn’t as harmful as you’d think. Whichever way it’s cut, this age-verification approach is not evidence-based.
  7. It’s censorship and control. It provides a mechanism for the government to monitor online activity and decide what content is acceptable or unacceptable for the population to access, and change this definition as they see fit. The terms in the act even include the ability to block “material other than the offending material”. We may trust today’s government (though do you, really?), but we’d be foolish to implicitly trust future governments not to extend the controls to other content. As the award-winning English lawyer Myles Jackman put it, “Pornography is the canary in the coal mine of free speech: it is the first freedom to die. If this assault on liberty is allowed to go unchallenged, other freedoms will fall as a consequence.”

Technologically, this approach is fundamentally flawed, is unlikely to work at all, and creates some worrying implications for digital identity and privacy in the hands of large US corporations.

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.