Faster vs. slower: coaching with peer data, not shaming

September 19, 2026 · 6 min read

When two people do the same job and one gets far more done, the gap is worth understanding. Used well, that comparison is the fastest route to helping the slower performer. Used badly, it's a shaming exercise that drives good people out.

Assume tooling and workload first

Before you conclude "less effort," check the boring explanations, which are usually the real ones: a slower laptop, missing software access, more interruptions, a harder mix of accounts, or a workflow with more waiting. Opus shows context-switching and dead-space alongside output precisely so you can separate friction from effort.

Make it about the work

• Compare within the same role, not across different jobs.
• Pair a high performer with someone struggling — often the fix is a technique the fast person takes for granted.
• Share individuals' data with them privately; never rank people publicly.
• Look for systemic patterns: if half the team is slow on the same task, the process is the problem, not the people.

The measure of good peer analytics isn't that it finds the slowest person — it's that, a month later, the gap is smaller because you removed what was in their way.

Keep reading