There are some inherent mis-alignments among internal stakeholders that can complicate enterprise product planning and roadmapping. How do we understand these systematically instead of as personal confrontations?
Occasionally building something unique and small for a single customer makes sense. But enterprise software companies can easily fall into the habit of including custom work in too many of their major deals… with disastrous results. This (long) post lays out root issues and possible solutions.
Eric Boduch hosts Pendo’s Product Love podcast. In this episode, we discussed enterprise vs consumer; roadmaps; organizations; chasing competitor features; DevOps; the need for product leaders to “merchandize” what product folks do; and being students of human behavior.
Product Plan is hosting a webinar on successfully managing rapid product growth. Panelists are Daniel Elizalde, Rich Mironov, and Jim Semick. Attendees can submit questions in advance for on-air responses.
Many infrastructure development teams don’t have a product manager. That forces an architect or senior developer to manage a range of responsibilities they are not best equipped to handle: settling conflicting business priorities; internally “selling” the value of architecture; tying technical decisions to business metrics; making connections between software and end user joy.
This interactive workshop with Rich Mironov will help product managers improve their understanding and skills for working with stakeholders, cross-functional teams, executives, and customers. We will frame the main challenges forproduct managers, then look at specific tools/techniques to drive decisions/strategies.
Your different audiences have different (often opposing) goals and incentives, which means they probably want different product decisions and therefore different roadmaps. You need to understand and anticipate their agendas.
What are the questions that various groups really want to ask, and how does that shape our roadmap conversations?