Lenny's Podcast / episode intelligence
Speakers in the public record
Claim mix
Evidence policy
Every row below preserves an exact excerpt. Identified speakers are linked; unresolved voices are labeled and excluded from people counts.
Claim ledger
22 published records
01 / recommendation
“Because I work a lot, I try to read things that are completely outside of work. I don't think I can get through any fiction or nonfiction book that's often recommended. So anything that will pull on your heartstrings and try to make you more human. When Breath Becomes Air is a really good one that I often recommend.”
02 / belief
“I know another important ingredient to how you all operate is you really like to empower product teams and give them a lot of control over how they operate and what they build and how they set goals and things like that versus micromanaging them. I think you have this concept of context over control.”
03 / belief
“I think the debate around working hard and burnout misses a key point, which is all about how much impact and how good you feel about the work that you're doing.”
04 / belief
“I think that the contract between me and the team is really their strategy and their roadmap.”
05 / uncertainty
“If you book a time during this time, I'll slap you. And I don't know if I'm allowed to put that into meeting calendar invites anymore, but that actually worked really well.”
06 / belief
“I think where we get to nuances, like user experience improvements, the metric there that I really look at is how many support tickets come in that were due to a customer being confused.”
07 / belief
“I think that I should never really be in the critical path of anything. So largely, I'm not available, but if they really need to get to me, they have my phone number.”
08 / belief
“We've been extremely consistent from the start and I think most of the products that we build, most of the code that we written, is in the customer's hands and hasn't been ripped away.”
09 / belief
“I think the first year of consulting, we just got really good at Excel and Excel shortcuts, and it was a big part of our training.”
10 / belief
“Yeah, it was one of the biggest cultural differences, I think, in Ramp versus other companies that were as a part of where my boss, the CTO, Karim, was extremely hands-off in terms of the actual pride decisions because we were extremely aligned on the goals themselves.”
11 / belief
“I think we've hit a hundred million in annual revenue for the first two years and we've continued to grow significantly since then.”
12 / belief
“I think running a team has a huge impact on your physical health, on your mental health, and I think you are an athlete at a high growth startup or even a small business or a large company.”
13 / commitment
“Marketing can take that product roadmap and create market moments. And ultimately, if your product roadmap doesn't actually hit the goals of the company, then I'm accountable because I've created a system by which I've aligned with each team on why the roadmap is going to hit the goals.”
14 / evaluation
“Basically, our contract is the vision and the priority and a very high-level spec and everything else is pushed on the engineering teams. And I think that's when engineers actually are also able to move even faster because they can create whatever tickets they want, they can break down the work that they want, they are accountable for the projects that they're driving, and that increases trust and moves things faster as well.”
15 / evaluation
“I think there's a constant pushback to like, "Okay, what can we actually achieve?" But you're able to move super, super fast if you have those two things in mind, the market and the revenue goal, because very revenue driven as a company and the designs that can really keep you anchored on what this could look like.”
16 / preference
“That was an awesome answer. And I think as a PM, you often don't want your engineers and designers to have such strong opinions and to be so on top of everything because there's just like, "Oh, no.”
17 / recommendation
“We have product operators that are protecting the PM from the chaos that is documentation and escalations and release management and enablement customer requests. So we have layers of protective tissue to core teams, but I would say for any of these big bets, you basically have to pull folks from different teams and reorganize a sub-team.”
18 / recommendation
“I think we're relating now is any large rock that we have on the roadmap needs to be brought into the product review process, where myself and the head of design are present and giving feedback, but it needs to be structured in a way where you are asking specifically for what type of feedback you need and you're highlighting the key risks and tradeoffs that you're making implicitly in that review.”
19 / evaluation
“People are leaving and coming and teams are shifting and priorities are always adjusting." And she's just like, "This is the problem you want, you want to be going through this because that means you're growing and you're going through hypergrowth because the alternative is much worse where you're not growing and that's much more painful.”
20 / evaluation
“" I think the key is what you said is that you have to actually be proud of it and it has to be something that's meaningful to you because you could work long hours on something that you have no interest in and that does not help and that does lead to burnout.”
21 / evaluation
“For a period of time at Ramp, we created OKRs with financial goals and quotas to some extent for different teams. And that led to just taking a long time to plan because people were trying to make sure there was the right metric, trying to make sure that it was achievable.”
22 / preference
“I stay away from them from a product perspective because, again, I want to focus on velocity, which is just output, which is your roadmap, but they're pretty strong at more of the cross-functional side of things as well as the financial side of things.”