Sam and Ryan continue their discussion about the role of product in an engineer's daily working life. They talk about what product gaps are, the symptoms of product gaps on tech teams, and what you can do about product gaps if you're on a team with no product manager.
2:05 – All about productMore product responsibilities fall on engineers than ever beforeCoders can help surface valuable info to business teams about the tradeoffs of their product decisionsLearning product makes coders better because it influences what they code, it increases their chance of building software that will actually be used, and it helps them focus at workThe symptoms of a product gap drives engineers to think that they need to code moreProduct gaps often creep up on medium-size teams that don't have dedicated product managersSymptoms of a product gap:Having three number one prioritiesCoding after hoursTons of work being done, but feeling like you're moving an inch in every directionHard time estimatingYou finish a sprint, and you're not sure what the value was"We just need more engineers"If you're on a team with no product manager, and you have a product gap, what can you do?Ask a lot of questions, and push the product decisions up.Let the whole organization feel the pain of the product decisions that aren't being made.Surface the tradeoffs being made."But this is not my job, I'm an engineer! I just want to code."If you ignore this stuff, your "just coding" won't be sustainableHow to get your engineers out of meetings and firing on all cylinders: a product roadmapMake sure your product cards are not about implementation detailsHow to recognize which decisions you can make as an engineer, and which you can'tWhy you shouldn't say yes to every work requestHow doubling your estimates can surface product issues