Technology Pilot Postmortem
Capture what worked, what didn't and the scale-or-kill recommendation after a pilot ends — so the organization learns something even when the pilot doesn't proceed.
Pilots that end quietly teach nobody anything. This postmortem format makes the learning explicit and portable: original hypothesis, what was actually tested, results against the success criteria, and the recommendation.
It also asks what would have to be true for this to work later, which is often the most valuable paragraph in the document a year on.
Keep them in a shared archive. The second most useful thing an innovation function can offer a business unit is proof that something has already been tried.
Capture what worked, what didn't and the scale/kill recommendation after a pilot. This tool is part of the InnoLead Tools library — a set of editable templates drawn from what our members use to run innovation functions inside large organizations.
- Download the document and drop in your organization's name, logo, and terminology.
- Delete the prompts you don't need; the structure matters more than the boilerplate.
- Circulate a draft to two or three stakeholders before you socialize it broadly.
