Block's "AI-Native Org" and What It Means for Mid-Market Leaders
Published: 2026-04-21 · Last updated: 2026-04-15
Freshness note: Reflects Block's 2026 public writing and media coverage framing AI as a catalyst for flatter org structures and fewer management layers.
By Roy Gatling (RMG Associates)
AI is not just changing how work gets done. It is changing how work gets coordinated.
Block's recent "from hierarchy to intelligence" thesis is a signal that the next productivity wave is less about automating tasks and more about compressing management layers that exist to move context and decisions around.
For mid-market firms, here is the question: If AI lowers the cost of coordination, should you redesign roles, incentives, and decision rights now, or will you carry organizational drag into a faster moving competitive cycle?
What did Block actually say, and why should a mid-market CEO care?
Block argues companies move fast or slow based on information flow, and that hierarchy and middle management can impede that flow.
Public coverage of Dorsey's comments and related reporting frames AI as a driver for a flatter, more directly accountable structure, including concepts like player-coaches and reduced permanent middle-management layers.
A mid-market CEO should care for one reason: the mid-market already runs thin management capacity. If AI makes coordination cheaper, competitors will:
- - run smaller teams with the same output
- - make decisions faster with fewer meetings
- - ship changes in weeks instead of quarters
The compounding effect is strategic, not operational.
What is the core idea: hierarchy is an information-routing system?
In most firms, hierarchy exists to solve three problems:
- - Context distribution: getting the right information to the right person
- - Decision routing: determining who gets to decide and when
- - Work synchronization: coordinating dependencies across functions
Block's implied bet is that AI can do more of context distribution and synchronization, and make decision routing easier by clarifying ownership and surfacing tradeoffs faster.
For executives, this is the key reframing:
- - If coordination costs drop, the org chart becomes less about control and more about throughput.
- - If throughput becomes the differentiator, you want fewer layers between signal and action.
What changes first in the next 12-18 months (and what does not)?
What changes first
- - Managers become operators of throughput, not supervisors of tasks.
- - Decision rights get tighter with explicit one-owner accountability.
- - Meeting volume becomes a visible tax as AI handles routine coordination.
What does not change
- - Regulated work still needs controls in finance, security, compliance, and privacy.
- - Talent development still requires real coaching, feedback, and judgment.
How should a mid-market org redesign itself without copying Big Tech?
Do not copy Block's structure. Copy the logic.
Step 1: Identify where management is acting as a router
List recurring coordination pain: approvals, backlog prioritization, cross-team handoffs, customer escalation loops, and forecast changes. Then ask which pain exists because information is hard to find, trust, or interpret.
Step 2: Separate build, run, and change work
- - Build work: shipping product, automation, client delivery
- - Run work: operating cadence, quality, risk controls, reporting
- - Change work: redesigning processes, re-platforming, new offerings
Step 3: Create single-threaded ownership
Pick 3-5 outcomes such as quote-to-cash cycle time, on-time delivery, churn drivers resolved, support time-to-answer, and release frequency. Assign one accountable owner with authority to change process and data flows.
Step 4: Replace recurring meetings with exception-based operating
Use AI-prepared weekly metrics with deltas, drivers, and anomalies. Keep humans focused on decisions, tradeoffs, resourcing, and exceptions.
What are the risks and tradeoffs of flattening with AI?
- - Silent failure modes: teams feel fast while quality decays; define measurable quality gates.
- - Decision thrash: disagreement surfaces faster; make decision rights and escalation explicit.
- - Burnout risk: faster coordination can force always-on behavior; enforce cadence, WIP limits, and stop-doing decisions.
What should a CEO do in the next 30 days?
- - Measure coordination load: recurring meetings, status hours, alignment and handoff time.
- - Pick one workflow where information quality is the bottleneck and implement AI support.
- - Clarify ownership for three outcomes and give owners authority to change process and tooling.
- - Set a layers target as a design constraint to remove latency.
If you do this well, you will not just use AI. You will reduce organizational drag and increase execution capacity in a way competitors can feel.
Ready to redesign for throughput?
The Executive AI Operating Model Intensive helps leadership teams remove coordination drag and increase execution speed in 1-2 days.
Assess Your AI Operating MaturityFeatured guide
Start with where most AI programs actually break down
Why Your AI Transformation Is Being Overcomplicated (And How to Fix the Partner Problem) — the operating logic for picking partners and pacing transformation so execution matches mid-market realities.
Read the flagship guide