{"id":4912,"date":"2026-01-06T15:07:46","date_gmt":"2026-01-06T15:07:46","guid":{"rendered":"https:\/\/theresponsibilitymatrix.com\/home\/?p=4912"},"modified":"2026-03-05T15:07:59","modified_gmt":"2026-03-05T15:07:59","slug":"agreements","status":"publish","type":"post","link":"https:\/\/theresponsibilitymatrix.com\/home\/agreements\/","title":{"rendered":"3. Create Responsibility Agreements"},"content":{"rendered":"\n
\n

The Responsibility Agreement: Making Commitment Visible<\/h1>\n\n\n\n
<\/div>\n\n\n\n

Unless commitment is made, there are only promises and hopes; but no plans.
<\/p>\u2014 Peter Drucker<\/cite><\/blockquote><\/figure>\n\n\n\n

<\/div>\n<\/div>\n\n\n\n

If you’d like to understand TRM’s view of delegation as a cooperative discussion before continuing, start here<\/a>.<\/p>\n\n\n\n

If you want to review the essential elements that make up any any responsibility agreement, start here<\/a>.<\/p>\n\n\n\n

<\/div>\n\n\n\n

A delegation discussion, however well conducted, produces something fragile. It lives in the memory of two people. It is subject to tidal flow of recollection \u2014 what each party believed was agreed, what each assumed was implied, what each has since reinterpreted in light of subsequent events.<\/p>\n\n\n\n

The Responsibility Agreement is the act that changes this. It converts a private discussion into an organizational asset. It is where Transparency \u2014 the catalyst that makes Alignment and\u00a0Accountability observable \u2014 finally arrives. <\/em><\/p>\n\n\n\n

Why Writing It Down Changes Its Nature<\/h3>\n\n\n\n

There is a common assumption that documenting an agreement is an administrative act \u2014 a record of what was decided, useful for reference but not fundamentally different from the conversation itself.<\/p>\n\n\n\n

This assumption is wrong.<\/p>\n\n\n\n

A documented commitment is qualitatively different from a verbal one. Not because people are untrustworthy, but because visibility changes the nature of accountability. When a commitment exists only between two people, it can be unintentionally reinterpreted, gradually adjusted, or conveniently forgotten without either party necessarily acting in bad faith. Memory is imperfect. Priorities change. What felt clear in the room becomes ambiguous six months later.<\/p>\n\n\n\n

When a commitment is documented \u2014 clearly, specifically, and accessibly \u2014 it acquires a permanence that verbal agreement cannot provide. It becomes something the everyone can see, reference, and rely upon. It stops being a private understanding and becomes a governance instrument.<\/p>\n\n\n\n

This is the transition the Responsibility Agreement creates. The delegation discussion established Alignment \u2014 both parties understood the direction and committed to a shared outcome. The essential elements established Accountability \u2014 one person owns a specific commitment with an objective performance standard. But until those things are documented, they remain interior states, visible to the two people in the room. But it\u2019s invisible to the organization that depends on them.<\/p>\n\n\n\n

Transparency is what makes Alignment and Accountability real in the governance sense. The Responsibility Agreement is how Transparency arrives.<\/p>\n\n\n\n

What the Agreement Captures<\/h3>\n\n\n\n

The Responsibility Agreement is not a comprehensive legal document. It is, in Buffett’s terms, a one-page contract \u2014 clear enough that both parties can describe it without ambiguity, complete enough that the organization can rely on it.<\/p>\n\n\n\n

It captures the three essential elements agreed during the delegation discussion: the Objective, the Authority and Constraints, and the Key Results. Nothing more is required \u2014 and nothing less is sufficient.<\/p>\n\n\n\n

The Objective is documented in terms specific enough that both parties would characterize it identically if asked independently. Whether committed or aspirational, the nature of the Objective and what success looks like under its terms is stated explicitly. There is no room for later divergence about what was intended.<\/p>\n\n\n\n

The Authority and Constraints are documented in full \u2014 including approval requirements, resource boundaries, and any operating limitations that will shape the owner’s strategy. A constraint that isn’t documented is a constraint that will eventually be disputed. The agreement makes the operating environment permanent and unambiguous.<\/p>\n\n\n\n

The Key Results are documented as the objective standard against which performance will be evaluated. This is the governance commitment that gives the Responsibility Agreement its most consequential property: what is not in the Key Results cannot legitimately factor into the performance evaluation of this Responsibility. The agreement protects both parties \u2014 the owner from subjective reassessment after the fact, and the delegating owner from the organizational cost of a later performance conversation that feels unfair.<\/p>\n\n\n\n

When the full network of Responsibility Agreements exists and is accessible, something larger becomes possible \u2014 the organization’s mission chains become traceable, and the Responsibility Matrix begins to emerge as a living governance architecture rather than a theoretical construct. That transition deserves its own discussion, and we’ll address it fully in a subsequent post.<\/p>\n\n\n\n

The Agreement as a Reference Point<\/h3>\n\n\n\n

Here is where most frameworks stop \u2014 with the agreement signed, filed, and retrieved only when performance is being evaluated. TRM’s view is different.<\/p>\n\n\n\n

The Responsibility Agreement is not primarily a compliance instrument. It is a reference point that the owner returns to \u2014 not because they are being held to their word, but because returning to it is an act of responsible ownership.<\/p>\n\n\n\n

There is a meaningful difference between understanding a commitment from the outside and understanding it from the inside. When the agreement was first made, the owner understood what they were committing to from the outside \u2014 through the discussion, the context provided, and their best judgment at the time. A few months into execution, they understand it from the inside. They know where the strategy is working and where it isn’t. They know which constraints are genuinely limiting and which turned out to be irrelevant. They know whether the Key Results are measuring what actually matters or whether they’re tracking the wrong signals. This inside understanding is valuable. And the owner who pulls out the agreement, reads it with fresh eyes, and asks honestly \u2014 does this still reflect what we intended? \u2014 is exercising ownership at its most mature.<\/p>\n\n\n\n

This is reevaluation not as a response to failure, but as a natural governance act. The owner who recognizes that the original commitment no longer reflects reality \u2014 and brings that recognition back into a cooperative discussion \u2014 is doing exactly what the delegation framework was designed to support. They are keeping the agreement honest rather than allowing it to drift into irrelevance or, worse, continuing to perform against a standard they no longer believe in.<\/p>\n\n\n\n

What Renegotiation Actually Requires<\/h3>\n\n\n\n

Renegotiation is not abandoning the commitment. It is returning to the same cooperative, mission-focused discussion that created it \u2014 with better information.<\/p>\n\n\n\n

The owner comes back to the delegating owner not with an excuse but with an observation: here is what I now understand about this Responsibility that I didn’t understand when we agreed to it. Here is what I think needs to change, and why. Here is what I believe the right commitment looks like given what I now know.<\/p>\n\n\n\n

That conversation may result in a modified Objective, adjusted Constraints, revised Key Results, or simply a shared confirmation that the original agreement remains sound. What it produces, in every case, is a commitment that both parties can stand behind with current knowledge \u2014 which is a more valuable governance instrument than one that was accurate six months ago and hasn’t been examined since.<\/p>\n\n\n\n

The delegating owner carries an obligation here too. A subordinate owner who returns with an honest renegotiation request deserves a genuine response \u2014 not a defense of the original agreement for its own sake. The purpose was never a documented agreement. The purpose was the mission the agreement was designed to activate.<\/p>\n\n\n\n

Commitment Made Visible<\/h3>\n\n\n\n

Drucker’s observation is precise. Until commitment is documented \u2014 until it exists as something the organization can see, reference, and rely upon \u2014 it remains in the territory of promises and hopes.<\/p>\n\n\n\n

The Responsibility Agreement is what converts the cooperative discussion and its essential elements into a plan. Not a plan in the procedural sense. It\u2019s not a to-do list or a project schedule. It\u2019s a plan in the governance sense \u2014 a documented commitment that makes performance visible, accountability real, and the mission traceable from intention to execution.<\/p>\n\n\n\n

But its deepest value isn’t in what it captures at signing. It’s in what it enables afterward \u2014 an owner who returns to it with fresh eyes, an honest renegotiation when reality diverges from intention, and a governance architecture that stays current because the people within it are paying attention.<\/p>\n\n\n\n

This is where Transparency arrives. And it is what makes the Responsibility Matrix a governance architecture rather than a theoretical construct.<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

In TRM, a responsibility isn’t “official” until it is written down.<\/p>\n

Once the 3 Essential Elements (Objective, Constraints, and Key Results) are shaped during a 1:1 discussion, they must be captured in a Responsibility Agreement.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":true,"template":"","format":"standard","meta":{"nf_dc_page":"","footnotes":""},"categories":[52],"tags":[],"class_list":["post-4912","post","type-post","status-publish","format-standard","hentry","category-disciplines"],"_links":{"self":[{"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/posts\/4912","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/comments?post=4912"}],"version-history":[{"count":11,"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/posts\/4912\/revisions"}],"predecessor-version":[{"id":5790,"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/posts\/4912\/revisions\/5790"}],"wp:attachment":[{"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/media?parent=4912"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/categories?post=4912"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/theresponsibilitymatrix.com\/home\/wp-json\/wp\/v2\/tags?post=4912"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}