by Braden Kelley and Art Inteligencia

Every CSO I talk to agrees, without hesitation, that strategic foresight matters. Almost none of them have a foresight team. That’s not a contradiction — it’s a budget reality. Foresight sounds like a function you’d staff if you had unlimited headcount: a few analysts, a research subscription or two, maybe a futurist on retainer. Most organizations don’t have that, and most CSOs I’ve worked with have quietly concluded that means real foresight is out of reach for now. It isn’t. What’s actually out of reach is foresight-as-a-department. Foresight-as-a-method is a completely different proposition, and it’s one you can run yourself, starting with your next planning cycle.

The department was never the point

Here’s the thing dedicated foresight teams are actually good at: running a repeatable process for collecting signals, testing them against trends, and building out possible futures in a structured way. That process is genuinely valuable. The team that runs it is not the value itself — it’s just one way of executing the process, and an expensive one. If you can borrow the process without hiring the department, you get most of the value at a fraction of the cost, and you get it fast enough to actually use before your next planning cycle rather than after a hiring search.

What the process actually needs to include

Any real foresight process, department or no department, has to move through the same core stages, whether or not anyone calls it that explicitly:

Signals. Real, specific, early evidence of change — not opinions about the future, not trade press headlines repackaged as insight, but the actual raw material: a shift in customer behavior, a regulatory rumbling, a technology crossing from experimental to viable. Most organizations are already collecting fragments of this informally, scattered across different people’s inboxes and conference notes. The first job of a lightweight foresight process is simply gathering it into one place and being disciplined about separating real signal from noise.

Trends. What do multiple signals, taken together, actually suggest is happening? This is where a lot of informal foresight efforts quietly fail, because it’s tempting to jump straight from one interesting signal to a confident prediction. A trend needs more than one data point behind it, and it needs the room to genuinely disagree about what it means before converging.

Possible futures. Not one future — several, genuinely held as plausible at the same time, even when they contradict each other. This is the step organizations without a formal process almost never do at all, because it feels inefficient to build out three futures when you’re only going to act on one. It isn’t inefficient. It’s the entire point — holding multiple futures seriously is what keeps you from betting everything on the first plausible story anyone tells convincingly in the room.

The probable future, and the preferable one. Eventually you do have to narrow down — most organizations can’t operate against three futures simultaneously forever. But narrowing to your probable future is only half the job. The other half is identifying your preferable future and building a deliberate path toward it, rather than just passively waiting to see which future arrives and reacting once it does.

Building this into your existing calendar, not a new one

You don’t need a standing foresight function to run this. You need a recurring slot on a calendar you already have. Most CSOs I’ve worked with fold this into the run-up to quarterly business reviews as a lightweight signal-check, and run the fuller version — trends through preferable future — as a structured session ahead of annual planning. The key discipline is treating it as a process with defined inputs and outputs, not an open-ended brainstorm, because open-ended brainstorms are exactly what devolves into “opinions about the future” instead of genuine foresight work.

Who actually needs to be in the room

Resist the temptation to run this solo, or with just your immediate strategy team. The signals worth catching often live with the people furthest from the strategy function — sales hearing objections in real deals, support seeing friction firsthand, product watching usage patterns shift. A cross-functional group, even a small one, catches signals a strategy team working in isolation will miss entirely, and it builds organizational buy-in for whatever future the group eventually converges on, which matters enormously when it’s time to actually execute against it.

This is exactly what FutureHacking™ was built to be

I built FutureHacking™ to be precisely this — a structured, visual, collaborative methodology that takes a cross-functional team through signals, trends, possible futures, your probable future, and a real path to your preferable one, without requiring a dedicated foresight function to run it. FutureHacking™ is the art and science of getting to the future first, and it’s built for CSOs running lean, not for organizations with a research budget to spare.

Where to start

The free FutureHacking Signal Picker is the fastest way to run the first stage of this process before your next planning cycle — identifying and prioritizing real signals, at no cost, with no department required.

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 to running an entire FutureHacking™ session on your own.

I’m opening early access to a select group first — CSOs and strategic planners 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.

You don’t need a department to see what’s coming. You need a process, run consistently, with the discipline to hold more than one future until you’ve genuinely earned the right to narrow it down.

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.