3 Truths of Product Discovery & UX

3 Truths of Product Discovery & UX

Dear?Designer,

Last week, I introduced you to "product discovery," a term for your team's work to?build the right product.

It's an important term because too many teams are focused on delivering, a.k.a. building?the product right.

If you're a designer stuck in delivery, you won't get to explore problems...only solutions.

UX Research, UX Strategy, and pretty much anything with UX requires time for discovery. Give a UX Designer all delivery tasks, and you will severely limit the methods she can use.

It's like trying to design with one hand behind your back.

Discovery Methods vs. Delivery Methods shown on the product design process

(An incomplete map of design methods and where they might be commonly used in the product design process)

UX can't reach its full potential if it only lives in delivery. Tacking a usability test at the end of a project is like "putting lipstick on a pig."

You might uncover a few problems, but what's the point if you've already decided what to build?

If you want to do UX and Product Discovery right, you have to accept these three premises to be true.

If you can't imagine saying these sentences out loud, you might be in more of a UI role in product delivery (a crucial role but not today's topic).

1) "Your stakeholders and executives can't tell you what to design."

But boy, will they try!

It's not UX or product discovery if someone gives you detailed directions on exactly what to design and how.?

I've seen lots of startups do this with their first UX hire. The poor UXer will try to do research and connect with customers, but it's tough to make a case for research when your executive team is wireframing for you.

If people outside the product team tell you precisely what to build, it will always turn into product delivery, not discovery.

If you want to do product discovery, stakeholders and executives have to give you problems to solve, not solutions to build.

Discovery requires?team empowerment, meaning the responsibility and authority to make decisions.

Empowered teams give decision-making power to the people building the product, not executives. It's a dream for both UX and Product Discovery.

2) "Your users can't tell you what to design."

*All the Junior UX Designers just gasped.

It's true, though. Users don't have all the answers.

UX Researchers will know that not everything a user says is reliable, and?self-reported wants and needs are unreliable?(what users?do?should get more weight than what they?say).

When customers tell you what they want, they tell you what they?think?they want. Instead of figuring out what they want, try to figure out?why?they say and do these things.

In the end, customers don't have the solutions...they have the problems.

It would help if you were going to your customers to understand problems. The way that you will solve that problem is up to the team.

3) "You can't decide what to design by yourself."

Just because you talk to users doesn't mean you have all the answers. You need the whole product team to figure out what to design and build.

Product discovery is a collaborative practice. UX should also be highly collaborative, but product discovery can't be done alone.

You need the constraints of users, stakeholders, and execs, and you need the decisions of the?entire product trio: product manager, product designer, and even the engineers.

Roles of product discovery with the words, "Product teams should do product discovery"? and including product manager, product designer, ux researcher, and engineer

(How the roles of discovery might look on a typical product team)

Even if you're an expert researcher or a data scientist with access to all the world's data, you can't decide what to build with gathered data alone. Product ideas should be prototyped and tested before the delivery stage, which should be the product team's work.

UX shouldn't be one person's job, and product discovery?can't?be.

TL;DR: Product discovery and UX share?the collaborative challenge of deciding on the right thing to build?despite the constraints of the users, business, and technology.

It ain't easy doing discovery. But if you're a UXer, the process should be familiar to you.

What is the product discovery process?

The Product Discovery process is a bit different from a typical UX process. There's a lot of generating data, not just gathering it.

Rather than building that shiny thing your CEO just dreamed up, you can implement an actual discovery process and?get a say in what gets built...finally!

-Jeff Humble, Designer & Co-Founder of the Fountain Institute

Sofie Pompa

Enterprise Partnerships, Product, & Strategy

2 年

Spot on Jeff.

Anja Lena Sack-Hauchwitz

Freelance UX/UI Designer - Webdesigner - Service Designer - UX Manager *OPEN TO WORK*

2 年

Excellent newsletter! ??

Andres Campo

7+ years building startup communities in EU and LatAm.

2 年

The content from Beyond Aesthetics is the gift that keeps on giving, keep up the great quality.

Maximilian Schmidt

Crafting magical customer experiences from the core of a product.

2 年

Hard to digest at first. Visual Truth 2022: Infinity Loop beats Venn Diagram in a head-to-head race.

要查看或添加评论,请登录

Jeff Humble的更多文章

  • How to Shift from Reactive Design to Strategic Design

    How to Shift from Reactive Design to Strategic Design

    Some people spend their whole careers reacting to other people's moves. I remember being in this position as a design…

    1 条评论
  • Chasing Competitors Instead of User Needs

    Chasing Competitors Instead of User Needs

    Have you ever had a CEO overly obsessed with beating the competition? I know I have. Usually, this obsession comes at…

    2 条评论
  • Designing an AI-Powered Automation System with Activepieces & Discord

    Designing an AI-Powered Automation System with Activepieces & Discord

    If you’ve ever used Zapier, Slack, or an AI agent to manage work, this article is for you. I hacked this automation…

    4 条评论
  • 28 Testing Methods That Are Not A/B Testing

    28 Testing Methods That Are Not A/B Testing

    Dear Product Person, Today I'm thankful for all the ways you can test that are not A/B tests. Executives and product…

  • Spirit of Halloween Costume Meme Special ??

    Spirit of Halloween Costume Meme Special ??

    Dear Designer, This year, I went a little crazy with the Halloween memes. So today, it's all about ridiculous designer…

    18 条评论
  • The Secret Killer of Strategic Projects

    The Secret Killer of Strategic Projects

    Strategic projects can fall into a million difficulties, but one thing takes down more projects than any other, and the…

  • 5 Ways to Do Strategy Research

    5 Ways to Do Strategy Research

    You may have done some user research and thought, what does the next level of research project look like? Well…

  • The 4 Signs of a Good Strategy

    The 4 Signs of a Good Strategy

    I teach a strategy course for designers, and one of my jobs is giving feedback on strategies. And it is NOT easy.

  • The Big Lesson Behind Figma AI

    The Big Lesson Behind Figma AI

    Designers are on the frontlines of something every software worker will soon be going through. It’s a question you…

    7 条评论
  • Why Designers Should Align to the Business Strategy

    Why Designers Should Align to the Business Strategy

    by Jeff Humble Dear Designer, Lots of designers never "get" their company's business strategy. And to the executives…

    2 条评论

社区洞察

其他会员也浏览了