# Comparing Teams Fairly Without Inventing Leaderboards

> Stop comparing teams by arbitrary scores. Use Plan/Fact/Gap to see where work actually gets stuck — and fix the system, not the people.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-19
- Updated: 2026-10-19
- Source: https://aiadvisoryboard.me/blog/comparing-teams-fairly-without-inventing-leaderboards

When you're trying to understand which teams are truly moving the needle — and which are just busy — it's tempting to slap a leaderboard on top of activity metrics. But that almost always backfires: people optimize for the metric, not the outcome. As a founder who’s worked with dozens of SMBs, I’ve seen how leaderboards create silent resentment, sandboxing, and ultimately, worse data. The real goal isn’t ranking teams — it’s seeing where the gaps between plan and fact are biggest, so you can act.

## TL;DR
- Compare teams using Plan/Fact/Gap, not output scores or activity counts.
- Look for consistent gaps in similar work — not who’s “best.”
- Use the data to remove obstacles, not to rank individuals.

**Definition:** Plan/Fact/Gap — a simple operating taxonomy where Plan is what was intended, Fact is what actually happened, and Gap is the difference between the two, used to surface systemic issues without blame.

**Definition:** Throughput consistency — the degree to which a team delivers what it plans, week over week, regardless of volume. High consistency means predictable execution.

**Definition:** Gap pattern — recurring types of discrepancies (e.g., scope creep, blocked dependencies, unclear requirements) that appear across multiple teams, indicating systemic friction.

How do you compare teams fairly when output varies by role and complexity? Start by normalizing the comparison: look at each team’s Plan vs Fact for comparable work types. A sales team’s “plan” might be 10 outreach sequences; a support team’s might be 15 ticket resolutions. Don’t compare the 10 to the 15 — compare each team’s ability to hit its own plan.

When you see that Team A consistently delivers 90% of its plan while Team B hits only 60%, the question isn’t “Why is Team B lazy?” It’s “What’s systematically preventing Team B from executing?” Maybe their plan includes work that depends on another team that’s always late. Maybe their tasks are poorly scoped. The gap reveals the friction point, not the team’s effort.

## Manager Scan (2-minute digest example)
- Sales: Plan 10 sequences, Fact 8 → Gap: 2 (delayed lead list from marketing)
- Support: Plan 15 tickets, Fact 14 → Gap: 1 (escalation wait time)
- Engineering: Plan 5 story points, Fact 3 → Gap: 2 (unclear acceptance criteria)
- Marketing: Plan 3 campaigns, Fact 3 → Gap: 0
- HR: Plan 4 screenings, Fact 4 → Gap: 0

This isn’t about who’s best — it’s about where the system is leaking. Marketing and HR are executing as planned. The others have repeatable gaps tied to inputs, not effort.

## Tool tip (AiAdvisoryBoard.me):
> The Plan → Fact → Gap framework turns team comparison from a judgment exercise into a diagnostic tool. Instead of asking “Who’s falling behind?” you ask “Where is the work getting stuck?” This shifts the conversation from blame to problem-solving — exactly what owners need to scale visibility without micromanaging. See how the 7-day diagnostic surfaces these gaps automatically across your company.

## Micro-case (what changes after 7–14 days)
A 40-person professional services firm started tracking Plan/Fact/Gap by team each Monday. After two weeks, the owner noticed the design team consistently had a 30% gap due to late feedback from clients. Instead of questioning the designers’ speed, they introduced a client feedback SLA and a Tuesday checkpoint. The gap dropped to 10% in the next cycle. The owner didn’t need to know who was “fastest” — they needed to know where the process broke.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ
**How is this different from tracking velocity or output?**
Velocity and output can be gamed and vary wildly by role. Plan/Fact/Gap focuses on execution reliability — whether a team does what it says it will do — which is a fairer baseline for comparison.

**What if teams have very different types of work?**
Normalize by comparing each team’s ability to meet its own plan, not the absolute volume of work. A team that plans less but delivers consistently is more reliable than one that plans more and misses often.

**Won’t this just create another metric to game?**
Only if you use it to rank or punish. If you use it to uncover systemic blockers — like unclear scope, missing inputs, or dependency delays — it becomes a tool for removing friction, not measuring individuals.

**How often should I review this data?**
Weekly, in a 10-minute owner digest. Look for patterns: Is the same type of gap appearing across teams? Is one team consistently blocked by another? That’s where to act.

**Can I use this to decide who gets resources or recognition?**
Only indirectly — by fixing the systemic issues that hold teams back. Recognition should come from removing obstacles, not from beating a leaderboard.

To see where your teams are truly stuck — and where to focus your energy — run a 7-day diagnostic that maps Plan, Fact, and Gap across your organization. It’s the fastest way to move from guessing to knowing.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.

---

When citing, link to https://aiadvisoryboard.me/blog/comparing-teams-fairly-without-inventing-leaderboards. More articles: https://aiadvisoryboard.me/blog