# Shape Intelligence with Mandates: The Org Design Lever Nobody Talks About **Author:** Alexey Krivitsky **Date:** 2026-07-24 **Reading time:** 5 min **Category:** Org Design **Tags:** org-design, organization-design, mandates, 10x-org, leadership, org-topologies **Canonical:** https://krivitsky.com/post/10xorg-p3-shape-intelligence --- **TL;DR:** Mandates set the ceiling of what an organization can handle. The skills a unit is allowed to use and the scope of work it's trusted with — these define its organizational intelligence. Change the mandate, change what's possible. The third principle from 10X ORG. This continues the Friday series — one principle from *10X ORG* each week, the ideas that make an organization ten times more effective, not ten percent. We started with the one everything rests on, [own, not rent](/post/10xorg-p1-own-not-rent), then looked at how [org design drives performance](/post/10xorg-p2-drive-performance). This week is the one that makes org design concrete: what you can actually change to shape how an organization thinks and acts. ## The hangar in Delft Summer 2019. Roland is coaching a group of student engineers at Delft University of Technology. They're building a hydrogen racing car — teenagers, mostly, with no corporate experience between them, handed total freedom to organize however they see fit. Within a few weeks they had built something oddly familiar. Functional silos. A lead for each area. Standing coordination meetings to stitch the pieces back together. Nobody handed them an org chart. Nobody told them how a company is "supposed" to run. They reinvented it from scratch, because that's what people do when work gets complicated: they divide it up and assign someone to own each part. That instinct is worth naming, because it's the raw material of every organization. In *10X ORG* we call those bundles of authority and responsibility **mandates** — the license a unit holds to decide, act, and deliver within a defined scope. And here's the part leaders underestimate: mandates set the ceiling of what an organization can handle. Not the people. The mandates. ## Two things a mandate defines A mandate answers two questions, and they run along different axes. **What skills is this unit allowed to use?** Some units are incomplete. A customer service team handles the ticket but can't touch the billing system, the pricing engine, or the contract behind the problem. So it hands off, waits, and depends on three other groups to actually resolve anything. Incomplete doesn't mean incompetent — the people can be excellent. It means the structure forces handoffs. A complete unit, by contrast, can take the whole customer problem from "something's wrong" to "it's fixed" without leaving the room. There's a small story that makes this land. A support team gets a ticket about a VAT error and does exactly what its mandate allows: it processes the ticket. The fix goes in — set the multiplier to zero when the country isn't "EU." Ticket closed. Output delivered. Everyone did their job. Except Switzerland, which isn't in the EU, keeps getting charged wrong. Canada has its own rules. Finance keeps flagging discrepancies that nobody upstream can see. The code did precisely what the mandate said. The mandate was the problem. **How much of the work is this unit trusted with?** This is the second axis. Some units get a narrow output scope — ship this feature, close these tickets, process these claims. Others are connected to the outcome: did the customer's problem actually get solved, did the number move. A narrow work mandate pulls a team toward optimizing its own little square. A broad one pulls it toward learning and steering. The economics underneath this are simple — when it's expensive to change direction, high switching costs push an organization to predict and lock in; when redirecting is cheap, the organization can afford to learn as it goes. ## Four intelligences Cross those two axes and four kinds of organizational intelligence emerge. **Doing Intelligence** sits bottom-left: specialists executing well within narrow scopes, dependent on coordination handed down from above. **Delivering Intelligence** is bottom-right: complete units that ship reliably inside their boundaries, though they don't own the end-to-end outcome. **Directing Intelligence** is top-left: oversight and coordination without direct value creation — the PMO and program-management world, orchestrating pieces it doesn't build. And **Driving Intelligence** is top-right: units that blend strategy with execution, own the outcome, and can steer without waiting for direction from above. That last quadrant is where "business agility" actually lives. Not from a process overlay bolted onto a slow structure, but from the structural conditions that let a unit sense and act at the same time. Which is the whole point of the principle. Organizational intelligence isn't a trait of the people you hired — it's a result of the mandates you gave them. Change the mandate and you change what the organization can see, learn, and act on. That's the lever. ## Why this sharpens with AI AI doesn't rewrite this dynamic. It amplifies it. Strategic AI adoption starts by asking which organizational intelligence is missing, then using AI to help grow it — automation and supervision for Doing units, faster feedback loops for Delivering ones, sharper synthesis and sensing for Directing work. But there's a catch, and it's the one most rollouts walk straight into. If the mandates stay narrow, AI just accelerates local output and leaves every structural handoff exactly where it was. You get faster Doing and the same coordination drag — the [Ferrari effect](/post/the-ferrari-trap) again, the car quicker and the road still laid out wrong. The [DORA data keeps finding this](/post/dora-2026-developers-faster-teams-messier): hand AI to a unit with a cramped mandate and its speed climbs while delivery gets messier around it. The mandate has to open up first. Then AI has something worth accelerating. ## The lever What mandates give a leader isn't a slogan — it's a place to push. When an organization can't seem to learn, or every problem needs three teams and a meeting to resolve, the answer usually isn't more talent or more exhortation. It's a mandate drawn too narrow. Widen it and the intelligence follows. The full picture — the 2x2 map, the four intelligences, and how they interact with strategy — is in *10X ORG*, a bestseller in Management Strategy and related categories, on [Amazon](https://www.amazon.com/10X-ORG-Topologies-Elevating-Performance/dp/9083670406) in Kindle, paperback, and hardcover. Happy Friday, all.