If you’ve spent time in a product or innovation team, you’ve probably heard both terms thrown around, sometimes in the same meeting, sometimes by people who mean very different things by them. Design thinking and agile are two of the most widely adopted approaches in modern business, and they’re also two of the most misunderstood, especially when people treat them as competitors.
They’re not competitors. But they’re not the same thing either.
What Design Thinking Actually Is
Design thinking is a problem-solving approach that puts the human at the centre of everything. Before you build anything, write a single line of code or spec out a feature, you need to spend real time understanding the people you’re building for. What are their frustrations? What are they actually trying to accomplish? Where does their current experience break down?
The process typically moves through stages: empathize, define, ideate, prototype, and test. It’s intentionally uncertain at the front end. You’re supposed to sit with ambiguity, explore broadly, and resist the urge to jump to solutions mode too quickly. The whole point is to make sure you’re solving the right problem before you invest in solving it well.
Design thinking originated in the world of product design and architecture, but it’s been widely adopted in business strategy, healthcare, education, and just about every other sector you can think of.
What is Agile Actually
Agile is a project delivery methodology. It came out of software development in the early 2000s as a reaction to the rigid, slow, and often disastrous world of waterfall project management. The idea is that you work in short cycles called sprints, typically one to four weeks, and you continuously deliver, review, and improve.
Rather than spending a year planning something in exhaustive detail and then building it, agile teams ship small pieces of working product, get feedback, and adapt. The emphasis is on speed, flexibility, collaboration, and responding to change rather than following a fixed plan.
Agile has its own vocabulary: sprints, standups, backlogs, retrospectives, velocity. For people new to it, the terminology can feel like a lot. But the underlying philosophy is pretty simple: build a little, learn, repeat.
Where People Get Confused
The confusion usually starts when organizations adopt one without the other and then wonder why things aren’t working.
A team running pure agile without any design thinking can ship quickly and consistently, but there’s a real risk they’re building the wrong thing.
Speed is great. Speed in the wrong direction is expensive. If you never slow down to deeply understand your customer’s problem, you can end up with a very efficiently delivered product that nobody actually wants.
On the flip side, a team that only practices design thinking can produce beautiful insights, rich customer research, and stacks of sticky notes from workshops, but struggle to actually get anything out the door. Design thinking without a delivery discipline can become an endless loop of exploration that never translates into real outcomes.
How They Work Together
The teams that tend to get the best results use design thinking to figure out what to build, and agile to actually build it.
Think of it as two gears that need each other. Design thinking operates at the front of the process where you’re still defining the problem and generating ideas. Once you’ve landed on a direction worth pursuing, agile takes over as the delivery engine that gets it into the world quickly and iteratively.
Some organizations formalize this with a “dual-track” model, where a discovery track runs design thinking activities in parallel with a delivery track running agile sprints. The discovery work feeds the backlog with well-researched, validated ideas, and the delivery team builds them out.
A Practical Way to Think About It
If you’re working on something where the problem is already well understood, your customer needs are clear, and you just need to execute efficiently, agile on its own might be what you need.
If you’re working on something new, entering an unfamiliar market, solving a problem you haven’t fully defined yet, or finding that your solutions keep missing the mark, design thinking is where you should start.
And if you want to build things that are both right and fast, the answer is usually both, applied thoughtfully at the right stages.
The best practitioners of either approach will tell you the same thing: the methodology is just a tool. What matters is staying genuinely curious about your customers, staying honest about what you know and don’t know, and building a team culture where learning is valued as much as shipping.
Want to apply these ideas in your organization? Let’s talk, book a free 30-minute consultation.