Bringing Customers Into Every Stage From Problem Discovery to Release

How do you keep customers involved across a product's life, from first discovering a problem through developing and shipping the solution? Walk through what you do at each stage, using an example from your own work. ```hint Tie each touchpoint to a decision For every stage between the first signal of a problem and general availability, think about which customers you would bring in, through what channel, and which decision their input is meant to change. ``` ### Clarifying Questions - Do you want one worked example from my past work, my general operating model, or both? - Is this a business product where the engineers who use it every day are not the people who approve the purchase, so both groups need to be heard? - Does "development" run through beta and launch, or stop once the feature is built? - Can I assume direct access to customers through account and customer-success teams, or mainly indirect signals such as support tickets and usage data? ### What a Strong Answer Covers - A clear sequence of stages from discovery through post-launch, each with a named customer touchpoint and the decision it serves. - How customers are chosen at each stage (daily users versus buyers, large versus small accounts, current versus lost customers) and how the loudest account is kept from setting the roadmap. - How interview and beta feedback is combined with usage data and turned into decisions, including an instance where customer input changed or stopped the plan. - Coordination with sales, customer success, support, design and engineering, including engineers hearing customers directly and no roadmap promises made in passing. - A concrete example told in STAR order with a measurable result and how the loop was closed with the customers who contributed. ### Follow-up Questions - Your largest customer insists on a feature that interviews with smaller customers suggest few others need. What do you do? - How do you keep design partners engaged during a long build without committing to a ship date you might miss? - What evidence from a beta tells you a feature is ready for general availability?