The Pitfalls of Blindly Following Methodological Frameworks in Product Development
When it comes to product development, many organizations put all their faith in methodological frameworks, hoping they will guarantee success. However, this approach can be misguided. The goal of product management is to deliver the right product in the right way and at the right time, and no two products have the same customers, needs, technologies, or teams to deliver them. As such, product teams should not follow a methodological framework without modification.
Common Methodological Frameworks in Product Development
Before we dive into the pitfalls of blindly following frameworks, let’s explore some of the most common ones in play today:
- Scrum: A lightweight framework that excels in iterative, emergent single-team efforts.
- Extreme Programming (XP): A customer-centric approach that drives internal quality and technical excellence.
- Kanban: A visual system that helps improve the flow of complicated increments of value.
- Large-Scale Scrum (LeSS): A scaling framework that simplifies organizational structures and removes bureaucracy.
- Scaled Agile Framework (SAFe): A non-invasive solution that appeals to large organizations who need to handle scale.
- Waterfall: A phase-gate, linear, big-batch, planning-driven approach that assumes minimal learning during the lifecycle of a product.
Pitfalls of Blindly Following Methodological Frameworks
While these frameworks can be useful, many organizations falter in their application. Here are four common pitfalls to avoid:
- Applying the Wrong Framework: Picking a framework that’s not appropriate for your product context can lead to failure. For instance, using waterfall for complex and uncertain product development can result in budget overruns, late delivery, and frequent failure.
- Focusing on Output Without Value: Many organizations focus on output without considering the value it brings to customers. This leads to products that nobody loves, except maybe the builders. Learning along the way is absent, avoided, and feared.
- Following the Rule Book Without Adaptation: Continuously following the same rules without adapting to changing contexts can stagnate your process. Product development is complex and uncertain, requiring a continuously adapted process to address its ever-evolving context.
- Centralizing Decision-Making to a Select Few: Centralizing important decisions to a select few can elongate and complicate the decision-making process. Instead, democratize decision-making to involve those doing the work, leading to better decisions and engagement.
Taking it Forward
To avoid these pitfalls, it’s essential to be mindful of your product context and select simple techniques that support a whole team approach to emergent innovation based on evidence. Then, adapt your behavior to ensure you don’t misapply the framework. Product success relies on your ability to adapt to your ever-changing context.