template · helpdesk reading

Helpdesk reading template

Copy-paste skeleton. Five lines, every Friday. The CS Lead's reading of the week — theme, not count.

How to use

The five lines are non-negotiable. Replace every [...] with concrete content. The Top theme line is the discipline — find the one pattern, name it specifically. If you find yourself writing six lines, cut to five.

text

Helpdesk reading — week of YYYY-MM-DD

Volume:        [N tickets (vs M last week; +/-X%)]
Top theme:     [The one pattern that mattered most this week.
                Specific. Named cohort or persona where useful.
                Not a category — a shape.]
Change since:  [What shifted from last week to this week.
                If nothing shifted, name that.]
Watch:         [The forward-looking line. What to track next
                week to know if the theme grows or fades.]
For the trio:  [What the PO / TL / Designer should know.
                Brief input candidates surfaced here.
                If no action: name that.]

[Name (CS Lead)], YYYY-MM-DD.

Worked example — a reading the trio actually used

text

Helpdesk reading — week of 2026-05-12

Volume:        47 tickets (vs 38 last week; +24%)
Top theme:     Hebrew-speaking teachers reporting the grading
               shortcut "freezes" at submit. Three independent
               schools, similar wording. Looks like the dialog
               doesn't render until the language pack loads,
               and the page appears unresponsive for 2-3s.
               Persona: Gal (and her colleagues at pilot schools).
Change since:  Last week was all "how do I". This week is
               "doesn't work" — failure mode has shifted from
               learnability to reliability.
Watch:         Next week we enable two more Hebrew-default
               schools. If the same shape surfaces, this is
               an `observation-mismatch` not a one-off.
For the trio:  Likely brief input — language-pack loading
               affects perceived reliability for non-English
               graders. Worth a 30-min observation with
               one of the affected teachers before designing.

Maya (CS Lead), 2026-05-16.

Where this lives in your project

The reading goes to the trio by name — PO, Tech Lead, Designer — in the channel where the trio reads (email or a pinned weekly thread). It is read at the bi-weekly sync as the first input to the CS patterns section. The CS Lead writes the reading before the sync, not during.

What to do if a section resists

Resistance	What it means	Where to go
Cannot name one top theme	Either the week was truly varied (say so) or the CS Lead hasn't read deeply enough	Re-read the week's tickets for shape, not just routing
Volume number is the most interesting line	The reading is a tally, not a reading	Add context — "47 vs 38 last week" — then move to theme
Change since is "more tickets this week"	Time-series without interpretation	Name what shifted in kind, not in count
Watch line is generic	"We'll keep watching"	Specific. Cohort 3 enables 2026-05-25 — will the gap surface there too?
For-the-trio line is empty every week	Either CS isn't surfacing brief inputs, or the reading isn't being read	Both are chain-level signals at retro

Helpdesk reading template ​

Worked example — a reading the trio actually used ​

Where this lives in your project ​

What to do if a section resists ​

See also ​

Helpdesk reading template

Worked example — a reading the trio actually used

Where this lives in your project

What to do if a section resists

See also