Stephan Sagmeister

Stefan Sagmeister pushes back on the rush to call every designer a storyteller, arguing not everyone needs to be one. Useful when a team is being told to add narrative everywhere and wants a counterpoint to the trend.

Deepak Deolalikar

Survey of growth strategies for PMs across acquisition, activation, and retention with frameworks for picking the next bet. Useful when a PM is asked to drive growth without a fixed playbook.

Shayna Stewart

Distinguishes data-driven (data decides), data-informed (data plus judgment), and data-inspired (data sparks new ideas) and shows when each fits. Useful when a team argues about how much weight to give data on a specific decision.

Paul Swanson

Adds data-justified to the data-driven, informed, and inspired categories, with a focus on schools but applicable to any human-centered org. Useful when teams use data to defend a decision they had already made.

Vishal Chaudhary

Walks through major product strategy frameworks and shows how to pick the right one based on stage, market, and goals. Useful when a PM is overwhelmed by framework choices and needs a way to commit.

Noelle Saldana

Talk that walks through how to make a realistic plan for adding AI to a product, covering pain points, data needs, human-in-the-loop, value prop, and timeline. Useful when leadership is excited about AI but the team needs a way to keep it grounded in real value.

Maria Ciampa

High-level guide covering why to add AI, what functionality to build, build-versus-buy choices, data management, and model robustness. Useful when a PM is new to AI work and needs a single map of the major decisions ahead.

Alan Gleeson

Alan Gleeson outlines how to compete in crowded B2B SaaS markets with sharper focus and positioning. Useful when a SaaS team is one of many and struggling to break out.

Kashi.Ks

Kashi.Ks walks teams from using LLM APIs to building their own GenAI tools, with trade-offs explained. Useful when a team is choosing whether to buy, wrap, or build AI.

Rob Chappell

Rob Chappell envisions the next wave of AI-enhanced experiences and what they mean for designers. Useful when a design team is mapping its AI roadmap for the next year.

Eudardo Feo

Compares blue ocean and red ocean strategies and shows how to balance fighting in known markets with creating new ones. Useful when leaders need a quick, shared mental model before a strategy debate.

Vihan Chelliah

Walks through Blue Ocean Strategy in plain words and shows how to find market space where rivals don't matter. Useful when a team is stuck fighting in a crowded market and wants a simple frame for finding new ground.

Snowber Vaqar

Frames UX research as its own blue ocean and pushes researchers to find untapped questions and methods. Useful when a UX research lead wants a fresh angle on planning research priorities.

Suren Karapetyan

Practical guide on using a blue ocean strategy to enter empty markets, with a frank reminder that no market is truly empty. Useful when a PM is thinking through whether their idea sits in a blue or red ocean and how to position.

Ross Mayfield

Walks through common challenges in product discovery, including cross-functional collaboration and choosing the right validation metrics. Useful when a discovery lead needs to anticipate the team-level snags before kicking off discovery.

RuleTheOne

Reddit discussion on common pain points in product discovery, including stakeholder pressure, confirmation bias, and lost signal. Useful when a PM wants the practitioner view on why their discovery work feels stuck.

Stephan Beyer

Step-by-step guide to building Opportunity Solution Trees from outcomes to tested assumptions. Useful when a team is new to OSTs and needs a clean blueprint.

Rob Gifford

Rob Gifford on simple techniques for making any experience easier to use. Useful when a team is staring at a tangled flow and needs a way to start cutting it down.

Ioana Teleanu

Podcast and post on when teams really should skip UX research, and why pressure or budget alone is not a good reason. Useful when a team is debating whether to skip research and needs a balanced view from a UX leader.

Nikki Anderson, MA

Argues that user research can sometimes be skipped if you do not have the time, skill, or budget to do it well. Useful when a small team is pressured to do research and needs a sober view of when to skip.

Mesh Flinders

Explores why hand-drawn, imperfect lo-fi visuals feel fresh again and how brands use them to seem human. Useful when a creative team is choosing a visual direction for a campaign or brand refresh.

Jeff Humble

Jeff Humble's Fountain Institute guide explains the four phases of the Double Diamond and the diverge-converge pattern. Useful when newer team members need a friendly entry point before debating its limits.

Eduardo Hernandez

Eduardo Hernandez calls for letting go of the Double Diamond in favor of an emergent design mindset that adapts to messy real-world projects. Useful when teams keep forcing reality into a tidy diamond.

Ricardo Martins

Ricardo Martins argues the Double Diamond is a fallacy because design is not actually linear and the model hides setup work. Useful when teams treat the Diamond as gospel and you need to push back.

Leon Gauhman

Leon Gauhman pushes teams to ditch the Double Diamond and just start shipping to learn faster. Useful when a team is paralyzed by process and needs a nudge into action.

Dan Ramsden

Dan Ramsden offers an evolved Double Diamond that ties to organizational context, especially for strategic design work. Useful when design leaders need a model that survives boardroom discussions.

Dan Ramsden

Dan Ramsden critiques the Double Diamond for hiding ambiguity and setting false expectations, while still valuing what it teaches. Useful when leaders defend or attack the Double Diamond and want a balanced critique.

Maciej Lipiec

Maciej Lipiec proposes a Three Triangles model that runs Discovery, Ideation, and Delivery in parallel rather than the linear Double Diamond. Useful when teams find the Double Diamond too tidy and want a richer mental model.

Ghaida Zahran

ZURB blog argues that designers slide into 'dumb design' when they take orders instead of asking why, and that critique should push them to own the problem. Useful when leaders see designers acting like puppets and want a way to lift them up.

Traction - A Community for Innovators

Gibson Biddle shares a mock 2022 Netflix strategy using the DHM, GEM, and SMT frameworks together to demand a 10x roadmap. Useful when a product leader wants a worked example of stacking strategy frameworks for big swings.

Ant Murphy

Ant Murphy argues that product strategy is messy and not the same as your vision or roadmap, with four steps from inputs to choices. Useful when leaders confuse strategy with a Gantt chart and need a sharper definition.

Suzanne Abate and 100productmanagers

100productmanagers' transcript captures Gibson Biddle explaining the DHM model: delight customers in hard-to-copy, margin-enhancing ways. Useful when a leader wants the canonical short version of DHM in writing.

Lenny Rachitsky

Lenny Rachitsky interviews Gibson Biddle on his DHM strategy framework, GEM roadmap method, and Netflix-era stories. Useful when a product leader wants frameworks for setting strategy and prioritizing the roadmap.

Ash Maurya

Ash Maurya argues that asking lean startup or business model design or design thinking is the wrong question — they all answer different parts of the same arc. Useful when leaders are tribal about methods and a team needs to merge ideas instead of fighting over labels.

Ryan Loveday

Ryan Loveday compares design decision-making to the halting problem in computer science — you cannot always know in advance when more analysis will help, so you have to set a timer and decide. Useful when a team keeps researching the same question and needs a frame to call it and move.

Vicki T.

Argues good designers blend pattern intuition with deliberate research. Useful when leaders want to coach designers on trusting their craft.

Brianna Koch

Looks at when designer intuition is helpful and when it leads us wrong. Useful when teams debate gut calls vs. evidence in design choices.

Daniele Altomare

Argues the Opportunity Solution Tree beats rigid feature roadmaps because it stays outcome-driven. Useful when leaders want to move from feature lists to discovery-led plans.

Reddit, Inc.

Reddit thread where PMs share signals that it is time to scale a product. Useful when you are debating whether your team is ready to scale and want a gut-check from peers.

Robert Hoekman Jr

Robert Hoekman Jr argues simplicity in UX is overrated and explains when it backfires. Useful when a team is reflexively cutting features and forgetting users sometimes want power.

Carlos Yllobre

Carlos Yllobre on a simplified journey from data to content to visuals when designing data products. Useful when a team is building a data-heavy product and the design feels overwhelming.

Andy Polaine

Andy Polaine on getting from where you are to where you want to be in design and service work. Useful when a team or designer is stuck in the gap between vision and reality and needs a way to move.

Hugo Pegley

Hugo Pegley argues that product experience can outweigh user experience in some products. Useful when a leader is choosing where to invest between UX polish and broader product experience.

Lee Dale

Lee Dale argues the experience makes the product, not the features themselves. Useful when a team is stacking features and forgetting the experience users actually walk through.

Mitchell Clements

Mitchell Clements argues that value should come before usability in product decisions. Useful when a team is over-polishing a product nobody clearly values yet.

Mariia Kasym

Mariia Kasym asks how much personalization is enough in UX, with trade-offs between delight and creepiness. Useful when a team is debating how far to push personalization on a sensitive product.

Alistair Garfoot

Alistair Garfoot on designing systems with AI in the loop, including handoffs between humans and models. Useful when a team is shipping a workflow where AI makes some calls and humans make others.

Mikah Sellers

Mikah Sellers on how AI is powering the next generation of fluid, adaptive interfaces. Useful when a designer or PM is thinking about where AI changes the shape of UI itself, not just content.

Dan Phillips

Dan Phillips shares a case study in multimodal, adaptive UX where humans and AI share an interface. Useful when a team is designing AI-collaborative tools and wants a worked example to learn from.

Andy Curry

Walks from static UX to adaptive UX and shows why personalization can be a real win when done right. Useful when a marketing or product team wants a sober view on the upside and risks of personalization.

Aditi Priya

Aditi Priya makes the case for adaptive UX, where products adjust to different users instead of treating everyone the same. Useful when a product team is debating whether to invest in personalization or stay one-size-fits-all.

Holly Davis

Holly Davis pushes back on calling scope creep a dirty word and offers a healthier way to think about it. Useful when a PM or design lead wants language to talk about scope changes that does not blame the team.

Tanaya Shekatkar

Asks why a product with great UX and good UI can still flop, and pulls apart possible reasons. Useful when a team has shipped polished work but adoption is weak and they need a wider lens.

Svyatoslav Biryulin

Argues SWOT is too simple a tool: present-bias warps strengths, opportunities are vague, and the model limits disruptive thinking. Useful when a team relies on SWOT but ideas feel small and you want a critique to start a different conversation.

Roger Martin

Roger Martin says SWOT is useless without a hypothesis to test and pushes leaders to drop SWOT-only strategy work. Useful when a strategy team is about to start a SWOT and you want to redirect them.

Alex Czartoryski

Czartoryski's framework asks what adjacent technologies are needed to make an impossible idea possible, and recurses until you find a possible step. Useful when planning long-horizon innovations and you need a way to break them into reachable bets.

ð¨ð»‍ð» Andy Budd

Proposes a Triple Diamond update to the Double Diamond, adding a bridge phase where stakeholder management and translating insights into action happen. Useful when teams feel the gap between research and design and you need a process model that names it.

Adobe

Walks through eight visual principles — alignment, contrast, hierarchy, repetition, proximity, color, white space, and balance — for making cleaner graphics. Useful as a quick refresher before reviewing visual work or briefing a non-designer.

Taras Bakusevych

Pulls together ten classic principles — like flexibility versus usability and error prevention — that shape good product decisions. Useful as a reference when defining your own product principles or critiquing a design.

Sébastien Dubois

Explores the trade-off between technical quality and user happiness, arguing that one without the other leaves products fragile or unloved. Useful when teams debate spending sprints on polish, refactors, or new value and need a frame for the conversation.

Dave Snowden

Dave Snowden's Cynefin framework helps decision-makers identify whether a problem is clear, complicated, complex, chaotic, or in disorder, then act accordingly. Useful when teams use the same playbook for very different kinds of problems.

Carissa Carter

Carissa Carter argues we should stop talking about THE design process - the d.school now teaches eight design abilities so students become chefs not recipe-followers. Useful when design teams over-index on process and want to refocus on capability.

Pabini Gabriel-Petit

Pabini Gabriel-Petit distinguishes design as a process (iterative steps) from a methodology (a system of methods) and argues teams should focus on the process. Useful when teams confuse process and methodology and codify the wrong thing.

Jordan Bowman

Jordan Bowman argues UX overemphasizes process - real teams adapt their process to each project. Useful when newer designers think there's one right way and feel stuck when reality differs.

Brian Ling

Brian Ling argues designers should focus on methods rather than rigid process - even better, work from a design philosophy. Useful when teams treat their process as a sacred checklist instead of a tool.

Marty Neumeier

Marty Neumeier's No-Process Process runs discovery, definition, and design in parallel rather than in sequence. Useful when teams find linear phases blocking learning and want a more swarm-like approach.

Jon Daiello

Jon Daiello argues design isn't a process - it's a craft that's non-linear and improvisational like jazz. Useful when teams treat process compliance as the goal and lose sight of judgment.

David Peterson

David Peterson argues AI product design rests on affordances, predictive UIs over chatbots, and critical thinking over speed. Useful when AI products default to chat and teams need a wider design vocabulary.

Mateusz Cygan

Mateusz Cygan and Ania Wojcieszczak frame AI as four design capabilities - personalization, prediction, recognition, and anomaly detection - so designers know which intervention to pick. Useful when teams need a vocabulary for what AI can actually do in their product.

Ken Sigel

Ken Sigel argues AI products need new UI patterns since today's blank text box hides AI's range and demands programming-level skill. Useful when teams design AI features and the chat UI keeps confusing users.

Alexander Trukhin

Lex Trukhin argues startups can use AI to drive empathy-informed design decisions and ship better products faster. Useful when small teams want concrete ways AI can shape their design work, not just personalize features.

Mike Schindler

Mike Schindler invokes Herbert Simon's "satisficing" to warn that AI-generated mockups look so authentic stakeholders treat them as final products. Useful when AI prototypes shortcut conversations and design loses a seat at the table.

Sean J. Savage

The article explains that outcome-driven approaches fail when teams lack decision clarity, ownership, and mechanisms that translate outcomes into concrete action. Use this when diagnosing why outcome metrics aren’t changing behavior and when deciding how to redesign work so outcomes actually influence decisions.

Daniele Pesaresi

The article argues that outcomes are often misused as shortcuts for decision-making, warning that labeling work as “outcome-driven” doesn’t eliminate the need for judgment, context, and tradeoff thinking. Use this when evaluating whether outcome framing is genuinely improving decisions or simply masking unresolved ambiguity and responsibility.

Esben A. Poulsen

The article argues that blindly adopting “outcomes over output” can fail when teams don’t clearly define ownership, decision rights, and the mechanisms that translate outcomes into action. Use this when evaluating whether an outcome-driven approach is actually improving decisions or just replacing one form of theater with another.

Dr. Myriam Munezero

The article argues that outcomes only create value when they are explicitly tied to decisions, warning that teams often track outcomes without clarity on how those signals should change behavior or direction. Use this when diagnosing why outcome metrics aren’t influencing priorities and when deciding how to design work so signals clearly enable decisions.

Sunil Shrivastav

The article argues that focusing on outcomes alone is insufficient unless teams also design for the decisions those outcomes are meant to inform, making decision clarity the missing link between intent and impact. Use this when diagnosing why outcome-driven work isn’t changing behavior and when deciding how to structure product work so signals clearly unlock decisions.

Peter Lewis

The article explains value mapping as a way to explicitly connect user value, business value, and delivery effort so teams can see where work creates real impact and where it doesn’t. Use this when deciding which opportunities are worth pursuing and how to prioritize work based on shared value, not just ideas or features.

Todd Daniel

The video explains how product and design teams can shift from shipping features to deliberately driving outcomes by defining desired behavior change and aligning work to measurable impact. Use this when deciding how to frame success, align teams around outcomes, and move away from output-based planning and reporting.

Teresa Torres

The video explains why product teams should stop measuring success by features shipped and instead focus on outcomes—measurable changes in user behavior and business results. Use this when deciding how to define success, reframe roadmaps, and align teams around impact rather than delivery.

Ash Maurya

The article explains that while the Lean Canvas is effective for capturing assumptions and early learning, it cannot replace a full business plan when deeper analysis, execution detail, and long-term planning are required. Use this when deciding which planning artifact is appropriate based on company stage, audience, and the level of rigor needed to make investment or execution decisions.

Matthew Pattinson

The article identifies four recurring mistakes teams make when using the Lean Canvas—treating it as documentation, failing to surface assumptions, not updating it with learning, and focusing on completion over validation—which prevent real learning and iteration. It reframes the canvas as a living tool meant to drive hypothesis testing and decision-making, not static alignment. Use this when diagnosing why Lean Canvas work isn’t leading to better decisions or when resetting how teams validate assumptions and learn over time.

Arthur von Kriegenbergh

This talk explains why teams should stop measuring success by features shipped and instead define success through outcomes—measurable changes in user behavior and business impact. It shows how reframing work around outcomes improves prioritization, decision-making, and cross-functional alignment. Use this when you’re deciding how to judge success, move away from delivery metrics, and align teams around impact rather than activity.

Jeff Gothelf

This video provides a walkthrough of the Lean Strategy Canvas and the Lean Product Canvas, updated versions of the Lean UX Canvas that help teams visualize assumptions, strategy, and product hypotheses on one page and align work around measurable outcomes. Use this when deciding how to structure strategy, clarify hypotheses, and track assumptions visually to ensure product work ties to business and user outcomes.

Ash Maurya

The article argues there’s no single correct sequence to fill out a Lean Canvas — instead, teams should focus on deconstructing their idea’s backstory and prioritizing validating their riskiest assumptions rather than rigidly following a box order. It reframes the canvas as a tool to uncover beliefs and assumptions about a business model, promoting iterative learning and hypothesis testing.

Jorge Valencia

The article argues that designers should shift their focus from shipping features (outputs) to creating measurable impact (outcomes) by defining desired customer behaviors that drive business results and planning work backward from impact to outputs. Use this when you want to align design work to outcomes that matter, ensure solutions are tied to behavior change, and influence prioritization and measurement decisions.