Skip to main content

Trend Spotting

Which changing force could alter a workflow you can observe, and what would prove that it matters to a beneficiary?

Trend spotting is a research habit, not an opportunity verdict. It turns a dated signal into a bounded observation question. A trend earns attention; only buyer behaviour can earn commitment.

Inputs​

  • One domain, workflow, or community you can access.
  • A dated source describing a change in behaviour, cost, regulation, capability, distribution, or coordination.
  • Your access limits, time budget, and claim-maturity vocabulary.

Steps​

  1. Capture the force. Record the source, publication date, observed claim, forecast, and provenance. Output: one source record.
  2. Separate claim maturity. Mark each statement observed, inferred, or hypothesized. Output: a claim ledger.
  3. Cross it with a workflow. Ask what existing task, workaround, delay, risk, or spending might change. Output: one candidate intersection.
  4. Name the beneficiary. State who would notice the change and the exact struggling moment. Output: a buyer observation question.
  5. Seek contrary evidence. Name what would show that the signal is fashion, vendor promotion, or irrelevant to this workflow. Output: a falsifier.
  6. Route the result. Use the Opportunity Scanner for comparable candidates, then the Opportunity Atlas only after behaviour and evidence survive. Output: observe, park, or discard.

Output​

Force:
Source and date:
Observed claim:
Forecast or assumption:
Affected workflow:
Named beneficiary and struggling moment:
Contrary evidence:
Cheapest observation:
Disposition: OBSERVE | PARK | DISCARD

Checks​

  • The source is dated and its incentives are visible.
  • A forecast is not restated as an observation.
  • The beneficiary is reachable without building first.
  • At least one result could make the signal irrelevant.
  • The next action gathers evidence rather than amplifying attention.

Failure Modes​

  • Feed capture — novelty and repetition are mistaken for importance.
  • Vendor proof — a seller's launch proves only that a seller launched.
  • Market-size theatre — a large category hides the missing buyer moment.
  • Solution anchoring — a product is chosen before the workflow is observed.
  • Trend permanence — a temporary spike is treated as a durable force.

Proof Of Done​

The record has a dated source, explicit maturity, named beneficiary, affected workflow, falsifier, and one cheapest observation. A second reader can explain why the signal is being observed without claiming that demand exists.

Action Ladder​

  1. Do it now — choose one signal from your current feed and write the eight-line output above.
  2. Do it this week — observe one affected workflow and record the workaround or absence of one.
  3. Continue only if evidence survives — compare it through the Opportunity Scanner.

Changes my mind: Direct observation repeatedly shows that this source set predicts no changed beneficiary behaviour.

Context​

  • depends-on Principles — keep signal interpretation anchored to stable decision tests.
  • applies-to Opportunity Scanner — turn qualified forces into comparable candidate intersections.
  • pairs-with Opportunity Atlas — preserve evidence, contradictions, residue, and reversible tests for surviving wedges.
  • pairs-with Performance — define the observation that would distinguish a useful signal from attention.
  • pairs-with Reality — compare trend interpretation with observable conditions.

Questions​

Next question: Which signal in your current feed changes an observable workflow, and which only changes what people are talking about?

  • What direct observation would falsify the claimed change?