An internal strategy team’s operating model is the practical system that turns “strategy” from episodic conversations into a repeatable enterprise capability. It defines what the team produces, how work is initiated and run, how stakeholders are engaged, and how decisions leave the room with ownership and follow-through. Without an operating model, a strategy team becomes reactive: it chases urgent requests, optimizes for polish, and substitutes motion for progress. With a sound operating model, leaders experience strategy as a force multiplier: fewer reruns, clearer trade-offs, and faster commitment.
This chapter covers four design choices. First, you will anchor the team to decision moments and the work products that make those moments productive. Second, you will define a small set of engagement models so business units and functions know what to expect. Third, you will establish decision rights, escalation paths, and “one team” rules that reduce politics and rework. Finally, you will decide what to centralize versus decentralize so the enterprise gets coherence without smothering local ownership.
4.1 Work Products and Decision Moments the Team Must Enable
Design from outcomes, not activities. Strategy teams often describe themselves by what they create—decks, market scans, models, updates. Those artifacts can be useful, but they are not the job. The job is enabling decisions that change direction, reallocate resources, or reshape capabilities. When you define your operating model around decision moments, you naturally prioritize what matters and stop doing work that cannot plausibly change a choice.
Decision moments: A decision moment is a specific point in time when a named leader or forum must choose among alternatives and commit the organization to a path. It has a decision owner, a decision forum, and a decision date. If any of those are missing, what you have is discussion, not a decision moment.
In most companies, the highest-leverage decision moments cluster into a small set of categories. Your operating model should explicitly cover each category, even if your involvement differs by case.
- Enterprise direction: where to play, how to win, and which capabilities the company will build or defend.
- Resource allocation: capital, talent, and management attention trade-offs across businesses and initiatives.
- Portfolio shaping: entries, exits, partnerships, acquisitions, or divestments that change the portfolio.
- Growth bets: new business builds and adjacency moves that require staged commitment under uncertainty.
- Operating model choices: decision rights, organizational structure, and core processes required to enable the strategy.
- Strategic risk responses: actions triggered by disruption, regulation, supply shocks, or major competitive shifts.
Once you name the decision moments, define the minimum work products required to make each moment decision-ready. Treat these work products as components in a decision package. The package should be consistent enough that leaders know where to find what they need, yet flexible enough to fit different problems.
Work product 1: Decision brief. One to two pages of plain-language framing: the decision question, why it matters now, what is in and out of scope, the owner, and the forum/date. This is where you prevent ambiguity from infecting everything downstream.
Work product 2: Options set. A small number of real alternative paths, not a list of initiatives. For each option, state the strategic logic, customer and capability implications, required investment, and key risks. Include a baseline (“continue as is”) so the cost of inaction is visible.
Work product 3: Comparable fact base. The minimum assumptions, definitions, and value drivers that make options comparable. Show ranges for the handful of uncertainties that matter most, and be explicit about what evidence would change your view.
Work product 4: Alignment map. A deliberate plan for who must be aligned, what their likely concerns are, and what conversations must happen before the forum. Alignment is not soft work; it is the mechanism that prevents reruns.
Work product 5: Decision-to-execution handoff. A crisp summary of what was decided, what will change, who owns what, what resources are committed, and how progress will be reviewed. If the handoff is weak, the organization will interpret the decision as optional.
Define “decision-ready” in operational terms so you can move fast without lowering the bar. Keep the standard simple enough to apply in a short review.
- Clarity: the decision is written as a choice, with owner, forum, and date.
- Alternatives: at least two credible options plus a baseline, each with implications and risks.
- Comparability: common definitions and assumptions, with the most sensitive drivers highlighted.
- Trade-offs: explicit statement of what will be stopped, delayed, or deprioritized.
- Pre-wiring: key stakeholders engaged, and unresolved disagreements surfaced explicitly.
- Handoff: owner, first actions, cadence, and early indicators agreed in principle.
Now connect decision moments to cadence. Strategy teams get crushed by “last-minute” requests because the enterprise does not see decisions coming. Maintain a forward-looking decision agenda: a 90-day view for capacity planning and a 12-month view to anticipate the planning cycle, portfolio reviews, and board-relevant decisions. The agenda is a management tool that helps you start early, sequence work, and protect deep-work capacity.
Not all strategy work is decision work. Some work improves strategic readiness, such as refreshing a competitive fact base or clarifying capability maturity. These are valuable only when they are time-boxed and explicitly connected to upcoming decision moments. If you cannot name the decision moment, treat the work as optional and deprioritize it when capacity is tight.
4.2 Engagement Models with Business Units and Functions
With decision moments defined, the next choice is how the strategy team engages with the rest of the organization. Engagement is where operating models either create leverage or create resentment. If the team behaves like a command center, business units will resist and withhold information. If it behaves like a service bureau, it will be overloaded and lose influence. The answer is to define a small set of engagement models, make them explicit, and choose among them based on the decision’s scope, stakes, and ownership.
Most companies need three engagement models.
Model A: Challenger and facilitator. The business or function owns the analysis and the recommendation. Strategy designs the decision journey, ensures comparability, challenges assumptions, and facilitates trade-offs. Use this model when a P&L or functional leader owns the decision, local teams can do the heavy lifting, and the primary enterprise need is quality control and coherence.
Model B: Co-creation partner. Strategy and the business/function jointly build the options and recommendation. Use this model when the decision is high stakes, time constrained, or capability intensive, or when the work requires tight integration across functions. Co-creation is also the best vehicle for building local capability, because the team transfers methods and standards through joint work.
Model C: Enterprise orchestrator. Strategy runs the end-to-end process for decisions owned by the CEO or an enterprise forum. It coordinates inputs, synthesizes options, manages pre-wiring, and ensures a clean handoff. Use this model when decisions cut across businesses, require significant reallocation, or involve shared platforms and enterprise capabilities.
Make the models concrete by defining roles that apply in every engagement.
- Decision owner: accountable for making the choice and owning outcomes.
- Work lead: accountable for running the workplan and producing the decision package.
- Content owners: accountable for key inputs such as market insight, operational feasibility, and technology implications.
- Approvers: executives or forums that must sign off on funding and priorities.
Then set engagement norms that reduce friction and rework.
Early question lock: confirm the decision question, option boundaries, and required evidence in the first week.
One assumptions baseline: agree on “official” assumptions for comparability; treat alternates as scenarios, not as competing spreadsheets.
No surprises: surface major concerns before the forum; if someone plans to object, it should be known and addressed.
Line ownership: even in co-creation, the line leader owns the recommendation in the room and the follow-through afterward.
For major efforts, use a lightweight engagement agreement that can be agreed quickly and referenced under pressure.
- Purpose: what decision will be made and what success looks like.
- Roles: decision owner, work lead, and key contributors.
- Outputs: required work products and the decision-ready standard.
- Cadence: working meetings and pre-wiring conversations, with dates.
- Constraints: nonnegotiables, risks, and resource limits.
Engagement design also determines staffing. Challenger/facilitator work requires senior judgment and the ability to push without damaging relationships. Co-creation work requires analytic horsepower and crisp synthesis. Orchestration work requires stakeholder management and the confidence to drive closure. If you staff all models with one profile, you will either be too junior to influence or too senior to scale.
Finally, build a two-speed system. Some decisions require rapid cycles, such as responses to competitive moves or time-sensitive partnerships. Others require deeper cycles, such as enterprise direction refreshes or major platform investments. Protect capacity for both by reserving a core block tied to the decision agenda and a smaller surge block for urgent executive needs. Without explicit protection, urgent work will consume everything.
4.3 Decision Rights, Escalation Paths, and “One Team” Rules
Trade-offs create tension, and tension becomes politics when decision rights are unclear. A good operating model makes decision rights explicit and treats escalation as normal enterprise management, not as a personal conflict. The objective is speed with legitimacy: disagreements are heard, but they are resolved in the right forum and at the right altitude.
Use a simple decision-rights logic that leaders can remember.
Recommend: who is accountable for assembling options and bringing a point of view.
Decide: who has the authority to allocate resources and set direction.
Commit: who must change priorities, budgets, or behavior for the decision to be real.
Then define escalation paths with triggers, destination forums, and payload expectations.
- Trigger: the team cannot agree on the decision question, the assumptions that drive economics, the option set, or the resource trade-offs.
- Destination: the smallest forum that can resolve the conflict, such as the executive sponsor, a capital allocation committee, or the CEO staff meeting.
- Payload: a crisp summary of the disagreement, the implications, the recommendation, and the decision required.
Escalation should be framed as a choice, not a complaint. Instead of “we disagree,” bring the fork in the road: “Option 1 protects margin but slows growth; Option 2 accelerates growth but requires investment and operating change. Which risk do we accept, and what will we stop to fund the choice?” This keeps the enterprise moving even when evidence is imperfect.
Decision rights reduce ambiguity, but trust is built through “one team” rules: working agreements that prevent recurring rework and back-channel lobbying. Keep them few, concrete, and enforce them consistently.
Rule 1: One fact base. Enterprise decisions use shared definitions and baseline assumptions. Disagreements appear as explicit scenarios, not hidden edits.
Rule 2: Debate options, not intent. Challenge assumptions and implications without questioning motives. The strategy team should actively solicit counterarguments to avoid groupthink.
Rule 3: Pre-wire before the forum. Major concerns are surfaced early; the decision meeting is for choice and commitment, not ambush.
Rule 4: Disagree and commit. After the decision, leaders align their teams and stop relitigating. If new evidence emerges, reopen the decision explicitly.
Rule 5: No decision without a handoff. Every decision leaves the room with an accountable owner, initial actions, a cadence, and measures of adoption and value.
Reinforce these rules with a small number of mechanisms. Require decision packages to include a visible “key assumptions” section. Keep a decision log that records what was decided, why, and the next checkpoints. Establish a standard pre-brief practice where the decision owner and strategy lead align with the CFO and COO on feasibility and resource implications before enterprise forums. These mechanisms reduce surprises and speed convergence.
Also define confidentiality norms. Strategy teams work with early hypotheses and sensitive topics. If partial drafts circulate broadly, leaders will stop engaging early and the enterprise will lose the benefits of iterative problem solving. Agree that early drafts stay within a small working group, broader sharing happens once options are mature, and final decisions are communicated through agreed leadership channels.
4.4 What to Centralize vs. Decentralize
The final operating model choice is structural: what should sit in a central strategy team versus what should sit in business units and functions. The right answer balances coherence and ownership. Centralize too much and you create dependency and resistance. Decentralize too much and you create fragmentation and weak trade-offs.
A useful principle is to centralize what requires enterprise comparability and cross-unit arbitration, and decentralize what requires proximity to customers and rapid iteration. Then connect the system with shared standards, integrated cadence, and talent flow.
Centralize what creates enterprise leverage. These activities benefit from a single enterprise lens and consistent standards.
- Enterprise narrative and priorities: coherent direction, explicit choices, and a clear “stop list.”
- Portfolio and allocation conventions: common value drivers, investment thresholds, and decision package requirements.
- Enterprise decision orchestration: end-to-end processes for cross-business choices, including pre-wiring and handoffs.
- Planning design and integration: a cycle that forces trade-offs and makes unit plans comparable.
- Strategic standards: decision-ready criteria, option framing expectations, and a shared language for uncertainty.
Decentralize what requires local ownership. These activities work best close to operators who will execute.
- Market and customer sensing: ongoing insight and competitor monitoring tied to commercial action.
- Business unit strategy detail: segment choices, offers, channels, and local operating moves within guardrails.
- Functional delivery planning: detailed capability build plans owned by functions with resources and accountability.
- Program execution: initiative management, dependency resolution, and day-to-day delivery discipline.
The connective tissue is what makes this workable.
Shared standards: keep them few and enforce them—common definitions, a small set of economic conventions, and a consistent decision memo structure for major requests.
Integrated cadence: link enterprise priorities to unit plans through a predictable rhythm so reallocation and trade-offs are explicit, not negotiated ad hoc.
Talent flow: build rotations between the center and the businesses to keep the center grounded and to raise strategic capability in the lines.
Two structural mistakes are common. The first is centralizing analysis that should be owned locally. When the center does all the thinking, leaders may accept the recommendation but fail to internalize the trade-offs, which weakens execution. Prefer to centralize synthesis and challenge while ensuring businesses own key inputs and assumptions. The second mistake is decentralizing without comparability. If each unit defines metrics and economics differently, the enterprise cannot arbitrate resources credibly, and the CEO ends up making trade-offs based on relationships instead of evidence.
When unsure, apply the single-answer test: would the enterprise benefit from one consistent answer? If yes, centralize the standard or the decision. If no, decentralize within guardrails and focus the center on integration and challenge.
Treat the operating model as a living contract. Rehearse it in real work, tune it after major decisions, and reinforce it in hiring and performance reviews. Consistency, not novelty, is what makes leaders trust the process.
Operating model design is not a one-time exercise. As line capability matures, shift the center from co-creation toward orchestration and challenge. Revisit centralization choices annually based on where decisions stall, where coherence breaks, and where local teams are ready to own more. When the operating model evolves deliberately, the strategy function stays valuable as the enterprise changes around it.
