Persona Playbooks
A guide for writers on how to organize a growing research library — build a project-based structure for articles, books, and essays that makes research
A journalist is three drafts into a long profile when an editor flags a quote: where did this come from, and can she stand behind it? She's fairly sure it came from one of the people she interviewed, sometime over months of reporting. Finding it again means re-listening to recordings or re-reading dozens of saved sources, because nothing was organized well enough to answer "where did this come from" in under an hour.
That scenario is the writer's specific research problem, and it's different from a scholar's. A single magazine profile can generate interviews, years of background reading, and dozens of saved web sources; a nonfiction book project multiplies that volume many times over across a multi-year reporting process. In both cases, the organizing question is never "how do I format this citation?" — it's "where does this source fit in the story I'm telling, and can I still find it when I need it?"
That's the question this guide organizes around: a project-based structure, use and verification status tracked separately, so a writing session starts with writing instead of searching.
Writers retrieve research in the context of writing: "what do I have for Chapter 5?" or "what sources support the claim I'm making in this section?" The organizational structure should mirror how the writing is structured, not how research was gathered.
This means organizing primarily by project, and within projects, by section, chapter, or theme — whatever maps to the narrative architecture.
For a book project:
For journalism:
For essays:
Writers make a category error by treating "research I gathered externally" and "ideas I generated internally" as the same type of thing. They're not.
External research (articles, studies, quotes, documents) needs to be organized for retrieval — you need to find it when writing. Internal ideas (structural insights, thematic connections, a paragraph that came to mind in the shower) need to be organized for development — you need to build on them and see how they relate to each other.
Keep these in separate Collections:
Research that's been incorporated into a draft is different from research that hasn't been. Research that's been found to be inaccurate or unusable is different from research that's still active. Recording use status prevents:
Standard use status tags:
active — in the working library; potentially usefulused — incorporated into a draft passagenot-used — reviewed and decided not to use (but keeping for reference)superseded — replaced by a better source on the same pointA source that's used in a draft may still need verification. A fact that's been captured but not verified shouldn't appear in a published piece. Track these independently:
verified — the fact, quote, or claim has been confirmed accurateto-verify — captured but not yet verifiedunverifiable — could not confirm from an authoritative sourceA nonfiction book researcher may spend 2-3 years gathering research before or during writing. At this scale, organization isn't just convenient — it's a prerequisite for the project being completable.
Phase-based organization within a project:
Early research (field orientation):
Active reporting/research:
Writing phase:
The master source list: For book projects, maintain a master source list note in the primary book Collection:
BOOK: [Title]
Total sources: [running count]
Last updated: [date]
MOST IMPORTANT SOURCES
1. [Source name] — [Why it's foundational to the book's argument or narrative]
2.
3.
SOURCES BY CHAPTER
Chapter 1: [list of key sources]
Chapter 2: [list]
...
OUTSTANDING RESEARCH NEEDS
1. [What I still need to find]
2.
3.
The master source list serves as a map of the research landscape: where you are, what you have, what you still need.
A journalist who covers a beat over years accumulates knowledge that's valuable across assignments. The environmental reporter who has covered water issues for 5 years has developed a mental database of sources, organizations, research, and context that no single assignment would justify building from scratch.
But this accumulated knowledge is only useful if it's organized and retrievable. A clipping folder by year is not useful. An organized, tagged library by topic and source type is.
Beat reporter's cross-assignment organization:
Each new assignment creates a project Collection that draws on the beat archive for background and adds to it with new research.
Most professional writers are working on multiple projects simultaneously: a magazine piece due next month, a book proposal, an essay collection, and early research for a future book. Each project has its own research library, but some sources cross project lines.
Managing multi-project research:
Project-first Collection structure: Each project gets its own primary Collection. Never mix research from different projects in the same Collection.
Cross-project tagging: When a source is relevant to two projects, tag it with both project names: project-book-A and project-essay-collection. It lives in one Collection (wherever you primarily captured and annotated it) but is findable from either project tag.
Reference Collections for persistent knowledge: Some knowledge is relevant across projects indefinitely — your understanding of a field, profiles of recurring sources, general background. These live in Reference Collections that aren't tied to a specific project.
Project close-out: When a project ends (book submitted, article published), move its research to an Archive Collection. Capture any "future use" captures in a separate note before archiving.
When a new project grows out of an old one — a book article that becomes a book proposal, a journalism piece that turns into a longer investigation — the old project's research becomes the new project's foundation.
Inheritance protocol: when starting the new project, review the old project's Archive Collection. Move items that remain relevant to the new project Collection. Note why each moved item is relevant to the new work. Leave the original archive intact as a reference.
Writers need annotations that serve three moments: (a) building the research library (when you annotate a source), (b) writing from the research (when you're in a draft and need a source), and (c) revision and fact-checking (when you're verifying claims in a finished draft).
CAPTURE: [Title or description]
Source: [Publication, author, date — in whatever format you'll remember]
Project: [Which book/piece/essay this is for]
Section relevance: [Which chapter, section, or theme this supports]
USE
What I captured this for: [One sentence on what this source is specifically useful for]
The specific detail/fact/quote I need from this: [The most important sentence or data point]
Where in the narrative this appears: [Draft location or "not yet placed"]
How I'm using this: [background / cited fact / direct quote / scene detail / structural idea]
VERIFICATION
Is this fact/quote verified: [Yes / No — still need to confirm]
If no: what I need to verify and how: [specific]
NARRATIVE VALUE
What this contributes to the story: [why this source belongs in the piece at all]
Better sources that might replace this: [if there's a stronger source I should find]
The "narrative value" annotation field is what makes a writer's annotation different from a researcher's. A researcher asks "what does this source argue?" A writer asks "what does this source contribute to the story?" The answer is often different: a study contributes not just a finding but a scene (the researchers working in a specific lab), a character (the lead researcher), and an argument (the finding and its implications). The annotation should note all of this.
Writers accumulate quotations — statements by sources, historical figures, public officials, experts — that may or may not appear in the final piece. A quote library organized as a separate Collection or sub-Collection allows you to see all quotations from all sources together and identify the strongest ones for the piece.
For each quotation capture:
QUOTE: "[Exact verbatim text]"
Speaker: [Name, title, context]
Source: [Where this appears — interview transcript / publication / public statement]
Date: [When it was said or published]
Project: [Which piece this is for]
Context: [What was being discussed when this was said]
NARRATIVE USE
Why this quote is strong: [What makes it worth using]
Where it might appear: [Epigraph / section opening / body quote / closing]
Status: [Active — considering using / Used in draft at [location] / Not using]
The quote library helps you evaluate competing quotes for the same narrative purpose. If you have 5 possible quotes for the piece's opening, seeing them together is more useful than finding them scattered across separate source annotations.
The scenario: A nonfiction author is writing a book about a significant corporate fraud case that took place over a decade. She has 3 years of reporting ahead and will accumulate a large research library of court documents, financial records, journalistic sources, and interview research.
Library structure created before reporting begins:
Primary Collection: "Book: [Title]" Sub-Collections:
Tag scheme established:
By time period: early-phase mid-phase resolution-phase (periods in the fraud's timeline)
By character: one tag per major character (character-cfo character-whistleblower)
By document type: court-doc financial-record regulatory-filing news-coverage
By status: verified to-verify used not-used
At 18 months:
Organizational dividend during writing:
Author's observation: "Writing Chapter 4, which covers the investigation, I opened the Chapter 4 sub-Collection and had exactly the sources I needed for that chapter. It took 10 minutes to orient and I was writing. Before I had a system like this, that orientation took 2-3 hours of searching through undifferentiated folders."
A writer's research library serves a different purpose than a scholar's or an analyst's. It serves the story: it provides the facts, quotations, context, and texture that a narrative needs to be accurate, vivid, and credible. Organization that serves the story means organizing by project and narrative structure, tracking what's been used and what needs verification, and maintaining the kind of master source list that keeps a two-year project navigable. A well-organized research library is what allows a writer to start a writing session already knowing where the relevant sources are, what each one contains, and what's still missing — so the work of the session is writing, not searching.
Related reading: Clip Articles for Later Reading.
More WebSnips articles that pair well with this topic.
A guide for educators and course creators on how to organize a growing research library — build a structured teaching resource system for subject matter
A guide for lawyers on how to organize a growing research library — build a structured legal intelligence system for case law developments, regulatory
A guide for marketers on how to organize a growing research library — build a structured marketing intelligence system for competitive ads, campaign
A guide for remote team leads on how to organize a growing research library — build a structured knowledge system for async communication practices
A guide for knowledge workers and consultants on how to organize a growing research library — build a structured system for client intelligence, domain
A guide for PKM and tools enthusiasts on how to organize a growing research library — build a structured web research archive that integrates with your