An online, filterable, sortable list of every feature, who owned it, what was done — and what was deliberately not done, with the reason. The institutional memory the product team needs to stop relitigating decisions every six months.
Without a written history, two predictable failures repeat: features get re-pitched as if no one had thought of them before, and the reasons something was discarded last year are forgotten just in time to repeat the mistake. The history file is how the product team protects its own past learnings.
A tool I conceived to know which PM worked on which feature.
An overlay on the live product surfaces, by area, who has owned the feature historically. Hover a section, see the PM (current and previous), the epic, the date of the last meaningful change, and a link to the related Jira tickets. New PMs use it to onboard onto a surface in hours instead of weeks; senior PMs use it to know exactly whom to consult before touching something.
Three threads, kept on the same online list so they can be filtered and sorted together:
Has to be an online list that can be filtered and sorted. Not a slide deck, not a quarterly export — a living artifact that anyone in the team can query in ten seconds.
| Feature / area | Owner(s) | Status | Decision | KPI before → after | Last change |
|---|---|---|---|---|---|
| Cart quantity selector — mobile | PM A → PM B | Shipped | — | +3.2 pts cart→checkout | 2026-01 |
| Brand filter on catalog | PM C | Discarded | Out of scope (deferred to FY +1) | — | 2025-09 |
| HP carousel — variant B test | PM B | AB tested — variant A won | Variant B retired | +5.1 pts HP→PIP | 2026-02 |
Discipline
Every closed epic must add at least one row. The PM who closes the epic is responsible for the entry — not the next person who happens to be in the area.