The roadmapping process is almost always broken. Roadmaps are met with frustration and boredom in equal measure… Different voices in the company want different things. How do we balance competing demands while uniting the organization behind a plan?
Synerzip webinar for product managers (and others) with tips for working with data scientists and DS/AI/machine learning projects.
How do we provide additional context? Understand possible failure modes? Define “done” operationally rather than academically?
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.
There are some fundamental laws of tech product economics (especially software) that should drive executive-level decisions about business and product strategies. It’s easy to forget them, or decide they don’t apply to our special situation. We’ll unpack a few while we share some war stories.
Product managers must be part of the (enterprise) selling process. But selling and learning are hard to do at the same time with the same customer. How do we create separate learning opportunities with a wide range of customers and prospects to deeply understanding markets, segments and fundamental needs?
For those who missed this year’s Agile Alliance conference in Atlanta (July 25-29), Rich gave talks on “Intro to Agile Product Innovation” and “Intro to Agile Product Management.” Both were for general agile audiences, geared to those working on (or coaching) agile development teams, and emphasizing the revenue-generating market side of the software business. LeanUX / Lean Startup practitioners will recognize many of the themes.
I visited Bangalore for a combination of workshops, public talks and client meetings hosted by Confianzys. The trip had a cooking theme: sharing Silicon Valley’s “secret sauce” for innovation and successful products.
Motivating our development teams may be as important for product managers as writing good requirements. A first step is understanding what matters to devs, such as knowing that real users run/appreciate our products.