Client notes
What teams said after observation sittings and briefings.
Short notes
“They sat with our night-shift operators for three sessions and mapped every dead-end in the billing console. The write-up named the exact screens — including one we had defended for years. We still disagree on one label, but the rest of the list cleared two weeks of tickets.”
Marina K., operations lead · Console Interaction Audit
“I expected a glossy slide deck. Instead we got a twelve-page briefing with path sketches that looked like the sticky notes our supervisors already use. The follow-up call was blunt about what observation could not prove.”
Tomás R., product manager · Interaction Briefing Pack
“The session review on our refunds workflow caught a hand-off our day crew never sees. Scheduling around shift change was awkward at first, but they waited through two handovers without rushing people off the floor.”
Priya S., support manager · Operator Session Review
“Useful, though the first draft leaned too hard on one junior operator’s habits. After we asked for a second sitting with a senior lead, the priority list settled and felt fair.”
Ellen W., console owner · Console Interaction Audit
Extended story: fulfilment console, Fremantle team
A mid-size fulfilment application team asked us to review the packing console after a release that added two confirmation steps. Supervisors reported longer pack times; engineering insisted the steps were “only two clicks.”
We observed four packers across morning and late shifts. Three consistently skipped a confirmation by using a keyboard shortcut that still worked from the previous release. The fourth followed the new path and lost roughly forty seconds per order when the second confirmation lagged on a slow network share.
The briefing separated “shortcut survivors” from “new-path users” and recommended either retiring the old shortcut with a visible warning or restoring a single confirmation with a clearer failure message. The team chose the warning path. Six weeks later they reported fewer packing disputes between shifts, though network lag on the share remained a separate infrastructure ticket outside our scope.
Extended story: utilities incident console
A utilities operations group in Western Australia needed a desk briefing only — live observation was restricted. We synthesised six months of incident-console tickets and two internal how-to guides. Themes clustered around ambiguous severity labels and a status that meant different things on weekday versus weekend rosters.
The pack recommended a live Operator Session Review once access rules allowed. Until then, the team used our label glossary in handover meetings. That interim use was not something we sold; it simply showed the briefing had landed in the room where the console is actually used.