Blog

Posted on

25 Skills Every Product Manager Should Be Building in 2026

Product Manager sitting in his home office reading

Quick answer: The 25 skills every PM should build in 2026 fall into five areas — customer obsession, strategic thinking, execution, communication, and personal mastery — but they all trace back to one root skill: deep customer knowledge. Without it, ruthless prioritization, product strategy, and stakeholder management have nothing solid to stand on. The newest addition for 2026 is AI fluency: knowing which parts of your PM work (research synthesis, first drafts, data analysis) benefit from AI acceleration and which still require human judgment (strategy, relationships, trust).

There’s no shortage of “skills for PMs” lists on the internet. Most of them read like a job description, technically correct, but practically useless.

This isn’t that list. These are the 25 skills I’ve seen separate the product managers who move the needle from the ones who stay busy. I’ve organized them by the areas where I see the biggest gaps, not by some theoretical framework. Some of these are timeless. Some are specific to right now. All of them are things I wish someone had told me earlier in my career.

I. Customer Obsession

These are the skills that everything else builds on. Get these wrong and nothing else matters.

1. Deep Customer Knowledge

You can’t fake this one. The best PMs I’ve worked with can describe their top customer segments in vivid detail – not just demographics, but the actual daily workflow, the frustrations, the workarounds they’ve built, the language they use when they’re annoyed.

This doesn’t come from dashboards. It comes from sitting with customers, watching them use your product, and resisting the urge to defend your design choices when they struggle. Do this monthly, not quarterly. The PMs who “don’t have time” for customer conversations are the same ones who build features nobody uses.

2. Jobs-to-be-Done Thinking

Clayton Christensen’s framework has become so mainstream that people name-drop it without actually applying it. The real skill isn’t knowing what JTBD is, it’s being able to articulate the job your customer is hiring your product to do in one sentence.

If you can’t do that, you don’t understand your customer well enough yet. Every feature decision should trace back to that job. If it doesn’t advance the job, it’s noise.

3. Continuous Discovery

Teresa Torres literally wrote the book on this. The skill isn’t “doing user research” – it’s building a rhythm of weekly customer touchpoints that inform your decisions in real-time, not once a quarter when the research team delivers a 40-page report nobody reads.

The PMs who do this well talk to 2-3 customers every single week. Not formal research sessions with screeners and discussion guides. Quick, focused conversations that answer specific questions about specific opportunities.

I have “virtual coffee” times available on my calendar and invite users on our emails to book some time with me. It’s fantastic and gives me tons of insight into our customers.

4. Knowing When to Ignore Feedback

This sounds counterintuitive after three skills about listening to customers. But one of the hardest skills in product management is knowing WHICH feedback to act on and which to file away.

Not every customer request is a product insight. Sometimes a customer wants something that serves them but hurts the broader user base. Sometimes they’re describing a symptom, not the root cause. The skill is triangulating. When you hear the same pain from multiple segments, supported by data, that’s signal. When one loud customer demands something, that’s noise.

5. Empathy That Goes Beyond Platitudes

Every PM claims to have empathy. The actual skill is translating empathy into product decisions. It’s the difference between saying “I understand the user’s frustration” and redesigning the onboarding flow because you watched someone struggle for 8 minutes trying to complete a task that should take 30 seconds.

Real empathy is uncomfortable. It means watching your product fail in real-time and sitting with that feeling instead of explaining it away.

II. Strategic Thinking

These are the skills that determine whether your team is building the right things.

6. Product Vision

A compelling product vision describes what the world looks like 2-5 years from now if your product succeeds. Not a feature list. Not a technology roadmap. A picture of a better future for your customer.

The skill is making this concrete enough to inspire and vague enough to allow room for discovery. “We’ll be the leading platform for X” is not a vision. “Every pastor will have a personal AI-powered sermon preparation assistant that cuts their weekly prep time in half” – that’s a vision.

7. Product Strategy

I wrote about the 10 most common strategy mistakes recently, and the biggest one is teams that have no strategy at all — just a backlog they call a strategy.

The skill here is making choices. Real ones. Strategy means explicitly deciding what you will NOT do, who you will NOT serve, and which opportunities you will walk away from. If your strategy doesn’t make someone uncomfortable, it’s not a strategy.

8. Ruthless Prioritization

This is the skill that separates senior PMs from everyone else. You will always have more opportunities than capacity. The question is never “should we build this?” Everything on your list is probably worth building. The question is “should we build this INSTEAD of that?”

Frameworks like RICE scoring help, but the real skill is having the conviction to say no to good ideas because they’re not the BEST idea right now. Warren Buffett’s two-list strategy applies: identify your top 25 priorities, circle the top 5, and treat the other 20 as your “avoid at all costs” list.

9. Outcome-Focused Roadmapping

The shift from output-based roadmaps (“Q2: Ship feature X, Y, Z”) to outcome-based roadmaps (“Q2: Reduce trial-to-paid time from 14 days to 7 days”) is one of the most important evolutions in modern product management.

The skill is framing your roadmap around the problems you’re solving and the metrics you’re moving, not the features you’re building. This gives your team room to discover the best solution instead of being locked into a predetermined one.

10. Saying No (and Making It Stick)

Every PM knows they should say no more often. The actual skill is saying no in a way that maintains relationships and builds trust. “No, because our strategy is focused on X, and here’s why that matters more right now” is dramatically different from just “no.”

The best PMs I’ve seen turn a “no” into a learning moment by explaining the reasoning, sharing the data, and making the person feel heard even when the answer isn’t what they wanted. I’ve found that people can disagree with a well-reasoned decision. What often causes stress is ambiguity.

III. Execution and Delivery

These are the skills that turn strategy into a shipped product.

11. Rapid Experimentation

The ability to test ideas in hours or days instead of weeks or months is a superpower. This means prototyping. Not pixel-perfect mockups, but rough, testable concepts that answer specific questions.

Can users find this feature? Does this flow make sense? Will anyone actually use this? You can answer all of these questions with a prototype and 5 users in a single afternoon.

12. Writing Clear Requirements

This is an underrated skill. The gap between “what the PM imagined” and “what engineering built” is almost always a requirements problem, not a competence problem.

The skill is writing requirements that are specific enough to build from but flexible enough to allow engineering creativity. I’ve found that focusing on the PROBLEM and the SUCCESS CRITERIA while leaving the implementation approach to engineering produces the best results.

13. Data Literacy

You don’t need to be a data scientist, but you need to be dangerous with data. That means understanding statistical significance (so you don’t kill an A/B test too early), knowing which metrics actually matter for your product, and being able to query your own data when the analytics team is backed up.

AI has made this dramatically easier. You can now describe what you want in plain English and get a SQL query back. That’s a genuine unlock for PMs who previously had to wait days for a data pull.

14. Delivery Management

Understanding how your team ships code, whether it’s sprint cycles, deployment pipelines, feature flags, rollback procedures, makes you a better PM. Not because you need to manage the process (that’s engineering’s job), but because understanding the constraints helps you make better tradeoff decisions.

“Can we ship this behind a feature flag to 10% of users first?” is a much better question than “when will this be done?”

15. Technical Literacy

You don’t need to code, but you need to understand enough about your technology stack to have meaningful conversations with engineering. What’s an API? What are the database constraints? Why does this “simple” change actually require refactoring three services?

The skill is asking good technical questions, not having the answers. When your engineering lead says “that’s a 3-month project,” you should be able to ask “what makes it 3 months?” and understand the answer.

IV. Communication and Influence

These are the skills that get people aligned and keep them there.

16. Stakeholder Management

Your stakeholders have competing priorities, different incentive structures, and varying levels of product literacy. The skill is navigating all of that without losing your strategic direction.

The best approach I’ve found: radical transparency about your decision-making process. Share the data, explain the tradeoffs, make a clear recommendation, and invite disagreement before the decision, not after. People support what they help create, even if they don’t get everything they wanted.

17. Executive Communication

Executives don’t want details. They want: what’s the problem, what’s the recommendation, and what do you need from them. That’s it.

The skill is compression, taking a complex product situation and distilling it into a 2-minute narrative that leads to a clear ask. If you can’t explain your strategy in the time it takes to ride an elevator, you haven’t thought about it clearly enough.

18. Cross-Functional Leadership

PMs lead without authority. You can’t tell engineering what to build, design what to design, or marketing what to say. You can only influence.

The skill is making other teams WANT to follow your lead because you’ve earned their trust. That means understanding their constraints, respecting their expertise, giving them credit publicly, and never throwing them under the bus when something goes wrong.

19. Writing as a Leadership Tool

Product managers who write well have an outsized advantage. Strategy docs, product briefs, stakeholder updates, customer communications – writing is how PMs scale their influence beyond the meetings they attend.

Jeff Bezos banned PowerPoint at Amazon for a reason. Clear writing forces clear thinking. If you can’t write a coherent one-page strategy doc, your strategy probably isn’t coherent.

20. Storytelling with Data

Data alone doesn’t persuade anyone. The skill is wrapping data in a narrative that makes people care. “Churn increased 3%” is a data point. “We’re losing 40 paying customers every month, and here’s what they’re telling us on the way out the door” is a story that drives action.

Every dashboard metric should have a “so what?” attached to it. If you can’t articulate the “so what,” the metric isn’t useful yet.

V. Personal Mastery

These are the skills that compound over time and separate the good from the great.

21. AI Fluency

This is the new table-stakes skill for 2026. Not building AI products (though that’s increasingly common) but using AI tools to accelerate your own work.

I like Dell computers tagline of: “It’s a you-multiplier.”

Customer research synthesis, competitive analysis, PRD drafting, experiment design, data analysis, all of these are dramatically faster with AI assistance. PMs who aren’t using AI in their daily workflow are leaving massive productivity on the table.

The skill isn’t prompting. It’s knowing which parts of your work benefit from AI acceleration and which parts still require human judgment. Strategy, customer relationships, and cross-functional trust can’t be automated. Research synthesis, first-draft writing, and data analysis absolutely can.

22. Product Evangelism

Your product needs a champion, and that’s you. The skill is inspiring genuine excitement in your team, your stakeholders, and your customers without crossing the line into hype.

The best product evangelists I’ve seen lead with the customer problem, not the product solution. “Let me tell you about a pastor who spent 12 hours preparing a single sermon because our tools weren’t good enough” hits harder than “let me show you our new feature.”

23. Managing Your Energy, Not Just Your Time

PM burnout is real. The role pulls you in every direction: stakeholder meetings, customer calls, sprint planning, strategy reviews, fire drills. You can optimize your calendar perfectly and still burn out.

The skill is recognizing which activities give you energy and which drain it, then structuring your week accordingly. For me, customer conversations and strategy work are energizing. Back-to-back status meetings are draining. I protect my calendar accordingly.

24. Continuous Learning

The product management discipline is evolving rapidly. The frameworks that worked 3 years ago might not work today. The best PMs read broadly, attend selectively, and most importantly apply what they learn immediately.

Books that have shaped my thinking: Inspired by Marty Cagan, Continuous Discovery Habits by Teresa Torres, The Lean Startup by Eric Ries, Escaping the Build Trap by Melissa Perri, and Chief Customer Officer 2.0 by Jeanne Bliss. But reading without applying is just entertainment.

25. Intellectual Humility

This might be the most important skill on the entire list. The willingness to say “I was wrong” or “I don’t know” is what separates PMs who keep growing from ones who plateau.

Every strong opinion you hold about your product, your customers, or your market should come with an asterisk: “based on what I know right now.” New data should change your mind. Customer feedback that contradicts your hypothesis should make you curious, not defensive.

The best product managers I’ve worked with hold their strategies with conviction AND their assumptions with humility. That balance is the whole game.

The Thread That Connects All 25

If I had to distill all of these into a single principle, it would be this: the best product managers are relentlessly curious about their customers and brutally honest about what they don’t know.

Every skill on this list is either about understanding customers more deeply or making better decisions with incomplete information. That’s the job. Everything else is just technique.

The good news? Every one of these skills is learnable. None of them require a specific degree, a specific title, or a specific number of years in the role. They require intentional practice and the willingness to be uncomfortable while you’re learning.

Start with the ones where you have the biggest gap. Work on them deliberately. And be patient with yourself. The best PMs I know are still working on all 25.

Frequently Asked Questions

What is the most important skill for a product manager?

Deep customer knowledge is the foundational skill that enables everything else. Without a genuine understanding of your customers, their workflows, pain points, and goals, no amount of strategic thinking, technical literacy, or stakeholder management will produce great products. Build a habit of weekly customer conversations and the other skills become dramatically more effective.

How do product managers use AI in 2026?

Product managers use AI primarily for research acceleration like synthesizing customer interviews, generating competitive intelligence, drafting PRDs and experiment hypotheses, and querying data with natural language. The key skill is knowing which tasks benefit from AI assistance (research, analysis, first drafts) and which still require human judgment (strategy decisions, customer relationships, cross-functional trust-building).

What technical skills do product managers need?

Product managers don’t need to code, but they need enough technical literacy to have meaningful conversations with engineering. This includes understanding APIs, database constraints, deployment processes, and architectural tradeoffs. The goal isn’t to make technical decisions, it’s to ask informed questions and understand the implications of technical choices on product capabilities and timelines.

How do you transition into product management?

The most common entry points are from engineering, design, data analytics, or customer-facing roles like support or sales. Each background brings a natural strength: engineers bring technical depth, designers bring user empathy, analysts bring data fluency, and customer-facing roles bring direct insight into user pain points. Focus on building the skills in whichever category you’re weakest. Most transitions fail not because of lack of domain knowledge, but because of gaps in communication, strategic thinking, or customer understanding.

Posted on

The 10 Product Strategy Mistakes I Keep Seeing (After 10+ Years in SaaS)

An enamel pin about Product Management

I’ve made every one of these mistakes. Some of them more than once. Product strategy reads well in a blog post, but in practice it’s a minefield of competing priorities, stakeholder pressure, and the constant temptation to say yes to everything.

After more than a decade leading product and growth for SaaS companies – including subscription products serving millions of users – I’ve developed a pretty reliable list of strategy mistakes that kill momentum. Not the theoretical kind you read about in business school. The real kind. The ones that cost you quarters.

Here are the 10 pitfalls I keep coming back to, the ones that have cost me the most time, energy, and momentum over the years.

What is Product Strategy, Really?

Before we get into the mistakes, let’s get aligned on what product strategy actually is – because the lack of a shared definition is often the first problem.

Product strategy is the set of choices that connect your company’s vision to the work your team does every day. It answers three questions:

  1.  Who are we building for? (target audience)
  2.  What problem are we solving for them? (value proposition)
  3. How does this create value for the business? (business model)

Marty Cagan, author of Inspired and founding partner at Silicon Valley Product Group, puts it simply: strategy is about deciding which problems are worth solving. Roman Pichler frames it as the path to your product vision – the high-level plan for achieving your goals.

The important thing is that strategy is about CHOICES. Not a roadmap. Not a feature list. Choices about what you’ll do, and more importantly, what you won’t do.

With that foundation, here are the 10 mistakes that undermine those choices.

Mistake 1: Confusing Activity with Progress

This is the one that gets almost everyone. You ship a feature. Then another. Then another. Your release notes look great. Your team feels productive.

But the metrics aren’t changing.

I’ve lived this. We shipped feature after feature and our conversion numbers stayed flat. Lots of effort, but no forward motion. The problem was that we were building things that were nice to have, not things that moved the needle.

This is what the Jobs-to-be-Done (JTBD) framework helps you avoid. When you understand the actual job your customer is hiring your product to do, it becomes much easier to evaluate whether a feature advances that job or just adds noise. Clayton Christensen’s insight was that customers don’t buy products – they hire them to make progress. If your feature doesn’t help the customer make progress on their core job, it’s activity, not progress.

How to avoid it: Before greenlighting any feature, ask “which metric does this move, and by how much?” If the team can’t answer that clearly, the feature isn’t ready to build. This is easy to say, but extremely difficult to do. Use a prioritization framework like RICE scoring (Reach, Impact, Confidence, Effort) to force the conversation beyond gut feel.

Mistake 2: Strategy by Consensus

There’s a version of inclusive leadership that sounds great in theory but kills strategy in practice. You bring everyone to the table. You gather input. You synthesize. You try to find a path that makes all stakeholders happy.

… and you end up with a strategy that offends no one and inspires no one.

Real strategy requires choices. Hard ones. The kind where someone in the room won’t like the answer. If your strategy document doesn’t explicitly state what you’re NOT doing, it’s a wish list.

This is what killed products like Google+. Google had the engineering talent, the distribution, and the resources to build a social network. But the strategy tried to be everything to everyone – a Facebook competitor, a Twitter alternative, an identity platform, a photo sharing service. No hard choices were made and the product sadly died a slow death by committee.

How to avoid it: I’ve learned (the hard way) that my job is to make everyone feel heard, synthesize the inputs, make a clear decision, and then communicate the reasoning. People can disagree with a well-reasoned decision, what they can’t work with is ambiguity. Write down your strategy in one page. If it doesn’t fit on one page, you haven’t made enough choices yet.

Mistake 3: Copying the Competition

Your competitor launches a feature. Your sales team forwards the announcement. Your CEO asks “why don’t we have this?” And suddenly your roadmap has a new top priority that wasn’t there yesterday – classic!

I’ve fallen into this trap more than I’d like to admit. You absolutely should know what your competitors are doing. The real risk is letting their decisions drive YOUR strategy.

When you copy a competitor’s feature, you’re solving for THEIR customers with THEIR context.

You don’t know why they built it. You don’t know if it’s working. You don’t know if they’re about to kill it. You’re making a strategic bet based on a press release.

Gibson Biddle, former VP of Product at Netflix, uses what he calls the DHM Model – Delight, Hard-to-Copy, and Margin-Enhancing. The “hard-to-copy” piece is key but with AI it’s getting more difficult. If your strategy is just replicating what competitors build, you’ll always be behind AND you’ll never build anything that’s uniquely valuable to your users.

How to avoid it: Understand what problem the competitor is trying to solve, then ask whether YOUR users have that same problem. Sometimes they do, and then you should solve it in a way that fits your product, your architecture, and your users’ workflow. Sometimes they don’t, and the right answer is “we’re not building that” – Jeff Bezos has a great framework for this kind of decision.

Mistake 4: Ignoring the Metrics That Actually Matter

Vanity metrics are seductive. Page views are up! Sign-ups are growing! App downloads hit a new record!

But if your churn rate is climbing at the same time, you’ve got a leaky bucket. And no amount of top-of-funnel growth fixes a retention problem.

I’ve been in situations where the dashboards looked green but the business was struggling, and situations where the top-line numbers looked concerning but the underlying health was strong. The difference was which metrics we were watching.

This is what the North Star Metric concept helps solve. Your North Star is the single metric that best captures the core value your product delivers to customers. For Spotify, it’s time spent listening. For Airbnb, it’s nights booked. For a subscription SaaS product, it might be weekly active usage or feature adoption depth.

How to avoid it: For any subscription product, the metrics that matter are: how many people start a trial, how many convert to paid, how many cancel, and what’s the net change. Everything else is context. Build your dashboard around these numbers first, THEN add the supporting metrics that explain why they’re moving.

Mistake 5: Trying to Serve Everyone

This one is especially hard in mission-driven organizations. You WANT to help everyone. Every user segment seems important. Every use case feels valid.

But trying to serve everyone equally means serving no one well.

Your onboarding can’t be optimized for beginners AND power users simultaneously. Your pricing can’t be accessible to individuals AND competitive for enterprises without compromise.

Trying to serve everyone equally means serving no one well.

Kodak learned this the hard way. They saw digital photography coming but tried to straddle both worlds – maintaining their film business while half-heartedly investing in digital. They served neither audience well, and a company that once dominated an entire industry filed for bankruptcy in 2012.

How to avoid it: The best products I’ve used (and the best products I’ve built) made clear choices about who they were for. They explicitly prioritized one audience and designed everything around their needs first. When you do that well, other segments often benefit anyway, from a focused, coherent product rather than a compromised one. Define your primary persona. Write it on the wall. When someone asks “but what about this other segment?” you have your answer ready.

Mistake 6: Having No Strategy at All

This sounds obvious, but it’s shockingly common. My last few roles I’ve called “The Fixer” because years of the company running hard has caused them to lose their focus and they suddenly realize they don’t have a strategy. They have a roadmap. They have a backlog. They have quarterly goals. They ship things on time.

But there’s no unifying thesis about WHERE the product is going and WHY.

Roman Pichler calls this the most common product strategy mistake he encounters. Teams jump straight from vision to execution without the strategic layer that connects them. The result is a collection of features that individually make sense, but collectively don’t tell a coherent story.

How to avoid it: Your strategy should be a testable hypothesis, not a document that lives somewhere on the server. Try this format: “We believe that [target audience] struggles with [problem]. If we build [solution], we’ll see [measurable outcome] within [timeframe].” If you can’t fill in those blanks, you don’t have a strategy yet. You have a to-do list.

Mistake 7: Treating Strategy as Static

You spend weeks crafting the perfect strategy document. Leadership signs off. The team aligns. You print it out and pin it to the wall.

Six months later, the market has shifted, a competitor has launched something unexpected, and your customers are telling you something you didn’t anticipate. But the strategy is “locked.”

Eric Ries built the entire Lean Startup methodology around this problem. The Build-Measure-Learn loop isn’t just for startups – it’s for any team that operates in uncertainty, which is literally every product team. Your strategy should have built-in checkpoints where you evaluate whether your assumptions still hold.

How to avoid it: Set quarterly strategy reviews. Not annual planning sessions where you redo everything – lightweight reviews where you ask: “What have we learned? What’s changed? Do our bets still make sense?” The best strategies are living documents, not manifestos. Jeff Bezos distinguishes between “one-way door” decisions (irreversible, deliberate slowly) and “two-way door” decisions (reversible, move fast). Most strategic choices are two-way doors. Treat them that way.

Mistake 8: Skipping Validation Before Committing

You have a great idea. The team is excited. Leadership is bought in. You go straight to building.

Three months later, you launch to silence. Customers don’t want it, don’t understand it, or already solved the problem another way.

I’ve seen this pattern destroy entire quarters. The excitement of a new idea creates momentum that skips right past the “should we build this?” question and lands on “how do we build this?”

How to avoid it: Before committing engineering resources, validate the problem AND the solution. Talk to 5-10 customers. Run a fake door test. Build a prototype and put it in front of real users. Teresa Torres’ Continuous Discovery framework calls this “opportunity solution trees” – mapping the opportunity space before jumping to solutions. The cost of 2 weeks of discovery is nothing compared to 3 months of building the wrong thing.

Mistake 9: Siloed Strategy Without Cross-Functional Input

Product writes the strategy. Engineering learns about it at spring planning. Design gets brought in when wireframes are needed. Marketing finds out at launch.

This isn’t strategy. It’s a relay race where nobody can actually see the finish line.

The best product strategies I’ve been part of were shaped by engineering constraints, design insights, and market intelligence from day one. Your engineers know what’s technically feasible and where the architecture creates opportunities. Your designers have insights about user behavior that data alone can’t capture. Your sales and support teams hear objections and pain points every day.

How to avoid it: Include engineering and design leads in strategy formation, not just execution. Share customer research broadly. Bring it up in meetings regularly. Make your strategy document accessible to everyone on the team, not locked into a leadership slide deck. When people understand the WHY behind the strategy, they make better decisions at every level.

Mistake 10: Being Unrealistic About Execution Capacity

This is the mistake that ties all the others together. You have a clear strategy. You’ve validated the direction. You’ve made all the hard choices about what to build.

Then you commit to 3x more than your team can actually deliver.

Your roadmap becomes a pressure cooker. Quality drops. Shortcuts get taken. The team burns out. And paradoxically, you end up delivering LESS than if you’d committed to fewer things done with excellence.

I’ve seen this cycle repeat across every company I’ve worked with. The ambition is always bigger than the capacity, and the gap gets filled with overtime and technical debt instead of honest prioritization.

How to avoid it: Be ruthlessly honest about how much your team can ship in a quarter. Then cut 20% from that estimate. Even writing that sounds crazy, but it must be done. Use the OKR framework (Objectives and Key Results) to limit your bets to 3-5 outcomes per quarter – not 3-5 per team, 3-5 total. Warren Buffett’s “two-list strategy” applies here: write down your top 25 priorities, circle the top 5, and treat the other 20 as your “avoid at all costs” list (avoid them entirely until the top 5 are achieved). The same logic applies to product strategy.

The Uncomfortable Truth

Product strategy is about having the discipline to say no to good ideas that don’t align with what matters most right now.

Every mistake on this list comes from the same root: the unwillingness to make a hard choice and live with the tradeoff.

Choose the right things. Decide clearly. Pick your own path. (I wrote about this focus in 5 things needed for business success.) Watch the honest metrics. Serve someone specific.

Strategy is the art of sacrifice. The sooner you get comfortable with that, the better your products will be.

Product Strategy Checklist

Before you finalize your next product strategy, run through this list:

  • Can you state your target audience in one sentence?
  • Can you articulate the core problem you’re solving for them?
  • Does your strategy explicitly state what you’re NOT doing?
  • Is every major initiative tied to a measurable outcome?
  • Have you validated your assumptions with real customers?
  • Does your team have the capacity to execute this quarter’s plan?
  • Have you set a date to review and adapt the strategy?
  • Can your entire team articulate the strategy without looking at a document?
  • Is there a clear North Star Metric everyone is aligned on?
  • Would you bet your own money on this plan working?

If you can’t check every box, your strategy still has gaps. Go back and make the hard choices.

Frequently Asked Questions

What are the most common product strategy mistakes?

The most common product strategy mistakes include confusing activity with progress (shipping features that don’t move metrics), strategy by consensus (avoiding hard choices to keep everyone happy), copying competitors instead of solving for your own users, ignoring retention metrics in favor of vanity metrics, and trying to serve every user segment equally. The root cause of most strategy failures is an unwillingness to make clear choices and accept tradeoffs.

What is the difference between product strategy and a product roadmap?

Product strategy defines WHERE you’re going and WHY. It’s about choices, tradeoffs, and the thesis behind your product direction. A product roadmap is the HOW and WHEN – the sequence of work that executes the strategy. A roadmap without a strategy is just a feature list. A strategy without a roadmap is just a vision. You need both, but strategy comes first.

How do you create an effective product strategy?

An effective product strategy begins with a clear understanding of your target audience, the problem you’re solving, and how solving it creates business value. Frameworks like Jobs-to-be-Done help identify what customers actually need. Validate your assumptions through customer discovery before committing resources. Set a North Star Metric to track progress. Review and adapt quarterly. Most importantly, be explicit about what you will NOT do – that’s ultimately where the real strategy lives.

How often should you update your product strategy?

Product strategy should be reviewed quarterly and updated when market conditions, customer needs, or business goals change significantly. It should NOT change weekly based on competitor moves or stakeholder requests. The best approach is setting lightweight quarterly checkpoints where you evaluate whether your core assumptions still hold, while keeping the overall strategic direction stable enough for the team to execute with confidence.

Posted on

15 quotes to stir Courageous Leadership

I’ve been collecting quotes on courageous leadership for a while now. The kind that don’t just sound good on a poster but actually rearrange how you think about showing up for the people in front of you.

Here’s the question that started this collection:

Can an individual affect their society by simply, courageously caring for the individual in front of them enough to see who they truly are and encourage them into that identity?

I believe the answer is yes. And these 15 quotes have shaped how I try to live that out.

On Seeing People

  1. How many of us are stuck in the daily grind of survival? If you were to plot yourself on Maslow’s Hierarchy of Needs, where would you be today? Most of us live at level 3, but David Whyte challenges us to step beyond, to risk being truly seen and to see others as they really are.

  2. “The greatest thing a human soul ever does in this world is to see something and tell what it saw in a plain way. Hundreds of people can talk for one who can think, but thousands can think for one who can see.” – John Ruskin

  3. “Attention is the rarest and purest form of generosity.” – Simone Weil. Constant distraction makes full presence rare. Choosing to be fully present with another person is an act of courage.

On Leading with Vulnerability

  1. “Vulnerability is not winning or losing; it’s having the courage to show up and be seen when we have no control over the outcome.” – Brene Brown. This applies to every hard conversation you’re avoiding right now.

  2. “The only thing more unthinkable than leaving was staying; the only thing more impossible than staying was leaving.” – Elizabeth Gilbert. Sometimes the most courageous leadership decision is the one that costs you the most personally.

  3. “Have I not commanded you? Be strong and courageous. Do not be afraid; do not be discouraged, for the Lord your God will be with you wherever you go.” – Joshua 1:9. Courage is the decision that something else matters more.

On Doing the Hard Thing

  1. “The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood.” – Theodore Roosevelt. Courageous leaders lead from inside the mess.

  2. “You gain strength, courage, and confidence by every experience in which you really stop to look fear in the face. You must do the thing which you think you cannot do.” – Eleanor Roosevelt

  3. “Courage is not the absence of fear, but rather the judgment that something else is more important than fear.” – Ambrose Redmoon. I come back to this one regularly. Especially when I’m about to say something in a meeting that I know won’t be popular but needs to be said.

On Serving Others

  1. “Everybody can be great because anybody can serve. You don’t have to have a college degree to serve. You don’t have to make your subject and verb agree to serve. You only need a heart full of grace and a soul generated by love.” – Martin Luther King Jr.

  2. “The best way to find yourself is to lose yourself in the service of others.” – Mahatma Gandhi. The leaders who’ve had the deepest impact on my life were the ones who showed up for me when it cost them something.

  3. “Do nothing out of selfish ambition or vain conceit. Rather, in humility value others above yourselves.” – Philippians 2:3. This is the hardest standard of leadership I know. And the most transformative when you actually live it.

On Persistence

  1. “Success is not final, failure is not fatal: it is the courage to continue that counts.” – Winston Churchill

  2. “Courage doesn’t always roar. Sometimes courage is the quiet voice at the end of the day saying, ‘I will try again tomorrow.’” – Mary Anne Radmacher. This one resonates with anyone who’s had a week where nothing went right but showed up on Monday anyway.

  3. “Let us not become weary in doing good, for at the proper time we will reap a harvest if we do not give up.” – Galatians 6:9. The most courageous thing you might do today is simply not quit.

The Thread

Courageous leadership is the daily decision to see people, serve them, and keep going when it would be easier to stop.

That’s available to anyone, in any role, at any level. You don’t need a title to lead courageously. You just need to care enough about the person in front of you to show up fully. And then do it again tomorrow.

View all posts