Organization — Authority · HOT
HOT
O
O · The Organization dimension
Organization · Authority

The structure has to be
built to move.

Prepared people inside a rigid organization produce friction, not transformation. Authority is the thing an agent needs and cannot grant itself — and an organization does not fail to grant it once. It fails at successive walls, each of which looks like progress from the inside.

AUTHORITY, MADE EXPLICIT {{ r.label }} {{ r.tag }} THE PERMIT LINE — what the org allows without a human
Drag the line · set what runs without a human {{ permitRead }}{{ permitSub }}
Authority draws the line before any agent runs: what it may do alone, and what it must always hand back to a person. Structure is what makes the permit legible.
01 · Problem 02 · Shift 03 · The core 04 · How it holds 05 · Handoff
01 · The problem

The pilot worked. Nothing changed.

The most common outcome of an agentic program is not failure. It is a working pilot inside an unchanged company — because the structure absorbed the capability and left every decision path exactly where it was. The agent proposes at machine speed into an approval chain that still runs at meeting speed.

Companies that crossed into production did not buy a better model. They changed how decisions get made and who is allowed to make them. Everything short of that is rearrangement.

02 · The shift

Authority stops being implicit.

In a human-only organization authority can stay tacit — people read the room and know what they can sign. An agent cannot read the room. It needs the line drawn in advance, explicitly, by someone accountable for where it sits. The moment agents enter the business, every unwritten permission becomes a design decision someone has to own.

Is your organization built to move at the speed the agentic era demands — or built to hold still?

03 · The core

Three walls. Each one looks like progress.

An organization does not stall once. It stalls at three successive walls, and each has its own tell. This is not a maturity ladder you are graded on — the walls are where the structure stops the change, and you can be at all three in different parts of the same company.

Advance the state · watch where decisions pile up

State {{ stateNum }} · {{ stateName }}
{{ q.label }} {{ q.status }}
{{ stateNote }}
{{ stateStat }}
04 · How it holds

Purpose is what the structure is measured against.

A transformation with no purpose pulling it is just motion. The organizing intent — what the company is actually pulling toward — is the test every structural choice is held against. Without it, redesign is rearrangement. At framework level, three things have to be true for the structure to keep moving.

The unit
The decision, not the box

Reorganizations move boxes. This work moves decision rights — which is why a new chart with the old approval path changes nothing.

The order
Destination, then readiness, then build

Picture where the company is going. Check whether it can carry that. Then build. Reverse the order and you rebuild the company you already had.

The test
The line can be moved on purpose

A structure is built to move when the permit line has a named owner, a review rhythm, and a way to widen as judgment earns it — not when it is redrawn in a crisis.

The line HOT holds
Requirement, not method

HOT names the walls and what it takes to pass them. Which transformation method a team runs, and in what sequence, is a practice's work.

This dimension, pointed at you
Which wall are you standing at?

The scan reads each dimension separately and creates a score for each one.

Run the HOT scan → ~4 minutes · No email
Next dimension · five layers
The platform has to carry it.
T