Future state is the past with better tools. Future-casing is the business you haven’t built yet — and you can tell the difference before you spend another dollar.
Somewhere in your organization right now, there’s a roadmap with a title slide, an owner, and probably a color-coded status column that has been “yellow” since roughly the dawn of enterprise project tracking. On that roadmap is a list of what most people call current-state use cases.
I’d like to reframe what that list really is.
Every current-state use case listed is the organization admitting — in writing and with a budget attached — that it’s already behind. That’s not an insult, it’s just the mechanism. You don’t put something on a roadmap because you’re ahead of it. You put it there because a gap opened up, someone noticed, and now you’re paying to close it.
That work may be necessary, and I’m not suggesting anyone ignore it. I genuinely enjoy operational reality as much as the next overly caffeinated data person with trust issues; somebody has to keep the lights on, patch the leaks, and make the quarterly numbers. I’ve spent a career in those rooms, and I respect the people who live there.
But a backlog of confessions is not a strategy, it’s a guilty plea with a project plan.
The Math on Catching Up Never Worked
Here’s the part nobody wants to hear. The moment you finish closing yesterday’s gap, the gap has already moved (again). The capability you spent two quarters shipping is now table stakes, while the competitor you were chasing has spent those same two quarters defining an operating model you haven’t even scoped yet.
The math on catch-up never actually worked, we just got really good at pretending it did because, for a while, the pretending was survivable. Everyone was moving at roughly the same speed, so being a step behind felt like a healthy jog rather than a slow-motion fall.
AI, innovation, and the futures movement changed the speed, it didn’t invent the problem, it just made it impossible to hide. When the frontier moves this fast, a strategy built entirely on catching up is really a strategy built to lose politely.
The Word “Future” Is Doing Two Opposite Jobs
Walk into almost any transformation conversation and you’ll hear the word “future” tossed around like confetti. The trouble is that it’s doing double duty, and the two meanings point in completely opposite directions:
- Current state asks: how do we fix what we have?
- Future state asks: how do we improve what we have?
The first two are renovations but nobody is talking future casing. What would we build if we didn’t already have this? That’s the missing question. The one almost nobody puts on the agenda and the question that changes everything.
Future state is current state with better tools: same org, same processes, same assumptions, just shinier. It is a more expensive way to preserve the shape of the past. You migrate the platform, modernize the stack, buy the shiny thing, and at the end of it the business runs exactly the way it always did, only now with a bigger invoice and a nicer dashboard sitting on top of the same tired decisions.
Future case is the business you haven’t built yet. The one designed to learn as it operates rather than merely document what already happened. It is built around where the work is going, not where it has always been. It asks what the business would look like if intelligence had been designed into the work from the beginning. What decisions would move earlier? What processes would disappear entirely? What data would no longer need to be chased, reconciled, translated, and defended because the business was built to make sense of itself as it runs?
One paves the cowpaths. The other asks whether cows are still the right animal.
Most transformation never asks the question It takes the trails we’ve worn into the grass over 20 years of habit and lays fresh asphalt right on top: smoother, faster, still the same path, and still going to the same place. Future-casing asks the harder question, not “how do we pave this better,” but whether cows are still the right animal to be walking here at all.
That’s not a rhetorical flourish; it’s the whole game. The organizations that survive the next wave of disruption won’t be the ones with the best current stack. They’ll be the ones whose strategy doesn’t depend on the stack at all, because you don’t get insulated from what’s coming by buying better tools. You get insulated by not needing the ones you bought to begin with.
This Isn’t a Strategy Problem. It’s a Courage Problem.
Here’s the part most leaders won’t say out loud, defaulting to current-state use cases isn’t really a strategy problem. It’s a curiosity problem, and underneath the curiosity is the harder thing to name… courage.
Future-casing requires someone to stand up in the steering committee, the one with the yellow status column, and say, “Half of what we do today won’t exist in five years, and we should stop funding it now.” That sentence is expensive because it threatens the very thing the meeting was built to protect. It asks people to defund their own comfort, which in some rooms ends careers and, in the good ones, defines them. Nobody wants to be that person. Be that person.
We Start Where Most Firms Skip
This is exactly why we start our most important modernization, AI, data, and technology work with a step most firms skip entirely. Most companies begin by asking what can technology improve; we start by asking what the future will actually require. Before anyone invests in tools, pilots, or automation, leaders need clarity on which capabilities, decisions, and ways of working will create value in the years ahead, not just which fires are burning today.
We call it Opportunity Future-Casing, and it’s powered by our Foresight & Futures discipline (more on that here). It is the difference between an AI, data, or technology strategy that gets overtaken by the technology and one that evolves with it, it’s how you introduce autonomy on purpose, build governance in from the beginning instead of bolting it on after something breaks, and replace inherited assumptions with what’s now genuinely possible.
Related Read: Foresight & Futures Equips Companies to Thrive Beyond Today’s Horizon
Your competitors are optimizing for the present, but the winners are already operating in a future the rest of the market can’t see yet. Done right, investments in technology don’t just make you faster; they let you see around corners and leapfrog the field while everyone else is still running pilots.
So before you approve another current-state use case, ask the question that isn’t on the slide… if we were building this business today, knowing everything we now know, would we build it this way at all?
If the honest answer is no, then you don’t have a roadmap; you have a confession. And a confession is a fine place to start, as long as you don’t mistake it for a strategy.
Stay curious my friends.
Ready to stop funding yesterday’s roadmap. Learn how Opportunity Future-Casing can help you identify what the future will require — and build for it before your competitors do. Dive deeper here.