A case for using structured protocols instead of ad-hoc prompts when working with NotebookLM. Protocols differ from prompts by incorporating decision gates (GO/HOLD/NO-GO) that can halt a task entirely, protecting against the cost of getting convincing answers to badly framed questions. A repertoire of 18 named protocols (e.g., Deep Drill, Crucible, Architect, The Refinery) lets users match the right method to the task type rather than improvising each time. Key ideas include defining a 'protected zone' where the user must think before the tool intervenes, and extracting reusable rules from each session so the system compounds over time.
Table of contents
A Protocol Begins With a Decision, Not a CommandThe Repertoire Beats the TrickThe Protected ZoneGet Mihailo Zoin’s stories in your inboxWork That Doesn’t Get Thrown AwayWhy This WorksIt’s Not About the Tool139 Impressions