Your Strategy names one audience, but weak evidence describes another


Your Strategy names one audience; weak evidence describes another

PUBLISHED

Sep 24, 2026

READ ON

​HERBIG.CO​

​Dear Reader,​

One of the most common questions that came up in my recent Strategy to Execution workshop at the ProductLab conference revolved around intentional strategic audiences vs. reactive chasing of new business.

Many teams either operate where the company focuses on all customers of a given market (i.e., "all lawyers") or throw a wishful-thinking segment out there.

In a warehouse of productivity software context, one thing I ask teams to consider is whether average task completion time would look different for their chosen audience. That insight could support a central assumption in the strategy, so understanding whom it described mattered for deciding how much confidence to put in it.

Choosing a specific audience should help you decide which problems to solve and which opportunities to say no to. But you can lose that focus when you start using whatever research or analytics are available to support your choices. The audience in the strategy stays specific, while the insights informing your priorities become increasingly broad.

For example, a team working on expense-reporting software might choose to focus on employees submitting their first expense report. Feedback from frequent users about how tedious it is to upload receipts could suggest that bulk uploading is worth pursuing. But first-time users might struggle with understanding which expenses they can claim in the first place. Making it easier to upload more receipts would do little to reduce that uncertainty.

Both are potentially valuable problems to solve. Your audience choice should help you decide which one deserves your attention, and your discovery needs to establish whether that problem exists for the people you have chosen to focus on.

Remember that a strategic audience focus does not necessarily mean you won't make solutions available to other audiences as well. But you will use insights from this strategic segment to prioritize your efforts and evaluate the success of solutions based on audience-specific metrics.

In our expense-reporting example, that means looking at whether first-time users can successfully submit their expenses. An improvement in completion time across all users could come from making life easier for experienced users, while the people you intended to help continue to struggle.

Of course, you might already have useful insights about your chosen audience within a broader study or dataset. I would start by looking at who contributed to those findings before deciding to run more research. And if the evidence repeatedly points to a more valuable problem in another segment, that can be a reason to revisit your strategic choice.

When reviewing your next strategy iteration, pick one proposed priority and look at the strength of the evidence supporting it. Can you trace those insights back to the audience you want to create value for? If you can't, checking whether the problem exists for that audience gives you a concrete starting point for discovery.

Thank you for Practicing Product,

​Tim​

Ways we can work together

1️⃣ Order my book: Real Progress: How to Connect the Dots of Product Strategy, OKRs, and Discovery, which readers call "a practical guide you can return to again and again."

2️⃣ Learn about my in-house training and coaching options for product teams, with a focus on creating strategic clarity, setting pragmatic goals, and implementing real-life discovery practices to reduce risk

​

If you consume one thing this week, make it this...

We’re a Data-Driven Company. We Test Everything.

Martin Eriksson shares an example from his time at Huddle where customers wanted the individual features they tested. What remained untested was whether those customers wanted all of those features together from Huddle. I think this is a useful example of why we need to examine the assumptions behind our strategic choices with the same attention we give to individual solutions.

Who is Tim Herbig?

As a Product Management Coach, I guide Product Teams to measure the real progress of their evidence-informed decisions.

I focus on better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.

Product Practice Newsletter

1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes. Explore my new book on realprogressbook.com

Read more from Product Practice Newsletter

Product Practice #432 Your Product Strategy Can Be Focused Without Covering Everything PUBLISHED Oct 29, 2026 READ ON HERBIG.CO Dear Reader, If your Product Strategy prioritizes paid customers, what happens to everyone using your product for free? Aakash Gupta raised this question in our Product Growth podcast conversation. At Apollo, the strategic focus was on paid users. But he couldn’t ignore everyone else. It’s a useful tension. A strategy needs to concentrate your effort, while your team...

Product Practice #431 Linked Better Practices over Stacked Best Practices PUBLISHED Oct 23, 2026 READ ON HERBIG.CO Dear Reader, Last week, Julia and I taught our new The AI-Powered PM: From Hype to Agentic Application workshop, and I wanted to share my top three takeaways across our material and participants' takeaways: #1 Effortless Agentic Building Enables True Product Creativity Once everyone locked in on the fundamental agent components of user prompt, system prompt, context, and output,...

Product Practice #430 How to Think About Product Strategy in the Age of AI PUBLISHED Oct 16, 2026 READ ON HERBIG.CO Dear Reader, Two weeks ago, I had the incredible opportunity to be on Akash's Product Growth Podcast. Now that the episode is out, I can finally share it with you as well. I typically don't put podcast episodes front and center in this newsletter, but since this is more of a 1-hour AI Product Strategy Masterclass than an audio-only podcast, I think it's one of the best pieces of...