Lenny's PodcastRyan Singer: Why appetite beats estimates in Shape Up's plan
Through six-week appetites and shaping sessions with engineers in the room; Shape Up teams stop shredding scope into tickets nobody understands.
At a glance
WHAT IT’S REALLY ABOUT
Ryan Singer explains Shape Up: timeboxed, collaborative, reality-based product delivery
- Ryan Singer, longtime product leader at 37signals/Basecamp and author of Shape Up, breaks down a practical alternative to Scrum and traditional Agile for planning and shipping software. The core of Shape Up is working backward from a fixed time budget (“appetite”), deeply shaping solutions with product, design, and engineering in the room, and then giving small teams end-to-end ownership to build without constant rituals. Singer contrasts Basecamp’s unique environment with most companies, emphasizing how to adapt Shape Up to “real life” constraints like non-coding designers, entrenched Scrum, and multiple stakeholders. The conversation spends significant time on how to run effective shaping sessions, when to consider Shape Up, common failure modes, and how this shifts the PM role upstream toward problem definition and product strategy.
IDEAS WORTH REMEMBERING
5 ideasStart from appetite, not estimates.
Instead of asking, “How long will this take?”, decide upfront how much time the business is willing to invest (e.g., two, four, or six weeks) and then shape a solution that can realistically fit within that fixed time budget.
Shaping must be collaborative and technical, not just docs or Figma.
Effective shaping isn’t a solo PM-writing-PRDs exercise; it’s a live, collaborative working session where product, design, and a senior engineer explore solution options, stress-test ideas, and surface hidden complexity before committing engineering time.
Define clear, bounded problems before designing solutions.
Broad asks like “build a calendar” must be narrowed to a specific problem (e.g., “our users can’t see free time slots”) so teams can reason about trade-offs, scope, and feasibility instead of chasing an ever-expanding concept.
Avoid shredding projects into tickets before the team understands the whole.
Shape Up rejects the “paper shredder” of decomposing work into dozens of tickets written by non-builders; instead, teams receive a cohesive, well-shaped concept and create their own implementation tasks and scopes (often ~9 major chunks).
Use timeboxes as a maximum horizon, not a rigid six-week dogma.
Six weeks is a practical upper bound for most substantial features, but the core idea is having a fixed, short horizon you can see across—some work may need one, two, or four weeks depending on size and context.
WORDS WORTH SAVING
5 quotesWe are not going to start something unless we can see the end from the beginning.
— Ryan Singer
We’re not going to take a big concept and then say, ‘What’s the estimate for this thing?’ We’re gonna go the other way around and say, ‘What is the maximum amount of time we’re willing to go before we actually finish something?’
— Ryan Singer
You can have the most beautiful rendering of the new bedroom, but if you haven’t checked if there’s electricity in that wall, it’s going to drastically change the cost and the time.
— Ryan Singer
If you have a feature factory that’s continually cranking out features, you’re probably quite healthy. Most teams aren’t even shipping reliably enough to be a factory.
— Ryan Singer
Changing is really hard. If the unfamiliarity of Shape Up is the big problem, maybe things are still fine—wait until it hurts more.
— Ryan Singer
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome