The Future State Trap

Published: June 2026 | OpenNova

There is a meeting that happens in a lot of organizations right now. A roadmap is on the screen. The dates are set, and most of the room is nodding. One person, usually whoever will actually have to build the thing, is quietly doing the math and already knows the date is wrong. They don’t say it. In that room, saying it is expensive.

We see some version of that meeting constantly. It is where the gap between the conversation and the reality actually lives, and it tells you more than any survey does.

The surveys do confirm the gap is widespread. Accenture’s 2026 Pulse of Change research found a 24-point spread between the C-suite expecting significantly elevated change this year and the employees who are supposed to deliver it. But the number isn’t the part that matters. What matters is what happens inside that one meeting, and why the person who knows stays quiet.

The status deck and the people who know better

The status deck says the foundation is ready. The team doing the work knows it isn’t. Both are true at the same time. Often the migration still gets reported as on track anyway, sometimes because the date was committed a year ago, in a different room, by people who needed it to be true to get it funded.

That isn’t dishonesty. It is how the two halves of an organization are built to run. The planning side is rewarded for confidence, so the person with the boldest credible roadmap wins the budget. The delivery side is rewarded for what actually ships. Those are different people, measured on different things, and they are rarely in the same meeting at the same time. The roadmap travels upward as a set of dates. The reality stays down where the work is.

The same thing is happening with AI right now. Most large organizations have approved the spend. Far fewer can point to what it changed. The expectation that the investment would pay off arrived the day it was approved. The harder question, what problem it was actually solving and how anyone would know it worked, got pushed to later, and usually to no one in particular.

What gets optimized

So the gap doesn’t get closed. It gets absorbed, by the people close enough to the work to see it, who have learned that naming it in the wrong room costs them something.

Over time an organization can get very good at the visible half of this: the roadmaps, the updates, the confident forecasts. Meanwhile the invisible half, whether the thing is actually ready, quietly drifts. Nobody decides to run it that way. It is what you get when one half is rewarded and the other half is assumed.

The leaders who seem to avoid this aren’t moving faster than everyone else. They have usually just made it safe, in the room where the dates get set, for the person doing the math to say what they see. That is a smaller change than it sounds, and a rarer one.

The question

Figuring out where your own organization sits isn’t a question about technology, or speed, or how much you’ve invested. It is simpler than that. In the meeting where the next set of dates gets committed, is the person who has to deliver them actually in the room, and would it cost them anything to tell the truth?

If you already know the answer, you already know how wide your gap is.

OpenNova works directly with technical leaders on the delivery itself, from scoped builds to embedded teams. If what you’re reading connects to something you’re navigating, let’s talk about your project.