| ▲ | p1esk 3 days ago | |||||||||||||||||||
Almost nobody else in engineering did this. What you described is the job of a product manager. Are there no PMs at Google? | ||||||||||||||||||||
| ▲ | Xorlev 3 days ago | parent | next [-] | |||||||||||||||||||
There are, and often times they're stuck in a loop of presenting decks and status, writing proposals rather than doing this kind of research. That said, interpreting user feedback is a multi-role job. PMs, UX, and Eng should be doing so. Everyone has their strengths. One of the most interesting things I've had a chance to be a part of is watching UX studies. They take a mock (or an alpha version) and put it in front of an external volunteer and let them work through it. Usually PM, UX, and Eng are watching the stream and taking notes. | ||||||||||||||||||||
| ▲ | javawizard 3 days ago | parent | prev | next [-] | |||||||||||||||||||
Xoogler here. When you get to a company that's that big, the roles are much more finely specialized. I forget the title now, but we had someone who interfaced with our team and did the whole "talk to customers" thing. Her feedback was then incorporated into our day-to-day roadmap through a complex series of people that ended with our team's product manager. So people at Google do indeed do this, they just aren't engineers, usually aren't product managers, frequently are several layers removed from engineers, and as a consequence usually have all the problems GP described. | ||||||||||||||||||||
| ▲ | stefan_ 3 days ago | parent | prev [-] | |||||||||||||||||||
PM is a fake job where the majority have long learned that they can simply (1) appease leadership and (2) push down on engineering to advance their career. You will notice this does not actually involve understanding or learning about products. It's why the GP got that confused reaction about reading user reports. Talk to someone outside big company who has no power? Why? | ||||||||||||||||||||
| ||||||||||||||||||||