Busy teams, declining output
Objective. Equip Sales and CSM to run the single most common Time Champ problem play: teams are fully occupied yet delivery is slipping. Show which applications turn 'busy' into 'delivering', how they chain, how the value is measured, and the honest boundary of the claim.
A leader sees full attendance, high utilisation and long hours, and still misses delivery. This play reframes the conversation from activity to output: Time and Activity proves the hours were available and used, Work Output shows whether the expected work was actually produced to standard, Work Understanding explains why it lagged, and Value Leakage turns the recoverable gap into a tracked, owner-assigned recovery with capacity kept separate from cash. The value is the ability to manage to results; the boundary is that the tools surface candidate causes, not proven causality, and a customer's own numbers depend on validated definitions.
See it in the demo
The problem and who feels it
The symptom is a contradiction leaders cannot explain: dashboards say the team is present, utilised and often working overtime, yet backlog grows, SLAs slip and promised volume does not land. Who feels it: an operations or delivery leader held to a throughput or SLA number; a finance partner who approved headcount and overtime against 'busyness' and cannot see the return; a team manager caught between 'everyone is flat out' and 'we are still behind'.
The reason the problem is invisible is that activity and attendance tools answer a different question from the one the leader is being judged on. They tell you people were occupied; they do not tell you whether the expected work got done, to standard, at acceptable quality and cost. So the leader argues for more people, because that is the only lever the available evidence supports.
The business impact
Three costs accrue while the gap is invisible. Paid-for-but-unrealised capacity - hours are bought and used but the output they should produce is not landing, and no one can size the shortfall. Wrong decisions - headcount, overtime and staffing are negotiated against activity, so the organisation over-hires or burns overtime without moving delivery. Misjudged teams - leaders compare raw completed-work counts across teams with different mix, complexity, tenure and quality, and reward or penalise the wrong people.
In a competitive or displacement setting the impact is sharper: the deciding question becomes output per FTE and cost per clean unit, which an activity-only incumbent cannot answer. Being unable to show results, not just effort, is what loses the argument.
Which applications address it and how they chain
The play chains four applications, each independently useful, in the order the leader's question unfolds.
- Time and Activity (https://time-activity.demo.timechamp.io/) establishes that the paid hours were available and used - attendance, utilisation and exceptions. This closes off 'they were not really working' and sets the denominator honestly.
- Work Output (https://work-output.demo.timechamp.io/) is the heart of the play: it counts completed work in context of complexity, standard, quality and cost, so you can put utilisation next to output attainment and name the gap - the fully-utilised team that is still below standard.
- Work Understanding (https://work-understanding.demo.timechamp.io/) answers why: waiting, friction, rework and process variants behind the shortfall, so the gap becomes a specific, actionable finding rather than a complaint.
- Value Leakage (https://leakage.demo.timechamp.io/) attributes the recoverable value, assigns an owner and tracks recovery from baseline to verified - keeping recovered capacity explicitly separate from cash recovered.
The chain is the story: hours used (T and A) - work produced to standard (Work Output) - why it lagged (Work Understanding) - what is recoverable and verified (Value Leakage).
The value story and how it is measured
The value is the ability to manage to results instead of activity: to see clean output per paid hour, know the cost of a clean unit, tell a busy team apart from a delivering one, and act on the specific reason output lags.
Measure it with the applications' own candidate measures, against the customer's baseline, not an invented benchmark: counted-work coverage (what share of real completed work is actually counted - gaps undercut everything downstream); clean output per paid hour (output that met quality, over the hours that produced it); cost per clean unit; and, once a finding is acted on, verified recovery with evidence and time to verification from Value Leakage. Keep 'clean' honest - output per hour without the quality filter flatters a fast-but-wrong team.
The honest boundary - what this does not solve
This play diagnoses and sizes the output gap and points to its likely cause; it does not by itself fix the operation. Be explicit about four limits.
- Causality: Work Understanding and any AI-impact view surface candidate causes and correlations, not proven causality. Treat them as leads to validate before acting.
- Definitions first: output, output-per-hour and cost-per-unit are only as good as the agreed completion definition, source coverage, standards and complexity weightings. Confirm these with product and the customer before quoting their numbers.
- Capacity is not cash: a recoverable-capacity figure is an opportunity, not money in the bank. It becomes cash only through a decision the customer makes (redeploy, avoid a hire, take on more volume), and Value Leakage keeps the two separate on purpose.
- Overlap: multiple friction findings cannot simply be summed into one savings number.
Sales states these out loud; CSM validates them before the first business review.
Interpretation check
High utilisation and full attendance do not prove delivery. The gap this play exposes is a team that is fully occupied yet below output attainment - and that gap is only valid once completion definitions, source coverage, complexity and quality are agreed, and causes are validated rather than assumed.
In the field
KnackGlobal RCM (largest customer, active ProHance displacement): the deciding metrics are output per FTE and cost per clean claim, which an activity-only incumbent cannot produce. This play is the direct route to them - utilisation confirmed, output attainment contrasted, the lag explained, and the recoverable capacity tracked to verified recovery, all kept honest on definitions and on capacity versus cash.
Practical task
Using the demo lab, build a 7-minute 'busy vs delivering' story for one team: show utilisation in Time and Activity, then output attainment in Work Output and name the gap, then one candidate cause in Work Understanding, then how Value Leakage would track the recovery with capacity separate from cash. Write the four definitions you would validate with the customer before quoting any of their numbers, and the one limit you would state out loud in the call.
Self-check
A prospect says 'my teams are already at 90% utilisation, so the problem must be headcount'. How does this play respond?
Accept the utilisation figure (Time and Activity confirms hours were used) but put it next to output attainment in Work Output. If a highly-utilised team is below standard, the problem is not raw hours - it is the gap between busy and delivering, and Work Understanding shows why before anyone buys headcount.
Why is Time and Activity in the chain if the play is about output?
It establishes the denominator honestly - that the paid hours really were available and used - so the output gap cannot be dismissed as 'they were not working'. It frames the question; Work Output answers it.
What must a CSM validate before trusting a customer's cost-per-clean-unit number?
The completion definition (what 'a completed unit' is), source coverage (is any completed work uncounted), standards and complexity weightings (agreed, not defaults), and the quality signal that makes 'clean' real. Loose definitions make every downstream number loose.
Where is the capacity-versus-cash line in this play?
Value Leakage sizes recoverable capacity as an opportunity and tracks it to verified recovery, but a capacity figure is not cash. It becomes cash only through a customer decision to redeploy, avoid a hire or absorb more volume, and the two are reported separately.
A manager wants to rank five teams by last month's completed transactions. What is the error to prevent?
Comparing raw counts across different work type, complexity, period, tenure and quality. Normalise first and use clean output per paid hour, or the ranking rewards the wrong teams.
Verified vs demo. The full chain - utilisation, output attainment, complexity and quality, a friction finding and a tracked recovery - is demo-shown on a seeded dataset. A customer's actual completion definitions, source integrations, standards and resulting cost-per-clean-unit must be confirmed with product and the customer; causes are candidates to validate, not proven, and capacity value is an opportunity, not cash.