Why innovation champion networks fizzle out

Most innovation champion networks fade because they ask volunteers to spread innovation without giving them real work to do, time to do it, or anyone senior who acts on what they bring. The fix is not more enthusiasm or a bigger launch event. Give each champion a live problem in their own area, a protected slice of time agreed with their manager, a coach, and a fixed term with a clear end.

The belief, stated fairly

The belief runs like this: you cannot put an innovation specialist in every team, so recruit enthusiastic volunteers across the organisation, give them some training and a title, and they will carry the message, run sessions and surface ideas. It is a sensible idea. It is cheap, it reaches parts of the organisation a central team never will, and it draws on people who genuinely care. Champion networks are a familiar tool in change management for exactly these reasons.

Many networks start well. The launch is energetic, the first meetings are full, and a few early sessions happen. Then, often within a year, attendance thins, the group chat goes quiet and the network exists mainly on an organisation chart.

Why it fails in practice

Champions are given a message, not a job

"Promote innovation in your department" is not a task anyone can complete. Without a concrete problem to work on, champions end up running awareness sessions or collecting ideas. Both are hard to do well and produce little that anyone notices. People lose interest in work that has no visible result.

The time is borrowed, not given

Most champions take the role on top of a full job. Their manager agreed in principle but was never asked to give up anything. When a busy month arrives, the champion role is the first thing dropped, and nobody objects because nobody planned for it.

Ideas go up and nothing comes back

Many networks become idea collection channels. Champions gather suggestions from colleagues and pass them to a central team or committee. If those ideas wait months for a reply, or vanish, the champion is the one who faces colleagues asking what happened. After two or three rounds, they stop asking colleagues for ideas. The network has quietly taught people that speaking up is pointless.

There is no one to learn from

A two-day training course and a monthly call is not enough support for someone trying to run their first workshop in a sceptical team. Without a coach, champions either avoid the methods or use them badly, and conclude that the methods don't work.

Recognition is generic, or competitive

Champions often receive a certificate at the end of the year, or appear on a list of "most active champions". The first means little; the second turns colleagues into competitors and rewards visible activity over useful work. Neither tells the champion's manager what they actually contributed.

There is no end

The role is open-ended. Nobody knows when they are allowed to stop, so people drift away without saying so. The network keeps its headcount on paper while its real membership shrinks.

What works instead

1. Give each champion a real problem

Each champion should work on one live problem in their own area, chosen with their manager and a sponsor. The champion's job is to lead a small team through understanding, testing and handing over a change. The message about innovation spreads because colleagues see something change, not because they attended a session.

2. Agree the time in writing

Agree with the champion's manager a specific amount of time, for example half a day a week for one cycle, and what they will set aside to make room for it. A stop-doing list is useful here. Record the arrangement in a RACI so it is visible, not a favour.

3. Connect champions to decision-makers

Use a stakeholder map to identify who needs to decide on each champion's work, and set a date by which a decision will be made. Every idea or test that goes up must come back with an answer, even if the answer is no.

4. Pair each champion with a coach

Each champion should have an experienced practitioner who helps them prepare sessions, reviews what happened, and gradually steps back. Champions who have finished a cycle can coach the next intake. This is how the network grows real capability rather than just membership.

5. Meet to learn, not to report

When champions meet as a group, use the time for a short retrospective across their projects: what worked, what got stuck, what they would do differently. That is more useful than status updates and keeps people coming.

6. Recognise specific contributions

Keep a plain record of what each champion actually did: the problem they took on, the research they ran, the decision they secured. Share it with their manager. See how to recognise who contributed what, without rankings.

7. Set a term and a graceful exit

Make the role a fixed term, perhaps one or two cycles. At the end, champions can step down with their contribution recorded, renew, or become coaches. A clear end makes the commitment easier to accept and keeps the network honest about its real size.

Illustrative example: an engineering firm's champions

Illustrative. The organisation is invented.

An engineering consultancy with offices in Dublin, Lisbon and Warsaw launched a network of thirty innovation champions. Each received two days of training and a monthly online call. A year later, six were still active and the idea inbox had a backlog nobody had answered.

The firm relaunched with twelve champions instead of thirty. Each took one problem from their own office, such as slow handover of site survey data to design teams. Managers signed off half a day a week for a twelve-week cycle. Each champion had a coach from the firm's small practice team, and a director committed to deciding on each test within two weeks. Champions met every three weeks for a cross-project review.

At the end of the cycle, eight problems had tested changes, three had been stopped on evidence and one was still in progress. Five champions renewed, four became coaches for the next intake, and three stepped down with their work recorded and sent to their managers.

Do's and don'ts

Do

• Start small, with fewer champions and real problems.
• Agree time with each champion's manager in writing.
• Guarantee an answer on everything champions send up.
• Give every champion a coach.
• Use group meetings for shared learning.
• Set a fixed term with a clear end.

Don't

• Ask champions to "promote innovation" with no concrete task.
• Turn the network into an idea collection box.
• Rank champions by activity or publish "most active" lists.
• Measure the network by its headcount.
• Leave the role open-ended.
• Expect a single training course to equip people for the role.

Questions people ask

What does an innovation champion do? In a network that works, a champion leads a small team through one real problem in their own area: finding out what is going on, testing a change and handing it over. They also bring what they learn back to the other champions. In networks that fade, the role is usually limited to promoting innovation and collecting ideas.

How many innovation champions do you need? Fewer than you think. Start with as many as you can coach properly and give real problems to, often between five and fifteen in a mid-sized organisation. Grow the network when champions who have completed a cycle are ready to coach others.

How do you keep innovation champions motivated? Give them work with visible results, protected time, a coach and fast answers from decision-makers. Recognise what each champion actually contributed, specifically and to their manager. Motivation follows from results and from being taken seriously, not from events or badges.