How to prioritize

In this thought-provoking video, Rafa Sabbagh stresses the significance of shifting our focus from collecting requests to understanding the core problem or need. By emphasizing the importance of defining value and grasping the core issues at hand, Rafa guides viewers towards a more informed approach to prioritization. Drawing inspiration from the Pareto principle, he explores the art of identifying the most crucial elements within a problem for maximum impact. Understand the iterative and empirical nature of Agile, where short cycles and frequent deliveries drive continuous learning and adaptation from the use of what was delivered.

Introduction

When working with product development, is usual to find ourselves caught up in the trap of collecting tickets (or requests) from people, and simply trying to impose some order on them. However, when working with agility, it is crucial to have a clear understanding of what value truly means. Value is defined by the problem we are trying to solve, the need we are striving to fulfill, or the opportunity we aim to seize. To simplify, I prefer to call all these a “problem.”

Starting with the problem, not the solution

In my experience, a fundamental aspect of agile product development is starting with the problem we’re trying to solve, not the solution. Rather than being driven by external requests or predefined solutions, we delve into the core of the problem itself. This approach ensures that we align on a shared definition of value and set our sights on the ultimate goal or opportunity we want to seize.

The art of prioritization: applying the Pareto Principle

When it comes to prioritization, I find inspiration in the Pareto Principle, which states that 80% of the effects come from 20% of the causes. It initially referred to Italian landowners, but it has been applied to various concepts. We should strive to identify and tackle the next most important part of the problem at hand. In our product development journey, we start with a core of value, the core of the core of the problem, and gradually expand outward. We therefore to relentlessly pursue the next “Pareto”, incrementally building the solution that generates the greatest value.

Incremental delivery and frequent feedback

To effectively prioritize and deliver value, we rely on an iterative approach. In this journey, we rely on hypotheses—our best guesses about what is the next small thing that will create next highest value. We solve the problem by producing small, valuable increments that we can create and deliver at a rapid pace. By frequently deploying these increments for actual use, we gain valuable insights and user feedback promptly that guide our further development. This continuous feedback loop enables us to adapt, adjust, and identify the next most valuable thing to work on.

“Use defines the product”

Short cycles, such as sprints in Scrum, allow us to converge on usable value in each iteration. These shorter cycles do not merely serve to split a larger plan but to deliver valuable increments frequently. By delivering often, we enable real-world usage, learn from it, and use the feedback to guide our next steps. Given that, I came up with what I believe is a core principle of agile product development: “use defines the product” (or “use defines the service”, when talking about service development). We need to put what we created to be used so that we can gain a better understanding of what they need to be. This means that our understanding of what the product should be evolves through its usage. By focusing on delivering next most important usable features early and often, we gain understanding of how our product is used, allowing us to refine and shape it accordingly.

An empirical approach

Agile product development relies on an empirical approach, where we are continuously validating and invalidating hypotheses. We formulate our best assumptions about what will create value, and then iterate based on real-world usage and feedback. This empirical mindset is at the heart of agility, enabling us to learn, adapt, and deliver the most valuable outcomes.

Conclusion

In my journey through agile product development, I’ve learned that prioritizing value is essential for success. By starting with a deep understanding of the problem, applying the Pareto Principle, and embracing an iterative and empirical approach, we can consistently deliver incremental value. By letting use define the product and fostering a continuous feedback loop, we ensure to create relevant and valuable solutions. Prioritization becomes an art, guided by the continuous pursuit of the next most impactful thing to create given a clear definition of value.