Principles
Durable claims that survive beyond the speaker's biography — each with explicit limits, transferability judgment, and evidence.
Principle
Steadiness is low decision-variance under fire — not always being right
"Steadiness" is decision-variance compression: holding decision-quality constant whether the room is calm or on fire.
Self-audit: when something explodes, do you make the same kind of decision you''d make in a Tuesday meeting? The gap is the work.
“I don't know if I always make the right decisions in that moment, but probably the variance between a decision under fire and one where we're just, like, in a normal meeting is a little bit lower.”Vlad Tenev
“My partner at Sequoia, Andrew, said of you you're the steadiest hand he's ever met.”Brian Halligan
Principle
Speed and quality aren''t a tradeoff — for the best people
The speed-quality tradeoff is a property of average performers, not elite ones. A team built around elite hires can demand both simultaneously.
When a team brings you a speed-vs-quality "or," push back: ask which hires would make it an "and." That conversation is a hiring-bar audit in disguise.
“My experience is you have to demand both. It's like you have to move fast and I don't want any corners cut. If you look at a really good engineer, the best engineers move the fastest and also have high-quality code with no bugs. It's not really a tradeoff.”Vlad Tenev
“I used to call that the tyranny of or. Everyone would bring me or, and I'd be like, How about an and? Just once. Let's do an and.”Brian Halligan
Principle
Tactical vs strategic urgency are different — match the urgency to the certainty
Urgency should match certainty: high-uncertainty decisions reward information-gathering; high-certainty ones reward execution velocity. Misallocating urgency is the dominant decision failure.
For your top 3 unresolved decisions, classify each as uncertain (gather info) or clear-and-aligned (ship). If you''re running clear-and-aligned ones at info-gathering pace, you have a velocity bug.
“I think that there's sort of a difference between the tactical and the strategic urgency. I think that if you have a lot of uncertainty in what the right thing to do is, it makes sense to gather more information. When the right thing to do is clear and everyone is aligned, at that point, you have to move through with maximal urgency.”Vlad Tenev
Principle
Trust is lost overnight, regained over years — there are no magic words
Recovery is structurally asymmetric to loss: a single public failure can drop NPS instantly, while regaining it requires hundreds of small product improvements compounding over years.
Don''t allocate budget to "trust-recovery campaigns." Allocate it to whichever product improvements compound — that''s the only lever that holds.
“It can go from very high to low practically overnight, but the reverse is rare. ... maybe if you have a really big announcement that people get excited about, you'll gain five points of NPS. But the gains are always slower and more gradual than the losses.”Vlad Tenev
“We kind of like look for magic bullets. Like, can we say these magic words or issue a blog post and make everything okay. ... But really what it is is just improving your products over time.”Vlad Tenev
Principle
Build feedback loops to customers — not to Twitter
Direct customer/business feedback is high-signal because it''s grounded in your specific context; analogical advice from social media is low-signal because the conditions never match.
For each major decision in flight, name the customer-feedback signal that would tell you you''re right or wrong. If you can''t, you''re reasoning by analogy.
“I think a lot of the advice that you read and that people parrot around is wrong or misguided. I mean, I wouldn't spend a lot of time just, like, looking on Twitter and gauging how to run your company.”Vlad Tenev
“I try to not even read it, to be honest. Like, I think when I come across it, I actually say, You know, I'm not interested in this.”Vlad Tenev
Principle
Wartime is the default — and ideally internally generated
Operating as if wartime is permanent compresses cycle time and prevents the slack-creep that emerges in apparent peacetime; ideally the wartime is internally generated so it remains under the founder's control.
If your team meeting feels calm, audit whether you''re under-executing. The signal of healthy operating tempo is permanent, not periodic, intensity.
“I think it's always wartime. ... Ideally actually, the wartime is internally created, because then it's under your control.”Vlad Tenev
“I'm sitting around the table with my co-founder or my executive team and it's like, Oh, there's really not too many problems going on right now. And at the time it felt good, but in hindsight I was like, we probably weren't executing aggressively enough.”Vlad Tenev
Principle
Don''t build slack into the system — reprioritize in real time
Slack is wasted human cost; reprioritization is the better mechanism for handling surprise because it forces the org to confront the real opportunity-cost of every project.
Audit whether anyone on your team is on "buffer" projects. If yes, the work isn''t critical — and the people deserve to be on something that is.
“Yeah, we try never to have slack.”Vlad Tenev
“It wasn't free and we had slack in the system and people were just sitting around that could pick up the work, because if you have that you got to make sure those people are contributing. ... There's too many critical things to have people just not working on them.”Vlad Tenev