|
|
|
|
|
|
by gxs
3212 days ago
|
|
|
As a product manager for one of the big tech companies in the bay area, I agree. Most problems that we solve on a daily basis aren't cutting edge, they are complicated business logic or customer facing UI that needs to be tested more than anything else. Communicating requirements and vision at this point become more important than having your "rockstar" engineers outshine everyone else. That said, one thing I've learned is that you can't please developers. The same people on this forum that are deriding "personal communication" in favor of more formal communication are the same ones that complain about project managers and "unnecessary" status updates and communication. I typically just do whatever the team wants, makes no difference to me whether they like to figure out everything in conversation or desire more formal status updates etc. At the end of the day if I see the team gelling and working at a good clip, I don't mess with them and try to stay out of their way. |
|
|
The same people on this forum that are deriding "personal communication" in favor of more formal communication are the same ones that complain about project managers and "unnecessary" status updates and communication."
I agree with all of your points, except this one. My own view is that managing a technical team is just extremely demanding, and many managers simply aren't up to it. Developers are educated, intelligent professionals who spend a lot of time thinking and talking about a range of specialized technical stuff. If managers can't keep up with their team on their own resources, they end up asking for more of the team attention to compensate. And from the point of the view of developers, that is unecessary communication that they don't get value from.