Explore / Build the product / Product management

Product management · Starting Up

How do product teams keep a consistent shipping rhythm as they grow?

Separate your planning cadence from your execution cadence and lean on async updates instead of endless meetings. A predictable operating rhythm, what to decide when, and who's in the loop, is what lets teams ship fast without chaos. Rituals should speed up decisions, not become the work.

Go deeper18 sources

  • Shape Up: Stop Running in Circles and Ship Work that Matters

    Ryan Singer · Basecamp / 37signals · Book · free online book

    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.

  • Shipping is your company's heartbeat

    Darragh Curran, Intercom · Intercom Blog · Essay · 8 min read

    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.

  • The safety of speed: How we ship code 180 times per day

    Danny Fallon and Ryan Sherlock, Intercom · Intercom Blog · Article · 12 min read

    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.

  • How Ramp builds product

    Lenny Rachitsky · Lenny's Newsletter · Article · 25 min read

    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.

  • How Linear builds product

    Lenny Rachitsky · Lenny's Newsletter · Article · ~20 min read

    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.

  • How Duolingo builds product

    Lenny Rachitsky · Lenny's Newsletter · Article · 25 min read

    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.

  • Linear Method: Practices for building

    Linear · Tool · Reference site

    A crisp, opinionated set of principles for building software: work in cycles, say no to busy work, keep momentum, and let the tool nudge one good default way of working. Even if you never use the app, the written method is a usable template for a lightweight operating rhythm. Skim it for concrete rules you can adopt this week.

All 18 sources
  • Maker's Schedule, Manager's Schedule

    Paul Graham · paulgraham.com · Article · short

    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.

  • TBM 12/52: The Basics

    John Cutler · John Cutler, The Beautiful Mess · Essay · 12 min read

    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.

  • Building Zerodha with Kailash Nadh

    Utsav Shah · Software at Scale · Podcast · 1 hr · India

    Zerodha, India's largest broker, built almost everything in house with a famously small team, and its CTO explains why owning the core product mattered so much. It is a concrete Indian case of the payoff you get when the thing you sell is software you fully control. Listen for the reasoning about dependencies and ownership, not the scale.

  • Building the Right Operating Cadence

    Travis May · Travis May, Medium · Article · 12 min read

    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.

  • Product Operating Rhythm

    Phil Farhi · Phil Farhi, Coda · Template · Interactive doc

    A ready made doc that lays out planning, review, and communication rituals across weekly, monthly, and quarterly horizons, built by a former product leader. You can copy it and adapt the cadence to your own team rather than starting from a blank page. Useful when you know you need a rhythm but do not want to design every ceremony from scratch.

  • Asynchronous communication for remote work

    GitLab · The GitLab Handbook · Article · 25 min read

    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.

  • How to Plan an MVP

    Michael Seibel (YC) · Y Combinator (YouTube) · Video · ~13 min

    The single most-cited practical talk on scoping a first product, from the person who ran YC's accelerator. It cuts through the theory and shows what an MVP actually looks like using Airbnb, Twitch, and Stripe.

    Watch it here
  • Empowered Product Teams

    Marty Cagan · Silicon Valley Product Group · Article · 10 min read

    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.

  • The Perfect Meeting Cadence: How to Set One for Your Team

    Range · Article · 10 min read

    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.

  • The Cadence: How to Operate a SaaS Startup

    David Sacks · David Sacks, Craft Ventures · Essay · 20 min read

    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.

  • The Rhythm of the Fight: Why a Startup Needs Cadence To Succeed

    Michael Wolfe · Michael Wolfe, Point Nine Land · Essay · 12 min read

    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.