Product Management Auckland and Pushpay are hosting this 2o February talk on building and scaling product management teams. We will focus on initial product hires, division of labor as teams grow, and owning end-to-end bits of value.
Enterprise (B2B) sales teams deal with the world one account at a time; product managers deal with whole customer segments. This naturally creates some friction, which good companies anticipate and manage.
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?
The software bits we release are not the whole product, but a part of the product. We need to make sure we ship a whole product, which includes a compelling story of interest to customers. Strategy, segmentation and customer joy matter.
Rich offered this one-day workshop for 12 participants in New York on August 15th. Agenda included product managers/product owners, portfolio thinking, and how to manage executives/stakeholders. Attendees get to revise the agenda, adding topics about “your first week on the job” and “how to say NO nicely.”
As data-driven product managers, we’d like to pretend that incoming technical requests are simply transactional. In the real world, though, real people and real agendas are involved. And that means there’s a personal and political context to consider when prioritizing demands on our already-overloaded development organization.