Read the original at Lenny’s Newsletter ↗lennysnewsletter.com · subscriber post
By Lenny Rachitsky · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
Lenny Rachitsky answers a reader's question about team speed by compiling a list of roughly fifteen tactics drawn from founders, his own experience, and community input. The core argument is that velocity matters (though not above impact or choosing the right problems), and that leaders should pick one or two tactics to test each month or quarter.
Subscriber post — summary only01Key takeaways
- Speed matters but should not outrank impact or choosing the right problems to solve.
- Narrowing team focus tends to improve how well the remaining work gets done.
- Syncing more often, with short decision-oriented meetings, helps unblock work faster the quicker you need to go.
- Cross-functional teams with resources to ship and clear outcomes, plus earlier engineer involvement, reduce translation loss and speed delivery.
- Test one or two velocity tactics per month or quarter, measure whether they help, and iterate.
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.