Vox

Leitura de 18 min

Delegation, Ownership, Responsibility, and Agency

Summary

The episode begins by introducing the Eisenhower Matrix as a common prioritization tool for leaders, focusing specifically on the delegation quadrant. It challenges the simplistic view of delegation as merely transferring tasks from one person’s to-do list to another’s. Instead, the host proposes that true delegation requires transferring full ownership, which is composed of two essential elements: responsibility and agency.

Responsibility is defined as being accountable for and caring about the outcome of a task. Agency is the reasonable ability to operate within the solution space and make consequential decisions. The host introduces the “Four T’s” as resources that prove agency: Training, Time, Tools, and Talent. The episode then examines the first common delegation failure: delegating only agency without responsibility. This creates a “social contract” where the person executes the task to please the delegator rather than caring about the actual outcome, leading to misaligned motivations and potential breakdowns, especially in larger organizations with abstract high-level goals.

The second failure mode is delegating responsibility without providing the necessary agency. This often manifests as a leader asking someone to “own” a solution without equipping them with the resources (the Four T’s) needed to succeed. This scenario merely increases stress and creates an impossible situation where responsibility grows but capabilities do not. The host advises leaders to always pair the question “What can you do?” with “What do you need?” to ensure agency is granted. Conversely, those receiving delegation should clarify what resources they require to fulfill the new responsibility.

The conclusion emphasizes that for most listeners’ careers, aiming for full ownership—the pairing of both responsibility and agency—is the most effective delegation strategy, far superior to partial transfers that lead to frustration and inefficiency.

Recommendations

Frameworks

  • Eisenhower Matrix — A prioritization framework mentioned at the start. It’s a four-quadrant graph (urgent/important) used to categorize tasks and decide whether to do, delegate, plan, or eliminate them.

Tools

  • Jam.dev — A sponsored tool described as ‘developer friendly bug reports in one click.’ It’s a Chrome extension that automatically creates detailed bug reports including video, console logs, network requests, and reproduction steps, saving engineers time on debugging.

Topic Timeline

  • 00:00:00 — Introduction to delegation via the Eisenhower Matrix — The episode opens by framing the discussion for new leaders managing overwhelming schedules. It introduces the Eisenhower Matrix (urgency vs. importance) as a common prioritization tool. The host explains the four quadrants and their recommended actions, specifically zooming in on the delegation quadrant for tasks that are urgent but not important. The core idea of delegation is introduced as transferring ownership of tasks to another person, team, or service.
  • 00:02:25 — The flawed mental model of delegation — The host identifies a common mistake in how we think about delegation: we imagine simply moving an item from our matrix to someone else’s matrix, hoping it lands in their important/urgent quadrant. In reality, we often only delegate parts and pieces. This sets up the discussion for two specific ways delegation goes wrong, introducing the framework of ownership being composed of two subparts: responsibility and agency.
  • 00:03:30 — Defining ownership, responsibility, and agency — The host defines the key terms for the episode’s framework. Ownership is defined as full ownership of an item. It breaks down into Responsibility (being accountable for and caring about the outcome) and Agency (having the reasonable ability to operate and make decisions within the solution space). To illustrate agency, the host introduces the “Four T’s”: Training, Time, Tools, and Talent. These are the resources needed to have and prove agency.
  • 00:05:10 — Failure mode 1: Delegating agency without responsibility — The first major pitfall is explored: delegating only the agency to make decisions without attaching the responsibility for the outcome. This leads to a lack of motivation; the person may act only due to a “social contract” or obligation to the delegator, not because they care about the result. This is common in organizations where high-level goals (like OKRs) are not broken down into atomic, practical goals that teams can feel responsible for, causing a breakdown between work and desired outcomes.
  • 00:08:37 — Sponsor break and introduction to the flip side — The episode takes a break to thank the sponsor, Jam.dev, a tool for creating developer-friendly bug reports. After the break, the host previews the second major delegation failure: what happens when you ask someone to own something (delegate responsibility) but don’t give them the agency to operate effectively.
  • 00:11:51 — Failure mode 2: Delegating responsibility without agency — The second pitfall is examined: a leader asking someone to “own” a solution without providing the necessary agency (resources). This sounds empowering but is actually disempowering. If the person’s responsibility grows but their access to the Four T’s (Training, Time, Tools, Talent) does not, they are simply being asked to do more with less, which increases stress and prevents true ownership. The person is responsible for an outcome but lacks the power to affect it.
  • 00:13:59 — Practical advice for leaders and recipients — The host offers practical guidance. For leaders: when asking “What can you do?”, always pair it with “What do you need?” to proactively grant agency. Recognize that asking for resources after being given a task can be uncomfortable for the recipient due to power dynamics. For recipients: it is your responsibility to clarify what agency (resources) you need to accomplish what you’re being asked to own. The goal in most cases should be full ownership.
  • 00:15:11 — Conclusion on the effectiveness of full ownership — The episode concludes by reiterating that for the audience’s careers, aiming for full ownership—the combination of both responsibility and agency—is the most effective delegation strategy, far superior to partial ownership transfers. The host thanks the sponsor again and shares a website update about fixing a bug that prevented access to old episodes.

Episode Info

  • Podcast: Developer Tea
  • Author: Jonathan Cutrell
  • Category: Technology Business Careers Society & Culture
  • Published: 2024-02-16T08:00:00Z
  • Duration: 00:16:23

References

Podcast Info

Transcript

[00:00:00] Let’s say you’re a new leader, you are trying to learn how to manage your overwhelming schedule

[00:00:19] or your long list of responsibilities and you’ve probably been reading about something

[00:00:26] like the Eisenhower matrix. If you haven’t heard of the Eisenhower matrix, the basic

[00:00:30] breakdown is a quadrant four-part graph. And on the x-axis, we’ve talked about this on the

[00:00:38] show before, on the x-axis is urgency and on the y-axis is importance. So you have x-axis would

[00:00:47] be not urgent or urgent and then not important or important. And the idea is that based on where

[00:00:56] you place the different things that you have on your list, you might take different actions

[00:01:03] for those things. So for the things that are urgent and important, do them now. For the things

[00:01:09] that are urgent but not important, you may delegate those. For the things that are important but not

[00:01:16] urgent, plan for those. And finally, for the things that are not important and not urgent,

[00:01:22] delay or offload. Don’t do them. Cancel them. And this gives you this bucket. We want to focus in

[00:01:31] today on the delegation bucket. The idea that you would basically transfer the ownership,

[00:01:42] we’re going to use very specific words today, the ownership of those particular tasks or

[00:01:48] responsibilities to another person or to a team or to a service. So as you begin to grow in your

[00:01:59] career, what may have once been urgent and important may move down to that urgent but

[00:02:05] not important square. Because it is dependent on your context, dependent on your role,

[00:02:12] your responsibilities, your goals, your values. All of these things can play into your prioritization

[00:02:18] scheme. But here’s where we get something wrong. And I want to zoom in again on this delegation

[00:02:25] concept. In our heads, what we imagine that we’re doing, it was we’re taking those items off of our

[00:02:33] matrix and we’re putting them on to another person’s matrix. Presumably, we’re hoping to put them on to

[00:02:40] somebody’s important or important and urgent box. Maybe they are urgent but not important for that

[00:02:49] person and they can find another way to delegate that. But in any case, we’re imagining that we are

[00:02:54] just lifting and shifting those things directly to them. But what tends to happen in reality is

[00:03:00] very different. We tend to only put parts and pieces of those things on to other people’s

[00:03:09] shoulders. We’re going to talk about two specific ways this can go wrong in today’s episode. We’re

[00:03:15] going to define some terms here that we’ll use in sort of a framework. We’re going to use this

[00:03:21] ownership concept to mean a full ownership of whatever that item is. And the two subparts of

[00:03:30] that ownership, the two things that are required to make up ownership is responsibility and agency.

[00:03:38] Responsibility and agency. Responsibility is you are accountable for that thing being done. You

[00:03:45] care about the outcome. You have some stake in the outcome. And the agency is you have the reasonable

[00:03:54] ability to operate within the space, within the solution space, and make decisions that have some

[00:04:00] level of consequence. Those decisions are not being made for you if you have agency. Usually,

[00:04:06] agency comes along with some kind of empowerment to make the agency actually have weight.

[00:04:12] Specifically, I want you to remember the four T’s for the sake of this episode and maybe going

[00:04:18] forward a good framework for you to think about this. Agency tends to be proven through the four

[00:04:24] T’s. The four T’s are training, time, tools, and talent. Training, time, tools, and talent. These

[00:04:33] are the resources that you would need to be able to operate with to have agency. Implicitly, all of

[00:04:40] these things can translate to some kind of monetary value in one way or another. But those

[00:04:45] four things are critical. If they are being provided to you, then you have some level of agency. If you

[00:04:51] have full freedom across all four of those things, then you have a very high level of agency. Okay,

[00:04:57] so with this framework in mind, you have the idea of ownership breaking down to both responsibility

[00:05:02] and agency. You can kind of see where this is going. If you delegate only agency to someone,

[00:05:10] in other words, if you’re only delegating the ability to make a decision about an outcome that

[00:05:18] they don’t have a stake in, there’s no responsibility attached to that, then it’s very unlikely that this

[00:05:26] person will understand any kind of motivation for doing that thing. What will probably happen is if

[00:05:33] they do that thing at all, they’re going to do it through some kind of social obligation to you.

[00:05:39] This is something that sounds like responsibility, may look like responsibility. They are being held

[00:05:45] accountable to you for you asking them to do the thing, so it may look like and feel like

[00:05:51] responsibility, but in fact, it’s not actually true full ownership. You’re still owning the

[00:05:58] thing that you care about the real outcome for. If they could accomplish the social contract that

[00:06:05] you’ve requested for them to accomplish without doing the thing, without spending their time,

[00:06:10] without spending their training or their tools or their talent, if they could do that thing without

[00:06:17] using that agency, they’re likely to fulfill that requirement without actually caring about

[00:06:22] the outcome. That’s not because anybody is nefarious in that particular situation,

[00:06:27] but because the thing that they own is not the thing that you care about. They have only been

[00:06:34] given agency without having a stake in the actual outcome. This tends to happen a lot in companies

[00:06:41] that produce some kind of goals at a very high level, but don’t produce goals that are more

[00:06:47] atomic or at a low level, more practical specific goals for the teams that are executing against

[00:06:53] the higher level things. Because the teams at the lower level can’t necessarily associate the work

[00:06:59] that they’re doing to those higher level outcomes very easily, they have to substitute a different

[00:07:05] responsibility. In other words, they’re doing the thing because, fill in the blank, their boss told

[00:07:11] them to, because they have some obligation to another team. There’s a social contract rather

[00:07:19] than a full ownership. And this creates a breakdown because the outcomes that you care about at the

[00:07:25] high level, they ultimately are going to be accomplished by the work that’s done at the

[00:07:32] lowest level. So those OKRs that you have at the team or at the company level, they are essentially

[00:07:39] meaningless in terms of ownership. Your teams are not going to feel any ownership over those OKRs

[00:07:47] because they can’t see how that work connects to or how those outcomes connect to the work that

[00:07:53] they’re doing. At least that’s true in sufficiently large organizations. So the work to be done there

[00:08:00] to fix that is to try to encourage the full ownership transfer. So you’re not just giving

[00:08:09] agency to people to operate, but you’re also saying, hey, your success is dependent on these

[00:08:16] outcomes. It’s not a social contract between you and your boss. It’s not an expectation that you

[00:08:23] just make somebody happy. It is based on this thing that you now are responsible for. So you’re

[00:08:31] pairing the responsibility with the agency. We’re going to take a quick sponsor break and then we’re

[00:08:37] going to come back and talk about the flip side. What happens when you’re asking somebody to own

[00:08:42] something, but you’re not giving them the agency to operate. Today’s episode is sponsored by

[00:08:57] Jam.dev. Jam.dev is developer friendly bug reports in one click. You may have heard it before. It is

[00:09:04] used by more than 75,000 people. It’s a free tool that saves software engineers a ton of time and

[00:09:11] frustration. You’ve probably received bug reports that are really frustrating. They mean well,

[00:09:18] probably, but unfortunately there’s no console logs, no user ID attached. There’s no replication

[00:09:25] specificity. You know, they may say that they close the window, but you actually care about did

[00:09:30] they use the X button or was it just a tab? Did they quit the browser? This kind of context is

[00:09:39] important for you to be able to solve the bug, but if you don’t have it, it ends up going back and

[00:09:44] forth over weeks in the ticket comments. Maybe it gets lost or drops through the cracks or maybe

[00:09:50] the bug goes away and you have no idea how it got resolved in the first place and then it shows back

[00:09:54] up a few weeks later because actually turns out it wasn’t resolved at all. And Jam.dev helps solve

[00:10:01] this problem. Jam.dev provides the correct guardrails to make sure your teammates are making

[00:10:06] the perfect bug report because they literally can’t do it wrong. It automatically includes a

[00:10:11] video of the bug, console logs, network requests, all the information you need to debug and even

[00:10:18] things like internet speed. It even automatically lists out the steps needed to reproduce the bug.

[00:10:23] And it’s so easy to get your teammates to use because it’s just a Chrome extension. When they

[00:10:28] see a bug, they click a button and right away it creates a ticket in your issue tracker. So

[00:10:33] it saves time for them and it saves you a lot of hopping on calls and meetings to debug.

[00:10:38] Using Jam, you can go from having a bug report that doesn’t have any information that’s relevant

[00:10:43] to having something that’s so descriptive you could make an automated test just by copying the

[00:10:49] attributes from the report. Head over to Jam.dev to get started. It’s totally free today. If you’re

[00:10:56] an engineer, you’d rather spend your time writing code than responding to comments in your issue

[00:10:59] tracker. Send your team to jam.dev. That’s jam, j-a-m dot d-e-v. Thanks again to jam.dev for

[00:11:08] sponsoring today’s episode of Development Team. In today’s episode, we’ve been talking about

[00:11:17] ownership and delegation. We’re using these terms with really specific definitions

[00:11:23] for the sake of the episode. There may be other words that you want to use in place of this,

[00:11:29] but really ownership is a combination of caring about the outcome and having the agency

[00:11:35] to actually do something about it. So we’re saying ownership is a combination of responsibility

[00:11:41] and agency or power. So what happens if you try to delegate but you don’t provide agency?

[00:11:51] What this typically looks like is a well-meaning, perhaps well-intentioned push from a leader.

[00:11:59] Of some kind. Usually, this is the way it goes. A leader is saying, you can own the solution.

[00:12:07] We’re really relying on you to do this. This is part and parcel of your job. We really want

[00:12:13] people at your level owning these kinds of problems. So this is the intention.

[00:12:20] The problem on the backside of that, that sounds a lot like ownership, but it’s missing the critical

[00:12:27] piece, which is how do we actually get this done? If agency is not provided, if that,

[00:12:34] let’s say you’re an engineering manager and you’re being asked to do something or you’re

[00:12:37] an engineer and you’re being asked to own a particular problem. If you’re not able to then

[00:12:42] say, I need X, I need a new tool, I need people, I need time to get that done. If you’re unable

[00:12:55] to say the thing that you’re needing in order to accomplish the thing that you are now responsible

[00:13:01] for, then you lose the full ownership. All that’s really happening is that you’re now stressed out

[00:13:10] about trying to do more with less. The resources you have available to you if you’re in this

[00:13:16] position are now less powerful than they were before because your responsibility list has grown

[00:13:25] but your options list or your capabilities list has stayed the same. If you don’t have the training,

[00:13:32] the time, the talent or the tools to do the thing that you’re being asked to do or you’re being

[00:13:38] asked to do more with the same of those four T’s, those same resources that you have before,

[00:13:44] that really is not providing ownership to that person. It’s just increasing their stress level.

[00:13:53] So if you’re in a position of power and you’re asking for people to own the solution on something,

[00:13:59] my challenge to you is anytime you’re asking someone to do something or asking them what

[00:14:05] can you do, you should always pair this with what do you need. What can you do given some resources?

[00:14:17] If you don’t provide the resource, a follow-up for this, then you’re basically relying on that person

[00:14:25] to then ask for the resources, which may be a reasonable contract that you have with them.

[00:14:30] But recognize that this is a position of power usually that you’re sitting in and someone asking

[00:14:37] you for something after you’ve asked them for something can be a little bit uncomfortable.

[00:14:43] If you’re on the other side of this, if you are on the receiving end of somebody asking you to do

[00:14:47] something, then it is your responsibility to make it clear that in order to do whatever it is they’re

[00:14:56] asking you to do, you may need some agency. All of this, of course, assumes that your goal

[00:15:04] is indeed full ownership. In most cases, full ownership is the most effective strategy for

[00:15:11] delegation. It’s not always the case, but in the vast majority of cases for people who are listening

[00:15:17] to this show in the careers that you’re in, full ownership is going to be a much more effective

[00:15:22] route than partial ownership. Thanks so much for listening to today’s episode. Thank you again to

[00:15:27] jam.dev for sponsoring today’s episode. If you want your bug reports to get much better than

[00:15:33] they are today, head over to jam.dev to get started totally free today. That’s jam.dev.

[00:15:40] This episode and every other episode of developer T can be found at developert.com. I recently pushed

[00:15:45] a bug fix to this. It’s a long standing bug to the developer T website. You can now access all of

[00:15:53] those old episodes that had kind of disappeared or they were actually returning a 404 for quite

[00:15:59] a while that is now fixed. So you should be able to listen to the full back catalog of developer T

[00:16:05] now. Thanks so much for listening. If you enjoyed this episode, please consider joining the developer

[00:16:09] T discord community, head over to developert.com slash discord. Thanks for listening and until

[00:16:14] next time, enjoy your tea.

Visão de gráfico