Path From CX Manager to Director of CX

You drove a 14-point NPS gain in 18 months. You own three flagship programs. When the Director of CX role opened, you assumed the conversation was a formality. Then someone from product strategy got the slot.

If that's happened to you, or to someone on your bench you believed was ready, the instinct is to call it political. It usually isn't. The instinct after that is to do another flagship program and wait. That's also wrong.

Director of CX isn't "CX manager with a bigger budget." It's a different job, and the promotion is a campaign for a role that requires capabilities you may not have built yet. This guide is for two readers in parallel: the CX manager building the case for themselves, and the VP of CS coaching their bench. Both should leave with the same map.

Why Program Success Alone Backfires

Companies that promote on program metrics alone produce Directors who stall within 18 months. The new Director doubles the program count and discovers the role isn't about programs. It's about four things their predecessor didn't have to do at the same depth.

Cross-functional influence over product, marketing, and CS roadmaps. Directors don't just run programs. They change what other teams ship.

Hiring and retaining a CX team. Directors are evaluated on the bench they build, not the dashboards they run. A Director who has never hired, ramped, developed, or cleanly exited a team member is a Director on training wheels.

CX strategy at board level. NPS movement is a metric. CX-to-revenue is a narrative. The Director sits in the room where the CFO and CEO decide what to fund.

VoC as an operating system. Surveys are snapshots. Directors own the continuous voice-of-customer engine wired into product, support, and sales. It catches problems before the quarterly NPS reading does.

Program success is the floor, not the ceiling.

Shift 1: From Running Programs to Cross-Functional Influence

The CX manager says, "I run our NPS program, our journey mapping, and our customer advisory board." The Director says, "Product changed three roadmap items last quarter because of CX input. Marketing redesigned the post-purchase nurture because of the CAB. CS rebuilt the renewal play because of churn driver analysis."

The CX manager owns programs. The Director moves other teams' work. You don't get credit in your own quarterly review for a roadmap item product shipped. You get credit when the VP of Product says in the exec meeting, "We shipped this because CX showed us the data."

Development plan:

• Biweekly standing 1:1s with the lead PM, lead growth marketer, and lead CS manager. Bring one piece of customer signal each session. Ask: "Does this change anything you're working on?" Track which conversations move something.
• A quarterly CX-into-roadmap ritual. Present the top three customer signals before product finalizes next quarter. Don't ask permission; send the invite.
• Co-own at least one OKR with a peer function. Not "support CX." Your name and theirs both show up.
• Track named influence. Keep a private list: PRD-217 (CAB session). Q3 nurture redesign (post-purchase journey analysis). Renewal play v3 (churn driver report). This list is your proof.

Customer Journey Mapping That Actually Changes Product covers turning journey work into roadmap moves.

Shift 2: From IC Manager to Builder of a CX Team

You may manage two CX coordinators today. That's not this shift. The shift is from managing the work to managing the careers of people who will run that work better than you do.

Directors are judged on three team questions. Can you hire well, with a rubric and two strong hires in the last 18 months? Can you develop people, with someone promoted under you on a documented plan? Can you exit cleanly, with one termination owned honestly without losing your team's trust? Any "not yet" is a gap to close before the conversation, not after.

Development plan:

• Hire and ramp at least two CX team members before going for Director. No headcount? Ask for an intern or a rotation from CS. The point is the rep.
• Document a hiring rubric. Five competencies, behavioral questions, calibration with one peer interviewer. Artifact-level proof you hire on a system, not a hunch.
• Run skip-level conversations. Quarterly, 30 minutes with each of your reports' direct reports or peers. This is the muscle of being a manager of managers.
• Own one termination cleanly. The first time you do it as a Director without a manager rep underneath you is the worst time to learn.

A VP who tells their bench "you need more program wins" when the actual gap is team-building is doing both of you a disservice.

Shift 3: From CX Metrics to Board-Level Strategy

The board doesn't want your NPS dashboard. They want a 12-month CX strategic narrative that shows up in the revenue model.

NPS moved from 32 to 46. So what? Here's the so-what version: detractor-to-passive movement among enterprise accounts correlates with a 7-point lift in renewal probability, roughly $2.4M of ARR protected, against a CX program cost of $380K. That's the conversation the CFO understands.

This is also where CX managers confuse visibility with influence. Presenting at all-hands isn't influence. Being in the CEO's board deck isn't either. Influence is when the CFO asks you a question in board prep and your answer changes a number.

Development plan:

• Build a CX-to-revenue model connecting NPS, churn drivers, and CSAT to renewal probability, expansion, and CAC. It doesn't have to be perfect. It has to exist.
• Present to the exec team quarterly. Not "join the meeting." Present, with slides, a recommendation, and a number you're asking the room to commit to.
• Get on the board deck even as a guest. Two slides per board meeting is enough. Be in the room often enough that the board recognizes you when the Director conversation happens.
• Learn the CFO's vocabulary: gross retention, net retention, CAC payback, magic number. If you can't translate your work into those terms, you can't have the conversation.

Building an NPS Program That Drives Action covers wiring NPS into the CFO's model.

Shift 4: From Survey Cycles to VoC as a System

A CX manager runs surveys. A Director runs the system that listens continuously, routes signal to the right team, and proves it changed a decision.

VoC as a system means support tickets, sales call notes, churn interviews, in-app feedback, NPS verbatims, and social signal all flow into one place where they're tagged and surfaced. Engineering invests in the pipes. Product gets a weekly digest of customer pain by feature area. Sales hears about objections before lost-deal reports surface them.

This shift requires the most engineering buy-in, which is why CX managers underinvest in it. You can't build a real VoC system on a Google Sheet and a quarterly survey blast.

Development plan:

• Design the VoC architecture on paper before asking for funding. Sources, routing, ownership, consuming teams. A one-page diagram is enough to start the conversation.
• Get engineering investment. Not "we'll do it ourselves with Zapier." A named engineer for at least a quarter. If you can't get that, the gap isn't VoC; it's your influence with engineering, which loops back to Shift 1.
• Prove the system changed a roadmap decision. Within 90 days, point to a specific PRD, campaign, or CS play that exists because of what VoC surfaced. If you can't, the system isn't working.

Wiring VoC Feedback Into the Product Roadmap is the operational guide for turning VoC into a system that changes shipped product.

Director-Readiness Self-Assessment

Score 1 to 5 on each. No evidence is a 1 or 2.

Shift 1, Cross-functional influence. Can a peer in product name a roadmap item that shipped because of your work? In marketing, a campaign that changed? In CS, a play that was rewritten? Co-own an OKR with a non-CX function? A quarterly ritual that puts CX signal in front of roadmap decisions?

Shift 2, Team building. Hired and ramped two CX team members? Documented hiring rubric? Anyone promoted under you? Owned a clean termination? Run skip-levels on a regular cadence?

Shift 3, Board-level strategy. CX-to-revenue model you can defend in front of the CFO? Presented to the exec team in the last two quarters? In the board deck? Can you translate CX into gross retention, net retention, and CAC payback? When the CFO asks a CX question, does your answer change a number?

Shift 4, VoC as a system. Continuous VoC system in production? Multiple input sources? Named engineer on the pipes? Consuming teams get digests they actually read? A decision the system changed in the last 90 days?

Below 3 of 5 in a single shift is the gap to close before the Director conversation. For VPs, score the manager first, then have them score themselves. The gap between the scores is usually the most useful coaching conversation of the year.

Cross-Functional 1:1 Standing Agenda

Biweekly, 30 minutes, same agenda for the PM lead, growth marketer, and CS manager.

1. What's on your roadmap this quarter that I should know about?
2. Here's one piece of customer signal that might change something you're working on. Bring data; ask if it changes anything.
3. Where am I getting in your way, or where could I be more useful?
4. What's one decision in the next two weeks where CX input would help? Commit to bringing it.

The point isn't the agenda. It's showing up biweekly with signal that changes their work. Do that for two quarters and you have cross-functional influence.

Manager-to-VP Promotion Script

The conversation to have with your VP six months before you want the title.

"The Director of CX role is what I'm building toward. I'm not asking for it today; I'm asking you to coach me toward it.

Here's how I'd assess myself. Cross-functional influence: [score] because [evidence]. Team building: [score]. Board-level strategy: [score]. VoC as a system: [score].

Where are the biggest gaps? I'd like to leave with one or two priorities, not five. And I'd like to know what evidence would change your assessment. Six months from now, let's look at this together again."

This signals ambition without entitlement. It makes the VP a coach, not a gatekeeper. Most VPs run toward this conversation. The ones who don't are telling you something.

90-Day Development Plan Worksheet

Pick the shift with your lowest score. Don't close all four at once.

Days 1 to 30, diagnose and design. Score yourself on the evidence questions. Write down the artifact that would move your score to a 4 (hiring rubric, CX-to-revenue model, VoC architecture diagram). Identify the one peer leader whose buy-in you need.

Days 31 to 60, build and socialize. Produce the artifact. Ask the peer leader: "What would make this useful to you?" Get one piece of evidence into the world: a 1:1 you ran differently, a hire you closed, a board slide you presented.

Days 61 to 90, prove and re-score. Point to the named outcome. Re-score and ask your VP to score you too. If the gap closed, pick the next shift. If not, diagnose why first.

Three months. One shift. One artifact. One named outcome.

Common Pitfalls in the Director Campaign

Assuming program success equals promotion. It's the entry ticket. Every additional flagship program produces diminishing returns.

No cross-functional credibility. If a peer in product can't name a thing you've shipped together, you don't have the influence shift. Slack and all-hands don't count.

No team management track record. You can be a brilliant manager of programs and still not be a manager of managers-in-waiting. The Director job is mostly the latter.

Waiting to be tapped. Promotions are rarely surprises. They're the result of a campaign by someone who said out loud what they wanted, asked for the gaps, and closed them on a visible timeline.

Confusing visibility with influence. Presenting at all-hands is visibility. Changing a roadmap decision is influence. Only one earns the title.

Common Pitfalls Every CX Manager Falls Into covers the broader pitfalls of the manager job.

Measuring Whether You're Ready

Four signals tell you the campaign is working.

1. Cross-functional influence. When your VP asks the PM lead, marketing lead, and CS manager independently, they cite specific shipped work. Named PRDs, campaigns, plays. Not "she's great to work with."
2. Roadmap items influenced. You can point to decisions that went your way in the last two quarters because of CX input, and those teams agree with your version.
3. Exec engagement. You're invited into board prep, not just briefed afterward. The CFO asks you questions in real meetings.
4. Team built. People you've hired have been promoted under you. Your team is the bench other VPs try to poach from.

When three of four are true, the conversation is "here's the offer," not "make the case." For VPs, those four signals are your honest rubric. If your bench candidate has program wins but doesn't hit them, you're about to promote a Director who will stall.

How Rework Supports the Director Campaign

The campaign means tracking artifacts most CX managers don't: influence wins, hiring rubric versions, board deck appearances, VoC milestones, and the running list of named decisions that moved because of your work. Most managers keep all of this in a personal Notion doc and reconstruct the case from memory.

Rework Work Ops (from $6/user/month) gives you one place for development milestones, peer 1:1 commitments, and the influence log behind the four shifts. When the conversation comes, the evidence is dated and tied to outcomes. For VPs with a bench in parallel, it's where the plan and check-ins live.

What Comes After

If you close the four shifts and the Director conversation still isn't happening in 6 to 12 months, the gap isn't capability. It's company structure. Some companies don't have a Director slot. Some have one and the incumbent will be there for a decade. At that point the campaign isn't development. It's a search.

Director of CX is a different job, not a bigger budget. The promotion is a campaign, not a reward. The four shifts are the durable answer to the question your VP is actually asking when they decide who gets the seat.