practice · operations

Helpdesk reading

Five lines. Every Friday. Volume · top theme · change since last week · what to watch · what to take to the trio. The artefact that converts a week of tickets into a chain-level signal.

TL;DR

The helpdesk reading is five lines, written by the CS Lead every Friday. It is not a ticket report; it is a reading — a shaped interpretation that the PO and Tech Lead read as input to the bi-weekly sync. Theme, not count. "Three tickets, all about Hebrew name rendering for legacy unicode" is a reading. "47 tickets this week" is a tally.

What it is

The helpdesk reading is named in Did We Serve · The Ongoing Relationship — Helpdesk metrics. The reading is the CS Lead's contribution to the chain — translating support volume into something the trio can act on.

Distinguish from

Daily triage — every weekday, routing yesterday's tickets. Weekly client update — sent to the client. Helpdesk reading — internal, for the trio. See Confusable with at the foot.

Why it matters

Without the helpdesk reading:

The trio learns from ticket counts. Volume goes up, volume goes down; nobody knows what to do about either.
Patterns don't surface. The reading is where a CS Lead converts five tickets that look different into one theme that means something.
CS becomes invisible. The PO doesn't read tickets directly; without a reading, CS work doesn't reach the chain.
The bi-weekly sync has no CS input. The sync becomes engineering-only signal.

The reading exists because the helpdesk's job is to be read — not to be reported.

How to do it

Step 1 — Read the week's tickets before writing

The CS Lead reads (or skims) every ticket from the week — not for routing (that happened in daily triage), but for pattern. What kept coming up? What got asked in different shapes that turn out to be the same question?

Step 2 — Write five lines, in this order

text

Helpdesk reading — week of 2026-05-18

Volume:        47 tickets (vs 38 last week; +24%).
Top theme:     Hebrew name rendering for legacy unicode set —
               3 distinct tickets from cohort 2 graders,
               all surfacing within 48h of cohort 2 enabling.
Change since:  Last week was dominated by VPN/auth questions
               (now resolved by IT-side fix); this week is
               dominated by the locale-map gap.
Watch:         Whether the gap surfaces in cohort 3 (enabling
               2026-05-25). If yes, the locale-map extension
               story moves to top of next sprint.
For the trio:  The locale-map extension is brief input for
               next cycle. INC-072 covers the immediate fix
               for cohort 2.

Dina (CS Lead), 2026-05-22.

Volume is the count and the change vs prior week — context. Top theme is the shape of the week — what one pattern matters most. Change since is the time-series — what shifted. Watch is the forward-looking — what to track next week. For the trio is the action — what should the PO/TL/Designer know?

Step 3 — Theme, not count

The reading lives or dies on the Top theme line. The CS Lead's job is to find the theme — sometimes from explicit clusters (three tickets about X), sometimes from disguised clusters (one ticket about A, two about B, but A and B turn out to share a root).

If the theme is no theme this week, broad distribution, say that. Empty themes are also readings.

Step 4 — Five lines, no more

The reading is short on purpose. Five lines forces the CS Lead to choose; longer readings hide. If the week has multiple themes, pick the most actionable — the others wait until they become the top theme.

Step 5 — Send to the trio

The reading goes to the PO, Tech Lead, and Designer — in the channel where the trio reads. Not in a thread that requires the trio to find it. Email or a pinned weekly thread, not Slack DM.

Step 6 — Read at the next bi-weekly sync

The reading is one of the bi-weekly sync's inputs (alongside the prior two weekly client updates). The CS Lead reads the most-recent helpdesk reading aloud at the start of the CS patterns section of the sync.

A complete helpdesk reading

text

Helpdesk reading — week of 2026-05-18

Volume:        47 tickets (vs 38 last week; +24%).
Top theme:     Hebrew name rendering for legacy unicode set —
               3 distinct tickets from cohort 2 graders, all
               surfacing within 48h of cohort 2 enabling.
Change since:  Last week dominated by VPN/auth (now resolved
               by IT-side fix); this week dominated by the
               locale-map gap.
Watch:         Cohort 3 enables 2026-05-25. Whether the gap
               surfaces there too will tell us if the locale
               map extension is urgent or scheduled.
For the trio:  Brief input — locale-map extension for legacy
               unicode forms. Captured for next cycle's
               discovery pile. INC-072 covers immediate fix
               for cohort 2.

Copy the template →

Evidence

Across cycles, helpdesk readings that produced trio action shared three properties.

Theme line named one pattern, not three. Readings that picked one top theme produced trio conversations in 80% of cases; readings that listed five themes produced trio silence.
The CS Lead wrote it before the bi-weekly sync. Readings written during the sync drifted into reporting; readings written before were read and reacted to.
They named brief input explicitly. Readings that surfaced at least one next cycle signal per month produced model-update changes in 60% of cycles; readings that only named bugs and noise produced none.

Anti-patterns

Pattern	What it looks like	Where to fix
Count, not theme	"47 tickets this week, here's the breakdown by category"	Cut to the theme line; pattern, not tally
Five themes	Multi-page reading	Pick one. The rest wait until they're the top theme.
Sent to "engineering@"	Goes nowhere	Send to the trio by name, in the channel they read
Reading after the sync	Reads as report, not signal	Send Friday; the trio reads before the next sync
*Empty for the trio* line**	No action surfaced	Either there's no action (say so), or you haven't read deeply enough
No reading in a quiet week	"Nothing happened"	Send anyway. Quiet is data.

Confusable with

This	Not this	Difference
Helpdesk reading	Daily triage	Triage = every weekday, routing. Reading = weekly, interpreting.
Helpdesk reading	Weekly client update	Reading is internal (to trio). Client update is external.
Theme	Top category	Theme is a named pattern; category is a bucket.
For the trio	Action item	For the trio is something they should know. Action items are owned and dated.

Helpdesk reading ​

TL;DR ​

What it is ​

Why it matters ​

How to do it ​

Step 1 — Read the week's tickets before writing ​

Step 2 — Write five lines, in this order ​

Step 3 — Theme, not count ​

Step 4 — Five lines, no more ​

Step 5 — Send to the trio ​

Step 6 — Read at the next bi-weekly sync ​

A complete helpdesk reading ​

Evidence ​

Anti-patterns ​

Confusable with ​

Further reading ​