Thinking in Systems
I vividly remember an interview where I was asked about my design process. My response felt very textbook. I said something about how my process varies depending on the problem’s context and how we want to approach it, I understand the situation, find multiple solutions, and test them out.
It sounded alright, but it didn’t capture the details of my approach — How do I understand the problem and find solutions?
I do this by thinking about design as a system and everything else as an output of changing the system as required.
Behind every design is a system that has smaller, interconnected parts. Think of it as the multiple parts of a vehicle that allow it to function so smoothly. Either I identify these parts in an existing system or put together parts to create a new system, based on the requirement.
Understanding the System
The first step in my process is breaking down a system into its basic elements. Whether it’s a website, an app, or a physical product, I look at the “atoms” that make up the “molecules” of the system. This includes UI elements like buttons and navigation bars, or more abstract elements like user flows and content structures.
By identifying these elements, I understand their functional role and the kind of reaction they are meant to evoke in users. For example, a bright button might draw attention and encourage action, while a clean layout aims to create a sense of ease and clarity. Understanding these reactions helps me evaluate whether each component fulfills its intended purpose. I do not fail to map these “conclusions” or “realizations” I have about the system.
Introducing intended change in the System
Once I’ve identified/put together these parts, I start tweaking them to see how the system responds. This is where I experiment with small changes to understand their impact on the design. For instance, moving a call-to-action button or changing a part of the navigational structure can alter user interactions and overall experience.
This helps me design at a detailed level, ensuring every small change supports the overall goal and every failure can be traced back to its related part.
So how do the Design Methods we’ve all heard of come into play?
Design methods like user journey mapping, wireframing, and prototyping are crucial throughout my process. They help me understand or build the system by exploring user needs and behaviors. As I tweak the system, tools like sketching and prototyping let me experiment with different ideas and see how they work. User testing and A/B testing then help refine these ideas based on real feedback.
This isn’t any different from popular processes like Double Diamond, but thinking of it as a system highlights how all parts are connected and how they can adapt, making the design more cohesive and flexible.
Addressing Challenges
Applying a system-based design approach isn’t without its challenges. One common difficulty is ensuring consistency across all parts of the system, especially in complex projects with multiple stakeholders. Balancing innovation with usability can also be tricky, as new ideas must still be intuitive for users.
Conclusion: Design as a Living System
In conclusion, my design process is about thinking in systems — understanding, tweaking, and optimizing each part to create a cohesive and functional whole. Whether I’m building something new or refining an existing design, this approach helps me make solutions that are adaptable and user-focused.
By looking at the fundamental parts of a system and how they interact, I can design more thoughtfully and anticipate future changes and challenges. This approach doesn’t just apply to digital interfaces. It’s a versatile method that can be used in any design context, from service design to physical product design. By understanding the system as a whole, I can create designs that are effective, durable, and ready for the future.
