cx-career-pathing

Use to design support career progression with IC and lead tracks, skill gates instead of tenure alone, and paths that do not treat leaving the phones as the only promotion. Trigger for "career pathing

SKILL.md

GitHub

Career pathing for support

In many support orgs, the only promotion is off the queue — team lead, QA, WFM, or "special projects". Strong agents who want to stay customer-facing hit a ceiling; weak managers get promoted because they were available. Tenure becomes the proxy for merit because nobody wrote down what merit means at each level.

A usable progression framework answers: what changes at each level, how you know someone is there, and why both IC and lead tracks exist.

Step 1: name the tracks

At minimum, split:

Track Purpose
IC (individual contributor) Deep customer work, complexity, coaching-by-example, subject-matter depth
Lead / management People development, scheduling, performance process, queue health

Optional specialist lanes (QA analyst, WFM analyst, KM, training) should lateral from IC, not be the only escape from the phone. If every senior agent must become a lead to earn more, you will lose your best ICs or promote reluctant managers.

State whether pay bands align to levels (structure only — do not invent salary percentiles without HR data).

Step 2: define levels by scope of impact

Typical IC ladder (rename to your titles):

Level Scope Differentiator
Foundation Owns own tickets Meets quality and reliability bar on primary work
Proficient Owns complex strata Independent on hard drivers; consistent QA
Senior IC Owns outcomes beyond self Mentors on floor; handles escalations; improves macros/KB
Principal / expert IC Owns capability for others Defines playbooks; calibrates QA; leads incident comms to agents

Lead ladder:

Level Scope
Team lead 6–12 agents; coaching, scheduling input, first-line performance
Senior lead / manager Multiple teams or site; hiring; cross-functional fixes

Promotion changes scope, not just tenure. Write one sentence per level: "A Senior IC is accountable for …"

Step 3: skill gates vs tenure

Tenure is a minimum eligibility, not proof of readiness.

For each promotion, specify evidence gates:

Gate type Example
Sustained performance QA at or above team median on comparable mix for two consecutive review periods
Scope evidence Led nesting for N agents; owned driver X playbooks
Skill matrix Independent on defined complex strata (see skills-matrix skill)
Lead-specific Documented coaching packs; calibration participation; attrition/engagement not ignored

Avoid gates agents cannot influence (CSAT on assigned mix only, luck-based SPIFF wins).

No universal trait list. Gates reference observable work products and metrics you already measure fairly.

Step 4: avoid common path failures

Failure mode Fix
Promotion = leave the phones Add Senior IC and Principal titles with pay parity to first-line lead
Title inflation One level change at a time; panel calibration for lead promotions
Tenure queue Publish gates; reject "time served" as sole justification
Permanent trial lead Time-box acting roles with explicit evaluation
Specialist dead end Lateral moves with level mapping, not pay cut
QA as only senior path Only works if QA is staffed as career, not parking

Step 5: process and transparency

Agents should see:

  • Level definitions and gates — internal doc, not tribal knowledge
  • How to apply or be nominated — and whether manager sponsorship is required
  • Panel or calibration for lead and principal promotions
  • Feedback on failed promotion — which gate missed, with evidence
  • Re-application window

HR/legal own comp bands and employment law; this skill defines operational evidence, not pay numbers.

Step 6: connect to development

Each level should map to development actions, not vague "leadership training":

  • Senior IC: nesting ownership, complex queue rotation, KB authoring
  • Lead: coaching pack skill, WFM basics, hiring panel training
  • Principal: scorecard calibration, driver taxonomy ownership

Development without a path feels like extra work; path without development is fiction.

Traps

  • Promoting top QA score to lead — individual performance ≠ people leadership.
  • Single track hidden in job titles — "Senior agent" means IC to you and lead-in-waiting to them.
  • Gates that reference metrics agents cannot see — destroys trust.
  • No demotion/stay rules — clarify whether level is retained if performance drops.
  • Copying engineering ladders — support IC impact is customer and ops outcomes, not code shipped.

Present results to the user

  1. Track structure — IC vs lead (and specialists), with purpose of each.
  2. Level definitions — scope sentence per level, aligned to your titles or proposed renames.
  3. Skill gates — evidence required per promotion; tenure as eligibility only.
  4. Anti-pattern fixes — how this addresses phone-as-ceiling and title inflation.
  5. Process — nomination, panel, feedback on miss, re-application.
  6. Development map — actions per level tied to real work.
  7. Explicit gaps — comp bands, headcount ratios, or HR policies not supplied.