Comparing your teams

🚧 Role coming, expected early 2027. This page describes the product intent, not a delivered screen.

Comparing your teams is the main thing the role is designed for: seeing them side by side, and spotting the one falling behind. This page explains what that comparison is meant to show, and the three precautions that decide whether it means anything.

What the comparison is meant to show

The reading is intended to be by team, not by person: where each of your teams stands, which one is moving, which one is falling behind. Drilling down to a single learner is meant to stay possible, but it is not what the role is built for.

Why the existing statistics do not cover it

The figures already exist, but they live in the back office, they address an administrator and they are built for central steering.

What the role is meant to add is the same information inside the app, for someone who personally knows the people concerned. A completion gap between two stores, read centrally, produces a row in a table. Read by you, it produces a call to the store manager, and that call is what changes the outcome.

Compare what is comparable

Three precautions decide the usefulness of the comparison more than the screen itself.

Size. A store of 8 and a store of 60 do not belong on the same line.

Seniority. A team that has just taken on six people is mechanically behind a team stable for two years.

What they received. A gap can come from engagement, or from the fact that one of the two teams never received the content. Check that before calling a manager. A group’s Related tracks card, on its edit screen in the back office, lists the tracks that population receives.

A ranking is not a performance measure

⚠️ A completion rate measures what has been followed, not what is known. A team at 95% may have clicked through everything and retained nothing. A team at 60% may be the one actually applying it on the ground.

Using the comparison to put teams in competition over a figure produces figures. That is the outcome you do not want.

🔧 On the administrator side. A comparison is only worth something if the groups match real teams. Groups cut for distribution, wide and convenient to target, represent no team at all, and the comparison then bears on sets that do not exist. See Preparing for the role.

🔧 The group report does not count like the others. Its Completion rate divides distinct capsules completed by distinct capsules started, so a team that started very little can show a high rate. Read that column against the definitions before concluding anything from a gap. See What does each metric measure?.

Going further

• Preparing for the role: what to ask your administrator for now, so that the comparison means something later.
• Understanding the area manager’s role: what the role is intended to cover, and what it is deliberately not.
• Common problems: distribution: uneven distribution across an area is the first cause of a misread gap.