A New Product VP’s 90-Day Checklist

By Rich Mironov May 26, 2016

Individual product professionals drive individual products or services. But vice presidents of product establish the broader context for getting great products built and making them successful. They use a combination of processes, trust-building, hiring, mentoring and cross-functional leadership to help their individual product managers succeed. Since I spend most of my time wrangling product issues at the C-level, here are some thoughts on creating conditions that can unleash great product work.

For context, let’s imagine a newly arrived vice president (or director) of products. She is taking over a product team of five, matched with a development organization of 50. Product roles are poorly defined, priorities are muddy, overall development productivity is uninspiring and there’s lots of griping about how product management isn’t doing its job. What should our heroine put on her 90-day strategic
to-do list?

1. Create and merchandise a minimalist current-quarter priority list. As quickly as possible, she needs a simple, force-ranked answer to “What are our top three priorities this quarter?” This should be obvious but rarely is. Even if it’s only partly correct, the list gives her a way to push consensus among the executive team—which will be critical to everything that follows. An astute negotiator, she gets the executive staff’s agreement that her list is “right enough” and they will back her product priorities. She relentlessly shares this high-level list with her functional partners (development, sales and marketing) to uncover any festering disagreements. (The list is less than a roadmap, and it doesn’t address feature-level choices, but it helps her sort “you don’t agree with my priorities” from “you think my team is failing.”)

2. Become the heat shield for escalations. Our VP won’t be surprised that her team gets five-plus escalations every day from sales, support, customers and prospects. Each of these makes sense in a vacuum, but her individual team members are spending a lot of time defending the current plan from trainloads of seemingly good suggestions. She knows that sales and marketing live in an “and” universe, but development lives in an “exclusive or” universe. Her product professionals straddle the two.

Since she has buy-in to her few explicit priorities, her team can respond more clearly to other requests: “That’s a great idea; tell me more about the customer’s root issue … but we’ll need to put that into the backlog since it’s not one of our top things for this quarter.”

Lots of escalations will ricochet back to her, but she can stand firm on most of the account-specific requests that consume so much development time. She becomes the congenial promoter of “exclusive or” thinking at the executive level, freeing up her team to make more nuanced decisions.

3. Create some job boundaries. She’s certain to discover that every department feels short-changed for product management attention, and the combined set of demands is impossible to meet.

    • “The scrum product owner book says that product management must be at every standup and available to development teams 24/7. Every story needs to be exhaustive, and we need four sprints worth of groomed backlog.” — development
    • “Product management must be on every new customer call and in every technical partnering meeting. Everyone at the company works in sales.” — sales
    • “We need dual-track discovery teams of product + UX + technical architecture in the field at all times.” — innovation/lean strategy
    • “Your team has to staff six industry events next quarter, create four segment-specific product pitches and do weekly webinars.” — marketing
    • “Incoming bugs need to be ranked and sized within a week.” — support

Her individual product managers don’t have enough organizational leverage to fight back against this job-scope creep, and they’ve inadvertently raised expectations by temporarily filling gaps, only to inherit those gaps permanently. Our new VP needs to set general guidelines for her team, which makes this less personal. “I expect that you’ll each spend 60 percent with development; 30 percent with customers, prospects and market discovery; and 10 percent with organizational communications/planning. Trade shows only if you’re speaking. No unqualified sales calls: only train-the-trainer and technical closer meetings. Let’s talk through where that’s challenging, and what I can take off your collective plates.”

4. Build trust, promote cross-functional goodwill and sell the value of product management. Our VP will be frustrated (but not surprised) that almost no one at her company understands what product management does, or how they really add value. Combined with the unbounded job expectations above, her team is often viewed as failing. So she starts a slow-but-steady roadshow for her peers and their departments. This combines basic education (“Here’s how my team helps us build the right products and make money”), active listening (“I’m sure things aren’t perfect. Let’s talk through your issues and pick one to address first”) and endless reiteration of priorities (“Here are our No. 1 and No. 2 deliverables for the quarter. Let me know if there’s anything you would put above No. 1.”) She’s building trust along the way, clarifying that her team is neither rejecting enhancement requests out of spite nor willfully avoiding meetings just to sit around. Her product managers have tons of responsibility but no authority, so they need cross-organizational trust to get anything done.

5. Get development re-energized. She may hear some developer complain about wasted work or erratic priorities. A student of Daniel Pink, she knows that we get the most out of teams through motivation, not force. She’ll work to get development excited about problems and emotionally connected to users. She’ll show that they are working on what really matters to paying customers. And she’ll do it by organizing product/vision sessions specifically for development. (“Real users have these problems. Product and development collectively refine problem statements and collectively find solutions. We want the smartest people in the room to figure it out.”) Engineers start working late because they love to solve meaningful problems.

6. Update the hiring and training/mentoring plan. Our VP has repeatedly inherited untrained, unmentored product teams with the wrong skill sets and in the wrong geographies. She rips up the current hiring plan and job descriptions, which emphasize subject-matter expertise over product management experience. She moves actual product experience to the top of her candidate filter and requires that all new product hires be co-located with their development teams. Then she starts a weekly mentoring/coaching cycle with her current staff, emphasizing organizational collaboration and strategic market understanding. Not all of them are well-suited for product management, but she’ll groom as many as she can. (And help find better-fitting roles in the company for the rest.)

7. Organize market discovery teams. After a month or two, morale is up and escalations are down. Her product teams are starting to find their grooves. Now it’s time to start identifying what the broader market really wants from her product line. Our VP might partner with development to form a part-time market validation team (her best product professional, a UX veteran and a software architect) to validate new product concepts with real B2B users. Or she might push for instrumentation and A/B testing of consumer SaaS improvements. Or maybe oversee a few other lean experiments. Executive-level air cover for these teams is critical, since it’s easy to value current-quarter deliverables above all else and keep postponing real market learning for just another quarter or two.

It’s a lot to do. It’s a good thing our heroine plays the long game, finding motivation in small wins and attitudinal improvements along the road to great products. And revenue. And cross-functional trust.

It’s worth noting that great product professionals can work out some of these issues for themselves (and their teams). But we want them to focus on their specific products and services. It’s very hard to drive organizational change while also building winning products.

Also, some directors and VPs are really player-coaches, managing a small part of the product portfolio themselves while overseeing a team. If you have more than three direct reports, though, you should be focused on this kind of organizational enablement and process improvement — which your staff can’t do for you. Delegate the product-specific work.

Product management leaders have to create an environment where their teams can be successful. That includes a lot of organizational design, behavior modification and relentless focus on the few most important projects.

Rich Mironov

Rich Mironov

Rich Mironov is a seasoned software executive and serial entrepreneur. He has been the "product guy" at six tech startups including as CEO and vice president of marketing/products. He has also consulted to dozens of technology companies.

Rich founded the first ProductCamp and chaired the first product manager/product owner tracks at the Agile Alliance’s annual conference. He is the author of "The Art of Product Management" (BookSurge Publishing, 2008), which collects the best of his long-running Product Bytes blog about software, start-ups, product strategies and Silicon Valley product management.  Rich has a bachelor’s degree in physics from Yale (with a thesis on dinosaur extinction theories), an MBA from Stanford, and provides guest lectures at various business schools about the business of software. He can be reached at rich@mironov.com.

Looking for the latest in product and data science? Get our articles, webinars and podcasts.