Join us on the porch for our series on Product Manager Power Skills. These are the skills that help good product managers become great ones. They stay valuable across tools, processes, and product types, and building them can help you grow your impact and your career.

What happens when a product manager gets really good at moving fast… but stops questioning their own thinking? In this episode, Todd Blaquiere, Ryan Cantwell, and Joe Ghali dig into critical thinking as a power skill for PMs and why it matters more than ever in a world full of AI, strong opinions, and easy answers. They break down how better thinking helps product managers ask sharper questions, spot weak assumptions, consider other points of view, and catch second-order consequences before they turn into expensive mistakes. They also get practical about how to use AI the right way: not as a replacement for judgment, but as a tool to challenge your thinking and make your decisions stronger.

If you want to make better product decisions, earn more trust, and avoid the kind of mistakes that look obvious in hindsight, pull up a chair on the porch, pressure-test your own thinking, and give this one a listen.

What Critical Thinking Means
[00:00] Power skills series – Critical thinking opens the new Product Porch power skills series.
[01:13] Working definition – “Thinking about thinking” as a path to better judgment.
[01:53] Reasoning model – Paul and Elder framework connects directly to product work.

Better Product Decisions
[03:55] Point of view – Strong decisions require multiple stakeholder perspectives.
[06:17] Consequence mapping – First-order and second-order effects shape product outcomes.
[08:19] Assumption testing – Five whys helps expose weak reasoning early.
[09:10] Thinking discipline – Frameworks and discovery habits create more defensible decisions.

Standards and Maturity
[11:27] Intellectual standards – Clarity, accuracy, relevance, logic, and fairness improve product thinking.
[15:26] “So what?” test – Data needs meaning, not just volume.
[20:38] Thinker stages – PM growth moves from unreflective thinking to practiced judgment.
[23:02] PM maturity range – Most product managers fall between challenged and practicing thinker.

AI and Critical Thinking
[22:27] AI as challenger – AI can pressure-test ideas and surface blind spots.
[23:47] Work slop risk – Polished output can hide shallow thinking.
[26:58] High AI literacy – Better outcomes come from critical use, not passive reliance.
[29:54] Final judgment – Product decisions still require human context and trade-offs.

Building the Skill
[32:27] Practicing thinker habits – Better questions, broader evidence, stronger reasoning.
[33:34] Postmortem habit – Retros reveal where judgment held up or broke down.
[35:35] Power skill payoff – Critical thinking moves PMs from good to great.
[37:57] Daily self-check – Competing evidence and opposing views strengthen decisions.
[38:27] Leadership example – Teams lose the skill when leaders stop modeling it.

Help keep the Product Porch lights on by giving at https://www.patreon.com/TheProductPorch

Join our email list and never miss an episode at theproductporch.com

So now you have defined the starting point and the ending point. Check out Part 1, “Decisions in Uncertainty (Part 1): When ‘Go Build This’ Is All You Get.” What do you do next? In part two of this conversation, Todd Blaquiere and Ryan Cantwell define the messy middle and give you the playbook for making the call when certainty is still out of reach.

They walk through how to use a decision-making rubric, identify the highest-risk assumption, and test what matters most before a team sinks too much time into the wrong thing. They also dig into one of the hardest parts of product work: how to read unclear signals, weigh imperfect evidence, and know when you have enough confidence to stop researching and start recommending.

If part one was about slowing down long enough to get clear, this episode is about what it takes to move forward anyway. Pull up a chair on the porch and know how to make the call.

What should a product manager do after getting clear on the outcome?
[00:00] Part two setup - Episode moves from clarity to decision-making
[01:01] Why this still feels hard - Clear requests can still hide unclear success
[02:19] What defines the target - Business outcomes and customer outcomes shape the call
[04:05] Why success must be defined - Better decisions start with clear success criteria

How can a product manager make a better decision when the answer is not obvious?
[05:13] Why a rubric helps - Shared criteria make hard calls easier
[06:04] What goes into a rubric - Value, demand, fit, timing, and right to win
[07:50] Why weighting matters - Some criteria matter more than others
[08:08] Why confidence matters too - Weak evidence should not count the same as strong evidence
[11:43] What a rubric is really for - Alignment matters more than fake objectivity

How can a product manager figure out what to test first?
[13:07] What the “monkey” means - The highest-risk assumption can kill the idea
[13:32] How to move faster - Tiny Acts of Discovery focus on the biggest risk first
[14:27] Example: missing data - No data can mean no product
[15:31] Example: willingness to pay - Real pain does not always lead to real revenue

How can a product manager test assumptions without fooling the team?
[19:32] Say versus do - Real behavior matters more than polite feedback
[19:54] Why direct asks work - Simple requests can reveal the truth faster
[20:33] What commitment looks like - Pre-orders, signups, and emails show stronger intent
[21:02] What to avoid - Friendly audiences can give false confidence
[22:12] Why the answer stays messy - Evidence is rarely perfect or complete

How does a product manager know when it is time to make the call?
[23:04] How to use the evidence - Outcomes, rubrics, assumptions, and tests work together
[24:07] Why a second lens helps - Another prioritization method can expose weak thinking
[25:01] What “enough confidence” looks like - Full certainty usually never comes
[25:27] When the job changes - Research mode must turn into recommendation mode
[29:06] How to present the call - Start with the ask, the risk, the test, and the recommendation
[30:22] What leaders want first - Executive audiences want the answer up front
[36:00] Who owns the decision - Judgment cannot be handed to someone else

Help keep the Product Porch lights on by giving at https://www.patreon.com/TheProductPorch

Join our email list and never miss an episode at theproductporch.com

Have you ever been told to “go build this” and felt that little pit in your stomach because you were not totally sure what success even meant? In this episode, Todd Blaquiere and Ryan Cantwell dig into one of the most uncomfortable parts of product management: making decisions when the path is unclear and the pressure to move is high. They talk through why vague direction creates misaligned expectations, how product managers get trapped into building motion instead of outcomes, and what it takes to slow down long enough to clarify business outcome, customer value, and the real risk underneath the request.

Along the way, they share stories of getting it wrong, and dig into why so many product managers freeze or default to the safest path, and offer a more practical way forward.

_If you have ever felt stuck between vague direction and the pressure to act, pull up a chair on the porch, rethink how you make decisions under uncertainty, and start building the judgment that sets great product managers apart.__

What should a product manager do when the direction is vague but action is expected?
[00:00] Episode framing - Uncertainty and pressure to act set up the core problem
[00:57] Why this feels hard - Product managers feel overwhelmed when the path is unclear
[02:50] Two kinds of uncertainty - Empowered decision-making versus unclear direction with no real guidance

Why is “just go build it” such a dangerous trap?
[03:11] Blind execution trap - Following the request without understanding the outcome creates risk
[04:04] LA Times example - Building the thing without asking why leads to misalignment
[05:27] Hardware example - Big expectations show up before customer, problem, or business context is clear
[06:29] False progress - Busy work, polished decks, and shallow analysis can hide the real problem

How should a product manager clarify what success actually means?
[09:33] Start with why - Better decisions begin with understanding the outcome behind the request
[10:34] Curiosity over confrontation - Better questions create alignment without triggering defensiveness
[13:06] Outcome alignment - Business goals and stakeholder goals need to be made explicit
[15:55] Playback and check-ins - Repeating understanding and revisiting direction reduces drift

What makes a good decision framework when certainty is impossible?
[18:43] Business outcome and customer value - Both sides are needed to make strong product decisions
[20:26] Specific customer definition - Clear value starts with identifying the exact customer
[23:27] Business context - Portfolio gaps, business risk, and cost of inaction sharpen the goal
[24:20] Partial certainty - Strong product decisions often happen before perfect clarity exists
[26:12] Working rubric - Outcomes and value become a hypothesis for what to test

How should a product manager reduce risk before committing to a path?
[28:09] Monkey on the pedestal - The riskiest assumption should be tackled first
[29:35] Hard thing first - Early validation reduces waste and improves confidence
[32:53] AI feature scenario - Sales pressure becomes a practical example of reframing a request into assumptions and tests
[38:19] Discovery patterns - Lost deals, customer segments, and recurring signals help focus investigation
[41:15] Closing takeaway - Simple mental models help product managers move forward under uncertainty

Help keep the Product Porch lights on by giving at https://www.patreon.com/TheProductPorch

Join our email list and never miss an episode at theproductporch.com