The 60-30-10 Portfolio Allocation
by Ryan J. Salva • VP of Product at GitHub
Ryan is a product leader with a non-traditional background in Philosophy and English, focused on how humans communicate and create. Previously a Principal PM Manager at Microsoft working on Developer Tools and Azure DevOps, he currently leads product at GitHub, overseeing major initiatives like Codespaces, Actions, and the incubation and launch of GitHub Copilot.
🎙️ Episode Context
In this episode, Ryan J. Salva discusses the fascinating origin story of GitHub Copilot, detailing how it evolved from an accidental discovery to a transformative AI product. He shares deep insights on structuring innovation within large organizations, specifically how to transition 'moonshot' projects from R&D labs to scalable production teams, and explores the ethical challenges of building AI pair programmers.
Problem It Solves
How to balance resource allocation between maintaining current products and investing in future innovation within a large organization.
Framework Overview
A resource management heuristic for product leaders to ensure immediate business needs are met while securing the company's long-term future through high-risk bets.
🧠 Framework Structure
60% Incremental Progress: Iterative i...
25-30% Operations: Maintenance, relia...
5-10% Moonshots: Bold, audacious bets...
When to Use
During annual planning or organizational restructuring to ensure the team isn't trapped in a cycle of purely reactive maintenance.
Common Mistakes
Allowing operational drag to eat into the moonshot capacity, or over-indexing on moonshots without a stable operational base.
Real World Example
Ryan manages his larger product teams at GitHub by ensuring roughly 10% of capacity is ring-fenced for projects like what eventually became Copilot, while the majority focuses on incremental roadmap items.
I certainly try to make sure that we're always reserving some capacity for bold, audacious experimental research projects.
— Ryan J. Salva