12 Oct Innovation Methods: What Brainstorming, Design Sprints, and Design Thinking Can Actually Do, and What They Can’t Deliver
You’ve probably seen this before. Ten people in a workshop room, sticky notes covering the wall, and by the end of the day there’s actually a good idea up there. By Monday, it’s dead. Nobody’s quite responsible for it anymore, and nobody’s quite convinced anymore either. Most of the real problems with design thinking, or with brainstorming, or with a design sprint, start right here. It’s a pattern I’ve run into too often over the years, too often to chalk up to coincidence.
Most debates about brainstorming, design thinking, design sprints, and innovation methods split into two camps. One side calls the method useless, nothing more than smoke and mirrors with sticky notes. The other defends it with rules, steps, and better variations. Both sides miss the actual point. The method was never the problem. Nobody ever clearly asked what a method can actually deliver in the first place.
I look at this from two angles. First, I’m trained in design thinking and design sprints myself. I’ve run dozens of sessions, trained other facilitators to run them, and I still do it today whenever a client genuinely needs it. Second, I’ve spent years looking at exactly these formats through the lens of systems theory and organizational design. That’s why I know where the method holds up and where it gets oversold.
Before we can even talk about the method, though, we need to understand the idea itself, and what it takes for one to survive.
Contents
Why an Idea Is Already Dead Without Its Originator
What Brainstorming, Design Sprints, and Design Thinking Actually Deliver
Where the Real Problems with Design Thinking Start
Why the Better Idea Doesn’t Automatically Win
Why a Good Idea Still Isn’t an Innovation
Why Ideas Die at Functional Boundaries, Not From a Lack of Courage”
Why an Idea Is Already Dead Without Its Originator
The Moment Ideas Die
An idea starts out as a thought in a single person’s head, rough and unfinished, and in most cases not even remotely convincing at first, not even to the person who had it. It only becomes something solid through further thinking, conversations, and friction with reality.
This is exactly where organizations make their most common mistake. An idea comes up in department A, and because department B is responsible for that area, it gets handed over. That doesn’t work, because at this early stage an idea can’t be separated from its originator. Whoever had the idea knows the intermediate steps, the personal investment, and the small corrections that turn out to be necessary along the way. Whoever only inherits the result gets a hollow shell instead.
That only changes once the idea has turned into something tangible. A prototype, a sketch, or a piece of code can be handed off. A bare idea can’t be, not yet.
Why Employee Suggestion Programs Only Work for Small Things
Most idea management processes miss this distinction entirely, which is exactly why they reliably fizzle out as soon as more is at stake than a small, mundane improvement.
Classic employee suggestion programs and continuous improvement processes still earn their keep, just not for the reason usually given. For small but genuinely important things, like a sharp edge on a staircase or a step in the workflow that could be simplified, they work well.
For real innovation, they run into an extra problem. Anyone who has to submit an idea in writing ends up being judged on how well they write, not on how good the idea is. The sharpest mind on the shop floor is rarely the strongest writer on a suggestion form. Those are two completely unrelated skills, and a process that mixes them up filters out the wrong thoughts.
What Brainstorming, Design Sprints, and Design Thinking Actually Deliver
Producing Ideas Is the Wrong Ambition
A method like a design thinking session or a design sprint workshop doesn’t produce ideas. It creates a protected space where thoughts that have often been sitting there for a while finally get said out loud. The best ideas rarely show up during the scheduled session. They show up on a run, in the shower, or just while cooking dinner. What actually happens in the room is usually something else: people finally work up the nerve to say out loud something they’d already been thinking, but couldn’t voice before because there was no room for it.
If the method still gets sold as an idea-production machine, sticky notes and all, it quickly turns into what could fairly be called business theater: plenty of visible activity meant mainly to prove how innovative everyone is, without anything new actually making its way through the organization. In the end, it stays what it is: a frame, not an idea factory.
Where the Real Problems with Design Thinking Start
Most of what people call out as problems with design thinking takes aim at the method itself. Too loosely defined, too many sticky notes, not enough depth. There’s something to that, but it’s not the actual core of the issue.
Complicated or Complex: Wohland’s Distinction
Dr. Gerhard Wohland, a physicist by training and a management consultant who leads a German institute focused on what he calls dynamically robust organizations, draws a line between complicated problems, which can be solved with expertise and the right procedure, and complex problems, where the solution isn’t known in advance and what’s actually needed is judgment, not a checklist.
Not every idea automatically belongs in the complex category:
🔧 Complicated: a known process, a small improvement to it, like an approval workflow that requires three signatures when one would do. A procedure is all you need here.
🧠 Complex: no known solution, real judgment required instead of a checklist. This is the kind of idea this article is actually about, and it’s also what most innovation debates really mean.
Breaking a complex problem into five steps doesn’t automatically make it more manageable, and it doesn’t turn it into a complicated one either. A procedure can still make individual pieces of it more tangible. What it can’t do is remove the underlying uncertainty.
Recipe or Tool Is What Decides, Not the Method Itself
This distinction has a practical consequence that rarely gets spelled out. A method can be used as a recipe or as a tool. Used as a recipe, it works regardless of who’s following it, step by step, and whoever follows it hands over their own judgment in the process. When the recipe fails, the usual explanation is that it wasn’t applied correctly. Rarely does anyone admit that the real mistake was treating a complex problem as something a recipe could solve in the first place. That’s exactly the difference between a method and a tool, the distinction most people miss in organizations.
A tool, a hammer, say, still requires your own judgment to use it correctly in a given situation. Design thinking, brainstorming, and the design sprint all work when they’re treated as tools. They fail the moment they get carried out like a recipe, with the quiet assumption that five correct steps will automatically produce the right outcome.
The Real, Shared Problem Is What Decides, Not the Method
Even the right tool is useless if nobody actually has a real problem to apply their judgment to. What really decides the outcome is a real, shared problem. A meeting the boss called to figure out how to season a stew doesn’t cut it. What’s needed is a problem the people in the room genuinely want to solve, because it’s pressing from the outside and getting expensive to leave unsolved. Once that problem exists, the method becomes almost beside the point. Whether it’s classic brainstorming, a structured variant like brainwriting, or a full design sprint, none of it changes much at that level. Without a real problem, even the best procedure is worthless.
Why the Better Idea Doesn’t Automatically Win
Even when an idea is good and has an originator who’s carrying it, success still isn’t guaranteed. In the end, innovation is also a question of resonance, and resonance is not the same thing as quality.
Betamax vs. VHS: Quality Is Not Resonance
Tech history makes this easy to show. Betamax was technically superior to VHS and still lost, because a different dynamic than pure product quality ended up deciding the market. Anyone who believes the best product automatically wins is ignoring how much ultimately comes down to chance, timing, and social traction.
Resonance Depends on the Person, Not Just the Idea
That’s a different point than the originator argument from the first section. That one was about the knowledge needed to execute an idea. This one is about trust, about who people are actually willing to follow.
People often get behind the originator rather than the idea itself, because they trust that particular person to pull it off. That kind of traction depends not just on the idea, but on the person carrying it. It’s a question of fit.
Soccer offers a vivid illustration. When Zlatan Ibrahimović signed with FC Barcelona in 2009, nobody questioned his individual talent. Even so, he never really fit Pep Guardiola’s tiki-taka system, which was built around constant passing options and a specific style of movement, not around a single dominant striker. The experiment was over after one season. Ibrahimović wasn’t playing worse soccer. The system just had little use for his particular type of player. It’s the same with originators inside organizations. How good someone is doesn’t tell you whether they fit the system they’re in.
Why a Good Idea Still Isn’t an Innovation
Even a good idea with a convincing originator still isn’t an innovation. An idea is a thought inside one person’s head. That was the whole point of the first section. An organization, on the other hand, doesn’t have a head. Niklas Luhmann, the German sociologist and the most influential figure in systems theory and social cybernetics, described exactly this early on: an organization consists entirely of communication, of ongoing decisions, not of people with minds and feelings. Both disciplines still shape how we think about organizations at CoHive today.
For an idea to become an innovation, it has to enter that ongoing communication and actually change it. This is exactly the threshold where design thinking fails most often in practice, not at the point of coming up with the idea.
Why Ideas Die at Functional Boundaries, Not From a Lack of Courage
The second major cause of death for ideas rarely comes down to individual people. It sits in the organizational structure. When someone in sales spots a fundamental problem with the market, but engineering owns the solution to it, the idea gets stuck at the functional boundary. That’s rarely because nobody had the courage to speak up. It’s because functionally divided organizations make exactly this kind of handoff systematically harder.
The Invisible Decision Premise Behind Functional Boundaries
Niklas Luhmann would put this even more sharply. An organization uses its decision premises to determine, in advance, which decisions are even allowed to be made where. The split between sales and engineering is itself one of those premises. It settles, long before anyone has a good idea, that a market problem sales identifies isn’t sales’ decision to make, it’s engineering’s. That’s exactly what makes the idea structurally invisible before anyone even gets a chance to talk about it.
To an organization’s ongoing communication, any new idea simply doesn’t fit in at first, regardless of whether it would actually be useful. Decision premises don’t distinguish between useful and harmful novelty, they only recognize what’s already part of the existing repertoire.
It’s a Structure Problem, Not a Communication Problem
The problem sits in the organizational structure. Training people to speak up more or give better feedback doesn’t change much of that, as long as the decision premises are set up so that ideas need a different department to even get picked up. Anyone who takes that seriously inevitably ends up asking why organizational development rarely works at scale, and what organizational and team development work built to address exactly these functional boundaries would actually have to look like.
What an Actual Protected Space Requires
The protected space we talked about earlier, in the context of workshops, is psychological. It lets thoughts that were already there come out into the open. The protected space that actually matters in the end is something else. It’s structural.
A real protected space needs three things:
✅ Someone with enough power in the organization to temporarily suspend or change the existing decision premises for one team and one project.
✅ A real, urgent problem with real feedback from the market, not a sheltered simulation where a method gets rehearsed under artificial conditions.
✅ The resources and authority to implement a solution directly, instead of handing it off to the next department at the end, where it runs straight back into the old decision premises.
A well-run design sprint shows what this can actually look like for a few days. People from different departments sit in the same room, without the usual approval chains standing between them. If someone with real decision-making authority, the so-called Decider, is also in the room, directional calls get made immediately and stick, instead of drifting through weeks of approval loops. For those few days, the organization’s normal decision architecture is genuinely suspended.
That’s also exactly where it runs into its limits. A design sprint doesn’t make a rigid organization dynamic. It shows, for a few days, what a dynamic organization could look like. Once the sprint is over, though, the old system reasserts itself, unless someone makes sure the new decision pathways survive past the sprint. Anyone who wants to change an organization has to work on the hard structures, on how decisions actually get made, how teams are structured, and how bonuses get handed out, not on the color of the sticky notes.
Creating that protected space, and defending it long enough for the new way of working to prove itself, is actually the job of leadership. Not facilitating the next workshop.
Conclusion: The Real Problems with Design Thinking, Brainstorming, and Design Sprints Live in the Structure
Anyone planning a design thinking workshop, or any other innovation method, for tomorrow should honestly answer five questions first:
❓ Is there a real, shared problem that the people involved actually want to solve?
❓ Is the method being used as a tool that requires judgment, or as a recipe being followed blindly?
❓ Does the idea originator stay involved in implementation, instead of handing the idea off to another department?
❓ Is the organization even structured in a way that lets a good idea survive the functional boundaries between departments?
❓ Is someone willing to actively change the existing decision premises for this specific project, and defend that change against the rest of the organization?
If the answer to any of these is no, the method won’t fix that. Design thinking, brainstorming, or a design sprint are still worth doing, but only for what they actually are: a frame for existing thinking, not a substitute for the structural work that has to come first. Nobody does that work on the side during a workshop. It’s a leadership job.
Get in Touch
Plenty of organizations keep investing in new creative methods while the real problem sits somewhere else entirely, in a structure that keeps good ideas from ever getting a real chance. In an initial conversation, I look together with you at where the real leverage points are in your organization. No charge, no pitch, no obligation.