.png)
"Strategic" is what a function calls itself when it wants status. "Growth" is a word the business already funds.
Count the strategics in your organization.
Strategic recruiter. Strategic talent partner. Strategic HRBP. Strategic sourcing. Strategic workforce planning. Strategic talent advisory. There are conference tracks named after the word, certifications built around it, and an entire genre of LinkedIn post arguing that TA must finally become it.
Now notice who else uses the word about themselves. Finance does not have strategic accountants. Engineering does not staff strategic developers. Legal does not offer strategic contract review. Those functions describe what they do, and the strategic part is either evident or it is not.
"Strategic" is an adjective functions apply to themselves when they suspect they are not being taken seriously. That is why it appears so densely in HR and TA, and that is precisely why it does not work. It is a request for status wearing the costume of a description.
The problem with an unfalsifiable word
Here is the deeper issue. Nobody can disprove that you are strategic, which sounds like a benefit and is actually the whole problem.
A claim that cannot be tested cannot be believed either. When you tell an executive your function is becoming more strategic, you have given them nothing to evaluate, nothing to fund, and nothing to be wrong about. They will nod, because there is no counterargument to a word that means "important in a way I have not specified."
Compare that to a claim like "the Q3 revenue target depends on nine account executives being productive by August, and at our current conversion rate we will have five." That statement can be checked. It can be wrong. Somebody could look at it in September and say you overstated the risk. That exposure is exactly what makes it worth listening to.
Words that cannot fail also cannot persuade. "Strategic" is the safest possible thing to say about your function and therefore the least useful.
The business is not buying strategy
Walk into a leadership meeting and listen to the vocabulary that actually moves resources. Growth. Margin. Capacity. Speed. Risk. Retention. Cost. Every one of those words has a definition, an owner, a number attached, and a person who gets asked about it when it moves.
None of them is "strategic." Strategy is the process by which the business decides how to pursue those things. It is not itself a thing anyone buys.
So when TA asks to be strategic, it is asking to be admitted to a process. When TA speaks about growth, it is claiming partial ownership of an outcome. Those are very different requests, and only one of them is legible to the people making decisions.
Growth gives you somewhere concrete to stand
Consider two sentences that could be said by the same person in the same meeting about the same underlying situation.
"We need more investment in employer brand."
"Our ability to grow the field services division is currently constrained by our ability to attract technicians, and here is what that constraint is costing us per month."
The first is a budget request from a function. It will be ranked against other budget requests from other functions, on criteria you do not control, by people who are already skeptical of the category. The second is a diagnosis of a business problem that happens to sit in your domain. It invites a conversation about the constraint rather than a decision about your department.
Same person. Same request, ultimately. Completely different footing, because the second one stands on something the business already agreed was important before you walked in.
The translation, done properly
Most of TA's vocabulary describes internal process. Most of the business's vocabulary describes outcomes. Translation is not spin. It is saying the same true thing in the terms that let someone else act on it.
- Candidate experience is conversion. The experience matters because people abandon processes that frustrate them, and abandonment has a cost.
- Employer brand is talent market positioning. Not a look, not a tone. A defensible answer to why the right person chooses you over the alternative offer.
- Time to fill is delayed capacity. Nobody outside TA cares how long your process takes. They care when the work starts getting done.
- Quality of hire is productivity and ramp. How quickly does this person become capable, and how long do they stay capable.
- Talent pipeline is future capacity. What the business will be able to do in two quarters that it cannot do now.
- Hard-to-fill roles are growth constraints. That reframing alone changes who considers the problem theirs.
- Offer declines are competitive losses. You lost a head-to-head to a named alternative, which is a market result, not an administrative event.
- Early attrition is capacity leakage, and usually evidence that something was misrepresented upstream.
Use these long enough and something quietly shifts: people stop asking you for updates and start asking you questions.
Subscribe for more ideas and insights
Other functions have changed the frame before
There is precedent for this move, but the useful precedent is not the new title. It is the new accountability underneath it.
Site Reliability Engineering took work that had often been understood as operations and reframed reliability as an engineering problem with explicit measures, tradeoffs, and error budgets. Customer success took work that could have been filed as post-sale support and connected it directly to adoption, retention, and recurring revenue.
In both cases, the more consequential name reflected a more consequential way of managing the work. The function became easier for the rest of the business to understand because its contribution could be argued in outcomes rather than activity.
That is the part available to TA. Not a clever relabeling. A clearer claim about what the work protects or creates, backed by measures that can prove or disprove it.
But the word will not save you
Now the caveat, and it is the most important paragraph in this article.
Neither of those functions won anything by renaming. SRE got its status because error budgets made reliability arguable in numbers, and because SREs wrote software. Customer success got its status because churn and net revenue retention became board-level metrics that the function could visibly move. The name change was the last step, not the first, and in both cases the name was earned by a measurement discipline that arrived before it.
Which means "growth" is available to TA as a genuine reframe or as the next empty adjective, and nothing about the word itself determines which. If you start saying growth in meetings without being able to show a constraint, quantify a cost, or forecast a capacity gap, you will have accomplished exactly one thing: burning through a useful word the same way the field burned through "strategic," "business partner," and "talent advisor" before it.
The vocabulary is not the point. The vocabulary is what becomes available once the underlying work can support it. Say growth when you can show growth. Otherwise you are just asking for status in a new outfit, and executives have excellent pattern recognition for that.
Use the word where decisions get made
Assuming the substance is there, use the word on purpose in the places where the organization decides what your function is for.
In quarterly business reviews, where the framing of your function gets set for the next three months. In hiring plans, which should read as capacity plans. In business cases, where the constraint should appear before the request. In workforce planning, which is a growth-forecasting exercise mislabeled as an HR process. In your team's goals, so that the people doing the work understand what it is in service of. Eventually in titles, though that comes last and matters least.
Not artificially, and not as a verbal tic. Every use should be attached to something specific enough to be checked.
It will change your own decisions first
Here is the effect most people do not anticipate, and it may be the strongest argument for the whole exercise.
The moment TA genuinely understands itself as a growth function, its internal decisions get easier, because it finally has a criterion for making them. Which of these 47 requisitions matters most? A pure service function cannot answer that, because service functions treat all requests as equally valid, which is why TA so often works on everything at once and finishes nothing early. A growth function can answer it immediately: the ones the business's stated priorities actually depend on.
The same criterion resolves the other questions that usually get decided by whoever complains loudest. Which candidate segment deserves the most attention. Where the next dollar of budget goes. What to stop doing entirely, which is the hardest decision any function makes and impossible without a way to rank. What to fix upstream instead of compensating for downstream, forever.
Prioritization is not a personality trait. It is what becomes possible when you know what you are optimizing for. "Strategic" gives you nothing to optimize for. Growth does.
The test is whether the word changes decisions
The point of calling TA a growth function is not to win an argument about status. It is to give the function a better criterion for deciding what matters.
Which requisitions get scarce recruiter attention first? The ones tied most directly to the company's priorities. Which roles deserve deeper market research? The ones where a bad assumption threatens a growth commitment. Where should the next dollar go? Toward the constraint with the largest business consequence, not necessarily the loudest hiring manager.
That is what makes “growth” useful and “strategic” mostly decorative. One gives you a way to choose. The other gives you a way to describe yourself.
So use the word only when it earns its keep. Attach it to a forecast, a constraint, a cost, a capacity gap, or a decision the business actually has to make.
If nothing changes except the vocabulary, stop using it.
If the vocabulary changes what TA prioritizes, measures, challenges, and brings into the room, then the reframe is doing real work.
