A better way to plan, build, and ship products | Ryan Singer (creator of “Shape Up,” early employee at 37signals)
Summary
In this episode, Ryan Singer, creator of the 'Shape Up' methodology and former Head of Strategy at 37signals, discusses innovative approaches to product development that diverge from traditional Agile and Scrum methodologies. He critiques the recurring cycles that these methods can create, leading teams to frustration and stagnation. Instead, Ryan emphasizes an 'appetite-driven' approach, which focuses on fixed timeframes for work rather than scope, allowing teams flexibility in adjusting project details. He highlights the significance of collaborative shaping sessions, where stakeholders align on project goals before committing resources, and asserts that many organizations struggle with too little detail in planning. The podcast also outlines the importance of effective team size management and the need for a clear product vision to avoid becoming a 'feature factory.' Ryan provides practical strategies for implementing the Shape Up methodology, addressing common pitfalls that teams face during product development, particularly in the context of rising technological changes and the evolving role of engineering and product management. Overall, Singer's insights encourage organizations to refine their processes to focus on outcomes rather than mere outputs, making them more productive and responsive in a fast-paced environment.
Key Takeaways
- 1The importance of defining project parameters and avoiding scope creep.
- 2Identifying the pitfalls of traditional Agile and Scrum methodologies.
- 3The significance of appetite-driven development.
- 4Collaboration among engineering, product, and design in shaping sessions.
- 5Recognizing signs that current development processes are failing.
- 6Adapting Shape Up principles to unique company contexts.
- 7Healthy team sizes and structured processes as startups scale.
- 8Avoiding becoming a 'feature factory'.
Notable Quotes
"'A head of product and a head of engineering working closely is often the recipe for success.'"
"So the first thing is we are not going to start something unless we can see the end from the beginning. We're not going to take a big concept and then say, what's the estimate for this thing? We're going to go the other way around and we're going to say, what is the maximum amount of time we're willing to go before we actually finish something?"
"I've noticed more and more teams adopting the Shape Up method and especially with AI starting to change how we work and build product. There's a shift coming in how product teams will operate."
"This episode is basically going to give you everything you need to give Shape Up a shot on your team or at your company to see if it fixes the problems that you're having shipping great products."
""At the end of the day, it's actually the interface at the executive level of being able to say, how are we using our time? Like we have to change something.""
""So I think maybe it's more for us who are kind of using it for different purposes. Like we're the product people trying to pull something out of it that it's a little less aligned, but it's still useful.""
"'Be careful what you wish for.'"
""Sometimes dev teams, they like the idea of not having the scrum ritual. But unless the engineering and product come together to figure out how to collaboratively shape, like we talked about before, you know, that time box isn't going to go well.""
"'Most teams today are struggling with too little detail in their planning, not too much.'"
"We can't just take any project, no matter how giant it is, and then throw it at a team and say, figure it out."
"We don't want to have to throw it all away every time something changes, you know?"
"The whole idea is you commit to the appetite. And if you are not on track to hit that, instead of extending the date, you cut in order to still hit it."
""Here's a problem that we actually care about. It's timely, something that we would like to be shipped soon.""
"And we can have a really practical, realistic conversation about, is that a thing we can do in six weeks?"
"You know, there's going to be a create button to create an event. Right."
Episode questions
What strategies can organizations employ to transition from traditional Agile methodologies to the Shape Up model?
Organizations can start by piloting Shape Up with a single team to assess its fit within their current processes. They should focus on understanding appetite-driven project planning and shaping sessions to collaboratively define project scopes, thus fostering involvement from all stakeholders. Commitment to iterative feedback and adaptability in scaling the model can subsequently facilitate broader implementation across the organization.
How does the Shape Up methodology address the common pitfalls of feature factories?
Shape Up proactively counters feature factories by setting clear operational constraints around project timelines and keeping the focus on delivering valuable features rather than just shipping outputs. It emphasizes a thorough shaping session process that aligns all team members on goals and user needs, thus reducing the likelihood of misaligned projects that merely aim to add more features.
What are some practical techniques for implementing the Shape Up methodology?
Practical techniques include conducting structured shaping sessions that encourage collaborative brainstorming, establishing clear timelines to manage expectations, and involving cross-functional teams early in the ideation process. Additionally, engaging in regular feedback loops ensures alignment and continuous improvement.
How can teams avoid becoming 'feature factories'?
Teams can avoid this by focusing their efforts on meaningful user engagement and clarifying their product vision before embarking on new features. Constant iteration based on feedback rather than chasing a list of features will help maintain direction and relevance.