Every resource founders actually use, in one library.

What founders use most, ranked by how many answers lean on it.

1. A detailed look at a team obsessed with velocity: almost no estimating, minimal planning ceremony, and a bias toward shipping... Lenny's Newsletter Article · 25 min read · Starting Up How Ramp builds product Lenny Rachitsky
2. Duolingo's VP of Product walks through their planning cadence, org structure, and the team rituals that let many small teams... Lenny's Newsletter Article · 25 min read · Starting Up How Duolingo builds product Lenny Rachitsky
3. Cutler argues that cadence and closed feedback loops matter more than any framework, and that rituals should exist to move... John Cutler, The Beautiful Mess Essay · 12 min read · Starting Up TBM 12/52: The Basics John Cutler
4. A founder's practical account of designing the recurring meetings and reviews that keep a scaling company aligned, and which... Travis May, Medium Article · 12 min read · Starting Up Building the Right Operating Cadence Travis May
5. A ready made doc that lays out planning, review, and communication rituals across weekly, monthly, and quarterly horizons,... Phil Farhi, Coda Template · Interactive doc · Starting Up Product Operating Rhythm Phil Farhi
6. A free, focused summary of how empowered teams operate: given problems, held to outcomes, and coordinated by a light cadence... Silicon Valley Product Group Article · 10 min read · Starting Up Empowered Product Teams Marty Cagan
7. A practical guide to deciding which meetings to keep, which to make async, and how often each should happen. It maps live time... Range Article · 10 min read · Starting Up The Perfect Meeting Cadence: How to Set One for Your Team Range
8. This is the piece about the conversation itself, so the customer feels heard even when the answer is no. It walks through... Intercom Article · 8 min read · Starting Up The right way to respond to feature requests Paulina Welnic
9. Video · 2 min · Starting Up Focusing is about saying no (WWDC 1997) Steve Jobs
10. This names the failure mode you are trying to avoid: shipping feature after feature and mistaking motion for progress. Perri... Melissa Perri Essay · 6 min read · Starting Up The Build Trap Melissa Perri
11. This is the principle behind the first half of your answer: a request is a proposed solution, so back up to the problem before... Intercom Article · 8 min read · Starting Up Start with the problem to achieve better solutions Stephen Forbes
12. A practical, scripts-included guide aimed squarely at saying no without burning the relationship. It covers acknowledging the... Canny Article · 9 min read · Starting Up How to say no to product feature requests Jenna Potter
13. Elman helped grow Twitter, LinkedIn, and Facebook, and his rule is exactly your short answer in practice. Decide the core... Medium Article · Starting Up The Only Metric That Matters Josh Elman
14. Retention on the exact flow you shipped is one of the signals your short answer names, and this is the hands-on guide to... Lenny's Newsletter Article · Starting Up How to measure cohort retention Olga Berezovsky
15. Cagan draws the exact line at the heart of your question: output is what you shipped, outcome is the result it produced, and... Silicon Valley Product Group Essay · Starting Up Outcomes Are Hard Marty Cagan
16. Tavel gives you a ladder for what working actually means: users completing the core action, coming back, and eventually pulling... Medium Essay · Starting Up The Hierarchy of Engagement, Expanded Sarah Tavel
17. This answers the exact fear behind your question: does keeping code clean slow you down? Fowler separates internal quality... martinfowler.com Article · Starting Up Is High Quality Software Worth the Cost? Martin Fowler
18. Video · Starting Up Ship a feature every week, embrace technical debt, ruthlessly cut scope Gaurav Misra
19. Premature abstraction is a sneaky form of debt that fast moving teams create while trying to be clean. Abramov tells the story... Deconstruct 2019 Video · Starting Up The Wet Codebase Dan Abramov
20. Written by a fractional CTO for exactly your stage, this frames debt as a trade you make on purpose, not a moral failing. It... damiangalarza.com Article · Starting Up What Is Technical Debt? A Pragmatic Guide for Startup Teams Damian Galarza
21. A calm, stage aware walkthrough of when to ignore debt and when it starts to matter. It makes the point that before product... Cockroach Labs Article · Starting Up How to handle early startup technical debt Michelle Gienow
22. A concise, credible reference on why cutting work into small pieces speeds up feedback and lowers risk. Use it to justify... DORA (Google Cloud) Article · ~10 min read · Starting Up Working in small batches DORA (Google Cloud)
23. A tight, opinionated page on shrinking features to their smallest working version and shipping that first. It gives you a... Linear Method Article · ~5 min read · Starting Up Scope projects down Linear Method
24. Amazon's method of writing the outcome in plain language before any code exists, which forces you to make a request someone... Working Backwards (Bryar & Carr) Template · template + guide · Starting Up Working Backwards PR/FAQ template and instructions Working Backwards (Bryar & Carr)

Show the next 24