Time and Activity: Focus and intensity
Objective. Read focus and activity-intensity signals for a team and explain why intensity is not a measure of value or output.
This screen shows focus and activity-intensity signals - how concentrated or interrupted active time was. It answers 'how was the work pattern, not just how much?' and is easily over-read as a performance score.
See it in the demo
What this screen answers
Beyond how many hours were active, a manager sometimes wants the texture: was active time concentrated into focused stretches or fragmented by frequent switching? This screen surfaces focus and intensity signals that describe the shape of activity within available hours.
The task
Scope to a team and period and read focus/intensity as a pattern signal alongside utilisation, not as a standalone grade. The task is to notice shapes worth a conversation - heavy fragmentation that might signal interruption or tooling friction - and to treat them as hypotheses about working conditions, not rankings of people.
How to read it
High intensity or focus is not high value. Activity can be intense and concentrated while producing little that matters, and genuinely valuable work (deliberation, collaboration, careful review) can read as low-intensity. The misread is turning an intensity signal into a productivity score and ranking people on it. Read it as context for a conversation about how work happens, not a measure of what was produced - output lives in Work Output.
Honest limits
Focus and intensity are derived from activity signals and depend on how they are defined and captured - confirm with product what they measure. They do not capture the difficulty, quality or outcome of work, and they can penalise legitimate working styles. Treat this as a diagnostic for working conditions and friction, never as an individual performance metric on its own.
Interpretation check
Focus and intensity describe the shape of activity, not its value. Intense, concentrated activity can be low-value, and valuable work can read as low-intensity - never turn an intensity signal into a performance score.
In the field
In a displacement account wary of monitoring, positioning focus/intensity as a friction diagnostic ('are we interrupting our people?') rather than a score is what keeps it defensible.
Practical task
On the demo focus/intensity view, pick one team and write a one-line read framing its pattern as a working-conditions hypothesis (e.g. fragmentation to investigate), explicitly not a performance score.
Self-check
A manager wants to rank the team by focus score. What do you push back on?
Intensity and focus describe activity shape, not value or output. High intensity can be busywork; valuable deliberation can read as low-intensity. It is not a performance ranking.
What might heavy fragmentation actually indicate?
Interruptions, meeting load or tooling friction - a working-conditions hypothesis to investigate, not proof of a distracted individual.
Where does the question of value actually belong?
Work Output. This screen shows how active time was shaped, not what it produced.
Verified vs demo. Screen is live in the demo at /#/focus; exact controls and figures are SME-validation-pending.