Build operating routines
Objective. Translate dashboards into daily, weekly and monthly customer decisions by building a manager review agenda and an action log with ownership, so the product changes what the customer does rather than just what they can see.
Dashboards do not create value; decisions do. This lesson teaches you to convert the applications into a cadence - daily exception triage, weekly output and adherence review, monthly outcome check - each with a tight agenda and an action log that assigns an owner and a due date. A routine is the difference between a tool that is logged into and a tool that is relied on.
See it in the demo
The customer problem
A customer with beautifully configured dashboards can still get zero value from them. The failure is quiet: managers glance at a screen, nothing is assigned, nothing changes, and over weeks the login frequency falls to zero. The dashboard answered a question nobody was accountable for acting on. Business impact: the sponsor cannot point to a single decision the product changed, so there is no value story at renewal and no case for expansion. The missing ingredient is not more data - it is a routine: a fixed cadence, a short agenda, and an action log where decisions get an owner and a date. Operating routines are what turn observation into outcome.
How Time Champ addresses it - cadence by horizon
Map each horizon to the applications that feed it. Daily (team lead, 10 minutes): Time and Activity daily operations and exceptions - who is absent vs available, which exception is worth a conversation today; in a contact-centre, Real-Time Adherence control room and Intraday Management control tower - is today's plan still viable and which corrective action protects delivery. Weekly (manager, 30 minutes): Work Output People and teams - output attainment, quality and cost per clean unit, which team moved and whether it is real; Quality and Call QA review queue and coaching. Monthly (ops leader, 60 minutes): RCM Operations outcomes and SLA/risk, Value Leakage recovery status - which findings became verified recovery. Each cadence reads from a screen and ends in logged decisions. The decision-support surfaces (Intraday Copilot, RCM briefings) move the review from signal to proposed action.
What to say / do - agenda and action log
Build the manager a one-page weekly agenda: (1) Review the two or three numbers that map to the success plan outcome (C01). (2) For each notable change, one question - is it real or a data/standard artefact (C05)? (3) Decide one action per real signal. (4) Log it. The action log is the centrepiece: columns for signal observed, decision, owner, due date, and outcome-when-reviewed. The owner must be a named person, not a team; the due date must exist; the outcome column is checked at the next cadence so actions do not evaporate. Talk track to the manager: 'This review is not about watching numbers - it is fifteen minutes to turn two signals into two owned actions, then we check last week's actions actually happened.' Closing the loop on prior actions is what distinguishes a routine from a recurring meeting.
Avoiding the simulated-fix trap
Several applications let you simulate or propose an action - Intraday Management what-if, Scheduling optimization, Value Leakage opportunities. Build the routine so the log distinguishes proposed/simulated from executed from outcome-achieved, because they are not the same thing: a simulated improvement is not an executed action, and an executed action is not yet an achieved service result. The same discipline applies to Value Leakage, where the recovery screen separates recovered capacity from cash recovered. If the action log blurs these, the monthly review will overstate results and the QBR (C08) will not survive scrutiny. Teach the customer to let a signal travel the full path - observed, action owned, action executed, outcome measured - before it is counted as value.
Objections and honest limits
'We already have a weekly meeting' - good; the task is to add the two numbers and the action log, not a new meeting. 'My managers will not fill in an action log' - keep it to one line per signal and review it live so it is visibly used, not bureaucracy; an unused log is worse than none. 'Can the tool just alert us instead?' - alerts surface signals but do not assign ownership or close loops; the routine is still required. Honest limits: the cadence you design assumes the underlying data passes the C02 readiness and C05 definition checks - a routine built on untrusted data industrialises wrong decisions. Where a decision-support feature's production behaviour is uncertain, position it as support for a human decision and confirm with product rather than promising automated action.
Interpretation check
A dashboard produces value only through a routine that ends in owned, dated, loop-closed actions. A review that looks at numbers but assigns nothing is a meeting, not a routine.
In the field
KnackGlobal's monthly RCM review reads Mission Control outcomes and Value Leakage recovery to decide which denial/payer issue to own next; separating recovered capacity from collected cash in the action log is what keeps the ProHance displacement story honest and renewable.
Practical task
For one role on your account (RCM team lead, contact-centre manager, or ops leader), write a one-page review agenda for the right cadence and a blank action log template (signal, decision, owner, due date, outcome). Populate it with two real signals read from the relevant demo app, each turned into an owned, dated action, and mark whether each is a simulated or executed step.
Self-check
Why must an action log have an owner column and an outcome-when-reviewed column?
Without a named owner (not a team), actions diffuse and nobody acts. Without reviewing outcomes at the next cadence, actions evaporate unchecked. Both columns are what convert observation into reliable decisions and give the QBR evidence.
Map the three horizons to one application each and the decision each supports.
Daily: Time and Activity daily operations / RTA control room - which exception or coverage gap to act on today. Weekly: Work Output People - which output/cost change to act on and whether it is real. Monthly: RCM Operations outcomes / Value Leakage recovery - which outcome moved and what became verified value.
Why must the action log separate simulated, executed and outcome-achieved?
A simulated/proposed fix (Intraday what-if, Scheduling optimize, a leakage opportunity) is not an executed action, and an executed action is not yet an achieved result. Blurring them overstates value and makes the QBR indefensible.
A manager says they already meet weekly, so no new routine is needed. What do you actually add?
Not a new meeting - the two or three success-plan numbers, one real-or-artefact question per change, one owned action per real signal, and a live-reviewed action log that closes last week's loops.
Verified vs demo. The screens and the daily/weekly/monthly cadences are demo-shown. Decision-support features (Intraday Copilot, RCM briefings) and automated alerting behaviour in production are entitlement-dependent - position them as support for human decisions and confirm with product.