Feature requests aren't demand
In any product role, deciding what to build, what to prioritize, and what to avoid can be stomach-turning work. The closer we get to identifying demand (what people want from our product), the better we feel. The trap is that in many cases, when we think we’ve identified demand, what we have really identified is just supply-side thinking (features to be built). In this episode you’ll learn how misinterpreting an idea as demand can lead to building an expensive feature that nobody wants. Ryan and Chris also give a preview of what's to come on the series.