Note-taking method
Best Zettelkasten for Product Managers
A slip-box method for connecting atomic ideas into a web of knowledge. For product managers, the working week is juggling research, specs, stakeholder feedback, and launch plans across multiple tools. The rest of this page is the method, cut for that week.
By tentus team · Updated 2026-09-20
What Zettelkasten actually asks of you
One idea per note, and every note is linked to at least one other — deliberately, not by keyword.
The discipline is in the linking: when you file a note, you name the notes it argues with, supports, or extends. Structure emerges from those links; folders never appear.
How product managers put it to work
- 1
One discovery inbox
Interview notes, support tickets, sales calls, and the offhand comment from a beta user all land in the same place. Themed tagging happens later — the only job at capture is that nothing a customer said is lost to the meeting it was said in.
- 2
Decisions live with their evidence
When a spec decision is made, the reasoning gets captured where the discussion happened and linked to the spec. Three sprints later, "why did we drop the cycle button" is a link away, not an archaeology project.
- 3
Stakeholder recall before every review
Before a roadmap review, pull what each stakeholder was promised and what they pushed back on last time. Walking in with that is the difference between alignment and renegotiation.
The capture habit, the linking, and the retrieval are the parts tentus automates — zettelkasten without the daily upkeep.
Try it with tentus
tentus makes Zettelkasten practical for product managers. Capture, link, and retrieve without the busywork.
Other methods worth trying
Zettelkasten for other roles
Software Engineers
losing context between code reviews, incident postmortems, and technical research.
Designers
scattered moodboards, design critiques, and research that never gets referenced again.
Researchers
drowning in PDFs and citations with no way to connect findings across projects.
Writers
notes spread across drafts, interviews, and research that should connect but don't.