← The Research Station ~ dish 01 of 10 · the research station

News and Signal Monitoring

The operator gets buried in alerts because signal and noise aren't separated upfront. The station monitors news, sources, and people the Chef cares about and produces a briefing in a format the Chef actually reads. The leverage is guardrails written before deployment. Define what counts as signal. Everything else is noise.

The job

Right now the operator reads industry newsletters, sets up Google Alerts on competitors, skims LinkedIn for what matters. Sixty percent of that time is noise. A news article about the industry that’s irrelevant to this business. A competitor hiring announcement that doesn’t signal a move you care about. A trending topic that everybody’s talking about but doesn’t change anything.

When the station runs this dish well, a 200-word briefing lands in the operator’s inbox three times a week. The top three things that happened in the market that matter to this business. The source. Why it matters. What it might mean. The operator reads it in five minutes. They act on one item or they file it. Either way, they’re informed.

The difference between a briefing that gets read and one that gets ignored is simple. The Chef defines what counts as signal before the station ever runs. “New AI tools in our vertical” is signal. “AI in general” is noise. “Competitor hiring our target role” is signal. “Competitor hiring anyone” is noise. Without that filter, the station surfaces 30 things a day and the Chef ignores 29.

The recipe

All seven ingredients still apply. The leverage on this dish is Guardrails (Ingredient #3). The Chef defines what counts as signal. The station filters noise upfront. Without that guardrail, the briefing drowns in irrelevance.

Context matters. The station knows which topics, sources, and people to track. Examples matter. Show the station a briefing you actually read and would act on. That’s the standard. Guardrails matter. You don’t tell the station to find “important news.” You tell the station to find “price changes in our category” or “expansions into adjacent geographies.” Output Over Process matters. You don’t specify how to find the news. You specify the format. Three items. Source. Why it matters. Monday move.

How to build it

  1. List the topics that would change a Monday decision for your business. Five to ten topics. For a local service business, maybe that’s “labor costs in my region,” “customer sentiment shifts,” “competitor expansion,” “regulatory changes.” For a SaaS company, maybe it’s “product category shifts,” “new competitors,” “consolidation signals,” “new funding announcements in adjacent categories.”
  2. List the sources worth tracking. News sites. LinkedIn. Industry analyst firms. Your customers’ industry publications. Not everything. The sources that have signal-to-noise ratio you trust.
  3. List the named competitors and people you track. The three competitors that matter most. The three people in your category whose moves matter.
  4. Define the threshold. What counts as actionable. A competitor price change of what magnitude. A new product launch in what category. A hiring pattern that signals what move. Without this definition, everything lands in the briefing.
  5. Define your output format. Three items per briefing. Or five. Title, source, one paragraph on why it matters. One line on what it might mean. That’s it.
  6. Pull one briefing you actually wrote by hand and would read again. Show the station the format and the signal-to-noise ratio.
  7. Test on a mock run. Have the station scan your sources and topics for the last 48 hours. Does it surface three items that match your signal threshold. Does it skip the noise items. Adjust.
  8. Go live with a weekly cadence first. If the briefing reads useful, add a daily version. If you ignore it, go back and tighten the signal definition.

What breaks it

  • Signal definition is too broad. You tell the station to monitor “industry news.” It surfaces 50 items a week. The Chef reads two and stops. Tighten the definition. “News about customer acquisition costs in our region” is narrower and more useful than “industry news.”
  • Threshold isn’t named. What counts as an actionable competitor move. A 5 percent price change. A new job posting in a role nobody’s hired before. A new customer win in a new segment. Without that rule, the station flags everything and the briefing dies.
  • Sources include low-signal outlets. You add five news aggregators to the monitoring list. Four of them republish the same news as the others, adding noise without signal. Curate your sources. If the source doesn’t have insights the Chef wouldn’t get elsewhere, drop it.
  • Format isn’t standardized. The first briefing has three items. The next one has seven. The one after has two. The Chef never knows what to expect. Stick to the format. Three items. Source. Paragraph. Monday move. Same every time.
  • Feedback loop is silent. The Chef reads the briefing and ignores a category that wasn’t actionable. They never tell the station. The station keeps surfacing it because the feedback died. When the Chef ignores a category consistently, prune it.

When it’s working

At week four, the station surfaces three actionable items per briefing. The Chef reads the briefing every time. Sixty percent of items prompt a decision or a note. The Chef catches competitive moves earlier than they would have otherwise. Customer sentiment shifts show up in the briefing before they show up in revenue.

The signal that the recipe is sharp: the Chef checks the briefing first thing on the briefing day. It’s become part of the weekly rhythm.

Monday Move

List the five topics that would move a Monday decision. List the sources that have signal. Define your threshold. Write one briefing by hand in your format. The station is running by Tuesday.

Dish 1 of 10 on the Research Station. Build-note leverage: Guardrails (Ingredient #3).