Recommended resources
The freely available resources this lesson will direct you to.
- Dan Olsen "How to Create Your Product Strategy" at the 2018 NYC Product Leader Summitwww.youtube.com
- Strategies in business: The 4 types of strategies you needwww.youtube.com
- Corporate Strategy vs. Business Strategy: What’s the Difference? - Professional & Executive Development | Harvard DCEprofessional.dce.harvard.edu
- Think before you build: A guide to design strategy | Nulabnulab.com
Hello. This module examines business strategy through a design lens: where a company chooses to compete, how it aims to win, and how those choices reach customers through products and experiences. In this first lesson, you’ll distinguish corporate, business, product, and design strategy using Apple as a real-company example. Allow about 40 minutes, including the short reading and video segments.
The distinction matters in leadership conversations. “Make the camera easier to use” might be a sensible design direction, but it does not, by itself, explain why the company is investing in phones, how it competes in that market, or which customer benefit the product is meant to deliver. Moving confidently between those levels is part of connecting design decisions to business choices.
Strategy is a choice, not a collection of plans
A strategy describes where to focus, how to create an advantage, and what not to pursue. A goal states a desired result; a roadmap schedules work. Neither substitutes for a choice about how to succeed.
The four levels differ primarily by the scope of the decision:
| Level | Governing question | Typical choice |
|---|---|---|
| Corporate | Which businesses or markets should we participate in, and where should we invest? | Enter a market rather than put all available resources into existing ones. |
| Business | How will we win against alternatives in a particular market? | Compete on a differentiated experience rather than the lowest price. |
| Product | Which customers and needs will this product serve distinctively? | Prioritize a particular customer benefit over other possible benefits. |
| Design | What experience principles and decisions will make that benefit real for people? | Make the most important task clear and quick, even if some controls are less prominent. |
These are lenses on decisions, not necessarily four departments or four documents. A small venture might make corporate and business choices in the same meeting. A large company might have several business-level strategies, each supported by many products.
Read Harvard DCE’s distinction between corporate and business strategy, paying particular attention to its description of markets, resources, and competitive positioning.
Read Harvard DCE’s comparison to establish the scope of corporate and business decisions. Its Apple example also gives us a real company to examine throughout the lesson.
In “Corporate Strategy vs. Business Strategy: Definitions,” read the instructor's comparison, from the paragraph beginning “At the highest level” through its explanation of positioning across customer segments. Then, under “Business-level strategy vs. corporate-level strategy: a comparison,” find item “1. Level.” Read the Apple example, from its account of entering new markets through its final sentence about organization-wide decision-making. Focus on the scope of each choice, rather than treating the article’s example of a marketing campaign as a complete business strategy.
One qualification is important: business strategy is not simply a short-term departmental plan. In this lesson, it means the competitive logic for a business in a defined market. Marketing campaigns, sales plans, and engineering plans may support that logic, but none alone answers how the business intends to win.
Corporate strategy sets the playing field
Harvard DCE describes Apple’s movement from computers into music and smartphones as an example of decisions with organization-wide reach. At this level, leaders must consider whether to enter or leave markets, how much capital and attention to commit, and which capabilities can serve more than one business.
Imagine a company deciding whether to invest heavily in a new device category. The question is not yet “Where should the camera button go?” It is whether the potential market justifies diverting talent, capital, and executive attention from other opportunities. Saying yes commits resources; saying no preserves them for alternatives. Opportunity cost is present at every level of strategy, but corporate choices can reshape the whole portfolio.
Business strategy begins once we specify a market in which to compete. For a smartphone business, it asks: Which customers are we trying to win, what alternatives do they have, and why would they choose us? A claim such as “we’ll offer a coherent device-and-software experience rather than compete primarily for the lowest upfront price” is a business-level choice. It proposes a basis for competition, not merely a sales target.
Notice the boundary: entering smartphones is a corporate question; choosing how to compete against other smartphones is a business question. Both may be discussed by the same executives, but they demand different evidence.
Product strategy chooses a customer benefit
A business can have a compelling competitive position and still build products that do not deliver it. Product strategy narrows the focus to an offering: its target customers, their underserved needs, the benefit it will emphasize, and the alternatives against which it must stand out.
Watch Dan Olsen’s short segments for two especially useful ideas: strategy requires saying no, and a product should be defined by the customer benefit it delivers rather than by a list of features. His retrospective Instagram example makes that distinction concrete.
Dan Olsen "How to Create Your Product Strategy" at the 2018 NYC Product Leader Summit
Watch “How to Create Your Product Strategy” by Dan Olsen, on Spero Ventures. These excerpts connect strategic focus to customer needs and show how to distinguish a benefit from the feature that delivers it.
Start with saying no, where Olsen explains why accepting every attractive request is not strategy. Then watch the product pyramid for target customers, underserved needs, differentiation, features, and experience. Finally, watch the Instagram example. Notice that “make my photos look good” is a customer benefit; filters are one way to deliver it. Olsen presents this as a retrospective analysis, not as Instagram’s documented internal strategy.
That difference between benefit and feature is useful in executive discussions. “Build filters” can become a backlog item. “Help people feel good about the photos they share” states a benefit that several possible solutions could serve. Product strategy chooses which benefits to lead on and for whom; it does not require committing prematurely to every implementation detail.
Design strategy makes the intended benefit usable
Design strategy concerns the intended experience and the principles that guide its creation. It is broader than visual styling and more selective than “make everything intuitive.” It may guide interaction patterns, information architecture, accessibility, content, research priorities, and how consistency is maintained across a product.
Read Nulab’s concise product-versus-design distinction, then hold it to a demanding standard: “how” should mean which experience choices will serve a particular customer and product direction, not merely which screens designers will produce.
Think before you build: A guide to design strategy | Nulab
Read Nulab’s “Product strategy vs. design strategy” section for a compact distinction between a product’s market direction and the experience intended to deliver it.
Under “Product strategy vs. design strategy,” begin at the paragraph opening “With this in mind” and read the full comparison through the concluding warning about design without product vision. Pay attention to the questions each strategy asks. Treat its description of design as “how” as a starting point: a design strategy also needs priorities and trade-offs, not just an instruction to improve usability.
Suppose a product direction emphasizes helping people capture a usable photo quickly. A design strategy might prioritize immediate access to capture, understandable defaults, and clear feedback about what the camera is doing. It must also address a tension: exposing every advanced control could help some users while slowing the default experience for others. Choosing how to handle that tension is strategic; drawing a particular icon is usually an execution decision.
One company, four different decisions
Now apply the four lenses to Apple and the iPhone. The reading documents Apple’s broader expansion into smartphones. The remaining entries below are an illustrative strategic reconstruction: plausible choices for analyzing a real company and product, not quotations from Apple’s internal plans or proof that particular decisions caused its results.
| Level | Illustrative strategic choice | What it leaves open |
|---|---|---|
| Corporate | Participate in smartphones alongside other device and service categories; commit resources to that portfolio. | How to beat smartphone rivals. |
| Business | In smartphones, emphasize an integrated, reliable experience rather than make the lowest purchase price the primary basis for winning. | Which iPhone benefits deserve product priority. |
| Product | For everyday iPhone photography, prioritize helping people capture a satisfactory photo with little setup. | Precisely how the camera experience should work. |
| Design | Keep the common capture path fast and understandable while making more advanced options available without dominating the default view. | The final layout, controls, wording, and implementation. |
Read the rows as increasingly specific commitments, not as a guarantee that one choice automatically produces the next. The business choice could support several product directions besides photography. The product choice could support several design approaches. At each boundary, leaders need evidence and judgment.
The rows also reveal different ways a proposal can fail. A beautifully designed camera interaction might deliver the intended product benefit but make little difference to smartphone preference. A distinctive product benefit might attract customers but be too costly to sustain. And a promising smartphone position might still receive too little investment if the corporation chooses other priorities. Alignment means testing these links, not assuming them.
For the design-led leader, the most valuable contribution is often to make a link explicit: “We are prioritizing this experience for these customers because it should strengthen this product benefit, which supports our chosen basis for competing.” That statement invites productive scrutiny. It also separates a strategic recommendation from a preference for a particular interface.
A reusable way to locate a decision
When a proposal is presented as “strategic,” identify its unit of choice before discussing solutions:
- Is it choosing a portfolio or market? Examine it as corporate strategy.
- Is it choosing a basis for winning in a market? Examine it as business strategy.
- Is it choosing a customer and differentiated benefit for an offering? Examine it as product strategy.
- Is it choosing experience principles and trade-offs that deliver that benefit? Examine it as design strategy.
A proposal may affect several levels. For example, investing in a shared design system is not automatically “design strategy” simply because designers lead it. If the central decision is how multiple businesses share capabilities and resources, it has a corporate dimension. If the central decision is how product experiences remain coherent, it has a design dimension. Classify the question being decided, not the job title of the person proposing it.
The four-level account is also a useful teaching tool: it lets a team discuss whether disagreement is about where to compete, how to win, what benefit to deliver, or how people will experience that benefit. Those disagreements require different evidence and different decision-makers.
Conclusion
Corporate strategy chooses the company’s playing fields and major resource commitments. Business strategy chooses how to compete in one of those fields. Product strategy chooses the customers and benefits an offering will prioritize. Design strategy guides the experience choices that make those benefits usable and credible. The levels connect, but none is a substitute for another—and each involves saying no to alternatives.
In the next lesson, you’ll examine how a company creates, delivers, and captures value. That will give these strategic choices a more complete business model: not only why customers might prefer an experience, but how the organization can provide it and sustain itself by doing so.