TMS

TMS-CSA-1126

Full course structure

Four days. One practice file. Monday to Thursday, 09:00–16:30. 25 hours in the room. Facilitated by Ahmad A. Khan. Each block below is on the run sheet, with the moves and the faculty notes.

Thirty seconds, with voiceover. The outline, in the order of the four days.

01 Are we keeping the promise on speed?

02 Where is effort being wasted?

03 Who is leaving unhappy?

04 What changes before Monday?

Day 1 · Monday · 16 November 2026

The question before the chart

A chart without a decision is decoration. A dirty row makes the chart gossip.

Open the run sheet
  • Rewrite a vague leadership ask into metric, grain, window, and decision.
  • Run the trust check on the ticket log and flag every failure.
  • Build a queue summary: volume, breach rate, median hours — not one average.
TimeMethodSessionAim
09:00–09:30FrameThe contractSet the standard before anyone opens a file.
09:30–10:45FrameRewrite the askEvery person leaves with one question that has four parts.
11:00–12:30LabTrust the extractA Table named Tickets, five checks run, failures flagged in a new column, source cells untouched.
13:15–15:00LabThe first leadership tableOne summary by queue and by channel: tickets, breach rate, median resolve hours, open, reopen rate.
15:15–16:30CheckOne number you trustThe room hears the standard for a debrief, then sits a short check.

Day 2 · Tuesday · 17 November 2026

Where the work actually goes

Volume is not effort. The expensive work is the work that should not have existed.

Open the run sheet
  • Split the open pile into still inside the promise, and already late.
  • Show that fee-copy work meets the clock and still comes back.
  • Choose one complaint remedy and refuse the ones the counts do not support.
TimeMethodSessionAim
09:00–09:25ClinicClinic, then the wrong remedyUnblock yesterday without reteaching it, then aim the day at remedies.
09:25–10:45LabThe open pile is not one numberA split of open work: inside SLA at the as-of clock, versus already late. Plus inflow by week.
11:00–12:30LabThe work that came backReopen rate by queue, by reason, and by agent — in that order. Then repeat customers and transfers.
13:15–15:00LabComplaints are a different objectA complaint summary — category, upheld, age — and a decision drill.
15:15–16:30CheckWhat we stop reportingEach manager retires a metric, in writing, with the replacement next to it.

Day 3 · Wednesday · 18 November 2026

One model, three files

Excel answered the question once. Power BI is how the question stays answered when the file refreshes.

Open the run sheet
  • Relate tickets, surveys, and complaints without a many-to-many mess.
  • Write six measures you can defend in a sentence, including a response rate beside CSAT.
  • Leave with one page, titled as a sentence, that a director can read in two minutes.
TimeMethodSessionAim
09:00–09:25FrameWhat stays in ExcelAgree the handoff so nobody rebuilds Day 1 inside Power BI.
09:25–10:45LabThe model, not the canvasThree tables, a calendar, and relationships a manager can draw from memory.
11:00–12:30LabSix measures, said out loudEach measure accepted only after the author can say it in one sentence.
13:15–15:00LabOne pageA single page a director can read without a tour.
15:15–16:30CritiqueCritique, with a narrow set of questionsThree pages on the projector. The room practices Thursday’s pressure without the score.

Day 4 · Thursday · 19 November 2026

The Monday briefing

Finished means a skeptical peer cannot pull the number apart, and a director knows the ask.

Open the run sheet
  • Break a page on purpose: small n, blended SLA, agent standing in for a queue.
  • Deliver a six-beat brief inside six minutes.
  • Leave with a weekly rhythm and a private completion note.
TimeMethodSessionAim
09:00–09:20FrameThe six beatsThe brief has a shape, and they hear it before they build it.
09:20–10:45CritiqueRed teamEvery page gets one hostile pass, and one repair.
11:00–12:30BriefBriefing studioAhmad models one full brief, then each pair drafts theirs on the six beats.
13:15–15:30BriefBriefingsEvery manager speaks. Ahmad scores against the rubric during the brief, not after from memory.
15:40–16:30CheckThe rhythm, then the recordA one-page weekly rhythm, the feedback form, and the completion record.

What Thursday proves

  1. 01Write a service question a sheet can answer: metric, grain, window, and the decision it serves.
  2. 02Trust-check a ticket log and flag bad rows without overwriting the extract.
  3. 03Build an Excel summary of breach rate, reopen rate, and open work that is already late.
  4. 04Read a complaint file: aging, upheld, and concentration — and refuse a remedy the counts do not support.
  5. 05Join tickets, complaints, and surveys on the right key without double-counting.
  6. 06Write a short set of Power BI measures you can say out loud, including NPS that does not treat silence as a score.
  7. 07Design one page a director can read in two minutes.
  8. 08Brief it: observation, evidence, what it does not prove, and the ask.
  9. 09Set a weekly rhythm: who refreshes the extract, which three numbers stay, which three retire.

Participant pack: outline, manual, slides, practice file