What decides whether an innovation method fits
Choosing an innovation method is a decision about your organization's constraints, not about the method's record somewhere else. The record elsewhere tells you the method works. It does not tell you it works here.
An innovation method is a structured procedure for finding, selecting and testing ideas. Every one of them carries assumptions about the organization running it: where the information you are missing sits, how much of the current operation can be changed, and how long you are allowed to search before something has to be funded.
Design Thinking is a human-centred discovery discipline — understand the user, define the problem, generate options, prototype, test — set out for a management audience by Tim Brown in Harvard Business Review in 2008. It assumes two things. The information you lack is outside the organization, in the user's experience. And you will be able to act on what you find.
Where both assumptions hold, it is a strong tool and this note is not about you. The four conditions below are the ones under which one assumption or the other does not hold, and under which running the method again with a different facilitator tests nothing.
When the method mirrors how you already work
If your organization is already run on customer centricity, a customer-led discovery method will be unusually easy to adopt and unusually unlikely to produce something you have not already seen.
Market orientation was formalised in the marketing literature in 1990, in two papers published that year in the Journal of Marketing: Kohli and Jaworski on the construct itself, and Narver and Slater on its effect on profitability. Both describe an organization that generates intelligence about customer needs, distributes it across functions, and responds to it. Set beside the discovery half of a design-thinking cycle, the instruction is close to the same instruction.
The ease of adoption is the warning rather than the reassurance. A process that resembles the one you already run will draw on the same inputs, ask the same population the same kind of question, and return an output bounded by what that population can articulate. The organization concludes that innovation is hard. What it has actually established is that it already knew this.
This applies to the discovery half specifically. Prototyping and testing discipline may be genuinely new to a market-led organization, and where it is, it may be the part worth keeping when the rest is dropped.
When you cannot set the existing operation to zero
Ideas that require replacing an asset base get recorded, admired, and never funded. The method is not producing bad ideas. It is producing ideas priced for an organization that does not exist here.
A new venture commits nothing. It designs a process and starts it. An established organization has machines, buildings, people, a brand, and a customer expectation already in place before the search begins, and it has to run the existing operation while testing the replacement.
So the same ideation step produces a different result. The output tends to call for technology bought early in its cost curve, external capability the organization does not employ, and a workforce willing to learn something new on a timescale nobody has budgeted. Each of those is a separate approval. The idea stalls at the first one and is filed, and the executive team is told again that nothing came of it.
The mismatch is between a method that assumes a clean start and an organization whose whole value is the thing it cannot switch off. Both parties are behaving sensibly. The pairing is what fails.
When there is no runway for open-ended search
Fail fast assumes that somebody will keep paying while you fail. Where the licence to fail has not been explicitly granted, with money attached and a stated duration, the organization is being asked to run a search procedure it cannot fund to completion.
That is worth stating plainly rather than as an accusation. In a competitive market with a quarterly reporting rhythm, an unbounded search is not a cultural failure to tolerate risk. It is an accurate reading of the capital available. What such an organization needs is not more tolerance but a sharper filter.
Three conditions make an idea worth funding in that situation, and an idea should be tested against all three before it consumes a budget:
- It addresses a problem enough people have that solving it displaces the current answer rather than improving it.
- Nobody visible in the sector is already working the same direction. An idea several competitors are pursuing cannot carry a defensible return, because arrival becomes a race and the return depends on who gets there first.
- It is technically feasible with resources largely already held, so the remaining work is tuning an arrangement rather than acquiring a capability.
An outside-in search works against the third condition in particular. Starting from what the customer wants points reliably at solutions requiring knowledge and resources the organization does not hold, which is precisely the class of project that carries the highest capital cost and the least predictable schedule.
This does not apply where a research budget exists with an explicitly granted tolerance for failure. Some organizations have one. For them the constraint described here is not their constraint, and the argument above should be ignored.
When the requirement is already a specification
In business-to-business work and in regulated work, the empathy-and-define half of the cycle repeats what the business already does continuously, and returns information it already holds.
Business to business. What must be delivered is specified in advance, in a document that is already a written statement of the customer's requirement. Where the relationship runs across a supply chain, understanding the customer and agreeing the problem are continuous activities rather than an event. A discovery cycle run over the top of that duplicates the ordinary conduct of the business and surfaces nothing the account team did not have.
Regulated. A customer-research pass in a regulated business returns wants the rules do not permit, because everything the rules do permit has already been done. The ideation step then inherits a brief that was impossible at the moment it was written, and the team concludes it is not creative enough.
The productive direction in both cases reverses. Establish first what the organization can do inside the constraints it actually has, then test what that capability is worth to the customer. This is the only order in which an unrecognized need can be found, for a structural reason: a customer can only ask for what they already know exists, so a need nobody has articulated is reached by offering a capability rather than by surveying a want.
Before you conclude the tool is wrong
A method run partially and a method that does not fit produce the same disappointment, and they need opposite answers. Establish which one you have before changing anything, because switching tools is the more expensive mistake of the two.
Four checks settle it:
- The full cycle was run, including prototype and test, rather than a two-day ideation event with the rest of the method unfunded.
- Somebody who practises the method reviewed how it was run, rather than the team assessing its own compliance.
- A decision route existed for the output, so an idea that survived the method had somewhere to go.
- The constraints above were stated before the work started, not discovered when the ideas arrived.
If all four hold and the output still could not be used, that is a finding about fit, and it is worth considerably more than another cycle. If any of them does not hold, the organization has not yet tested the tool it is about to replace.
None of this is a verdict on the method. It is a verdict on a pairing, and a pairing has two halves.
What sits on the other side of the choice
The alternative to one method is not a different single method. It is holding more than one and knowing which situation each is for.
The field is wider than most organizations use. Analogy thinking, lateral thinking and biomimicry draw on psychology and observation. TRIZ, morphological analysis and technology trend analysis come from engineering, and work from what is technically possible rather than from what is wanted. Theory of Constraints and Systematic Inventive Thinking come from management, and search inside a fixed resource envelope rather than widening the options first. Each carries its own assumptions and its own conditions, exactly as the method under discussion does.
An organization holding one method is not badly equipped. It is equipped for one situation, and it will keep meeting that situation whether or not the situation is in front of it. Digging with a knife works until the ground is hard.
None of the methods named here belongs to Bold Group, and Bold Group certifies against none of them. Where a method credential exists on this team it is held by an individual and stated on that person's profile, not by the firm.
Where this does not apply
Where the genuine unknown is what customers want, where you reach those customers directly, and where you are free to build something new rather than replace something that is earning, a human-centred discovery method is a strong choice and none of the four conditions bites. Switching away from it in that situation costs you a tool that was working.
It also does not apply where idea generation was never the constraint. An organization that cannot get a good idea funded, or cannot say who decides, has a governance problem, and no method resolves that from below. Changing the search procedure in that case changes which ideas fail to get funded, not how many.