Work Understanding: Benchmarks and quadrants
Objective. Read the benchmarks-and-quadrants view to compare processes or teams fairly, so a reader only compares like with like and never reads a quadrant position as a verdict without aligning work type, complexity and period.
This view answers 'how does this process or team compare to others, and who stands out?' Quadrants make comparison vivid - and that is exactly why the like-for-like discipline matters most here.
See it in the demo
What this screen answers
The customer question is: which processes or teams are outliers worth looking at? A Sales person uses a quadrant to make relative performance tangible. A CSM uses it to pick where to investigate - after checking the comparison is fair.
The task
Scope to the processes or teams and period in question, then read the benchmark or quadrant and note the outliers. The essential move is to check the basis of comparison before reacting - are the compared units doing the same type of work, at similar complexity, over the same period? An outlier is a prompt to investigate, not a conclusion.
How to read it
A quadrant position is only meaningful when like is compared with like. The classic misread is reading a position as a performance verdict when the units differ in work type, complexity, period, tenure or quality. A team in the 'slow' quadrant may carry harder cases. Read the position as 'look here', align the comparison first, then investigate with the detail screens before judging.
Honest limits
The view does not prove an outlier is better or worse, and it does not control for complexity or quality on its own. It is bounded by detection coverage. Confirm the comparison basis with the customer and validate any apparent gap against complexity and quality before drawing a conclusion.
Interpretation check
A quadrant position is a prompt to investigate, not a verdict - compare only after aligning work type, complexity, period, tenure and quality, or the comparison misleads.
In the field
KnackGlobal RCM: a benchmark can make one team look slow until you align case complexity and payer mix - then the gap may vanish or point somewhere specific to investigate.
Practical task
On the benchmark/quadrant view, pick one outlier, write the comparison basis you would verify (work type, complexity, period), and state the one detail screen you would use to confirm whether the gap is real.
Self-check
A team sits in the 'slow' quadrant. Is that a performance problem?
Not on its own. They may carry harder, higher-complexity cases. Align work type, complexity and period first, then investigate the detail before judging.
What must be true before two processes can be compared on this view?
They should be like for like - same work type, similar complexity, same period, comparable tenure and quality - otherwise the comparison misleads.
What is the benchmark view actually for?
Spotting outliers worth investigating, not grading teams. The position tells you where to look, the detail screens tell you why.
Verified vs demo. Screen is live in the demo at /#/benchmark; exact controls, quadrant axes and figures are SME-validation-pending.