Innovation memory: why your company forgets its own ideas
A new colleague stands up in the planning meeting and proposes refill stations for the main products. The slides are good and the room likes it. Someone who has been around longer remembers that the same idea was proposed three years ago, tested in one store and dropped. Why it was dropped, nobody can say, and nobody can find out.
That is what missing innovation memory looks like. This piece explains what it is, why it fails in most organisations, and how to build one in an afternoon without buying anything.
What innovation memory is
Innovation memory is your organisation's ability to find what was proposed, what was decided and why, across workshops, teams and years. Not the ideas alone: the decisions around them and the reasoning behind each one.
A good test: pick an idea from a workshop two years ago. Can someone who was not in the room find out, within ten minutes, who decided what and on what grounds? If the answer is "ask the person who ran it", you do not have a memory, you have a person.
Why it fails
- Results live in slide decks and photo folders. The output of the workshop is a folder called "Workshop 2023-03-14" with forty photos of sticky notes. Nobody searches photos.
- The reason for a no is never written down. Ideas get dropped in a corridor or a steering meeting. The outcome reaches the list; the reasoning stays in the heads of the people who were there.
- People leave and take the context with them. The person who ran the store test knows why the refill stations failed. When they move on, the organisation only knows that the idea "did not work".
- Idea portals collect submissions, not conversations. A portal records that an idea was submitted and by whom. The three weeks of discussion that followed happened in e-mail and meetings and are not attached to it.
- Every workshop starts from zero. Because nobody can find the last round, the facilitator starts with a blank wall. The group produces the same ideas as last time, and the same objections surface in month three.
What a working memory contains
You do not need much per entry. You need the same few fields for everything, so that a search finds it.
| Entity | What to record | Example |
|---|---|---|
| Idea | One line, who proposed it, when, where it came from, current state | "Refill stations in flagship stores. Store operations, March 2023, retail workshop. State: dropped." |
| Question | The open question, who asked it, which idea it belongs to | "Do customers bring their own containers? Marketing, belongs to refill stations." |
| Assumption | What the idea depends on, who holds it, whether it was tested | "A discount is enough of an incentive. Untested." |
| Risk | What could go wrong, who raised it, how serious | "Hygiene rules for open food containers. Legal, serious." |
| Decision | What was decided, by whom, when, and the reason in one line | "Dropped by the retail steering group, September 2023. Reason: uptake in the store test stayed below the threshold agreed beforehand." |
The reason column matters most. "Dropped" without a reason is what you have today.
How to build it without a big tool
- Pick one shared place. A wiki page, a spreadsheet, a board, anything the whole team can open and search. Not e-mail. E-mail is where memory goes to die, because it belongs to one inbox.
- Write one line per decision, with the reason. Who decided, when, what, and why. "Parked: no budget in 2026" is a reason. "Parked" is not.
- Give every idea a state. New, scored (for example with the impact and effort matrix), in concept, decided, parked, dropped. Six states are enough. An idea without a state is an idea nobody owns.
- Keep parked and dropped ideas, with a date to look again. Dropping an idea is not deleting it. "Dropped: regulation forbids open containers. Look again: January 2027, when the regulation is reviewed." That sentence saves the next person three months.
- Look at the parked list for ten minutes every quarter. Read the reasons. Some no longer hold: the budget arrived, the regulation changed, a competitor moved. Those ideas go back to "new". The rest stay parked, and that is fine.
Tools like IdeaHone keep state and reason attached to every idea, but a well-kept spreadsheet does the job if the team actually opens it.
An idea dropped for a good reason is a result, not a failure. The reason is the valuable part: it is the one thing the next person cannot reconstruct on their own.
Signs you have no innovation memory
- The same idea returns every year. Usually with a new sponsor, new slides and the same objection in month three.
- Decisions get relitigated. A group that said no in spring argues the same question again in autumn, because nobody can show what was decided and on what basis.
- The sponsor asks what happened to the workshop in March. And the honest answer takes two days of asking around.
- New people propose old ideas. Which is not their fault. They searched and found nothing.
Never lose an idea between sessions
IdeaHone follows every idea from first mention to decision, across all your workshops and teams.
What is innovation memory?
Innovation memory is an organisation's ability to find what was proposed, what was decided and why, across workshops, teams and years. It lives in one searchable place, not in slide decks, photo folders or the heads of the people who were in the room.
How do we keep track of ideas across workshops?
Put every idea in one shared place with a one-line description, its origin, a state and the decisions made about it with the reason. Start each workshop by reading what the last one produced.
Should we keep rejected ideas?
Yes. Keep them with the reason they were dropped and a date to look again. The reason stops the idea from coming back unchanged, and the date brings it back when circumstances have changed.
