Innovation Campaign Canvas

How to plan and run a successful innovation campaign

Most innovation challenge templates give teams a checklist. This canvas gives them a dependency map. A measurable goal makes criteria possible, a defined audience tells you which channels belong, and a real budget decides whether the feedback loop will be trusted. The sections below explain each block through one running example: a products company planning a circular-design challenge around packaging and materials reuse.

Goal — set a measurable outcome before scoring begins

The goal block comes first because it cannot be changed quietly once submissions open. A challenge-ready goal names a metric, a scope, and a constraint. Without that, evaluators have no defensible way to choose between ideas, and the shortlist becomes a debate about preferences rather than outcomes.

Sample entry: We are tying this campaign to our 10-year vision of productivity gains through circular economy and materials reuse — concretely, cutting virgin-material spend 15% within three years, so every idea can be measured against money and material saved.

Challenge — write a question that attracts the right ideas

The challenge question is the public face of the goal. A good 'How might we' question names the domain, keeps the approach open, and adds the few constraints contributors must respect. Too broad invites off-topic submissions. Too narrow prescribes the answer before the audience has a chance to find it.

Sample entry: How might we redesign our packaging so materials come back to us instead of going to landfill — without raising unit cost? Context for responders: packaging is 22% of our material spend, customers have started asking about take-back, and a 2024 trial stalled on logistics rather than design.

Audience — define who should submit before you pick a channel

Audience definition comes before channel choice because the right channel depends on who must receive the brief. An internal employee challenge, a partner challenge, and a public challenge each need different language, different collection defaults, and different evaluation assumptions. If the audience is vague, the submission pool drifts away from the goal.

Sample entry: We are opening this to the three teams who touch materials every day — operations, design and procurement — roughly 400 people across our four sites, rather than the whole company, so the ideas come from people close to the problem.

Channels — reach the right people without inviting noise

Channel choice follows from the audience map. Broadcast too widely and evaluators spend time on noise. Under-communicate and the pool is too shallow to sustain a serious shortlist. Most campaigns need repeated touchpoints, but collection should still converge in one place so the pipeline stays manageable.

Sample entry: We are launching with QR-code posters on the shop floor for site teams and an idea form on the intranet for desk staff — both feeding the same shared inbox so nothing scatters across channels.

Submission form — ask for the minimum and leave the rest out

Form length directly controls idea volume. The useful question is not what would be nice to know later. It is what an evaluator needs now to judge the idea against the published criteria. If a tool can generate a title or summary from a short answer, let it. Every extra field pushes participation down.

Sample entry: We are asking for just two things — the idea in a sentence, and the material or waste stream it targets. AI drafts the title and a short summary from that, so no one abandons the form between tasks.

Criteria — publish the scoring logic in the brief

Criteria belong in the challenge brief, not only in the evaluator spreadsheet. They give the panel a shared standard and give contributors a visible target to aim at before they submit. Keep the list short. Define impact, feasibility, and fit with the goal, but avoid prescribing solution form if you still want novelty.

Sample entry: We are scoring every idea 1–5 on material saved, feasibility within 12 months, and fit with the circular-economy goal — and we are publishing those three criteria with the brief so people aim for them from the start.

Evaluators — decide where AI screening fits and who makes the call

Evaluator design changes when AI pre-screening is part of the workflow. Without it, the panel must absorb full volume. With it, humans judge a filtered subset and need calibration more than stamina. Functional diversity matters more than seniority: include domain knowledge, implementation authority, and someone close to participant reality.

Sample entry: AI will cluster submissions into themes and flag duplicates first; then a four-person panel — two designers, a procurement lead and our sustainability owner — scores the shortlist against the published criteria.

Implementation owner — name who will carry winning ideas forward

A campaign without a named implementation owner is a suggestion box with a deadline. Ownership has to be explicit before launch: a person, a mandate, and a commitment to act when selection ends. If implementation ownership is postponed until after winners are chosen, it turns into negotiation at the exact moment momentum starts to fade.

Sample entry: We are pre-assigning each theme to a site operations lead who has agreed, before launch, to pilot the winning idea on their line within the quarter — so no winner is left without an owner.

Budget — make the feedback loop credible before anyone submits

Budget is both a constraint and a signal. A named pilot fund tells contributors the challenge leads somewhere real. A vague promise of support tells them the opposite. The useful budget line says what gets funded, for how long, and who has authority to release it when the shortlist is set.

Sample entry: We are ring-fencing a €50k pilot fund plus two days of an engineer's time per winning idea, committed and announced before submissions open so people know the winners will actually be built.

Timeline — decide whether this is a one-off or a real program

The timeline block is where teams quietly decide whether they are running a single challenge or building a repeatable program. The two models need different funding logic, review rhythms, and ownership structures. Publish dates either way, but be honest about which operating model the timeline is actually supporting.

Sample entry: We are running a three-week submission window, one week of scoring, and announcing winners on a fixed date — then repeating the cycle each quarter so it becomes an always-on rhythm, not a one-off.

Feedback loop — design it before launch, not as an afterthought

The feedback loop is a pre-launch decision because it determines whether there is a next campaign. Decide who communicates outcomes, by what date, to which participant groups, and with what level of detail before submissions open. If feedback is left until the end, it arrives late, vague, and easy to skip.

Sample entry: We will send every submitter a short note on what happened to their idea and why, and feature each implemented one — with the person's name — in the monthly all-hands, so people see participating pays off.

Fill in all eleven blocks and you have more than a template. You have a planning sequence that shows which choices must be made before others can be trusted. Teams that revisit the canvas across multiple cycles stop arguing about missing structure and start arguing about the ideas themselves.

Two very different campaigns from the same canvas

The same dependency logic scales from a focused circular-design challenge to a single-team service sprint. The blocks stay the same. The operating model does not.

Frequently asked questions

What is an innovation campaign canvas and what does it include?

An innovation campaign canvas is a single-page planning tool that maps the eleven pre-launch decisions every innovation challenge requires: goal, challenge question, audience, channels, submission form, evaluation criteria, evaluator panel, implementation owner, budget, timeline, and feedback loop. Each block is sequentially dependent.

How do you write a 'How might we' challenge question?

A well-scoped 'How might we' question names a specific domain, keeps the approach open, and adds the few constraints contributors must respect. Too broad invites off-topic submissions. Too narrow prescribes the answer.

What criteria should I use to evaluate innovation challenge ideas?

Use criteria that define impact, feasibility, and fit with the challenge goal. Publish them before submissions open so contributors can aim at the same standards the panel will use.

Who should be on an innovation challenge evaluation panel?

Prioritize functional diversity over seniority. Include people close to the challenge domain, at least one person with implementation authority, and someone who can judge whether the idea is practical for participants and operators.

What makes an innovation challenge fail before it launches?

The most common pre-launch failures are a goal without a measurable outcome, no named implementation owner, and no planned feedback loop. Those gaps create evaluation confusion and erode trust before any winning idea can move.

How do you close the feedback loop so people participate again?

Plan the feedback loop before launch. Name who communicates outcomes, by what date, to which participant groups, and how specific the feedback will be. If you leave that decision until the end, it usually arrives too late.

What's the difference between a one-off challenge and a continuous program?

A one-off challenge has a fixed start and finish. A continuous program standardizes evaluation, funding, and ownership so the challenge model can run repeatedly without being rebuilt each cycle.