Philip Seifi

Philip Seifi shows how to build a Python pipeline using Intercom, Typeform, Airtable, pandas, and Plotly to distribute and analyze a Sean Ellis PMF survey. Useful when running PMF surveys and you want a tooling setup to close the feedback loop.

Adrian Cleave

Adrian Cleave shares how Airbnb built a DesignOps team across program management, design tools, localization, production design, and team coordination. Useful when scaling design and you want a real-world model for DesignOps.

ProductPlan

ProductPlan beginner's guide to product launches covering market research, positioning, messaging, marketing and sales, timeline, budget, and post-launch metrics. Useful when running a launch for the first time and you need a comprehensive plan template.

Userpilot

Userpilot's product launch checklist split into pre-launch, launch, and post-launch phases with goals like sign-ups, adoption, and sales. Useful when running a SaaS launch and you need a clear three-phase plan with shared steps for product, marketing, and sales.

Lindsay Kolowich Cox

Step-by-step product launch checklist from HubSpot covering picking a date, prepping the team, and using planning templates. Useful when planning a launch and you want a structured, time-boxed checklist.

John Cutler

John Cutler revisits his feature factory list three years later, sharing what works to escape it, like leaders who bake outcome reviews into how everything runs. Useful when a team has tried to break out and wants newer thinking on what actually moves the needle.

Teresa Torres

Teresa Torres lays out three best practices for continuous discovery: weekly customer touchpoints, infrastructure for fast learning, and a continuous mindset. Useful when starting continuous discovery and you want guardrails from the start.

Andrew Miller

Tells the story of moving from a feature factory to continuous discovery in one year using cross-functional teams, dual-track agile, and outcome-focused KPIs. Useful when a team wants a real-world playbook for breaking out of feature factory mode.

Katie Marcus

Recap of one quarter spent running continuous discovery, including OKRs that include weekly user talks, dual-track issues, and how the team learned to ship experiments faster. Useful when a team has just adopted continuous discovery and wants honest lessons after one cycle.

Finn Kollerup

Lists ten skills good innovation managers need and the typical obstacles that get in their way, like weak executive support and missing strategy. Useful when hiring or supporting an innovation manager and you want a clear skill and obstacle list.

Julian Wright

HBR piece arguing that products should be built with feedback loops baked in, so customer data flows back into machine learning and improves the product. Useful when planning a product where data and AI can compound learning over time.

Tim Herbig

Lays out a discovery structure with six steps, time-boxed to six weeks and split between problem space and solution space. Useful when setting up a discovery sprint and need a clear schedule with stakeholder check-ins.

Kinjal Dagli

Calls out six common discovery mistakes like confirmation bias, late validation, and weak feedback tools. Useful when a team's discovery is producing thin or biased results.

Irit Eizips

Walks through an eight-step customer engagement process across the lifecycle, with a customer relation matrix and outcome matrix. Useful when a customer success team wants a repeatable engagement playbook.

ANDREA RABINELLI

Walks through an IDEO tool that helps designers run concept tests in an ethical way, especially at scale where research quality and consent can slip. Useful when running large studies and you want a check on ethics, bias, and harm.

Brian Peterson

Splits releases (delivering code to production) from launches (delivering value through go-to-market) and points out both need plans and PM ownership. Useful when defining who owns what across software shipping and marketing teams.

Grace N.

Shares simple tips for getting more from a design review, like running a mini review first, setting context, and asking for the right kind of feedback. Useful when you want feedback that helps the work and doesn't bruise egos.

Marija Dimović

Shows how design implementation reviews keep designers, developers, and testers in sync so designs ship as intended. Useful when handoff goes wrong and the final build doesn't match the design.

Tim Herbig

Lists common traps in continuous discovery, like talking to users too often, doing it without strategy, or chasing tests with too little traffic. Useful when a team has adopted continuous discovery but isn't seeing payoff.

Maxence Mauduit

Reflects on common product discovery mistakes a team made and what they learned over time, like skipping outcomes or chasing too many ideas at once. Useful when a team is starting or fixing their discovery process and wants to avoid known traps.

Sophia Höfling

Argues product discovery is messy and only works when a multi-skilled team coordinates synchronously around a shared objective. Useful when one person is doing all of discovery and the team is missing the value of working through it together.

Brett Truka

Practical playbook for roadmap presentations: pre-align with execs, use visuals, save details for other audiences, handle questions live. Useful when prepping a roadmap review and you want fewer surprises in the room.

Sean Morrison

Shows how to bring dual-track into a Kanban board by tagging Discovery and Development tasks with timeboxed discovery tickets. Useful when a Kanban team has hidden discovery work that never makes it on the board.

Carlos González De Villaumbrosia

Connects dual-track agile to its 2007 roots, explains continuous discovery alongside delivery, and stresses that we need to build the right product, not just build it right. Useful when introducing dual-track to a new team and you want a primer with history.

Shamsi Brinn

Designer’s view of dual-track agile and how it removes the over-the-fence handoff between UX and engineering. Useful when designers feel stuck creating in isolation and tossing artifacts to dev.

David Denham

Argues that Lean and Agile usually focus on delivery velocity but learning velocity matters just as much, and dual-track agile (with Design Sprints) blends both. Useful when teams ship fast but rarely learn from what they ship.

CSM Practice

Conversation on transforming SaaS customer onboarding for adoption, with focus on the first 30-90 days and time-to-value. Useful when CS and Product need a shared playbook for the early customer window.

Trevor Hatfield

Ten onboarding strategies for B2B startups, structured around basics, then features, then advanced use, with continuous adjustment from feedback. Useful when planning a B2B onboarding flow that must scale with feature growth.

Rachel Posman

Splits Salesforce DesignOps into Team Ops (org-wide programs) and Product Ops (deep with product teams) and shows how the two scale design together. Useful when DesignOps is doing too much and you need a way to split the work cleanly.

Adriana Katrandzhieva

ThoughtWorks talk on running parallel discovery and development tracks that constantly feed each other with hypotheses to test. Useful when teams need a clear visual of how dual-track agile actually flows.

Jeff Patton

Argues dual-track development is two kinds of work, not two teams: developers belong in discovery and designers in delivery, with shared outcome ownership. Useful when dual-track has split a team into two camps doing handoffs.

Popular Pays

Pop Pays runs dual-track agile with discovery 1-2 sprints ahead of delivery, fed by Pendo, CSM input, and quarterly customer interviews into a scored feedback board. Useful when wiring up a feedback system that actually drives the backlog.

Niamh Parsley

Story of how Spotify grew service design from two people to 50+ practitioners through community, career frameworks, and clever internal tactics. Useful when planning to scale a design discipline without hiring an army.

Clement Kao

Breaks product sense into eight components and shows how to use generative AI to practice exercises like pre-mortems, segment analysis, and one-pagers. Useful when a PM wants a faster way to build product judgment without years of experience.

Ioana Teleanu

Podcast episode on getting buy-in for design and research, including how to present decisions clearly and what to do without impact data. Useful when prepping for a stakeholder review and you want practical talking points.

Sachin Rekhi

Shows how the best teams build an automated loop to gather, record, and synthesize customer feedback into the roadmap, with examples from LinkedIn and Notejoy. Useful when feedback is being collected but not consistently fed into product decisions.

Carlos González De Villaumbrosia

Ten concrete ideas for using AI to automate roadmap tasks, spark creativity, and keep planning organized. Useful when a PM wants quick wins for using AI inside their roadmapping workflow.

Luke Pivac

Practical playbook for spotting, raising, and clearing blockers using stand-ups, swarming, and breaking work into smaller pieces. Useful when a team keeps stalling and you need rituals to surface impediments faster.

9m Consulting

9m Consulting shows how strategy, design, and testing work together so teams keep learning while building. Useful when a team treats strategy and testing as separate phases.

Ofer Senderey

Ofer Senderey shares four tips for weaving user testing into the regular product workflow. Useful when a team treats user testing as a one-off event rather than a habit.

Product Owner Summit

Product Owner Summit shows how cross-functional discovery becomes a team sport, with practical patterns. Useful when leaders want to scale discovery beyond a single PM.

Jeff Gothelf

Jeff Gothelf argues product discovery is a team sport, not a single role's job. Useful when discovery work keeps falling to one person and stalls.

Teresa Torres

Teresa Torres shows how anyone can do continuous discovery with weekly customer touchpoints. Useful when a team wants to start discovery but feels they don't have time.

Stephen Butts

Stephen Butts argues cross-functional collaboration speeds product development and reduces rework. Useful when teams are siloed and shipping the wrong thing.

Louron Pratt

Karishma Irani at LaunchDarkly explains how a triad with dual-track agile splits discovery and delivery between three roles. Useful when a product org wants to add real discovery without slowing delivery.

Timothy K.

Timothy Kolke shares how Later solved triad collaboration by improving prioritization and dev estimation early. Useful when a triad is bogged down by misaligned priorities and slow estimates.

Allison Winter

Allison Winter shows how the PM, engineering, and design triad collaborates with a clear working agreement. Useful when a new triad needs a starter ritual to get aligned.

Maggie Sun

Maggie Sun walks through Gartner's Integrated Risk Management framework, showing how to view risks across an org instead of in silos. Useful when a leader wants one connected view of risk for planning and reporting.

Tim Herbig

Tim Herbig argues the real issue is not discovery itself but jumping to delivery without aligning ideas, validating problems, and using tools like the Test Card. Useful when teams blame discovery for slow progress and need a sharper diagnosis.

Jon Kolko

Jon Kolko argues that healthy design critique is the engine of innovation cultures and shows how to run them. Useful when a design team wants to build a regular critique habit that improves both work and trust.

Heikki Hellgren

Argues that DevOps teams need fast user feedback loops to decide what to build next, and outlines automation and manual options. Useful when an engineering team wants to plug user feedback into a continuous delivery process.

Dr Bart Jaworski

Lays out best practices for treating user feedback as a measurable signal and consolidating sources into one report. Useful when a PM wants to make user feedback a real driver of roadmap decisions.

Jessica Kende

Compares product design and growth design across timeline, scope, and stakeholders, with growth design running short monthly experiments. Useful when a designer is moving into a growth role and needs to understand what changes day to day.

Soham Sharma

Walks through what a successful product launch looks like and the steps to plan one well. Useful when a product team is preparing for launch and needs a clear process from prep to release.

Team Maxio

Argues that B2B brand advocates are an underused, low-cost growth channel and shows how to identify them inside your customer base. Useful when a marketing team wants to start a customer advocacy program but does not know where to begin.

Frederick O'Brien

Frederick O'Brien on designing the documentation itself for web design teams. Useful when teams want their docs to feel as polished as their products.

Teresa Torres

Teresa Torres talks about pulling engineers fully into the product trio and discovery work. Useful when engineers are skipping discovery and design feels like the only voice for users.

Vishnu Pillai

Argues that a tight trio of PM, design, and engineering drives better product outcomes. Useful when leaders want to convince stakeholders to invest in cross-functional discovery.

Cezara Moisuc

Cezara Moisuc combines the product trio with the opportunity solution tree as a discovery duo. Useful when a team wants a clear playbook for ongoing discovery work.

Steve Tsentserensky

Steve Tsentserensky explains the Agile UX process, where UX work runs alongside Agile development through close team collaboration. Useful when teams new to Agile UX need a high-level walk-through.

Craig Strong

Craig Strong explains how to set up a Product Portfolio Council and a Portfolio Manager who connects strategy to decisions and tooling. Useful when an org is shifting from project to product mode and decision rights are fuzzy.

Mike Cohn

Mike Cohn's reference page explains the user story format, the three Cs (card, conversation, confirmation), and gives sample stories from real projects. Useful when teams need an authoritative, plain-English source on what a user story is and how it works in scrum.

Anum Hassan

Anum Hassan on iterative product design steps for continuous improvement. Useful when teams want practical iteration steps to copy.

Nick Babich

Nick Babich's overview of common UX design deliverables. Useful when teams want a reference list of artifacts to consider.

Sachin Rekhi

Sachin Rekhi on building a continuous feedback loop into your product. Useful when teams want fresh signal between releases.

Quinn Keast, CDP

Quinn Keast on 'design syntropy', tying artifacts together so they reinforce each other. Useful when artifacts feel disconnected.

Slava Shestopalov

Slava Shestopalov on why people ignore your great design docs. Useful when teams write thorough docs that no one reads.

Heidi Adkisson

Heidi Adkisson argues documenting is part of designing, not extra work. Useful when teams treat docs as overhead and skip them.

Sunlight Foundation

Step-by-step guide to running co-design sessions in civic and community contexts. Useful when you are running a community session and need a structured plan.

Linda Le Phan

Step-by-step intro to handing off designs to developers using clear specs and asset prep. Useful when you are new to handoff and need a checklist to follow.

Ben Shih

Practical guide to organizing Figma files so developers can actually use them at handoff. Useful when devs keep asking 'where is X?' in your Figma files.

Ron A

Looks at handoff in agile teams where design and dev work in tight loops. Useful when sprints are tight and traditional handoff feels too heavy.

Joe Munko

Argues that disposable research is worse than skipping research, and pushes for studies that produce timeless insight. Useful when a research lead is rethinking how to plan studies that pay off long after the sprint ends.

Austin Govella

Explains why teams drift from project goals and how to keep alignment by revisiting goals throughout the work. Useful when a project keeps shifting and you need a way to anchor decisions back to a shared goal.

Rashika Ahuja

Rashika Ahuja walks through building an effective design management process. Useful when a design lead has no formal process and wants a starter kit.

UXPin

UXPin guide on how to manage design teams effectively. Useful for new design managers building habits and rituals from scratch.

Anna Efimenko

Anna Efimenko introduces UX research at Booking.com, blending data and empathy. Useful for research leaders wanting an example from a large data-rich company.

Theertha Raj

Theertha Raj's full guide to research ops, often called the ReOps bible. Useful when building or revamping research ops from scratch.

Julian Della Mattia

Julian Della Mattia argues every team should have research ops, not just big ones. Useful when a small team is debating if research ops is overkill.

Janelle Ward

Janelle Ward shares scrappy ways to do research ops without big tools or budget. Useful for solo researchers building ops habits on the cheap.

Rachel Miles

Rachel Miles walks through building a research ops framework that fits your org. Useful when a research lead needs a starting structure for the function.

Ella Webber

Ella Webber explains how research ops boosts research efficiency for product teams. Useful when leaders are deciding if research ops is worth investing in.

Emma Boulton

Emma Boulton shows how community-driven research ops creates real impact. Useful when starting or scaling a research ops function.

Luca Micheli

Luca Micheli walks from feedback collection to acting on insights with a clear loop. Useful when teams collect feedback but never turn it into changes.

Klaus Salchner

Klaus Salchner explains why short feedback loops beat long ones for both teams and products. Useful when a leader wants to push teams toward shorter cycles.

Gainsight

Gainsight explains how to embed feedback collection inside product delivery. Useful when product and CS teams collect feedback in silos.

Sajid Sadman

Sajid Sadman lays out the four stages of a strong customer feedback loop. Useful when a support team wants a starting structure for handling feedback end to end.

Alyona Medelyan

Alyona Medelyan walks through three ways to close the feedback loop and prevent churn. Useful when a CX or product team is losing customers despite collecting feedback.

Michael Fordham

Michael Fordham gives a full guide to running iterative design as a UX designer. Useful for a designer setting up an iteration plan from scratch.

Corey Hobson

Corey Hobson shows how to bake continuous improvement into a UX design process. Useful when a team wants iteration to be a habit, not a special project.

Jakob Nielson

Jakob Nielsen explains iterative interface design and why repeated rounds of testing keep improving usability. Useful when a team needs to defend why iteration time matters.

Paige Bennett

Paige Bennett looks at the role of feedback in design work and team change. Useful when teams want to build healthier feedback loops as they grow.

Sohaib Thiab

Sohaib Thiab walks through implementing a product trio step by step. Useful for managers rolling out a trio model across multiple squads.

Matt Paige

Matt Paige argues many product failures trace back to missing a real product trio. Useful when leadership is debating if siloed teams are slowing product progress.

Honza Bělohlávek

Honza Belohlavek explains the product trio, who belongs in it, and how it works in practice. Useful when a team is forming or reshaping a discovery group for the first time.

Yannis Karampelas

Yannis Karampelas at Userfeel explains how to set up an ongoing usability testing program inside a Lean UX rhythm. Useful when a team wants to make testing a habit, not a one-off.

Philip Wallage

Philip Wallage at BTNG.studio shows how building empathy maps with stakeholders bridges the gap between design and business. Useful when designers and execs disagree on user priorities.

Julia Martins

Julia Martins at Asana defines the iterative process as a five-step loop of plan, design, create, test, and refine. Useful when a team is new to iteration and wants a clean five-step model.

Elise Bentley

Elise Bentley explains how SaaS onboarding gets better through iterative testing and continuous investment — not a one-shot redesign. Useful when an onboarding flow is treated as a project instead of a long-running practice and a team needs to make the case for continued work.

Andrew Birgiolas

Andrew Birgiolas walks through six steps the Sephora team used to redesign their app using research and rapid iterative testing. Useful when a team plans a major redesign and needs a real playbook with results.

Lorraine P.

Lorraine Phillips lays out an iterative UX design process for beginners that pulls developers and stakeholders in at every step. Useful when a junior designer needs a clear picture of how research, design, and dev should overlap.

Susan Farrell

Susan Farrell's NN/g cheat sheet maps which UX activities and research methods fit each project stage, from strategy to handoff. Useful when planning a quarter and you want to make sure research lands at the right moments.

Cintia Romero

Cintia Romero shares simple tactics for telling clear, respectful stories during design critiques so feedback stays useful. Useful when reviews go off-track and you need the team to focus on the most important point.

Kannu sharma

Kannu Sharma explains how to communicate design intent — bridging ideas and the reality of execution so engineers and stakeholders read the design correctly. Useful when designers feel their intent is getting lost between handoff and shipping.

Ignacia Orellana

GOV.UK shares ten principles for service patterns — covering reuse, accessibility, governance, and how patterns evolve. Useful when a public-sector or large-org team wants a tested rulebook before building their own pattern library.

Jeanette Clement

Jeanette Clement shares how BT/EE uses service patterns — reusable building blocks for end-to-end services — to ship faster across many products. Useful when a service-design team is trying to scale and wants a real example of patterns at work.

Agoda

Agoda's engineering team shares how they moved from pixels to product by innovating with their design system — including tokens, automation, and developer experience. Useful when a design-engineering team wants a real-company example of investing in design systems for engineering speed.

Pedro Santos

Pedro Santos walks through creating a design system from scratch — audit, naming, tokens, components, and rollout. Useful when a designer has been handed a blank slate and wants a sequenced playbook from someone who has done it.

Gabe Tamborini

Gabe Tamborini outlines a lean research loop for digital products — frame, run, learn, share — that fits between sprints. Useful when a research team wants a tight ritual that fits agile cadence rather than living outside it.

Lorraine Phillips

Lorraine Phillips lays out an iterative UX design process for beginners that loops business stakeholders into every step. Useful when a UX lead keeps getting blocked by late-stage business pushback and wants a process that builds buy-in along the way.

Eleken.

Behind-the-scenes look at how DesignOps runs at Eleken — covering project intake, designer staffing, and quality reviews. Useful when a small agency or in-house team wants a concrete example of DesignOps in a lean setup.

Ahmed Ben Salem

Walks through the INVEST criteria — Independent, Negotiable, Valuable, Estimable, Small, Testable — and how to use them as a checklist when refining a story. Useful when a team's stories feel sloppy and they need a quick test to see whether each one is sprint-ready.

Hoa Loranger

Page Laubheimer and Hoa Loranger show how to write user stories that account for UX work — research, design, and content — not just engineering tasks. Useful when UX work keeps getting squeezed in agile sprints and the team needs a story format that makes design effort visible.

( )

Ron Jeffries' classic short post argues a user story is not a written document but a placeholder for a conversation between team and user. Useful when a team has turned stories into long Jira tickets and forgotten that the value is in the conversation.

Jacob H.

Simple, opinionated guide for writing better user stories — keep them short, focus on user value, and skip the technical detail until later. Useful when story drafts are bloated with implementation notes and the team needs a quick reset on the format.

@Max Rehkopf

Atlassian's reference page on user stories — the As-a / I-want / So-that format, examples, acceptance criteria, and how stories fit into agile backlogs. Useful when a team is new to user stories and needs a single page to align on the template and ground rules.

Kim Peterson Stone

Practical guide for B2B teams on stitching together marketing, sales, and customer success around a single journey view, with checks for where ownership breaks down. Useful when leaders see hand-off gaps between teams and want a clean way to assign who owns each stage.

Jeff Patton

Jeff Patton on the continuous product improvement cycle. Useful when teams want a named cycle to guide ongoing improvement.

Kyle Sandburg

Kyle Sandburg on continuous product management and the rituals that support it. Useful when PM teams want to mirror continuous design.

Awesomic

Awesomic's deep guide to continuous product design. Useful when teams need a long primer to plan a continuous practice.

Mikael Vesavuori

Mikael Vesavuori on continuous design and the systems that enable it. Useful when teams move from set design phases to ongoing design.

Rebecca Nguyen

Rebecca Nguyen on three content design artifacts she relies on every day. Useful when content designers want a starter kit of artifacts.

Thomas Budiman

Thomas Budiman frames design artifacts as a journey, not a final product. Useful when teams polish artifacts too long and lose focus.

Mayya Azarova, Ph.D.

NN/g video on how context boosts the value of UX artifacts. Useful when artifacts get shared with no setup and lose meaning.

Robin Rendle

Robin Rendle's notes on what design artifacts mean in practice. Useful when teams want a thoughtful, plain-language take on artifacts.

Nwajuo Sophia

Walks through user flows, wireframes, and prototypes and when each one shines. Useful when designers wonder which artifact to make next.

Jorge Arango

Jorge Arango on the real purpose of design artifacts and when they earn their keep. Useful when teams produce too many docs that no one uses.

Anna Kaley

NN/g on lean UX documentation for tracking and communicating in agile. Useful when agile teams want light docs that still capture key signals.

Rina Artstain

Rina Artstain on writing a design document that actually drives action. Useful before authoring a doc to align teams on a feature.

Dirkjan Kraan

Dirkjan Kraan's practical guide to design documentation. Useful when teams want a simple template for design docs.

Beau Ulrey

Beau Ulrey on collaborative user research with non-researchers in the room. Useful when teams want PMs and devs in the research, not just at the readout.

Susan Farrell

NN/g guide to collaborating with stakeholders during UX research. Useful before kickoff so stakeholders feel part of the work.

Jacqueline (Jax) Fouche

How Jax Fouche built a framework for continuous research. Useful when researchers need a clear blueprint to scale.

Bryan Zmijewski

Bryan Zmijewski's five-step framework to kickstart continuous discovery. Useful when teams need a quick, named plan to get started.

Laura Carroll

Story of how Medium implemented continuous user research. Useful when teams want a real-world model of continuous research at scale.

Allison Grayce Marshall

Part one of a series on continuous research for research enablement teams. Useful when ResearchOps leaders are setting up enablement programs.

Maria Panagiotidi

Maria Panagiotidi's how-to guide for moving from no research to continuous research. Useful when small teams want to start research from scratch.

Saravanan Kasi

A simple, universal design process with phases that can flex for any project. Useful when teams want one shared process they can adapt.

Jeff Pelletier

Common pitfalls teams hit when building or running design systems. Useful before kicking off a system to avoid known traps.

Ofer Senderey

Four practical tips for fitting user testing into a normal product workflow. Useful when teams say they want to test more but never find the time.

Robert Meza

Combines journey mapping with behavioral science to find better intervention points. Useful when you want a mash-up method to spot where behavior change is possible.

Marianela Grande

Walks through using behavioral journey maps as part of a product design process. Useful when standard journey maps feel flat and you want to add behavioral lenses.

Beacon Strategies

Step-by-step playbook for running a co-design project from kickoff to delivery. Useful when you are leading your first co-design project and want a clear path.

Voltage Control

How to apply human-centered design when planning organizational change. Useful when leading a change effort and want HCD methods to guide it.

Adam Fard

Practical tips for smoother handoff between designers and developers, with templates. Useful when handoff still feels rocky and you want concrete moves.

Daniel Schifano

Four-step framework to clean up your handoff process and reduce friction. Useful when you want a quick recipe to improve handoff right now.

Experience Design Academy

Best practices and case studies on design handoff between design and dev teams. Useful when handoffs feel painful and you want examples of what good looks like.

Thumỹ P.

Walkthrough of iterative study design and how to follow up qualitative studies effectively. Useful when first-round research left questions and you need a structured way to dig deeper.

Bryan Zmijewski

Argues iterative research drives continuous improvement by feeding small studies into product cycles. Useful when you want to embed research as an ongoing rhythm rather than a one-off.

Jack Moffett

Three-part series on detecting, tracking, and avoiding UX debt with documentation and self-use of the product. Useful when you want a fuller playbook for spotting and stopping UX debt before it grows.

Rohit Nair

Walks through a real UX writing process: kickoffs, working with PMs and devs, and a three-step internal review. Useful when you are setting up or improving how your UX writing team works inside sprints.

Christopher Wong

Argues that scope creep is best avoided with a clear, simple problem document up front. Useful when a team starts projects with vague problems and ends up arguing about scope later.

Owen Jones

Stack Overflow blog on how to prevent scope creep when running a project from kickoff to launch. Useful when a project lead is starting a new project and wants guardrails baked in from day one.

Lorenz Hofmann-Wellenhof

Spicy take from an engineer on the design rules they will reject pull requests over. Useful when a design system or front-end team wants a conversation starter on what should be enforced.

Ed Park

Practical playbook for PMs on how to work well with product designers, including handoffs and feedback. Useful when a new PM is starting a partnership with design and wants to get off on the right foot.

Alex Cringle

Shows how to set up a product discovery framework that works inside an agile delivery team. Useful when a PM or design lead wants to plug discovery into an existing sprint cadence without burning the team out.

Sophia Höfling

Gives a four-step daily discovery routine teams can run alongside delivery without slowing down. Useful when a team wants discovery to be a habit, not a separate phase or workshop.

Rachel How

Rachel How's video shares tips for designers collaborating with PMs, including communication, shared context, and asking for context early. Useful when a designer feels out of the loop with their PM and wants a short refresher.

Timothy K.

Tim Kolke's PM guide to working with UX designers covers the product triad model and the typical decision-rights confusion. Useful for PMs who want to set up clearer collaboration with their UX partner from day one.

Reddit, Inc.

Reddit thread where PMs and designers share how they navigate overlapping responsibilities through open conversation, empathy, and clear ownership. Useful when role friction is high and you want practitioner advice on aligning before working.

Andrea Karina Burgueño

IBM zCX case study using collaborative journey mapping to validate go-to-market touchpoints and find where users get stuck. Useful when adopting a new product and you want a real example of validating maps with users.

Melanie Long, CCXP

Outlines how collaborative journey mapping workshops bring stakeholders into the customer experience conversation rather than presenting maps after the fact. Useful when CX maps sit unused and you want stakeholders to feel ownership.

Jenn Lindeman

Story mapping as a tool to turn product, design, and stakeholder conversations into a shared visual narrative of the user's journey. Useful when teams over-rely on docs and you want to surface real conversation around user value.

Joshua Render

Joshua Render's quick guide to splitting stories with developer help, focused on cutting big requirements into pieces that fit one iteration. Useful when devs and PMs disagree on size and you need a method that pulls them into the conversation.

Mark Shead

Discusses splitting stories so each represents one or two days of work, with examples and reasons for slicing thinner. Useful when starting agile practice and you want a baseline rule of thumb for story size.

Patrick Sauerwein

Shows how Gherkin Given-When-Then steps make user stories thinner, more granular, and easier to prioritize. Useful when a team writes Gherkin scenarios and wants those same scenarios to drive how stories get split.

Steve Bishop

Three simple ways to split stories — clear acceptance criteria, scope-not-time framing, and reducing team stress — with worked examples. Useful when a team is anxious about big stories and you want a low-overhead way to break work down.

Reddit, Inc.

Reddit Scrum thread on story slicing that discusses vertical versus horizontal slicing and getting feedback faster from thinner stories. Useful when a team debates how to slice stories and you want a quick read of community advice.

George Dinwiddie

Suggests slicing user stories by separating ATDD examples into groups so each example becomes its own smaller story. Useful when example mapping is already part of your flow and you want a natural way to split as you go.

Peter Green

Humanizing Work guide consolidates over a decade of story-splitting practice into a flowchart and INVEST-based heuristics. Useful when a backlog has chunky stories and you want a single, structured reference your team can follow.

Mike Cohn

Mike Cohn's SPIDR method splits user stories by Spike, Path, Interfaces, Data, or Rules, with examples of each. Useful when a story is too big to estimate and you need a quick toolkit for slicing it into smaller, valuable pieces.

Wiebke Kudernatsch

Day 1 of a five-day product design sprint focused on building a product experience map and storyboarding the ideal user flow. Useful when running a design sprint and you want a clear plan for the first day's mapping work.

Nicole Nardelli

Uses Playmobil figures to walk through a museum experience map, blending physical and digital touchpoints into one journey. Useful when designing for cross-channel experiences and you want a low-cost way to walk through user steps with the team.

Georg Maureder

Real-world case study where one team replaced HiPPO calls with shared experience maps to align decisions and reveal context. Useful when stakeholders override design choices and you want a workflow that brings the user back into the room.

Bryan Zmijewski

Bryan Zmijewski post on how consistent, measured design loops help teams build confidence and improve faster through customer feedback. Useful when a design team feels stuck and you want a frame to argue for tighter learning cycles.

Sūryanāga Poyzer

Argues that local councils should standardize core services like parking permits or bin collections, but not centralize delivery, so users get a similar experience everywhere. Useful when designing across federated teams and you need to align on what to share versus what to leave local.

Jeanette Clement

Tells how BT/EE defines service patterns as repeated steps across journeys and uses them to cut duplication across teams. Useful when a large org is designing similar things in parallel and you want to reuse blocks instead of rebuilding.

Scott D. Clary

Reviews satisfaction metrics like NPS, CES, and CSI, then describes assigning ownership and clear targets so feedback turns into change. Useful when satisfaction data is being collected but no one is acting on it consistently.

Casey Gollan

Casey Gollan (IBM) argues research platforms lock data in instead of integrating insights into product planning, and shares a discovery-backlog ritual. Useful when research insights aren't reaching PMs in time to shape decisions.

Travis Gohr

Travis Gohr shares Chorus.ai's secret recipe for designer/PM happiness: design owns the open-ended solution process, both roles validate early and often. Useful when design and product friction is hurting the team's pace.

Tim Chan

Tim Chan walks through how to design and roll out a new team process: build credibility, expose pain, find early adopters, and get buy-in from above and below. Useful when leaders want to introduce a new ritual but worry it'll get ignored.

Ivano Aquilano

Ivano Aquilano introduces UX Chunking, breaking the design process into digestible chunks built on progressive disclosure. Useful when complex projects overwhelm teammates and stakeholders.

John Drilling, MBA

Design Digest lays out a 6-step framework for running customer journey mapping workshops, from setting objectives to turning the map into action. Useful when facilitators need a repeatable structure for journey-mapping sessions.

Jenny Chang

Jenny Chang sets a success metric for each design at Amplitude, so the team celebrates hitting the metric, not shipping. Useful when design teams want a habit that ties every project to a measurable success bar.

Rose Curtis

Rose Curtis explains how to use a feedback loop with the top users to refine a dashboard until it actually meets needs, then keep iterating as needs shift. Useful when dashboards launch but go unused because no one closed the loop with users.

Rich Holmes

Compares UX debt to tech debt and gives PMs practical steps for tracking, finding, and prioritizing it. Useful when a PM needs an iterative mindset and concrete tools to manage UX debt across the team.

Karine Sabatier

Argues UX debt comes from the gap between design and code and lays out six strategies to keep it low. Useful when a design system or component library is drifting and shipping speed is creating new debt every sprint.

Christopher Wong

Shows how to use user story mapping so the whole team can see and discuss backlog items together. Useful when your sprint backlog feels disconnected from real user needs and the team isn't aligned.

Christopher Wong

Explains the difference between user stories and requirements and why UX should help write them in agile backlogs. Useful when product owners use the words interchangeably and the team keeps shipping requirement-driven specs.

Andreas Johansson

Walks through how to set up a UX backlog in JIRA, Trello, or even a spreadsheet, with the fields each item needs. Useful when a team has scattered design work and wants one shared list of tasks, owners, and priorities.

Alice H.

Frames UX debt like a bank loan: skip it now and you pay compounding interest later. Useful when teams need a clear analogy to explain why ignored UX issues should be tracked alongside other product priorities.