by Mayokun Ogungbola
Complexity is an inevitable part of product design. It is easy to look at a set of requirements and assume it is a simple solution, like adding a button here or changing the layout. However, every project comes with its own set of requirements, user needs, business objectives, and technical constraints. If that complexity is not adequately understood, it leads to frustrated and confused users, which devalues the product.
A good example is research that indicates 88% of users will not return to a website after a negative experience, and a third of consumers will stop supporting a brand they love after just one negative interaction. As a designer, my goal is to make sure that doesn’t happen.
When working on projects with many moving parts, the first thing I do is seek clarity. I spend time understanding the problem thoroughly before considering solutions. This involves asking direct questions to unpack each requirement: What is the actual user problem behind this request? Why is it important now? Is it driven by user needs, business strategy, or technical limitations? Clarifying these questions often reveals assumptions that can be challenged or simplified. This initial “requirements engineering and UX design” phase typically accounts for around 10% of the total project cost, but investing here significantly reduces the risk of expensive rework later.
Once I have clarity, I visually map out the requirements and flows. This could be through user flow diagrams, journey maps, or simple sketches. Seeing the full picture helps identify overlapping features, unnecessary steps, and possible conflicts early in the process. Visual mapping turns abstract complexity into something tangible and manageable.
Next, I focus on prioritisation. I evaluate what is essential for users to achieve their goals effectively. This means identifying which features deliver core value immediately and which can be phased in later. Prioritising not only simplifies the product; it also ensures that design and development resources are used efficiently.
Throughout this process, I maintain a strong user perspective. It is easy to get caught up in business requirements and technical possibilities, but if a user cannot easily understand or use a product, it has failed. I keep asking myself: If I were a new user encountering this for the first time, would it make sense to me without explanation? Research indicates that approximately 94% of users judge a website based on its design, and if a website takes more than 3 seconds to load, over half of the visitors will leave. This underscores how quickly users form impressions and how critical an intuitive experience is.
Collaboration with developers is an integral part of the design process. Aligning with them early on makes sure that design solutions are technically feasible. They provide insights on the best ways to implement features and point out potential challenges that could affect user experience. This collaboration is invaluable because it saves time and prevents last-minute redesigns, making the team efficient and effective in our work.
Finally, no matter how great the design solution seems, testing and iteration should not be omitted. Real users will always reveal hidden friction points or confusion. Testing with them and refining the design ensures the final product feels natural and straightforward to use, regardless of its underlying complexity.
Another approach I’ve been using when testing and working closely with developers is running design experiments. We ship two different versions of a solution and collect data over a set period. This helps us better understand how well each design addresses the problem and provides a more objective perspective on what’s truly effective.
In my experience, simplifying complexities is a balance of understanding underlying needs. This understanding is the key to eliminating confusion and presenting solutions in a way that feels effortless to the user, even if the systems behind it are intricate.
At the end of the day, good design makes complexity invisible. This is what design strives to achieve. This isn’t just a personal goal but a collective one for everyone in the design field. This becomes possible when we approach every single feature and project with clarity, empathy and intentionality
