I spent the last few years working on innovation focussed projects. I was always part of the team expected to generate ideas and develop solutions for major organizational problems. The stress of not disappointing stakeholders was real. But what I struggled with most was explaining a simple truth: ideas don’t just appear out of a magic bag. They need to be researched, thought about, and experimented on.
But here’s the thing, before we research, think, and experiment, we need to think about our approach to the process. This is where terms like “design thinking” and “systems thinking” come into play.
I’ll be honest. For all many years of coding and integrations, my understanding of these terms was superficial. I didn’t know when to use one versus the other, or how they might work together. So I went to design workshops, learned about design thinking at Stanford, read the book Design of Everyday things for months.
In this article, I’m doing what I should have done years ago. I’m taking the time to break down these two approaches well enough to differentiate between them. I want to figure out where I lie on the spectrum as a practitioner.
If you’ve worked in technology, innovation, or problem-solving, you’ve probably heard about Systems thinking and Design Thinking thrown around. But what do they actually mean, and when should you use each one?
What Are They?
Design Thinking is about solving problems by deeply understanding the people who experience them. It’s a creative, human-centered approach that moves through stages: empathizing with users, defining the problem, brainstorming ideas, building prototypes, and testing solutions. Think of it as zooming in on the user’s experience and iterating quickly to find what works.
Systems Thinking is about understanding the bigger picture. It’s a way of seeing how different parts of a system connect and influence each other over time. Instead of fixing isolated problems, you look at patterns, relationships, feedback loops, and unintended consequences. Think of it as zooming out to see the whole ecosystem.
Key Differences
The approaches differ in some fundamental ways.
Focus and scope: Design thinking focuses tightly on the end user and their immediate experience. You’re solving for specific pain points that real people face. Systems thinking takes a broader view, examining how multiple stakeholders, processes, and components interact across an entire system.
Timeline: Design thinking operates in sprints and iterations. You prototype fast, fail fast, and learn fast. Systems thinking considers longer time horizons, asking what happens downstream and how changes ripple through the system over months or years.
Starting point: Design thinking starts with empathy for the user. You observe, interview, and walk in their shoes. Systems thinking starts by mapping the landscape, identifying all the players, forces, and connections at work.
Problem definition: With design thinking, you reframe problems as opportunities centered on human needs. With systems thinking, you define problems as symptoms of deeper structural issues within a complex network.
Solutions: Design thinking produces tangible solutions you can touch and test- apps, services, products, experiences. Systems thinking often produces insights, leverage points, or strategic interventions that change how the system behaves.
Where They Overlap
Despite their differences, these approaches share important common ground.
Both reject simplistic, linear problem-solving. Neither assumes you can just apply a fix and move on. They both acknowledge that real-world problems are messy and interconnected.
Both require iteration and learning. Design thinking does this through rapid prototyping cycles. Systems thinking does it by testing assumptions about how the system works and adjusting your mental model.
Both value deep understanding before jumping to solutions. Design thinking demands empathy research. Systems thinking demands systems mapping. Neither tolerates shooting from the hip.
Both recognize that problems worth solving are complex. They’re not mechanical issues with obvious answers- they involve people, context, trade-offs, and uncertainty.
When to Use Them Together
The magic happens when you combine these approaches. Here’s when that makes sense.
When you’re tackling wicked problems: Issues like healthcare access, climate change, or organizational transformation are both human-centered and systemically complex. You need to understand both the lived experience of individuals and the structures that create those experiences. Design thinking without systems thinking might create a beautiful solution that breaks the larger system. Systems thinking without design thinking might propose a theoretically sound intervention that nobody actually wants to use.
When designing for scale: You might use design thinking to create a solution that works beautifully for 100 users. But before rolling it out to 100,000 users, you need systems thinking to understand how it will interact with existing infrastructure, incentives, and behaviors at scale.
When unintended consequences matter: Design thinking helps you test whether people like your solution. Systems thinking helps you anticipate whether it might create new problems elsewhere. For example, a rideshare app solves individual transportation needs brilliantly but can increase overall traffic congestion: a systems-level consequence.
When you need both innovation and sustainability: Use design thinking to generate novel solutions that people love. Use systems thinking to ensure those solutions are viable within the constraints and dynamics of the real world over time.
A Practical Approach
Here’s how you might blend them in practice.
Start with systems thinking to map the territory. Who are all the stakeholders? What are the feedback loops? Where are the bottlenecks? This prevents you from optimizing one part of the system while breaking another.
Then zoom in with design thinking to understand specific user needs within that system. Build empathy, define the problem from the human perspective, and ideate solutions.
Create prototypes and test them- classic design thinking. But evaluate those tests through a systems lens. Ask not just “Do users like this?” but also “How does this change the system? What behaviors does it reinforce or discourage? What are the second-order effects?”
Scale thoughtfully by returning to systems thinking. How will this solution interact with existing processes, incentives, and structures? What might break? What reinforcing or balancing feedback loops will emerge?
The Bottom Line
You don’t have to choose between systems thinking and design thinking. They’re complementary tools for different aspects of complex problem-solving. The best technologists need to know how and when to zoom in and zoom out, to think about both the user experience and the system dynamics, and to create solutions that are both desirable and sustainable.
Where I Lie on the Spectrum
I realize I’ve been a design thinker by default, and that’s been both my strength and my limitation. But I am trying to bring systems thinking back in my projects. I’m naturally drawn to the tangible. I love talking to users, building prototypes, and seeing people’s faces light up when something works. The rapid iteration, the creativity, the immediate feedback – that’s where I feel most alive in my work. Design thinking gave me permission to experiment, to fail fast, and to put human needs at the center of everything.
But I need to ask before building: What might break if we change this?
For anyone working in innovation and technology, especially in AI product development, I think this is the journey we all need to take. Start with the empathy but develop the peripheral vision of systems thinking.