Episode 1: Feature requests aren't demand

[@mdswanson]

Really great stuff -- it's awesome to find something at the intersection of actually building SAAS products and concepts like JTBD and customer interviews.

[@imrafaelfrota]

That was one of the best content I've seen in the past few months. It's that kind of content that you finally feel is evolving, seeing other points of view and becoming a better professional. Thank you so much for that, looking forward to more!

[@MsDVoiz]

This is really good stuff guys. Any and every product manager faces this and it heartening to see someone put it out there. Over the years, I've so often come across stakeholders who dont appreciate questioning to figure out the underlying need. Good job :)

[@erichayes5000]

So excited about this series. Instantly subscribed.

[@DeepanManoharan01]

That was so insightful and explained excellently with a nice example. Thank you Ryan and Chris!

[@ChadWittman]

Well done guys, excited to follow along!

[@davidmkrell9806]

Very interesting, thank you both. I'm looking forward to exploring the Wild West!

[@PhilFreo]

Great stuff! I'd love to get episodes via Apple Podcasts in the future if possible!

[@rrawat02]

I feel lucky to live in a world where I (or anyone) can collaborate with the most interesting people around.

[@anirudhbbalotiaa]

Interesting...never thought in terms of "when" in the user journey. Subscribing.

[@sebastianvisual33]

This is GREAT!!!! please make more video :)

[@JordanCrawfordSF]

SIX YEARS AGO?!!

[@maxgeorgopoulos3516]

Is this another way of saying form and context?

[@LindsayTLadyEngineer]

Yay! This is definitely a User Centered Design concept that's been around for a while. I wrote about it in this article (originally posted in 2009): medium.com/@LindsayT/last-week-i-posted-my-tips-for-being-an-effective-designer-in-a-lean-environment-1baf29ebd3c The user is always right but they never know what they need. Furthermore, they'll tell you what they want but that's not what you should build. If they tell you want they want, ask them why? what problem are you trying to solve for yourself? what's your end goal?

[@DemandThinking]

Thanks Lindsay. Yes. What's different here vs. standard User-Centered Design is the emphasis on "when" over "why." Defining the chain of events gives us a test case that we can use to evaluate the fitness of different design options. - Ryan

[@LindsayTLadyEngineer]

Are you talking about taking a goal down to needs down to the specific tasks (i.e. chain of events) that the user may go through (IRL or with your product) to succeed in their goal?

[@DemandThinking]

We're framing it differently. We're differentiating between the chain of events on the demand side (what happened to the person that led them to look for a different solution) versus the series of tasks we could design for them to go through on the supply side.

[@LindsayTLadyEngineer]

Got it. Right. You have to understand what's happening before your customer comes to you so you know how to greet them, onboard them, treat them and solve their problems. I would challenge you to look more into qualitative research practices and the field of human computer interaction pre-Web 2.0. I don't believe "Demand Thinking" is a new concept. Maybe new-to-your-audience and with a new-name, but it's certainly not a new concept in software development. Good luck!

[@sandymakesplans]

can y'all use text in the future or like ... someone with legible handwriting in the future?

[@eightrice]

such an ample nose