Product research
Stop losing the research behind the roadmap.
A product decision rarely starts in the roadmap. It starts with something a user said.
A competitor flow. A screenshot. An article. A pattern. A problem someone noticed. The roadmap remembers what you decided; Shelf helps you remember what shaped the decision.
- User signal“I never got past the second screen”Interview, week two.
- ResearchActivation report, page 12Onboarding failure reads as churn.
- CompetitorTheir four-step first runKept as a flow, not a screenshot.
- ReferenceEmpty state that says one thingThe pattern you borrowed.
- Idea“Fix week one before adding anything”Written after the interviews.
- DecisionRebuild onboarding this quarterWhat the roadmap records.
Everything above led here
Six months later the question isn't what you shipped. It's why, and the trail is still attached.
The roadmap shows what.
Memory explains why.
Months after a decision, the important question often isn't “what did we ship?” It's “why did we think this was the right thing to do?”
How the trail survives.
- 01 · KeepCapture signalsKeep useful research and references.
- 02 · UnderstandConnect contextPreserve the relationship between the things that informed the thinking.
- 03 · RecallSearch laterFind old evidence from imperfect memory.
- 04 · ReuseRevisitSee how earlier research connects to today's question.
Four searches from a real quarter.
Each one starts from a decision or a half-memory, not a filename.
What you remember
There was an interview quote and a report section that convinced us.
Clues Shelf can use
- Interview note plus a report page
- Onboarding and activation in the text
- All kept in the same fortnight
- Meaning
- A first-run failure described by a user.
- Context
- Kept in the week the decision was made.
- Nearby
- The activation report and the competitor flow.
Kept nearby
- Activation report, page 12 · March
- Their four-step first run · March
Two things kept four months apart.
Neither mentions the other. Both belong to the same decision.
- Written after user interviews
- One line, no title
- Beside the activation report
- Kept while building the new first run
- Interface capture
- Beside the onboarding rebuild notes
Capabilities behind this workflow.
- 01Contextual searchSearch inside a project or a period.
- 02Memory graphEvidence, notes and references around a decision.
- 03Memory reconstructionRebuild the thinking, not just the artefact.
- 04Semantic searchFind the argument you remember.
- 05PDFsLand on the page, not the file.
- 06NotesFragments as legitimate evidence.
Unreleased plans and user words stay local.
Interview quotes, unshipped roadmaps and competitor evidence live on your Mac. Shelf reads them there, with no account and no upload.
Context is part of the product.
Keep the why close to the what.
Keep the signals as they arrive. The decision they produce stays explainable a year later.
Next thought
Every roadmap is a list of conclusions with the reasoning deleted.
Shelf for product managersKeep exploring
Shelf V3 is out now
Shelf V3 is the current build. Shelf does not use automatic updates, so download the latest build here and install it over your current version.
This is intentional. Shelf is built around a local-first, privacy-focused philosophy. An automatic updater requires additional background processes, network connections, update infrastructure, and another system with permission to modify the app. We prefer to keep Shelf’s network footprint and background activity as small as possible.
Manual updates keep the process explicit: Shelf only checks the internet when a feature actually needs it, and you decide when a new version is downloaded and installed.