The Nature of Quick Wins

Low Value or 1% Better?

In the intricate world of software product management, the topic of "Quick Wins" never fails to ignite robust discussions. Join me as we delve deeper into this concept, unraveling the dual perspectives that envelop it and navigating the nuanced landscape of efficient project prioritization.

Defining Quick Wins

At its core, a Quick Win is an activity that requires minimal effort and time, yet promises some benefits. The trick is to achieve quick results without sacrificing the integrity of the final product.

Competing Views: The Dilemma of Prioritization

1. Quick Wins: A Trade-Off with Value

Advocates of the Quick Wins strategy often prioritize the ease of effort over the intrinsic value of an activity. In this approach, the emphasis on quick execution tends to overshadow the importance of the value derived from each undertaking. Unlike traditional prioritization metrics, which tend to focus on value, Quick Wins advocates may inadvertently find themselves drowning in a sea of low-valued activities. It's not every day you hear someone enthusiastically suggest, "Let's dive into some low-value activities!" This perspective begs the question: Can the lure of quick, effortless wins lead to a proliferation of efforts that lack substantive impact?

2. Compound Returns: The 1% Improvement Philosophy

On the flip side, the philosophy of compound returns argues for the sustained, incremental improvement of a product. While a single Quick Win may seem inconsequential in its impact, it represents a small but positive step toward overall improvement. This notion reflects the principles of compound interest - small increments that add up to substantial progress over time. The illustrious British Cycling team is a prime example, meticulously pursuing 1% improvements across multiple facets simultaneously. But this approach requires patience and a long-term vision, because the real value comes when those incremental gains accumulate. Is a commitment to steady progress, even in small increments, the key to sustained success in the ever-evolving landscape of software product management?

The Crossroads: Choosing Your Approach

So which perspective holds the ultimate truth?

As you might expect, both perspectives have merit. The decision rests on a nuanced understanding of your unique circumstances and goals. Take a moment to consider whether prioritizing efforts seamlessly aligns with your current needs, or whether the compound returns philosophy better encapsulates your long-term aspirations.

In Conclusion: Orchestrating Harmony in Software Product Management

In the dynamic landscape of software product management, striking the right balance between quick wins and sustained improvements emerges as an ongoing challenge. This delicate orchestration demands a keen awareness of the contextual intricacies surrounding your projects. Choose the approach that resonates most cohesively with your overarching objectives, and witness the transformation of challenges into triumphs in the ever-evolving realm of software product management.

---

What I read

This is separate section of this newsletter. I will list some of the best articles I read on the internet. They may or may not be related to the topic of this article. I will keep a list of the best articles (currently >700) at https://www.digital-product-management.com. These are today’s picks:

Your Small Imprecise Ask Is a Big Waste of Their Time: When managers and leaders don't specify the expected time investment of an ask, the time that is invested is almost never what was intended.

How to tie product changes to business impact: Merging Hierarchy of Metrics with Opportunity Solution Trees.

Hire Better Managers: 35 Interview Questions for Assessing a Candidate.