Work Understanding: Workday and team mix
Objective. Read the workday and team-mix view to see how the day is composed across work types and people, so a reader can describe where effort sits without mistaking a time split for a productivity verdict.
This view answers 'what does the working day actually consist of, and how is the mix of work spread across the team?' It frames where process effort concentrates before the detail screens explain why.
See it in the demo
What this screen answers
The customer question is: how is the day and the team's effort distributed across the different kinds of work in this process? A Sales person uses it to show that effort composition is observed, not assumed. A CSM uses it to spot where the mix looks heavy or uneven and decide which process area to investigate.
The task
Scope to the team and period, then read the composition of the workday across work types and across people. Look for where effort concentrates and where the mix is uneven. Use it to form a question for the detail screens - not to draw a conclusion about who is productive.
How to read it
This is a composition of observed effort, discovered from captured signal. The classic misread is reading a time split as a performance ranking - more time on a work type is not proof of waste, and a person carrying more of one type may simply be assigned it. Read it as 'where the effort sits', then investigate the why at step time, friction or root cause before judging.
Honest limits
The mix does not prove effort is well or poorly spent, and it is bounded by capture coverage. It does not establish the right or standard mix for this process. Confirm with the customer what the intended mix should be and with product how completely the day is captured.
Interpretation check
A time split across work types is observed composition, not a productivity ranking - more time somewhere is a question to investigate, not proven waste.
Practical task
On the workday/team-mix view for one team, write a one-line observation about where effort concentrates and frame it as a question for a detail screen - explicitly avoiding a productivity judgement.
Self-check
One person shows more time on a work type than peers. Is that a finding?
Not on its own. It may reflect their assignment or case mix. It is a question to take to the detail screens, not a verdict on their productivity.
What is the workday-and-team-mix view good for?
Seeing where observed effort concentrates across work types and people, to choose where to investigate - not to conclude who performs well.
What bounds this view's accuracy?
Capture coverage - the mix only reflects observed effort, so confirm how completely the day is captured before reading it as the whole picture.
Verified vs demo. Screen is live in the demo at /#/workday; exact controls, splits and figures are SME-validation-pending.