Writing

Adoption is a decision. Proficiency is a system.

Kristian Kabashi · Zürich · 2 July 2026

Two large May 2026 studies agree on where AI value gets stuck, and it is not in your employees.

In May 2026, IBM's Institute for Business Value published its 2026 CEO study: 2,000 CEOs across 33 markets, surveyed with Oxford Economics. 83 percent of them said AI success depends more on people's adoption than on the technology itself. The same week, Microsoft's 2026 Work Trend Index put a sharper number on the same idea: organizational factors account for more than twice the reported AI impact of individual factors, 67 percent versus 32. Only 19 percent of AI users sit in the zone where personal capability and organizational readiness reinforce each other.

Read those two findings together and a familiar corporate playbook falls apart. Most companies still treat AI capability as an individual virtue: run a training, appoint champions, license a copilot, wait. Usage goes up. Impact does not. Then leadership concludes the workforce is not ready, and buys more training.

Proficiency is not a talent. It is a property of the system.

A person can only direct as much work as the system around them allows. If delegation to a machine is informal, every handoff is a personal risk. If nobody owns the quality of machine output, review becomes theater. If job descriptions still describe execution, people get evaluated on exactly the work they are supposed to be handing off. None of that is fixed by another prompt workshop.

This is the core of the Framework I have been writing about since The Blank Collar Equation: the worker of the AI era stops executing routine process and starts directing it. The more process you can hand to machines, the more headroom you get for vision, judgment and the human interface. But process can only be handed over where the organization has made it explicit, and direction only counts where the organization treats it as real work.

IBM's own numbers say the redesign is the difference. Organizations in the study that redesigned five core areas (technology, finance, HR, operations and cross-functional collaboration) were four times more likely to have delivered on business objectives. And the workforce math is not small: CEOs expect 29 percent of employees to need reskilling for a different role between 2026 and 2028, and 53 percent to need upskilling to do their current role well.

What I would do as an operator

  • Rewrite roles around directed outcomes. If a role description still lists tasks a machine now does, the description is the blocker, not the person.
  • Make delegation legible. Keep a written register of what agents own, what people own, and who reviews what. Informal delegation is where accountability goes to die.
  • Measure directed output, not tool logins. Adoption dashboards count seats. The business runs on outcomes per person, cycle time and error rates.

Adoption you can mandate by Friday. Proficiency you have to build, and it is built into the operating model, not into the people. The studies just put numbers on something operators already feel: the ceiling is the system.

Sources

More essays: kristiankabashi.com/writing · The practice: theblankcollar.com