3 Things to Put into Your Next Strategy Document


3 Things to Put into Your
Next Strategy Document

PUBLISHED

Feb 27, 2026

READ ON

HERBIG.CO

​Dear Reader,​

The most effective strategy document I've seen doesn't worry about the looks or format. Whether it's a scrappy Google Doc or a fancy Miro template, what matters is the quality and cohesiveness of the information it contains.

Make sure what you cover aligns with your company's expected standards to ensure stakeholder understanding and, consequently, buy-in. But make sure you don't skip these parts:

#1 The Basics

You know the drill. Your Product Strategy has a problem to solve.

And, to do that, you need to answer a few key questions. There are a gazillion versions of these out there, but all mostly center around the same core:

  • How does this connect to Company Strategy, Product Vision, and Business Goals?
  • For which audience (and their adjacent roles) are we trying to solve a problem? What is the problem? What else is solving that problem?
  • What will we provide as a solution? What makes our solution more likely to get chosen by the audience? How will we put it into people's hands?

The answers to these questions need to reinforce each other. TikTok ads won't help you reach people aged 70+. You're not just competing against similar software or services, but also against Excel and ChatGPT.

#2 Measurable Definitions of Success

Struggling to measure if the strategy is working?

Can you answer the simple question: "Which three metrics would show that this strategy choice has worked in the next 12 months?" Make them specific. Not just "Revenue" but "Revenue from Industry xyz." Then, use these to create influenceable team goals.

#3 "Stupidity-Flipping" Your Strategy Choice

A real strategy choice should feel slightly uncomfortable. If the opposite of your choice would be plain stupid, it might not be a real choice at all (thank you, Roger Martin). That's the stupidity flip. A simple way to pressure-test whether your strategy is actually saying something.

Bonus: "What's at Stake?"

To point out the relevance of your choices and urgency to act, outline the consequences of your product not adapting to a changing landscape. Use a simple formula: If we don't act → [core risk] → which means → [downstream consequence that hits something people already care about].

If we don't establish a clear wedge in this category → we become a feature, not a platform → which means customers adopt us tactically but never build workflows around us, and we're always one competitor's roadmap update away from being replaced.

If we don't earn repeat purchase behavior early → the unit economics of acquisition never close → which means we're permanently dependent on paid channels to drive revenue, and the business model only works if we keep spending.

Thank you for Practicing Product,

Tim

Get my Book

⭐️⭐️⭐️⭐️⭐️

"What makes Real Progress particularly special to me is that it’s not just a source of inspiration or a collection of ideas, but a practical guide you can return to again and again – no matter what area you’re currently focusing on."

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

In Praise of Guessing

When teams set Key Results without baselines, they’re making predictions about how the world works. “If we do this thing, we think this number will move by this much.” Then they ship, measure, and learn. Some teams hit their Key Results. Many don’t. But here’s what’s interesting: over time, the experienced ones get eerily good at predicting what will move the numbers. They look at a proposed feature and say, “That won’t work,” or “That’s going to have a bigger impact than you think.” That’s not magic. It’s compressed experience. It’s the result of making predictions, being wrong, paying attention, and updating their mental models over and over again.

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 #405 How to treat Prototypes as Decision-Making Tools PUBLISHED Apr 23, 2026 READ ON HERBIG.CO From Strategy Choice to Planned Experiments in One Workshop In my upcoming live remote workshop From Strategy to Discovery, I take you from sharpening your Product Strategy, to defining leading indicators for measuring progress, all the way to prioritized assumptions you need to derisk end-to-end. Three 4h Live Sessions - Lifetime Material and Recording Access - Real Results Join...

Product Practice #404 Linked Better Practices over Stacked Best Practices PUBLISHED Apr 16, 2026 READ ON HERBIG.CO Dear Reader, During a recent webinar, someone asked a question I had to think about a bit longer: "What do you do when your strategy is still early, and you're not sure if it's right?" The answer that popped into my head was based on an incredible piece of advice (or admission) I received from a former boss 10+ years ago: No one knows if their strategy is right in the beginning,...

Product Practice #403 Linked Better Practices over Stacked Best Practices PUBLISHED Apr 9, 2026 READ ON HERBIG.CO Dear Reader, During my last webinar on Connect Strategy, Goals, and Discovery with Progress Wheel, I asked people which part of their work is most prone to Alibi Progress. Almost everyone who chimed in named OKRs. And that's because many OKR cycles start the same way for teams: Someone opens a spreadsheet, fills in three to five semi-random metrics, and picks a value that isn't...