☞ Week 49 ☜
How to Identify the Best Design Problems
One of the core principles of UX is to solve existing problems, or problems that people are already struggling with. While this might not be as glamorous as inventing a brand new thing it is more practical: it makes identifying problems easier and people are much more receptive to your design. If you’re solving a known problem you don’t have to convince anybody that your design is valuable…they already know exactly why they want to use it.
Unfortunately, there are far more problems than there are designers to solve them. So how do you know you’re solving a problem that’s worth solving? How do you know that the problem you’re trying to solve is a real pain point that people will pay money for? How can you be sure that you’re prioritizing problems such that the one you’re focused on is the most important one?
Here is a simple framework that does just that:
1. Are People Frustrated?
If you ask people what their problems are, you’re likely to get a laundry list of issues as an answer. Saying we have a problem is easy, but the real problems are the ones we get emotional about. Frustration is the first clue that people have a real problem on their hands. They might not know how to articulate the problem they have but if they are frustrated then a problem exists somewhere. Frustration comes in several forms:
- They complain about it. (our favorite way to express frustration)
- They reluctantly accept something as “the way it is”
- It’s on a list of things to do
- They’re asking others for opinions & recommendations
If people aren’t frustrated, it means the issue at hand is not a real problem yet or they don’t recognize it’s a problem. Don’t try to convince people they have a problem…look for existing frustration instead of creating it anew.
Sometimes people are frustrated and don’t know exactly why. If people could articulate the root problem they might have solved it by now. So do user research by interviewing them, employing the Five W’s technique, or otherwise finding out what the real problem is. Once you know the real problem, often the solution presents itself.
2. Are People Actively Trying to Solve It?
Frustration is a major clue that a problem is important, but people get frustrated by a lot of things, some of which they’ll never do anything about. And, amazingly, some things stay problems forever! So try to wait until people take action against their problem in some way. This means they’ve prioritized the problem to one they really care about and are ready to take on.
Look for behavior that shows people are taking action. Are they cobbling together a solution from existing parts? Have they started a project with the express intent of taking on this problem? Are they amassing a library of information about this problem? Are they trialing software that is focused on this problem area?
People pay lots of lip service to problems they’re having but we have many more problems than time to solve them. So look for action, however small, to guide your design efforts.
3. Are People Already Spending Money?
Taking action is a necessary step, but it isn’t the best signal that we’re onto a great problem. People spending money is the strongest signal we have that they value the problem and would value a design that solved it for them.
Here are some ways that people might spend money:
- Purchased software - If they have purchased existing software then it’s a good sign this is a real problem to them. Note that this doesn’t mean they are happy…if they’re frustrated with existing software that they paid for then you can be further sure it’s a core problem.
- Hired consultants - they don’t know how to solve the problem…they want to get another brain on the job. When I was consulting this was key…many people were trying to solve a problem for so long that they couldn’t think objectively about it. What they needed was someone familiar with the problem space who didn’t have their head in the weeds. Being close to a problem for too long can actually make it much harder to solve!
- Building it themselves - this means that existing tools are yet good enough to solve the problem yet its worth the investment to get it solved. Building yourself is a crucial indicator that you’ve prioritized this problem to the top of your list.
Prioritizing the Most Important Problems
Prioritization is a core competency of UX designers. We have to prioritize the people we design for, the features we choose to build, the elements on a page, as well as the overall problems we choose to solve. But choosing problems isn’t always easy…people have no end to the improvements they want made in their lives. This simple framework helps you prioritize problems based on people’s actual behavior, not just what they say or think. By focusing on whether people are frustrated, already taking action, or most importantly already spending money, UX designers can be sure they’re tackling the most important problems for their clients and customers.December 8, 2010 by bokardo
- week 49
☞ Week 48 ☜
Why “Clean” Isn’t Such a Dirty Word For Designers
You have probably heard someone say, “That design is so clean!”
Or perhaps you’ve scanned your RSS feed and seen titles like “1000 Clean and Minimalist Designs”, “Super-clean, Simple, Minimal Website Designs”, or “How to Design Clean, Typographic, Minimalist Sites.”
I normally throw up in my mouth a little when I encounter such phrases. But I have to admit that I catch myself using these words unintentionally (on rare occasion, of course) when I am struck by a design that doesn’t rely heavily on design trends of the moment, but rather takes an approach that puts the content first, without much ornamentation.
It’s strange that so many people default to the term “clean”. A friend and co-worker wrote about this recently saying that using the term “clean” is “quite possibly the worst feedback anyone can ever give… It’s piss poor feedback.” While I agree with the larger point in principle, it got me thinking about the unspoken volumes of communication provided to us when someone uses a word such as “clean” to describe design.
The sum of our lives is sometimes conveyed as much in what we don’t say as what we do say. How we were raised, the things we were exposed to—the type of home we lived in, the style of clothing we wore, the company we kept—all left indelible marks on us as a person.
So I spent some time thinking about what “clean” means to me. My first thought was of my childhood home and chores. My mother taught us all how to help keep our home “clean.” Neat. Orderly. Not dirty, grungy or disregarded. And then I thought of my beautiful wife, whose ability to create the right atmosphere in any space comes from her desire to make any room into a clean, inviting, uncluttered space that draws you in and makes a place for you. Balanced. Harmonious. Peaceful and inspiring.
Suddenly, using the term “clean” to describe a design no longer made me want to retch. In fact, this word actually carries with it part of my formative years, things that shaped and informed my own personal aesthetic. Through this little exercise I realized that when people are describing a design, the words they use may actually be freighted with much more meaning and experience than we perceive.
That said, I do not support the egregious overuse of simple terms to categorize a style of design that can be subtle and varied. But the next time someone uses a word you consider generic or uninformed, take a moment to think about all the different things that one word could actually be communicating.
And then ask them to tell you more. Start a conversation around the design and give them other opportunities and other ways to describe the experience of seeing and interacting with your design.
In the end, we are all human and our experiences shape the way we communicate. Don’t be too quick to dismiss someone’s feedback just because of the language they use. Odds are, there just might be more to it than you realize.
P.S. If you are a designer working with other designers, you are responsible to expand your vocabulary and offer critical feedback that is concise and actionable. Do your homework and be honest. And don’t point to this article to try get you off the hook.November 30, 2010 by jbrewer
- week 48