Hey software engineers! What's something you'd like your *product manager* to know? Could be about working better with you. Could be about something you'd love to see in how the team works. Could be anything. Leave a comment and let us know. #softwareengineering #productmanagement
Trust is the most important element in any relationship. It might even be the essence of relationship. And it's certainly crucial to the developer - product manager relationship. For product managers, that usually means being open and honest about the team's work, and keeping their word. It might sound like any of these: - "We've got user testing sessions coming up next week, and it's possible that this part of the project might change as a result." - "I'd love to say that we can come back and improve this code later, but let's be honest - given the other priorities, we probably won't have that chance." - "We still don't know how well this product is going to resonate with the market, so we need to stay flexible for now." And likewise, the same open, honest, and trusty-worthy elements apply the other way around. But I'll let the product managers speak to what that would look like! Thanks for always setting such a great example in these areas yourself!
OKR's aren't all supposed to be boolean values. And if all of your key results read like an objective… You're letting the cats herd you.
Software is hard. Phrases like “can’t we just . . . ?” make it sound easy/simple/fast, but they hide the inevitable complexity, which leads to disappointment when things take longer. It’s better to assume there will be some hidden complexity and set up the team to surface the risks early. This reduces risk and sets everyone up for success.
Tagging some of my fave engineers here: Jacob Rakidzich, Brandon Williams, Jonathan Beebe, Dave Leeds