💡

InsightHunt

Hunt the Insights

G

Geoff Charles

Episode #104

VP of Product

Ramp

Execution👥Team & Culture🎯Product Strategy

📝Full Transcript

14,174 words
Geoff Charles (00:00:00): So when I joined, we were about 10-ish folks, about eight engineers, and in three months, we built a competitor to Amex. Six months after that, we built a competitor to Expensify, both publicly traded companies. We hit a hundred million in annual revenue. I think we were under at that point, 50 total in the R&D department, less than four engineers and three PMs. And then we started expanding into accounts payable. It was three engineers, one designer, one PM three months, and they hit out of the park. And that product is moving in billions of dollars a year. I think the recipe for all this is ... Lenny (00:00:32): Welcome to Lenny's Podcast, where I interview world-class product leaders and growth experts to learn from their hard one experiences building and growing today's most successful products. Today, my guest is Geoff Charles, who is VP of Product at Ramp. This episode is a unique glimpse into a startup and an approach to product that optimizes for moving quickly, thinking from first principles, and empowering individual team members. If you're not familiar with Ramp, they're the fastest growing SaaS business in history, getting to over $100 million in annual run rate in two years, which is just wild. And as you'll hear in this episode, they did this with 50 people. In our conversation, Geoff shares how they operationalize a culture of velocity, how they do a lot with few people, how they organize planning, how they define strategy, how they interview product managers and keep a very high bar for talent, plus also avoid burnout in a very fast moving culture and so much more. (00:01:25): My advice is to seriously study how Ramp operates because there's a lot to learn from their success and their approach to product. Enjoy this episode with Geoff Charles after a short word from our sponsors. (00:01:38): This episode is brought to you by Ezra, the leading full-body cancer screening company. I actually used Ezra earlier this year unrel...

💡 Key Takeaways

  • 1Velocity is a quality metric: Moving fast allows for rapid iteration and de-risking of decisions.
  • 2Structure teams as 'single-threaded': Dedicate small pods to one ambitious goal and shield them from organizational chaos.
  • 3Practice 'Context over Control': Leaders should align on goals and data, then empower teams to determine solutions.
  • 4Treat support tickets as product failures: Having Customer Support report to Product aligns incentives to reduce friction.
  • 5Hire for velocity and first-principles thinking: Look for candidates who are frustrated by bureaucracy and want to build.
  • 6Minimize planning time: Any second spent planning is a second not spent doing; focus accuracy only on high-stakes moments.

📚Methodologies (3)

Execution

A framework where small, autonomous teams (pods) are assigned a single, ambitious goal and are completely shielded from external distractions like maintenance or cross-functional meetings until they achieve product-market fit.

Core Principles

  • 1.Single-Threaded Focus: Individuals/teams have only one goal to wake up to; remove all other responsibilities.
  • 2.Shielding: Use Product Ops or rotational engineers to handle bugs/escalations, protecting the core building team.
  • 3.Lofty Goals & Tight Timelines: Motivate teams with massive targets (e.g., 'Build a competitor to Bill.com') and aggressive deadlines.
  • +1 more...

"It was three engineers, one designer, one PM, three months, and they hit out of the park."

#single-threaded#velocity#execution
View Deep Dive →
👥 Team & Culture

Instead of dictating solutions, leaders provide the strategic 'context' (goals, hypotheses, data). The 'contract' with the team is the strategy, and the team is trusted to define the roadmap and solutions.

Core Principles

  • 1.Align Upstream: Debate the goal, the hypothesis, and the data interpretation, not the specific feature solution.
  • 2.The Contract: Establish a clear agreement on strategy/roadmap; as long as the team executes on this, leadership steps back.
  • 3.Repeater-in-Chief: The leader's primary job is to constantly repeat the vision and strategy to ensure alignment.
  • +1 more...

"If you align on the goal, the hypothesis, and the data... the solutions actually can come much better from teams that are much closer to the ground."

#context#control#team
View Deep Dive →
🎯 Product Strategy

A problem-solving approach that involves stripping a problem down to its fundamental truths rather than reasoning by analogy or looking at competitors.

Core Principles

  • 1.Ignore Pattern Matching: Do not say 'At my last company, we did X'. Focus on the unique constraints of the current business.
  • 2.Write to Think: Shut down laptops, use pen and paper to answer a core question simply before looking for solutions.
  • 3.Redefine Roles based on Principles: Structure the org chart to solve specific problems (e.g., Support reporting to Product).
  • +1 more...

"Every support ticket is a failure of our product."

#first#principles#product
View Deep Dive →