Dec 6, 2023 · 59m · news
Geoff Charles: How To Hire Product Teams & Increase Product Velocity | E1091 · 20VC with Harry Stebbings
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 episode of 20VC, host Harry Stebbings interviews Geoff Charles, VP of Product at Ramp, to explore actionable strategies for building high-velocity product teams, designing strategic roadmaps, and mastering tactical hiring. Geoff breaks down his framework for product-led growth, sprint design, and strategy execution that propelled Ramp's rapid scale.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Harry holds 24% of the talking time here. How this is scored →
Harry as informed peer 2.5 Guest teaching 3.6 Guest disagreement 0.8 Harry pushing back 1.9
speaking balance: gold is Harry, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 49:08 Disagreeing with Shopify's Founder-as-CPO Thesis
Geoff explicitly rejects the premise quoted by Harry from Shopify's VP of Product, arguing that founders can focus on vision and culture while delegating product strategy to empowered tech leaders.
Hardest push from Harry ▶ 20:43 Host Challenges Open Specs vs. SpeedHarry forcefully pushes back against Geoff's open specification model, citing Spotify CPO Gustav Soderstrom and asking how welcoming endless comments on product specs doesn't directly undermine Ramp's core value of speed.
Biggest teaching moment ▶ 39:17 Explaining Why Tech Giants Fail to InnovateGeoff educates Harry on organizational inertia, detailing why incumbents like Google or Stripe struggle to copy agile startups due to short-term board pressures, fixed sales incentives, and legacy engineering structures.
Harry holds his own ▶ 20:43 Citing Industry Leadership on Speed vs TalkHarry demonstrates deep interview prep and industry knowledge by invoking Spotify CPO Gustav Soderstrom to construct a tight counter-argument against Geoff's internal feedback philosophy.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| Welcome and Geoff's Journey into Product | 1 | 2 | 0 | 0 | Harry welcomes Geoff warmly and asks standard interview questions about his entry into product management and how to understand customer pain points. Geoff explains his background and shares best practices for customer discovery. | |
| Career Advice and Finding What Excites You | 1 | 3 | 0 | 0 | Harry asks open questions regarding career advice and early hiring lessons at Ramp. Geoff offers insights on identifying personal motivators and avoiding go-to-market hiring traps at early-stage startups. | |
| Managing and Assessing Performance | 2 | 4 | 1 | 1 | Harry probes on the timeline for evaluating low performers and asks whether stage or category experience matters more. Geoff explains his technique for isolating variables in PM performance and decisively favors stage experience over category knowledge. | |
| Early Stage Focus & Product-Sales Integration | 3 | 3 | 1 | 5 | Harry interrupts Geoff to challenge the premise that pre-PMF startups have sales teams for product to sit with. Geoff clarifies that founders or early PMs must act as the sales function themselves to gather direct customer feedback. | |
| Distinguishing Polite Feedback from True Need | 2 | 4 | 0 | 1 | Harry asks how to parse superficial customer praise from genuine demand, then pivots to asking how Ramp structures two-week sprints. Geoff details Ramp's high-touch customer onboarding tactics and minimal meeting sprint cadence. | |
| Team Autonomy and Accountability | 2 | 4 | 1 | 2 | Harry asks how tasks are allocated and pushes on what happens when employees set low bars for themselves. Geoff strongly advocates treating employees like founders and parting ways with those who lack high ambition. | |
| Preventing Burnout & Strategic Reviews | 2 | 3 | 0 | 1 | Harry asks about the rhythm between sprint cycles and why time horizons expand as a company grows. Geoff explains the necessity of quarterly strategic resets to align GTM teams and build larger marketing moments. | |
| Aligning Product and Product Marketing | 6 | 5 | 2 | 7 | Harry directly challenges Geoff by citing Spotify CPO Gustav Soderstrom and pointing out the contradiction between open spec feedback and fast execution velocity. Geoff counters by separating information gathering from decision-making authority, arguing that clear ownership and disagree and commit prevent slowdowns. | |
| Reusability and Durability of Technology Systems | 2 | 4 | 0 | 1 | Harry asks Geoff to clarify what reusability of systems means in practice and when startups should launch a second product. Geoff explains how Ramp reused core infrastructure from cards to reimbursements and warns against distracting sales teams before achieving PMF on secondary products. | |
| Preventing Jerk-like Product Handoffs | 2 | 3 | 1 | 2 | Harry inquires about managing smooth internal product handoffs and asks if larger companies face real brand downside when new products fail. Geoff outlines Ramp's strategy of testing new products via PLG in lower segments before enabling sales teams. | |
| OKRs vs. Product Strategy | 5 | 5 | 3 | 5 | Harry challenges Geoff's critique of OKRs by arguing that value-based lagging metrics like net revenue retention offer a truer picture of success than short-term leading indicators. Geoff pushes back, explaining that metrics unusable within a two-week sprint fail to align team action with immediate outcomes. | |
| The Core Pillars of Product Strategy | 2 | 4 | 0 | 1 | Harry asks Geoff to break down good versus bad goals and explain Ramp's initial hypotheses. Geoff outlines Ramp's core premise that finance teams needed automated receipt enforcement and cautions PMs against becoming attached to specific solutions. | |
| Conducting Effective Blameless Postmortems | 4 | 5 | 2 | 4 | Harry questions whether startups ever truly have a right to win when giants like Stripe or Google can deploy massive resources. Geoff counters with an analysis of incumbent organizational inertia, board constraints, and GTM friction that prevent big tech from copying nimble startups. | |
| Competing with Incumbents vs. Startups | 2 | 4 | 1 | 1 | Harry asks whether incumbents or new startups pose a bigger competitive threat, and how to evaluate sunsetting features. Geoff dismisses legacy incumbents like Amex as lacking software DNA, emphasizing that fast-moving startups are the real competitive threat. | |
| Case Study: A Failed Financial Integration Hypothesis | 1 | 4 | 0 | 0 | Harry asks Geoff to share a hypothesis of his that failed. Geoff recounts an invoice financing feature where Ramp wrongly assumed accounts payable clerks had the strategic authority to approve business loans. | |
| Intuition vs. Data in Early-Stage Product | 3 | 3 | 0 | 1 | Harry asks about the role of intuition versus data and cites Plaid's CTO regarding AI eliminating traditional UI. Geoff agrees, predicting software will shift from static tables and drop-downs to dynamic, conversation-driven intelligence. | |
| The Role of the Founder in Product | 5 | 5 | 3 | 4 | Harry quotes Shopify's VP of Product claiming a company dies when the founder steps away from head of product. Geoff explicitly disagrees, arguing that founders should focus on vision and culture while empowering distinct product and tech leaders. | |
| Ramp's Tactical Interview and Case Process | 2 | 3 | 0 | 1 | Harry asks Geoff to break down Ramp's interview stages and take-home assignments. Geoff outlines their practical case study method that tests candidate clarity, framework thinking, and ability to influence teams. | |
| Essential Product Skills, Team Management, and Over-Communication | 2 | 3 | 0 | 1 | In a rapid-fire sequence, Harry asks about early product skill spikes, hiring mistakes, and team communication rituals. Geoff advises new PMs to spike in one core discipline and over-communicate with founders to build initial trust. | |
| Personal Ambitions: Why Geoff Prefers Building Over the CEO Role | 1 | 2 | 0 | 0 | Harry asks Geoff if he harbors CEO ambitions. Geoff explicitly declines, explaining that he prefers product building and operating over fundraising and press management, before praising Apple's long-term product strategy. |
Statements from this episode (52)
Founders or First PMs Must Sell the First 100 Customers
“The founder or the first product manager should be selling the first hundred customers.”
Product Managers Should Attend Every Sales Demo to Find Pain Points
“Products should sit with sales and should be in every single sales demo and use the sales process as a way to identify pain points.”
Early Product Teams Should Act Like Professional Services Organizations
“You actually should be like a bit more professional services oriented as a product team earlier on.”
Tailored Products for Design Partners Beat Best-in-Class SaaS Incumbents
“If you actually find one or two design partners and you just build for them, they will love you way more than the best in class SaaS product that's already in the market.”
Product Managers Default to Confirmation Bias in Customer Research
“Oftentimes like product managers, they have an idea and they ask the question to validate their idea and it's actually the wrong idea.”
Product Managers Spend Too Much Time in the Office
“Oftentimes just PM spend way too much time In the office, and I think that that's just a huge downside for your team.”
Ramp's Biggest Early Hiring Mistakes Were in Go-To-Market Roles
“The biggest mistakes were probably on, on on, on go to market earlier on, you know, we hired people who had seen success in growth.”
Startups Should Hire ICs Before Go-To-Market Leaders to Test Strategy
“Be super clear on the strategy, hire and hire more more IC level people who can show you the right path and test whether that strategy is the right strategy for you.”
Evaluate New PMs by Embedding Them Into Existing High-Performing Teams
“For ICPMs on my team, I basically place them in teams that are high performing. And I, and we immediately see whether they are, they're at the bar. So, so you take basically something that is fixed, you add a variable and you, and if anything changes, right, i…”
Freeze Headcount for New Executive Hires for at Least Six Months
“Don't hire executives that will then hire people under them, because that obfuscates a lot of their performance, and so be clear to the leaders that you're hiring, like, you're not gonna have headcount for at least, like, six months. You're gonna have to do th…”
Managers Should Know if a Hire Will Succeed Within Three Months
“I think within three months, you should actually be able to say and figure out, like, is this person gonna hit it out of the park, or is this person not gonna work out?”
Company Stage Experience Matters Far More Than Category Experience for PMs
“I think the category Is not that relevant. You know, I come from more consumer than B to B. And I think that's actually an advantage because you're focusing on metrics. You're focusing on conversion. You're focusing on models like lead scoring and lead routing…”
Early Ramp Teams Manually Logged Into Customer Software to Switch Cards
“We were extremely aggressive in terms of making it super easy for them to switch. And what I meant by that is like, we literally had teams say, give me your old credit cards. I will log in to all of your other software and I will switch your cards for you. I w…”
Let Product Team Members Sign Up for Work Instead of Assigning Tasks
“So don't assign, but have people sign up.”
Ramp Limits Recurring Product Development Meetings to Two One-Hour Sessions
“There are no other meetings that are recurring. In the entire product development process. Those are the only two one hour meetings that happen.”
Ramp Engineers Publicly Self-Assign Sprint Goals and Report Results
“We basically have engineers that sign up and then we post publicly here are our goals and here's who's doing what. And so the scoreboard is super, super clear. And then before the start of the next sprint, we basically go and say, this is what we wanted to ach…”
Leaders Must Treat Employees Like Founders to Build High Autonomy
“Don't treat your employees like babies because they will become babies or you will hire babies or you will meet, retain babies. Instead, like treat them like founders themselves.”
Leaders Must Fire Team Members Who Are Less Ambitious Than the Core
“If you have a core team that's ambitious and you have one person in the team that's not as ambitious as that team, you need to part ways with that person. Because it briefly lowers the bar and everyone becomes demotivated.”
Ramp Holds Quarterly Pod Off-Sites to Prevent Product Team Burnout
“Every quarter we take a step back and we look at, okay, like, what did we achieve in the last three months? We basically have off-sites per, per pod that are, like, customer-centric oriented, and we ask ourselves, like, okay, like, what does incredible look li…”
Early-Stage Startups Must Focus Purely on Shipping Speed
“You couldn't afford to do that earlier on. You would, you just have to have an existential crisis and ship as quickly as you can.”
Ramp Practices Building in the Open With Cross-Team Commenting
“We have a culture at RAMP where even if you're not in the team, you can Advise and leave comments and suggestions to other teams. And we build in the open. And so what I mean by that is like, if you're a salesperson, you can go into my product spec and leave a…”
Ramp Tracks All Negative Feedback and Lost Deals in Dedicated Slack Channels
“I mean, I, we have, I'll tell you, we have Slack channels with every single negative feedback we get from customers. Every time we lose a deal, there's a Slack, like, why did we lose a deal? Who did we lose it to?”
High Velocity Requires Single Decision-Makers and a Disagree-and-Commit Culture
“I think what you need to do, though, is you need to empower the person to make the decision, and when the decision is made, you need to commit, even if you disagree, and you need to align on the outcomes.”
Pre-Product-Market Fit Software Systems Usually Have a 12-18 Month Shelf Life
“When you're pre-product market fit, you know, it's very easy to try to build systems that have extremely long shelf life, and I think you should only do that if they are Very high confidence, meaning like you know that this system is going to be alive for a ve…”
A Startup's Second Product Should Leverage Existing Core Systems
“Because you should typically go after a second product that has you know, economies of scale in terms of systems you've already built.”
GTM Teams Must Stay Single-Product Focused Until Securing Strong Market Share
“So I think that for the majority of the company, You need to be like single product oriented for a very long time until you get to the really good market share. But as a tech team, you actually need to have an R and D department that is constantly shipping new…”
Launch New Products via PLG Before Enabling Sales Teams
“What we typically do is we start at the bottom of the market with product led growth on those products. And so there is actually no like sales and very little marketing. We use that to prove the business case to the sales team. And we continue iterating on the…”
Existing Customers Should Receive Product Betas Before Public Launch
“Market to your customers differently than to the market that your customers should already be probably on a beta before you even announce it to the market.”
OKRs Encourage Political Gaming by Focusing on Metrics Over Strategy
“The reason why I don't like The framework is that it doesn't actually talk about strategy. It just gives a goal and then it just tells the team like, go hit this goal, but there's no thinking on the exec level about like how we can actually achieve that goal a…”
Effective Product Team Metrics Must Be Moveable Within a Two-Week Sprint
“The question really is around metric setting is like, can I As a team, in a two-week sprint, move this metric. And if I can, it's a great metric. If I can't, It shouldn't be part of really our goals.”
Product Teams Should Focus on Only One or Two Goals
“Each team should probably have one, maybe two goals. And then as a tech organization or as a pride team, we try to synthesize those and aggregate those into like three, maybe four.”
Multi-Quarter Repeating Vision Statements Should Not Be Product Goals
“If you see yourself repeating the same goal for like many quarters at a time it's not motivating. And so something that's more like a vision or mission statement should not be a goal.”
Products Usually Fail Because the Underlying Hypothesis Was Wrong
“I think oftentimes PM are enamored with their solution and they're not actually good at defining the hypothesis that led them to that solution. And they just ship this product and the product doesn't work. And then they have to go back and say, like, why didn'…”
Non-Engineering Teams Suffer the Primary Impact of Product Failures
“Oftentimes, you know, when you screw up, it's not the engineering team that, that is affected. It's the customer service team. It's the account manager that had to apologize to the customer.”
Remote Work Erodes Trust Without In-Person Meetings
“Oftentimes trust is eroded if you don't actually meet in person.”
Facebook and Stripe Have Struggled to Expand Beyond Core Markets
“Whether it's like Facebook trying to enter the B to B space, whether it's Stripe trying to actually go from like developers and SME to finance teams in, in, in the enterprise. It's hard. And we actually haven't seen that much success.”
Geoff Charles: American Express Does Not Know How to Build Software
“And like Amex is like, it does not know how to build software. It is an incredible company with an incredible brand and an incredible card and merchant product. But they're a far cry away from being a SaaS company.”
Ramp Invests in and Acqui-Hires Startups as Product Testing Beds
“We invest in new players. We acquire you know, aqua hire great talent. And we actually use that as a testing bed to figure out, like, what's working, and we include that in our product strategy.”
Ramp Has Historically Struggled With Deprecating and Taking Down Features
“At RAMP, we've shipped a lot of things and I don't think we've been like particularly good at like taking things down.”
Geoff Charles Prefers Customer-Segment Feature Flags Over Deprecating Software Features
“I would much rather have a lot of features that we can turn on and off based on the segment and based on the needs and continue testing rather than deprecating.”
Product Teams Should Not Double Down Without Strong Secondary Hypotheses
“Oftentimes, you know, the first hypothesis was your main one, and you might not have a second one that's that strong. And if that's the case, then like, don't double down.”
Early B2B Startups Should Hire PMs With Strong Product Intuition
“So when you're a startup, a B to B startup, like you should hire people with strong intuition or at the very least like strong ideas that they can very quickly invalidate with more qualitative data than quantitative data.”
PMs From Facebook and Google Often Lack Strong Product Intuition
“I've oftentimes you have PMs from, you know, the Facebooks and Googles of the world that are actually just good at testing. And moving metrics, but their intuition oftentimes isn't actually locked into customer research and actual customers.”
Ramp Only Recently Gained Enough Data for A/B Testing
“Only recently do we have enough data to actually, you know, run maybe test only recently do we have enough data to say, To hold teams accountable to more of a lagging metric than the leading one, but it takes a very long time.”
Software UIs Will Shift From Tables to Conversational Interfaces
“So a hundred percent, I think the software is going to look a lot less like tables, graphs, and dropdowns, and a lot more like a conversation Where I release a UI that is extremely dynamic, that abstracts the data that you actually would need to see, and just …”
Founders Do Not Need to Remain Head of Product
“I listened to that and I love that. I don't agree. And again, this is the Shopify, you know, obviously, you know, Toby's like very involved in the product surface area at ramp. I think we have Slightly different approach. I think that the, our founder Eric is …”
Failed Ex-Founders and Early Engineers Carry Ideal Product DNA
“People who were ex-founders that might not have succeeded or early engineers that, that have been coding for a long time that, that, that just want to build great things. And I think you find that DNA that, that really helps.”
Ramp Designs Interview Cases on Lateral Problems to Avoid Work Theft
“We do cases that basically are, like, lateral things about RAMP, so they're about something that we would never do, so that we never really, like, steal people's work, but something that is, like, somewhat relevant to RAMP”
Product Candidates Who Cannot Convince Interviewers Cannot Guide Engineering Teams
“Largely what a product team really does with the engineering design team is like, they're the ones advocating for something and influencing teams. And so if you can't influence me, that this is a good idea. You're not gonna be able to influence the team.”
PMs Must Excel in One Key Discipline Early in Their Career
“You got to spike at one thing. Either you deeply understand technology, so you're an X coder, you know how to code. Either you deeply understand business equations, you're an X VC, or you just read, like, 10 k's for fun, or you're just a deep snob when it come…”
Founders Should Micromanage New Product Hires During Their First Month
“Be a super micromanager the first month and then signpost that with your hire and then step off and step out and be very clear on the outcomes you're trying to drive.”
Ramp Product Team Members Post Public Weekly Goal and Progress Updates
“Monday morning, the first thing everyone on my team tells me, what did they get done last week? What are they going to get done this week? What are the key decisions that they're going to make? And what do they need my help on? And it's public, and so everyone…”
Shorts cut from this episode
▶ Build the perfect 2 week sprint 🙌 · 20VC with Harry Stebbin (@11:58)
▶ How to lead a 2-week product sprint 👆 · 20VC with Harry Ste (@11:58)
▶ Don't treat your employees like babies! · 20VC with Harry St (@15:34)
▶ Most important skill to build in product · 20VC with Harry S (@55:21)
▶ #1 Tip for Managing Remote Workers · 20VC with Harry Stebbin (@38:04)
▶ How to Test Your New Employee (at a fast-growing startup) · (@5:42)