signal-first-researchlisted

# Signal-First Research Most "stay current" workflows fail in one of two directions: - **Volume bias.** You wire up ten sources, aggregate everything, and trust yourself to skim. Within weeks the backlog outruns your reading time; the system has become a guilt queue. The filter lives inside your head and degrades on tired days. - **False-abstinence.** You give up on breadth entirely and read nothing, because sorting what matters feels more expensive than ignoring everything. You miss things you would have acted on. A signal-first Research workflow refuses both. It searches widely — *no* source is excluded upfront — but admits each piece of information through a question the reader must answer *before* accepting it: **would this change what I do next?** If the answer is no, the filter drops the item at intake, not at read-time. This skill is the design pattern for that filter, plus examples of three ways to shape it and a diagnostic checklist for spotting filters that have quietly broken. --- ## The core rule: define the signal before the search Most research workflows collapse because the signal is defined *after* the search — "I'll know it when I see it." The volume of "maybes" then dominates the volume of "yeses," and the reader burns judgment budget classifying things they could have skipped. The reversal: 1. **Name the next action** the research is meant to inform. "I am going to decide X this week" / "I want to spot weekly shifts in topic Y" / "I need to know wh