Note-taking method
Best PARA Method for Journalists
Organize information by Projects, Areas, Resources, and Archives. For journalists, the working week is interview transcripts, source contacts, and story threads that don't connect. 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 journalists put it to work
- 1
Sources and what they said, linked
Every contact's statements are captured as quotes with the conversation they came from. When a story breaks open, what each person said — and when — is a search, not a shoebox.
- 2
Story threads that accumulate
Angle ideas capture as they occur, linked to the evidence that supports them as it arrives. The piece you write in March was mostly gathered in January.
- 3
Chronology on demand
Events, statements, and documents captured with their dates reconstruct into a timeline. In reporting, the order things happened in is often the story.
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 journalists. 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.