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

Industry Trend Synthesis

What's actually shifting in the category beyond the consensus take. Quarterly briefings the Chef would write if they had time. The station synthesizes. The Chef tastes and edits. The leverage is examples and house style. Show the station three of your own takes. The station learns the difference between consensus and crisp.

The job

The industry is shifting. Everybody’s talking about it. The Chef notices the pattern but doesn’t have time to write it up. The team never sees the insight, so they keep operating as if the old rules still apply. By the time the team catches up to the shift, competitors already moved.

When the station runs this dish well, every quarter the Chef gets a three-page synthesis. Here’s what’s shifting. Here’s why it matters to our business. Here’s the bet we should make. The synthesis sounds like the Chef wrote it because the station learned from three past syntheses the Chef actually authored. The team reads it and adjusts strategy.

The difference between research that shapes strategy and research that’s just summarization is voice and judgment. A synthesis that says “everybody’s talking about AI in our category” is true and worthless. A synthesis that says “the category is shifting from outcome-agnostic delivery to outcome-guarantees, which breaks the unit economics of 60 percent of the market” shapes how you think. That’s not a summary. That’s judgment.

The recipe

All seven ingredients still apply. The leverage on this dish is Examples (Ingredient #4) and Training (Ingredient #1). Show the station three takes you’re proud of. How you frame industry shifts. How you distinguish consensus from crisp. The station learns the difference between summarizing the news and synthesizing it.

Context matters. The station knows your industry, your business model, what shifts would actually matter. Examples matter. Three syntheses in your voice are the training set. Training matters. The station learns that your syntheses tell a story, not list facts.

How to build it

  1. Pull three syntheses or strategic insights you’ve written on industry shifts. These should be pieces you’re proud of. Pieces that shaped how your team thinks. Not a news summary. A genuine point of view.
  2. Read them and ask: what makes these yours. Is it the angle. The connections you draw. The bet you call out. Write down the pattern.
  3. Define what counts as an industry shift worth synthesizing. For a home services software company, maybe it’s labor market shifts or customer acquisition cost changes. For a SaaS company, maybe it’s consolidation, new buying committee changes, or go-to-market shifts.
  4. Define your synthesis format. Opening take (two paragraphs, what’s shifting). Why it matters (two paragraphs, how it changes your industry). The bet we should make (one paragraph, the decision this shapes). That’s it.
  5. Create a reading list of sources the station should monitor for shift signals. Industry analyst reports. Customer earnings calls. Hiring patterns across the space. News articles. Not everything, just the sources that consistently have signal.
  6. Test on a mock run. Have the station read the last three months of your reading list and synthesize one shift it found. You read it. Does it sound like you. Does it surface a real shift or a consensus take everyone already knows about. Adjust.
  7. Go live with quarterly cadence. After each synthesis, the Chef reads and edits. The edits teach the station what’s missing. When the station gets to “no edits needed,” the recipe is sharp.

What breaks it

  • Synthesis is just a news summary. The station lists five things happening in the industry. You read it and think “yeah, I already knew that from LinkedIn.” The synthesis isn’t an insight, it’s a news clip. Force the destination. The synthesis should answer “why does this shift matter to us” and “what should we do about it.”
  • Voice drifts away from yours. The station reads your syntheses but writes in LinkedIn voice instead of your voice. The team reads it and thinks “the Chef didn’t write this.” Voice is load-bearing. Show the station more examples. Let the edits teach the pattern. The station’s voice should sound like you.
  • Consensus is mistaken for insight. The station synthesizes “everyone’s talking about AI and it’s a big deal.” True. Consensus. Not an insight. Define what an insight looks like in your industry. An insight names the specific way the shift breaks economics or changes buyer behavior.
  • The shift is too small. The station identifies a minor trend that’s interesting but won’t change strategy. The team reads it and ignores it because it’s not actionable. Focus on major shifts. Quarterly is the right cadence because true shifts take time to move. Minor shifts can wait.
  • Feedback loop dies. After the Chef reads the synthesis, they have edits or thoughts on why the insight matters. The Chef never tells the station. The next synthesis has the same gaps because the feedback died. When you edit, explain what’s missing so the station can learn.

When it’s working

At week four of each quarter, the Chef reviews the latest industry synthesis. The synthesis surfaces a shift the team wasn’t talking about yet. The synthesis sounds like the Chef wrote it. The team reads it and strategy discussions change because the insight shaped thinking. The business makes a bet based on the synthesis because the shift felt real and the reasoning felt sound.

The signal that the recipe is sharp: the Chef references the synthesis in a strategic decision to explain why the business is moving in a direction.

Monday Move

Pull three syntheses or strategic takes you’ve written on industry shifts. Read them and articulate what makes them yours (angle, connections, bets). Define the shifts worth synthesizing. Create your synthesis format. The station is running this quarter.

Dish 6 of 10 on the Research Station. Build-note leverage: Examples (Ingredient #4) and Training (Ingredient #1).