When "it's simple" doesn't mean "it's worth it"

A stakeholder insisted on a visual feature described as a "simple quick win", while the real business backlog stayed unfinished. Holding the right priority —not the loudest one— is what allowed the project to scale to every client office.

The "quick win" that sounded reasonable

While building an MVP for a financial client, a business-side stakeholder insisted, in more than one meeting, that we add a visual tweak to the map view of their mobile app — differentiating field tasks by certain visual criteria. It sounded reasonable. It sounded, in their words, like "something simple, a quick win." Meanwhile, the project still had a major backlog of core business processes unimplemented — the ones that would actually let the app scale to every client office.

Holding the right priority

I held the position, together with the client's own technical lead: that visual change wasn't more valuable to the business than finishing the processes that let field agents analyze different credit products and reduce hours spent on case management. We agreed to formally dismiss it, kept the team focused on completing the full business scope, and left it for a future review instead of letting it slip into the current phase.

The result, measurable

The result: we kept the team focused on what truly moved the business case, and the app scaled to every client office. Today, all those offices still use exactly the processes we chose to prioritize in that phase — not the visual tweak that sounded urgent at the time.

Backed by data, not just intuition

A benchmark Pendo study on feature adoption found that barely 6.4% of a product's features drive 80% of real usage volume — the rest competes for engineering resources without moving the business. Software companies spent an estimated $29.5 billion in 2025 building features almost nobody uses. "Simple" and "quick win" don't always mean "valuable" — holding that line, especially against an insistent stakeholder, is uncomfortable in the moment, and it's exactly the work a delivery leader must do.

Data sources: Pendo — research/benchmarks on feature adoption (6.4% of features drive 80% of real usage); industry estimate on unused software: ~$29.5B USD spent in 2025 building features almost nobody uses.