Work Understanding: Overview
Objective. Open the Work Understanding home and read it as a map of where process time goes, then pick the one finding worth drilling into - without treating any headline as a proven saving.
The overview answers 'why does this work take as long as it does, and where should we look first?' It is the entry point that orients a Sales or CSM person before they drill into discovery, step time, friction or rework.
See it in the demo
What this screen answers
The customer question is: of all the time inside this process, where is it going and which part is worth investigating first? A Sales person opens the overview to frame the demo story - this is observed flow, not a whiteboard. A CSM opens it at the start of a review to decide where the week's attention goes, before diving into any single screen.
The task
Scope the view to the process, team and period the customer actually cares about, then let the overview orient you. Read it top-down: the discovered process shape, where time concentrates, and the findings the app is surfacing. Do not act here - use it to choose the one screen (step time, waiting, friction, rework) to drill into next. The overview is a starting point, not a conclusion.
How to read it
Everything on this screen is discovered and inferred from captured signal, not a definitive process map. Headline numbers are opportunity and observed contribution, not verified savings. The classic misread is treating an overview tile as money in the bank: a surfaced finding is a hypothesis to validate, and overlapping findings cannot be summed. Read it as 'here is where to look', then go validate at the detail screen.
Honest limits
The overview does not prove causality, does not confirm coverage is complete, and does not establish that the discovered process matches the customer's intended one. Confirm detection method, confidence and coverage with product, and confirm the process shape with the customer before quoting any figure externally.
Interpretation check
An overview headline is a place to look, not a proven saving - it is discovered from captured signal and must be validated at the detail screens before it becomes a customer claim.
In the field
KnackGlobal RCM: the overview is where you decide to chase the waiting that drives days-in-AR rather than the active data-entry step that catches the eye but barely moves the cycle.
Practical task
Open the overview for one process, write a one-line statement of where the time appears to concentrate, and name the single detail screen you would drill into next and why - without quoting any figure as a saving.
Self-check
A prospect points at an overview tile and asks 'so that is the number we save?' What do you say?
No. The tile is an observed opportunity discovered from signal, not a verified saving. We validate it at the detail screen and measure a real before/after before anyone quotes a number.
What is the overview actually for in a CSM review?
To orient and choose where to look first - it tells you which screen to drill into this week, not what to conclude.
Why can't you add up the findings shown on the overview?
They may overlap on the same time, and each is an observed contribution with a confidence, not an independent proven cause. Summing them double-counts.
Verified vs demo. Screen is live in the demo at /#/home; exact controls, tiles and figures are SME-validation-pending.