Dr. Jonah Tebaa argues that many organizations do not lose value because the original idea was weak. They lose value in the last mile of implementation.
A tool may be purchased. A process may be approved. A pilot may look promising. A launch may be announced. But none of that guarantees that the new way of working has actually become part of daily behavior.
For Dr. Jonah, the important distinction is between availability and implementation. Availability means the system exists. Implementation means people can use it correctly, consistently, and confidently during a normal working day.
That distinction is not only his. The International Labour Organization, writing on artificial intelligence in the world of work, holds that whether adopting a technology ends in automation or in complementing people depends on the centrality of the task, "how the technology is integrated into work processes", and management's intent — the integration, not the purchase, decides the outcome.
That difference matters.
The real test is not the launch meeting. It is a normal Tuesday, when the team is busy, clients or patients are waiting, messages are coming in, and nobody has extra time to interpret a confusing workflow. If a capable employee needs to ask three people what to do next, the implementation still has work to do.
The five last-mile questions
Dr. Jonah’s last-mile framework focuses on five practical questions.
First, who owns the outcome after launch? Many projects have clear ownership during setup, but vague ownership once the system goes live. Without a named owner, adoption drifts and workarounds become normal.
Second, can a busy person use the new process without confusion? A workflow that only makes sense to the project team is not ready for real operations. The last mile requires simple instructions, clear handoffs, and fewer points of interpretation.
Third, did the change remove work, or did it create duplicate work? If teams must use the new tool while still maintaining the old spreadsheet, old approval path, or old reporting habit, the organization has not truly changed. It has added another layer.
Fourth, is there a standard rhythm? A system used only when people remember is fragile. Implementation needs clarity around who checks what, when it is checked, where the work happens, and what happens when something breaks.
Fifth, is there a feedback loop from real users? The people closest to the work usually see the friction first. Their feedback is not a threat to the launch; it is how the implementation becomes stronger.
Shipping exposes strategy
The core idea is simple: shipping exposes strategy, but adoption proves it.
For Dr. Jonah, the last mile is not administrative cleanup. It is where strategy becomes operational reality. The best implementation work may look boring from the outside: ownership, training, measurement, handoffs, and follow-up. But that boring clarity is exactly what allows value to compound.
A launch is visible. Adoption is valuable.
Before calling an initiative complete, leaders should ask whether the new way of working has become ordinary enough to last.
