Who writes the design strategy?

Senior-design-managers (M2) write team-level design strategy. Group-design-managers (M3) write multi-team-or-product-surface design strategy. Directors of design (D1) write design-org strategic direction. VP Design / CDO (D2) writes the design-org strategy at the company level. The artifact is the design-strategy memo.

How often should the design strategy be updated?

Annual update is the modal cadence at most large tech companies. Some companies (Stripe, Figma) update bi-annually. The memo is a living document; it is updated as the strategic context shifts. Major strategic pivots (re-orgs, acquisition integration, leadership change) typically require an out-of-cycle update.

How is design strategy different from product strategy?

Product strategy answers 'what should we build' over multiple quarters. Design strategy answers 'how should the design language evolve' and 'what design-org capabilities should we invest in' over multiple quarters. Cagan's Empowered (Wiley, 2020) covers the cross-functional triadic strategy where product, design, and engineering strategies integrate. The strong design-leader strategy engages with the product strategy explicitly rather than existing in design-org isolation.

What's the difference between design strategy and design vision?

Design vision is aspirational and long-horizon (3–5 years); design strategy is concrete and medium-horizon (12–24 months). Strategy includes diagnosis, guiding policy, and coherent actions; vision typically includes only the aspirational direction. Both are useful; conflating them is the canonical failure mode (the 'vision-as-strategy' artifact has no actions).

How do I write the diagnosis section without sounding like I'm criticizing my predecessors?

Specific and evidence-based. 'Customer-perception research from Q3 2024 shows brand-coherence scores of 6.2/10 across our four product lines' is a diagnosis. 'The previous design leadership didn't prioritize coherence' is criticism. The diagnosis describes the current state in observable terms; it doesn't attribute cause-of-state to people. Larson's chapter on strategy in An Elegant Puzzle covers the diagnosis-without-attribution pattern.

How do I get C-suite buy-in on the design strategy?

Engage with C-suite priorities explicitly. The strong design-strategy memo references the company's product strategy, business strategy, and any explicit C-suite priorities. The C-suite reads design strategy in the context of the broader company strategy; the design-strategy memo that exists in design-org isolation is dismissed. Cagan's Empowered covers the senior-leadership buy-in patterns.

What if the design strategy and the product strategy conflict?

Surface the conflict explicitly to the senior-leadership team. The triadic resolution: design, product, and engineering leaders meet to align the strategies. Disagreements at this level are escalated to the C-suite (CPO + VP Design + CTO, with CEO when needed). The failure mode is the design strategy that pretends the conflict doesn't exist — the conflict surfaces later in execution and the strategy loses credibility.

Design Manager Hub

Design Strategy and Roadmapping: Cagan, Goodwin, Schleifer (2026)

By Blake Crosley · Last verified 2026-04-30

In short

Design strategy at the senior-design-manager+ tier is the multi-quarter narrative that explains where the design org is going and why. The canonical mechanics: Marty Cagan's Empowered (Wiley, 2020) on product-design-engineering triadic strategy; Kim Goodwin's Designing for the Digital Age (Wiley, 2009) on design-strategy structures; Will Larson's An Elegant Puzzle (Stripe Press, 2019) chapter on engineering-strategy applied cross-disciplinary; the publicly-discussed design-strategy work at Airbnb (Schleifer-era Design Language System) and Apple (HIG annual evolution). The dominant failure mode is the design strategy that is a feature roadmap with design polish — strong design strategy is about the design language, the design-system stewardship, and the multi-quarter design-org capability development.

Key takeaways

Design strategy is the multi-quarter narrative that explains where the design org is going and why. It is not a feature roadmap with design polish; it is the strategic articulation of design-language direction, design-system stewardship priorities, and design-org capability development over 12–24 months.
Marty Cagan's Empowered (Wiley, 2020) is the canonical reference for triadic product-design-engineering strategy at the senior-leadership tier. Cagan's framing: design strategy that doesn't engage with product strategy and engineering strategy is incomplete; the strong design-leader strategy integrates the three.
Kim Goodwin's Designing for the Digital Age (Wiley, 2009) chapter 2 ('Goal-Directed Design Process') and the broader Cooper-school heritage are the canonical references for design-strategy mechanics. The framework: user goals, business goals, design principles, then design decisions cascade.
Will Larson's An Elegant Puzzle (Stripe Press, 2019) chapter on 'Strategy' applies cross-disciplinary to design. Strong strategy has: a diagnosis of the current state, a guiding policy, and coherent actions. Weak strategy is a list of feature investments without the diagnosis or guiding policy.
The design-system-as-product roadmap is a load-bearing artifact at most large tech companies. Senior-design-managers and group-design-managers steward the design system with explicit roadmaps that span 6–18 months. The publicly-discussed design-system roadmaps at Airbnb (DLS) and Apple (HIG annual updates) are the canonical worked examples.
Design-org capability development is the multi-quarter strategic artifact. What capabilities does the design org need to acquire (research integration, content design, motion design, design-system engineering, AI-product design)? Which existing capabilities need investment? Which need divestment? The strategy answers these explicitly.
Mia Blume's Design Dept community materials cover the senior-design-leadership strategy patterns. The most-cited Design Dept artifact is the 'design strategy memo' template — a 5–10 page memo that articulates the design-org strategic direction, read by the CEO and the board.

What design strategy actually is (and isn't)

Design strategy is the multi-quarter narrative that explains where the design org is going and why. The structural elements drawn from Marty Cagan's Empowered, Kim Goodwin's Designing for the Digital Age, Will Larson's An Elegant Puzzle (cross-disciplinary applicable), and Mia Blume's Design Dept materials:

Diagnosis: where are we today? What is the current state of the design language, the design system, the design-org capabilities, and the cross-functional partnership? What's working? What's broken? Strong diagnosis is specific and evidence-based; weak diagnosis is vague and feels-based.
Guiding policy: what is the strategic posture? Larson's framing applied cross-disciplinary: the guiding policy is the principle that resolves trade-offs across the multi-quarter horizon. Examples: 'design quality as competitive moat' (Stripe-style), 'design language as platform foundation' (Apple HIG-style), 'designing for designers' (Figma-style). The guiding policy explains why specific actions are coherent.
Coherent actions: what are we doing in the next 12–24 months? 3–7 specific actions that follow from the guiding policy. Examples: unify the design language across consumer-web, mobile-iOS, and mobile-Android; expand the design-system to support the AI-product surface; invest in design-system engineering capability by hiring 3 senior IC engineers and 1 senior IC designer to the design-system team.
What design strategy is not. A feature roadmap with design polish. A list of design-craft commitments without diagnosis or guiding policy. A re-org without the strategic rationale. A 'design vision' that is aspirational without specific actions or measurable outcomes.

The reading list for design-strategy context: Cagan's Empowered (Wiley, 2020), Goodwin's Designing for the Digital Age chapters 2 and 25 (Wiley, 2009), Larson's An Elegant Puzzle 'Strategy' chapter (Stripe Press, 2019), Mia Blume's Design Dept community materials, Richard Rumelt's Good Strategy / Bad Strategy (Crown, 2011) for the cross-disciplinary strategy framework.

The design-system-as-product roadmap

The design-system-as-product roadmap is a load-bearing artifact at most large tech companies. The mechanics drawn from the publicly-discussed Airbnb DLS work, Apple HIG annual updates, Figma's design-system-stewardship culture, and the Material Design 3 / Material You evolution:

The design system as product. At most large tech companies in 2026, the design system is treated as a first-class product with its own roadmap, its own success metrics, its own engineering-and-design team, and its own internal customers (the product-design teams that consume it). This treatment is recent — pre-2018 most companies treated design systems as 'tools for designers' rather than as products.
The roadmap structure. 6–18 months horizon. The roadmap typically includes: foundations work (design tokens, primitive components), surface work (high-order components for specific product surfaces), pattern work (interaction patterns, page templates), and accessibility/internationalization work (which is often under-invested without explicit roadmap commitment).
Stewardship at the senior-design-manager+ tier. The design system is stewarded by senior-design-managers and group-design-managers, sometimes with explicit dotted-line reporting from a design-system team to the GDM. The senior-design-manager who owns the design system is typically the most-cross-functional design manager because the design system is consumed by every product surface.
The publicly-discussed worked examples. Airbnb DLS (2014, Schleifer-era; documented at airbnb.design/building-a-visual-language) was the canonical design-system unification at scale. Apple HIG annual updates are the canonical platform-design-system stewardship at scale. Material Design 3 / Material You (2021) is the cross-platform design-system-as-product worked example.
Failure modes. The design-system that has no explicit roadmap (the team ships components reactively in response to product asks). The design-system roadmap that is unconnected to the product roadmap (the system ships features that no product team needs). The design-system team that is under-resourced relative to the product-design team it serves (typical 1:8 to 1:12 ratio is healthy; below 1:15 the team is reactive).

Design-org capability development as a strategic artifact

Design-org capability development is the multi-quarter strategic artifact at the senior-design-manager+ tier. The mechanics drawn from John Maeda's Design in Tech reports (annual evolution of design capabilities at company scale), Mia Blume's Design Dept materials on org capability planning, and the publicly-discussed capability shifts at FAANG and design-strong consumer companies:

The capability inventory. What capabilities does the design org currently have? Research integration (UX research embedded in design teams or separate research org). Content design (copy, voice, microcopy, error messages). Motion design (animation, transition, dynamic-states craft). Design-system engineering (the technical infrastructure underlying the design system). Service design (cross-product, cross-touchpoint design). AI-product design (a new capability emerging in 2024–2026).
The capability roadmap. Which existing capabilities need investment? Which need divestment? Which new capabilities need acquisition? Examples drawn from publicly-discussed company shifts: Airbnb's investment in research-integration during the post-2014 DLS era, Apple's investment in motion-design during the iOS 7+ era and the Vision Pro era, Stripe's investment in content-design during the 2018+ developer-tool-quality push, Figma's investment in design-system-engineering during the 2022+ component-library-evolution, Notion's investment in AI-product-design during the 2024+ Notion AI integration.
The hiring implication. Capability development drives senior IC hiring. The design-org strategy explicitly identifies which senior IC roles (motion designer, content designer, design-system engineer, AI-product designer) need to be hired and at what level. The hiring plan flows from the strategy.
The internal development implication. Some capabilities are developed internally rather than hired. The strategy identifies which existing designers will be sponsored to develop new capabilities (typically through stretch assignments, structured learning time, or external coaching). Sponsorship is the senior-design-manager's craft.
Failure modes. The capability roadmap that exists in vibe but not in writing. The capability roadmap that doesn't connect to hiring or to internal development. The capability roadmap that doesn't acknowledge what's being divested (every investment requires a divestment in a constrained-headcount environment).

The design-strategy memo: the load-bearing artifact

The design-strategy memo is the load-bearing artifact at the senior-design-manager+ tier. The mechanics drawn from Mia Blume's Design Dept community materials on the 'design-strategy memo' template, Cagan's Empowered chapters on product-leadership writing, and Larson's An Elegant Puzzle writing on strategy memos:

Length and audience. 5–10 pages. Read by the CEO, the C-suite, the board (at design-strong consumer companies), and the entire design org. The audience is multi-tier — write for the most senior reader and provide footnotes / appendices for the more-junior readers.
Structure. (1) Executive summary (1 page): the strategic posture in one paragraph. (2) Diagnosis (2–3 pages): where are we today, evidence-based. (3) Guiding policy (1 page): the strategic posture in detail. (4) Coherent actions (2–3 pages): the 3–7 specific actions. (5) Risks and trade-offs (1 page): what could go wrong, what we're explicitly not doing.
Cadence. Annual update is the modal cadence at most large tech companies. Some companies (Stripe, Figma) update bi-annually. The memo is a living document; it is updated as the strategic context shifts.
Sponsorship. The memo is signed by the senior-design-manager (or group-design-manager, director-of-design, or VP Design at higher tiers). Sponsorship is explicit: the senior-design-leader stakes their credibility on the strategic direction.
Reading the room. Strong design-strategy memos are read in the context of the company's broader strategy. The memo references the company's product strategy, business strategy, and any explicit C-suite priorities. The memo that exists in design-org isolation is dismissed by C-suite as 'design wants more headcount.'

Frequently asked questions

Who writes the design strategy?: Senior-design-managers (M2) write team-level design strategy. Group-design-managers (M3) write multi-team-or-product-surface design strategy. Directors of design (D1) write design-org strategic direction. VP Design / CDO (D2) writes the design-org strategy at the company level. The artifact is the design-strategy memo.
How often should the design strategy be updated?: Annual update is the modal cadence at most large tech companies. Some companies (Stripe, Figma) update bi-annually. The memo is a living document; it is updated as the strategic context shifts. Major strategic pivots (re-orgs, acquisition integration, leadership change) typically require an out-of-cycle update.
How is design strategy different from product strategy?: Product strategy answers 'what should we build' over multiple quarters. Design strategy answers 'how should the design language evolve' and 'what design-org capabilities should we invest in' over multiple quarters. Cagan's Empowered (Wiley, 2020) covers the cross-functional triadic strategy where product, design, and engineering strategies integrate. The strong design-leader strategy engages with the product strategy explicitly rather than existing in design-org isolation.
What's the difference between design strategy and design vision?: Design vision is aspirational and long-horizon (3–5 years); design strategy is concrete and medium-horizon (12–24 months). Strategy includes diagnosis, guiding policy, and coherent actions; vision typically includes only the aspirational direction. Both are useful; conflating them is the canonical failure mode (the 'vision-as-strategy' artifact has no actions).
How do I write the diagnosis section without sounding like I'm criticizing my predecessors?: Specific and evidence-based. 'Customer-perception research from Q3 2024 shows brand-coherence scores of 6.2/10 across our four product lines' is a diagnosis. 'The previous design leadership didn't prioritize coherence' is criticism. The diagnosis describes the current state in observable terms; it doesn't attribute cause-of-state to people. Larson's chapter on strategy in An Elegant Puzzle covers the diagnosis-without-attribution pattern.
How do I get C-suite buy-in on the design strategy?: Engage with C-suite priorities explicitly. The strong design-strategy memo references the company's product strategy, business strategy, and any explicit C-suite priorities. The C-suite reads design strategy in the context of the broader company strategy; the design-strategy memo that exists in design-org isolation is dismissed. Cagan's Empowered covers the senior-leadership buy-in patterns.
What if the design strategy and the product strategy conflict?: Surface the conflict explicitly to the senior-leadership team. The triadic resolution: design, product, and engineering leaders meet to align the strategies. Disagreements at this level are escalated to the C-suite (CPO + VP Design + CTO, with CEO when needed). The failure mode is the design strategy that pretends the conflict doesn't exist — the conflict surfaces later in execution and the strategy loses credibility.

Sources

About the author. Blake Crosley founded ResumeGeni and writes about design management, hiring technology, and ATS optimization. More writing at blakecrosley.com.