Industry Playbooks
A note-taking system for authors must capture research insights with citations, interview observations with attribution, idea fragments with context, and writing assets across projects — building the documented foundation that makes books credible, writing faster, and a writing career compounding.
Nonfiction credibility rests on something an author can usually only half-remember: exactly where a fact came from. Two hundred pages into a manuscript, an author writes that giving people more choices makes them less likely to choose, and less satisfied when they do. She knows this is the Iyengar and Lepper jam study, or maybe the Schwartz paradox-of-choice work — she's encountered the finding in half a dozen books and can't say which one has the specific number she needs for this sentence.
She searches her notes for "Sheena Iyengar" and gets six results, none with the statistic, scattered across three different highlighting apps that don't talk to each other. Finding the original journal article costs her ninety minutes she didn't plan to spend.
A note-taking system for authors is the discipline that prevents that search — capturing research insights with their sources, interview observations with attribution, and idea fragments with enough context to be usable, all in one retrievable system rather than three disconnected ones.
Research notes connected to sources: Not "someone found that choice overload reduces satisfaction" but "Iyengar & Lepper (2000), Journal of Personality and Social Psychology — in the jam experiment, customers shown 24 varieties were 10 times less likely to purchase than those shown 6. p. 995-1006." The citation is what makes the note retrievable and the claim credible.
Interview notes with attribution clarity: On-record vs. background vs. off-record, documented at the interview level, is the legal and ethical infrastructure of nonfiction. Notes that don't document attribution status create risk when the book is published.
Ideas with enough context to reconstruct: "Good chapter idea" is an idea you'll never recover. "Chapter idea: the measurement problem — we can't measure remote work productivity without the presence proxy, so managers are uncomfortable not because of the work but because of the measurement" is recoverable.
Writing assets organized for reuse: Cut passages, abandoned chapters, strong paragraphs that went in the wrong book — archived and retrievable by theme, these are the source of future work.
For every book, article, study, or data source that informs your work:
Research note format:
The most important discipline: Write the citation FIRST. Before you write a single word about what you learned, write where you learned it. This is the reversal of how most people take notes — they capture the insight and forget to note the source. This single habit prevents 90% of fact-checking emergencies.
Verbatim vs. paraphrase — mark clearly: For any text that may end up quoted in the book, copy it exactly and mark it with quotation marks. Your paraphrase goes separately, without quotation marks. Confusing your own words with source words produces plagiarism — unintentionally but consequentially.
For conversations with research subjects, experts, and practitioners:
Before the interview:
During the interview:
After the interview (within 48 hours):
The attribution annotation: At the top of every interview record, clearly note the attribution status:
The ideas that arrive unbidden — in the shower, between books, at 3am:
Idea capture requirements:
What to capture:
Processing discipline: A weekly review of idea captures — what's worth developing? what needs to move to active research? what was a passing thought, not a real insight? — converts a capture system from an idea graveyard to a content pipeline.
Cut material as archived fragments: When you cut a passage from a draft, don't just delete it. Move it to a "Cut Material — [Theme]" file. Strong passages cut from one project frequently belong in another; archived by theme, they're recoverable.
For long-form projects (books), a running meta-note captures the project's evolution:
Project log:
This running log is the thinking record — not the research, not the draft, but the author's developing understanding of what the book is and what it needs.
| Context | Tool | Notes |
|---|---|---|
| Research notes | Notion or Obsidian | Topic-organized; searchable; linked |
| Source citations | Zotero | Separate from notes but linked |
| Interview notes | Notion + Otter.ai | Notes + transcript backup |
| Mobile idea capture | Bear / Apple Notes | Quick; syncs; reviewed weekly |
| Writing assets | Scrivener (Research folder) | Organized by project and theme |
| Web source capture | WebSnips | Clip with date and URL |
WebSnips for author note-taking: Web-based research sources need to be captured with the same source rigor as books and journal articles. A specific government data page, a specific journalist's investigation, a specific organizational report — these sources can change or disappear between research and publication. WebSnips captures specific pages with date and source URL. The clip becomes the retrievable source for the note, answering the fact-checker's "where did you find this?" with evidence rather than memory.
An author, Daniel Park, is writing a book on the history and future of urban public libraries. He's been developing a note-taking system he'll use for a 3-year project:
Research note:
Source: Pettigrew, K. E. (1999). "Waiting for chiropody: Contextual results from an ethnographic study of the information behaviour among attendees at community clinics." Information Processing & Management, 35(6), 801-817.
Key finding: People who visit community service locations (including libraries) often receive information incidentally — not by seeking it out, but through ambient proximity to others seeking it or offering it. Pettigrew calls this "information grounds." Libraries function as information grounds beyond their explicit information services.
My interpretation: This is the counter-argument to the "libraries are just book warehouses" view. The social function — information grounds — is what explains why libraries in disadvantaged communities have dramatically higher per-patron visit rates than those in affluent communities. The information ground function is more valuable where ambient social information is scarcer.
Connects to: Chapter 3 (social function of libraries); contrasts with the "libraries = information access" frame that focuses on collections
Questions raised: What's the current evidence for information grounds in public libraries post-2000? Has the concept been updated? Who has built on Pettigrew's work?
Tags: information-grounds, social-function, libraries-theory, Chapter-3
Interview note:
Subject: Patricia Johnson, Head Librarian, Parkside Public Library
Date: October 12, 2026
Setting: In-person at the branch; recorded (permission confirmed)
Attribution: ON-RECORD; name and title may be used; direct quotes permitted
Near-verbatim quote: "We have people who come in every day and don't use a single book or computer. They sit, they talk to people, sometimes they sleep. We're the only warm, safe space in 6 blocks that they can enter for free without buying anything. You can call that a library or you can call that a public living room."
Context: Patricia said this in response to my question about whether the library's role had changed with internet access. She pushed back on the premise that the internet changed the library's fundamental function.
My note: Strong quote for opening the chapter on the social function. The "public living room" framing is exactly the information grounds concept described in practitioner terms.
Follow-up: Ask Patricia if she'd be willing to let me spend a morning observing — I want to see the information grounds dynamic in practice, not just hear about it.
Idea capture:
Date: October 14, 2026 (train home from the library)
Idea: Opening of Chapter 1 — open with the statistic about what percentage of Americans say the public library is "important" to them and their community (it's over 90% consistently) vs. what percentage actually visit (somewhere around 50%). This gap — between what we believe about libraries and how we use them — is the book's central tension.
Connection: I know the Pew Research data on this; I need to find the most recent numbers; also find international comparisons for UK, Netherlands (both have strong library systems I'm covering)
Status: Strong hook — add to Chapter 1 outline; find the data
Source quotation and accuracy: Quoting a source requires accuracy — the source said what you claim they said, in the context you imply they said it. Misquotation, quote manipulation (assembling separate statements into one), or context distortion are journalism ethics violations that can result in legal liability as well.
Interview recordings: Audio recordings made for research purposes are often kept as backup verification for any quote attribution disputes. Some authors retain recordings for a defined period post-publication; some retain indefinitely. Know your publisher's guidance and consider the applicable retention policy.
Privacy for interview subjects: Interview subjects who provide sensitive information about themselves or others may have privacy expectations beyond what they explicitly articulate. The author's professional judgment about what privacy interests are implicated — and whether publication serves a purpose that outweighs those interests — is an ongoing ethical responsibility, not just a consent-and-proceed process.
Mistake 1: Citation at the end instead of the beginning. Writing the insight before writing the source is how citation notes end up missing their source. Write the citation first.
Mistake 2: Verbatim and paraphrase not distinguished. A paraphrase you wrote without quotation marks, in your notes, six months ago, may look like your original words when you return to it in the draft. Mark every verbatim passage clearly — in the notes, not just in the draft.
Mistake 3: Interview notes without attribution documentation. A set of interview notes without "on-record" or "background" marking creates risk when you use the material. Document attribution status at the top of every interview record, before you capture any content.
Mistake 4: Ideas captured without context. "Great chapter idea" — what chapter? what idea? Ideas captured without enough context to reconstruct them are ideas that evaporate. A sentence of context is usually enough to recover the insight; a word is rarely enough.
A note-taking system for authors is what converts years of reading and research into a retrievable foundation rather than a mass of highlights and memories. The author who writes citations before insights, marks verbatim clearly, documents interview attribution in real time, captures ideas with enough context to recover them, and archives cut material by theme is building a practice that makes each book faster and better than the last. The notes don't just support the book being written — they compound across a writing career.
To go deeper, check out Web Clipping for Research Papers.
More WebSnips articles that pair well with this topic.
AI knowledge work for authors is transforming research synthesis, draft structure development, fact-checking assistance, and content repurposing — enabling authors to write more thoroughly researched books faster without replacing the human judgment that makes books worth reading.
Knowledge management for authors is the practice of organizing research, interview notes, source materials, ideas, and writing assets — enabling authors to write books and articles grounded in evidence, with sources retrievable on demand and ideas that compound across projects.
Research workflows for authors are the structured processes for source discovery, interview research, expert consultation, fact verification, and synthesis — enabling authors to write books grounded in evidence, with claims that survive the fact-checker and sources that are retrievable on demand.
AI research for authors: where AI tools provide genuine leverage in book research and writing (literature orientation, structural drafting, administrative tasks), where they introduce quality risk for books (factual claims, primary source interpretation, historical specificity, argument originality), and the professional disciplines that maintain the intellectual and factual quality that book publishing requires.
Building a searchable knowledge base for authors: the four knowledge domains that long-form writing generates (research and source knowledge, idea and argument development, craft and technique knowledge, and professional and career knowledge), the organization structures that make each domain retrievable across long project timelines, and the maintenance practices that keep the KB useful as projects evolve and professional expertise develops.
Building a second brain as an author: the five knowledge components that compound across a writing career (intellectual preoccupations, craft expertise, research and argument development, professional practice wisdom, and reading intelligence), the organization that makes each retrievable during project work, and the capture habits that convert daily reading and writing work into compounding creative and professional expertise.