Running a Team Radar in Retrium

What is a Team Radar Retrospective in Retrium?

Team radars are a set of options in Retrium for gathering data in a retrospective. They’re used to gauge how the team is doing in areas like development practices, culture and values, Agile practices, or other topics. Radars can be especially useful because they can help get team members on the same page, illuminate agreement or disagreement, and allow for reflection at both the individual and team level.

A radar functions like a short survey to quickly understand where things are going well (or not) and where perspectives may differ. Because you can easily see individual responses and aggregated results (like the average, standard deviation, etc), it’s an efficient way to focus the discussion on the most important topics.

Radars are quite different than a column-based retrospective because your team members don’t generate any text-based notes in Retrium. Instead, each team member provides a response on a scale of 1-5 and the results are automatically calculated and displayed on a radar chart.

How do I run a Team Radar in Retrium?

In Retrium, the Team Radar includes:

  • Defining the radar, where you can add or remove spokes with labels,
  • Collecting responses, team members share a numeric response to each spoke of the radar,
  • Analyzing the results, where the team can review the individual responses and aggregated metrics plotted on a radar chart, and
  • Determining next steps, where the team decides where to focus the discussion and next steps based on the team’s interpretation of the results

Before collecting the responses, you just need to select your Team Radar technique from the menu.

Before the retro starts, you'll see what items are included for the team's feedback.

Just click the button to start the retrospective to begin.

Define the Retro

During this phase, the facilitator can add or remove spokes from the radar template if the team would like to do so. Additionally, the team should be sure that everyone has a shared understanding of the meaning of each label on a spoke so everyone is rating the same ideas.

Collecting Responses

Unlike our column-based retrospective techniques, team members provide ratings on a set of pre-determined topics, attributes, issues, or categories during the data gathering step of the retrospective. The category is listed as a label on each spoke.

Everyone then anonymously enters their response on a scale of 1-5. This is done all at the same time, so it’s really fast! The line colors are randomly generated each time you use a Team Radar.

The lines will connect as choices are made on each spoke.

You can see who has responded using the left panel, which shows information about presence.

Once everyone has made their selections, the facilitator can advance the retrospective to the analysis phase using the menu in the bottom right of the page.

Exploring the Results

We do all the work to plot the individual responses and automatically calculate metrics like the average, standard deviation, and much more. This saves teams a ton of time, especially with larger groups!

By default the individual responses are displayed.

Use the box label "Explore the Results" to look at different plots. 

The facilitator can advance the selection to show a pre-selected combinations of statistics to help you understand individual scores, agreement and disagreement, and divergence.

You can also turn on and off the plots using the legend.

Determine What’s Next

From there, your team may want to discuss the results with questions like:

  • What interesting points or patterns are visible on the radar?
  • What is surprising or unexpected?
  • What spokes warrant further feedback, discussion, or clarity?
  • What spokes do we want to highlight or celebrate?
  • What spokes warrant improvement, action items, or other next steps?
  • What information should be shared with leadership or other teams?
  • What trends have we seen over time in our radars?

Because the analysis phase is the last step of this retro format, you may want to leave the board open until the team is done discussing what they see and deciding what to do. Once you advance the retrospective, it will end the Team Radar and it will be saved to your retrospective history.

After a Team Radar, you might consider using a column-based technique to dig into a topic further. You can run one of our standard techniques like mad, sad, glad, or stop, start continue on the specific spoke. Another option is to do a custom retrospective with one or more spokes as the column headings. 

When Would I Use a Radar?

Ultimately, the decision of when to use a radar is best determined by the team, Agile Coach, or Scrum Master. While individual responses are anonymous and choices are made at the same time, the analysis does show and compare the individual choices. This means that having an established team with trust and psychological safety is best for this technique.

You can consider using a radar when:

  • You’re running low on time, since it’s an efficient way to narrow down topics to just one or two of the most important
  • You want to talk about broader topics, such as work happiness
  • You want numeric (as opposed to text) output
  • You want to add variety into your retrospective meetings when it seems like the team is getting bored

**A few helpful notes are to be sure everyone understands each label on the radar before providing their responses, and because the discussion section is more open-ended, ensuring that everyone has equal time to share their interpretations and participate in generating next steps.**

Current Team Radar Options

We currently offer 6 different radar options.

Development Process

  • Quality
  • Testing
  • Communication
  • Ceremonies
  • Throughput
  • Customer Value

Development Practices

  • Testing Practices
  • Shared Coding Standards
  • Managing Technical Debt
  • Clarity of Scope
  • Ability to Focus
  • Deployment Process

Scrum Ceremonies

  • Sprint Planning
  • Daily Standup
  • Sprint Review
  • Backlog Refinement
  • Retrospective

Scrum Values

  • Courage
  • Focus
  • Commitment
  • Respect
  • Openness

Work Happiness

  • Clarity
  • Autonomy
  • Mastery
  • Meaning
  • Impact
  • Engagement


  • Tools and technology
  • Collaboration
  • Processes and practices
  • Scope and schedule
  • Culture and values
  • Technical skills and expertise