Public vs. private leaderboards: when to use each

Every sales manager eventually gets asked: should we put a public leaderboard on the TV? Ranking every rep by closed deals, pipeline added, or whatever the primary metric is. Top rep at the top, bottom rep at the bottom, updated in real time.

The answer is: sometimes. Public leaderboards are a powerful tool that does specific things well and specific things catastrophically. Understanding the difference before you install one saves you from a specific kind of cultural damage.

When public leaderboards work

Conditions for a public leaderboard to improve team performance:

Reps compete in similar weight classes. All inbound AEs against each other: fair. All outbound SDRs against each other: fair. Mixing roles: unfair, and the leaderboard misranks.
The measured metric is directly controllable. “Deals closed” is controllable. “Deals inherited from last quarter’s rep” is not. Make sure what you’re ranking is what the ranked reps can actually affect.
Territory / lead distribution is roughly equal. If one AE gets the Enterprise-Fortune-500 accounts and another gets the SMB pool, their revenue numbers aren’t comparable. Either segment them, or rank on a metric that normalizes out the territory (win rate, demos-to-close ratio).
The culture rewards competition. Some team cultures genuinely enjoy competition. Others find it socially toxic. Read the room before installing.
Bottom performers have a path to move up. If the rep at the bottom has been working on weak leads for 6 months with no path to a better territory, the public leaderboard isn’t motivation; it’s cruelty.

When all five conditions are met, a public leaderboard is net-positive. When any one fails, it causes specific damage.

When public leaderboards destroy culture

Failure modes:

Top-performer hoarding. Public leaderboards can incentivize top reps to hoard inbound leads, refuse to collaborate, and sandbag pipeline. If only “first to close” ranks high, collaboration disappears.

Bottom-performer shaming. The rep at the bottom of the leaderboard experiences constant public diminishment. Even if they’re a competent performer getting unlucky territory, the leaderboard doesn’t show context. They disengage or leave.

Gaming the metric. Reps optimize for the visible metric even when it doesn’t serve the business. Leaderboard ranks deals closed? Small quick-close deals pile up while long strategic deals get deprioritized.

Manager weaponization. When the leaderboard exists, bad managers use it as a weapon instead of doing the work of coaching. “Why are you at the bottom?” instead of “let’s work together on your sales process”.

Psychological safety erosion. Reps stop sharing their challenges because they don’t want to look weak in the public ranking. Early-warning signs that would have been surfaced internally now stay hidden.

When private leaderboards are the right call

A “private” leaderboard is one the rep sees for themselves — their own rank — but not the full team’s ranking. They know where they stand; they don’t know where each of their peers stands.

Good use cases:

Teams that mix roles or territory types. Where absolute ranks don’t fairly compare reps.
Early teams still figuring out who fits. Where public ranks could force premature turnover.
Cultures that value collaboration over competition. Where public ranking would damage teamwork.
Teams with deep skill gaps. Where a public bottom-rank would be a constant demotivator for the developing rep.

A private leaderboard still gives each rep their self-awareness (“am I above or below median?”) without the social dynamics of a public display.

The hybrid pattern

The pattern I’ve seen work best: public leaderboards during contest windows; private (or no) leaderboards during baseline work.

Example:

Normal operations: team totals and goal progress, no per-rep ranking.
Monthly SPIF or quarterly contest: introduce a public per-rep ranking only for the contest window.
After the contest: revert to team totals.

This gives you the motivational intensity of public ranking for limited windows (when the team is mentally prepared for it) without the sustained cultural pressure of permanent ranking.

The counterintuitive case for fully public

One more variant worth considering: the fully-public-forever leaderboard, including compensation data.

Some companies (Basecamp has written about this) publish every rep’s compensation alongside the leaderboard. The argument: if you can’t be transparent about pay and performance, you haven’t built the team you claim.

This works for specific company cultures. It does not work for most. If you’re considering it, read Jason Fried and David Heinemeier Hansson’s writing on the topic before deciding.

How to install a leaderboard well

If you’ve decided public is the right call:

Announce it before installing. Don’t surprise the team.
Show the metric’s definition. “This is demos-held this week. Demos with any valid status excluding cancellations.”
Explain what will and won’t happen based on the ranking. Specifically: “This will be used to celebrate wins and coach improvement. It will not be used in performance reviews.”
Commit to not weaponizing it. Managers shouldn’t point at the leaderboard during 1:1s. The leaderboard is motivation; the 1:1 is coaching.
Pick a metric that’s close to revenue, not revenue itself. Demos booked, activities logged, meetings held. Revenue is too lumpy for day-to-day ranking.
Reset the leaderboard frequently. Weekly or monthly, not yearly. Fresh starts give lagging reps a reason to engage.

The question to ask before installing

“If we put this leaderboard up, would my team be proud to share it publicly, or embarrassed?”

If proud: install it.

If embarrassed: the leaderboard isn’t the problem. The team dynamics are. Fix those first.

Ready to install something simpler? Start a PingBell trial — start with a team total on a TV, evaluate before adding the per-rep split.