Product management is hosting a party, not playing chess
11–20 of 42 posts
Re: Product management is hosting a party, not playing chess
#12Re: Product management is hosting a party, not playing chess
#13The second one is more important than the first one. If you don't build the right product, it doesn't matter how well it scales or how it has amazing test coverage or wonderful documentation. To that end, I think that too many managers (and companies) do too much shielding of engineers from customers. If you are just given a figma mockup and told "build this", it's easy to get bogged down for a week with the details of building a search bar at the bottom of the page only to realize that the stakeholders would have been OK with a dropdown select. Better to understand the problem you are solving and the only way to really do this is to have some kind of interaction with customers. As an engineering manager, I try to encourage engineers to get on sales calls and see product demos. When you see it from a high level, you a) almost always notice things that need fixing or can be improved and b) see where the piece that you are working on fits into the larger picture.
That said, I find that many engineers don't want to get on customer calls, and usually there's room for those engineers in an organization as well. For example, "build a new video conferencing service for artists to collaborate" would be a very challenging problem (I think) that is not well defined and therefore requires deep customer understanding. "Make Google searches run with 10% fewer CPU milliseconds" is arguably a much harder problem to solve, but it's so well defined that it really doesn't need customer understanding (setting aside the initial decision about whether it makes sense to work on).
Re: Product management is hosting a party, not playing chess
#14Seems like there are some steps missing between the quoted at the beginning and the outrage in the article. I don’t really understand the specifics of the complaint. My main thought reading the quote at the top is, “you shouldn’t call people ‘neckbeards’”. But it is also true that not all engineers want to talk to customers. Don’t judge a fish by how well they ride a bicycle, and all that. “It takes all kinds” is a b…
My interpretation of the piece so far is that it's suggesting that leaders think about their role wrt to this as like the party host, who figures out how to facilitate socializing by each individual, to make the party successful. Rather than as the chess master, who keeps everything to themself in their head (and there's a lot of pawns).
I'll have to mull that over, but I do have plenty of anecdotes that would seem to support that.
Re: Product management is hosting a party, not playing chess
#15Product Management is hosting a party... ...but the venue owner wants the staff to do insane party tricks instead of buy chips and soda ...and wants to take half the guests off the list because they invited too many people ...and wants to change the theme 12 hours before the party starts, because they're _certain_ the party goers will love this new theme (despite never talking to them) Your job as a PM is to make sur…
Re: Product management is hosting a party, not playing chess
#16My metaphor for product leadership is a Jazz Band: step back and let your players shine.
Re: Product management is hosting a party, not playing chess
#17I think that software engineering is about two things: building things the right way and building the right things . The second one is more important than the first one. If you don't build the right product, it doesn't matter how well it scales or how it has amazing test coverage or wonderful documentation. To that end, I think that too many managers (and companies) do too much shielding of engineers from customers.…
Re: Product management is hosting a party, not playing chess
#18Dealing with these people is like golden gloves boxing. Every other move they make is a head fake or a trap. Before you open your mouth and take one step forward, you better have your back foot planted or else they're going to knock you on your butt simply to gain an iota of competitive advantage in the negotiation. One regrettable word or phrase in a sales meeting, even if it is technically and factually correct, can cost your team hundreds of thousands of dollars.
I don't understand why the author seemingly takes offense that sending an untrained person into a high-stakes scenario isn't something most companies do, or that some neurodivergent people might ethically struggle with personally misdirecting or suppressing technically and factually correct information as part of a business negotiation.
Re: Product management is hosting a party, not playing chess
#19Meanwhile, they never once addressed the central claim of the thing that made them so angry: some engineers aren't ready/willing to be customer facing. Instead they ranted about the benefits of introducing engineers to customers, all of which of course are true, but none of which address the original claim.
The self-importance of this person was beaming straight through my monitor the entire time.
Re: Product management is hosting a party, not playing chess
#20I always have this in my mind, “Life is Tetris; Business is Chess.”