A solution-based angle of problem-solving in design
Design thinking is no longer just a buzzword used to explain the process behind problem-solving in design. It’s a term that fully combines a way of thinking that includes creativity, analytics, and collaboration to resolve problems that may exist. Using a design thinking process, we can solve more complicated problems that require a bit more depth of knowledge and data. Some issues need a more ‘out of the box’ approach to the thought necessary to solve them. Let’s take a look at the steps involved in design thinking.
Empathise
Having a fair amount of empathy for the problem and its impact on our users is a cornerstone in the design thinking process. This involves research into the potential users, what the experience and concerns might be, and immersing yourself into the user’s mindset. This step is used to collect as much information as possible about the project, advocate for our users and provide a great user experience.
Define
The next step in the process is to harness the information we collected in the first step and explain the problems. To be as detailed as possible when making those definitions is an excellent way to ensure that the solution we come up with is solid. The definitions of the problems that we develop are going to help us formulate solutions using features, design patterns, or other elements.
Ideate
Once we’re aware of the exact definition of the problems that exist, we can start asking ourselves how to resolve them. We start brainstorming sessions to encourage the thinking component of the possible solutions and put pen to paper. We also design wireframes to help us better visualize the solution and implement it in a design. These wireframes could make their way into the next phase, so it’s essential to be as detailed as possible to avoid confusion in the future.
Prototype
Once the wireframes and solutions are positioned as best as possible, it’s time for the design team to put together some prototypes. These prototypes should be of simple quality to avoid any potential time issues. We will be using them for testing, but they do not require high fidelity or final designs. We’re working now at the experimental phase and will be subject to user testing soon. If our solution isn’t what we thought it would be, we don’t want to go too deep into the design. We’ll save that for later.
Test
This part of the process is where we get multiple users to test our solutions. This isn’t always the last stop on the train to a happy user because often we find ways to improve or simplify the solutions further. Sometimes we might get sent back a couple of steps to re-define the problem or new problems that arise during the testing phase. In the end, regardless of having to advocate for further issues, we end up with a deeper understanding of the product as a whole. When we understand product as best as possible, it helps us solve any future usability discrepancies.
It’s an iterative process
Testing is a wholly flexible process that’s intended for designers and product teams to use their minds separately and as a whole to solve problems. Problems are inevitable, but solutions are almost always possible, especially when working our them extensively to incorporate the steps (empathize, define, ideate, prototype, and test).
To recap a little bit on the steps of the process:
- Empathy: what are the users’ needs of the project
- Definition: collect deeper details of the problem and frame it
- Ideation: develop ideas of what could be a solution to the problem
- Prototype: put together a hands-on version of the solution
- Test: work through the solution and ensure that it meets all the needs
So as you can see, design thinking can help you incorporate more profound knowledge of the problems into a solution. Design thinking can also lead to an even more comprehensive understanding of the entire product.