Essay8 min read

What is context leadership? Leading people and agents

Leadership used to be direction. Now it's context. Briefing an agent and briefing a person turn out to be the same discipline.

Stuart Leo

Leadership used to be direction. Now it's context.

For most of the last century, the leader was the person who knew where things were going and said so. Direction flowed down. The organisation waited for the next instruction, acted on it, and came back with questions. That model still works for as long as the leader is in the room — and it fails quietly the moment they aren't.

Two things now act on the business without the leader in the room. People always did. AI agents are the new ones, and they are much less forgiving. Both act on what they can see. So the work of leading has moved from what you say to what you've written down.

A working definition

Context leadership is the practice of writing down what people and agents need to act well — the plan, the decisions, the standards and the lessons already paid for — keeping it in one place, and improving it every time it's used.

Three parts carry the weight.

  • Written down. Not said in a meeting. Not carried in your head. Written, so it can be read by someone who wasn't there.
  • In one place. A plan in five documents is five plans. The reader, human or agent, needs to know where to look first.
  • Improved every time it's used. Context isn't a document you finish. It's an asset that compounds, and it only compounds if every use leaves it a little better than it was.

The leader's job shifts from issuing direction to building the written context that people and agents can act on without them.

Why direction stopped scaling

Direction is a skill. Context is a system.

I draw that line from the third of the three tensions in Resolute: a skill is what one person can do, and a system is what survives that person leaving. A leader who directs well has a real and valuable skill. It lives in their head. Every decision routes through them, and the organisation can only move as fast as they can answer.

The twelve questions name the same failure from another angle. The leader who reaches for the answer first ends up running an organisation that depends on them for everything. The leader who reaches for the question first builds an organisation that thinks.

That was true before AI. Agents make it urgent, for a simple reason. An agent doesn't absorb direction over years. It starts every session from zero. Whatever it needs to act well has to be written down, or it doesn't exist.

Briefing an agent and briefing a person are the same discipline

Here is the thesis this whole site rests on.

When I brief an AI coding agent, I write down what to build, what not to build, and how I'll know it worked. I point it at the decisions already made, so it doesn't relitigate them. I record the traps already hit, so it doesn't walk into them again. In the Pilot model that's the first habit: brief before build.

Now look at what a good leader gives a new hire on their first week. The same things. The goal, the boundaries, what good looks like, the decisions behind the current plan, the mistakes nobody needs to make twice. The form is different. The discipline is identical.

The idea is old. The Twelve Questions are inspired by the British Army's Mission Command, where every officer trained in the same questions, the same intent-setting and the same decision rights. The result was autonomous decision-making at every level, aligned to a unified purpose. Clear intent, written so it can be acted on without the commander present. That's context leadership, a long time before anyone called it that.

What's new is the agent. A person can paper over a thin brief. They ask a colleague, they remember last quarter, they read the room. An agent can do none of that. It can't read your head. It can only read what's written down. So the agent is the most honest test of your context you will ever get. Where the agent drifts, a new hire was drifting too — they were just better at hiding it.

Fix the brief for the agent, and it gets better for the person. It's the same brief.

What changes in the leader's job

The shift is uncomfortable because it asks you to value work that was never rewarded. Producing the answer felt like leading. Writing down the context so the answer isn't needed from you feels like admin. It isn't. It's the higher-leverage work.

Direction (the old job)Context (the new job)
Answering the same question againWriting the answer where the next person reads it first
Holding the decision and the reason in your headRecording the decision, and why, so nobody relitigates it cold
Telling each person what to do nextWriting the brief: what to build, what not to, how you'll know it worked
Fixing the mistakeWriting down the trap, so the next person avoids it
Reviewing everything personallySetting the standard in writing, then holding it

The measure changes with it. A director measures the day in instructions given. A context leader measures it in how far people and agents got without needing them.

I've built this discipline twice, for two different things a leader can be responsible for.

Resolute: context for a company

Resolute is the method for the company. It gives a leadership team a shared, written picture of where the business is and where it's going.

The Leadership Curve says where you are. Six stages — Idea, Identity, Calibrate, Maturity, Mastery, Initiate — each demanding a different posture, skill and system from the same underlying character. It's a sensemaking framework. Before anyone can act well, they need to know which stage the business is actually in, because the right move in Identity is the wrong one in Mastery.

The 12 Questions say what has to be written down. Five questions of management for executing the present: plan, roles, goals, meetings, data. Seven questions of leadership for the future: vision, market, strategy, business model, customer experience, employee experience, and the one, two or three things that would shift the needle this quarter. Answered and written, those twelve are the company's context. Unanswered, everyone in the building is guessing at them.

Canvases and Clarity Statements turn the thinking into something people can act on. A canvas opens a hard question with divergent thinking. A Clarity Statement closes it with a short, structured sentence a new hire could repeat. That sentence is the unit of context. An agent can read it as easily as a person can.

And the questions get asked on a rhythm. The Seven half-yearly, the Five monthly or quarterly. Context that isn't revisited goes stale, and stale context is worse than none, because people trust it.

C²: context for a codebase

The C² Method is the same discipline applied to a codebase and the agents that build in it.

The router says where things are. One file the agent reads first — CLAUDE.md or AGENTS.md on disk. It's an index, not an encyclopedia. It routes the agent to whatever the task needs.

The contextbase holds what was decided and learned. A docs/ folder of plain markdown in git, next to the code. Briefs say what to build and what not to. Decisions record why. Gotchas record the trap once, so it never gets rediscovered cold.

A session brief closes every session. A few lines: what changed, why, what's verified, what's next. That's the written memory the next session reads, whether the next session is an agent or a person.

22 minutes into a live C² session, after the harness had already compacted the conversation, I asked the agent one question: how's your context? Its answer, verbatim: "everything load-bearing is externalized (PBs, briefs, PR bodies, memory), so even when the harness compacts the conversation, nothing about the program state lives only in my head." That is context leadership working at the scale of one agent. When the load-bearing context lives in git and not in the chat window, the agent survives its own forgetting.

One discipline, two methods

The two methods look different on the surface because a company and a codebase are different things. Underneath, they do the same job: keep the context in one place so it compounds.

The jobResolute, for a companyC², for a codebase
Say where things standThe Leadership CurveThe router
Decide what to build, and what not toCanvases and Clarity StatementsBriefs
Keep what was learnedThe 12 Questions, asked on a rhythmSession briefs and gotchas
The readerPeople, and the agents working with themAgents, and the people directing them

Most leaders will need both. The company's plan is context for the agents in the codebase, and the codebase's decisions are context for the leadership team.

Where to start

Pick the thing you lead.

If it's a company, find where the business sits on the Curve, then write one Clarity Statement the leadership team could repeat without looking it up. If it's a codebase, add a router file and write a five-line session brief at the end of your next session.

Then run the only test that matters. Hand what you wrote to someone who wasn't in the room — a new hire, or a fresh agent — and watch what they do with it. Every question they have to ask you is a gap in the context. Write the answer down where the next one will read it.

That is the whole practice. Direction gets spent the moment it's given. Context gets better every time it's used.

Start here: the map of both methods, Resolute, for the company, or C², for the codebase.

Questions people ask

What is context leadership?
Context leadership is the practice of writing down what people and AI agents need to act well — the plan, the decisions, the standards and the lessons already paid for — keeping it in one place, and improving it every time it gets used. The leader's job shifts from issuing direction to building the written context others act on without them.
How is context leadership different from traditional leadership?
Traditional leadership runs on direction: the leader decides and tells, and the organisation waits for the next instruction. Context leadership runs on what is written down. Direction is a skill that lives in one head. Context is a system that survives the leader leaving the room.
Why does leading AI agents change how you lead people?
An AI agent can only act on what it can read. It has no hallway, no memory of last week and no way to ask around. That exposes every gap in the written context that people quietly cover by asking the leader. Fix the brief for the agent and it gets better for the new hire too, because briefing an agent and briefing a person are the same discipline.
What are the two methods of context leadership?
Resolute, for a company: the Leadership Curve, the 12 Questions, and the canvases and Clarity Statements that turn a business plan into the operating plan people and agents run on. And the C² Method, for a codebase: a router file the agent reads first and a docs/ contextbase of briefs, decisions and gotchas that compounds with every session.
Where do I start with context leadership?
Pick the thing you lead. For a company, find where the business sits on the Resolute Leadership Curve and write one Clarity Statement your team could repeat. For a codebase, add a router file and write a five-line session brief at the end of your next session. Then test it: could a new person, or a new agent, act on it without asking you?

Commander in Brief

The weekly briefing: one real leadership decision in the news, connected to the framework. Fifteen minutes. Free.