← All issues
Field Notes · Issue 001

McKinsey, State of Organizations 2026 (The Agentic Organization)

Week of June 1 to 5, 2026

This week ran one argument through five lenses. The pattern that keeps appearing is the gap between the legible signal a senior leader is reading and the operating model decision that actually produced it.

Field Notes — June 6, 2026
This week's reading
The Field Note

The week, read against the grain

McKinsey, State of Organizations 2026 (The Agentic Organization)

McKinsey published its State of Organizations 2026 report this past month, and the headline argument is that AI transformation is no longer compatible with the operating model most large companies have been running for the last decade. The report uses the phrase agentic organization for what it says comes next. Cross-functional autonomous teams replacing functional silos. Redesigned incentives. A deliberate orchestration layer that decides which decisions should be made by people, which by AI, and which by the combination.

The argument is right, and it is also late.

The five pieces I published this week are not really five different problems. They are five reads of one problem, which is that organizations keep buying the visible solution to the wrong layer of the system. The leader's town hall does not move the trust number because the trust number is measuring the decision pattern underneath. The Agile-to-AI repetition is not a technology story; it is the same operating model trying to absorb a second tech shift without redesigning. The accountability dashboards do not build accountability because the operating model still rewards the behaviors that filter out hard information.

McKinsey is naming the problem at the corporate-strategy altitude. The leaders who are actually going to move on it are the ones willing to publish, internally, the answer to a question their boards rarely ask: which of our current decision patterns get to keep being made the way they are being made.

If you handed your operating model to an honest auditor next quarter and asked which of its current decision patterns would survive an AI integration, what would they put on the list of things that need to go first?
High Road Conversations
Podcast
High Road Conversations

On Episode 5 of High Road Conversations, Otis Florence tells the story of selling his business at a bus stop in Louisville to a man he assumed was homeless. The man turned out to be a retired executive. The episode reads as a study in what consistency looks like when no one is watching, which is the same pattern this week's articles keep arriving at.

Listen →
Lunch and Build
Skool
Lunch and Build

I don't just talk about Agile and leadership, I put it into practice in my Skool, building and shipping real products with Claude every Thursday at 12:30pm EST.

Join us →
From the book
Agile Sucks!

In Chapter 10 of Agile Sucks! (When You Do It Wrong) by Zac Parker and James Wright, the story of five civilian contractors taking a combat-zone operation from over 800 hostile incidents a month to under 50 in twelve months. The mechanism was distributed accountability made publicly and immediately. It is the cleanest example I have of what an operating model redesign actually looks like at ground level.

Get the book →

Get Field Notes in your inbox.

A short read every Saturday morning. No spam, unsubscribe anytime.

Subscribe