this post was submitted on 11 Jan 2025
103 points (96.4% liked)

Ask Lemmy

27414 readers
1756 users here now

A Fediverse community for open-ended, thought provoking questions


Rules: (interactive)


1) Be nice and; have funDoxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them


2) All posts must end with a '?'This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?


3) No spamPlease do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.


4) NSFW is okay, within reasonJust remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com. NSFW comments should be restricted to posts tagged [NSFW].


5) This is not a support community.
It is not a place for 'how do I?', type questions. If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.


6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online


Reminder: The terms of service apply here too.

Partnered Communities:

Tech Support

No Stupid Questions

You Should Know

Reddit

Jokes

Ask Ouija


Logo design credit goes to: tubbadu


founded 2 years ago
MODERATORS
 

I’m a business analyst, and a big part of my job involves working with engineers and product managers to gather detailed, in-depth information. For reasons I don’t fully understand (though I have my theories), I often find that engineers, in particular, seem oddly reluctant to share the information I need. This makes the process more challenging than I’d like. Does anyone have tips or tricks for building trust with engineers to encourage them to share information more willingly and quickly?

EDIT: Here's a summary with more details for those who requested more info: I’m working on optimizing processes related to our in-house file ingestion system, which we’ve been piecing together over time to handle tasks it wasn’t originally designed for. The system works well enough now, but it’s still very much a MacGyver setup—duct tape and dental floss holding things together. We got through crunch time with it, but now the goal is to refine and smooth everything out into a process that’s efficient, clear, and easy for everyone to follow.

Part of this involves getting all the disparate systems and communication silos talking to each other in a unified way—JIRA is going to be the hub for that. My job is to make sure that the entire pipeline—from ticket creation, to file ingestion, to processing and output—is documented thoroughly (but not pedantically) and that all teams involved understand what’s required of them and why.

Where I’m running into challenges is in gathering the nitty-gritty technical details from engineers. I need to understand how their processes work today, how they’ve solved past issues, and what they think would make things better in an ideal world. But I think there’s some hesitation because they’re worried about “incriminating” themselves or having mistakes come back to haunt them.

I’ve tried to make it clear that I’m not interested in punishing anyone for past decisions or mistakes—on the contrary, I want to learn from them to create a better process moving forward. My goal is to collaborate and make their jobs easier, not harder, but I think building trust and comfort will take more time.

If anyone has strategies for improving communication with engineers—especially around getting them to open up about technical details without fear—I am all ears.

you are viewing a single comment's thread
view the rest of the comments
[–] Canonical_Warlock@lemmy.dbzer0.com 16 points 5 hours ago (2 children)

I've worked very closely with engineers and I'm engineering adjacent myself. Most of the highly technical types I know in every field (myself included) struggle to talk to people about their job because they no longer know what normal people do or don't know and they don't want to come across as condecendong. Like for me the basic refrigeration cycle feels like something everyone should know but I logically know that actually isn't the case and at the same time I don't know where the laymans actual knowledge on the topic begins. Like do I need to start with explaining that boiling liquids remove heat? Do I need to start with what boiling even is? Do normal people even know that things boil at different temps at different pressures? If I start explaining any of this are they jist going to look at me like I'm an ass and say "Of course I know how thermodynamics works"? Eventually I just decide it's better to not to talk to them.

At the same time though, if you do manage to break the ice with them then you are more likely to sucessfully get a passionate stream of consiousness rant from them because they're passionate and now they know that you can be trusted not to see them as being condescending when they overexplain. Honestly the best way I've found to break the ice with technical types is to get them to start complaining about some part of their job. That also sounds like exactly what you're looking for if you're trying to make their jobs easier. But if they start seeing you as someone who it is safe to complain to then they will start seeing ypu as someone it is safe to talk to about other things.

Also as always there is a relevant XKCD.

https://xkcd.com/2501/

[–] indomara@lemmy.world 12 points 4 hours ago (2 children)

I am the wife of a mechanical engineer, who's brothers are mechanical and electrical engineers, who's parents are electrical engineers, who's best friends are aerospace engineers.

Basically I married into a family of robots, and I agree with this commenter here.

This is the crux of why senior engineers struggle to talk about work I think, and I find the best way for me to get them talking, is to try to learn something small about their work, enough that I can ask intelligent questions, and then listen carefully to the replies.

After a while they open up and I get to listen to the best rants about "special metals" or "systems architecture" or "braking systems in the railway". It's awesome.

It's how I connect with my husband.

The other wives stand in a circle and roll their eyes about them talking about work because they don't understand anything. "Oh there they go, talking about work again."

I decided I didn't want that to be me, and told myself I would listen when they were talking, listen when my husband was working from home. Learn to ask intelligent questions about his work, and eventually, I knew what he was talking about.

Enough that I now freelance in condition monitoring, giving me yet another way to connect with him.

Ask intelligent questions, get excited about the replies, encourage them so they know you won't be insulted when they assume you don't know about and you will have them opening up in no time.

[–] AnarchistArtificer@slrpnk.net 3 points 2 hours ago

This is a really sweet comment that's brightened my day while also being practical advice

[–] Shardikprime@lemmy.world 4 points 4 hours ago

You should always listen to your significant other. Of all the people in the world, they chose you to talk to

[–] Maggoty@lemmy.world 1 points 2 hours ago

Of course I know how thermo dynamics works! But uh if you could just explain it for my friend here, gestures in general direction of dog, that would be perfect.