There’s a question I hear from leaders all the time…and sometimes out loud, sometimes just in the look on their face at the end of a long day….“Is design thinking actually worth it?”
And honestly? It’s a fair question.
Because most organizations have tried it. They’ve booked the facilitator, cleared the calendar, covered the walls in sticky notes. Teams were energized. Ideas were generated. Someone photographed the wall for the slides.
And then Monday came. Projects stalled. Teams stayed misaligned. Customers still felt like an afterthought. The sticky notes dried up and fell off the wall.
So what went wrong?
The Problem Isn’t Design Thinking
I’ve been doing this work for over twenty-five years, and here’s what I know, the method isn’t the problem. The problem is what we do with it or more accurately, what we don’t do with it.
Design thinking gets treated like a one-time event. A creativity exercise. A “nice to have” box to check before the real work begins. We invite people into a room, generate a lot of energy, and then send everyone back to their desks to execute the plan they already had.
When that happens, you haven’t used design thinking. You’ve used the aesthetics of design thinking. And there’s a real difference.
What Leaders Are Actually Trying to Solve
When a leader asks me whether design thinking is worth it, they’re not really asking about the method. They’re asking something much more specific…
Will this stop us from building the wrong thing? Will this reduce the rework that’s eating our budget? Will this help our teams make faster, better decisions?
These are real operational problems. And they all share the same root cause: organizations move into execution before they’ve built shared clarity on the problem they’re actually solving.
That’s not a creativity gap. It’s an alignment gap. And it shows up everywhere: in the project that pivots at month four, in the product that launches to silence, in the strategy document no one can explain to a new team member.
Where Design Thinking Actually Delivers
Design thinking works when it’s embedded where decisions get made and not as a workshop sandwiched between planning and execution, but as the way an organization starts work. That is why we talk about deeper clarity and the importance of alignment.
That means three things in practice.
First, it means defining the right problem. Not “what are we building?” but “what are we actually solving, and for whom?” This sounds simple. In my experience, most teams cannot answer it clearly. They have a solution in mind before they’ve understood the problem, which is a very expensive way to move fast.
Second, it means aligning stakeholders early before execution begins, not halfway through when changing direction costs real money. The most powerful outcome of a well-run design thinking process isn’t the ideas…it’s the shared language. When everyone understands the problem the same way, they make better decisions independently. That’s where speed comes from.
Third, it means testing assumptions before you scale them. Every project is built on assumptions about what customers need, what the market wants, what the technology can do. Design thinking surfaces those assumptions early and gives you a structured way to check them. That’s not risk tolerance. That’s risk reduction.
What This Looks Like in Practice
I often tell clients, stop thinking of this as a workshop and start thinking of it as a way your organization starts projects.
Design thinking becomes a structured front-end process. The part that happens before the Gantt chart, before the sprint planning, before the RFP. It brings customer insight into the room when decisions are still reversible. It creates the shared clarity that makes everything downstream go faster.
I’ve watched teams cut months of rework by spending two focused days at the beginning getting clear on what they were actually solving. That’s the ROI. Not the sticky notes.
The bottom line
When design thinking doesn’t work, it’s almost always because it was treated as an add-on rather than a starting point. The organizations I’ve seen get real results from it are the ones who use it to answer the hard question first: are we solving the right problem?
When you get that right, everything downstream becomes easier. Decisions get made faster. Teams stay aligned. Customers stop feeling like an afterthought.
That’s not a workshop outcome. That’s a way of working.
If you’re questioning whether your current approach is creating clarity or just activity, let’s talk. Spring2 Innovation helps organizations align early, reduce risk, and build with confidence.
Want to apply these ideas in your organization? Let’s talk, book a free 30-minute consultation.