4 min read
The cheapest feature is the one you never build
Design ROI isn’t always what ships. Sometimes it’s what never gets built.
Design
Sanket Daithankar
Product & Game Designer
I help teams ship products faster, with research backed design that keeps users coming back.
The maths of building the wrong thing
A product team spends three weeks building something users never needed. Let’s put numbers on it. Say the team is:
1 Product Manager
3 Engineers
1 Business Analyst
1 QA Engineer
Assuming everyone spends those three weeks on it, that is roughly 720 hours and about ₹6,00,000 in salary, based on average Indian salaries for those roles. That is before employer costs, before infrastructure, and before the cost of delaying work users actually needed.
What 20 hours can change
Now imagine a designer spends 20 hours helping the team question its assumptions before development begins. Not designing screens. Not polishing prototypes. Just making sure the team is solving the right problem.
Those 20 hours cost roughly ₹17,000, around 3% of what the build would have consumed. The visible outcome might be nothing: no new release, no lift in conversion, no improvement in completion rate.
The saving nobody sees
The organisation hasn’t saved ₹6,00,000 in cash. The salaries still get paid. But even after accounting for the designer’s time, it has avoided most of that ₹6,00,000 of product capacity being spent on the wrong thing.
We usually measure design by what gets shipped and how it performs. Some of its biggest returns come from what never gets built:
The unnecessary solution
The avoidable rework
The complexity that never reaches production
Proving it shouldn’t exist
The best design outcome isn’t always a better interface. Sometimes it’s proving the interface shouldn’t exist at all.
If you want to make this visible in your own team, track the decisions that changed before development started. Each one is a build that never happened and a few weeks of capacity that went to work users actually needed.
