May 16, 2018

Combatting Observer Bias in Coaching with the Team Coaching Framework (TCF)

As coaches, our opinions and unconscious biases can mislead or misdirect those we are coaching.

In research, psychology, and any other field in which someone is intended to be an impartial observer, there is a phenomenon known as the Observer Expectancy Effect, or Observer Bias. This bias happens when an observer expresses their thoughts and expectations about a situation through tone, word choice, and body language in a way that influences how the people they are observing behave.

The observer expectancy effect can be subtle, but it can also be quite profound. In some research, the observer has been shown to unconsciously change the way a subject performs in a test based on whether the observer was told they were “smart” or “dumb” subjects.

Right about now, you’re probably thinking “Well I wouldn’t do that! I’m a professional!” and there I have bad news for you. We all do it. Because it’s largely unconscious, we can’t help it. The only way that’s been found to consistently address the problem is to not have any expectations, and that is really difficult. Even if we can enter a situation with none, human nature causes us to start forming them very quickly. As coaches, our opinions and unconscious biases can mislead or misdirect those we are coaching. Therefore, it is important that we are aware and careful of this effect.

At agile42, we use a structured approach to change on teams called the Team Coaching Framework (TCF) to limit or negate the impact of any observer bias we might bring to the table.

Structured Coaching through Coaching Cards

Coaching Structure - smaller size

In TCF, we leverage a structure that helps us avoid jumping ahead of ourselves in coaching. This structure starts with observations, then makes hypotheses about why those observations exist, co-created with those we are working with wherever possible. Once we settle on a hypothesis to work with, we set a goal and ways to measure that goal. Finally, we select tools to use to help get to this goal. Following this structure pushes our own opinions as far out in the process as possible in order to reduce the likelihood of influencing the process accidentally.

Micro-Observations

“The ScrumMaster is the center of conversation for the Daily Scrum.”Magnifying Glass - smaller size

Does this sound like an observation to you? It isn’t. It’s actually an inference about a pattern of observations. If that sounds pedantic, that’s ok – in many cases like this, it is a fair inference about a real pattern. But when we come to our hypotheses, this nuanced difference might really matter.

When we look at the actual events that occur, we may see that every person only speaks to the ScrumMaster. Or, we might see that people primarily speak to the ScrumMaster but they also update the board and occasionally speak to each other. Both of these patterns could be expressed as the ScrumMaster being the center of the conversation, but in the first, we may hypothesize that there is a structural component leading to the behavior, while in the second it is clear that nothing is blocking the team from speaking to each other – perhaps there is a social pressure or a habit leading to this behavior.

Reflecting back on these “micro-observations” can free us from anchors we’ve formed in our perspective.

Pairing or Coaching Groups

Having an extra set of eyes will almost certainly result in a different set of observations. Comparing these after-the-fact can help both coaches in removing their bias from the coaching. When doing this, the coaches can either decide to both watch everything or they can choose to have one coach focus on a very specific thing while the other takes a broad view in his or her observations. This second approach is particularly helpful when you are coaching a team through a particular challenge or new skill.

Multiple Hypotheses

One of the most common problems when formulating hypotheses is that we select the hypothesis that most closely matches our preconceptions or past experiences and then look for information that shows this hypothesis to be true.Exclamation Marks

In order to avoid this, we try to brainstorm multiple hypotheses in each coaching card. We will usually pursue only one at a time, but taking the time to come up with multiple hypotheses helps break us out of our own assumptions.

Coaching Tip: If you do this as a group, other coaches may come up with hypotheses you would never have thought of.

Invalidate Your Hypothesis

"It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail." - Abraham MaslowInvalidate Hypothesis

We are bombarded with a lot of information and our brain subconsciously filters out everything that we don’t think is relevant. When we try to validate a hypothesis, we can unconsciously filter out information that doesn’t support the hypothesis. This is called confirmation bias. One way to avoid this is to specifically look for information that disproves your hypothesis. Because you’re specifically looking for it, you are less likely to subconsciously filter it out.


Note: I recommend looking at the works of Robert Rosenthal, which primarily studied the effects of biases in childhood education.

If you want to acquire more techniques in making effective and valuable observations when coaching, join us on May 6th in Vancouver for the first ORGANIC agility conference. Walk away with practices you can apply immediately to improve team performance. 

ORGANIC agility conference - Team Coaching Workshop

Image of daniellynn

Daniel Lynn

Agile Coach
blog comments powered by Disqus
Image of daniellynn

Daniel Lynn

Agile Coach

Latest Posts

Scrumtisch September 2019

The Berlin Scrum User Group meets on September 30th at agile42, Gruenberger Str. 54, 10245 Berlin.

Image of aballer

Alexandra Baller

agile42 Team Assistant

The Scrum Master as an organizational multi-function pocket knife

The Scrum Master is a jack of all trades with a magic problem-solving knife in his back pocket or a master of Scrum?


Image of elrich.faul

Elrich Faul

I’m passionate about helping the current and next generations to develop the skills they need to be successful in a rapidly changing world. I believe that by leveraging my expertise in engineering, psychology and management I can empower individuals and teams to reach their maximum potential. I’m inspired when given the opportunity to coach teams as well as individuals toward growth and happiness.

Campaigning for Dave

agile42 coach Dave Sharrock is running for Scrum Alliance Member Elected Director and we support his candidacy!

Image of abragad

Alessio Bragadini

Web community manager of agile42, trying to post relevant, informational, fun bits of content on the blog and social networks

Talking agility at Agile Islands conference

Pascal Papathemelis and the agile42 team will be present at the Agile Islands 2019 conference in the Åland Islands

Image of pascal

Pascal Papathemelis

Pascal has worked as an agile project manager/scrum master/facilitator of various developments in size and type for almost two decades. His focus is on people and practical approaches in order to deliver value. Currently Pascal is working at agile42 as an agile coach on a journey to help organisations and individuals grow, improve and become more efficient in a sustainable way.

Coaching at the Nordic Business Forum in Helsinki

Giuseppe De Simone will represent the Scrum Alliance at Nordic Business Forum in Helsinki, October 9-10 providing agile conversations to attendees

Image of giuseppe.desimone

Giuseppe De Simone

Giuseppe De Simone is a Certified Scrum Trainer (CST), Certified Enterprise Coach (CEC) and Certified Team Coach (CTC), passionate about helping individuals, teams and organizations become more productive by embracing Agile values, principles and practices. He is one of very few to be accredited from the Scrum Alliance as an educator of the Certified Agile Leadership and Path to CSP programs.