Question 1

What are the key takeaways from Ryan J. Salva's episode on Lenny's Podcast?

Accepted Answer

1. Incubating moonshots within large companies requires ring-fencing an R&D team separate from the core product org, giving researchers creative freedom without the burden of operational fundamentals upfront. 2. Transitioning an R&D project to a productized offering requires moving researchers alongside the project temporarily, then replacing them in seat based on readiness rather than arbitrary calendar dates. 3. The product team closest to the customer must own the roadmap - outsourcing innovation exclusively to an R&D group erodes ownership and disconnects the feedback loop that drives product quality. 4. AI tools should augment human creativity rather than replace it - Copilot's design philosophy as an 'AI pair programmer' shaped both the technical implementation and the ethical guardrails around the product. 5. Portfolio management requires deliberate resource allocation: roughly 5-10% on bold experimental bets, 25-30% on operational maintenance, and about 60% on incremental improvements to existing products.

Question 2

What does Ryan J. Salva say about AI-product-development and innovation-at-scale?

Accepted Answer

"As developers, we love to be in that place where I'm creating things, where I'm focusing on some product, some piece of software that I'm going to give to my customers, my users. The labor of remembering what's the order of parameters that need to come into a particular API, or hey, what's the particular syntax of this thing I'm supposed to do... That's just labor. It's not creating. It's just typing." - Ryan J. Salva "We started experimenting with different user experiences. Do we want it so that you right click and get a little side panel that comes up with a bunch of different options for things that you might want here. That was nice because it would give you whole functions, but it's out of the cursor. You had to really switch over to a different panel, which itself was a little bit distracting. We eventually came to this idea of inline autocomplete." - Ryan J. Salva "Creating the model is one thing, but then figuring out how to use the model in terms of what parameters do you want to adjust for, what do you want to optimize for... When you're in a code editor, you don't necessarily want to type, type, type and then have to wait one second, two seconds, three seconds to get a suggestion back when your entire goal is to stay in the flow. We would run experiments to see how many milliseconds are the right amount such that a developer doesn't feel like they're being interrupted." - Ryan J. Salva

Question 3

What are Ryan J. Salva's views on AI-product-development, innovation-at-scale, developer-experience?

Accepted Answer

Ryan J. Salva: "As developers, we love to be in that place where I'm creating things, where I'm focusing on some product, some piece of software that I'm going to give to my customers, my users. The labor of remembering what's the order of parameters that need to come into a particular API, or hey, what's the particular syntax of this thing I'm supposed to do... That's just labor. It's not creating. It's just typing." Ryan J. Salva: "There are lots and lots of different opportunities for AI to essentially be able to take some of the drudgery out of our work so that we can focus on creative acts. What I hear from developers and what I experience myself is that Copilot kind of forces me to think a little bit more about what are the design patterns I'm trying to create?"

Ryan J. Salva

The role of AI in new product development | Ryan J. Salva (VP of Product at GitHub)

TRANSCRIPT

Ryan J. Salva

The role of AI in new product development | Ryan J. Salva (VP of Product at GitHub)

Ryan J. Salva

The role of AI in new product development | Ryan J. Salva (VP of Product at GitHub)

TRANSCRIPT

Ryan J. Salva

The role of AI in new product development | Ryan J. Salva (VP of Product at GitHub)