Lenny's Podcast• Mar 30, 2025• 1:45:09Interview

A better way to plan, build, and ship products | Ryan Singer (creator of “Shape Up")

From Lenny's Podcast

Ryan Singer•Creator of “Shape Up”

Executive Summary

The ShapeUp methodology, developed at Basecamp, is an alternative to Agile/Scrum that focuses on shipping meaningful work within fixed time budgets (up to six weeks) called 'appetites'.
A core practice is the 'shaping session,' where a small, cross-functional team de-risks a project by defining the problem, exploring solutions, and identifying technical unknowns *before* committing to build.
ShapeUp promotes team autonomy and forces trade-offs through a 'circuit breaker' principle, where projects not on track to finish within the cycle are canceled by default.
Adopting ShapeUp requires a cultural shift, particularly for Product Managers, whose role moves 'upstream' from writing detailed specs to focusing on business context and problem framing.

12 quotes

Concerns Raised

Teams may fail to involve engineers early and deeply enough in the shaping process.
Product managers might revert to old habits of creating overly detailed specs (Figma, PRDs) instead of shaping at the right level of abstraction.
The cultural shift required, especially regarding team autonomy and the PM role, can be difficult for organizations to implement.
Leaders are often hesitant to publicly admit their shipping processes are broken, which can stifle the initial conversations needed to consider alternatives like ShapeUp.

Opportunities Identified

Ship meaningful, complete product increments predictably within fixed six-week cycles.
Significantly reduce project risk by identifying technical unknowns and 'rabbit holes' before committing development resources.
Increase team autonomy, ownership, and morale by providing well-shaped problems and the freedom to solve them.
Shift product management focus toward more strategic work on business context and problem framing.

Key Themes

The ShapeUp Methodology

ShapeUp is a product development framework that uses fixed six-week cycles and defined 'appetites' for work, rather than sprints and backlogs. It prioritizes shipping finished, meaningful features predictably by strictly limiting the time investment for any given project.

It offers a compelling alternative for teams feeling burdened by the ceremonies, estimation overhead, and perpetual 'sprint-to-sprint' nature of traditional Agile and Scrum methodologies.

Upstream De-risking and Shaping

A critical phase in ShapeUp is the 'shaping session,' where product, design, and engineering collaborate to define a problem and sketch a solution at the right level of abstraction. The goal is to identify and solve for major risks and 'rabbit holes' before the project is approved and handed to a build team.

This upstream work prevents teams from discovering critical flaws or underestimations late in the development cycle, which is a common cause of project delays, scope creep, and team burnout.

Redefining the Product Manager Role

In a ShapeUp environment, the Product Manager's role shifts from a 'downstream' focus on writing detailed PRDs and managing backlogs to an 'upstream' focus on business context and problem framing. They become key participants in shaping the work, rather than dictating its implementation.

This shift empowers the build team with greater autonomy and ownership over the solution, while allowing the PM to focus on more strategic work that connects development efforts to business goals.

Basecamp's Counter-intuitive Culture

The development of ShapeUp was influenced by Basecamp's (37signals) unique culture of slow, deliberate hiring, avoiding VC funding, and integrating skills (e.g., designers who code). This environment fostered a focus on sustainable pace and shipping quality work without the pressures of hyper-growth.

Understanding this context helps explain why ShapeUp values calm, focused work and provides a model for how organizational philosophy can directly shape development practices.

Common Adoption Pitfalls

The primary failure mode when adopting ShapeUp is insufficient collaboration during the shaping process, such as product teams creating detailed specs without engineering input. This undermines the core goal of de-risking and can lead to the same problems ShapeUp is designed to solve.

Teams considering ShapeUp must recognize that it's a fundamental shift in how work is defined and requires breaking old habits, particularly the separation between 'planners' and 'doers'.

Get started free

Topics

ShapeUp Methodology Product Development Agile Alternatives Scrum Alternatives 37signals Basecamp Ryan Singer Product Management Project Management Software Development Lifecycle (SDLC)Six-Week Cycles Appetite-Based Planning De-risking Problem Framing Team Autonomy Ruby on Rails Bootstrapping

Processed Apr 3, 2026 yt-dlp + mlx-whisper + Gemini