Unit 4: Product strategy: connecting work to business outcomes

Learning objectives

By the end of this unit, you should be able to explain what product strategy is and why it matters, distinguish between strategy and a feature list, and create a basic product strategy framework for a product you know.

Video script

Reading material

Strategy in practice

A product strategy doesn't need to be a 50-page document. The best ones I've seen fit on a single page and can be explained in five minutes. Here's a template that works.

Vision (one sentence). Where is this product heading, and for whom? Example: "The go-to platform for mid-market B2B companies to manage their customer lifecycle from first touch to renewal."

Target customer (one paragraph). Who are you building for? Be specific. Not "businesses" but "B2B SaaS companies with 50-500 employees, selling to mid-market and enterprise customers, with a dedicated customer success team." Specificity creates focus.

Key problems (three to five). What are the most important unsolved problems for this customer? Rank them. The ranking is the strategy. Choosing to focus on problem #1 over problem #3 is a strategic decision that shapes everything downstream.

Approach (one paragraph per problem). For each key problem, what's your theory about how to solve it? What's your unique angle? This isn't a feature description. It's a hypothesis about the solution direction. "We believe that automated lifecycle health scoring, powered by our integration with the customer's existing tools, will help CS teams proactively identify at-risk accounts before churn signals appear."

Success metrics (one per problem). How will you know if your approach is working? Tie each key problem to a measurable outcome.

Common strategy mistakes

The strategy is a list of goals. "Increase revenue 30%, expand to new markets, improve NPS." These are goals, not strategy. Strategy is the plan for how you'll achieve the goals.

The strategy changes quarterly. Strategy should be stable for at least a year. If you're rewriting your strategy every quarter, you don't have a strategy. You have quarterly planning anxiety.

The strategy doesn't involve trade-offs. If your strategy says yes to everything, it's not a strategy. Strategy is about choosing what not to do as much as what to do. If you can't point to something you've explicitly decided not to pursue, your strategy isn't specific enough.

Strategy and AI

AI creates both opportunities and risks for product strategy.

The opportunity is that AI gives you more data to inform strategic decisions. Customer data, market data, competitive data can be processed faster and more thoroughly. This should make your strategy more evidence-based.

The risk is that more data creates the illusion of strategic clarity when you actually just have more information. Strategy requires judgment about what the data means and what to do about it. More data doesn't automatically lead to better judgment. Sometimes it leads to analysis paralysis.

The practical advice: use AI to gather and synthesize strategic inputs faster. Then turn off the tools and think. Strategy is a thinking exercise, not a data processing exercise.

Practical exercise

Exercise: One-page strategy

Choose a product you know well (ideally one you use regularly). Create a one-page product strategy using the template above.

Try to fill in each section based on what you know as a user and what you can research publicly. Don't worry about getting it "right." The goal is to practice the structure and notice where your knowledge gaps are.

After completing it, write down: which section was hardest to fill? Why? What would you need to learn to fill it better? These questions reveal where the real strategic thinking lives.