Julie Zhuo on Twitter: "Everyone has an opinion on design" - Deepstash
Julie Zhuo on Twitter: "Everyone has an opinion on design"

Julie Zhuo on Twitter: "Everyone has an opinion on design"

Curated from: mobile.twitter.com

Ideas, facts & insights covering these topics:

8 ideas

Β·

17 reads

Explore the World's Best Ideas

Join today and uncover 100+ curated journeys from 50+ topics. Unlock access to our mobile app with extensive features.

<p>Everyone has an opinion on ...

Everyone has an opinion on design. There's always an immediate gut reaction: "Ooh, I love this!" or "Meh."Β 

But how do you go beyond that to honing your skills of giving helpful, actionable feedback?

Here are the 7 questions I run through when critiquing a product's design.

1

10 reads

1. What is the user journey to get here?

You can’t furnish a room if you don’t know how someone lives.Β 

So learn the context:

  • Who is the user?
  • When do they use this product?
  • Why?
  • How did they arrive here, and what's on their mind?Β 

Don't critique unless you know this.

1

1 read

2. What do we want users to feel and achieve here?

β€œIf you don’t know where you’re going, you’ll end up someplace else.”

Let’s understand what a successful outcome looks like before we start lobbing feedback about the design.

1

1 read

3. How important is this page/experience?

In a perfect world, we make everything perfect.Β 

In the real world, let's spend more collective energy on the stuff that really matters. More eyeballs? More high-stakes? = more thorough inspection of every detail.

1

1 read

4. What is our scope/timeline/team?

If speed is critical, let’s get the greatest bang for the least effort. If we have more time and people, then let's remove constraints (#7) and dream bigger. The "best" design differs according to the time/people/money you have.

1

1 read

5. Is the new design better?

For every proposed design change, am I confident it is better that what currently exists?

If no:

  1. Cut it
  2. Iterate on / improve the design
  3. Get more user feedback
  4. A/B test it

Which to pick depends on the answer to #4

1

1 read

6. What can we remove?

What can we remove from this experience and have it work just as well?

When faced with a problem, we bias toward adding stuff to solve it rather than removing. So gut check if it's necessary.

https://www.scientificamerican.com/article/our-brain-typically-overlooks-this-brilliant-problem-solving-strategy/

1

1 read

7. What if there are no constraints?

If we could throw all our constraints away, would we still design it like this?

While we can't typically throw all constraints away (see #4), it's still worthwhile to ask because we accept some things as constraints (due to legacy, etc) when they really aren't.

1

1 read

IDEAS CURATED BY

thinkpad

Intersted in tech and startups

Tom Parker's ideas are part of this journey:

Machine Learning With Google

Learn more about cybersecurity with this collection

Understanding machine learning models

Improving data analysis and decision-making

How Google uses logic in machine learning

Related collections

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Personalized microlearning

β€”

100+ Learning Journeys

β€”

Access to 200,000+ ideas

β€”

Access to the mobile app

β€”

Unlimited idea saving

β€”

β€”

Unlimited history

β€”

β€”

Unlimited listening to ideas

β€”

β€”

Downloading & offline access

β€”

β€”

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates