StartUp / Founder Story
Explore founder stories, leadership decisions, startup building strategies and entrepreneurial lessons through curated summaries and business intelligence.
The product wisdom every CPO should ignore | Jeremy Epling (CPO, Vanta)
Summary
Jeremy Epling shares his transition from Microsoft to GitHub, emphasizing the importance of adaptability and continuous learning. His experience at Microsoft involved frequent team changes, which fostered a desire to understand various product areas deeply.
At GitHub, Epling highlights the significance of close collaboration with sales engineering teams to enhance product development. He discusses the introduction of usage-based pricing for GitHub Actions, showcasing the need for a holistic understanding of product impact across the business.
Epling defines the role of a Chief Product Officer (CPO) as one that requires attention to detail and a strong connection to customer experiences. He stresses the importance of maintaining a high velocity of feature delivery while ensuring product quality.
He discusses the challenges of managing a growing team and the necessity of understanding absorption capacity to maintain productivity. Epling emphasizes the need for effective communication and collaboration among executives to address challenges and adapt to market dynamics.
Perspectives
short
Jeremy Epling's Insights
- Emphasizes adaptability and continuous learning in product leadership
- Highlights the importance of collaboration with sales engineering for product development
- Defines the CPO role as requiring attention to detail and customer connection
- Stresses the need for high velocity in feature delivery while maintaining quality
- Discusses the significance of understanding absorption capacity in team growth
- Aims to foster a culture of open communication and empowerment among team members
Challenges in Product Leadership
- Managing a growing team can overwhelm productivity and quality
- Balancing speed and quality in product development is often challenging
- High-pressure environments can lead to burnout if not managed carefully
- Misalignment between individual contributors and leadership goals can hinder effectiveness
Neutral / Shared
- Effective communication is crucial for addressing challenges in product leadership
- Understanding market dynamics is essential for adapting product strategies
Metrics
pricing_strategy
usage-based pricing
GitHub Actions pricing model
This shift represents a significant change in how GitHub monetizes its services.
we were doing usage-based pricing. It was the first time GitHub had ever done usage-based pricing on anything.
win_rate
win rates like a metric that I think a lot about
measuring success in product delivery
Understanding win rates helps identify areas for improvement.
I'd say win rates like a metric that I think a lot about
other
the book stops with you
CPO accountability
This highlights the significant responsibility placed on CPOs in product development.
the book stops with you
other
weight on your shoulders
CPO decision-making
Indicates the pressure CPOs face in making critical decisions.
there's just a lot of kind of weight on your shoulders
revenue
ACVs are going down here %
indicates a decline in annual contract values
A decrease in ACVs can signal potential revenue challenges.
I'm worried that ACVs are going down here.
growth
we can still hit the revenue numbers %
assesses the feasibility of maintaining revenue targets
Maintaining revenue numbers is crucial for business sustainability.
Can we still hit the revenue numbers?
product_usage
we've done a big bet on like federal this year
indicates a strategic focus on federal projects
Strategic bets can impact resource allocation and overall business direction.
We've done a big bet on like federal this year.
performance
the more senior you get and I think this doesn't have to be like the C team even below
seniority level in the organization
Understanding performance expectations at different levels can guide management strategies.
the more senior you get and I think this doesn't have to be like the C team even below
Key entities
Timeline highlights
00:00–05:00
Jeremy Epling transitioned from Microsoft to GitHub, leveraging his extensive experience to enhance product development and marketing strategies. His role involved significant changes, including the introduction of usage-based pricing for GitHub Actions.
- Jeremy Epling transitioned from Microsoft to a startup, leveraging his diverse experiences to adapt quickly
- His time at GitHub provided a comprehensive understanding of product and revenue, bridging gaps he felt at Microsoft
- A close relationship with Sales Engineering at GitHub enabled better alignment with customer needs
- Epling emphasized the importance of marketing in product development, enhancing GitHubs value communication
- He introduced usage-based pricing for GitHub Actions, significantly altering their pricing strategy
- Understanding cost of goods sold was crucial for managing product delivery finances
05:00–10:00
The role of a Chief Product Officer (CPO) requires deep involvement in product details to align with customer needs and ensure effective delivery. A successful CPO must balance technical expertise with strategic vision while maintaining strong relationships with the executive team.
- A CPO must stay deeply involved in product details to align with customer needs and avoid confusion
- High delivery pace is essential, requiring a consistent flow of features and understanding loss reasons for improvement
- The CPOs role varies based on CEO preferences for vision and narrative ownership, impacting responsibilities
- Technical understanding of product architecture and SLAs is vital for balancing short-term delivery with long-term growth
- In scale-up startups, a CPO must move quickly and develop a multi-product strategy, making informed decisions on product adjacencies
- Quality and user experience are critical; misalignment on these can hinder a CPOs effectiveness
10:00–15:00
CPOs are responsible for setting the pace and quality of product development while ensuring alignment with broader business goals. Effective communication and collaboration among executives are crucial for addressing challenges and adapting to market dynamics.
- CPOs must independently set the pace and quality of product development, shifting from reliance on higher management
- Effective executive communication requires tailoring technical insights for meaningful engagement across the team
- Collaboration among executives fosters problem-solving for business challenges and aligns priorities
- A product perspective in executive discussions is essential for addressing customer needs and guiding strategy
- CPOs must balance immediate product demands with long-term vision, making tough resource allocation decisions
- Regularly gathering customer feedback is vital for adapting to market dynamics and competitive changes
15:00–20:00
Creating a culture of shared responsibility fosters collaboration and prevents blame in problem-solving. Effective communication between the product and revenue teams is essential for aligning on customer needs and product capabilities.
- Creating a culture of shared responsibility prevents blame and fosters collaboration in problem-solving
- The product team must balance immediate customer feedback with long-term strategic goals to maintain product vision
- A strong relationship between the CPO and CRO mitigates tensions and enhances communication
- Open communication is essential for aligning on customer needs and product capabilities
- Embracing conflict encourages dialogue and leads to better problem-solving outcomes
- Sharing customer insights with the revenue team ensures alignment on market needs
20:00–25:00
Direct communication within the executive team enhances collaboration and prevents misunderstandings. Regular C-suite meetings and data-driven decision-making are essential for aligning on product developments and addressing challenges.
- Direct communication resolves conflicts within the executive team, preventing exhaustion and miscommunication
- Regular C-suite meetings foster transparency, enhancing collaboration on challenges and successes
- Over-communication aligns the team on product developments, preventing misunderstandings
- Data-driven decision-making enables confident choices, informed by product revenue and usage data
- Clear decision-making boundaries prevent ambiguity, ensuring clarity on necessary data
- The fetching rocks concept highlights the need for clear requests to streamline decision-making
25:00–30:00
Annual planning at Vanta involves executives identifying key questions to ensure alignment on critical issues. The CEO plays a crucial role in discerning whether performance issues stem from individuals or systemic problems.
- Annual planning involves executives identifying top questions to align on key issues, ensuring focus and clarity
- Vanta promotes asking tough questions for growth but warns against a constant devils advocate approach that stifles progress
- Peer-to-peer communication is essential for addressing underperformance before escalating to the CEO, improving overall team effectiveness
- The CEO must discern if performance issues arise from individuals or systemic problems to manage effectively
- Engineering is placed under the CPO at Vanta to streamline decision-making and enhance execution speed
- A single accountability point for product and engineering simplifies decision-making and boosts quality