I
What would break if this role did not make specific decisions?
Mandate dependencies
Part of the CTO Operating System · The Modern CTO Circle
The CTO
Mandate
A structured instrument for mapping where your mandate actually sits — what the organization depends on this role to do, where authority reaches, and what the system requires that is not currently happening.
Open the toolWhat it is
Not a job description.
An instrument.
Most CTOs know what their job description says. Far fewer know where their authority actually reaches — which decisions the organization depends on them to make, and which are made elsewhere regardless of what the org chart implies.
The CTO Mandate is a structured instrument for closing that gap. It works through three questions that no other tool in the operating system asks — and produces a snapshot of the mandate as it actually operates, not as it was intended.
The mandate is not what the job description says. It is what the system requires.
Run it at the start of a new role. Run it annually. Run it when the mandate has drifted and needs to be re-established. Each Mandate is saved — the comparison across time reveals whether authority is expanding, contracting, or holding under pressure.
The three questions
The framework the tool works through
Each question targets a different dimension of the mandate. Together they produce a complete picture — what it depends on, where it reaches, and what it is not yet doing.
II
Where does my authority actually reach under pressure?
Authority boundary
III
What does this mandate require that I am not currently doing?
Structural gaps
What it produces
Four outputs.
One mandate picture.
Each Mandate produces a structured record — not a score, but a snapshot that becomes more valuable each time you return to it.
The snapshot
Where the mandate sits at this moment — the dependencies it rests on, the boundary it currently holds, and the three highest-leverage actions to close the gap between what it requires and what is happening.
The trajectory
Across multiple Mandates, a pattern of whether authority is expanding, stable, or contracting — and what conditions are driving the direction. The trend line is more informative than any single snapshot.
The comparison
Side-by-side view of any two Mandates. What changed between them — which decisions shifted, where the boundary moved, which gaps closed or opened. The comparison is where the instrument earns its value over time.
The action record
Three highest-leverage actions from each Mandate, preserved across sessions. Not the most visible actions. Not the most urgent. The ones that, if completed, would most change the structural conditions the mandate operates within.
How to use it
When to run a new Mandate
The tool is most useful when run consistently — not only under pressure, but as a standing discipline at defined intervals. These are the right triggers:
01
New role
Within the first 60–90 days. Before announcing direction. The mandate must be located before it can be exercised. What the organization needs from this role is not in the job description — it is in how decisions have been routed in the weeks before arrival.
02
Annual review
Once per year, before roadmap planning begins. Confirms whether the mandate has expanded, contracted, or drifted over the year — and whether the gaps identified in the previous Mandate have been closed or compounded.
03
Mandate drift
When decisions that should route through the CTO are consistently being made elsewhere. The boundary has moved without being acknowledged. Running the CTO Mandate surfaces exactly where it moved and what is required to re-establish it.
04
Org change
After a significant structural event — acquisition, leadership change, org restructure. The mandate does not automatically transfer to the new structure. It must be re-established in the new context. Assuming continuity is the most common mistake in these transitions.
05
Post-crisis
After a major incident, transformation failure, or governance breakdown. What the mandate requires has almost certainly changed — both in scope and in what the organization is now willing to support. The CTO Mandate surfaces what is different.
The mandate is not fixed.
It is built — and lost — through consistent behavior.
Each Mandate you complete is a precise record of where it stands. Over time, the record becomes the most honest account of how your authority is actually evolving — more accurate than any org chart, and more actionable than any job description.
Open the tool