Building & Scaling Product Teams – Feb Event

We’re thrilled to have the wonderful Rich Mironov able to join us for the 1st Product Anon of 2018!

Rich spoke at one of our sessions back in 2014 and it’s awesome to have him back in town.

If you haven’t RSVP’d yet, you’re going direct to the waitlist. This is a very popular session so pop yourself on the list.

If you’ve RSVP’d and can’t attend, PLEASE update your attendance to a ‘no’ so someone on the waitlist (which is about 60 people ATM) can attend. We’ll have a packed house so this is much appreciated!!

In our annual survey, we asked what topics you are interested in & ‘building/scaling product teams’ was #1 so we’ll kick off the year with… How do you arrange the puzzle pieces of roles, responsibilities and people when building or scaling a product team?

Rich’s talk will help us explore:

– Division of labor: how do we grow from one to three to many product folks?
– End-to-end management of product elements/features, or product owner and business owner roles?
– What does a Head of Product do?
– When do startups need to hire a product person?

This will be interactive, there will be some book giveaways and Rich invites us to ‘call BS’ on anything. Hope to see you there!

Our Host:
Big thanks to Zendesk for hosting the evening!


Our Speaker:
Rich Mironov is a 30-year veteran of Silicon Valley tech companies. Rich coaches product executives, product management teams and agile/lean development organizations. He also parachutes into software companies as interim VP Products/CPO to address company-level product/market/leadership issues. Rich has been the “product guy” at six Silicon Valley start-ups including as CEO and VP Product Management. Since 2002, his long-running blog has covered software, start-ups, product strategies, and the inner life of product managers. Rich is the author of “The Art of Product Management” (2008), and founded the first Product Camp. He has a BS Physics from Yale and an MBA from Stanford.

Leave a Reply

Your email address will not be published. Required fields are marked *