The Unfinished World
Most transformation programs are built to end. Iqbal believed the universe itself was never finished — and that belief is the one most enterprises need and least possess.
By Rahul Jindal · 5 min read · May 18, 2026
“This universe is, perhaps, still unfinished — for the call of 'Be, and it is' keeps sounding, moment after moment.”
Muhammad Iqbal · Bal-e-Jibril, 1935
Read this couplet on Iqbal for All →
Ask a transformation office when the transformation ends and you will get a date — a program close, a steering committee dissolved, a victory memo. The date is the problem. It tells everyone, correctly, that there is a finish line, and that on the far side of it the work goes back to being whatever it was before.
Iqbal looked at the cosmos and saw the opposite. The universe, he wrote, is perhaps still unfinished — because the command that brings things into being has not stopped sounding. Creation is not an event in the past tense. It is happening, damadam, moment after moment, now. It was the central conviction of his philosophy, and it is the one an enterprise in the AI era most needs to borrow.
Why the finish line is the failure
The instinct to bound a transformation is reasonable. Budgets need an end. Executives need a win to point at. So the work is shaped into a program: a start, a middle, a close. And the moment it closes, the organization does the thing it was always going to do — it exhales, and it stops.
This was survivable when the thing being absorbed was stable. You could digitize, declare victory, and coast, because the digital tools you installed one year were roughly the digital tools you had three years later. AI does not grant that. The capability is moving faster than your last program plan, and it will be moving faster still when the steering committee disbands. A transformation that ends has simply chosen the date on which it begins to fall behind.
“A transformation that ends has simply chosen the date on which it begins to fall behind.”
The unfinished operating model
The alternative is not a longer program. It is a different object. Iqbal's unfinished universe is not chaos — it is a structure that includes its own continuation. The work of becoming is built into what the thing is.
For an enterprise this means the transformation does not graduate into a steady state; the new steady state is continuous transformation. The capability you build is not 'we adopted AI' but 'we metabolize change as a standing function.' That is a harder thing to build and a far better thing to own, because it is the only version that does not expire.
The tell is in the grammar. When a leader says the company has been transformed — past tense — they have described a monument. When they say the company keeps transforming — present continuous — they have described an institution. Iqbal would have heard the difference instantly. Sada-e-kun-fayakun: the call is still sounding. Present tense. Always.
What to do with this
Concretely: stop chartering transformations that close. Charter a function that does not. Move the budget from program to capability. Replace the victory memo — quietly one of the most damaging artifacts in change management — with a standing cadence that assumes next year's operating model is not yet built, because it is not.
And retire the word done. In a finished universe it is a reward. In an unfinished one it is the first symptom of decline.
A transformation with a finish line is a project. A transformation without one is an operating model. The enterprises that compound treat 'done' as the most dangerous word in the room.