Killing ideas is part of the job, but teams often stop them for the wrong reasons.

A senior leader doesn’t like the idea, and that settles it. The sponsor changes roles, and nobody picks the project up. The team brings an AI-written business case to the gate and can’t answer the first hard question. The market looks too small on a slide. Or nobody makes the decision at all, and the project keeps running.

This week’s four articles look at who should decide which ideas to stop, and what they need in front of them when they do.

At Reckitt, Gianluca Balzamo lets consumers make the big calls before an idea reaches the brands. Vincent Atallah of Aucctus adds friction back into AI-driven research, so the team owns the case it brings to the gate. At Telefónica, Susana Jurado Apruzzese splits the decision to stop a project across three roles, with the bar set in advance. And Microsoft’s Inclusive Design Toolkit shows how to count everyone who shares a need before a small number ends the conversation.

What was the last idea your team stopped, and who made that decision?

Hans Balmaekers
Founder, the Compass and Novum

Let Consumers Do the Killing

Reckitt’s front-end ideas often got stopped once they reached the brands, because nobody could show that consumers needed them. Gianluca Balzamo’s team now tests every concept with consumers before asking the business for money.

The concept card shows a man in a VR headset with a spray bottle in each hand, chasing cartoon bacteria across a kitchen counter for points. Reckitt's front-end team designed the concept, called CleanQuest, for a frustration that 39% of surveyed consumers named among their top cleaning complaints: the chore feels too big to start. Even before testing, people on the team were asking whether it went too far.

In many companies, a doubt like that gets settled in a meeting room, by gut feeling or by whoever created the idea. The same forces decide the fate of front-end ideas once they reach the brands: an opinion ends some, while a sponsor who leaves or changes roles ends others. Underneath these decisions sits one weakness. Each idea rests on a guess about what consumers need, so anyone in the business can question it.

Gianluca Balzamo, a senior scientist on Reckitt's front-end team, built a process that replaces the guess with consumer evidence. Working with the business prototyping company NOBA Ventures, his team tested CleanQuest in AI-moderated interviews with 302 consumers in the US and Europe. Consumers ranked it last of ten, which settled the debate with data instead of opinion.

The same process took the brief effortless cleaning from 85 pain points to one technology platform, now briefed to R&D and on its way into Reckitt's product categories. AI made the approach practical for a small team, since AI-moderated interviews and AI ideation replaced days of workshops. The result is a front end that hands the business ideas consumers have already ranked, along with Gianluca's plan to get the business pulling for them sooner.

Friction Makes People Own the Decision

AI can build the case for an idea in minutes. Adding friction at four key moments makes sure the team owns the decision.

At Innov8rs Manchester, Vincent Atallah, co-founder and president of the AI innovation platform Aucctus, asked a room of innovation leaders three questions. Most raised a hand to say they had read an AI output and forgotten it by the next meeting. Most also said they felt buried by how much AI can produce. Only one person said they would feel confident taking an AI output straight to leadership and defending it.

A study of 119 innovation teams by Innov8rs and Aucctus found the same gap: 97% use AI, yet only 8% let it inform decisions to kill, continue or invest in an idea. Vincent’s explanation for the gap: teams don’t fight for conclusions they didn’t reach. AI now does most of the work, so teams have little to defend. His answer is friction: small, deliberate steps where people do part of the work themselves, so they own the result.

He suggests adding those steps at four points where an idea is most at risk: when the team checks its assumptions, before the research starts, at the gate meeting and in early talks with senior leaders. A short check at the end shows whether the friction is working.

Board, Sponsor, Innovation Manager: Who Stops a Project at Telefónica

The board judges each project against a written strategy, the sponsor commits more people and customers at every stage, and the innovation managers flag projects that have stopped making progress.

“This technology is cool. I want to test it.” That was how Telefónica’s independent technical labs picked their projects, Susana Jurado Apruzzese says. When the company pulled them into a new area called Innovation Labs, each lab focused on the solution more than the customer’s need, and wanted to build everything in-house. Susana, an engineer herself, understood the instinct: “We engineers love building things ourselves.”

Her brief was to point all of the labs at business impact without losing their speed. She got two months to do it, and no extra budget or people. What she did have was the observation that the teams wanted to keep working on their projects, and to do that, they had to pass the gates. So she turned the gate requirements, a document she calls the Rosetta Stone, into questions every team answers before each toll gate. The questions push teams to look at the business, and to weigh partnerships or startups before building in-house.

Those gates are where projects stop, and no single group makes that call alone. Three roles share it: the board that holds the budget, the business sponsor who sits in each decision and the innovation managers who flag stuck projects.

Count Again (Before a Small Number Kills Your Idea)

Microsoft’s design team found that a product for people who can use only one arm also serves 21 million others: people with a temporary injury, and people with their hands full. Its Inclusive Design Toolkit shows how to count them.

In May 2013, August de los Reyes was six months into his job as head of design for Xbox when he hurt his back and needed emergency surgery. The spinal injury left him disabled. Back at work and in daily life, he kept running into products and places that didn’t fit him, and he came to see disability as a design problem: a mismatch between a person and the world built around them.

He started pushing Microsoft to design for people like him, and Kat Holmes, a principal design director, took up the idea. Her team studied groups that products usually overlook, such as deaf people and people with dyslexia, and ran design sprints where people with disabilities worked alongside product teams as designers. What the teams learned became Microsoft’s Inclusive Design Toolkit.

The approach also had to answer a business objection: designing for people with a disability can look like designing for a small market. In the US, about 26,000 people a year lose an arm or hand for good. On a category review slide, an idea built for that group looks small, and small ideas often get stopped early.

So the toolkit counts everyone else who shares the same need. About 13 million people can use only one arm for a while, after an injury like a broken wrist. Another 8 million can use only one arm in certain moments, like a parent holding a baby. Together, that comes to more than 21 million people.

The toolkit turns that count into a method any team can use. The method starts with the customer who struggles most, then counts everyone who shares the same need. Innovation teams can use it to choose who tests an idea and to bring the full market size to the keep-or-kill call.

What’s happening @ Novum

Most innovation conversations start with “what can we create next?” Jonathan Reeves, Global Head of R&D and Innovation at Opella, thinks we should spend more time on another question: how can we turn what we know into a capability that can be used repeatedly?

Technical solutions, consumer and product insights and lessons from failed experiments tend to stay stuck in one project, one brand or one person’s head, so the next team starts from scratch. Next week Wednesday November 25th, we’ll explore with Jonathan how to turn that knowledge into capabilities that can be used again and again, and what it takes to make this happen in practice.

AI can now scan a market, size an opportunity and screen hundreds of ideas in an afternoon. Recent research suggests it often does this better than people do. So what is your innovation team actually for? We’ll discuss how AI is transforming the way innovation teams work, make decisions, and create value on Thursday December 3rd, with Danielle Jaffit (Quartz Labs), Christian Mühlroth (Itonics) and Vincent Atallah (Aucctus),

Which tasks have leading teams already handed to AI, and which did they take back? Where does AI quietly make judgment worse? And what changes in who you hire and how you justify the team to your CFO? Come with one task you’re unsure about handing over. We’ll put it to the panel.

Curious to join these discussions about capability building and/or human vs AI in innovation? Join the Novum Society - check this page for more info.

Interesting findings this week. Gianluca’s team at Reckitt put its most extreme concept into consumer testing on purpose, as a test of the process itself: would consumers reject a weak idea before it cost real money? They did, and Gianluca counts that as a success, because for a front-end team with limited resources, killing fast is a KPI. You can test your own process the same way: put one concept you expect to fail through it, and see how long your team takes to stop it.

What I take from Vincent’s piece is the opposite lesson about speed. Aucctus made its AI product slower on purpose: sessions grew from 11 to 43 minutes, and users became five times more likely to name the top three risks in their own concept. So before you speed up the next step in your process, ask what your team learns by doing it the slow way.

Next week: Frank Mattes on growth projects that are really bets which companies run like routine projects (about one in three, in his experience). Plus how Walmart tested its way to online grocery models that make money.

Hans

Hans Balmaekers
Founder, the Compass and Novum

Reply

Avatar

or to participate

Keep Reading