←back to thread

324 points bilsbie | 1 comments | | HN request time: 0.877s | source
Show context
dcastonguay ◴[] No.44974574[source]
> At the end of it, they were sketching a completely different architecture without my "PMing". Because they finally understood who was actually using our product.

I cannot help but read this whole experience as: “We forced an engineer to take sales calls and we found out that the issue was that our PMs are doing a terrible job communicating between customer and engineering, and our DevOps engineer is more capable/actionable at turning customer needs into working solutions.”

replies(41): >>44974602 #>>44974635 #>>44974655 #>>44974660 #>>44974676 #>>44974814 #>>44974873 #>>44975042 #>>44975156 #>>44975182 #>>44975196 #>>44975269 #>>44975293 #>>44975666 #>>44975685 #>>44975856 #>>44975925 #>>44975972 #>>44976091 #>>44976207 #>>44976426 #>>44976440 #>>44976835 #>>44976924 #>>44977035 #>>44977052 #>>44977553 #>>44978517 #>>44978620 #>>44978689 #>>44979587 #>>44979694 #>>44979713 #>>44980051 #>>44980093 #>>44980149 #>>44980874 #>>44981249 #>>44981402 #>>44982096 #>>44982636 #
crazygringo ◴[] No.44976207[source]
Sadly, I've seen a significant number of engineers who simply don't trust what PM's say about what the customers need.

They think PM's don't provide value, so they ignore what PM's say.

It's only when they hear from customers directly that they go... oh, so these needs are real? I thought it was just PM bullshit.

In a healthy workplace this doesn't happen. But sometimes engineers need to talk to customers to trust that the stuff their PM has been telling them is actually true. And then the relationship becomes more collaborative and trusting.

replies(1): >>44976571 #
1. ◴[] No.44976571[source]