Work Output: Overview
Objective. Open the Work Output overview, set scope and period, and read the headline figures as a summary that points you to the next screen - not as a verdict on performance.
The overview answers 'at a glance, is completed work keeping pace with what we are paying for, and where should I look next?' It is the landing screen Sales uses to frame the time-to-outcome story and CSMs use to spot where to drill.
See it in the demo
What this screen answers
A Sales or CSM person opens the overview to get the one-screen answer to 'are busy teams actually producing the expected work, and where is the exception?' It is the top of the time-to-outcome chain: hours in, work completed, attainment against standard, and the quality and cost of that output, summarised. Use it to orient before you drill, never to close an argument.
The task
Set the scope (organisation, team or process) and the period you want to talk about, so every tile shares one denominator. Read the headline tiles as a set - completed work, attainment, quality and cost together - rather than fixating on one. Then pick the single exception worth drilling (a team below attainment, a rising cost, a quality dip) and move to the matching detail screen. Treat the overview as the question-finder, not the answer.
How to read it
Every tile is scoped to the filter you set; change the period and the story changes, so state the scope out loud. The classic misread is treating a green headline as proof of delivery or a red one as proof of failure - a single KPI is a summary of a mix, not a judgement. Output is not activity: a healthy utilisation figure elsewhere does not belong on this screen, and completed-work volume here is not value until you have seen quality and cost. Read the tiles together or you will tell a one-sided story.
Honest limits
The overview proves nothing on its own - it aggregates seeded demo data across whatever scope is set. It does not establish that completed work is fully counted, that the standard behind attainment is agreed, or that the cost tile reflects a customer's real cost model. Confirm completion definitions, source coverage and the cost basis with product and the customer's own baseline before quoting any number from this screen.
Interpretation check
A headline tile is a scoped summary of a mix, not a performance verdict; read completed work, attainment, quality and cost together, and never present the overview figure as the proof - it only tells you which detail screen to open.
In the field
For KnackGlobal, the overview is where you frame output-per-FTE and cost-per-clean-claim as the headline, then drill - activity-only incumbents cannot even assemble this one screen.
Practical task
Set one team and one period, read completed work, attainment, quality and cost as a set, and write a one-line finding that names the single exception you would drill next (and which screen you would open).
Self-check
A prospect points at a green 'attainment' tile and says 'so we are fine'. What do you say?
It is a scoped summary, not proof. Attainment is only meaningful once the standard is agreed and credible, and it says nothing about quality or cost - we need to read those tiles together and then drill the exception.
Why state the scope and period before reading any tile?
Every tile is computed over the filter you set. The same team looks different across periods and scopes, so an unstated denominator is the fastest way to a misleading claim.
What is the overview good for in a demo?
Framing the time-to-outcome story and finding the one exception worth drilling - it is the question-finder, not the evidence.
Verified vs demo. Screen is live in the demo at https://work-output.demo.timechamp.io/#/overview; exact controls, labels and on-screen figures are SME-validation-pending.