Responsibilities: TRM's basic building blocks

Intention > Activation > Performance

The IAP sequence makes perfect sense inside a textbook.

Thankfully, it’s more than a textbook concept. This elegance also exists in the real world. We just have to see it. 

It’s called - a responsibility. 

TRM intentionally focuses on responsibilities as the basic building blocks for performance. These are where alignment and accountability naturally incubate together.

Working Backward from Performance

We identified responsibilities as the basic building block because, time after time, we kept running across them as the essential enabler for performance.  

Consider a software team that ships features reliably. What makes that possible?

If you work backward from "reliable delivery," you find a clear ownership structure. Someone owns the roadmap. Someone owns the architecture. Someone owns the testing. Someone owns the release. Each person has a clear responsibility. They aren’t stumbling into each other. They’re not overriding each others’ decisions. They each have a specific outcome they own, with authority to make decisions and abide by the constraints they operate within. That’s how work gets done.

Now consider a struggling organization—one where decisions move slowly, where accountability is murky, where people feel overwhelmed. Work backward through that mess, and you find the same thing missing: unclear responsibilities. People are ready to point fingers at others when something falls short. They argue that they did what they were told. There’s no accountability because no one was clearly responsible.

The pattern is consistent. Every high-performing system you examine—whether it's a surgical team, a product company, a military unit, a family—has a clear structure of responsibilities at its core. 

This isn't about personality or culture or hard work. It's structural.

If you believe that alignment and accountability are essential to performance—that people need to understand how their work connects to mission, and that they need to own their outcomes—then the responsibility is where both of those naturally emerge.

What Makes a Responsibility Clear

A responsibility becomes real when three things are defined:

The objective. What meaningful outcome are you responsible for delivering? 

The authorities and constraints. What decisions can you make and where do you need additional approvals?

The key results. How will everyone know (and agree) that you've succeeded? 

With these three elements defined, a responsibility stops being abstract. It becomes something a person can activate. We talk a lot more about these in Section 2.

The Recursive Nature of Responsibilities

Here's where it gets interesting structurally.

Your responsibility flows from someone else’s responsibility.

Your team lead has a responsibility to deliver an outcome. They delegate a key part of that outcome to you, specifically. Perhaps your team lead could have done it themself. But they recognize that everything will go more smoothly if, instead, you own this particular delegated portion of the larger responsibility.  

Their strategy (to delegate) created your responsibility. 

Your new responsibility has the same structure as every other responsibility: objective, authorities and constraints, key results. And the person carrying it activates the same way—assess environment, consider strategies, take first step, monitor and react.

And, if you choose to delegate part of your new responsibility to someone else, you’re also creating a new responsibility. Same structure. Same ideas.

That’s the recursive nature of responsibilities. 

Think of it visually: a responsibility at the top breaks into supporting responsibilities beneath it. Each supporting responsibility can break into further responsibilities. It's responsibilities all the way down. The beauty is that they're connected. Each one serves the larger outcome above it.

This is why the structure is so powerful. A sales leader has a responsibility to hit revenue targets. To do that, they delegate a portion to the manager of Sales Region A and part to the manager of Sales Region B. The two sales managers then further delegate sales expectations to each individual sales person. 

The sales leader created a strategy to hit their target. They did it through delegation. And their success now relies on the success of everyone below them in the delegation chain. The structure forces alignment—each supporting responsibility has to connect back to the mission it serves.

And it creates accountability at every level. The individual owns their sales goals. These support the Regional Manager’s sales goals. And those, in turn, support the Sales Executive’s goals. No one can hide. No one can be unclear about what they're responsible for.

This is the main focus for Section 3.

Why This Matters for Activation

Remember: activation is the sequence of assessing environment, considering strategies, taking a first step, monitoring and reaction.

But you can't activate what's not clear. If a responsibility is ambiguous, the activation sequence breaks down immediately. How do you assess the environment for an outcome you don't actually understand? How do you take the first step toward something that's undefined?

Clarity in responsibilities is what makes activation possible.

And the recursive structure is what makes activation scale. You don't need one heroic leader making all the decisions and monitoring everything. You have a cascade of clear responsibilities, each one activating at its own level, each one feeding into the larger structure.

A person activates their responsibility. They delegate to create supporting responsibilities. Those people activate theirs. The whole system activates together because the structure is clear.

The Foundation for What Comes Next

The posts ahead will show you how to define responsibilities at every level—how to create the clarity that makes activation possible.

We'll explore how to negotiate responsibilities with the people who carry them, how to ensure authorities and constraints are real, how to monitor that accountability is actually functioning.

But the foundation is this: Responsibilities are not administrative overhead. They are the basic building block where alignment and accountability naturally emerge.

Without clear responsibilities, you get confusion. With clear responsibilities, you get the structural foundation that makes everything else possible.

Once you see this, you start noticing it everywhere - at work, at home, the doctor’s office, the grocery store. You start being in tune to notice when responsibilities are clear. And when they aren’t. 

Congratulations - this is the first step toward the next level.