How Leaders Decide - Agile vs. Design Thinking or Both?

More predictable than the SWFLweather is the chance that I am asked, "what's the difference between Agile and?Design Thinking ?" While I may get caught in the rain without my umbrella often (hey - I'm an optimistic kind of gal). When it comes to consulting I prefer to provide value and resource tools. To that end, I thought it useful to provide the methodology differences of agile vs. design thinking as succinctly as possible. In this post, I will give you the distinct essence of the two. For more details into the differences and the process themselves, you will find these articles useful.:

A Beginner's Guide to the Agile Method & Scrums

What is Design Thinking, and why is it important? ?

Pondering in pictures

After reviewing both processes, I came to understand that it's not one versus the other. Instead, it is one or the other,?or both. And knowing which is essential. It's a creative quirk of mine that as I'm considering how things work and how to simplify explaining it, the inspiration often comes to me in images. The image of a hamster running on a wheel versus a hamster running a maze of tunnels came to mind as I pondered this topic. So what the heck does this image of hamsters have to do with agile vs. design thinking? Let's imagine ourselves in a medical lab.

Oh no, the rats are getting fat!

You're a medical researcher busy conducting your medical testing on lab rats. One day you notice the rats have become idle and fat. No longer are they busily playing with their other rat friends. Fat rats aren't healthy rats, and to appropriately measure the test's effectiveness; you need healthy rats. Alas, a problem that needs solving. How do we get the rats to exercise??

The right solution, wrong purpose

First, let's switch to the term hamster because it's not called a rat wheel, but I know you'll follow. And after many iterations to solve the problem, the hamster wheel is invented. The hamsters resume their activity. Yay! You have successfully resolved the "How do we get the hamsters to exercise?" problem. At least for a while. Strangely though within a few weeks or months, the hamsters become idle again and are uninterested in the hamster wheel. Why could that be? You've answered the "how-to" question, but you failed to answer the why question. And unless the two questions are connected, your solution is likely temporary at best.?

Like all animals (and humans in general), hamsters are naturally curious and playful, which leads to activity in their typical habitat. The problem the researchers solved was their problem, not the hamster's problem. The hamsters weren't lazy because they needed exercise; they were lazy because they were bored. The researcher's solution wasn't wrong. It just served the wrong purpose. This quote from?Edward Hadley from Mendix ?says it this way:

"Agile alone is no guarantee that your teams will consistently deliver truly engaging, impactful solutions. While agile can provide a highly effective way of solving problems, it doesn't guarantee that you're solving the?right?problems in the first place."?

In essence,

Agile solves problems while design thinking fulfills needs. -Karen Zeigler

This statement doesn't mean that design thinking negates agile. Or one is better than the other. It means that the two are distinct, used for two different purposes. Sometimes problems require one over the other and other times that requires both. Leaders' ability to distinguish between the two sets them and their teams up for greater success.

When to use which tool?

In sticking to my goal of delivering only the essence of the distinction, I offer this article if you want to further descend into the rabbit hole. Or in our case, the hamster labyrinth.

Design Thinking vs. Agile: Combine Problem Finding and Problem Solving for Better Outcomes

However, one key piece in understanding which tool to use is the origin of Agile methodologies. Agile began as a tool to help IT leaders solve systems problems, which are linear in nature. Design thinking originated with a more human-centered focus, in which humans are naturally more fluid.

Agile solves linear problems while design thinking is best for solving more unconfined or fluid issues. -Karen Zeigler

Thus issues around software, systems, certain parts of the supply chain, or manufacturing processes lend themselves to Agile methodologies. In contrast, the human aspects of the user interface, partnerships along the supply chain, managing people, or serving customers lend themselves to design thinking. You can likely see where some transformations would require both a means of addressing the linear aspects and a human-centered approach to understanding their needs. So the key to whether to use agile, design thinking, or both boils down to these questions.

1. Does the solution require a linear solution (even if it may be temporary) or a fluid one? Another perspective is to think specific vs. ambiguous.?
2. Am I seeking to achieve a particular desired outcome or to meet a need(s) of a human user?
3. Does my problem have elements of both??

Thank you for reading this post. If you found it valuable, please give it your favorite reaction and share the insight that resonated with you in the comments. If you are an expert in Agile or Design Thinking, please feel free to leave your value add in the comments.?

If you enjoyed this post, you might also enjoy:?Productivity Myths & the Power of Bringing Your Whole Self to Work. This article shifts perspective from focusing on the linear nature of tasks to the human aspects in increasing productivity.

For information on bringing design thinking into your next project or teaching design thinking principles to your organization's leaders, please send me a message.?