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
Why you should treat Prototypes as Decision-Making Tools
How to treat Prototypes as Decision-Making ToolsDear Reader, You've probably heard the statement "With the friction of building nearing zero, it's even more important to have conviction about what to build and why" before. Truth is, this reduction in friction does not just apply to software in production. It also applies to the methods you use before that. The comparison I see to "pre-AI" ways of working is that teams, which were good at or limited to qualitative interviews, tried to reduce the uncertainty around each Discovery question with, you guessed it, interviews. I call these dogmatic defaults. A recent article by Ravi Mehta prompted (pun intended) me to revisit this idea - only this time with prototypes. "Prototyping is fun — and it’s easy to get pulled into crafting the perfect thing. It’s critical to remember that prototypes aren’t the deliverable; they’re a tool for making better and faster decisions." With everyone on your team (and in the boardroom) getting excited about prototyping with Lovable, V0 & Co., it's tempting to prototype every uncertainty you're trying to reduce. But that's dogmatic defaults all over again - just in a different color. We have to remember what prototypes can help you learn:
They're also fantastic alignment tools since a visual idea can replace lengthy written and spoken discussions. What prototypes can't tell you They won't get you to informed conviction about scaled adoption or willingness-to-pay. Not because the tools aren't good enough yet, but because those questions require a different category of evidence. Prototype reactions are attitudinal. Adoption and willingness-to-pay are behavioral. Someone saying "yeah, I'd use this" while clicking through your Lovable prototype in a 30-minute interview tells you almost nothing about whether they'll actually trade their time, attention, or money for it when the moment of truth arrives. Humans are notoriously bad at predicting their own future behavior. No prototype, no matter how fast you produced it or how polished it is, changes that. The underlying principle Every discovery question deserves a method that matches it. The temptation with any new tool is to let the hammer pick the nail. The question isn't "Should we prototype this?" The question is "What are we trying to decide, and what's the lightest, most honest way to get evidence for it?" Sometimes that's a prototype. Sometimes it's a fake door. Sometimes it's a pricing page with a pre-order button. Sometimes it's still a good old interview. The AI era doesn't make prototypes the answer to everything. It just makes them cheap enough to be the answer to more things than before. Which is why choosing when not to prototype is now a skill worth sharpening. Thank you for Practicing Product, Tim 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
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...
Product Practice #402 Product Discovery forInternal Enabler Teams PUBLISHED Apr 2, 2026 READ ON HERBIG.CO Dear Reader, Because the customers of your product just sit three desks away, you might think you can just "talk to them." And that's precisely what often leads to the low adoption of better product practices among product teams working on internal products (also sometimes called Enabler Teams). And why, when a user has a company email address, it is likely nobody's doing discovery on...