Vox

Leitura de 13 min

Management Anti-Pattern - Detail Abstraction

Summary

The episode examines a common misconception in management and leadership: the belief that managers should operate at a high level of abstraction, removed from project details. This “detail abstraction” anti-pattern is compared to trying to understand the contents of an opaque bucket of Lego pieces without being able to see inside. The manager, like someone shaking the bucket, can only make guesses about what’s inside—such as estimating project timelines or resource needs—without accurate information.

This approach leads to significant problems, including costly estimation errors, project overruns, and miscommunications between teams. The core issue is the false belief that managers possess a “superpower” or x-ray vision to infer details from vague descriptions. In reality, abstract management cannot replace understanding the actual components of work, whether you’re a manager or an individual contributor working with abstracted collections of tasks.

The solution is not for managers to understand every single detail, but to ensure the “bucket” is transparent. Details must be made accessible, visible, and part of ongoing conversation. This requires building trust with teammates so they can accurately communicate what they’re contributing. Effective management involves collaboration and dispelling the myth that managers can handle orders of magnitude more detail than contributors; abstraction should not be a replacement for detail, but a tool used alongside it.

Recommendations

Services

  • Linode — The episode’s sponsor. Jonathan describes Linode as offering Linux servers with root access starting at $5/month, dedicated CPU plans with reserved physical cores, GPU compute plans for AI/machine learning, 11 worldwide data centers including Sydney, enterprise-grade hardware, S3-compatible storage, and a next-generation network.

Topic Timeline

  • 00:00:00 — Introduction to the management anti-pattern of detail abstraction — Jonathan introduces the episode’s topic by asking listeners to consider who manages details in design and projects. He presents the anti-pattern of managing from too high a level, contrasting it with the misconception that managers should only operate at a zoomed-out perspective. The core problem is identified: managing big pieces devoid of details leads to costly mistakes.
  • 00:02:27 — The Lego bucket analogy for abstracted project details — Jonathan introduces the central analogy: project details are like Lego pieces in an opaque bucket. If you can’t see inside, you can only guess what’s there by shaking it. This mirrors how managers are asked to estimate project chunks without visibility into the actual work components. The point is made that all such high-level estimations are merely guesses until the details are examined directly.
  • 00:05:29 — Defining the detail abstraction anti-pattern and its consequences — The anti-pattern is formally defined as the tendency to abstract away details while assuming repeatable accuracy. The problem escalates when you have even less information—a bucket you can’t even shake. Stacking margins of error from these abstractions leads to major project issues like 2x overruns and inter-team tension due to misaligned responsibilities.
  • 00:07:35 — The solution: transparency and accessible details — The solution is presented: you don’t need to know every detail, but the information must be accessible. This requires a transparent bucket or, metaphorically, building trust with teammates so they can accurately report what they’re contributing. The false belief that managers have x-ray vision to infer details is highlighted as the core of the anti-pattern.
  • 00:08:51 — Applying the lesson beyond managers to all developers — Jonathan notes this anti-pattern applies not just to managers but to any developer working with abstracted collections of details. When you bucket things together without making them small and consumable, you either ignore details or invent non-existent ones. The key is to make details accessible, visible, and part of the conversation.
  • 00:10:04 — Dispelling the myth and emphasizing collaboration — The episode concludes by dispelling the myth that managers can handle orders of magnitude more detail than contributors. Abstract management is not a replacement for detail. Success requires collaboration, making details an ongoing part of shared representation and discussion, not something resolved in a single meeting.

Episode Info

  • Podcast: Developer Tea
  • Author: Jonathan Cutrell
  • Category: Technology Business Careers Society & Culture
  • Published: 2020-01-24T10:00:00Z
  • Duration: 00:11:16

References

Podcast Info

Transcript

[00:00:00] if you’re standing in a building or maybe you’re riding in a vehicle right now i want you to look

[00:00:10] around and think about some of the details the details of why the room is shaped the way that

[00:00:20] it is or whose decision it was to use those particular colors or maybe why is the button

[00:00:27] on the radio where it is whose job is it to manage the details not just in this kind of

[00:00:37] design work but when we’re talking about executing a project whose job is it to manage the details

[00:00:44] and on the flip side the anti-pattern that we’re talking about today what happens when you try to

[00:00:52] manage from too high of a level my name is jonathan

[00:00:57] you’re listening to developer t and my goal on the show is to help driven developers find clarity

[00:01:02] perspective and purpose in their careers and this happens on teams all the time this seems to be

[00:01:12] a misconception about leadership a misconception about management the idea that managers are

[00:01:20] responsible for sitting up at a high level and only getting involved

[00:01:27] when they’re explicitly asked to be involved and otherwise looking at the big pieces of the puzzle

[00:01:36] moving big blocks around on the project timeline for example and while this isn’t totally untrue

[00:01:47] the manager does need to have kind of a perspective that is zoomed out at times it is also not a

[00:01:57] representation of the job of the manager managing the details is indeed important for the individuals

[00:02:05] who are contributing to this project but if the manager tries to manage the big pieces devoid of

[00:02:15] those details then they’re very likely to make some perhaps very costly mistakes think about it

[00:02:24] this way imagine that the smallest piece of the puzzle is the biggest piece of the puzzle and

[00:02:27] the smallest detail in a project is a lego piece and someone hands you a bucket of lego pieces

[00:02:37] and they ask you to tell them about the lego pieces that are inside of that bucket summarize

[00:02:44] what is in the bucket now if the bucket has a lid on it and if it’s opaque then really the only

[00:02:53] information that you’re going to be able to have is from shaking it and trying to

[00:02:57] defer what may be in the bucket other information is going to be totally hidden from you for example

[00:03:03] the color or maybe whether or not some of those lego pieces are broken on the inside of that

[00:03:10] bucket and when you try to manage a large sum of work in this way you’re going to see similar types

[00:03:19] of problems someone may ask you to estimate how long a given chunk of a project is going to take

[00:03:27] for example this is like trying to estimate how many legos are in that bucket and so you might try

[00:03:35] to wrap your head around it pick up the bucket shake it try to pick up a different bucket and

[00:03:41] compare but at the end of the day it’s all guesses until you pour out those legos and actually count

[00:03:50] them so what do we do to fix this problem that’s what we’re going to talk about right after we talk

[00:03:56] about today’s sponsor

[00:03:57] linode today’s episode is sponsored by linode you can do so many things with linode for example

[00:04:05] you can have a nanode plan it starts as low as five dollars a month and this is a linux server

[00:04:12] that you get root access to for five dollars a month just for the learning benefit of that

[00:04:18] it’s worth the five dollars much less the fact that it’s actually a production level server

[00:04:22] you get dedicated cpu plans if you want with physical cores that are reserved just for

[00:04:27] you that means that nobody’s going to be stealing your cycles you can even get gpu compute plans

[00:04:34] that are suitable for things like ai or machine learning and video processing linode has 11 data

[00:04:41] centers worldwide so latency is going to be at a minimum including their newest data center in

[00:04:46] sydney australia they have enterprise grade hardware in these data centers s3 compatible

[00:04:51] storage options and their next generation network linode delivers the best of the best

[00:04:57] the perfect balance of the performance you expect at a price that you don’t and you can get started

[00:05:04] on linode today with 20 worth of credit for listeners of this show head over to linode.com

[00:05:11] developer t use the promo code developer t 2020 as developer t 2020 at checkout thanks again to

[00:05:20] linode for sponsoring today’s episode of developer t the management pattern or anti-pattern that we’re

[00:05:27] talking about today is the management pattern of linode the management pattern of linode is the

[00:05:27] management pattern of linode the management pattern of linode the management pattern of linode is the

[00:05:29] management pattern of linode the management pattern of linode is the tendency to try to abstract away

[00:05:34] details and to imagine that you can do so with some level of repeatability and accuracy

[00:05:45] in other words taking those buckets we were talking about earlier and based on your experience

[00:05:53] with buckets of legos knowing about how many of those legos are going to be used in the future

[00:05:57] those are in that bucket but here’s the problem when you have a bucket that you can’t look into

[00:06:05] in other words when you’re unaware of the details in fact imagine a bucket that you can’t even pick

[00:06:12] up and shake around you have so little information somebody tells you about the bucket from a

[00:06:18] kind of a fuzzy picture that they provide to you realistically you know almost nothing

[00:06:27] about that bucket no matter your experience with previous buckets of legos this one is going to be

[00:06:35] invariably different in some way and maybe you’ll get lucky from time to time and get within that

[00:06:43] 10 percent kind of number of details that you get right about the bucket but most of the time

[00:06:51] there’s going to be some margin of error and when you stack those margins of error you end up having

[00:06:57] perhaps some very big problems for example projects that run two times over what they were

[00:07:05] supposed to run or maybe miscommunications between two different organizations you may

[00:07:13] have a lot of tension between one team and another because one team believes that their

[00:07:17] responsibility doesn’t include something but the other team believes their responsibility does

[00:07:22] include something and this can happen when we create these

[00:07:27] abstractions away from the details and so it doesn’t necessarily mean that you have to get in

[00:07:35] and understand every single detail but what it does mean is that you need to have a transparent

[00:07:42] bucket this simple idea is that the only way for you to understand the units the abstracted units

[00:07:52] is for that information to be accessible in some way

[00:07:57] and sometimes that means that you need to rely on your teammates building trust for example so that

[00:08:04] a teammate can come to you and tell you that they have a hundred legos that they’re going to put into

[00:08:10] the bucket but here is the anti-pattern the belief is that managers should have a superpower or

[00:08:19] some kind of x-ray vision to see what everyone else doesn’t see

[00:08:25] to look into

[00:08:27] those feature buckets or to look into the details and just infer to have a gut intuition

[00:08:35] or to be able to predict based on some very vague descriptions what else may be involved

[00:08:46] and this is problematic and it happens with developers all the time as well by the way

[00:08:51] this doesn’t just apply to managers it applies at any time when you have an abstract kind of

[00:08:57] collection of details and you refer to them at that abstract level when you bucket things together

[00:09:05] and you don’t make them small enough to consume you very often ignore a lot of those details

[00:09:12] they go underserved or maybe you add extra detail that isn’t actually even there

[00:09:19] find a way to make those details accessible visible and a part of the conversation that’s going to be

[00:09:27] very interesting but you have to remember to make it accessible because how are we going to store

[00:09:33] that information and how do we make sure that people are understanding what we are saying

[00:09:38] and what we are trying to do and so thatになります afford to those concepts

[00:09:43] i’m going to start with abstract you can go straight to it maybe you have to use abstract

[00:09:47] to come to the conclusion that you have to bring into conversation where you can then

[00:09:52] add some of the elements you can bring into the process if you were just writing in a document

[00:09:57] can’t just be done in a single meeting it’s an ongoing representation that has to be shared

[00:10:04] it has to be talked about so dispel with the idea that managers can manage bigger

[00:10:10] more hairy levels of detail that they can manage you know 10 times the level of detail that an

[00:10:19] individual contributor could this simply isn’t true we can’t think about our abstract management

[00:10:25] as a replacement for that detail and so this requires that we collaborate

[00:10:32] thank you so much for listening to today’s episode of developer t

[00:10:37] thank you again to today’s sponsor linode with linode you can get 20 worth of credit

[00:10:42] on any of their plans and services by the way those plans start at five dollars a month head

[00:10:47] over to linode.com slash developer t to get started today use the code developer t 2020

[00:10:53] at checkout by the way linode is

[00:10:55] hiring head over to linode.com slash careers to check out their open positions thank you so much

[00:11:02] for listening to today’s episode today’s episode was produced by sarah jackson my name is jonathan

[00:11:06] and until next time enjoy your tea

Visão de gráfico