Susana Jurado Apruzzese had two months and no extra budget to point Telefónica’s tech labs at business impact. Her lever was the gate every project has to pass.

“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.

Give the board a written thesis to judge projects against

The innovation board sets priorities and decides which projects get funding and which ones stop. Its job is to keep four kinds of project out of the portfolio:

  • Orphans: projects customers want but the company won’t sell, usually because they don’t fit its strategy.

  • Zombies: projects that get nowhere but refuse to die.

  • Ghosts: projects everyone in the company has heard about, but nobody has seen.

  • Cheaters: projects that promise a breakthrough “unique AI” that turns out to be “just prompting” once someone scratches the surface.

To keep them out, the board judges each project against an innovation strategy that follows the company’s overall plan. If the two don’t match, Susana warns, the work turns into “innovation theater,” and next year’s budget request gets harder to defend. She writes that strategy as an innovation thesis with four parts:

  1. Statement: what the company wants innovation to achieve.

  2. Thesis: the areas it wants to invest in.

  3. Antithesis: the areas it wants to stay out of.

  4. Assets: company resources a project can use (Susana’s own addition).

The thesis filters projects at the start of the funnel, so work outside the strategy stops before it uses resources.

Put the business sponsor in the decision

The board holds the money, but the business units hold the customers, infrastructure and operations teams a project needs. Susana calls a business-unit sponsor “absolutely key,” and no project moves forward without one.

At each toll gate, the checkpoint where a project moves on or stops, the sponsor helps the board decide. That role gives the business unit a stake from the start, and the stake grows through the funnel:

  • Prototype: an early version built to test the idea. The sponsor opens access to the business unit’s customers.

  • Pilot: a small trial in a real setting. The sponsor supports running it with the unit’s customers.

  • MVP: the minimum viable product, the first version good enough to sell. The sponsor puts business-unit people on the team, because that unit will take over the product.

A nice-to-have is fine with a business unit as long as it’s free, Susana says. Asking for more at each stage shows whether the project is more than that.

Ask innovation managers to watch for stuck projects

The board reviews projects at the gates, on a set schedule or when a project is ready. Between those reviews, a project can keep running without making progress, which is how zombies are made. Spotting them falls to the innovation managers, who meet the teams regularly.

Innovation managers watch two signals. Once the model has some history, Telefónica knows the average time a project spends in each phase: if the MVP phase usually takes six months and a project has spent eight there, something is probably going on. The second signal is what Susana calls the boredom metric. A manager sits down with a team, feels bored and realizes the team is repeating what it said two weeks earlier.

Exercise: the zombie check.

Use this check before each portfolio review to decide which projects to raise with the board.

  • Time in phase: How long has each project spent in its current phase, compared with your average for that phase?

  • Boredom: In your last two check-ins, what did the team tell you that was new?

  • People and budget: If this project stopped today, which promising project could use its people and money?

Explain every kill, then move the team on

Susana has heard the alternative to a deliberate kill too often: “My idea was incubated during six months, but then nothing happened because there was no budget to continue.” People who say that, she notes, probably won’t join the next innovation initiative.

Susana calls her answer the art of killing, built on three moves:

  • The decision makers explain their reasons to the whole organization, so everyone understands why the project stopped.

  • The team holds a debrief and shares what it learned, which shows its members that their effort created value for the company.

  • Team members move to other innovation projects and take on new challenges. Susana notes that this fits Telefónica and could look different elsewhere.

Because teams know the bar in advance from the Rosetta Stone questions, they can see for themselves when a project falls short. In Susana’s experience, kills handled this way may even lead some teams to stop their own projects.

Reply

Avatar

or to participate

Keep Reading