Design Is More than Problem Solving

Design Is More than Problem Solving

"I'm a problem solver."

It's a common phrase on junior UX designer's Linkedin profiles. I get it. It's a catchy little phrase that shows hiring managers that you can do more than "make stuff pretty."

But designers are more than problem solvers.

UX designers have to be concerned with the problem, but in the early days of your career, your work might be more solution-focused. You might even find yourself with a UX title but doing the work of a UI designer. That's ok; Solving problems is the gateway drug to more advanced work. Problem-solving and solution-work is an easy place to start a design career.

However, solutions shouldn't be your main focus.

Understanding problems vs. solving problems
Meme by Jeff Humble

Understanding problems may not get as much airtime, but it's key to good solutions.

Too many solutions in this world aren't based on a real problem.

For example:

The Amazon Fire Phone's debut
Image by Ted S. Warren

Take the Amazon Fire Phone. You may have forgot Amazon that tried to design a phone once. It had its own app store and lots of fancy 3d-rendering technology. This was Jeff Bezos' pet project, and he was sure it would be a success...but it was a total failure. The phone was a great solution to a non-existent problem. The Fire Phone a total failure that cost Amazon $170,000,000.

As your career progresses and you tackle more complex problems, you will get the opportunity to work on problems, not just solutions. That's when you will become more than a problem solver.

It takes skill to solve problems, but it takes experience to find and frame problems. Problem-finding and problem-framing is a way to set yourself apart from the never-ending supply of design graduates ready to "solve problems" for anyone that will hire them.

Problem-focused skills are very strategic career skills for any ambitious designer. Here are some ways to use these skills at tech startups.

Finding Problems

Gather inputs for future design outputs.

Many companies naively think they can design great products through their own expertise. These companies might have great ideas, but they don't always check these ideas against the external.

A little bit of discovery can go a long way. It can save weeks of building the wrong thing.

No alt text provided for this image
Without Discovery or With Discovery by Jeff Humble

Finding the time and permission to talk to customers is really hard. What super-specific ways can you find problems when you're low on time?

Some specific ways to find problems:

  • Talk to customers.?Get a?Calendly?and send that link out!
  • Gather existing knowledge.?Desk research whenever you can.
  • Get access to user data.?Just ask your PM.
  • Observe the context.?The setting can provide clarity.
  • Scope research into projects.?(try this UX Research Canvas for planning)

Framing Problems

Form clear and conquerable problems from customer data.

The way that problems are formed and articulated is extremely important in UX design. There is a power to the way that we talk about the problem we're trying to solve.

The common misconception with research is that we can stop discovery when we hear the same problem from a few customers. There is an entire phase after the interviews that most UX designers skip.

This missing phase after gathering research is all about examining the data more closely. It allows us to break down what was said (analysis), and It allows us to connect with the bigger concepts and ideas (synthesis). This abstract mental phase is known as design synthesis.

No alt text provided for this image
Design Synthesis by Jeff Humble

This stage helps you to connect the research input (usually observed data on a customer) with the application of that research (often a visual such as a wireframe).

Some specific ways to frame problems:

  • Gather & edit insights.?Do this throughout any research project.
  • Analyze & synthesize research data.?Know the difference?and do both. Take the time to work with data, not just gather it.
  • Create concise problem statements.?Narrow down to the final problem through editing and collaboration (one of the most underrated skills in UX).

Check out these?10 specific methods?you can use to frame (and reframe) problems.


You can be more than a problem solver.

Solving problems can be the gateway to more advanced work.

If you're only a problem solver, and you want to be more, check out this?free course on UX research. It's a great way to get a start in problem-finding and framing.


Jeff Humble is a Co-Founder of the Fountain Institute and former Head of Design at CareerFoundry. He writes about design from a generalist perspective and loves talking about advanced UX, product strategy, and emerging trends.

This article was originally posted in Beyond Aesthetics. Get design resources and exclusive access to events by signing up for Jeff's free weekly newsletter:

Thanks for that! very helpful!

Jessica Webb

UX/UI Designer: identify problems, discover simple innovations, create intuitive solutions.

3 年

This is a fantastic article! Really though, puts “problem solving” into perspective. Discovering problems and being able to frame them to find solutions. That’s where it’s at. :)

Keith March Mistler

UX/UI Designer @Salesforce | Generative AI | Design Strategy

3 年

Great article! I love how you talk about the importance of finding problems rather than just solving them. It’s a great way to reframe our thinking when going into a project. Thanks for sharing.

Melody Jaros

UX Researcher | 10+ years of crafting stories and aha moments

3 年

Guilty as charged. I definitely wrote down "problem solver" in my about me section in the first version of my portfolio.

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

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…

    2 条评论
  • 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 条评论

社区洞察

其他会员也浏览了