Note-taking method
Best PARA Method for Writers
Organize information by Projects, Areas, Resources, and Archives. For writers, the working week is notes spread across drafts, interviews, and research that should connect but don't. The rest of this page is the method, cut for that week.
By tentus team · Updated 2026-09-20
What PARA Method actually asks of you
Every note lives exactly where it can be acted on — Projects for now, Areas for ongoing responsibility, Resources for reference, Archive for the rest.
The weekly work is re-homing: anything untouched in Projects moves down the ladder. The archive grows without guilt; a dead project note is a filed decision, not a failure.
How writers put it to work
- 1
Fragments before paragraphs
Lines land where they occur — the opening of a piece, the phrase for later, the argument you overheard. Writing starts from assembled fragments instead of a blank page that owes you a draft.
- 2
An interview shelf searchable by theme
Transcripts and quotes are captured with the person and the theme attached. The quote you half-remember from a conversation last spring is findable by what it was about.
- 3
Assembly by connection
Drafting becomes pulling: related fragments surface next to each other, and the outline forms from what your notes already believe. The argument was half-made before you sat down.
The capture habit, the linking, and the retrieval are the parts tentus automates — para method without the daily upkeep.
Try it with tentus
tentus makes PARA Method practical for writers. Capture, link, and retrieve without the busywork.
Other methods worth trying
Zettelkasten
A slip-box method for connecting atomic ideas into a web of knowledge.
GTD
Getting Things Done — a workflow for capturing and processing tasks.
Atomic Notes
One idea per note, linked to others through context.
Progressive Summarization
Layer summaries on top of captured content as you revisit it.
PARA Method for other roles
Product Managers
juggling research, specs, stakeholder feedback, and launch plans across multiple tools.
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.