Teo Yu Siang

Interaction Design Foundation overview of stage 4 in the design thinking process, prototyping, with low and high fidelity options and how each fits user testing. Useful when a team is learning the design thinking flow and wants to know when to prototype.

Anna Kaley

NN/g study guide that pulls together articles, videos, and tips on UX writing and tone of voice. Useful when ramping up on UX writing or building a team's foundation for clear product copy.

Nick Jain, CFA

IdeaScale article defining innovation management as the systematic process of generating, picking, and developing new ideas to drive value. Useful when a team is setting up an innovation pipeline and needs a clear definition and stages.

Emma Taggart

Surveys current trends in design storytelling, including UX personas, interaction design, and how users co-create the story. Useful when refreshing a team's storytelling habits or scoping work that needs more emotional pull.

R B Srikanth

Walks through a discovery framework that includes governance, ideas intake, and continuous learning loops with users. Useful when setting up or improving how a team finds and validates new product ideas.

Dan Olsen

Lean Product Meetup talk by Alex Osterwalder on product innovation, business models, and customer development. Useful when shaping innovation strategy and you want a refresher from a canonical source.

Dennis Hambeukers

Argues that designers and product owners share the same human, technical, and business dimensions, even if they emphasize different ones. Useful when designer-PO clashes feel turf-based and you want a frame for shared ground.

The Chisel Team

Walks through user research, personas, feedback, and value-vs-effort prioritization to keep a product aligned with real user needs. Useful when launches feel disconnected from users and you need a checklist of basics to revisit.

Mikael Cho

Argues that better products often fail because incumbents have switching costs and habits on their side, not just inertia. Useful when leadership keeps assuming better tech automatically wins.

Chad Alessi

Looks at why innovative products fail, often because of weak adoption, poor positioning, or solving the wrong problem. Useful when reviewing a launch postmortem and you want a frame for what went wrong.

Peter Yang

Argues for retiring the vague phrase product sense and replacing it with empathy, creativity, and craft, with practical tips for each. Useful when feedback like "build product sense" feels too vague to act on.

Rikke Friis Dam

Lays out core principles of service design: ground services in real demand, design for customer needs, treat the service as one connected system, and build for value and efficiency. Useful when standing up service design work and you want a shared set of principles to guide the team.

Houda Boulahbel

Story-style comparison of how linear, design, and systems thinkers each approach the same complex problem (a future house) and why all three perspectives are needed. Useful when teams default to one mindset and you want a quick way to show what gets missed.

Santhosh Gandhi

Argues that design thinking is human-centered while systems thinking is interconnection-centered, and the two together let teams see both user needs and the wider system around them. Useful when a design challenge feels too narrow and you need to understand the system shaping user behavior.

Jess Shutt

Explains the cognitive forces behind freemium: endowment effect, mere exposure, loss aversion, and status quo bias, and how to design with each. Useful when planning a freemium experience and you want to know which mental levers actually drive upgrades.

Shaili Guru

Maps the AI and ML model landscape across paradigms like GANs, transformers, and traditional ML, with applications for each. Useful when a PM needs a quick mental map of model types before scoping a new feature.

Platform Revolution Team

Argues that great products win by removing skill, access, time, and cost barriers, with examples like Instagram, Kickstarter, and YouTube. Useful when shaping a product strategy and you need a lens for which barrier to attack first.

UXPin

UXPin shares how to apply strategic design principles to UX work day to day. Useful when a UX designer wants concrete moves to bring strategy into their craft.

Alberto Brandolini

Alberto Brandolini connects technical debt to design integrity using EventStorming-style thinking. Useful when an engineering-heavy team wants a shared lens on debt and design.

Austin Knight

Austin Knight shares his definition of design debt and how to keep it under control. Useful when a design lead wants a personal essay-style read to align the team.

Andrew Chen

Andrew Chen contrasts product design debt with technical debt and why both need separate plans. Useful when leaders lump them together and starve one of attention.

Neil Turner

Neil Turner explains what design debt is and shares simple ways to deal with it. Useful when a designer needs a friendly intro to design debt for non-design audiences.

Ashley McClelland

Ashley McClelland challenges the 'don't listen to customers' myth attributed to Steve Jobs and shows when listening matters most. Useful when leaders use the Jobs quote to dismiss research.

Dr. Marcus Collins

Dr. Marcus Collins (HBR) argues data alone misses the cultural context behind why customers act. Useful when a team only relies on dashboards and is missing the 'why' behind the numbers.

Alex Ewerlöf

Alex Ewerlof flips the lens to show common bad PM behaviors so you can avoid them. Useful when a team wants to spot PM anti-patterns in their own work.

Shelly Kalish

Shelly Kalish breaks down the everyday work of PM that rarely makes the headlines. Useful when leaders are setting expectations for new PMs.

Jason Shen

Jason Shen shares the unspoken realities of product management, from ambiguity to politics. Useful when someone is considering moving into PM and wants the honest picture.

Mithil Srivastav

Mithil Srivastav argues many people called PM are really doing project work and explains the real difference. Useful when a team is unsure whether they have real PM coverage.

Prasant Lokinendi

Prasant Lokinendi shows a real day in the life of a PM, from standups to user calls and roadmap work. Useful when a non-PM stakeholder wants to understand what PMs really do.

Liam Kane

Liam Kane connects design thinking with product discovery so teams can find better problems to solve. Useful when a team mixes the two methods and creates noise.

Alex Jupiter

Alex Jupiter explains Jobs To Be Done as a way to focus on what users are really trying to achieve. Useful when a product team is overwhelmed by feature requests and needs to refocus.

Emily Djock

Emily Djock at ITONICS lists five product design principles that are both innovative and sustainable. Useful when a design team is building principles to guide future products.

LexisNexis

LexisNexis webinar on bringing clarity to sustainable innovation, especially in patent and IP space. Useful when an IP team needs a current view of sustainable innovation trends.

Sreya Majumdar

Sreya Majumdar shows how design thinking can fuel sustainable business innovation across teams. Useful when a leader needs a story tying design thinking to long-term innovation.

Houda Boulahbel

Houda Boulahbel describes ten faces of systems thinking and how each helps tackle complex problems. Useful when a team faces a tangled problem and needs different lenses to see it clearly.

Juan Carlos Rosales López

Juan Carlos Rosales Lopez shows where AI is changing UX, from personalization to predictive design. Useful when a design team needs a fast briefing on AI's UX impact.

Henry Wang

Henry Wang of Google walks through Product Marketing 101, with examples from real launches. Useful when a new PMM wants a fast on-ramp to the discipline.

Joshua Gene Fechter

Joshua Fechter explains what a PMM does day to day and how it differs from PM and marketing. Useful when execs are confused about where PMM fits.

Lindsay Kolowich Cox

Lindsay Kolowich Cox at HubSpot explains what product marketing does, from positioning to launches and enablement. Useful when a team is unclear what to expect from a product marketing hire.

Dane W.

Dane Wesolko summarizes Peter Morville's UX Honeycomb and how its seven facets shape good experiences. Useful when a team needs a shared lens for talking about UX quality with non-designers.

H Locke

H Locke questions whether modern UX work still leaves room for true user-centricity given org pressures. Useful when a design lead is reflecting on whether the team's process actually serves users.

Eduardo Fe

Eduardo Feo shows where AI is reshaping UX work, from personalization and predictive flows to chatbots and analytics. Useful when a design team needs a quick map of where AI could help across their UX practice.

Katy Le

Katy Le explains the user-centered design (UCD) phases: context, requirements, solutions, and evaluation, with users at every step. Useful when a team is setting up a new design process and wants a clean UCD baseline.

Saadia Minhas

Frames marketing KPIs as outcome measures and proxy metrics as steps that show progress, with conversion-rate flow as a concrete example. Useful when a marketing team is sorting which numbers are real KPIs and which are just signposts.

Indeed

Indeed primer on the OGSM framework with definitions of objective, goals, strategies, and measures plus how to build one. Useful when a manager is new to OGSM and wants a clear introduction before facilitating planning.

Judith Lopez

Walks through growth design as the practice of building products that scale through user-centered, data-driven, cross-functional work. Useful when a designer wants a comprehensive starter guide before joining or leading a growth team.

Dhawal Patel

Argues that growth design pairs customer experience with business impact and that customer development is a key skill for designers. Useful when a designer wants a practical view of growth design and the skills to build first.

Carl Thomas

Defines growth design at the intersection of growth science and human-centered design with principles like user focus, simplicity, and fail-fast learning. Useful when leaders need a clear definition of growth design before staffing or training the team.

Mari Luukkainen

Beginner guide to growth hacking that defines it as fast, experiment-driven growth using marketing, design, and analytics together. Useful when a startup team needs to understand what growth hacking really is before picking tactics.

Ben Sadick

Discusses choice architecture, the compromise effect, and default settings in interface design. Useful when designers want concrete patterns for nudging users toward better choices.

Mike Darnell

Mike Darnell applies choice architecture to B2B buying journeys and pricing pages. Useful when a marketer is laying out plans, packages, or CTAs for business buyers.

Ryan Setliff

Ryan Setliff covers how digital media uses choice architecture to shape consumer behavior. Useful for product or marketing teams trying to understand patterns they see in big platforms.

Wicar Akhtar

Wicar Akhtar shows how small layout choices guide users toward better actions. Useful when a designer wants to improve a flow without redesigning whole screens.

Bhavik Patel

Bhavik Patel argues North Star Metric is a bad metaphor because the real North Star is dim, hidden, and useless from the south. Useful when a team blindly chases North Star Metrics without questioning the idea.

Isaac Jeffries

Isaac Jeffries' BMC Part Sixteen describes the four outside forces that can help or hurt a business model, like Industry Forces and substitutes. Useful when teams new to the Business Model Canvas need a friendly walk-through of the environment piece.

Jakob Nielsen

Jakob Nielsen explains why enterprise usability is broader than screens, with cost of ownership, install, and admin pains driving total impact. Useful when leaders need to push past surface fixes and see the wider system that affects users.

Julie Zhuo

Julie Zhuo writes about perplexing design intentions — products that seem to want one thing while quietly pushing another, and how to keep your own intent honest. Useful when a designer feels unease about a product direction and wants language for naming the gap between stated and real intent.

Priscila Avila

Priscila Avila explains the differences and overlaps between UX, CX, EX, and service design — and why teams keep tripping over the labels. Useful when an org is restructuring and leaders need clarity on which discipline owns what.

Michael Feder

University of Phoenix's primer on what product innovation is — incremental versus radical, and how companies typically organize for it. Useful when a team needs a plain-English definition before getting into method debates.

Pascal Potvin

Pascal Potvin explains emotional delight in product design — moments of surprise, recognition, and care that make people feel seen. Useful when a team wants to add delight thoughtfully and needs categories for what kind of feeling each moment should create.

Mariia Kasym

Real examples of UX design that older users love. Useful when teams want concrete inspiration before designing for seniors.

Becca Selah

Salesforce UX team on what older adults teach us about accessible design. Useful when teams want senior insights to lift design for everyone.

Lexie Kane

Lexie Kane (NN/g) on usability challenges and changes for senior citizens. Useful when teams plan testing with older users and want known issues in mind.

Lauren Cochran

Lauren Cochran on crafting engaging UX for senior users. Useful when teams want both usable and fun experiences for older audiences.

Joshua Reach

Joshua Reach's comprehensive guide to UX/UI design for elderly users. Useful when products serve older audiences and need clear, accessible patterns.

Productboard

Argues PMs' real responsibilities are alignment and communication, not just feature lists. Useful when your PM role feels stuck on backlog grooming and you want a wider lens.

Jori Bell

Personal story of accidentally becoming a PM and what that taught about the role. Useful when your path to PM is unconventional and you need a relatable story.

Emma Blomkamp

Walks through key co-design principles like power-sharing, lived experience, and trust. Useful when you are setting up a co-design effort and need a principles list.

Hoa Loranger

Argues bluntly that UX without user research is just opinion and risks shipping designs that fail with real users. Useful when leaders need to be reminded why user research is non-negotiable in any UX practice.

Adarish Nair

Argues that automation and rigid policies are eroding customer trust and proposes segmenting customers by value to keep empathy alive. Useful when CX leaders are weighing automation versus human treatment in customer journeys.

Kathi Kruse

Personal essay about an auto detailing experience that argues a customer-first culture builds long-term loyalty. Useful when leaders want a simple story to make the case for putting customer experience at the center of operations.

Marion Hekeler

Walks through how IBM design teams used data storytelling to bring designers, data scientists, and journalists together to build product experiences with a clear narrative. Useful when a team wants to move from raw dashboards toward stories that help users feel confident in their choices.

Ilya Dmitruk

Ilya Dmitruk shares a six-step framework for effective UX strategy in video form. Useful for teams that want a quick walkthrough they can watch together.

Magnus Lundström

Magnus Lundstrom explains what UX strategy is and why it matters. Useful when a team is brand new to the idea of UX strategy.

Fei Ren

Fei Ren shares UX strategies for guiding users through complicated journeys. Useful when a product has long, multi-step flows that confuse users.

Nirmalson Harry

Nirmalson Harry explores design thinking's value beyond just solving problems. Useful when leaders are deciding how to scale design thinking in their org.

Staney Joseph

Staney Joseph argues for design that goes past problem solving toward human-centered solutions. Useful when teams keep solving narrow problems and missing larger user needs.

Ian Gonsher

Ian Gonsher proposes a richer design taxonomy that goes beyond classic design thinking. Useful when teams want fresh language for the kinds of design work they do.

Rebecca Ackermannarchive

Rebecca Ackermann's retrospective on design thinking and where it went wrong. Useful when leaders are debating whether to keep using design thinking as a framework.

Rob Peart

Rob Peart pushes back on the idea that design is mostly problem solving. Useful when teams default to design thinking for every kind of work.

Amy Thibodeau

Amy Thibodeau shows how to practice empathy in product design beyond buzzwords. Useful when designers want concrete habits, not slogans, for empathy.

Neil Turner

Neil Turner argues design should be data-informed rather than data-driven, leaving room for judgment. Useful when teams over-rely on dashboards at the cost of intuition.

Tom Connor

Tom Connor connects nudge theory to everyday product and policy choices. Useful when a team is debating whether a nudge is appropriate for their product context.

Georgina Guthrie

Explains choice architecture, common nudge patterns, and the line between helpful and manipulative. Useful when a team is designing defaults or option layouts and wants to stay ethical.

Yaryna Demkiv

Lists ten steps in a product design process from kickoff to launch with a short note on each. Useful when a team needs a checklist-style process to follow on a new project.

Rachel McConnell

Rachel McConnell explains how content design fits into the product design process and how to argue for it. Useful when a team is trying to bring content work in earlier instead of at the end.

Julia Szymik

End-to-end guide to the product design process with stages, tools, and examples. Useful for designers building or sharing a process playbook with a new team.

Ideo

IDEO's primer on what design thinking is, the mindsets it depends on, and how teams use it. Useful when leaders need a quick shared definition before kicking off a human-centered project.

Nick Babich

Long-form guide that walks through every phase of product design, from research to launch, with examples. Useful when a new team needs a shared map of what good product design looks like end to end.

Yvonne X.

Yvonne Xiao gives a short video intro to content design, explaining it as user-centered work that covers writing, structure, and message hierarchy. Useful when a team wants a friendly first explanation of what content designers do.

Rachel Krause

Rachel Krause at NN/g explains Lean UX in a short video as a collaborative, cross-functional, fast way to design. Useful when a leader needs a five-minute briefing for a team that hasn't tried it.

Jeremy Bird

Jeremy Bird shares why Lean UX worked for his consumer prototypes but stalled on enterprise back ends that take months to build. Useful when a team blindly applies Lean UX and hits walls in complex environments.

Sam

Sam at Bootcamp compares Design Thinking, Agile, and Lean UX, framing them as problem finding, problem solving, and learning loops. Useful when a team mixes the three and needs a clean way to talk about each.

Wes O.

Wes O'Haire shares seven mental models like First Principles, Inversion, and Abstraction Laddering that designers can use to solve problems. Useful when a team is stuck and needs new thinking tools to break through.

Alan Klement

Alan Klement argues you should design for progress, not outcomes, because customers want forward motion in their lives, not just a finish line. Useful when a JTBD-aligned team wants to redefine success.

Will Tsui

Will Tsui defines a great design outcome as one that creates real value for a clearly understood audience and is measurable. Useful when designers debate what a good outcome even is.

Vidhi Tiwari

Stuti Mazumdar and Vidhi Tiwari's complete guide explains Agile UX as iterative design that loops user feedback into every cycle. Useful when newer teams want a long-form intro before they actually try it.

Shamsi Brinn

Shamsi Brinn argues that Agile, as practiced, leaves design and discovery in the cold and that Design Sprints just patch the gap. Useful when teams find themselves designing inside two-week sprints with no real discovery.

Indi Young

Indi Young challenges the idea of Agile UX by separating understanding people from building and delivering software. Useful when teams jam research into sprints and lose depth.

Interaction Design Foundation

Interaction Design Foundation defines KPIs in UX, why they matter, and tools like the System Usability Scale. Useful when teams need a shared, plain-language definition before debating which KPIs to use.

Strategyzer

Strategyzer's short video sets up why business models live inside a context of forces and trends, not in a vacuum. Useful when training a team that is brand-new to the Business Model Canvas.

Roel Wieringa

Roel Wieringa maps Netflix as an ecosystem, showing how studios, viewers, investors, and competitors create value together. Useful when teams build platform or marketplace products and need an example of mapping ecosystem actors.

Lisa Angela

Lisa Angela argues that the hardest part of enterprise UX research is choosing the right method for the real problem, not running the method itself. Useful when researchers feel stuck following recipes and need permission to think critically before picking a tool.

Savannah Kunovsky

IDEO sketches seven imagined AI experiences inspired by the movie Her, like a generative storyteller toy and calm-tech windows. Useful when product teams want fresh provocations beyond a chatbot to think about AI's future.

Interaction Design Foundation

The Interaction Design Foundation page introduces Human-AI Interaction (HAX), the field studying how people and AI systems work together. Useful when teams need a shared definition before debating AI design choices.

Google

Google Arts and Culture and the Barbican curated 21 short examples of art and tech projects that show different ways people can interact with AI. Useful when teams want creative inspiration for AI experiences beyond a chat box.

Gavin Johnson

ActiveMatter walks through working principles for designing with AI, like using AI as a provocation and refining its output through human judgment. Useful when product teams are figuring out how to bring generative AI into their design workflow without losing taste.

Khan Academy

Pixar's free Khan Academy course teaches the building blocks of story through short videos with Pixar artists. Useful when designers and PMs want to sharpen narrative skills they can bring to product pitches and user flows.

Stefan Sagmeister

Designer Stefan Sagmeister pushes back on calling every creative a storyteller, arguing the label is overused and dilutes the craft. Useful when teams want to be honest about what they are really doing instead of dressing work in trendy language.

Elizabeth Mally

Storytelling.design is a small library that explains why stories matter on the web and shows examples of digital narrative work. Useful when designers want quick inspiration and a primer on how stories shape user attention.

Natasha Mortimer

Storytelling shapes experience design by tapping memory, emotion, and shared understanding so brands connect with people in lasting ways. Useful when teams need to make a product or brand feel meaningful instead of just functional.

Braden Kowitz

Story-centered design uses sequential mockups like film frames so teams can see how a product flows from start to finish. Useful when you want to spot user-experience problems early and align the team before pixels get polished.

Jared Spool

Jared Spool questions whether 'delight' is really the best UX design intention — and proposes that fewer barriers, not more sparkle, often serves users better. Useful when a team is debating delight features versus removing friction and a leader wants a sharp argument for the latter.

Caroline Hamer

Caroline Hamer cautions against confusing user experience with customer experience — the two are linked but operate at different scales. Useful when a leader is using the terms interchangeably and a team needs language to clarify before scope creep.

Reddit, Inc.

Reddit thread debating CX versus UX — practitioners weigh in on the differences in scope, ownership, and skill. Useful when a designer is fielding the same CX-vs-UX question from leaders and wants peer-sourced answers to reach for.

Davis Levine

Davis Levine introduces service design patterns — what they are, how they differ from UI patterns, and how to start cataloging them. Useful when a service designer wants a primer before pitching a pattern library to leaders.

Sheena Lyonnais

Sheena Lyonnais traces the term 'user experience' back to Don Norman at Apple in the 1990s and how it evolved since. Useful when a designer is making a case for the broader scope of UX and wants the historical context to back it up.

Ben Le Ralph

Ben Le Ralph's intro to user experience design — what UX designers do, the process, and how it differs from visual design. Useful when a non-designer is starting to work with a UX team and needs a primer on what to expect.

Marija S.

Marija S. summarizes the elements of user experience — Garrett's classic five-plane model from strategy down to surface. Useful when a designer needs a quick refresh of the foundational UX framework before a strategy conversation.

Kate Kaplan

Kate Kaplan from NN/g defines user experience in plain language — covering everything that shapes a person's interaction with a product, not just the screens. Useful when a team needs the clearest possible answer to 'what is UX?' from a trusted source.

Reddit, Inc.

Reddit thread where designers debate what UX actually is — touching on its overlap with UI, research, and product. Useful when a team is arguing about UX scope and wants outside views before locking in a job description or process.

Shilpa Payyanadan

Shilpa Payyanadan walks through how psychology principles — Hick's law, Fitts' law, Gestalt — should shape design decisions, and where teams ignore them. Useful when a designer wants research-backed reasons for layout and flow choices instead of taste arguments.

Alex Klein

Alex Klein argues that designing for delight is dead — the real goal should be user well-being, not slot-machine moments that prey on impulses. Useful when a team chasing micro-delight features needs a reminder to weigh long-term user impact, not just short-term smiles.

Luis Mizutani

Argues that the user-story template is less about the words and more about a way of thinking — putting the user, their goal, and their why at the center of every requirement. Useful when teams fill in the template mechanically and miss the empathy it was built to force.

Elias Crum

Lays out how the B2B buyer's path has shifted to long, self-serve research before sales ever talks to a buyer, and what marketing teams should change in their lead-generation playbook. Useful when sales pipeline is shrinking and leaders need to rethink where signals about real intent come from.

Reddit, Inc.

Reddit thread where designers share tips for designing for seniors. Useful when teams want quick peer advice from real designers.

Sergei P.

Sergei P.'s guide to UI design for older adults on Toptal. Useful when teams need concrete UI rules for senior users.

Vitaly Friedman

Vitaly Friedman's guide to designing for older adults with patterns and pitfalls. Useful when designers want a deep, hands-on reference.

Jeff Humble

Explainer on what continuous UX research is and why it matters. Useful when leaders want a shared definition for the team.

Dave Hora

Dave Hora compares continuous discovery to one-off research projects. Useful when teams want to switch from project research to ongoing discovery.

Charles Wyke-Smith

Charles Wyke-Smith's four value dimensions tool for analyzing UX. Useful when teams need a quick way to score an experience on multiple axes.

Nathan Shedroff (down the page)

Nathan Shedroff's DIKW diagram lays out data, information, knowledge, and wisdom as a stack. Useful when teams build experiences that should help users move up that ladder.

Peter Morville

Peter Morville's classic on user experience design and the UX honeycomb. Useful when teams want a shared definition of what good UX even means.

Erik Messaki

Short essay on emotional design and why feelings shape user experience. Useful when teams want to add warmth and pull to flat designs.

IDEO U

IDEO U overview of the six steps of the design thinking process. Useful when a team wants a clean primer before running a workshop.

Dan Saffer

Dan Saffer argues empathy alone is not enough; design also needs craft and rigor. Useful when teams over-rely on empathy talk and miss real product work.

Lola Salehu

Seven starter tips for designers new to AI and ML products. Useful when designers are switching from non-AI work and need a quick on-ramp.

Emily Stevens

How-to guide for designing AI-first products from the ground up. Useful when a team is rebuilding a product around an AI model.

Veronica Chen

Adobe story on patterns and choices when designing generative AI features. Useful when teams are about to ship their first AI-powered flow.

Tim Herbig

Tim Herbig's guide to product discovery for teams, covering when and how to discover. Useful when a team is moving from delivery-only to running real discovery.

Debbie Widjaja

Senior PMs question both the problem and the solution rather than just executing tasks. Useful when teams want to spot which PMs are really thinking strategically.

Aaron Otani

Walks through a behavioral approach to designing products that change user actions. Useful when you want a method for designing for behavior, not just preference.

Kristen Berman

How to apply behavioral science principles to product design. Useful when you want to build products that nudge user behavior on purpose.

Mariya Besedina

Side-by-side breakdown of user goals and business goals and how they interact. Useful when you need a quick teaching tool to align a team on both.

James Biggs

Lays out PM roles and responsibilities clearly across stages and team types. Useful when you are writing a PM job description or setting expectations.

Reddit, Inc.

Reddit thread where PMs debate what the role should and shouldn't include. Useful when you want unfiltered peer takes on PM scope.

Reddit, Inc.

Reddit rant capturing common PM frustrations and what to do about them. Useful when you are considering PM as a career and want to hear the unfiltered downsides.

Seyifunmi Olafioye

Frontline stories about the PM journey across different teams and stages. Useful when you are early in your PM career or considering the role and want real stories.

Anna Maria Hall

Personal story of blending product design and product management roles. Useful when you are weighing how much PM work to take on as a designer.

Chris Walsh

Defines authentic co-design and how to avoid token participation. Useful when you want to make sure co-design is real and not performative.

Emma Blomkamp

Explains different shades of co-design from light involvement to deep partnership. Useful when 'co-design' means different things on your team and you need shared definitions.

Cassie Robinson

Asks what comes after human-centered design, looking at planet, systems, and futures-oriented framings. Useful when human-centered alone feels too narrow for the problem you're solving.

Reddit, Inc.

Reddit thread where practitioners answer 'what is service design?' in plain words. Useful when you need quick peer answers to share with a non-design teammate.

The Accidental Design Thinker

First-person learning story about getting up to speed on service design fast. Useful when you need a fast, friendly intro to the discipline.

Dev Singh

Plain-language intro to what service design is and how it differs from product design. Useful when you are new to service design and need a single, simple primer.

Yuanyuan Hu

Looks at why intent-driven UX matters more in B2B, where users have specific jobs to finish. Useful when you are designing complex B2B tools and want intent at the center of the work.

Jason Nissen

Explains intent-driven UX as designing around what users are actually trying to do, not just what they click. Useful when you want to shift your team from feature-first to intent-first design.

Nussi Einhorn

Reflections on where UX is headed: AI as a partner, immersive experiences, well-being focus, and sustainability. Useful when you want a quick scan of trends to discuss with your team.

Uzoma Ibekwe

Six lessons from two years as a UX writer, like demonstrating value and bridging the theory-to-practice gap. Useful when you are new to UX writing or hiring one and need to understand the real day-to-day.

Kshitij Agrawal

Introduces 'vibe design' as a way to design with AI by focusing on full presentation and feel instead of pixels and tokens. Useful when you are exploring how AI changes the designer's role and want a fresh framing.

Leran Admoni

Shares four guidelines for designing products in the AI era while keeping empathy and real user pain points central. Useful when you are setting team direction for AI work and want a short list of principles to align around.

Nurkhon Akhmedov

Walks through Google's 2024 AI design principles, like only using AI when it really helps and setting clear user expectations. Useful when you need a starter set of principles to shape AI features in your own product.

Christopher Roosen

Shares a set of human-centered design principles for safely using AI inside teams and across an organization. Useful when you want a checklist of principles to guide AI rollout and avoid common automation mistakes.

Nicole Leaper

Walks through how to apply human-centered design when adding AI to learning experiences so learners stay supported, not overwhelmed. Useful when you are shaping AI features in a learning product and need to keep learner needs front and center.

Dina Gkritzapi

Looks at how AI tools are changing UX work and asks teams to keep humans at the center of every design choice. Useful when you want to set guardrails for using AI in your design process without losing sight of user needs.

Rory James Zauner

Rory James Zauner's manifesto for human-centered AI, with principles and a call to action. Useful when a designer wants a strong piece to share with their team to set the bar for AI work.

G. Hussain Chinoy

Lessons from designing generative AI solutions inside Google Cloud, drawn from real product work. Useful when an enterprise team is shipping gen AI features and wants lessons from a team already in production.

Adam Fard

Adam Fard on new frameworks for designing AI-powered experiences, with templates teams can use. Useful when a team is starting an AI product and wants frameworks to organize their thinking.

Rafał Korzeń

Rafal Korzen shares twelve expert tips for designing human-centered AI experiences. Useful when a team wants a quick list of tips they can run through in a design review.

Lennart Ziburski

UX of AI is a curated site of patterns and examples for AI product UX. Useful as a reference when a designer wants to scan many examples of AI UX before designing their own.

Dive Club

Dive Club video on seven mental models designers can use when shaping AI products. Useful when a designer prefers learning by video and wants quick mental models to apply on real work.

Hal Wuertz

Hal Wuertz on what people designing for AI should know, with patterns for trust, errors, and feedback. Useful when a designer is moving onto an AI team and needs a starter mental model.

Justin Weisz

Justin Weisz lays out design principles for generative AI applications, drawn from IBM's research. Useful when a team is shipping a gen AI feature and wants principles backed by real research.

Brianna Koch

Brianna Koch on how a designer's intuition fits into a craft built around evidence and feedback. Useful when a designer is doubting their gut and wondering whether to trust it.

Ben Nadel

Ben Nadel on the UX of value in web app design, framing how users feel value through interaction. Useful when a web app team wants to think about value at the level of every interaction, not just features.

Dr Bart Jaworski

Dr Bart Jaworski explains what product value is and how to think about it cleanly. Useful when a team keeps using the word 'value' loosely and needs a sharper shared definition.

Zhaochang He

Zhaochang He on UX design for AI products, with patterns for prompts, results, and feedback. Useful when a team is building an AI product and wants a grounded set of UX patterns to copy.

Samiksha Makhijani

Samiksha Makhijani shares a real-world journey of designing user experiences for AI products. Useful when a designer is starting their first AI project and wants to learn from someone who already shipped one.

Ranjeet Tayi

Ranjeet Tayi's guide to designing for AI, focused on building trust, transparency, and guardrails. Useful when a designer is shipping AI features and worries users will not trust the output.

Alex Shires

Alex Shires on building ML-driven applications, with what designers need to know about the model and data. Useful when a designer is sitting between PM and ML engineers and wants enough context to contribute.

Ardavan Hp

Ardavan Hp explains adaptive user interfaces and how they revolutionize standard UX with smart context. Useful when a designer wants a primer on adaptive UI before pitching one to their team.

Tanmay Vatsa

Tanmay Vatsa walks through hyper-personalization in design with examples of tailoring each interaction. Useful when a team wants concrete examples of hyper-personalization before they pitch their own.

Maria M.

Designlab explains data-driven design in plain words, with examples of how teams use data in their process. Useful when someone new to data-driven design wants a friendly intro before joining a team that uses it.

uxplanet

UX Planet's ten core product design principles with examples for each. Useful when a designer onboarding a new teammate wants a single shared post to align on principles.

Chris Becker, MFA

Ten UI principles drawn from Dieter Rams and applied to digital product work. Useful when a designer wants a quick reference rooted in classic principles before a design review.

Fabricio Teixeira

Walks through a cringe-worthy real-world volume control as a lens on bad UI choices. Useful when a designer wants a sharp story to share in a critique on why details matter.

Paul Boag

Paul Boag shares ten UI design principles he learned the hard way through real projects. Useful when a UI designer or front-end dev wants a battle-tested checklist before shipping.

Fabian Gampp

Plain intro to systems thinking and what it offers compared to linear thinking. Useful when a team is hearing 'think in systems' and needs a starter explanation before diving in.

James Hostford

Government Digital Service post on how to find your way into systems work when the system feels overwhelming. Useful when a designer or policy person is new to systems thinking and not sure where to start.

Micheal Foley

Walks through a personal approach to content design and content strategy, with how the two stack together. Useful when a content lead is shaping their playbook and wants a worked example to react to.

Louisa Harper

Pushes back on content design being treated as editing or polish, with examples of what real content design looks like. Useful when a content designer needs language to explain their work and protect their seat at the table.

Mo Williamson

Maps the many job titles in content roles, like UX writer and content designer, and explains the differences. Useful when a hiring manager or candidate is sorting out which title and scope fits.

Kaysie Garza

Hotjar piece breaking down content design and showing why it is its own discipline, not a UX subset. Useful when a product team is structuring roles and wondering where content fits.

Lizzie Bruce

Argues content design should be compared to UX design, not to copywriting, with reasons rooted in process. Useful when a content lead is trying to set the right expectations for their team and partners.

Victor Beigelman

Asks why content design matters and where it pays off compared to plain copywriting. Useful when a leader is deciding whether to invest in content design as a discipline.

Louise Bruton

Plain explainer of what content design is and how it differs from UX writing or copywriting. Useful when someone new to the field or a stakeholder needs a quick orientation.

Jane Ruffino

Argues that content design is the user experience itself, not a layer on top of it. Useful when a content designer or UX lead needs to push back on being treated as a copy resource late in projects.

Elizabeth Churchill

Argues for a data-aware approach where designers know what data can and cannot tell them. Useful when a UX leader wants to push the team beyond surface-level dashboards into deeper questions.

Christopher Wong

Explains data-informed design as a growing role that mixes UX, analytics, and product sense. Useful when a designer or hiring manager is trying to scope this role or pitch it inside their org.

Alastair Simpson

Compares data-driven and data-informed design inside Atlassian and shows why mixing data with judgment beats either one alone. Useful when an enterprise team is fighting over whether tests or designer intuition should win an argument.

Aaron Gitlin

Pushes designers to move past being data-driven and become data-aware, treating data as one input alongside research and instinct. Useful when a design team is being pressured into A/B test culture and wants a healthier way to use data.

Helge Tennø

Helge Tennø argues thick and rich data should be available to every decision in a project, not stored away for special studies. Useful when teams default to dashboards for every call and you want a frame to widen the inputs.

Dr. Virendra Kumar Shrivastava

Argues big data and thick data complement each other — quantitative scale plus qualitative depth — to answer both what and why. Useful when teams treat them as either-or and you need to make the case for combining them.

Tricia Wang

Tricia Wang's foundational essay on why big data needs thick data, drawing from her Nokia case study and ethnographic work. Useful when leadership over-relies on dashboards and you need a classic source to explain why qualitative depth matters.

Jacqueline (Jax) Fouche

Jacqueline Fouche argues that thick data — qualitative, ethnographic insight — gives the why behind big data and acts as a leading signal for product teams. Useful when a team relies only on quant signals and you want to make the case for thick data investment.

Kashyap Vyas

Sogolytics post on keeping humans in the loop of AI decisions to maintain ethics, trust, and oversight. Useful when an AI feature is moving toward autonomy and you need a checklist for where human review should stay.

Britt Watwood

Britt Watwood reviews Ethan Mollick's Co-Intelligence framing of integrating AI without handing over our lives to it. Useful when planning AI usage policy and you want a short reflection to share with educators.

Eric Hudson

Eric Hudson on Substack defines being a 'good human in the loop' as bringing prior knowledge to prompting, evaluating, and reflecting on AI use. Useful when teaching students or staff to use AI tools without losing agency.

Leon Ho

Frames human-in-the-loop as a co-pilot model where humans steer and AI handles repetitive tasks while humans keep ethical judgment. Useful when explaining HITL to a team or deciding where humans must stay in an AI workflow.

Kike Peña

Argues that AI-driven fast UI generation is hurting designers' systems-thinking skills and pushing surface-level work. Useful when AI tools are speeding output but you suspect quality is slipping and want a frame to discuss it.

Stuart Kauffman

Stuart Kauffman TED talk explaining the adjacent possible from biology to computing and what it means for innovation today. Useful when introducing the concept to a team and you want a short, authoritative video to share.

Understanding Innovation

Argues for using the adjacent possible to evaluate technology — what does it expand, what range does it open, what should we mitigate? Useful when assessing a new technology and you want a frame for both upside and downside.

Scott Rosenberg

Scott Rosenberg connects blogging and the adjacent possible, arguing that writing for an audience changes how we read, think, and imagine systems. Useful when reflecting on how creative practice grows your range of ideas.

Steve Johnson

Steve Johnson's idea of the adjacent possible as a building of connected rooms where progress only moves one room at a time. Useful when explaining slow but real innovation to a team that wants giant leaps.

Daniel H

Daniel writes that exaptive innovation is about identifying existing patterns and bright spots inside the org and pushing them further. Useful when teams want fresh ideas but already have hidden bright spots no one is amplifying.

Ameet Ranadive

Frames innovation as remixing existing inputs at the frontier of the adjacent possible, with Tesla as a worked example. Useful when teams complain there are no new ideas and you want a frame for remixing what already exists.

Chris Loper

Defines the adjacent possible as the realm of new ideas reachable from what we already know, and shows how to nudge into it. Useful when feeling stuck on creative work and you want a frame for moving by small reachable steps.

Kyle Evans

Seven actions that elevate product thinking in a team, from clarifying outcomes to involving customers earlier and challenging assumptions. Useful when product thinking feels shallow and you want a list of moves to push it deeper.

Breana Jones

Curated Medium list of articles that elevate product mindset and unstick team thinking, by Breana Jones. Useful when looking for a curated reading list to share with new product folks.

Jeff Patton

Argues that the service-provider mindset baked into agile and corporate processes kills product thinking by replacing outcomes with output demands. Useful when teams measure delivery instead of impact and you need a frame to push back.

Sudarshan Sahu

Comprehensive guide that frames product thinking as the journey from user problem to product-market fit, walking through why, what, and how steps. Useful when joining a new product team and you want a single map of the design process.

Ali Raza Khan

Argues that product thinking lives at the company-strategy level by deciding what kind of product to be in a market, like Instagram versus Facebook. Useful when leadership asks why a feature focus is not enough and you need a higher-altitude answer.

Martina Sartor

Explores AI agents as digital companions and looks at design challenges, opportunities, and concrete strategies for shaping them. Useful when starting work on a conversational or agentive product and you want a survey of the design space.

Noman Siddiqui

Argues UX must now serve three users — customer, employee, and AI agent — and shows how to design data and interfaces for agent participation. Useful when adding AI agents to an existing product and the team has not thought about machine-readable design before.

Greg Nudelman

Introduces a four-capability framework — perception, reasoning, memory, agency — for evaluating AI agents and shaping the user interaction. Useful when building AI features and you need a checklist for what the agent can sense, think, and do.

Kshitij Agrawal

Defines agentive UX as designing for systems that act on the user's behalf, drawing on Christopher Noessel's framework, and shifts the goal from tasks to outcomes. Useful when designing AI-powered features that work in the background and you need new design rules.

Tyler La

Explains why pairing systems thinking with design thinking helps designers balance stakeholders, business goals, and engineering limits. Useful when scaling a design practice and you want both holistic thinking and fast iteration on the same team.

Stewart Dean

Argues that surface thinking — jumping to UI sketches — leads to fragile design, and that teams should sit with the messy middle to find real solutions. Useful when a team rushes to interfaces before understanding the system behind the problem.

Cara Tomko

Frames systems thinking as a way for designers to make more ethical, holistic choices, with mapping as the core technique to find leverage. Useful when a project's effects ripple beyond the screen and you need a shared map to navigate.

Erica R. Wexler, MSOD

Academic framework that combines design thinking's prototyping with systems thinking's whole-context view to tackle complex org problems. Useful when leading work on org or service problems where one lens alone misses the wider context.

Boon Yew Chew

Shares a designer's first-person account of weaving systems thinking into everyday design work to handle complex problems. Useful when you want practical examples of bringing systems thinking into your own design practice.

Nikhil Mahen

Argues systems thinking and design thinking sit on a spectrum and are most powerful when used together rather than chosen between. Useful when teammates debate which mindset to apply and you need a shared frame for combining the two.

Nicole Yu

Argues that putting customer desirability ahead of feasibility or viability widens the range of problems a business can solve. Useful when innovation efforts feel constrained by tech or finance and you want a fresh starting frame.

Kelly Custer

Argues desirability comes from strategy — meeting a real need, an enticing aesthetic, and a delightful experience aimed at a clear target. Useful when pitching a new product idea and you need a frame to show why design choices were intentional.

Ward Andrews

Explains product thinking as a holistic mindset for finding what makes a product useful, and contrasts it with feature-only design thinking. Useful when leadership asks you to define product thinking and explain why every team should practice it.

Sophia Latache

Frames product thinking as a problem-solving skill open to anyone on the team, not just PMs, and shows how to spot when it is missing. Useful when you want to grow product thinking on a cross-functional team without changing roles.

Chelsi N.

Argues product thinking is problem-solving for users rather than feature-adding, and outlines how to keep needs central while designing. Useful when a team's design work feels feature-driven and you want a frame to refocus on user problems.

Merissa Silk

Shows how to push product thinking into any team using impact-effort and impact-unknowns matrices to expose assumptions early. Useful when teammates jump to fully formed feature ideas and you want a tool to slow that down.

Laurence Berry

Traces how service patterns moved from UK gov roots into a global pattern library that helps teams reuse proven service designs. Useful when you want context on why service patterns matter and how big orgs are building shared libraries.

Rikke Friis Dam

Lists service design principles including customer-centered demand, unified delivery, and value creation, drawn from Design4Services. Useful when starting a service design project and you need a shared frame for what the service should do for users.

Carol Rossi

Argues that more studies are not always better and that researchers should ask whether each project provides business value before running it. Useful when a research team feels stretched and needs a frame for saying no or pushing back on low-value requests.

Sherry W.

Reflects on Erika Hall's Just Enough Research and how to find a workable middle ground between too much and too little research on a project. Useful when scoping a study and trying to decide how deep to go before analysis paralysis or guesswork takes over.

Contentsquare

Contentsquare's guide compares product design and product management roles - different goals and workflows but stronger together. Useful for new teams clarifying who owns what across research, iteration, and shipping.

Reece Rogers

Reece Rogers and Pattie Maes warn AI agents are still tricked easily and that misplaced confidence makes users trust them when they shouldn't. Useful when teams ship agentic features and need to design human-in-the-loop guardrails.

Jiquan Ngiam

Jiquan Ngiam (Lutra) argues AI agent UX is hard - users want real-time visibility into what the agent is doing, and the AI-computer interface layer is design-critical. Useful when teams build agentic features and worry about visibility and trust.

Greg Nudelman

Greg Nudelman's framework for agentic UX builds on four core capabilities - perception, reasoning, memory, agency - with a multi-stage Supervisor/Worker example. Useful when teams designing AI agents need shared design vocabulary.

Mary Daniel

Mary Daniel's Wix UX piece on building human-centered AI experiences covers trust, transparency, honesty, control, and humanity as guiding principles. Useful as a starter set of AI UX principles for product teams.

Sarah Tan

Sarah Tan argues traditional design thinking falls short for AI products because of new complexity and edge cases. Useful when design teams hit the limits of user-centered thinking on AI features.

Anthony Pierri

Anthony Pierri's positioning formula is Target Customer + Differentiation, with the discipline to focus on one segment, one use case, one channel. Useful when startups try to appeal to everyone and end up reaching no one.

Robert Kaminski

Robert Kaminski lays out three levels of product-market fit - Feature, Product, Platform - and argues founders should start with feature-level fit. Useful when founders are stuck building too much, too soon.

Owen D.

Owen Derby shares Workday's Human-AI Experience guidelines built around explainability, user control, learning over time, and accurate mental models. Useful when enterprise design teams need a starting set of AI UX principles.

Mary Daniel

Mary Daniel offers five principles for human-centered AI: trust through reliability, transparent reasoning, honest disclosure, user control, and protecting humanity. Useful when product teams design AI features and need shared guardrails.

Grace Hwang

Grace Hwang reminds teams that tech is a tool, not the goal, and AI is a creative partner that needs verification. Useful when product teams over-rely on AI and lose touch with real human needs.

Jagna Birecka

The article argues that outcomes alone don’t create direction, and that teams mistake outcome statements for strategy when they lack intent, tradeoffs, and decision logic. Use this when clarifying why outcome-driven language isn’t improving execution and when deciding how to pair outcomes with real strategic choices.

Jascha Goltermann

The article explains that outcomes only become useful when they are treated as signals that inform decisions, not as strategy or goals in themselves. Use this when clarifying how outcomes should guide choices, ownership, and learning rather than replacing intent, planning, or leadership judgment.

Jason Yip

The article explains that outcomes only become useful when they are treated as signals that inform decisions, not as strategy or goals in themselves. Use this when clarifying how outcomes should guide choices, ownership, and learning rather than replacing intent, planning, or leadership judgment.

Jaime Diaz Beltran

The article explains why outcomes should not be treated as goals, arguing that outcomes are signals that inform decisions, while goals represent intent and direction. Use this when clarifying how to frame goals, outcomes, and metrics so teams don’t confuse measurement with strategy.

Mike Lingle

The article argues that focusing on outcomes alone is insufficient unless teams also clearly define which outcomes matter, how they will be measured, and who is accountable for achieving them. Use this when diagnosing why an “outcomes over outputs” shift isn’t improving decisions and when clarifying ownership, metrics, and intent behind outcome statements.

Jim Semick

The article argues that product discovery shouldn’t be treated as a one-off project phase but as an ongoing, team-wide practice that continuously refines customer understanding, problems, and validated solutions through collaboration. It highlights that great discovery combines qualitative and quantitative insights, involves cross-functional teams early, and keeps learning loops short to decrease risk and increase confidence. Use this when you’re deciding how to structure your discovery practice and integrate it into delivery cycles rather than treating it as a separate upfront step.

Steve Mullen

This article explains the fundamentals of product thinking, focusing on solving user problems by aligning business goals, user needs, and solutions. Use this when a team needs to decide whether they are building the right thing, not just building it well.

Naren Katakam

This article explains the fundamentals of product thinking, focusing on solving user problems by aligning business goals, user needs, and solutions. Use this when a team needs to decide whether they are building the right thing, not just building it well.