Ask Better Questions, Design Better Solutions — Transcript
Full transcript
- 0:00trying to solve the right problem sounds
- 0:02like asking a lot of questions and
- 0:05figuring out which question to ask. Do
- 0:08you have like a mental model or to kind
- 0:10of approach this? Absolutely. Yeah.
- 0:13There's one things really separates
- 0:15amazing designers from good designers
- 0:17and I think that's being curious. I
- 0:20think you find that the best people at
- 0:22like solving problems or understanding
- 0:25problems are the people are like
- 0:26constantly questioning and constantly
- 0:28being curious about things. So if I go
- 0:30back and thinking of myself when working
- 0:32like as a founding designer with
- 0:34startups, I've always been curious about
- 0:36everything and I see something in
- 0:38designers and it really makes a
- 0:39difference. So stakeholder says
- 0:40something a commercial person or a
- 0:42marketing person you're asking oh why
- 0:43tell me more about this like let me
- 0:45understand this. What have we done in
- 0:46the past around this? What problems are
- 0:48you facing in your area? Maybe a
- 0:50researcher mentioned something. It all
- 0:52starts from being really curious about
- 0:54everything you're hearing and not just
- 0:56taking it at face value. I think that is
- 0:58number one before we mention any kind of
- 1:01framework or mental model. I always go
- 1:04very simple. I always try and ask a
- 1:06number of questions. What do you think
- 1:07is the problem? Let's start with that.
- 1:08Cuz often it's like, oh, we need to do a
- 1:10redesign of this feature. And you're
- 1:12like, what is the problem? Right? So, we
- 1:14start really basic. What do you think
- 1:16are we solving here? Then what is the
- 1:17user that is being affected by this and
- 1:20what are other stakeholders around this?
- 1:21What data do we have about this problem?
- 1:23Is this just your assumption or is this
- 1:26based on something? And by the way, I'm
- 1:28happy with problems that come from
- 1:30hunches and assumptions like it is part
- 1:32of the work that we do and sometimes
- 1:34understanding how much data you have on
- 1:36a problem and that data can be quant or
- 1:38quad data. So have you done any research
- 1:40on this? Gathering all the data that you
- 1:43have around a problem is probably one of
- 1:45the most impactful and essential things
- 1:47to do and yet it's almost never done
- 1:49right because we always say we need to
- 1:51move quickly so let's quickly design a
- 1:52solution and then there's so much data
- 1:54that we're leaving behind. There's other
- 1:56teams in our business that have done
- 1:58like reports and research and gathered
- 2:00evidence on this but we're not using it.
- 2:01So what data do we have? And then if we
- 2:04go towards kind of like the solution
- 2:05side of the problem, have we tried
- 2:07anything in the past to solve this? Have
- 2:09other businesses tried things? How are
- 2:11they solving it? Do we have any
- 2:12suggested solutions? And then extremely
- 2:15important, what are we hoping to do if
- 2:17we solve it? So let's say everything
- 2:18goes right. How do we know if we're
- 2:20successful? Because obviously you can't
- 2:22judge something like the success of an
- 2:24initiative by completed this or we did
- 2:27some interviews. The success of an
- 2:29initiative is did it move the business
- 2:31metric? Did it make us learn something?
- 2:33And I'll actually stick to the last one
- 2:35because obviously there's a lot of talk
- 2:37around measuring impact and making sure
- 2:40that everything has like a sizable
- 2:41impact. It's not always about the impact
- 2:44because not everything you do is
- 2:45successful, but it's also about the
- 2:47learning. So sometimes it's also
- 2:49important to say, well, you know what,
- 2:51this problem is defined by answering
- 2:53these questions. Well, one of these
- 2:54things is what are we going to learn if
- 2:56we do this? And maybe that is how we're
- 2:58successful. Maybe we didn't move the
- 3:00business metric but we're actually very
- 3:02successful because we actually learned
- 3:03one two three things that will make our
- 3:05next initiative um very impactful. So
- 3:07yeah, that's where I would start like
- 3:08what is the problem? What is the
- 3:10evidence that we have? What kind of data
- 3:11do we have call or quant? What is the
- 3:13audience that is being affected by this
- 3:15either directly or indirectly? What are
- 3:16other companies doing around this or
- 3:18what have we done in the past? What are
- 3:20the suggested solutions? How do we
- 3:21measure success if all goes well? That
- 3:23was so good. Oh god, it reminds me of
- 3:26the experience canvas from Alassian
- 3:29where it's like this real simple one
- 3:31pager where you basically divide it into
- 3:33quadrants and problem ideas, value,
- 3:35stakeholders, team, personas, and test
- 3:37ideas or data to back it. And that's a
- 3:40really healthy way to just like can you
- 3:42brain dump on like a one pager that's
- 3:44like really easy and quick to share. But
- 3:47it also sounds like there's so much up
- 3:50work even deciding and you mentioned
- 3:52that most of the times we're expected to
- 3:55run fast. How does this play out in
- 3:58day-to-day life at work where it's like
- 4:00there's so much to consider but then at
- 4:03one point sometimes there could be some
- 4:04analysis paralysis. How do you kind of
- 4:06solve for that? I think that's such a
- 4:08great question. This has been tormenting
- 4:10me my whole career. I think there's a
- 4:12couple of things here. The first and
- 4:14most important thing, especially for
- 4:15junior or mid-level people that are
- 4:17listening to this, it's like there's no
- 4:19perfect process around this. And there's
- 4:21no perfect expectation of what you need
- 4:24to get at each step of the process. And
- 4:26that doesn't just apply with like
- 4:27defining problems. It applies to every
- 4:29single thing that you're doing in
- 4:30design, right? With discovery, with
- 4:32defining, with ideulating, with design.
- 4:33So, for starters, you don't need to get
- 4:35everything right. You just need to make
- 4:37sure that you're covering some of the
- 4:38essentials. The second thing that I
- 4:40would say is it sounds overwhelming at
- 4:42first, but if you build that curiosity,
- 4:45this becomes a conversation that you can
- 4:47have with someone in like 5 to 10
- 4:49minutes. That's why I stress so much
- 4:50that you don't have to do this in a
- 4:52whiteboard. If you make a habit of
- 4:54asking a PM, a stakeholder, your team of
- 4:57like the best people that are going to
- 4:58work on this problem, like those seven
- 5:00things before you start working on
- 5:01anything, this becomes second language.
- 5:03And you build the second language over
- 5:05years and years and years of trying to
- 5:07do this again. And the first time you do
- 5:08it, it feels awkward and it feels
- 5:10uncomfortable and it might even feel a
- 5:12bit mechanical. But then the second and
- 5:13the third and the 10th time you're doing
- 5:15this, it almost becomes a let me just
- 5:17take 10 minutes to make sure we'll align
- 5:19on these things. Now to cover the most
- 5:21challenging bits, sometimes you don't
- 5:23have answers to all of these questions.
- 5:25And that's completely fine. Maybe you
- 5:26haven't done research on something. It's
- 5:28okay to say, you know what, I'm getting
- 5:30answers to three of these seven
- 5:31questions. And that's better than
- 5:33getting answers to none of these
- 5:34questions. So being okay with that
- 5:36imperfection so that you're able to move
- 5:38fast is I think something that is really
- 5:41important for every designer. I think
- 5:42most designers that I see struggle a lot
- 5:45with imperfection in the process and
- 5:47they say oh we haven't answered all of
- 5:49these things. The truth is there's never
- 5:52a perfect process and being able to have
- 5:54that sense of what is really important
- 5:56for you and for the business and then
- 5:58moving on and saying that's good enough.
- 6:00Let's figure out the next thing. I think
- 6:01this is what's really important. I think
- 6:03the last thing that I'm going to mention
- 6:04because obviously you mentioned things
- 6:06like speed. Who doesn't like speed,
- 6:08right? And so imagine if you're a
- 6:10business stakeholder and they're like,
- 6:12"Hey, we need to really move fast and
- 6:14build something that works." And the
- 6:15designer goes like, "Oh, no, no, no.
- 6:16Hold up. We have a process to follow
- 6:18here. I need 3 weeks of doing discovery.
- 6:21We're going to come up with some ideas.
- 6:22In a month or two months from now, we're
- 6:24going to have something that's a no-go,
- 6:26right?" I think being able to say, you
- 6:28know what, from the 50 things that I've
- 6:30learned in this boot camp that I did,
- 6:32actually, there's five or six things
- 6:33that really make a difference, and those
- 6:35things are never the same. And so, I'm
- 6:37going to focus on these things when I'm
- 6:38pushed for speed. That's what's really
- 6:40important. And then there's other times
- 6:42where people might push for speed. And
- 6:43you might be able to say, hey, if we do
- 6:45this very, very fast, it's very unlikely
- 6:48we're going to succeed because it's not
- 6:49a problem we know enough about. We
- 6:51haven't done any research. It's a new
- 6:53problem that we can't really take
- 6:54inspiration from other businesses. So
- 6:56actually I think we should take more
- 6:57time. I think that balance of saying I
- 6:59need to do this at a very fast pace but
- 7:02I still have enough to do this so I'm
- 7:03okay with imperfection versus I don't
- 7:06have enough time to do this and I need
- 7:07to spend more time on it because I don't
- 7:09understand this problem enough that's
- 7:10really difficult to build. But I would
- 7:12always say you are the person that
- 7:14always knows what's important based on
- 7:16what are the areas you have the most
- 7:17confidence in. If you're very confident
- 7:19that this is the right problem, then
- 7:20yeah, maybe you don't need to redo
- 7:22interviews or redo surveys, like go
- 7:24straight into solutionizing. If you
- 7:26don't, then yeah, take more time to do
- 7:27this piece of work because otherwise
- 7:28it's very unlikely you're going to be
- 7:30successful. When you coach your team and
- 7:33designers out there, how do you think
- 7:34about adaptability and how do you
- 7:36suggest designers on this call kind of
- 7:38work on? This is a topic I'm very
- 7:40passionate about. There's a couple of
- 7:41things to being adaptable. I think
- 7:43firstly, want to listen to the full
- 7:45conversation? Click the video on screen
- 7:47now. Subscribe to the channel if you
- 7:49want to join us live. Oh,
- 7:55wait. Okay, fine. You don't have to join
- 7:58us for the live stream, but if you like
- 8:00stuff like this, then click that
- 8:01subscribe button. I'll see you on the
- 8:03inside. Bye.
About this transcript
This page contains the full transcript of Ask Better Questions, Design Better Solutions by Chris from UX Playbook, generated from the public captions YouTube serves with the video. The transcript has 1,755 words across 252 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.