Action Latency
An organization responds to its existing decision pathways, not to calculated potential.
Good morning. Let’s start this Tuesday together. Because, as always, “It is perfectly possible to be both rational and wrong.”
Cognizant published its “New Work, New World 2026” report today. Headline number: 4.5 trillion dollars in untapped AI productivity potential in the US workplace, available now.
In a board meeting this week, a CFO put that number on the table and asked why the organization wasn’t seeing it. HR got the order to have a plan by next quarter. Nobody asked how the last two promises this size, reskilling in 2023 and the first AI rollouts in 2024, turned out.
How Does It Work?
A report like this calculates potential by measuring what a tool could do, times possible users. What it leaves out is the action infrastructure between tool and outcome: who decides, how fast approvals move, what incentives make a new way of working worth adopting. An organization responds to its existing decision pathways, not to calculated potential.
Why This Is Important?
Boards read this number as a mandate, not a hypothesis. The pressure lands on HR and IT, on a deadline set by the number, not the organization’s actual pace of change. This pattern sank the last two big promises: not because the idea was wrong, but because nobody measured the gap between announcement and capacity.
And Now?
Instead of adopting 4.5 trillion as a target, a CBO would first measure the organization’s action latency: how long it takes to move from a new possibility to real change in daily behavior. Instead of “how do we make sure everyone uses the tool,” the question becomes “which decision rights must change before use is even possible.” That decides whether the number is cited as a win next year, or as one more broken promise.
Core knowledge: A potential number is not a forecast. It describes what could happen if the action infrastructure already existed, which in most organizations it doesn’t.
Measure action latency before adopting a target number.
Audit decision rights, not tool access.
Treat approvals as a bottleneck, not a formality.
Use earlier broken promises as data, not noise.
Where are management decisions made every day that are still based on people acting logically? Where can you be a Chief Behavioral Officer yourself this week?
See you next Tuesday.
If you would like to send us any tips or feedback, please email us at redaktion@cbo.news. Thank you very much.