Work Output: Benchmarks
Objective. Compare a team or process against a benchmark for a period and read the gap only after confirming the benchmark's definition and basis - never treat a benchmark as truth or a commitment.
Benchmarks answers 'how does this team or process compare against a reference point?' It turns an isolated number into a relative one, which is persuasive in a demo and risky in a review - because a benchmark is only as sound as the definitions behind it.
See it in the demo
What this screen answers
Sales uses benchmarks to give a figure meaning - 'this team is below where comparable work usually sits' lands harder than a bare count. CSMs use it to set expectations and spot genuine outliers. The customer question is 'relative to a sensible reference, where do we stand, and is the gap real?'
The task
Scope to the team or process and period, pick the benchmark that matches the work, and read the gap, not just the absolute. Before narrating it, check what the benchmark is: an internal peer group, a historical baseline, or an external reference, and over what definitions. Carry a real gap to root cause or improvements. For a CSM, the task is to establish which benchmark the customer will accept as fair before any gap becomes a talking point.
How to read it
A benchmark is a reference, not a target of record and not an entitlement. The classic misread is comparing a team to a benchmark whose work type, complexity or definition does not match, then treating the gap as fact - an apples-to-oranges gap is noise. Read the gap only after aligning definitions, and present it as 'worth investigating', never as a promise of where the customer should be. A favourable benchmark in the demo is seeded, not a guaranteed outcome.
Honest limits
This screen does not prove the benchmark is appropriate for the customer or that hitting it is achievable or contracted. External or industry references especially must not become implied commitments. Confirm the benchmark's source, definition and relevance with product, and anchor any target to the customer's own agreed baseline rather than a demo benchmark.
Interpretation check
A benchmark is a reference whose definitions must match the work before the gap means anything; never treat a benchmark as truth, a target of record, or an implied commitment to the customer.
Practical task
Compare one team to a matched benchmark for a period, write a one-line finding stating what the benchmark is and whether the gap survives a definition check before you would raise it.
Self-check
A team is 15% below the benchmark. Is that a real performance gap?
Only if the benchmark's work type, complexity and definitions match the team's. An ill-matched benchmark produces a gap that is noise. Align definitions first, then treat the gap as a lead to investigate.
A prospect asks you to commit to the benchmark figure. What do you do?
Do not - a benchmark is a reference, not a commitment or entitlement. Anchor any target to the customer's own agreed baseline and confirm achievability with product.
What three things could a benchmark be, and why does it matter?
Internal peer group, historical baseline, or external reference - each means something different, so you must state which one and its definition before narrating a gap.
Verified vs demo. Screen is live in the demo at https://work-output.demo.timechamp.io/#/benchmarks; exact controls, labels and on-screen figures are SME-validation-pending.