A better way to plan, build, and ship products | Ryan Singer (creator of “Shape Up,” early employee at 37signals)
Guest Ryan Singer, author of Shape Up, discusses his product development method, emphasizing fixed-time "appetites" over deadlines and intense, cross-functional "shaping" sessions. He shares how to define clear problems, empower build teams, and adapt the framework to different company stages by focusing on early collaboration and addressing unknowns.
Deep Dive Analysis
10 Topic Outline
Ryan Singer's Background and Shape Up Origins
Shape Up's Distinct Approach to Product Development
Core Elements of the Shape Up Methodology
Deep Dive into Shaping Sessions and Timeboxing
Balancing Detail and Flexibility in Shaping
Getting Started and Implementing Shape Up
Warning Signs Your Development Process is Failing
The Role of the Product Manager in Shape Up
Unique Characteristics of Basecamp's Operating Model
Linking Product Strategy with the Shaping Process
6 Key Concepts
Appetite-Driven Development
An approach where teams set a fixed maximum amount of time they are willing to spend on a project, then work backward to define a scope that can be completed within that time. This shifts focus from estimating large projects to fitting solutions within a budget of time.
Shaping
Creative, collaborative sessions involving engineering, product, and design to define a project idea. Participants wrestle with problems and solutions to make the idea concrete and feasible within a set timebox, ensuring clarity before development begins.
Timebox
A fixed period of time, typically a maximum of six weeks, during which a team commits to finishing a shaped project. The scope is varied to fit the allocated time, rather than extending the deadline, to ensure consistent shipping.
Framing
The upstream work of narrowing down a broad problem or opportunity to a specific, well-defined challenge before moving into the shaping phase. This ensures that the shaping effort is focused on a clear, valuable problem.
Circuit Breaker
A principle stating that if a project is not on track to finish within its fixed timebox, it should be canceled or brought back into shaping mode for re-evaluation. This prevents indefinite dragging and encourages rethinking unclear work.
Fat Marker Sketching / Breadboarding
Low-fidelity visual tools used in shaping sessions to quickly express and collaborate on detailed ideas, flows, and interactions. These methods allow teams to move fast together and see something real without getting bogged down in high-fidelity design tools.
5 Questions Answered
Shape Up begins by setting a fixed time (an "appetite") for a project and then shaping the scope to fit that time, rather than estimating a large project and letting its timeline expand. It emphasizes deep collaborative shaping by product, design, and engineering upfront to ensure clarity.
The output is a diagram or drawing that clearly communicates the idea, its moving pieces, and how it works, allowing engineers, product, and design to understand exactly what needs to be built without ambiguity. It is not a detailed Figma file or a lengthy PRD.
Signs include projects dragging indefinitely, teams running in circles without shipping, constant questions and pushback during the build phase, unexpected complexity surfacing late, and a general lack of clarity around what is being built.
While applicable at any stage, problems often become apparent when product and engineering teams collectively reach 30-50 people, or when founders start delegating work and find that projects slow down or don't meet expectations.
The PM role shifts upstream, focusing less on project management and shepherding tasks during the build phase, and more on deeply understanding the business context, narrowing down problems (framing), and negotiating what problems are truly worth solving.
24 Actionable Insights
1. See End From Beginning
Do not start a project unless you can clearly envision its completion from the outset, to avoid open-ended work and ensure a defined outcome.
2. Set Project Appetites
Instead of estimating project deadlines, define the maximum amount of time you are willing to spend on a project before it’s finished. This forces trade-offs and prevents projects from dragging on indefinitely.
3. Cross-Functional Shaping Collaboration
Bring design, engineering, and product together in a room to collaboratively shape the plan for a project. This approach is more effective than writing long PRDs or trying to finalize designs before building, as it integrates diverse perspectives early.
4. Shape Ideas to Timebox
Develop ideas and solutions that are specifically designed to fit within a fixed time budget or ‘appetite.’ This ensures that projects are feasible and can be completed within the business’s desired investment of time.
5. Empower Teams with Shaped Ideas
Provide build teams with a single, well-shaped idea that they fully understand, rather than splitting it into numerous small tickets. This allows them to take responsibility for defining their own tasks and implementation details, fostering greater engagement and ownership.
6. Use Project Circuit Breaker
If a project is not on track to finish within its committed timebox, do not extend the deadline or cut essential value; instead, stop building and move it back to shaping mode. This allows for clarification of unknowns and prevents continued investment in an unclear direction.
7. Conduct Live Shaping Sessions
Hold short, intense, collaborative sessions with a senior engineer (who knows the codebase), a product person (who understands the problem), and a designer. These sessions involve whiteboarding and ‘wrestling’ with ideas to define a real, achievable solution within the timebox.
8. Protect Team Focus
Once a build team is committed to a timebox, protect them from external distractions and other work. This dedicated focus maximizes their productivity and increases the likelihood of completing the project on time.
9. Narrow Problem Framing
Before shaping a solution, clearly ‘frame’ the problem by narrowing it down to a specific, solvable core. This prevents scope creep and ensures that efforts are focused on delivering targeted value.
10. Address Risks Early
During shaping, proactively identify and deeply understand the biggest risks and unknowns (e.g., technical complexities or ‘rabbit holes’) before committing to a project. This prevents costly mid-project surprises and delays.
11. Untangle System Dependencies
Engineering leadership should actively work to untangle system dependencies in the architecture. This enables different teams to work independently on specific systems without constant coordination overhead.
12. PMs Focus Upstream
Product Managers should shift their focus ‘upstream’ to deeply understand the business context, narrow down problems, and negotiate the core value of potential projects. This elevates their strategic contribution rather than having them primarily manage the build phase or process rituals.
13. Actively Break Ideas
In shaping sessions, actively challenge and try to ‘break’ ideas from technical, product, and design perspectives. This process helps identify flaws early and strengthens the proposed solutions.
14. Use Low-Fidelity Sketching
Employ tools like ‘breadboarding’ and ‘fat marker sketching’ in shaping sessions to express ideas clearly and quickly. This allows for rapid collaboration and prevents getting bogged down by the premature detail of high-fidelity design tools.
15. Limit Implementation Chunks
At project kickoff, have the build team break down the shaped idea into nine or fewer major implementation chunks. This aligns with cognitive science principles, ensuring the team can hold the entire project’s scope in their heads.
16. Adjust Detail by Team
Tailor the level of detail provided in shaping based on the experience level of the build team. More junior teams benefit from additional guidance and suggestions, while senior teams may require less.
17. Start with Pilot Project
When adopting Shape Up, begin with a pilot project that is meaningful, timely, and of a manageable size (e.g., 3-4 weeks, not necessarily 6). This provides a safe environment to learn the new approach and demonstrate its value.
18. Cultivate Urgency to Finish
Foster a cultural energy within the team and leadership that prioritizes getting to ‘done’ and shipping products. This drives continuous movement and prevents projects from lingering.
19. Deliver Consistently for Autonomy
Consistently delivering meaningful, finished products without excuses builds trust with executive leadership. This demonstrated success can earn teams greater autonomy and reduce external interference.
20. Discuss Shipping Struggles
Acknowledge that teams often hide their struggles with shipping products due to discomfort. Create safe spaces or ‘failure corners’ to openly discuss these challenges and learn from them.
21. Leverage Constraints for Process
Use extreme constraints, such as limited engineering time, to design highly efficient ways of working. These limitations can force creativity and prioritization, leading to more effective processes.
22. Read Demand-Side Sales 101
To deepen understanding of customer struggles and problems for effective product framing, read ‘Demand-Side Sales 101’ by Bob Moesta.
23. Read Competing Against Luck
For a general introduction to the ‘Jobs to be Done’ framework and its spirit, read ‘Competing Against Luck’ by Clayton Christensen.
24. Seek Expert Guidance
If your projects are consistently dragging, lacking clarity, or failing to meet quality standards, consider reaching out to experts who specialize in these problems for guidance and support.
5 Key Quotes
You can't put 10 pounds of crap in a five-pound bag.
Bob Moesta (quoted by Ryan Singer)
The dominant failure case that I see in the real world is always, again and again, not enough detail.
Ryan Singer
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.
Ryan Singer
We are not going to start something unless we can see the end from the beginning.
Ryan Singer
If you haven't checked if there's electricity in that wall there or not, it's going to drastically change the cost and the time and everything.
Ryan Singer
3 Protocols
Shaping Session Output Example: Calendar Feature
Ryan Singer- Frame the problem: Narrow down the broad concept of 'calendar' to a specific user need, e.g., 'seeing empty spaces' in an existing agenda view.
- Define the core idea: Propose a concrete solution, such as a two-month grid with dots indicating scheduled days.
- Detail interactions: Specify that tapping a day (with or without a dot) reveals a scrolling agenda view underneath.
- Include key actions: Add navigation for months and a 'create' button for new events when viewing an empty space.
- Verify clarity: Ensure the description is clear enough that a technical person knows exactly what to build, typically described in less than 10 moving pieces.
Adopting Shape Up: Pilot Project Approach
Ryan Singer- Identify a pain point: Recognize that current processes lead to dragging projects, lack of clarity, or slow shipping.
- Gain leadership alignment: Ensure senior product and engineering leaders agree on the need for change.
- Select a pilot team: Choose a team to experiment with Shape Up.
- Choose a pilot project: Select a problem that is meaningful, timely, not too small (to learn the new muscle), and not so large that it overwhelms the first attempt.
- Set a timebox: Determine a fixed duration for the pilot project (e.g., three, four, or six weeks).
- Conduct framing work: Narrow down the problem for the pilot project to ensure clarity.
- Run shaping sessions: Bring product, design, and a senior engineer together to collaboratively shape the solution within the timebox.
- Coach the team: Provide guidance on how to run effective shaping sessions and translate shaped ideas into buildable tasks.
Build Team Kickoff for a Shaped Project
Ryan Singer- Receive the well-shaped idea: The build team is given a clear, shaped concept for the project.
- Create implementation tasks: The builders (engineers) define their own tasks based on the shaped idea.
- Visualize major chunks: Draw a grid with nine boxes, outlining the nine major implementation chunks required to complete the project.
- Review and refine: Use this exercise to identify potential scope issues or discuss implementation approaches, especially between junior and senior team members.