You’re stuck with a design problem. How can you identify the root cause?

1 Define the problem

The first step is to clearly define the problem you are trying to solve. What is the goal of your design? Who are the users or stakeholders? What are their needs and expectations? What are the constraints and requirements? Write down the problem statement in a concise and specific way, and avoid vague or ambiguous terms. A good problem statement should describe the current situation, the desired outcome, and the gap between them.

2 Analyze the problem

The next step is to analyze the problem and identify its root cause. A root cause is the underlying factor or condition that leads to the problem. Finding the root cause can help you understand why the problem exists, how it affects your design, and what actions you can take to prevent or solve it. There are many tools and techniques you can use to analyze the problem, such as the 5 Whys, the Fishbone Diagram, or the Pareto Chart. Choose the one that suits your context and data, and apply it systematically and objectively.

3 Generate ideas

Once you have identified the root cause of the problem, you can start generating ideas for possible solutions. This is the creative phase of the problem-solving process, where you can brainstorm, sketch, prototype, or test different options. The key is to generate as many ideas as possible, without judging or filtering them at this stage. You can use various methods to stimulate your creativity, such as SCAMPER, Mind Mapping, or Morphological Analysis. You can also involve other people, such as your colleagues, clients, or users, to get different perspectives and feedback.

4 Evaluate ideas

After you have generated a large number of ideas, you need to evaluate them and select the best ones for further development. This is the critical phase of the problem-solving process, where you can compare, rank, or score the ideas based on their feasibility, desirability, and viability. You can use various criteria to evaluate the ideas, such as their alignment with the problem statement, their impact on the users or stakeholders, their cost and time implications, or their sustainability and scalability. You can also use tools such as SWOT Analysis, Decision Matrix, or Cost-Benefit Analysis to help you make informed decisions.

5 Implement ideas

The final step is to implement the ideas that you have selected as the most promising solutions. This is the action phase of the problem-solving process, where you can plan, execute, and monitor the implementation of your design. You can use various tools to help you manage the implementation, such as Gantt Charts, Action Plans, or Checklists. You should also communicate your design clearly and effectively to your users or stakeholders, and collect feedback and data to measure its performance and outcomes.

6 Learn from the process

The problem-solving process is not a linear or static one, but a cyclical and dynamic one. You should always be ready to learn from the process, and to adapt and improve your design based on new information, feedback, or changes. You should also reflect on your own strengths and weaknesses as a problem solver, and identify areas for improvement or development. Learning from the process can help you enhance your problem-solving skills, and prepare you for future design challenges.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?