by Braden Kelley and Art Inteligencia
Ask any leadership team to name a trend shaping their industry, and you’ll get an answer within seconds. Ask them to explain why they believe it’s real, as opposed to something that just happened to come up in three meetings this month, and the room usually goes quiet. Most organizations aren’t short on trends. They’re short on a way to tell which of the dozens of things competing for the label “trend” actually deserve it.
Why this matters more than people think
Every strategic plan I’ve ever reviewed has been shaped, at least in part, by trends nobody rigorously tested. Not because the people building the plan were careless, but because there’s rarely a formal step in the process for testing a trend before acting on it. Something gets mentioned by a well-regarded analyst, or shows up in three unrelated conversations in the same month, and it quietly graduates from “thing I noticed” to “trend we’re planning around” without ever passing through anything that could reasonably be called scrutiny. Get that step wrong at the start of a planning cycle, and everything built on top of it inherits the mistake.
What actually separates a signal from noise
A genuine signal has a few characteristics that noise almost never does, and it’s worth being explicit about them rather than trusting instinct alone.
- It shows up from more than one independent direction. A single source, however credible, is a data point, not a trend. When you start seeing the same underlying shift from unrelated sources — a customer behavior pattern, an unrelated industry’s earnings call, a regulatory conversation, a technology adoption curve — that convergence is a much stronger indicator than any one source repeating itself loudly.
- It has a mechanism, not just a correlation. Noise often sounds like a trend because two things happened around the same time. A real signal comes with an explanation for why it’s happening — an incentive that changed, a cost curve that shifted, a constraint that got removed — not just a coincidence in timing that a confident narrator strung together after the fact.
- It’s sustained, not spiking. A lot of what gets treated as a trend is really just a spike — a burst of attention that fades within a quarter once the news cycle moves on. Real signals tend to persist and, more tellingly, tend to keep showing up even after the initial attention around them fades.
The traps that let noise through anyway
Even knowing these criteria, a few predictable biases let noise slip past them constantly. Recency bias — whatever you read most recently feels more significant than it actually is, purely because it’s fresh. Authority bias — a signal feels more credible because someone senior or well-known repeated it, regardless of whether they did any more rigorous evaluation than anyone else in the room. And the most dangerous one, confirmation bias — signals that happen to support what leadership already wants to believe about the future get waved through with far less scrutiny than signals that would require uncomfortable change. I’ve watched this last one derail more planning cycles than any of the others combined, because it’s the hardest one for a room to catch in itself.
Building a genuine filter, not just a gut check
The fix isn’t more research, exactly — it’s a consistent set of questions applied to every candidate signal before it earns a place in your planning conversation: Where else is this showing up, independently? What’s the actual mechanism driving it, and does that mechanism hold up under a second look? Has it persisted past its first burst of attention? And, the uncomfortable one worth asking every time — would we be this quick to believe it if it pointed toward a future we didn’t want?
This is exactly what FutureSignals™ is built to do
This filtering discipline is the first formal stage of FutureHacking™, and I built a specific component — FutureSignals™ — around exactly this problem: giving a team a structured, repeatable way to gather candidate signals and stress-test them against real criteria, before any of them get promoted into “trend we’re planning around” status. It’s the foundation the rest of the methodology builds on, because every later stage — the trends you map, the futures you build, the roadmap you eventually commit to — is only as good as the signals it started from.
Where to start
The free FutureHacking Signal Picker puts this exact discipline into practice, at no cost, before your next planning cycle — a genuinely useful way to arrive at your next strategy conversation with signals that have actually been tested, rather than whatever happened to come up most recently.
Something new I’m building
I’m also finishing a second tool — the FutureCanvas Picker — that carries a planning team through the full arc in one sitting: from signals, to the trends they suggest, to a genuine set of possible futures, narrowing to your most probable future, and mapping the path to your preferable one. It’s the closest thing I’ve built yet to running a complete FutureHacking™ session on your own.
I’m opening early access to a select group first — strategic planners, CSOs, and leaders actively running planning processes right now — because I want real feedback from people using it under real deadline pressure before it’s available more broadly. If that’s you, and you’d like to be considered for early access, reach out and let me know — I’ll be following up personally with the first few who get in.
Most planning cycles fail long before the strategy gets built. They fail at the moment someone mistakes a spike for a signal, and nobody in the room had a way to catch it.
Image Credits: Gemini
Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.
Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.