skill · foundations
CS Lead foundations
A six-week, ten-step path. By the end of it you have routed tickets correctly, run a release-to-support handoff that protected both sides, written a weekly helpdesk reading the trio acted on, and added your voice to a signal reading. You are not a senior CS Lead. You are a CS Lead whose first cycle gave the team an honest ear.
TIP
A skill is read → practice → check → reflect, anchored to your real cycle. Bring real tickets from your week.
Mastery looks like
When you finish this path, you can:
- Sort an unfamiliar ticket in three minutes — bug, brief input, noise.
- Write a five-line weekly helpdesk reading the trio actually reads.
- Refuse a release without a CS-signed handoff, calmly.
- Add a voice-of-customer paragraph next to the signal reading.
- Grow at least one L1 into L2 craft over the quarter.
Self-rating before you start
| 1 — Never | 3 — Sometimes | 5 — Default | |
|---|---|---|---|
| Tickets route cleanly into bug / brief input / noise | |||
| I write a weekly helpdesk reading | |||
| The trio reads my weekly reading | |||
| Every release has a CS-signed handoff | |||
| The signal reading has my voice next to it |
Step 1 — Orient in the chain
Read: Did We Serve? · The Ongoing Relationship · After We Build · Bugs and Their Roots · The Map.
Practice prompt: in three sentences, explain how a ticket saying "it's broken" becomes (a) a bug, (b) a brief input, or (c) noise.
Step 2 — Sit on L1 for a day
Practice prompt: spend a full day on L1 with the existing CS team. Take five tickets end-to-end. Don't try to optimise — observe.
Output: a one-page note on what surprised you about the team's current routing.
Step 3 — Walk the pipeline
Practice prompt: trace ten recent tickets through L1 → L2 → L3. For each, name where it landed and whether the landing was right.
Output: a note on at least one misrouted ticket and where it should have gone.
Step 4 — Sort a backlog
Read: After We Build · Bugs and Their Roots.
Practice prompt: take a week's incoming tickets. Sort each into bug, brief input, or noise. Push back on engineering for tickets routed as bugs that are not.
Mini-check: a bug should trace to a chain level. If it doesn't, it's a brief input or noise.
Step 5 — Write your first weekly helpdesk reading
Practice prompt: five lines. Volume. Top theme. Change since last week. What to watch. What to take to the trio. Send it.
Pair task: ask the PO: did this reading tell you something the dashboards didn't? — note the answer.
Step 6 — Hold the release-to-support handoff
Read: Did We Serve? · The Ongoing Relationship.
Practice prompt: for the next release, sit with the trio. Read the release brief. Ask the questions a Tier-1 agent would ask the first time a customer calls. Refuse a handoff that doesn't answer them.
Output: a handoff note signed by the trio.
Step 7 — Watch the first 48 hours
Read: After We Build · The First 48 Hours.
Practice prompt: during the cycle's first release, watch what tickets arrive. Note theme, not count. Compare to the brief's prediction.
Step 8 — Add your voice to the signal reading
Read: After We Build · Signal & The Prediction.
Practice prompt: when the PO writes the signal reading, contribute your paragraph. Name the moments tickets witnessed.
Mini-check: if your paragraph is a list of complaints, rewrite. The voice-of-customer note is a moment, not a feature request.
Step 9 — Grow one L1
Practice prompt: pick one L1 agent. Walk them through one L2 ticket end-to-end. Hand them the next similar one with you on standby.
Pair task: ask them: what was hard about that? what's still unclear? — feed back into routing docs.
Step 10 — Teach back, contribute back
Practice prompt: write a one-page guide for the next new CS Lead joining your team. What I wish I'd known before my first cycle. One page.
Authoring contribution: open a PR — sharpen one thing in the corpus about the support-to-bug pipeline.
Self-rating after: rate yourself again. Bring the gap to your next cycle.
After this path
- CS Lead · Practitioner (coming) — multi-product support pipelines, SLA design.
- CS Lead · Advanced (coming) — relationship strategy across the studio.
Stuck?
| If you got stuck at | Read |
|---|---|
| Step 3 — pipeline felt arbitrary | The Ongoing Relationship |
| Step 4 — every ticket felt like a bug | Bugs and Their Roots — bugs trace to a level |
| Step 5 — reading felt long | Cut to five lines. Theme, not count. |
| Step 8 — voice-of-customer felt like a feature request list | Name a moment, not a feature |