Éamon Cullen

Walks through seven steps to recover when a startup has built a product no one wants, including listening, iterating, and pivoting like Climate Corporation did from WeatherBill. Useful when the team is staring at flat metrics and needs a path to product-market fit.

Tom Greever

Tom Greever's IDEAL framework (Identify, Describe, Empathize, Lock) for responding to design feedback, paired with four categories: business, design, research, limitations. Useful when a designer wants a script for hard stakeholder questions.

Briana Bui

Reflects on a stakeholder meeting where defending design choices was hard, and shares the muscle designers need to build to articulate why a design is right. Useful when a designer is unsure how to defend their work in reviews.

Antonio da Fonseca Neto

Argues that knowing when to sunset a product is as important as launching one, and walks through how to gather data and buy-in before pulling the plug. Useful when a product is fading and the team has to choose between investing more or shutting it down.

Melanie Hambarsoomian

Explores how to balance more research with shipping early to learn, and warns against both over-validating and rushing out broken work. Useful when the team is stuck deciding whether to keep testing or just release.

Akorede J. Ayanbisi

Walks through how to back design choices with app analytics and OKRs so stakeholders can buy into the decision. Useful when execs keep pushing back on design recommendations and you want a data narrative they will accept.

Edward Chechique

Argues you will rarely know the perfect design upfront, so anchor on user needs and methodically narrow choices using design thinking. Useful when designers feel paralyzed by competing trade-offs in a project.

Itay Sagie

Looks at the sunk cost trap in business decisions and how leaders break out of it to focus on future value. Useful when a team keeps defending a project because of past investment.

Finn Lawrence

Single-question framework for cofounders ("what does it look like when you win?") that surfaces hidden differences in goals and end states. Useful when a founding team is moving fast but quietly out of alignment.

Paige Lansing Valle

Weighs when to test brand positioning before going live, especially the move from strategy to creative. Useful when leadership debates spending on positioning research before approving the next launch.

Ryan Law

Ryan Law at Cobloom shows how to build, improve, and pivot a minimum viable SaaS product. Useful when a SaaS founder is unsure whether to keep iterating or change course.

SMB Services

Five steps for deciding whether feedback should make you iterate the MVP or pivot the whole idea. Useful when a team is stuck reading mixed early signals from users.

John Menard

John Menard shares hard-earned lessons on backing every design choice with clear reasoning so it survives critique. Useful when a designer needs to defend work in stakeholder reviews without taking it personally.

Phillip Hunter

Phillip Hunter writes about creating a Statement of Design Intent — a short doc that captures what a design is meant to do, and why, before pixels move. Useful when a team is starting a new project and wants a way to align on intent before investing in mockups.

Arturo Ríos

Arturo Ríos shows how mental models from many fields (psychology, statistics, economics) help designers cut through bias. Useful when a designer is making a tough call and wants extra lenses to check assumptions.

Ross Floate

Ross Floate argues that the famous 'rule of threes' — show three options to clients — leads to weak work and false choice. Useful when a designer is stuck performing options for a stakeholder and wants permission to pick one and defend it.

Reddit, Inc.

Reddit thread where designers share tactics for fighting design indecision — set time limits, use constraints, get a second pair of eyes, and ship to learn. Useful when a designer is stuck choosing between two visual options and needs honest tips from peers.

Tarun Kohli

Tarun Kohli explains how to push back on HiPPO syndrome — when the highest-paid person's opinion wins — by bringing data, prototypes, and user voice into the room. Useful when a senior leader keeps overriding design decisions and the team needs tactics that protect the work.

John F. Magee

Classic Harvard Business Review piece on using decision trees for choices. Useful when leaders face a series of either/or calls with risk.

Trilly Chatterjee

Trilly Chatterjee on first-principles thinking for product decision making. Useful when teams want to question old defaults and rebuild logic.

Roman Pichler

Roman Pichler's tips for making product decisions with stakeholders and dev teams. Useful when calls keep getting blocked by misaligned groups.

Sheekha K.

Reveals the unspoken trade-offs and politics behind product calls. Useful when new PMs are surprised by how messy real choices are.

Harpreet Singh

Presents a 'show me the money' framework for sharper decision-making skills. Useful when teams want a money-first lens for product calls.

Kurnia Sukma Adiguna

Looks at how bias creeps into PM decisions and how to spot it. Useful when teams want fairer, more honest calls.

Rohit Verma

Introduces the S.O.L.V.E.D. framework for product decision making with examples. Useful when teams want a named framework to guide tough calls.

Sam Nordstrom

Walks through mental shortcuts that help product teams decide faster under noise. Useful when teams feel stuck in analysis paralysis.

Ravi Mehta

Ravi Mehta's three pillars of product decision making: data, judgment, and conviction. Useful when PMs want a memorable model for tough calls.

Mike Mason

Mike Mason lists seven ways product teams reach decisions. Useful when teams want to compare modes like consensus, vote, or single owner.

Roman Pichler

Roman Pichler shares decision rules to make product calls more consistent. Useful when teams keep relitigating the same product choices.

Brandon Chu

Brandon Chu's guide to making good PM decisions, with rules of thumb. Useful when PMs face high-stakes calls and want clear guardrails.

Andy Healey

Andy Healey video on how PMs and designers can make better product decisions. Useful before a big planning session with stakeholders.

Rohit V.

Introduces the S.O.L.V.E.D. framework for product decision making with examples. Useful when teams want a named framework to guide tough calls.

Sam Nordstrom

Walks through mental shortcuts that help product teams decide faster under noise. Useful when teams feel stuck in analysis paralysis.

Lia Garvin

Practical guide from Google Design on running design reviews that end in clear decisions. Useful when reviews drift and the team leaves without a call.

Figma

Figma's resource on what a decision matrix is and how teams use it for product and design picks. Useful when a team wants a tool for picking between options without endless meetings.

GV (Google Ventures)

Google Ventures' design sprint method for using a decision matrix in the Decide phase. Useful when a sprint team has a wall of ideas and needs a fast structured way to pick a few.

JD Vogt

Salesforce's four product principles — Clarity, Efficiency, Consistency, Craftsmanship — are stack-ranked and used to guide every design decision. Useful when defining your own product principles and looking for a worked example with priority order.

Smashing Magazine

Aggregates Smashing Magazine articles on design principles, covering visual weight, gestalt, and layout systems across many writers. Useful when you want a reading list to deepen team knowledge of principles across different design problems.

Maria Rosala

Explains that product-specific design principles are value statements that guide trade-offs and keep teams aligned on what good looks like. Useful when defining principles for a single product so designers, PMs, and engineers stop relitigating the same calls.

IDEO

Describes IDEO's method for setting design principles up front so a project team has a shared north star while making choices. Useful at the start of a human-centered design project when the team needs guardrails before generating ideas.

Llara Geddes

Defines product principles as shared value statements that frame decisions, and shares a workshop format for creating ones that stick. Useful when running a session to define principles for a team or product line.

Gabriel Svennerberg

Curates a public library of design principles from companies and creators, with each entry explaining how the team uses theirs. Useful when you are drafting your own product principles and want concrete examples to compare against.

Reddit, Inc.

Reddit thread distills tactics for defending design decisions: focus on goals not preference, use data, reference industry examples, show alternatives, avoid defensiveness. Useful when designers face hostile design reviews and need a playbook.

Bryan Zmijewski

Bryan Zmijewski breaks design decisions into six layers (strategic, conceptual, structural, aesthetic, functional, technical) so teams can move faster on each. Useful when teams confuse strategic and tactical design choices and slow down both.

Jared Spool

Jared Spool maps five styles of design decisions - unintentional, self, genius, activity-focused, experience-focused - and argues great designers know which they're using. Useful when teams need a vocabulary for how decisions are actually getting made.

Hollie Parsons

Hollie Parsons gives concrete tactics for defending design decisions with evidence, by showing your process, and by citing sources like NN/G and Google Scholar. Useful when designers need to articulate why a choice should win over preference.

Tanner Christensen

Tanner Christensen reminds readers that a final design hides hundreds of decisions and tradeoffs you can't see from the outside. Useful when stakeholders judge design work without context for the research and tradeoffs behind it.

Charis Liang

Charis Liang shares a method for product designers facing competing solutions: align on the problem, then evaluate options through business needs, user needs, and tech constraints. Useful when designers, PMs, and devs disagree and the choice keeps drifting.