The Essential Elements

Responsibilities are the basic building block of performance, where alignment and accountability naturally emerge. 

But what does a responsibility actually look like? How is it structured? What makes one clear and actionable?

In TRM, a responsibility has a very specific architecture. It consists of three essential elements, and understanding how they work together is what transforms a vague intention into something you can actually activate.

The Goal

A goal is the outcome you're responsible for delivering. It can be specific or broad—what matters is that it's mission-focused. It's tied to why your work exists in the first place.

"Ship the Q3 feature set" is a goal. So is "Build the engineering team's capability in cloud architecture." So is "Reduce customer acquisition cost by 30%." The specificity varies. The requirement is alignment: your goal should connect clearly to the mission you're serving.

Authorities and Constraints

Authorities are the decisions you can make without approval. Constraints are the boundaries you operate within. Together, they define your operational space.

Authorities might be: "You can make technology choices without approval up to $50K. Beyond that, you need executive sign-off." Or: "You have hiring authority for your team up to 12 people." Or: "You can commit to customer timelines within existing capacity; if new work exceeds capacity, we negotiate."

Constraints might be: "You have a budget of $200K for the year." Or: "You must coordinate with the product team before committing to feature changes." Or: "You operate within our existing compliance framework."

There's no "right" set of authorities and constraints. There's only whether they're appropriate for the situation. Appropriateness depends on several things:

• The nature of the goal. High strategic impact goals often require tighter constraints and more frequent check-ins. Operational goals might have broader authorities.
• The nature of the person carrying the responsibility. An experienced leader might have broader authorities for a given goal than someone new to that domain.
• Required coordination. Goals that touch multiple teams often need explicit constraints around how collaboration happens.

The key is that authorities and constraints are defined, not left to assumption. That clarity is what transforms a responsibility from abstract to actionable.

Key Results

Key results are how you measure success. They track two things: whether the goal has been achieved, and whether constraints have been honored.

Key results can take different forms depending on the nature of the goal:

• Project-based: A goal with a defined endpoint has a key result that's assessed at conclusion. "Ship the feature set" with key results like "All planned features delivered by December 15th. Zero critical bugs in production in the first 30 days."
• Ongoing metrics: A goal that's continuous has key results that track regularly. "Maintain customer satisfaction above 4.5/5" with monthly key results. Or "Grow new customer acquisition" with quarterly key results showing growth trajectory.
• Laddered progression: A goal with a long-term target might have key results that show incremental progress. "Achieve 100% improvement in manufacturing efficiency over the year" with key results of "25% improvement by Q1, 50% by Q2," and so on. This shows you're on trajectory toward the larger goal without requiring everything to happen at once.

The beauty of key results is that they're objective. You can't argue about whether they've been met. Either the feature shipped on time or it didn't. Either customer satisfaction is above 4.5 or it isn't. Either you hit 25% improvement by Q1 or you didn't. That objectivity is what makes accountability real.

How Responsibilities Activate

Remember the activation sequence: assess environment, consider strategies, take first step, monitor and react.

A responsibility's three elements structure that entire sequence.

When you assess the environment, you're asking: "Given this goal, these authorities, and these constraints, what's actually possible?" The constraints define your boundaries. The authorities define your decision space. The goal defines what you're aiming for.

When you consider strategies, you're asking: "What approach has a reasonable likelihood of delivering this goal, as defined by these key results, while honoring these constraints?" The goal tells you what success looks like. The key results give you the measures. The authorities tell you what you can do. The constraints tell you what you can't.

When you take the first step, you're committing to action within this defined structure.

When you monitor and react, you're tracking against the key results. Are we on trajectory? Are we honoring constraints? Do we need to adjust strategy? The key results keep you honest. They show you what's actually happening versus what you intended.

The three elements don't just define a responsibility. They structure how you activate it.

Strategy Flows from the Elements

Once these three elements are clear, strategy becomes a natural next step. A strategy is simply an approach that provides a reasonable likelihood of delivering the goal, as defined by the key results, while operating within the constraints.

You don't need a perfect strategy. You need one that's reasonable given what you know. And because you're monitoring against key results, you'll know quickly whether your strategy is working. If it's not, you adjust.

This is crucial: Strategy is not fixed. The goal might be fixed. The key results might be fixed. The constraints might be fixed. But strategy is fluid. It's your best hypothesis about how to deliver the goal given the environment. And as the environment changes, as you learn what works and what doesn't, your strategy evolves.

The three elements create the structure. Strategy provides the path. Together, they make activation possible.

Ownership Through Responsibility Agreement

Owning a responsibility means you're committing to the activation sequence within this structure. You're saying: "I understand the goal. I understand my decision space. I understand how success is measured. I'm committing to activate this responsibility and deliver the outcome."

But commitment only becomes real when it's transparent. When both you and the person who delegated the responsibility have the same understanding of what you're agreeing to.

This transparency happens through a responsibility agreement—a clear statement of the goal, authorities, constraints, and key results that defines what you're activating. It doesn't have to be elaborate. It can be a conversation that gets documented. It can be a brief written statement. What matters is that it's explicit.

A responsibility agreement does several things:

• It forces clarity. Writing down the goal, authorities, constraints, and key results surfaces ambiguity. If you can't define them clearly, you're not ready to activate.
• It creates shared understanding. Both parties know what they're agreeing to. There's no hidden assumption about what success looks like or how much authority you have.
• It establishes accountability. Once you've agreed on key results, accountability becomes objective. You're not arguing about whether you tried hard enough. You're looking at whether the key results were met.
• It enables monitoring. The agreement gives you both a framework for checking in. "How are we tracking against key results? What's emerging? Do we need to adjust?"

This is where TRM makes accountability real. It's not about how hard you work or how committed you are. It's about whether you're delivering the agreed-upon outcome, within the agreed-upon constraints, as measured by the agreed-upon key results.

Why This Structure Matters

The three elements—goal, authorities and constraints, key results—might seem simple. They are. But their simplicity is their power.

They force specificity. You can't hide behind vague intentions. You have to define what you're actually trying to accomplish.

They enable activation. Once these are clear, the activation sequence becomes natural. You know what you're aiming for, you know what you can decide, you know how you'll measure success.

They scale recursively. A person activates a responsibility. They delegate a portion to someone else, creating a supporting responsibility with its own goal, authorities, constraints, and key results. That person activates theirs. The whole structure activates together because each level is clear.

They make accountability objective. Key results are measurable. Constraints are explicit. Success is unambiguous.

What Comes Next

The sections ahead will show you how to create these responsibilities at every level—how to define goals that connect to mission, how to negotiate authorities and constraints that match the situation, how to establish key results that actually measure success.

But the foundation is this: A responsibility is a structure, not a burden. It's clarity that makes activation possible.

Once you see how goal, authorities and constraints, and key results work together, you start designing them everywhere. You notice that the teams executing well have crystal-clear responsibilities. The ones struggling have ambiguity at this fundamental level.

This is where performance actually begins: not with motivation or culture or values, but with structural clarity about what you're responsible for, what you control, and how success is measured.

That clarity is what transforms intention into owned outcome.