Flagship programme
Signal Taxonomy Lab
A twelve-week studio course for quality leads, routing owners, and operations partners who need customer support signal analytics they can defend without a vendor overlay.
Informational fee: £2,180 per seat · next Hardwick cohort listed on the enquiry form
What you should be able to do afterwards
- Separate retry loops from true first-contact failure without flattening both into “reopen rate.”
- Build a sampling frame that a sceptical analyst will not dismiss as anecdote shopping.
- Write a one-page signal brief that a finance partner can annotate rather than ignore.
- Explain why a CSAT movement lagged the thread by days, using timestamps you already own.
Modules
Queue as a text
How we read a week of tickets as a document with motifs, not as a volume graph with a sad colour.
Noise, intent, and policy fog
Drills on contacts that look identical in the CRM and mean opposite things for the desk.
Silence windows
Measuring pauses that customers experience as abandonment even when SLA clocks look healthy.
Handoff friction maps
Drawing the path a problem takes across teams, including the unofficial Slack detours.
Sampling without theatre
Stratified pulls, stop rules, and what to do when legal will not release the raw thread.
Briefing the building
Presentations that refuse a single score. You practice with your own desk, not a fictional retailer.
Instructor
Priya Calder ran quality for a UK telecoms desk before founding the studio’s teaching practice. She still marks every taxonomy draft herself. She will not pretend to be a data engineer; if you need warehouse work, we say so in week one.
Fee note
The published £2,180 is informational and covers tuition, critique hours, and materials. Travel to Hardwick, extra 1:1 days, and custom data processing sit outside that figure. See Fees and Refunds.
People who already sat the lab
Module 03 forced us to admit our “within SLA” chats still left customers hanging after the bot. Mild reservation: the briefing templates assume you have a willing ops partner. I did not, so week 12 was lonelier than advertised.
Priya’s refusal to let us average silence into handle time is the sentence I quoted in our Q2 review. I still argue with module 05’s stop rule, which felt conservative for a 12-person desk.
Questions we actually get
Do I need SQL?
No. Exports in CSV or a well-labelled spreadsheet are enough. If your only access is screenshots, we will spend the first fortnight reconstructing a sample, which eats taxonomy time.
Will this replace our QA scorecards?
No, and that is a real limitation. Signal Taxonomy Lab does not certify agents, does not produce a calibrated scorecard, and will not satisfy a regulator looking for call-monitoring coverage. It teaches you to name motion in the queue. Compliance sampling remains your existing process.
Can two people share a seat?
We allow a pairing if they work the same queue. Critique hours are still counted as one seat; do not expect two sets of written feedback.