Completing a three-post skills model for product owners, partly borrowed from product management… For some projects, product owners need market-facing skills as well as core agile practices (release/sprint planning, story writing, prioritization, backlog grooming). They *may* need to tell economic stories, segment users, design incentives and take a portfolio-level view.
Rich: I’m a product manager writing PRDs, but my features are always de-prioritized when engineering allocates resources. (We have constrained engineering bandwidth). How can I get priority for my features so that my PRD will see the light of day?
— Generating Reams of Unfunded MRDs and PRDs
Basic product owner descriptions assume a best-case situation: clear sponsor/user alignment, obvious project value, willing subject experts, budget authority and rational expectations. What skills do product owners need for real world projects?
How do we reconcile the broad, market-focused scope of a technology product manager with the sprint-level attention to excellence of a product owner? In the first of three posts, I propose a customer diversity scale to identify how much “product-manager-ness” a product owner needs.
“I’m a new MBA who’s just moved out to San Francisco, and am looking for a product marketing job. I worked on analytic tools for banks before B-School, but got a cool internship with a Bay Area social media company here last summer. So I want to work on something more exciting than FinTech. How should I restructure my résumé and LinkedIn profile?
— Recently Moved to the Bay Area with a Respectable MBA”
This year’s Silicon Valley Product Camp (the sixth!) again drew record crowds of product managers and product marketers to share, network, learn and have fun! 600+ attendees came to eBay’s Paypal/San Jose location. I ran a session on Understanding the Next Job Up… and Getting Promoted. We had an energetic (semi-structured) discussion about what individual contributor Product Managers do, how this is different from Director-level and VP Product roles, and ways to address various real-world (political) issues. Some of the more senior attendees offered advice to newcomers. We talked about how to signal that you’re interested in “the next job up” while respecting your current manager. Understanding the Next Job Up… and Getting Promoted from Rich Mironov With a…
When opening up a new product management position (or any job), it’s easy to over-specify what candidates must have. We risk finding no candidates at all, or missing those with unique skills and backgrounds, so it helps to clearly prioritize our requirements.
We did an analysis of job requirements and qualifications for posted product management openings. Previous PM experience, segment expertise and great communication skills are at the top of the list. What if you don’t look like the typical PM hire?
I’ve been tuning an analogy about painters for the last few months, which has become my litmus test for which companies see software strategically – and the kind of talent they attract. First the analogy, in three parts: If you want someone to paint your house, you get a few quotes from house painters. Bids focus on size of house, cost of paint, prep time and ladder time. Good references help, but your decision is mostly about price and availability. If you want someone to paint a portrait of your loving spouse, however, you might prefer a modern-day Renoir to a Cassius Coolidge, even at substantially higher cost and less convenient scheduling. The quality of the work product really matters,…