📖 Book
✓ Link checked
Free
Intermediate
Why we picked it
Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary source, free in full. The antidote to over-planning your roadmap.
From
Basecamp / 37signals
by Ryan Singer
free online book
- Work in short cycles with a cool-down between them.
- Fix time, vary scope, use 'appetites,' not estimates.
- Make bets, not plans; no runaway backlog.
Open
basecamp.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
A short, quotable case that the cadence at which you ship defines your company, and that shipping small and often is safer than saving up big releases. It reframes shipping from an output to the metabolism of the team. Good to send to a co-founder who wants to hold every release until it is perfect.
From
Intercom Blog
by Darragh Curran, Intercom
8 min read
- The frequency at which you ship becomes your company's operating rhythm.
- Small, frequent releases carry less risk than large, infrequent ones.
- Shipping regularly keeps the team, the product, and customers energized.
Open
intercom.com →
📄 Article
✓ Link checked
Free
Advanced
Why we picked it
The mechanics behind a high shipping cadence: small batches, feature flags, fast pipelines, and the safeguards that let a growing team deploy constantly without breaking things. This is the how that makes the heartbeat essay real. Useful once your team is asking what infrastructure and habits a fast cadence actually requires.
From
Intercom Blog
by Danny Fallon and Ryan Sherlock, Intercom
12 min read
- Small batches minimize the risk of any single deploy.
- Feature flags let you ship code continuously and release it separately.
- Speed and safety compound together when the pipeline is built for it.
Open
intercom.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
A detailed look at a team obsessed with velocity: almost no estimating, minimal planning ceremony, and a bias toward shipping as early as possible. It is a real, named example of how a fast growing company keeps rituals light so they speed up decisions rather than becoming the work. Read it to see how far the lean toward doing over planning can go, and decide how much of it fits you.
From
Lenny's Newsletter
by Lenny Rachitsky
25 min read
- Ramp treats planning time as time not spent shipping, and minimizes it.
- Skipping heavy estimation can raise velocity when scope stays small.
- Culture and rituals are designed around one goal: keep shipping.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Linear is a small, largely distributed team that ships a famously polished product, and this breaks down how they organize around projects and keep scope tight. You will see how a lean team stays accountable through clear ownership and shipped work rather than process theater. Relevant because it is a modern example of the visible-output, small-team model working in practice.
From
Lenny's Newsletter
by Lenny Rachitsky
~20 min read
- Teams form around a project, then disband when it ships
- Keep scope small so progress stays visible
- Ownership and shipped work replace heavy process
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Duolingo's VP of Product walks through their planning cadence, org structure, and the team rituals that let many small teams ship independently at scale. It shows what an operating rhythm looks like once you are well past the founding team. Good for seeing how planning and execution cadences stay separate as headcount climbs.
From
Lenny's Newsletter
by Lenny Rachitsky
25 min read
- Many small autonomous teams need a shared cadence to stay aligned.
- A clear planning rhythm lets teams ship without constant coordination.
- Rituals should be few and load bearing, not decorative.
Open
lennysnewsletter.com →
✍️ Essay
✓ Link checked
Freemium
Intermediate
Why we picked it
Cutler argues that cadence and closed feedback loops matter more than any framework, and that rituals should exist to move learning and decisions forward. It is a grounding read on why a kickoff and a learning review beat a wall of ceremonies. Good for pruning rituals down to the ones that actually earn their place.
From
John Cutler, The Beautiful Mess
by John Cutler
12 min read
- Cadence and feedback loops beat frameworks and tools.
- Every ritual should move a decision or a learning forward.
- Without checkpoints and closed loops, a team's system quietly decays.
Open
cutlefish.substack.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
A founder's practical account of designing the recurring meetings and reviews that keep a scaling company aligned, and which ones to drop. He is specific about matching the horizon of a ritual (weekly, monthly, quarterly) to the decisions it serves. A clean companion piece for turning cadence theory into a real calendar.
From
Travis May, Medium
by Travis May
12 min read
- Match each ritual's frequency to the decisions it exists to make.
- Longer time horizons deserve less frequent, deeper reviews.
- Revisit the cadence as the company grows. It is not set once.
Open
travismay.medium.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
This is the operating manual behind the answer's core rule: don't run a remote team on vibes. GitLab runs 1,600+ people across 60+ countries entirely on written, handbook-first, async-default communication, and this page hands you the exact norms to copy from your first hire: document the decision not just the outcome, put questions in a public channel instead of a DM, and treat working-hours overlap and response time as explicit agreements. It is the rare playbook written by a company that actually lives it at scale, so you can lift the practices wholesale into a three-person team.
From
The GitLab Handbook
by GitLab
25 min read
- Async-by-default means the source of truth is written down, so a teammate in another city can act without waiting for you to be online
- Broadcast important decisions in multiple places (channel, email, meeting) because you cannot assume everyone saw the one message
- Set response-time expectations and working-hours overlap explicitly instead of letting them form by accident
Open
handbook.gitlab.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
A free, focused summary of how empowered teams operate: given problems, held to outcomes, and coordinated by a light cadence rather than top down task lists. It is a fast way to grasp the operating model before committing to the full book. Good for aligning co-founders on how much autonomy and how much rhythm your teams should have.
From
Silicon Valley Product Group
by Marty Cagan
10 min read
- Teams own outcomes, not just a backlog of assigned features.
- A light shared cadence keeps autonomous teams pointed the same way.
- Clarity on who decides what, when, is what makes empowerment work.
Open
svpg.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A practical guide to deciding which meetings to keep, which to make async, and how often each should happen. It maps live time to conflict, ambiguity, and real trade offs, and pushes routine status into writing. Handy as a quick audit tool when your calendar has quietly filled with recurring meetings nobody chose on purpose.
From
Range
by Range
10 min read
- Use live meetings for ambiguity and trade offs, async for status.
- Set each recurring meeting's frequency deliberately, then review it.
- A standup can become a written thread and free up maker time.
Open
range.co →
✍️ Essay
Free
Intermediate
Why we picked it
This is the clearest argument for the exact thing your short answer names: run two synchronized systems (a planning rhythm and a launch rhythm) offset from each other so the company always knows what month it is. Sacks shows how a predictable quarterly beat replaces the chaos that growth creates, without hiring a COO to babysit it. You get a concrete calendar you can copy, not a vague call to be more organized.
From
David Sacks, Craft Ventures
by David Sacks
20 min read
- Sync your planning cadence and your execution (launch) cadence, then offset them so each month has a clear theme.
- Predictability is the point. A repeatable rhythm lets the whole company self-coordinate.
- Chaos in a growing startup is usually a missing operating cadence, not a missing manager.
Open
medium.com →
Why we picked it
A veteran founder makes the case that a steady, brisk (but not burning) cadence is one of the highest leverage things a young team can build. He is concrete about how a predictable weekly pulse keeps momentum and morale up even when the work is hard. It is a short, motivating read that frames rhythm as a competitive weapon, not overhead.
From
Michael Wolfe, Point Nine Land
by Michael Wolfe
12 min read
- Aim for a cadence that is brisk but not burning, sustainable for years.
- A regular shipping pulse compounds momentum the way regular training compounds fitness.
- Cadence gives a team a sense of progress even during long, uncertain stretches.
Open
medium.com →
Why we picked it
The essay that explains why one badly-placed meeting can destroy a founder's entire day of building, and what to do about it. Essential mental model for anyone who both makes and manages.
From
paulgraham.com
by Paul Graham
short
- Makers need time in half-day units; managers slice time into one-hour appointments
- A single meeting can wreck a maker's whole afternoon by fragmenting the block
- Batch meetings into designated windows to protect long stretches of deep work
- Founders who both build and manage must consciously switch between the two modes
Open
paulgraham.com →
