If you’d like to understand TRM’s view of delegation as a cooperative discussion before continuing, start here.

A well-structured delegation isn’t a legal defense. It’s a clear agreement between two people who are both committed to the same mission.

What Needs to Be Agreed

Delegation is a cooperative discussion — not a directive. That discussion has a specific purpose: to arrive at a shared understanding of a Responsibility that the new owner genuinely commits to delivering.

But a discussion without structure produces commitment without clarity. And commitment without clarity always underperforms.

TRM identifies three essential elements that every delegation discussion needs. Together they define the Responsibility clearly enough to be owned, acted on, and held accountable, and simply enough that both parties can describe it without ambiguity.

Element One: The Objective

The Objective answers a single question: what is the new owner intending to pursue?

That question is deliberately open. Objectives exist on a spectrum — from committed outcomes that the owner is fully expected to deliver, to aspirational goals where ambitious pursuit matters as much as final achievement. Both are legitimate within TRM. What is not legitimate is ambiguity about which kind of Objective this is.

A committed Objective — “ensure that every new customer is fully operational within 30 days of contract signing” — creates a clear performance standard. Both parties know what delivery looks like. A committed Objective that is met is a delivered Responsibility.

An aspirational Objective — a moonshot that might produce transformational results or fall short — operates differently. Here, the Objective establishes direction and ambition. It signals what the organization is reaching toward. Seventy percent achievement might represent extraordinary performance. Or it might not. What matters is that both parties agree before the commitment is made, and what success looks like under its terms.

Every Objective should be clear enough that both parties would characterize it the same way, without discussion, when asked independently.

This is also why some Objectives need not carry the full burden of performance definition. That work belongs to the Key Results — which is where the objective measurement of delivery lives.

Element Two: Authority and Constraints

Every Responsibility exists within boundaries. The new owner needs to know what resources, decisions, and approaches are available to them — and which are not. This is the Authority and Constraints element, and it is the most frequently omitted in conventional delegation.

Authority defines the scope of the owner’s decision-making power. What can they decide unilaterally? What requires consultation? What requires approval? These boundaries are not bureaucratic limitations — they are the honest description of the environment within which the new owner will develop their strategy. A strategy built on assumed authority that doesn’t exist is a strategy headed for friction.

Constraints are the specific limitations that apply to this Responsibility in this context. They may be resource constraints — budget, headcount, tools. They may be process constraints — required approvals, mandatory reporting, coordination requirements. Or they may be performance constraints — standards that must be maintained while pursuing the Objective.

One constraint deserves specific attention: the approval requirement. In some delegations — particularly where the new owner is developing in a role, or where the stakes of strategic misstep are high — the delegating owner may require that the strategy be approved before implementation. This is sometimes dismissed as micromanagement. It is not. It is an honest constraint that, when named explicitly and agreed to, is simply part of the operating environment. The problem with micromanagement is not the oversight — it is the oversight that was never disclosed. An approval requirements are simply a constraint to be discussed and agreed-upon. Conversely, undisclosed control is a betrayal of the delegation discussion.

The Right to Push Back

Here is where the cooperative nature of delegation becomes most consequential.

The new owner has not only the right but the obligation to push back if the constraints make success highly unlikely. This is not insubordination. It is mission focus.

A delegation discussion that produces a commitment the owner doesn’t believe they can honor — because the constraints are too limiting, the resources too scarce, or the timeline too compressed — has not produced a Responsibility. It has produced a set-up for failure dressed as an agreement. Both parties will discover this eventually. The only question is whether they discover it before or after the performance consequences arrive.

The delegating owner should welcome this pushback. It surfaces problems when they are still solvable — when constraints can be adjusted, resources reallocated, or timelines renegotiated. A new owner who accepts an impossible commitment without raising it has done neither party a service.

This is what makes the delegation discussion genuinely cooperative rather than performatively so. Both parties are trying to arrive at a commitment that is honest, achievable, and mission-focused. That requires both parties to say what they actually think.

Element Three: Key Results

Key Results are the objective definition of performance for this Responsibility. They are what both parties agree, in advance, will determine whether the Responsibility has been successfully delivered.

This is not a minor administrative detail. It is a governance commitment with direct consequences. If it isn’t captured in the Key Results, it cannot legitimately factor into the performance evaluation of this delegation. The delegating owner may have other observations about the new owner’s broader professional development — but their evaluation of this specific Responsibility is bounded by what was agreed. The Key Results are the standard. There is no room for subjective reassessment of delivery after the fact.

This places a significant obligation on both parties during the delegation discussion. The new owner must ensure the Key Results are complete — that every outcome they will be evaluated against is captured, and that no implied standard has been left unspoken. The delegating owner must ensure the Key Results are honest — that they reflect what genuinely constitutes successful delivery, rather than a minimal standard that will later feel insufficient.

Effective Key Results operate at two levels.

Leading Key Results track progress, adherence, and interim milestones. They make performance visible before the final outcome arrives, which supports ongoing oversight and creates natural renegotiation points if conditions change. A laddering sequence — 50% of the goal achieved in three months, 75% in twelve — is a legitimate and often valuable form of leading Key Result. So is adherence to agreed constraints. If a constraint is important enough to agree to, it is important enough to track. An approval requirement consistently honored, a budget ceiling consistently respected — these are measurable performance signals that belong in the Key Results if they help define success.

Lagging Key Results measure final outcomes. They answer the ultimate question: was the Objective achieved, and to what standard? For committed Objectives, a lagging Key Result is typically binary or near-binary — the standard was met or it wasn’t. For aspirational Objectives, the lagging Key Result captures the degree of achievement against the ambition that was agreed.

Together, leading and lagging Key Results give the Responsibility an ongoing performance story — not just a final verdict. They surface problems early enough to address, create honest checkpoints for renegotiation, and produce the objective record on which a fair performance evaluation depends.

What These Three Elements Produce

An Objective, Authorities and Constraints, and a set of Key Results together define a Responsibility clearly enough to own, act on, and be accountable for.

They do not define the Strategy. That is the Responsibility owner’s domain — and deliberately so. Strategy emerges from the owner’s understanding of their Objective, their Authority and Constraints, and their own judgment about the best approach given their context. Requiring strategic agreement during the delegation discussion risks producing a dictated strategy dressed as collaboration. The owner needs the room to think, adapt, and commit to an approach that is genuinely theirs.

What the three elements produce, instead, is the framework within which that strategy will be developed and executed. They make the commitment clear, the operating environment honest, and the performance standard objective and agreed.

Buffett’s one-page contract isn’t a low standard. It’s a high one. It means that the agreement is clear enough, and the relationship honest enough, that complexity is unnecessary. That is exactly what a well-structured delegation produces — and what the Responsibility Agreement makes permanent and transparent.