Post B2icATVUATZdHwfdOS by Jagahati@noauthority.social
 (DIR) More posts by Jagahati@noauthority.social
 (DIR) Post #B2iXPn5Z957sas1xTs by Jagahati@noauthority.social
       2026-01-27T17:38:57Z
       
       1 likes, 0 repeats
       
       I was recently reminded of some of the best advice I have ever heard for doing technical work in a large organization.“Nobody wants to hear about the details, just show them the baby.”Talk technical details in private with the people responsible for navigating them, not in meetings with a mixed audience. In meetings just shut up and say “We can handle it.” Nobody cares how smart you are, only that when they hand you a problem the problem disappears.
       
 (DIR) Post #B2iZhEwF3QeFnb7LWq by sirjoho@noauthority.social
       2026-01-27T18:04:32Z
       
       0 likes, 0 repeats
       
       @Jagahati this applies to trade work as well. when i hire an electrician I don't need them to prove to me they understand the internal issue. please just fix the issue thanks 👌
       
 (DIR) Post #B2iaSItIB275fSBC3E by justinerickson@noauthority.social
       2026-01-27T18:13:01Z
       
       0 likes, 0 repeats
       
       @Jagahati the only time I explain the details is when it is important for the decision makers to know the pros and cons so they don’t come back to me and say “you told us you could handle it” when they finally understand the con.  If you work in an environment where people share details just so they can flex, I suggest quitting. If you are that person, I suggest doing some soul searching and knock that shit off.
       
 (DIR) Post #B2icATVUATZdHwfdOS by Jagahati@noauthority.social
       2026-01-27T18:32:13Z
       
       0 likes, 0 repeats
       
       @justinerickson yes if you need to decide between a few options and there are defined trade-offs, you will have to explain some…But you should keep that to a minimum, and if possible get all the technical people aligned before the meeting starts.
       
 (DIR) Post #B2idr35SN7QrksMP1k by justinerickson@noauthority.social
       2026-01-27T18:51:07Z
       
       0 likes, 0 repeats
       
       @Jagahati ya. I understand. I just have seen this bite people in the ass.  I have seen people get upset about getting too many details and then turn around and get upset because “why don’t you just do it this way?  Why is this so complicated?!”Or something has trade offs and you want them to know them so they don’t believe something is simply “taken care of”.  But anyone in the tech industry has seen technical people get into the weeds. I get it. You can go too far either way. It’s an art.
       
 (DIR) Post #B2imvuygqdnhdlalXM by mhjohnson@noauthority.social
       2026-01-27T20:32:50Z
       
       0 likes, 0 repeats
       
       @Jagahati For serious problems I came up with a one page briefing format. IIRC a 2x2 grid with - brief text summary of the problem & what we do to solve it- color / shape status of tech, schedule, metric, etc.- 3 or 4 line schedule with status- a metric showing progress to the goalYou can talk one to five minutes with that one page. Read the audience.I made sure you could read the color / shapes on black & white copies too.Lower right, status as of date too.