Your CS Transformation Needs a Shorter Plan, Not a Bigger One

By Kristen Hayer

Almost every CS transformation plan I see starts out sensible and ends up too long. A leader decides the program needs work, and over a few weeks the plan picks up new segments, new journeys, a new platform, a training initiative, and a fresh set of metrics. Six months later it is beautifully documented and almost none of it has happened. Nobody on the team was slacking; the plan simply tried to fix everything at the same time. Transformations get done when the plan is short and the order is clear.

Why Long Plans Stall

In a struggling program everything feels urgent, so everything goes on the list, and every item on the list gets an owner and a deadline. The trouble is that the items depend on each other. You can’t build a good journey until you know who your customers are, and training won’t stick until the journey exists. Picture a plan with a dozen initiatives and no indication of which one starts Monday. People will start with whatever interests them most, which usually isn’t what the program needs most. Meanwhile the executives start asking where the results are, and the first thing they hear is a status update on six workstreams. That is usually the point where the transformation gets called a failure, even though the real problem was that nobody decided what came first.

Do the Work in Order

Here is the order I’d follow. Start with segmentation, because you have to know which customers you serve and what each one is worth. Then build the journeys, since a journey only makes sense for a defined group of customers. Next come goals and CSM ratios, which tell you how many people you need to deliver those journeys. Training goes last, because people can only apply new skills to a process that already exists. I’ve written about most of these steps recently, in the posts on segmentation, CSM ratios, and building the foundation before you train. Those posts belong together, because each step feeds the next, and if you skip one you’ll end up redoing it later.

Pick One Thing

Choose one priority for the quarter and tell everyone what is waiting. Most leaders push back on this, because telling a good idea “not yet” feels like falling behind. In my experience it works the other way. If your team and your executives both know this quarter is about segmentation, nobody expects a new health score to show up alongside it, and the people doing the work get to finish. Say it plainly in the kickoff and again in every update.

The plan itself should fit on one page: this quarter’s priority, who owns it, what comes next, and what waits. If it needs a second page, it probably has two priorities.

Bring in the Rest of the Company

A transformation that only involves the CS team is going to stall, because customers deal with the whole company. When I run journey mapping for a client, we build one journey completely before starting the next, usually beginning with the highest-touch segment. After that, we look at how each of the other segments differs. Sales, support, product, finance, and operations all join the work, because each of them hands something to the CS team or relies on what the team does. Working through one journey at a time keeps a two-day session from turning into a free-for-all, and a first draft exists about a week later. That is when the useful arguments start.

Decide How You’ll Know It’s Working

Pick two or three checkpoints for the quarter and skip the dashboard. For a segmentation quarter, mine would be that every customer sits in a segment, finance has reviewed the model, and each member of the team can describe their segment’s journey in one sentence. If they can’t do that last one, the work isn’t finished, however good the spreadsheet looks. It’s also common for this work to show a team what it isn’t ready for yet, and you would rather find that out before you buy tools or build training.

Boring Is Fine

The best transformations I’ve watched felt almost boring from the inside. One thing was in progress, everyone knew what came next, and nobody was scrambling. If your current plan is so long that no one can summarize it, find the one thing that has to happen first and start there.

Want to build your foundation first but don’t know where to start? The Success League can help. Training sticks when your program is ready for it. Our consulting team helps B2B CS leaders nail segmentation, journey mapping, goal setting, and process design. Hundreds of leaders have done it with us. Reach out to us today or visit TheSuccessLeague.io to view our full offerings.

Kristen Hayer - Kristen is the Founder & CEO of The Success League, a global, customer-focused consulting and training firm. Kristen’s background includes leading award-winning sales, marketing, and customer success teams in early and growth-stage tech companies. She is the host of several podcasts on CS and leadership, and has written over 100 articles on the field of customer success. The book she recently co-authored with 5 other CS thought leaders - The Customer Success Talent Playbook - hit #1 on Amazon in 5 categories. Kristen received her MBA from the University of Washington and splits her time between San Diego and San Felipe, Mexico.

Next
Next

Black Friday: 25% off CSM Training!