Feb 07, 2020

3 questions designers should be asking

Why, How might we, and...

Since our work as a designer is very much in a very abstract phase. We can’t just make a conclusion too soon, because when you do so, your work will be converged too quickly and have a few shortcomings in it. Instead of relying upon conclusion or solution, I usually rely more on the questions because it allows me to constantly reframe my perspective. Here are a couple of questions that I often use.

Why and Who

A fundamental question that everyone needs to ask. When things still very abstract in the beginning phase, you can rely on the Why and Who. That must be the center of your focus to help yourself and your team navigates in the abstractness.

Example of questions:

  • Why are we even doing this?
  • Why are we building this?
  • Who will consume this product / experience?
  • Who are our competitors?

A result of this first layer of question is often portrays the high-level objective, strategy, and rationale. It’s a foundation of what you will be working on.

How might we…

Once the why and the who get less blurry in the picture of what you do. The how is often time comes up to my mind as a complementary. This question is trying to frame a specific objective that you have in the “why”, but better articulated.

Example of questions:

  • How might we reduce the food waste in the hotel buffet?
  • How might we help an amateur chef to train?

These questions will frame a problem to a specific point of view based on insights that will prepare your team to start thinking about the “what”

What if…

Presumably, you get a clearer understanding of the why, the who, and the how. At this point, you want to answer those how might we questions and make something a bit more concrete. It’s time to wonder and think as high as a blue sky with “What if…”

  • What if we ask the hotel guest to order the food from the buffet list the night before?
  • What would happen if we make the digital preparation table for the chef?

You see, we answer the “how” with another set of questions and this is great because we still don’t know what the best solution is. In a question format, nothing set in stone and everything is still can be challenged. Also, allow you and your team to keep wondering.


Don’t take this as a linear way of thinking. Sure, Why and Who often come first in mind. But, you must be able to juggle around the layers throughout the progress you make. Gather information as you go and reframe your perspective if needed.

So, what question do you want to ask next?

I’m happy to have a conversation! Hit me on Twitter





Nov 24

About self-doubt

Nov 11

Don't confuse design with artifacts

Nov 06

What if you need to find another job tomorrow?

Oct 26

Making sense of your design project by writing

Sep 30

When was the last time you reflect?

Sep 29

Methods are tools

Sep 24

How can I get a bigger project?

Sep 23

Entering product design – Chapter 7: Craft and analysis

Sep 22

Entering product design – Chapter 6: Narrow collaborator

Sep 21

Entering product design – Chapter 5: Soloist product designers

Sep 17

Entering product design – Chapter 4: Product designer key skill areas

Sep 14

Entering product design – Chapter 3: Misunderstanding of business

Sep 11

Entering product design – Chapter 2: Principles over steps

Sep 10

Entering product design – Chapter 1: Silver bullet

Sep 10

Entering product design – Overview

Sep 04

SAR: A framework for concise storytelling

Aug 27

Start your design with outcome

Aug 24

New medium post: Collaboration ground for design systems

Aug 17

Action points

Aug 13

Pulse check: Listen to your team

Aug 11

You should actively apply for a new job

Aug 10

Design systems' area of influence: Service (3/3)

Aug 04

Design systems' area of influence: Offering (2/3)

Aug 03

Design systems' area of influence: Identity (1/3)

Aug 01

My mom ran me to the hospital

Jul 29

Reader question: Do we need to build MVP for every product?

Jul 27

Reader question: Do I need formal design education?

Jul 24

Recognize assumptions

Jul 21

Sandbox for your personal growth

Jul 20

Start your week with questions

Jul 17

Specificity in feedback

Jul 15

Don't sell the design. Sell the business impact

Jul 14

Overwhelming inspiration

Jul 13

The framing trap

Jul 10

Everyone vs. Specific

Jul 09

The blind horse designer

Jul 08

Set the context in your meeting

Jul 07

Let's just try and see what happens

Jul 06

Managing expectation

Jul 05

Low UX maturity company

Jun 17

A simple exercise for career reflection

May 31

The “Coach sheet” – A paper-based system for people management

May 26

Bring calm to your remote team

Feb 13

Workshops can be more efficient than meetings

Feb 07

3 questions designers should be asking

Feb 06

Walking 1on1: A refreshing way to connect


Nov 21

My hope for stubborn 'Innovators'

Jul 18

Five simple actions to help you gain more time

Apr 23

Evolving Product Experience Principles at Bukalapak

Mar 09

A framework to give better design feedback: Analyze, Discuss, Suggest

Jan 28

Making a decision is hard, here's my rule of thumb


Dec 04

Essential skills for Product Designers

Nov 16

Quick life update

Nov 06

Things I learned from working at Shopify

Oct 15

About design critique

Sep 17

Common icon design problems you should avoid

Sep 06

Preface: Welcome to yellowstroke.com