Enterprise Strategist

Enterprise Strategist

When to Use

• Set or refresh corporate strategy — where to play, how to win, strategic pillars
• Define business unit (BU) strategy aligned to corporate intent and P&L accountability
• Prioritize the enterprise portfolio — invest, sustain, harvest, divest
• Build a strategic roadmap and initiative backlog tied to outcomes, not features
• Evaluate growth and diversification options (organic, partnerships, M&A themes)
• Frame competitive and market positioning at enterprise or multi-BU scale
• Design target operating model and capability implications of strategy
• Plan enterprise transformation — sequencing, dependencies, value waves
• Frame M&A, partnerships, or divestitures at strategy layer (thesis, synergies, boundaries)
• Run scenario planning and articulate strategic trade-offs for leadership
• Align initiatives with board and executive priorities; define strategic KPI trees
• Prepare board or exec strategy narratives, decision memos, and option papers

When NOT to Use

• User stories, sprint backlog, or feature-level roadmap → business-analyst, technical-program-manager
• Multi-team delivery tracking, RAID, launch readiness → technical-program-manager
• Hypothesis workshops and consulting engagement framing only → business-consultant
• Detailed financial models, DCF, or close calendars → financial-analyst, compute-accounting-manager
• Contract redlines, MSAs, or legal risk → commercial-counsel
• M&A closing matrix, signing, or funds flow → transaction-manager
• Live deal valuation, IC materials, negotiation → transaction-principal
• System integration ADRs, C4, or NFR targets → senior-system-architecture
• Cloud landing zones, CCoE, or EA commits → enterprise-cloud-architect, cloud-architect
• Hands-on cloud service configuration → cloud-engineer
• Security program, controls, or IR → cybersecurity, enterprise-security-architect
• Marketing campaigns, brand, or demand gen → communication-lead (comms cadence only)
• Single-product roadmap and feature prioritization → business-analyst

Related skills

Core Workflows

1. Strategy framing and scope

Clarify level (corporate vs BU), time horizon, constraints, and decision audience.

See `references/enterprise_strategist_scope.md`.

2. Portfolio prioritization

Map businesses and initiatives; apply invest/sustain/harvest/divest and capacity limits.

See `references/corporate_portfolio_and_prioritization.md`.

3. Growth, diversification, and market position

Generate and compare strategic options; position vs competitors at enterprise scale.

See `references/growth_diversification_and_market_position.md`.

4. Operating model and capabilities

Translate strategy into target operating model, capability gaps, and org implications.

See `references/operating_model_and_capability_strategy.md`.

5. Corporate development framing

Articulate M&A/partnership/divestiture theses, synergy logic, and integration boundaries (not legal DD).

See `references/ma_partnerships_and_corporate_development.md`.

6. Scenarios, alignment, and metrics

Build scenarios, exec/board alignment, and strategic KPI trees linked to initiatives.

See `references/scenario_planning_and_executive_alignment.md`.

When to load references

• Scope, outputs, boundaries → references/enterprise_strategist_scope.md
• Portfolio and prioritization → references/corporate_portfolio_and_prioritization.md
• Growth, diversification, positioning → references/growth_diversification_and_market_position.md
• Operating model and capabilities → references/operating_model_and_capability_strategy.md
• M&A and partnerships (strategy) → references/ma_partnerships_and_corporate_development.md
• Scenarios, board, KPI trees → references/scenario_planning_and_executive_alignment.md

Corporate portfolio and prioritization

Table of contents

1. Portfolio mapping 2. Prioritization lenses 3. Invest sustain harvest divest 4. Initiative prioritization 5. Capital and capacity allocation 6. Common pitfalls

Portfolio mapping

Build a business portfolio view (not only IT projects):

Plot each cell on at least two axes—for example:

• Market attractiveness vs competitive position (classic portfolio matrix)
• Strategic fit vs economic performance
• Option value vs execution risk (for early bets)

Document data sources and vintage; stale market data invalidates portfolio calls.

Prioritization lenses

Use multiple lenses; leadership should see where lenses disagree:

1. Strategic fit — alignment to pillars and where-to-play 2. Economic return — NPV, ROIC, payback (coordinate with finance) 3. Risk — regulatory, concentration, execution, reputational 4. Optionality — learning, platform, ecosystem lock-in 5. Feasibility — talent, tech debt, change capacity 6. Urgency — competitive window, contract cliff, covenant

Invest sustain harvest divest

Every BU or major product line should have an explicit posture and rationale. Avoid "invest everywhere"—state trade-offs and what is not funded.

Initiative prioritization

Separate strategic initiatives from BAU and from product backlog:

Initiative → strategic outcome → owner (exec sponsor) → value wave → dependencies → kill criteria

Scoring template (weighted 1–5):

Publish top N initiatives for the planning horizon; park the rest with explicit deferral reasons.

Capital and capacity allocation

Tie portfolio decisions to:

• Capital — capex, M&A budget, transformation fund
• People — critical roles, change saturation by BU
• Attention — exec committee time, SteerCo slots

Reconcile portfolio moves with financial constraints (leverage, covenants, dividend policy)—escalate to CFO narrative, not spreadsheet ownership.

Common pitfalls

• Treating all projects as strategic because they have executive sponsors
• Ignoring technical and org debt that blocks value realization
• Portfolio review without exit criteria for failed bets
• Confusing revenue size with strategic importance (large but low-growth cash cows vs small high-option bets)

Enterprise strategist scope

Table of contents

1. Role definition 2. Strategy levels 3. Typical deliverables 4. Inputs and stakeholders 5. Boundaries vs adjacent roles 6. Quality bar

Role definition

Enterprise strategy answers where the organization competes, how it wins, and what must change across businesses, geographies, and functions—at horizons of 1–5+ years. Work is decision-oriented for CEOs, BU presidents, boards, and executive committees—not sprint planning for a single product team.

Strategy levels

Clarify which level the user needs before deep analysis. Corporate choices constrain BU strategy; BU strategies must roll up to portfolio logic.

Typical deliverables

• Strategic pillars and narrative (3–5 pillars max for exec recall)
• Where-to-play / how-to-win (or equivalent) one-pager per BU
• Portfolio map with invest/sustain/harvest/divest recommendations
• Strategic initiative roadmap with outcomes, dependencies, and owners
• Options paper with criteria, trade-offs, and recommendation
• Target operating model (TOM) outline and capability heatmap
• Scenario briefs (base / upside / downside) with triggers and responses
• Board or exec deck storyline (decision ask on final slide)
• Strategic KPI tree linking corporate metrics → BU → initiatives

Inputs and stakeholders

Gather or state assumptions for:

• Financial baseline (revenue, margin, cash, leverage)—use financial-analyst for models, not this skill alone
• Market and competitive context—segment size, growth, share trends
• Capability and talent constraints
• Regulatory or geopolitical constraints affecting where to play
• Board and investor priorities (growth vs margin vs resilience)
• In-flight M&A or partnership discussions (strategy framing only)

Stakeholders: board, CEO, CFO, BU leaders, corp dev, strategy/PMO, HR for org design implications.

Boundaries vs adjacent roles

Quality bar

• MECE options and explicit recommendation with dissent risks noted
• Outcome-linked initiatives (revenue, margin, risk, capability)—not activity lists
• Capacity-aware roadmaps (funding, people, change absorption)
• Traceability from board priority → pillar → initiative → metric
• Avoid generic platitudes; anchor claims in stated assumptions and label unknowns

Growth, diversification, and market position

Table of contents

1. Growth paths 2. Diversification types 3. Competitive positioning at enterprise scale 4. Options generation and comparison 5. Strategic narrative 6. Metrics

Growth paths

Map options to Ansoff-style paths but validate with segment economics—not labels alone.

Diversification types

For each diversification option document:

• Thesis — why now, why us
• Capabilities required — build, buy, partner
• Synergies — revenue, cost, risk (quantify ranges)
• Anti-synergies — distraction, culture, regulatory
• Exit / failure mode — how to unwind if thesis fails

Competitive positioning at enterprise scale

Enterprise positioning spans multiple BUs and brands—avoid single-product taglines as corporate strategy.

Analyze at layers:

1. Corporate — reputation, scale, trust, ESG, financial strength 2. BU / category — segment share, differentiation, price band 3. Capability — what is uniquely hard to replicate (data, distribution, IP)

Use structured comparison:

Positioning statement template (per BU):

For [target segment], [BU/offer] is the [category] that [primary benefit] because [proof points].

Corporate rollup should explain coherence across BUs (platform, bundle, cross-sell) or deliberate separation (house of brands).

Options generation and comparison

Generate 3–5 distinct strategic options (not minor variants). Compare on:

End with recommended option, conditions that would change the recommendation, and no-regret moves valid under all scenarios.

Strategic narrative

Exec-ready storyline:

1. Context — market shift, performance gap, opportunity 2. Ambition — measurable 3-year outcomes 3. Choices — where to play / how to win (explicit nos) 4. Enablers — capabilities, operating model, capital 5. Roadmap — waves, not a flat Gantt 6. Ask — decisions, funding, governance changes

Metrics

Link metrics to strategic pillars in the KPI tree (see scenario_planning_and_executive_alignment.md).

M&A, partnerships, and corporate development

Table of contents

1. Strategy layer vs execution 2. M&A strategic thesis 3. Synergy types and realism 4. Partnerships and alliances 5. Divestitures and portfolio exits 6. Integration boundaries 7. Governance and stage gates

Strategy layer vs execution

This reference covers corporate development strategy framing—not legal due diligence, signing, or funds flow.

M&A strategic thesis

Thesis template:

1. Strategic gap — what capability or position is missing 2. Why M&A vs build/partner (speed, assets, talent, regulation) 3. Target profile — size, geography, tech, culture fit criteria 4. Value creation — revenue synergies, cost synergies, multiple expansion logic 5. Risks — integration, antitrust, talent flight, tech debt 6. Deal breakers — lines not crossed

Screen targets against portfolio posture (invest vs harvest)—acquisitions in harvest businesses need exceptional rationale.

Synergy types and realism

Apply haircuts to synergies in upside cases; separate cost to achieve (integration, retention bonuses, systems).

Partnerships and alliances

Use when full acquisition is excessive risk or capital:

Define: objectives, scope, exclusivity, IP, data sharing, exit clauses (strategy summary—not contract drafting).

Divestitures and portfolio exits

Reasons: focus, liquidity, regulatory, poor fit, valuation capture.

Plan at strategy level:

• Separation thesis — stand-alone viability, TSA needs (high level)
• Buyer universe — strategic vs financial
• Impact on remaining portfolio — stranded costs, brand, customers
• Timing — market window, internal distraction

Integration boundaries

Pre-deal, define integration ambition:

Document must-integrate vs must-not-touch lists to protect the thesis (e.g., brand, core tech, key talent).

Governance and stage gates

Typical stage gates (names vary):

1. Theme approval → 2. Target longlist → 3. Approach / NDA → 4. IOI → 5. LOI → 6. Confirmatory DD → 7. Sign → 8. Close → 9. Integration

Enterprise strategist contributes most through gate 1–4; partner with corp dev and transaction-principal thereafter.

Operating model and capability strategy

Table of contents

1. From strategy to operating model 2. Target operating model components 3. Capability mapping 4. Gap analysis and sourcing 5. Organization and governance 6. Transformation sequencing

From strategy to operating model

Strategy without operating model change often fails in execution. Translate strategic choices into:

• How work is organized (structure, centers of excellence, shared services)
• How decisions are made (governance, delegation, metrics)
• How value is delivered (end-to-end processes, customer journeys)
• What capabilities must exist at what maturity

Distinguish target state from transition state—interim models are valid for 12–24 months.

Target operating model components

Document design principles (e.g., "customer ownership in BU, platforms shared at group level") before detailed design.

Capability mapping

Define business capabilities (what the enterprise must do), not org chart boxes:

Level 1: e.g., Customer management
  Level 2: e.g., Account planning, Service delivery
    Level 3: optional for heatmaps

Rate each capability:

Heatmap: current vs target vs priority (H/M/L) for investment.

Gap analysis and sourcing

For each priority gap choose build, buy, borrow, bot:

Hand off build execution to technical-program-manager; buy strategy thesis to corp dev / transaction-principal; tech platform implications to enterprise-cloud-architect or senior-system-architecture.

Organization and governance

Align governance to strategy:

• Steering forums — strategy vs delivery vs architecture (separate agendas)
• Decision rights — RACI or DACI for portfolio, spend, standards
• Funding model — central transformation fund vs BU P&L chargeback

Flag matrix pain explicitly when strategy requires dual reporting—propose escalation paths.

Transformation sequencing

Order changes by value waves and dependency:

1. Quick wins that fund belief and cash 2. Foundation (data, core platforms, leadership) 3. Scale (rollout, operating model shift) 4. Optimize (automation, portfolio cleanup)

Each wave needs: outcomes, scope boundaries, change impact, and stop rules if benefits do not materialize.

Scenario planning and executive alignment

Table of contents

1. Scenario planning process 2. Scenario archetypes 3. Strategic trade-offs 4. Board and executive alignment 5. KPI trees and strategic metrics 6. Decision memos and governance

Scenario planning process

1. Identify driving forces — macro, industry, technology, regulation, competition 2. Select critical uncertainties — two axes that most affect outcomes 3. Name scenarios — memorable, not probability labels only 4. Flesh narratives — 1–2 page story per scenario with leading indicators 5. Stress-test strategy — which options win/lose per scenario 6. Define signposts — metrics that signal which scenario is emerging 7. Pre-commit responses — no-regret moves vs contingent bets

Avoid false precision in scenario financials; use ranges and explicit assumptions.

Scenario archetypes

Map initiatives to scenarios: core (all), optional (one scenario), hedge (downside protection).

Strategic trade-offs

Make trade-offs explicit—leadership cannot optimize everything:

Use even-over statements where helpful: "We prioritize share in core segment even over margin expansion in adjacencies this cycle."

Board and executive alignment

Alignment checklist

• [ ] Single set of strategic pillars endorsed by CEO
• [ ] Portfolio postures agreed per major BU
• [ ] Top initiatives capped with named sponsors
• [ ] Financial envelope reconciled with CFO
• [ ] Risk appetite stated (growth, compliance, concentration)
• [ ] Comms narrative aligned (communication-lead for execution)

Board materials

Typical board strategy section:

1. Performance vs strategic plan 2. Market and competitive update 3. Portfolio decisions required 4. Major initiative status (outcomes, not tasks) 5. Scenario update and signposts 6. Decisions requested (approve / note / defer)

Avoid operational detail; link to strategic risks and mitigations.

KPI trees and strategic metrics

Build a KPI tree top-down:

North star / corporate outcome
  ├── Pillar 1 metric(s)
  │     ├── Initiative A leading indicators
  ├── Pillar 2 metric(s)
  └── Financial guardrails (cash, leverage, ROIC)

Rules:

• Few metrics at corporate level (≤7–10)
• Distinguish outcome vs output vs activity
• Assign one owner per metric
• Set review cadence (monthly ops vs quarterly board)

Cascade without metric overload—BUs should not inherit 40 corporate KPIs.

Decision memos and governance

Decision memo structure:

1. Decision required (one sentence) 2. Context (brief) 3. Options (2–4) with pros/cons 4. Recommendation and rationale 5. Risks and mitigations 6. Resource ask 7. Implementation outline and owners 8. Appendices (detail for readers who need depth)

Log decisions in SteerCo or strategy forum minutes; revisit when signposts trigger scenario shifts.