Nov 1, 2017 · 33m · saastr
What a Great VP of Product Really Does | SaaStr
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this SaaStr panel hosted by Satya Patel, seasoned SaaS product executives Ciara Peter, John Strauss, and Zach Smucha examine the strategic responsibilities, hiring triggers, team structures, and operational frameworks essential to the VP of Product role.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
Jason as informed peer 4.8 Guest teaching 2.1 Guest disagreement 0.0 Jason pushing back 0.0
speaking balance: gold is Jason, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 9:30 Trap of non-product CEOs thinking they don't need a VP
In an otherwise collaborative panel, John directly rejects the naive assumption of non-product founder-CEOs who believe their generic vision is sufficient without a dedicated product function.
Hardest push from Jason ▶ 18:52 Clarifying pod longevity and structureSatya presses John on whether cross-functional product pods should be permanent, long-living teams rather than ad-hoc, temporary project units.
Biggest teaching moment ▶ 13:24 De-prioritization data loop for foundersCiara educates the audience and host on managing visionary founders by demonstrating how the VP of Product must use quantitative user analytics to justify de-prioritizing founder pet projects.
Jason holds their own ▶ 6:14 Shit umbrellas and credit funnelsSatya synthesizes his deep operating experience to define great product leadership as shielding the team from executive disruption while deflecting all praise to individual contributors.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Jason as informed peer | Guest teaching | Guest disagreement | Jason pushing back | Why |
|---|---|---|---|---|---|---|
| Welcome and Panelist Introductions | 6 | 1 | 0 | 0 | Satya Patel opens the panel by introducing the guests and asking what defines the VP of Product role. After the panelists offer their frameworks, Satya actively shares his own product leadership model ('mobilize, prioritize, optimize, and recognize'). | |
| Characteristics Distinguishing Great Product Leaders | 6 | 1 | 0 | 0 | The panel discusses characteristics distinguishing great product leaders, such as being the oil in an engine rather than the sand. Satya validates and enriches the dialogue by adding the adage that great VPs of product act as 'shit umbrellas and credit funnels'. | |
| Ideal Backgrounds and Foundational Traits for Product Leadership | 5 | 2 | 0 | 0 | Ciara details a Venn diagram of product disciplines while John highlights hiring from customer support for product taste. Satya caps the discussion with his perspective that product leadership is 'more attitude than aptitude'. | |
| Timing and Trigger Points for Hiring a VP of Product | 4 | 3 | 0 | 0 | Satya prompts the guests on the timing and signals for bringing in a VP of Product. The guests outline operational metrics such as reaching 100 customers and founders running out of capacity to translate vision into tactical tickets. | |
| Managing the Relationship Between Founders and Product Leaders | 3 | 4 | 0 | 0 | Satya explores how product leaders manage strong-minded founders. Ciara presents her 'idea ROI feedback loop' and explains the importance of proving why certain items are de-prioritized with user data. | |
| Organizational Placement and Cross-Functional Alignment | 4 | 1 | 0 | 0 | Satya asks where product should report within the company. John and Zach provide nuanced takes on reporting structures, emphasizing mutual trust with engineering leadership over rigid org charts. | |
| Structuring Cross-Functional Pods, Design, and Marketing | 4 | 2 | 0 | 0 | The panel explores team topology, pod structures, and where design should sit. John details long-living pods with shared backlogs, while Satya seeks clarification on whether these pods remain permanent. | |
| Execution Processes, Cadence, and Product Velocity | 6 | 3 | 0 | 0 | Panelists share concrete operational practices like retros, OKRs, and PDRs to maintain velocity. Satya contributes his favorite tool, the documented user story, and explains how it aligns teams during retrospectives. | |
| Hiring and Evaluating Standout Product Managers | 5 | 2 | 0 | 0 | The panel details interview techniques and evaluation criteria for PMs, including reviewing requirements documents and testing context switching. Satya concludes by sharing his network hack of interviewing PM direct reports to vet VP candidates. |
Statements from this episode (18)
Smucha: VP of Product boils down to strategy, velocity, and go-to-market
“What's the role of a VP product? I think it's really boils into three things. One is strategy, making sure the company really knows what it's doing. Who they sell, what they sell, how they sell, manage that process over time. The second thing is the minutia of…”
Stross: VP of Product must say no while maintaining team belief
“The VP of product is the choke point in a lot of ways for the whole company, where you're listening to all the different things coming in, whether it's requests from customers, or future customers, or what your engineering team thinks that needs to be done, or…”
Peter: Product leadership rests on conductor, communicator, and coach roles
“I'd say that there are probably like three roles within the VP of product. So the conductor, the communicator, and the coach. I call these like the three C's of product leadership. And what that means is like, as a conductor, you're, you know, the product is y…”
Smucha: Product teams must actively support sales deals and customer renewals
“In my mind, the product team needs to be the team that supports sales, support new deals, support saving and renewal.”
Stross: Great product managers lubricate teams while bad ones grind progress to a halt
“Great product manager is like the oil that makes everything go well. And bad product management is the sand that makes everything stop.”
Patel: Great product VPs act as shit umbrellas and credit funnels
“Great VPs of product are, ah, shit umbrellas and credit funnels. Right? Like, they protect their teams and make sure that if there's great work being done, it's never their own work, it's the work of their teams.”
Stross: Greenhouse hires product managers out of its customer support team
“Something we've done is, like, we've hired a bunch of people out of our customer support group. Folks, because we saw that they knew the customer backwards and forwards and had good instincts as to, like, what they liked and didn't like. They knew the product …”
Stross: Visionary founders without product backgrounds struggle to direct engineering tasks
“The trap that companies will fall into is, ah, that you've got the CEO with some vision of, like, here's this customer problem, and I'm gonna build this product. But they've never actually been a product person, and breaking down that kind of generic vision in…”
Smucha: B2B SaaS startups must hire a VP of Product at 100 customers
“I think when you get to a hundred customers, you just have to do that, right? If you're a SaaS B to B, of course. Before that, you could compromise depending how deep the founder and the CTOs are in the product.”
Peter: Explaining deprioritization to CEOs is more critical than explaining prioritization
“Most founders are going to have the big idea to start the company, and they're going to have many ideas that are all top priorities, and so I think it's the job of the VP of product to be able to not just prioritize those ideas but really do the analysis and g…”
Smucha: Technical product leaders must not report to non-technical executives
“If you want to empower somebody to really define the strategy, he needs to kind of like have that power and access, and that relationship with the VP of Eng that are kind of like love-hate in a way sometime.
so if you wanted to be successful, just give them t…”
Peter: Enterprise design should sit within product due to shared goals
“I think in an enterprise, ah, organization where you have a different buyer and a different end user, you might have like four, you know, three, four percentage you work with. I think it's okay for design to be nested within product because you really have the…”
Stross: High shipping velocity dramatically eases feature prioritization trade-offs
“Velocity is kind of everything. Like, if I know I can ship 20 things a quarter, I have to stress way less about the priority of those 20 things. If I'm like, ah, maybe I can do three, then it's like a bloodbath deciding which three I'm gonna do.”
Peter: Direct customer interaction makes engineering trade-off discussions significantly easier
“Complete a hundred user research activities per quarter, and then engineers either spend a day with support or they do three sales calls. And the reason I'm, the reason I think this actually has a lot to do with process is that you know, everyone has these lik…”
Peter: PM candidates should submit sample PRDs to prove goal clarity
“We ask of designers to see their portfolio. We ask of engineers to do a code exercise, but we don't really ask anything of product managers. And so, you know, I think asking to see a requirements document or any, you know, if they're, you know, senior person p…”
Stross: Greenhouse tests PMs by having them spec third-party product features
“We do do a project with them, where we say, like, I'm looking for the kind of product sense, so we'll say, take some product that you use that's not ours, and have some complaint with it, and spec a feature to improve it. And then tell me why they haven't buil…”
Strauss: Find high-signal product hires by asking engineers who they loved
“Engineers typically very, ah, opinionated about product folks, and frequently in a negative way, and so when you go to engineers and say who's the product person you've worked with, who you loved you get pretty meaningful answers.”