What an innovation manager does all day, and what they should

The job description says "drive innovation across the organisation". The calendar says eleven meetings, two slide decks and a hackathon to organise by March. This is for the person with that title, and for the manager who hires one: what the role becomes, what it should own instead, and three numbers that show whether it works.
What the role tends to become
Nobody plans it this way. Events are visible, decisions are not.
- Event organiser. Hackathons, idea campaigns, innovation days. Each produces a wall of sticky notes and a photo for the intranet.
- Method evangelist. Design thinking trainings, canvases, a certificate for everyone. Useful once, a career if you let it.
- Portal administrator. Someone has to approve submissions, fix categories and merge duplicates. That someone is you.
- Slide producer for the board. A quarterly deck with idea counts, participant counts and a funnel nobody compares with last quarter's.
None of these is wrong. All of them together leave no time for the work the title promises.
What the role should own
Owner of the question
Vague ambitions land on your desk: "we need to be more digital", "do something with AI". Your first job is to turn them into a question a workshop can answer. "How could we halve onboarding time for new customers" is a question. "Digital transformation" is a mood. A workshop brief makes the sponsor say what a good answer looks like before you book a room.
Owner of the path from workshop to decision
Nothing produced in a session leaves the room without an owner, a score and a decision date. Not "we will look at it": a name, a number and a day in the calendar. Most ideas fail in the weeks after the workshop, not in it. Why ideas die after the workshop lists the causes; your role exists to remove them.
Keeper of the memory
You are the one person who knows what was tried, what was decided and why. In your head it is worth nothing. Put it where a product manager in another department finds it in two minutes: idea, score, decision, reason, date. An innovation memory is what separates an innovation function from a series of events. Tools like IdeaHone keep this record as a by-product of the session; a shared folder with discipline also works.
Broker between the room and the sponsor
The room produces a concept. The sponsor needs a one-page ask: what we test, what it costs, what we learn, by when. You translate both ways: upwards, a concept becomes an ask; downwards, a no becomes a reason the team can learn from, not a silence.
The person who kills ideas well
Most ideas should not survive, and your job is to make sure they die properly: parked with a reason and a review date, or dropped with a reason that gets written down. Nobody is humiliated. The proposer hears the decision from you, not from a status field.
A week, before and after
A typical pattern, not data. Your week will differ; the direction matters.
| Activity | Hours typical | Hours better |
|---|---|---|
| Workshops and their follow-up | 6 | 12 |
| Sponsor conversations | 2 | 6 |
| Keeping the record | 1 | 4 |
| Events and campaigns | 12 | 4 |
| Reporting and slides | 8 | 3 |
| Trainings and method work | 6 | 3 |
The total stays roughly the same; the hours spent on workshops, sponsors and the record more than double.
Block Friday morning for the record: every idea from the week gets its owner, score and decision date written down. If the memory is not kept, the rest is theatre.
Three measures that say whether the role works
- Time from workshop to decision. Days between the session and a recorded yes, no or parked. Past a month, the path is broken, not the ideas.
- Share of workshop ideas with a recorded decision. Not implemented, decided. The number should approach all of them.
- Number of ideas that came back unchanged. The same proposal from another team, nobody aware it was dropped two years ago. Each one is a hole in the memory.
Submissions, participants and events are missing on purpose. They measure activity.
An innovation manager without a sponsor who decides is an event manager. Before you accept the job, ask who says yes to a tested concept, how much they can commit alone, and how often you see them. Vague answers, vague title.
Four ways to stay busy and change nothing
- Measuring submissions. More ideas in the portal is easy to produce and proves nothing.
- A workshop a week with no follow-up. People stop contributing once their work vanishes. Fewer sessions, each closed properly.
- Owning the portal instead of the decisions. Administering a tool is a task; owning the path to a decision is the job. If the portal eats your week, delegate it.
- Being the only one who innovates. If every idea passes through you, you are the bottleneck. Make the path usable by others, then step aside.
Never lose an idea between sessions
IdeaHone follows every idea from first mention to decision, across all your workshops and teams.
What does an innovation manager do?
Turns vague ambitions into questions a team can work on, owns the path from workshop to decision, keeps the record of what was tried and why, and brokers between teams and the sponsor. Events and trainings are tools, not the job.
What skills does an innovation manager need?
Facilitation, writing a one-page ask a sponsor can decide on, discipline in keeping records, and the nerve to say no with a reason. Method knowledge matters less than follow-through.
How do you measure an innovation manager?
Time from workshop to recorded decision, share of workshop ideas with a recorded decision, and how many ideas return unchanged because nobody knew they were dropped. Submission counts measure activity, not results.