Innovation debt

Every technology shift has two parts. The first is the wave: the new capability, the products built on it, the companies racing to ship them. The second is the wake: what the wave leaves behind as it moves on. The retraining nobody planned, the professions whose rules changed underneath them, the places the wave never reached at all.

We call the accumulated cost of that wake innovation debt. Technology compounds: each capability becomes the foundation for the next. Adaptation does not. People learn at roughly the speed people have always learned. Professions revise their standards at the pace of committees, and institutions reform at the pace of budgets and elections.

The gap between what machines can suddenly do and what people, professions and institutions are ready for is the debt. Like any debt, it accrues interest. Unlike most debts, nobody signed for it.

The companies that build a wave rarely build for its wake. That is less a moral failing than a matter of incentives. A frontier company is rewarded for pushing capability forward and selling it to the customers most ready to buy. Its attention follows its revenue, which sits at the front of the wave, not with the people working to keep up behind it.

The institutions that might absorb the wake run on slower clocks. A curriculum takes years to rewrite. A professional body updates its guidance after the practice has already moved. A public program needs evidence of a problem before it can fund a response, and by the time the evidence is in, the next shift has begun.

So the cost of adaptation falls between chairs. It is real, but spread across a great many people, each carrying a share too small to organize around and too large to ignore. No balance sheet records it and no quarterly report names it. That is what makes the wake nobody’s job. We founded iSYNCSO in the Netherlands in 2025 to make it somebody’s job.

Innovation debt does not land evenly. It lands hardest on whoever can least afford it: the professional now accountable for work a system produced, the tradesperson whose teachers are retiring, the person who has never had a connection, the builder who shipped a prototype and discovered it had users.

It compounds because each new capability assumes the previous one was absorbed. A tool built for people fluent in software does little for those who never received the first generation of it. A skill not passed on now cannot be passed on later, because the person who held it has gone.

Every unabsorbed wave makes the next one harder to absorb. That is why waiting is not a strategy. A debt left alone does not shrink; it becomes the baseline the next shift is built on.

We go where the challenges land, not where the hype is. The current shift lands in four places, and we have built one division for each.

In knowledge work, there is too much machine. The tools took the labor and left the accountability, and professionals now command systems they were never trained to command. Our division there is Hyves, which is live: an AI go-to-market team for business-to-business companies, built as a layer on the CRM a team already runs.

In the skilled trades, there is too little machine. The work keeps growing while experienced hands retire, and the tools have barely changed in decades. Our division there, Raven, is in the making.

In access, there is no machine at all. By the count of the International Telecommunication Union, about a third of the world is still offline. The Hyve Foundation, which is being built, starts there.

And builders are alone past the demo. Anyone can start now, but the distance between a prototype and a system people depend on is where projects stall. Hangar is taking projects to close that distance.

In practice, building for the wake comes down to a short list of commitments.

People keep the judgment: they decide how far a system may act on its own, and every step it takes is written down where they can see it. Evidence comes before action: a claim that cannot point at its source does not ship. And the user owns the compounding: the value that builds up from using a tool belongs to the people doing the work.

What technology can do only counts if people can reach it, so we judge our work by who can use it. We ship into reality: a tool is finished when it works where the problem lives, not when it demos well. And we announce late, because we would rather describe something that exists than something we hope will.

It also means paying for the work honestly. The wake has never been an attractive market on its own terms, which is part of why nobody builds for it. Hyves is the division that sells, built to fund the rest.

The debt comes due either way. The question is whether anyone works on it first. That is the job we have taken on.