Skip to main content
Learning to see problems from above to create new approaches and solutions

Learning to see problems from above to create new approaches and solutions

uxdesign.ccuxdesign.cc3 weeks ago in#UX Love39

Adopting this mindset helps to acknowledge in a better way design problems.As an old and bad habit, one of the most common mistakes designers make is rushing to have a final solution as an immediate response to any request. Although this reaction may be good (questionable) because it allows us to visualize a final shape of an experience in a short time, the truth is we often miss a significant portion of information to understand the dimension of a problem and fully develop a functional product design.In my experience with this “approach,” I’ve learned that rushing to solutions too early may result in reprocesses, wasted time, and, most importantly, money loss. But, conversely, blocking solutions is not a good strategy either. So I asked myself this question; how to adequately cover all fronts when understanding a design challenge and still be agile?Let’s start from the basics. We know the stages of execution of product design (bottom to top); the frontstage design (UI), which focuses on interfaces, and interactions directly related to users, and then we have the backstage design (UX), which focuses on understanding and measuring user behavior, among other actions.We tend to think the design process starts from the UX stage, but it should start from a global view of planningBut there is, for me, an additional layer of creation in this structure; the strategic design whose mission is first to understand the business needs and then look down on the problems and get the actual dimension of the challenges to guide a team properly.The reverse funnel of design (top to bottom)In my opinion, how we understand layers of design is backward. Let me explain; Most of the time, we tackle problems and challenges from a general perspective, understanding the possible impacts, actions, and extensions (top of the structure). In this part, we first can construct initial concepts or judgments of how to proceed, prioritize steps, and project it into a timeline. We are looking from a top perspective at the problem before proceeding (this is also how humans learn). After that, we dive into specific things solving one part at a time (bottom).The most significant part should be acknowledging the problem first, then diving into small actions later (UX — UI stages)A quick example of this idea; Once you have decided to organize your room, you first analyze the magnitude of the challenge: how big is the room? Do I need extra help? Do I have time to accomplish the task or the necessary equipment? Then, after all that mental process, you decide where to start by taking one step at a time.The same happens with product design; the first action shouldn’t be the solution itself as the bad habit of some designers. That can be a mistake. Instead, we need to start looking down on challenges (strategic design) to understand how big it is, estimate the resources, determine the actual dimension and consequences of things, and prioritize efforts to move forward.But what happens when the business requires to rush into solutions? How to move even knowing this isn’t the proper approach? In start-up companies, fast resolution thinking is vital, but I think it should be a balance of activities when facing these problems. Delivering as fast as we can is not a good long-term strategy,  » Read More

Like to keep reading?

This article first appeared on uxdesign.cc. If you'd like to continue this story, follow the white rabbit.

View Full Article
Laravel Vs Symfony: Answering All The Questions To Make a Better Choice

Laravel Vs Symfony: Answering All The Questions To Make a Better Choice

#Dev
How to Channel a Daily Vision into a 20-Year Photography Career

How to Channel a Daily Vision into a 20-Year Photography Career

#Silicon Valley
WordPress Punts Locally Hosted Fonts for Legacy Default Themes to 6.2 Release

WordPress Punts Locally Hosted Fonts for Legacy Default Themes to 6.2 Release

#Web Design
Fresh For Designers

Is the Dynamic Island plain stupid or the next revolutionary UX pattern?

#All

Let's talk about UX