Design Thinking Is Not a Workshop
After 19 years of facilitating Design Thinking, there's one pattern I see more reliably than any other: companies that book Design Thinking like a team event — two days, clear agenda, nice photos for the intranet — and then wonder why nothing changes afterward.
The energy in the room is real. The ideas are often genuinely good. People leave feeling like something important happened. And most of the time, they're right — something did happen. It just doesn't survive Monday morning.
I've watched this play out at telecom companies, airlines, automotive manufacturers, consulting firms. Across industries, the pattern is remarkably consistent. And I've been in this business long enough to be honest about one thing: part of the reason it happens is because of how we — the consulting industry — have packaged Design Thinking.
The Workshop Trap
At some point, Design Thinking became a product. Two days, a proven process, a skilled facilitator, tangible results by Friday afternoon. From a sales perspective, it's perfect — clear scope, clear deliverables, easy to budget for. The problem is that you can't compress a way of thinking into a two-day format and expect it to outlast the calendar invite.
What happens instead is a cycle that I've seen repeat so many times I could set my watch by it: A team goes through a workshop. Energy is high. Ideas are generated. Maybe a prototype is built. There's a presentation to leadership. Everyone agrees this was valuable. And then the results enter the organization's bloodstream — slowly, then not at all. Momentum fades. Priorities shift. Three months later, someone suggests booking the next workshop.
Each spike looks productive in isolation. But zoom out and you see the pattern: the organization isn't building capacity. It's renting energy. The workshop generates a temporary high, but the underlying way of working hasn't changed. The same meetings happen the same way. The same decisions get made with the same assumptions. Design Thinking becomes something the company does occasionally, not something the company is.
Why It Happens
I don't think anyone designs it this way intentionally. It happens because workshops are easy to buy and easy to justify. They have a start date and an end date. They produce visible outputs — photos of sticky notes, prototype videos, a final deck. Leadership can point to them as evidence that the organization is innovating.
What's harder to buy, harder to justify, and harder to photograph is the slow, unglamorous work of changing how teams actually operate. Adjusting meeting rhythms. Embedding user contact into regular workflows. Creating structures where insights lead to decisions, not just presentations. That kind of work doesn't fit into a two-day format. It happens over months. And it's much harder to put on the intranet.
What Actually Works
The companies I've seen get real, lasting value from Design Thinking have one thing in common: they stopped treating it as an event and started treating it as a practice. Not a dramatic shift — a quiet one. The kind of change that's invisible from the outside but transformative from the inside.
In practical terms, this means a few specific things. First, they created weekly rhythms instead of quarterly events. Ninety minutes a week where cross-functional teams work on real problems — not as a special initiative, but as a recurring slot in the calendar. The regularity matters more than the intensity. A consistent 90 minutes every week compounds faster than a brilliant two-day workshop every quarter.
Second, leaders participate instead of spectating. This is the single highest-leverage change I've observed. When the person who controls budgets and priorities sits at the table during prototyping — not to evaluate, but to co-create — the results don't end up in a drawer. They end up in the next quarter's roadmap. Because the decision-maker was there when the insight emerged.
Third, results connect to real decisions. The most common mistake I see in innovation programs: beautiful workshops that produce ideas nobody is accountable for implementing. The companies that make Design Thinking stick define upfront what decisions will be informed by the sprint results. Not "let's see what comes out of it" — "the output of this sprint will determine whether we invest in X or Y." That specificity changes the quality of everything that happens in the room.
The Honest Part
I sell workshops for a living. So let me be direct about something that works against my own short-term interests: if you only book workshops, you're not getting the full value of what Design Thinking can do. The workshop is genuinely valuable — it generates energy, aligns teams, creates shared language, and often produces real insights. I believe in the format. I've spent nearly two decades refining it.
But a workshop without follow-through structure is a spark without fuel. It burns bright and then it's gone. The organizations that get lasting results pair the workshop with months of embedded practice afterward. Not because they want to spend more on consulting — but because behavior change doesn't happen in two days. It happens in the weeks and months that follow.
Design Thinking is not a method you book. It's a muscle you build. The workshop gets you started. The practice makes you strong.
If you're planning a Design Thinking workshop, plan the six months after it at the same time. Define the weekly rhythm. Identify who participates from leadership — not as an observer, but as a co-creator. Connect the sprint results to a real decision with a real deadline. Without these structures, the workshop will be a great experience that doesn't change anything. With them, it becomes the beginning of something genuinely different.