Work Understanding: Process health
Objective. Read the process-health view as a composite signal built on discovered, confidence-weighted findings, so a reader uses it to prioritise attention and never presents a health score as a precise, proven grade.
Process health answers 'at a glance, which processes look healthy and which need attention?' It is a prioritisation surface that rolls up the detail - and a roll-up is only as sound as the findings beneath it.
See it in the demo
What this screen answers
The customer question is: across my processes, where should attention go first? A Sales person uses it to frame a portfolio view before drilling into one process. A CSM uses it in a review to triage - to choose the process to work this period and track whether it improves over time.
The task
Scope to the processes and period, then read the health signals and rank attention. The move is to use health as a triage layer: pick the process that most warrants investigation, then go to the detail screens (step time, friction, rework, root cause) to understand why, and to the improvement workspace to run a validated change.
How to read it
A health signal is a composite of discovered, confidence-weighted findings, not a precise proven grade. The classic misread is treating the score as an exact measurement and comparing tiny differences, or acting on the score without opening the findings beneath it. A health signal inherits the confidence and coverage of its inputs. Read it as 'where to look', then validate at the detail before acting.
Honest limits
The view does not prove a process is healthy or unhealthy in an absolute sense, and it depends entirely on the quality and coverage of the findings it rolls up. It does not substitute for validation. Confirm with product how the signal is composed and its coverage, and validate any action through a measured before/after.
Interpretation check
A process-health signal is a composite of confidence-weighted findings, not a precise grade - use it to prioritise where to look, not as a proven score to act on directly.
Practical task
On the process-health view, pick the process that most warrants attention, write why, and name the sequence of detail screens you would open to validate before proposing any action.
Self-check
Two processes differ by a couple of points on the health score. Is one clearly worse?
No. The signal is a confidence-weighted composite, not a precise measurement, so small differences are not meaningful. Use it to triage, then open the findings beneath before concluding.
What is process health best used for?
Prioritising which process to investigate this period and tracking direction over time - a triage layer, not a final verdict.
What does a health signal inherit from the screens beneath it?
Their confidence and coverage. If the underlying detection and findings are low-confidence or partial, the health signal is too.
Verified vs demo. Screen is live in the demo at /#/health; exact controls, health signals and figures are SME-validation-pending.