A strategy function becomes overhead when its work ends at the slide. It becomes an engine when its work ends in a decision that gets executed.
That distinction matters in any company trying to grow or transform quickly: private equity backed, venture backed, founder led, or public and under pressure to change. Call it a value creation plan, a growth agenda, a transformation roadmap, or a board mandate: the underlying work is the same. A strategy team that only analyzes is a cost. A strategy team that drives decisions is a lever.
Why the “cost center” read is understandable
A strategy function is easy to undervalue because its output is diffuse. A sales leader’s contribution shows up in bookings. A CFO’s shows up in the reporting. Strategy’s contribution often shows up as decisions other people execute, which means the credit lands elsewhere and the cost lands squarely on the strategy line. When a plan is under pressure, or revenue is down, and leadership is looking for margin, the strategy function is an easy target precisely because its value can be hard to attribute.
Cutting it is often a mistake, and the function frequently invites it by operating too similarly to an external consultancy (producing studies on request, staying one step removed from the decisions, and never quite owning a result). That is often the mandate it was given. But the mandate only starts the story; the hire decides how it ends.
What the function looks like when it is an engine
A strategy function built as a value creation engine completes initiatives that tie directly to the growth or transformation thesis, whatever form that thesis takes.
It owns the value creation roadmap, not just individual analyses. Rather than answering discrete questions as they come up, it holds the full picture of where the next increment of value will come from. It keeps that picture current as reality shifts and drives the sequencing decisions that determine whether the levers get pulled in time.
It pressure tests the thesis against what is real. The best strategy teams are not closer to every customer, process, or number than the operators are. Their value is that they can see across those inputs, pressure test the plan against reality, and surface tradeoffs that individual functions are not positioned to see or resolve on their own.
It orchestrates the initiatives that cross functions. The highest value initiatives in a company rarely sit inside one function. A pricing overhaul, a go-to-market shift, an acquisition integration all cut across the org. Strategy is often the natural orchestrator of work no single function is positioned to drive. The best functions keep the initiative moving, make the tradeoffs visible, and make sure accountability lands with the right operating owner. Done well, this is orchestration, not empire building. Strategy keeps the work moving, resolves the tradeoffs, and hands off cleanly to the operators who own the P&L.
In practice, this is the team that does not just identify a transformational M&A pipeline. It helps drive the deals and then leads the integrations, codifying the playbook along the way. It is also, in the strongest versions, a feeder of talent into the business: a place where smart people learn the company and then are deployed, over time, into functional and P&L roles carrying that strategic orientation with them.
The hire that determines which one you get
Whether a strategy function becomes overhead or an engine is decided largely by the leader you put at the top of it. A brilliant consulting leader whose career has rewarded analysis more than operating outcomes may rebuild the advisory model they know. The leaders who build an engine instead are the ones who instinctively work backward from the decision and the outcome, not forward from an interesting question.
That instinct does not require a particular resume. Some of the best strategy leaders have spent the bulk of their career in consulting firms; others have come up through high growth or transformation organizations, owning implementation of initiatives they helped design. The screen is not the credential, it is the orientation. Does this person treat the analysis as the finish line, or as the setup for a decision they intend to see executed? Do they anticipate where execution will meet resistance? Is their plan built to bend when reality shifts, as it always does? Those questions predict far more than where they trained or what their last title was.
This reframes the strategy hire entirely. It is not a support role to be filled economically. It is one of the higher leverage hires a growing or transforming company makes, because the person running it ultimately determines whether the function drives recommendations toward implementation, or just presents analysis.
A strategy function is overhead or an engine depending on who runs it. That is not a budget decision. It is a hiring decision, and it is worth treating like one.