If you’d like to understand the Responsibility as TRM’s basic building block before continuing, start here.

Follett wrote this in the 1920s. Most organizations still haven’t absorbed it.

Why We Delegate

Delegation is not a management convenience. It is the mechanism through which an organization’s mission travels from intention to execution.

No leader — at any level — can personally deliver every outcome their responsibility requires. The scope is too broad, the work too varied, the expertise too specialized. The only way a Responsibility owner can fulfill a complex commitment is by enlisting others — by creating subordinate Responsibilities that activate specific parts of their strategy.

This is why delegation exists. Not to reduce a leader’s workload. Not to develop junior staff, though it may do that too.

Delegation exists to deliver outcomes that would otherwise not be possible. It’s an act of performance scaling.

It is the structural act through which Activation flows downward through an organization, expanding what can be accomplished. Every delegation is a governance act. It creates a new round of Intention → Activation → Performance, one level down, with a new owner who now carries a specific piece of the mission.

Understanding delegation this way provides insights about how it should be done.

What Most Delegation Gets Wrong

Conventional delegation is essentially an assignment. A leader identifies work that needs doing, determines who should do it, and communicates the expectation. The subordinate receives the assignment and executes.

This approach has a structural flaw. It produces compliance, not commitment. The person who receives an assignment understands what they’re supposed to do. But they don’t necessarily own it. The objective was handed to them. The strategy was implied or dictated. The key results were someone else’s idea of success.

When performance falls short, the result is predictable. The assignee followed the direction they were given. The assigner is frustrated that the outcome wasn’t what they intended. Both are right. The problem isn’t capability or effort — it’s that the delegation created a task, not a Responsibility.

Follett understood this a century ago. Bringing someone into the situation — genuinely enlisting their participation in defining the responsibility — is what converts an assignment into a commitment.

Delegation as Cooperative Discussion

TRM’s approach to delegation is specific. It is a cooperative discussion, not a directive. And the distinction matters because commitment cannot be manufactured. It can only be created through genuine participation in the outcome being agreed upon.

The delegation discussion has a clear purpose: to arrive at a shared understanding of a Responsibility that the owner genuinely commits to delivering. This requires three things.

First, the context must be established. The person being delegated to needs to understand not just what they’re being asked to own, but why — how this Responsibility connects to the strategy above it, what it’s trying to activate, and why it matters. This is a discussion about purpose. Without this context, they’re executing a task. With context, they’re contributing to a mission. That difference is not motivational language. It is the structural difference between compliance and ownership.

Second, the Responsibility must be shaped, not dictated. The Objective, the Strategy, and the Key Results should emerge from a discussion — not be handed down fully formed. This doesn’t mean the delegating owner has to bow to demands. It only means they bring their view into a conversation rather than issuing it as a conclusion. The person who will own the Responsibility typically has closer knowledge, context, and perspective that the delegating owner doesn’t. A negotiated Responsibility reflects that. It is also one that the new owner will actually believe in — because they helped shape it.

Third, commitment must be explicit. The discussion ends with a clear, mutual understanding of what has been agreed. Not an implied acceptance — an explicit one. The owner understands what they’re committing to deliver, by when, and how progress will be visible. The delegating owner understands what they’ve agreed to support. Both parties know how and when to renegotiate this agreement if conditions change.

This is what Follett meant by bringing those ordered into the situation. Not consultation for its own sake. A cooperative act that produces genuine ownership of a specific outcome.

What Delegation Creates

Every delegation creates two things simultaneously.

It creates a new Responsibility — a structured commitment, owned by one person, with a clear Objective, a negotiated Strategy, and explicit Key Results. This is the subordinate node in the mission chain, the next necessary link between intention and performance.

And it creates a new governance obligation for the delegating owner. Having delegated a Responsibility, they are now accountable not just for their own performance but for whether the delegation is working. Do the Key Results from the delegated activity show what they need to show? Is the strategy the owner chose actually activating the intended outcome? Is there anything the delegating owner needs to adjust — in their own strategy, in their support, or in the Responsibility itself — to make the chain function?

Delegation, in TRM, is never a handoff.

It is the creation of a relationship — a new, important link in the mission chain that requires ongoing attention from both ends.