AI Guides › Trend Watch
By Nigel Guy · 3 min read
A screenshot circulates: an internal slide, a list of codenames, a supposed timeline for the next model or product. It looks plausible, it's been shared by accounts you recognise, and the details are specific enough to feel real. You start treating it as a preview of what's coming. What you've actually done is accept a document whose origin nobody in the chain can vouch for — because specificity and repetition feel like evidence, and neither of them is.
The rule: before believing any leaked roadmap, ask one question — "Who, specifically, could lose something if this turned out to be false?" If the answer is nobody, weigh it at nearly zero.
Accountability is the thing that separates information from noise. A journalist at an established outlet risks their reputation and their publication's standards process. A company risks its customers' trust when it misleads them. A named individual risks being publicly wrong. An anonymous screenshot passed between accounts risks nothing for anyone — so nothing is holding it to accuracy.
The question doesn't tell you whether the leak is true. It tells you how much the claim has been tested before it reached you.
Trace the claim back as far as you can, and note what you find at each step.
Score it roughly: a named, accountable origin with corroboration is worth noting. Anything less is a rumour — handle it with "The Difference Between A Rumour And A Reason To Plan Ahead."
These don't prove a leak is fake, but they should lower your confidence further:
Skip the forensic analysis of fonts and slide templates that often follows a leak; it's absorbing and rarely conclusive. Skip rearranging any plans around leaked timelines. And skip forwarding it, even with "not sure if true" attached — the caveat gets dropped the moment someone else shares it.