The Difference Between Operational and Strategic Work (and Why It Matters)

Operational work is the set of repeatable activities that produce the company's current output. Strategic work is the set of choices that change what the company does, who it serves, or how it competes. The two are not a spectrum. They are different categories of activity with different time horizons, different decision criteria, and different definitions of success. Most operations leaders spend 90% of their hours on the first and call a portion of it the second. The confusion is expensive.

We walk into growth companies and find the Head of Ops doing 95% execution, 5% direction. The CEO wonders why there is no strategy. There is, technically. It is just compressed into five minutes a week while someone else owns the rest.

What counts as operational work?

Operational work is the recurring activity required to produce the company's current output at the current quality and cost. It is the set of tasks, handoffs, and decisions that keep revenue flowing and customers served. If stopping the work would interrupt cash flow or delivery inside 90 days, it is operational.

Examples that are clearly operational: processing an order, running payroll, closing the books, responding to a support ticket, renewing a contract, onboarding a new hire, fixing a broken integration, running the weekly ops review. All of these repeat. All of them have a known output. All of them have defined success criteria that do not require debate.

Operational work is not lesser work. Bain & Company's 2024 research on operational excellence found that companies in the top quartile of execution quality delivered 2.3x the total shareholder return of bottom-quartile peers over a ten-year window. Execution compounds. A team that has run billing cleanly for three years has more trust and cleaner data than one that has rebuilt the billing system twice. Operational depth is a competitive asset, even if nobody writes board slides about it.

What makes work operational is not how important it is. It is the nature of the decision. Operational decisions are reversible, repeatable, and scoped within an existing playbook. The question is "how well do we run the thing we already run?"

What actually counts as strategic work?

Strategic work is the set of choices that change what the company does, who it serves, how it competes, or what capabilities it builds. Michael Porter's 1996 Harvard Business Review essay "What Is Strategy?" defined it as the creation of a unique, defensible market position through a coherent set of activities that fit together. Roger Martin's updated framing calls strategy "an integrated set of choices that uniquely positions the firm in its industry to create sustainable advantage."

Strategic work is rare, slow, and hard to reverse. Picking which customer segment to stop serving is strategic. Deciding to build an in-house capability rather than outsource it is strategic. Choosing a pricing architecture that changes which deals you win is strategic. None of these repeat weekly. Most of them commit the company to a path for two to five years.

Roger Martin, former Dean of Rotman School of Management, makes a sharper point. Strategy is not a plan, a vision statement, or a list of priorities. It is a set of explicit choices with explicit tradeoffs. If your "strategy" does not have a list of things you are choosing not to do, it is not strategy. It is ambition.

Gartner's 2024 survey of 437 senior operations leaders found that 68% said they were "responsible for strategy" in their function. When asked to list the five most recent strategic choices they had made, 41% could not produce a list that met Martin's definition. They listed operational improvements like faster close times or better vendor pricing and called that strategy.

How do the two differ on decision criteria?

Operational and strategic work differ on five decision criteria: time horizon, reversibility, optionality, resource commitment, and second-order effects. A decision that scores operationally on all five is operational. A decision that scores strategically on three or more is strategic. Mixed scores indicate the category itself is wrong, which is where most confusion starts.

The framework is useful because people misread each variable in isolation. "This will take eight months" feels strategic because it is long. It is operational if the outcome is to run an existing process better. "This is a $2M investment" feels strategic because the number is big. It is operational if the investment sits inside the current budget and does not change what the company is capable of doing.

The test that holds up is the reversibility score combined with the optionality score. A decision that is hard to reverse and that creates or kills future options is strategic. Everything else is operational, regardless of its cost or complexity.

BCG's 2023 analysis of 1,400 corporate decisions found the same misclassification. Executives consistently labeled high-effort operational work as strategic and low-effort strategic work (a pricing change, a channel exit, a segment cut) as "just an ops decision." The mislabeling pulled attention away from the choices that actually mattered for long-term position.

When does operational work become strategic?

Operational work becomes strategic when the outcome of a single decision will change what the company is capable of doing afterward. A billing system replacement is operational if the new system runs the same billing model the old one did. It is strategic if it is the precondition for a pricing change that shifts what customers you can serve.

The crossover point is usually invisible until someone draws it. A Head of Ops at a mid-market SaaS company might spend a quarter on CRM consolidation and call it operational. If the consolidation is the unlock for a product-led growth motion that the company has never run before, the real decision is strategic. The CRM work is the execution path. The strategic question is whether to pursue PLG at all.

This is why boundary cases eat operations leaders. The work looks operational. The decision about whether to do the work is strategic. Owning the execution without owning the decision leads to burnout. Owning the decision without the capacity to execute it leads to empty slide decks.

McKinsey's 2024 report on the COO role identified this pattern as the single largest driver of COO role dissatisfaction. COOs who reported clear separation between operational ownership and strategic decision rights had 2.8x higher engagement than those operating in ambiguous territory.

Why do leaders mislabel their work?

Leaders mislabel operational work as strategic for three reasons. The first is that "strategic" is a status word. Calling a project strategic signals that it matters and that the person doing it is senior. Operational, by contrast, sounds like chores. Status hygiene leads people to rebrand their calendar.

The second is that the word strategic has quietly shifted in business usage to mean "important to me" rather than "long-term and irreversible." A weekly forecasting meeting the CFO personally runs becomes "the strategic finance review." The meeting is operational. The CFO's attention makes it feel different to the people attending, but the content of the decisions has not changed.

The third is that the absence of real strategic work in most weeks creates a vacuum. If an executive goes a quarter without making a genuinely strategic decision, the pressure to narrate their contribution as strategic grows. Operational improvements get relabeled. A vendor consolidation becomes "strategic procurement transformation." A faster close becomes "the strategic finance modernization program." The work is the same. The name gets better.

Harvard Business Review's 2023 analysis of executive time-use studies, built on data from 27 CEOs tracked for 13 quarters, found that 72% of time logged as "strategic" failed the reversibility and optionality tests. The work was important. It was not strategic. The researchers called the gap a leading indicator of strategic drift.

The hybrid-role trap

The hybrid role trap is a pattern where a single leader is assigned both operational execution and strategic direction for the same function, with no time or structural protection for the strategic half. The result is that strategic work gets crowded out by operational urgency every time, because operational problems have immediate consequences and strategic ones do not.

The pattern is most common in companies between $30M and $200M in revenue, where the Head of Ops is both the COO in waiting and the senior individual contributor who fixes broken things. The role is sold as "operational leadership with strategic scope." In practice, it is 50 hours a week of execution and one strategic conversation per quarter that ends without decisions because nobody did the prep work.

The structural fix is usually one hire, not a reorganization. A senior operations manager or director owns first-line execution, which frees the Head of Ops to spend the intended 30% of their time on strategic work. Companies that resist the hire usually do so for budget reasons, then pay more in turnover when the Head of Ops leaves 18 months later because the strategic work they were hired to do never happened.

How to audit what you actually spend time on

A time allocation audit measures what percentage of your working hours map to operational execution versus strategic work. The method is four steps: a calendar pull, a task categorization pass, a two-week time study, and a reconciliation with your job description. Most leaders find a 30 to 50 point gap between what they think they do and what they actually do.

We ran this audit with a VP of Operations at a 140-person healthcare services company last year. Her role charter specified 60% strategic, 40% operational. The calendar showed 18% strategic, 82% operational. The two-week time study showed 11% strategic, 89% operational. The gap was not a personal failure. It was a structural one. The function had no ops manager below her. She was the escalation point for everything.

The audit is uncomfortable, which is why most people do not run it. It forces a conversation about whether the role is actually what the hiring conversation described. It also gives the leader the data to argue for the hire, the budget, or the scope change that fixes the problem.

Strategy-washing and how to spot it

Strategy-washing is the practice of rebranding operational work as strategic to make it sound more important. The work itself is useful. The relabeling is misleading, because it obscures the absence of actual strategic choice-making and makes it harder for the organization to notice that nobody is doing the long-term work.

A few tells. Any project with "transformation" in the title that is actually a system upgrade. Any initiative labeled "strategic" that has a defined scope, timeline, and success criteria at kickoff (real strategic work has none of those at kickoff). Any program owned by a steering committee that meets monthly (strategic work usually has a single owner, not a committee).

Roger Martin has written that the word strategy is now used to mean "aspiration." A company announces its strategy as "to be the leading provider of X." That is not a strategy. It is a statement of ambition. A strategy says: we will serve these customers and not those, with this value proposition and not that, using these capabilities and not those, at this price point and not others. If the statement has no "not," it is not strategic.

The same test applies at the function level. An operations strategy that says "run operations excellently" is not a strategy. One that says "we will centralize service delivery at the expense of regional responsiveness, accepting a 48-hour SLA where competitors offer 24" is a strategy. The second version will get pushback from the regions. The first will get unanimous approval and mean nothing.

What the best COOs do differently

The best COOs draw an explicit line between operational ownership and strategic decision rights, and protect the second category with structural rather than aspirational defenses. Three patterns show up repeatedly in the McKinsey and HBR research on high-performing COOs.

The first is a named number two. The deputy owns first-line execution, which frees the COO to spend a planned 30 to 40% of their time on strategic work. Without the number two, the math does not work.

The second is separate reviews. The weekly ops review covers current-quarter execution. The monthly strategic review covers choices that will affect the 12-to-36-month horizon. Mix them, and the urgent drives out the important in every single meeting.

The third is a published time allocation. A COO who commits publicly that 30% of her time goes to strategic work creates accountability. When a week drifts to 10%, the gap is visible. Most executives resist this level of transparency because it exposes how little strategic work actually happens.

Related reading: how the best COOs think about operations covers the decision patterns that separate execution-first COOs from strategy-first ones. Aligning operations strategy with business goals goes deeper on tying the strategic half to the CEO's plan. If your calendar is the problem, how to build an operations roadmap shows how to protect capacity for both kinds of work.

Key takeaways for operations leaders

Operational and strategic work are different categories, not points on a spectrum. Operational work is repeatable and reversible. Strategic work is rare, hard to reverse, and creates or kills future options. Both matter. Confusing them is what produces burnt-out ops leaders and under-strategized companies.

Use the five-criteria test. Time horizon, reversibility, optionality, resource commitment, second-order effects. A decision that scores strategic on three or more is strategic. Everything else is operational, regardless of how expensive or complex it looks.

Audit what you actually spend time on. Pull 90 days of calendar data. Run a two-week time study. Compare the result to your role charter. The gap is the argument for the hire, the scope change, or the conversation you have been avoiding.

Watch for strategy-washing in yourself. If a project has scope, timeline, and success criteria at kickoff, it is operational. Real strategic work has none of those at kickoff. If the word strategic is doing status work in your vocabulary, stop using it. Call the operational work operational. That does not shrink the work. It clarifies what is missing.

Protect strategic work structurally. One deputy, one separate review cadence, one published time allocation. Aspirational protection (everyone agrees the COO should spend time on strategy) fails every quarter. Structural protection survives the quarter.