The team has run out of ideas.

What to do when the team has run out of ideas

Ventura, California, September two thousand and twenty-two. Yvon Chouinard, the founder of Patagonia — fifty years old when he started the company in nineteen seventy-three, eighty-three at the moment this scene takes place — has been working through a problem that has occupied him for most of his career.

The problem is not a marketing problem. It is not a product problem. It is not, in any familiar sense, a team has run out of ideas problem.

It is the problem of how to reconcile Patagonia's environmental mission with the commercial imperative of growth. For fifty years he has tried. Most years the reconciliation has worked well enough. Some years it hasn't. And for fifty years the reconciliation has lived inside Chouinard, in the Chouinard family, and in the company's leadership — held by people who could be replaced.

In two thousand and twenty-two, when the company is valued at around three billion dollars, Chouinard makes a move that sits entirely outside the standard menu of corporate ideas.

He transfers the ownership of the company to a purpose trust and a non-profit, structured so that all future profits — roughly a hundred million dollars a year — go directly to fighting climate change. The Chouinard family keeps no equity. No board seats. No controlling interest.

The interesting thing about the move isn't the generosity. Plenty of founders donate. The interesting thing is that it is an answer to the question how do we innovate as a company that no innovation workshop would ever have produced. Because the innovation isn't a new product. It isn't a new process. It is a new ownership structure that makes the company's stated purpose structurally unfakeable.

When the team has run out of ideas, the problem the team is working on may not be a product problem. It may be a structural problem, and the ideas that would solve it live in a completely different part of the building.

So let's go to the office and work through it.

Start by asking whether the team is tired or trapped in its words

"The team has run out of ideas."

The feeling is stagnant.

The team has been in the same room, looking at the same whiteboard, for what feels like a week. Every new idea is a variation on a previous idea. The ideation sessions have started feeling like rituals — they happen because they are scheduled, not because anyone expects anything to come of them.

Two choices. Same stagnant team. Different first move.

When the team needs fresh input

Choice one: the team is tired. Cognitively, environmentally, visually. They have been staring at the same whiteboard for a week. The ideas they are generating are variations on ideas they already had. The brain forms its associations from what is in the environment, and an environment that hasn't changed for three days is an environment that can't produce new associations.

If that's the read, cancel the meeting. Send everyone out, alone, for an hour. A gallery, a hardware store, a supermarket, a park. Anywhere that isn't the office.

Steven Johnson, working on what he calls the adjacent possible, has written about this. The hour away isn't rest; it is raw material. The brain needs new inputs to make new associations. Walking through a hardware store while thinking about a software problem produces connections that staring at the whiteboard cannot.

When the team's own jargon is the trap

Choice two: the team is trapped in their own vocabulary. Every sentence is loaded with industry terms. The terms are carrying assumptions the team has stopped noticing. The discussion sounds sophisticated and is producing nothing, because the language itself has become a constraint on what can be said.

If that's the read, ban the jargon for the day. Nobody is allowed to use any of the standard words. User, engagement, funnel, conversion, churn, retention. Force the team to describe the problem using only ordinary English and whatever analogies they can find.

Richard Feynman, in the technique that bears his name, found that if you can't explain it in plain language, you don't actually understand it. The discipline is painful for the first twenty minutes and productive after that, because the jargon was doing the thinking for them, and stripping it out forces them to think again.

Tired, or jargon-trapped. Same stagnant team. Two different first moves.

How to structure the divergence on purpose

Three tools. The discipline is to structure the divergence; don't trust it to happen on its own.

Use a constraint to force new starting points

The first is

Ideation Techniques as a discipline.

Ideation Techniques as a structured field traces through Alex Osborn's Applied Imagination in nineteen fifty-three — the same Osborn who codified Brainstorming, which we covered in scenario one — and the wider creativity-research tradition that emerged from advertising and design through the nineteen-fifties and nineteen-sixties. The contemporary toolkit is multi-source: SCAMPER — substitute, combine, adapt, modify, put to other uses, eliminate, reverse — morphological analysis, random word association, and a dozen others.

The reason structured Ideation Techniques matter when the team has run out of ideas is that unstructured brainstorming tends to produce variations on whatever the loudest person said first. The technique is the constraint, and the constraint is what produces genuinely different starting points.

The unique insight is that the specific technique matters less than the forcing function. SCAMPER and random-word association produce different ideas, but both produce ideas different from whatever the team would have generated under unstructured conversation. The forcing function — use this specific operator on the existing concept and see what it generates — is what breaks the team out of variation-on-the-loudest-voice.

What you get is a set of starting points the team would not have produced on their own. Not all are good. The point isn't that the techniques generate winning ideas; the point is that they generate different starting points, from which winning ideas can be developed.

So. How to use them.

Pick. SCAMPER for variations on existing concepts. Random word association for genuine lateral moves. Morphological analysis for systematic combinatorial coverage. Reverse brainstorming — how would we make this fail? — for problems where the team has been too positive.

Run. SCAMPER means going through every letter — substitute, combine, adapt, modify, put to other uses, eliminate, reverse — even the ones that feel unproductive. The discipline is the structure; skipping letters defeats it.

Capture. During the technique, no idea gets evaluated. The team writes down whatever surfaces. Evaluation comes later.

Filter. Once the technique has run, the team evaluates against the problem. Most of what surfaces will be unworkable. A small number will be genuinely new starting points.

Switch. Different techniques produce different shapes of idea. Running the same technique twice produces diminishing returns; switching produces fresh material.

Surface connections a list would hide

The second is

Mind Mapping.

Mind Mapping as a structured visualisation was popularised by Tony Buzan through the nineteen-seventies and his Use Your Head book in nineteen seventy-four, with deeper roots in nineteenth-century concept maps and Joseph Novak's educational research. The structure is simple — a central concept with branches radiating outward, sub-branches developing each direction, all on a single page. The format is doing structural work: it forces the team to capture associations non-linearly.

The reason Mind Mapping matters when the team has run out of ideas is that lists encourage linear thinking, and the associations the team is trying to surface are specifically the non-linear ones. The list format reads top-to-bottom and produces ideas in the same shape; the map format radiates outward and produces ideas across the page.

The unique insight is the visual structure. Two ideas that would never appear next to each other on a list often appear next to each other on a mind map — and the proximity is what makes the team see the connection. The visual layout is doing the connection-finding the team's discussion has been failing to do.

What you get is a single-page artefact the team can look at together, where unexpected connections become visible because the format makes them visible.

So. How to draw one.

Idea. The problem or the goal in the middle of the page, in a single phrase.

Branch. First major direction radiating outward. Sub-ideas develop along it — who, what, when, why, how. The sub-branches are where the genuinely interesting material surfaces.

Branch again. Another direction. Already the map sees combinations the linear list never would.

Keep branching. Three to five primary branches in total. When two sub-branches on different sides of the map suggest a combination, draw a connecting line — the cross-branch connections are usually the productive ones.

Every branch invites another branch — the structure multiplies, it does not list.

Protect a full day for ideas to surface

The third is

the Innovation Workshop.

The structured Innovation Workshop as a contemporary practice traces through IDEO's work in the nineteen-nineties and two-thousands, the d.school's design-thinking curriculum, and the deeper organisational-development tradition that goes back to T-groups and the Tavistock Institute work of the nineteen-fifties. The format — a full day, protected time, mixed-discipline team, external facilitator if available — is structural rather than novel.

The reason the Innovation Workshop matters when the daily format has stopped producing ideas is that the daily format never survives normal office conditions for long. Meetings get hijacked by other priorities. Discussion gets cut short. The team that has been ideating in thirty-minute slots between other work has been ideating in conditions that don't support the work.

The unique insight is the protected day. Not three hours, not a half day. A full day, blocked, with a facilitator if one is available. The facilitator isn't running the content; they are protecting the time, which is the part that never survives normal office conditions.

What you get is a structured environment in which the team can actually run the ideation toolkit at depth. Different techniques, different exercises, time to follow the productive lines without the meeting ending.

So. How to design one.

Define. Before the day, agree what specific question the workshop is trying to generate ideas for. How do we increase activation in segment X by twenty per cent? is a workshop question. How do we innovate? is not.

Pick. Engineering, design, product, customer support, sales — different perspectives on the same problem. The mix is part of the design.

Structure. Morning: divergent generation using two or three techniques. Afternoon: convergent evaluation, prototyping, prioritisation. Don't conflate the two halves.

Protect. Calendars cleared. No interruptions. The facilitator's main job is preserving this.

Carry. The workshop produces candidate directions; the next sprint validates them. Without follow-through, the workshop becomes the activity rather than the input.

That's the toolkit. One more story before we close — although the story comes in three voices, across three phases of one decision, years apart.

A precedent: changing the category instead of the product

The Chouinard story we opened with showed the move of stepping the question sideways at the scale of a billion-dollar company — when the team has run out of ideas inside the existing category, sometimes the move is to change the category itself. The story we close with shows the same move at organisational and civic scale, more than a hundred years earlier — and the move is carried not by a single architect, but by three women across three phases of one campaign.

Sempervirens Creek, the redwood basin south of San Francisco, eighteenth of May, nineteen hundred. A small group of journalists, naturalists, and civic-minded Californians camp along the creek and at that campsite found the Sempervirens Club. The conventional path of saving the redwoods has run out. Private ownership of the standing timber is being consolidated for harvest; appeals to existing federal-park machinery have not produced results at the speed the trees are being cut. The club's structural decision is not to find a better appeal to the existing machinery — it is to build a state-park system from scratch in a state that has never had one.

Carrie Stevens Walter is named the founding secretary alongside Charles W. Reed — president — J. Q. Packard — treasurer — W. W. Richards — sporting secretary — and the photographer Andrew P. Hill — official artist. Walter, a poet and journalist already established in San Jose, takes on the work of converting the campsite convening into an institutional vehicle that can hold the campaign across the years it will take to deliver.

Sacramento, nineteen-oh-three to nineteen-oh-six. Laura White — a veteran of the California suffrage campaign by the time she takes the Sempervirens Club presidency — carries the campaign through its delivery years. Governor Henry T. Gage signed the appropriations bill purchasing twenty-five hundred acres in nineteen-oh-one. In nineteen-oh-four, on White's watch, California Redwood Park officially opens — the first state park in California. White's tenure carries the campaign across the gap most state-level legislative achievements quietly fall into: the gap between the bill is signed and the park is running.

California Redwood Park, nineteen-oh-seven to nineteen-oh-eight. Kate Moody Kennedy succeeds White as Sempervirens Club president and carries the campaign through the first sustained operational years of the new park. The question shifts. Can a state-park system be built? The nineteen-oh-four opening answered that. Will this one survive its first administrators? Kennedy's tenure answers that question by making the answer routine — by holding continuity through the early-park transition, the structural decision proves itself as a working institution rather than as a legislative achievement.

So.

Chouinard at Patagonia stepped the category sideways at the scale of a billion-dollar company — the question moved from what new product or process to what new ownership structure. The Sempervirens Club stepped the category sideways at organisational scale and across an eight-year horizon — the question moved from how do we save these specific trees from this specific harvest to how do we build a state-park system that can hold the question structurally. Two scales, a hundred and twenty-two years apart, the same structural move.

What the Sempervirens Club arc shows that Chouinard's case alone could not: the structural decision sometimes requires more than one architect. Walter could not have delivered without White. White could not have made the decision survive its first operational years without Kennedy. Three named architects, one structural decision, three phases. When the team has run out of ideas, the question is not always who has the next idea? — sometimes the question is what shape of decision is bigger than any one architect can carry alone, and who are the others who can carry the phases I cannot?

So. Your Next Move from this playbook.

How well-defined is the question you're about to ideate against — and is the team's frustration about lack of ideas actually about ideas, or about a problem nobody has properly framed?