Rich Mironov will be MC for Australia’s largest product conference in Melbourne (October 17th) and Sydney (October 22nd).
Industrial hardware and enterprise software are both great business, but have very economics, scorekeeping, and development models. To run a strong software business, we may need to retool some operating processes as well as executive assumptions.
A videocast with Mike Belsito of Product Collective about “Moving Up into a Product Leadership Roles”
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?
Software is intangible: it doesn’t have weight or size or per-unit manufacturing costs. But if we’re in the software business, we have to assign units and prices that reflect our value to customers. And we should be mapping out pricing strategy before we start development, not the day before product launch.
How does enterprise product management differ from mass-market consumer product management? We’ll look at organizations, politics and experiments… and why “experiments” mean very different things in B2C and enterprise/B2B.
Holly Hester-Reilly’s Product Science Podcast brings me in for an episode called “The Rich Mironov Hypothesis: Great Product Leadership is Both Subtle and Slow to Pay Off”
My team says that my stories are too short, insufficient. Except when they say I’m long-winded, overspecifying HOW instead of WHAT. What’s really happening? Thoughts on engaging with our teams to unpack issues and work better together.
It’s easy for CEOs to think that they personally are the best-informed people within their companies about what customers need and what markets want. In reality, product and design teams have the time, focus, expertise, and large numbers of non-selling interviews to do more objective validation of product ideas.
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.