Are you “flying blind” on understanding how your team is performing?

Struggling to find time to reflect on how the team is working together?

Here red10 ‘s Sarah Barber describes a team tool that provides a valuable temperature check on the reality team members are experiencing.

I love how concise it is – I don’t have to digest a multi-page report.

What I like is that the report is actionable. It is great that we have seen progress since last time we did this

What do the team need to tell each other?

A senior leader approached us recently to say she felt she was “flying blind” in understanding what her team were thinking about themselves as a team.

The members of that team told us the same thing, in different words.

It is not always easy for team members to provide feedback to the leader or each other about what is working well and what is not. We recommended this tool to her as it provides a positive approach for team members to describe the reality they are experiencing and then turn it into positive action.

How do we gather the feedback?

Our ideal is that we begin by conducting a 30-min MS Teams call with every member of the team. We ask two open questions to get qualitative feedback:-

  1. What is working well in the team that we want to keep, protect and nurture?
  2. What do we need to do differently to make the team the best it can be?

We then ask for quantitative feedback in the form of a 1-10 score on the nine dimensions of team effectiveness and an overall score.

We say “our ideal is 30-min call” because red10 also offers a lower-cost Feedback-on-a-Page service using an anonymised internet-based feedback form and using the latest AI techniques to craft the report. The quality by internet form is good, the quality by 30-min phone call is great.

What happens after the feedback call?

The transcript of the interview is shared with the team member only to allow them to make any corrections or additions. It is not shared with anyone else.

What does the Feedback-on-a-Page™ report look like?

Once we have agreed transcripts from everyone, we start to compile a report. For the quantitative feedback, we work out an average and a range for each score and present these in traffic light format on the first page of the report.

Average scores of 7.0 or above are presented as GREEN. In our experience, these are teams that are working with speed and good-decisions and are getting great outcomes for their business. The research shows that these teams are getting:

  • Up to 30% more performance than other teams
  • Up to 25% extra output from the workforce they lead

Average scores between 5.0 and 6.9 are presented as AMBER traffic light. Our experience is that these teams have more potential. Teams often identify actions they could take to lift performance into the green. And they like to have the benchmark to see whether they have improved next time they use the tool.

Average scores of less than 4.9 are presented as RED. These teams highlight areas that they urgently need to address.

What does a sample text page look like?

We look across the qualitative feedback and identify themes that three or more people have mentioned. We give the theme a name and add a number in brackets to show the number of people who have mentioned this theme.

We describe the theme using people’s own words yet mixing up sentences from different people so that it is not obvious who has said what.

Feedback that only one or two people have given is not lost but is recorded briefly in a category called “other”. The result is a concise summary of “working well” and “do differently” on a single side of paper.

We use people’s actual words with just four alterations in which red10 uniquely help teams create positive traction:

  1. During interview:
    replacing judgements with facts/observed behaviour
  2. During interview:
    Replacing “What you didn’t want” with a future-based requests
  3. Post interview so the feedback gets traction:
    Reframing statements into questions/request
  4. Post interview:
    Replacing SMOG (should, must, ought to, got to) with could, will, can…

Why do we anonymise the feedback?

Feedback is anonymised because this makes it easier for people to be frank. More importantly, it reduces “noise” (or random variation) in expert judgements. A collection of anonymised individual judgements reduces noise because it avoids the bias introduced by cascade effects (everyone getting behind one individual) and group polarisation.

What comes next?

We share the report first with the team leader. They help us to remove any comments which might clearly identify an individual, and any comments likely to cause hurt to someone on the team. This is an important step as team feedback is unlikely to land if it causes hurt or offence. There are better ways to give constructive feedback to individuals.

We then share the report with the whole team – usually as a pre-read for a meeting. In this way everyone gains an understanding of current reality.

How do the teams respond to the feedback?

At the meeting, we start by celebrating the positive – finding the themes that really resonate with people and taking time to be rightly proud of the things that are working well.

Teams often then prioritise 3 or 4 topics that they would like to address in breakout groups that playback to refine and agree actions.