Mar 30, 2025 · 1h 45m · lennys-podcast
A better way to plan, build, and ship products | Ryan Singer (creator of “Shape Up")
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Shape Up creator Ryan Singer joins Lenny Rachitsky to unpack an alternative operating model for product development that trades open-ended sprint estimates for fixed appetites, upstream shaping rituals, and autonomous execution cycles.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 18.9% of the talking time here. How this is scored →
Lenny as informed peer 4.8 Guest teaching 4.9 Guest disagreement 2.3 Lenny pushing back 1.8
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 1:13:40 Wait until it hurts more
Ryan bluntly dismisses hesitant teams worried about process unfamiliarity, telling them not to adopt Shape Up until their current dysfunction causes severe pain.
Hardest push from Lenny ▶ 29:40 Challenging the appetite scope-cutting premiseLenny pushes Ryan on the textbook Shape Up premise that teams should simply slash scope to meet fixed time appetites when running behind.
Biggest teaching moment ▶ 47:26 Lack of detail as the primary failure modeRyan corrects Lenny's worry about engineering pushback against detailed specs, explaining that in real organizations projects fail from under-specification and undiscovered edge cases.
Lenny holds their own ▶ 1:27:42 Connecting upstream shaping to AI product managementLenny demonstrates deep product synthesis by linking Ryan's vision of upstream problem shaping to the paradigm shift emerging from AI development tooling.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| The Hidden Shipping Crisis and the Rise of Shape Up | 4 | 3 | 2 | 1 | Lenny introduces Shape Up as an alternative to Agile/Scrum and asks about its rising interest. Ryan explains why shipping struggles are rarely discussed publicly by leadership. | |
| The Origin of Shape Up: Constraints at Basecamp | 4 | 4 | 1 | 1 | Ryan details Basecamp's origins, including DHH's 10-hour-per-week engineering constraint that forced extreme efficiency. Lenny probes into the backstory and DHH's early focus on Rails. | |
| Core Principles: Appetites, Shaping, and Team Autonomy | 5 | 5 | 3 | 2 | Ryan outlines the core mechanics of Shape Up, contrasting whole-concept shaping with Scrum's 'paper shredder' approach to tickets. Lenny asks whether teams can adopt these practices modularly. | |
| Six-Week Time Boxes and Handling Project Risk | 5 | 6 | 3 | 3 | Lenny suggests that teams simply cut scope when behind schedule on an appetite. Ryan clarifies that naively cutting valuable scope destroys morale and explains why projects need to return to shaping instead. | |
| Adapting Shape Up Across Large Organizations | 5 | 4 | 1 | 2 | Lenny inquires how Shape Up's variable timeboxes fit into larger corporate quarterly roadmaps. Ryan explains how senior engineering leadership untangles dependencies and how consistent delivery satisfies executives. | |
| The Output of Shaping: Framing and the Calendar Example | 5 | 5 | 2 | 1 | Ryan illustrates shaping using Basecamp's calendar feature, defining the problem as finding 'empty spaces' rather than rebuilding Google Calendar. Lenny summarizes the output as wireframe architecture rather than detailed PRDs. | |
| Sponsor: Airtable Product Central | 5 | 6 | 3 | 3 | Lenny raises the concern that detailed shaping turns engineers into 'code monkeys'. Ryan counters that real-world failure almost always stems from insufficient detail and hidden technical rabbit holes. | |
| Running a Shaping Session: Breadboards and Fat Markers | 4 | 5 | 2 | 1 | Ryan describes running collaborative three-hour shaping sessions using fat markers and breadboards to avoid low-utility 'blurry Figma' mocks. | |
| Kickoffs, Nine-Box Scoping, and Scrum Comparisons | 5 | 5 | 3 | 2 | Ryan contrasts Scrum ticket assignment with Shape Up's builder-led nine-box scoping exercise. Lenny asks tactical questions on the optimal number of boxes and pilot project parameters. | |
| Identifying Failure Signals and Company Inflection Points | 5 | 5 | 3 | 2 | Ryan pushes back on popular 'feature factory' complaints, noting that most struggling companies cannot even ship predictably. He identifies the 30-50 person org inflection point as the typical breakdown stage. | |
| The Upstream PM Role and Basecamp's Unique Realities | 6 | 6 | 2 | 2 | Ryan highlights the upstream PM role and admits Basecamp's unique environment (coding designers, no sales team) initially blinded him to typical org friction. Lenny connects upstream PM shaping directly to AI product workflows. |
Statements from this episode (25)
Singer: Tech leaders avoid publicly discussing product shipping struggles
“What I started to learn pretty early on is that people don't like to talk about their struggles shipping. Especially, you know, CPOs and CTOs don't like to go on a public forum and say, our company isn't shipping, or our engineering team is stuck, or our team …”
Singer: 'Shape Up' book left gaps because few teams share Basecamp's structure
“Honestly, there are so few teams that are structured just like base camp that there are a lot of gaps in the book of like, well, what about this? And what about that? And how do we do that in our situation?”
Singer: DHH programmed only 10 hours a week on Basecamp V1
“Even when we were building V one, David wasn't actually full-time as the, as our only technical person. He was programming 10 hours a week.”
Singer: Six weeks is the maximum horizon for reliable product planning
“We found that six weeks is kind of the maximum that we can see into the future where we could actually say like, how do we work backward and figure out something we could build in that six weeks and really land it, you know?”
Singer: Whole project ownership drives much higher engagement than Scrum tickets
“Instead, we want to have a whole idea, give it to a team. So they see the whole, they really understand it. Right. And then they can come up with their tasks and they can figure out how to track that and break it into pieces so they can actually take more resp…”
Singer: Autonomous development cycles fail without rigorous upstream shaping
“Is that if you want that reality of the team happily buzzing and humming like a, you know, like some happy bee colony, you know, for this six weeks, they need to have a lot more clarity around what's the thing that we're solving, right? And so when we start wo…”
Singer: Six-week project caps reveal problems that six-month plans obscure
“If we think of six weeks as a maximum, that's going to force us to ask some really good questions to ourselves about where do we actually, what piece of this do we really think we can land? Because if you try to say, you know, in six months, we're going to shi…”
Singer: Two weeks is rarely enough to build substantial product features
“When it comes to feature development or, you know, building something that's going to be needy enough to sell, you know, then there's very few things that are going to be a substantial value add to a product that you can do in two weeks.”
Singer: Almost no teams have stomach to cancel unfinished six-week projects
“We had this principle at base camp, which was this notion of the circuit breaker. Like if a project is not on track to actually finish after the six weeks, we're just going to cancel it and rethink, you know, almost no teams have the stomach for that.”
Singer: Pull delayed projects back into shaping mode instead of building blindly
“What we can do is say, we're not going to keep reinvesting in something that we don't understand, you know? So let's take this out of build mode and bring this back into shaping mode”
Singer: Shape Up works in enterprise companies with thousands of employees
“It can function in very large companies. We have, for example I have some friends at a at a they're a what is it called? They're doing clinical trials. So they're in the pharmaceutical industry. And I mean, the companies, you know, thousands of people, and it'…”
Singer: Product teams do not need quarterly alignment if shipping consistently
“The other thing I've seen is when the team is just continuously delivering meaningful things, it doesn't have to line up. Because from the executive level, if you are CPO or CTO, or I mean, in these bigger cases, it's more like, you know, VP in some area, but …”
Singer: Detailed product solutioning without engineers usually leads to failure
“When there's a lot of solutioning all the way down to detail without engineering involved, usually that's a painful recipe, you know, and then it's kind of like, no, we can't do that.”
Singer: Well-shaped features can be described in under 10 moving pieces
“If it's shaped well, you can usually describe it in less than 10 moving pieces.”
Singer: Insufficient detail, not over-specification, causes most product failures
“The dominant failure case that I see in the real world is always again and again, not enough detail. And it's also the most common failure mode where the engineers run back to the product folks and say, I'm not getting enough from you.”
Singer: High-fidelity tools like Figma hinder early product shaping collaboration
“In a shaping session, you can't collaborate on, on, on something so high fidelity, right? And so we need also some ways to collaborate, and this is where you see these techniques in the book like breadboarding and fat marker sketching. These are tools to help …”
Singer: Non-builder Scrum tickets hide dangerous unknowns
“The person who's writing the ticket doesn't actually understand the work that's involved. You know what I mean? So there are so many unknowns and time bombs waiting in those tickets that sound reasonable, but they weren't really created by the person who under…”
Singer: Scoping projects beyond nine boxes degrades into ticket chaos
“If it's if it's more than 10, then you just get into ticket land of here's a million things I have to do. You know what I mean? If you have a hundred things, it's like, that doesn't tell me anything, but if it has to be nine or less, you know.”
Singer: Being a feature factory is healthier than being unable to ship
“The thing is that, like, I would say if you have a feature factory, meaning you're continually cranking out features, you're probably quite healthy. All you need to do is feed a different input to the beginning of the factory, right? What most teams are strugg…”
Singer: Product delivery typically breaks down at 30 to 50 people
“It's after they hired the first PM, after they hired the second PM and maybe even the third, you know, and they're kind of getting to like the product and engineering together are like 30, 50 people, you know, and it's like, we thought we put everybody in the …”
Singer: Delivery dysfunction begins when founders take their first step away
“I really think, honestly, I think it starts the first project where For example, the founding engineers hands off and then the new hire is, is taking over responsibility or the person who was like sort of founder slash CEO is like first giving it to a PM to ki…”
Singer: In Shape Up, PMs move upstream from build management
“And shape up teams when they hit their stride is that the PM moves upstream. So the PM is less busy with how do I get this project to like not be in a bad state when it's getting built? And they're way more in how do I understand the business context? How do I…”
Singer: Every designer at Basecamp writes code and runs the app locally
“Every designer codes. Imagine if every designer codes and not, and I don't just mean HTML. I mean, like running the app locally, going into the place where that view is rendered to make that thing look the way that they want it to look or whatever. Right. I me…”
Singer: Basecamp had no sales or marketing orgs competing for engineering time
“Imagine you have no sales org. You have no marketing. That all of sales, sales, selling and marketing is happening by the unicorn founders. So it means that there isn't contention for engineering time, that there isn't kind of like all these different sources …”
Singer: Jobs-to-be-Done frames demand, while Shape Up manages the supply side
“Before the problem definition, there's this question of like, what's the demand? Where are people struggling? Where is really the place The itch they're trying to scratch, you know, and then a lot of the shape up stuff is kind of when I have something where I …”