Everyone agrees support must change. I have yet to find two people who agree on what it should become.
Every other function in the company has a strategic definition of its role. Sales owns pipeline and bookings. Product owns the roadmap and what gets built. Marketing owns brand and messaging. They can state in a sentence why it exists and how it moves the business forward. Support can describe the work it does but cannot connect that to the business impact its work drives. And a function that cannot define its strategic role does not get to have a strategic future—it gets managed as a cost.
Two questions
I have started asking support leaders a simple question: what is the role of support? The answers scatter, but they cluster around one idea—resolve customer issues quickly and efficiently.
Then I ask a second question: what does executive leadership think the role of support is? The answers are remarkably consistent—keep customers happy, and don’t cost too much.
These two answers are revealing.
Neither definition is strategic. One describes efficient issue resolution; the other describes contained cost and adequate satisfaction. Both describe a function to be managed, not a capability to be invested in. And notice what is missing from both: any connection to whether customers renew, expand, adopt, or consume—the outcomes the business actually grows on. Satisfaction is desirable. It is not a promise of retention, nor a reliable driver of growth.
When the function and the people who fund it both define the role in tactical terms, only one future is possible: incremental efficiency. Do the same work, measure the same metrics, with fewer people. That is not a move toward strategic indispensability—it is a short-term decision with a long-term cost. Neglected capacity. Squandered expertise. A function optimized for this quarter’s margin while the growth it could have driven goes unclaimed.
Whose decision is this?
Current definitions of support’s role are tactical. But who gets to decide whether support has a strategic role?
Attempts from the bottom up hit a wall. A support leader who sees the strategic potential has neither the agency nor the capacity to act on it. The existing workload consumes the team. There is no room to redirect toward higher-value work, and no budget to add it, because every resource is committed to the case volume the business already expects. The vision dies in the gap between seeing it and being allowed—and resourced—to build it.
It does not come from the top down either. Executive leadership has no reason to imagine support as strategic, because support has never shown them it could be. You cannot have an epiphany about a capability you have only ever seen used to close tickets. So executives keep defining the role the way they always have—keep customers happy, keep costs down—and the definition becomes self-fulfilling.
So the ownership vacuum persists by default. Not because anyone decided support should be tactical forever, but because no one has claimed the authority to define it as anything else. Absent that ownership, efficiency fills the space, because efficiency is the only ambition a tactical role can hold.
The fix isn’t process — it’s purpose
The shift to a strategic role will not come from better case management, smarter escalation, tighter backlog control, knowledge management or improved deflection with good-enough CSAT. Those are refinements to the tactical role. They make the cage support is trapped in more comfortable; they do not open the door and let support strive to reach its full strategic potential.
The future of support begins with a fundamental reframing of its purpose—a clear, defensible definition of what this function is actually for. And here we run into the elephant in the room.
Meet the elephant
“Support.” The word itself is the obstacle.
It comes with predefined perceptions for everyone: reactive, tactical, fix-what’s-broken, the place you go when something fails. The name is the cage that keeps support from running free. As long as the conversation is about “support,” the imagination is bounded by what that word has always meant, and no redefinition can escape its bars.
So stop saying it. To define the future, stop talking about support at all.
Not because the function doesn’t matter—it matters more than the business currently understands. Stop saying the word because the word hides the capability. Describe the capability instead, with no name attached, and watch what an executive sees:
A team with deep technical expertise in how the product actually works. Intimate, current knowledge of how customers are really using it—and where they are getting stuck. The ability to see friction before it becomes failure, and to engage before a customer stalls. The standing to drive the product improvements customers actually care about, and to guide customers to the outcomes they paid for and the consumption that grows the account.
Describe that and you have described something an executive recognizes immediately as strategic. Nothing in that description is aspirational—it is what the best support teams already do, when the work allows. The capability is real, but it is the label that limits the perception of what that capability can make possible.
The first step
The capability of support is not in doubt. What is missing is a definition of support’s strategic purpose.
Until that definition exists, support will be held within a cage fulfilling a tactical role: doing more of the same, more efficiently, with fewer resources. That is the future support gets by default.
The other future has to be defined and named. Not in the language of support—in the language of the outcomes the business is trying to reach.
This is a daunting task. The ONE MOVE below won’t finish it—but it’s a starting point, and a way to begin building consensus about where support goes next.
ONE MOVE
One concrete step. No budget. No permission. Do it this week.
Write a single sentence describing what your team does—without using the word “support,” and without naming a single activity (no “resolve,” “respond,” “close,” “deflect”). Describe only the business outcomes your team’s capability makes possible. If the sentence sounds strategic, you have found the definition worth fighting for. If it still sounds tactical, you have found exactly why the role hasn’t changed.
Support Leadership, Unfiltered is a series helping support leaders transition from tactical execution to strategic indispensability. For the complete framework: The Support Attribution Framework. For all Support Leadership frameworks and playbooks, visit www.servicexrg.com