SaaS B2B · Enterprise · 2023
The validated
feature:
letting go of
the right idea
Management had approved four months of development for a complex analytics dashboard. Motivation: "customers are asking for it". User research: zero. Budget allocated. Three weeks of prototyping changed everything.
4 months
Avoided development · Closed investment round
3 sec.
To build and test the prototype
8
Tested users. The results were unanimous.
* Real data. Company name omitted for confidentiality reasons.
‘Customers
asked for it.’
A B2B enterprise SaaS platform had accumulated four months of roadmap around an advanced analytics dashboard. The idea was born out of three conversations with satisfied customers in a booming quarter. The management had built us on a comprehensive development plan, estimated to take four months with a five-person team.
No one had done user research. No one had verified whether those three conversations represented a real need for segment or three satisfied outliers who were asking for something they didn't know how to ask differently.
The budget was already allocated. The planned sprints. Developers waiting for specifications. In that context, asking "but are we sure it's worth it?" requires a certain amount of courage, and something concrete to show as an alternative.
The most dangerous phrase in a product meeting: "Customers asked for it". It often means that two or three people mentioned something and the company built us on a quarterly plan. The gap between "a customer asked" and "the market needs" is exactly where most development budgets are wasted.
Context of the report
Enterprise
Product strategist
Prototyping
HiFi, user testing
3 weeks
to save 4 months.
The proposal was simple: before we allocate four months of development, let's give three weeks to validation. If the prototype confirms the need, it goes ahead with data. If not, it fits. The initial resistance is normal. The pivot that followed was decisive.
Jobs to be done · Week 1
Interviews with 12 active clients using the JTBD framework. Not "Would you like a dashboard?" but "When you need to figure out how your team is doing, what do you do now?" The answer was unanimous and different from the dashboard: proactive alertsNot one more page to monitor.
Prototype · Week 2
Two parallel prototypes: the original analytics dashboard and an intelligent proactive alert system. Both high-fidelity, both interactive, built in Figma in 5 days. That's when speed matters: the more realistic the prototype, the more valid the tests.
Comparative test · Week 3
Eight target users, 45 minutes each. Identical tasks on both prototypes. Measurement: completion rate, time-on-task, declared preference and satisfaction. Results: 7 out of 8 users preferred the alert system. The dashboard produced anxiety, not insight.
Pivot and pitch · Weekend 3
Presentation to management with test data, videos of the most significant sessions and a mockup of the revised alert system. Decision in 48 hours: full pivot. The pivoted prototype became the centerpiece of the pitch to investors in the next round.
The Right Question
We didn't ask, "Do you like this dashboard?" We asked, "When you need to know if something is wrong, what do you do today?" The right question produces useful answers. The wrong question produces unnecessary consent.
The pivot in 5 days
Once we confirmed that the real need was the alerts, we redesigned the prototype in five days. Not starting from scratch: from patterns that already worked in the dashboard and reshaping them around a notification-action flow. The right stuff was already there. He was missing the direction.
The role of investors
The prototype wasn't just a product deliverable. It was a proof of customer validation, it showed that the company had a process to verify the assumptions before building. For investors, this is as valuable as metrics.
Not one fewer feature.
The right one.
4 months
Savings in the wrong direction
3 sec.
To validate, pivot and produce an investmentable prototype
7/8
Users who preferred the alert system to the dashboard
Round ✓
Closed with the prototype as the centerpiece of the pitch
This is not a case study of how we made a great feature. It's a case study of how we avoided making the wrong feature, and how that choice produced something more valuable than what was planned.
The 4 months of development saved were not wasted: they were redirected to the alert system, which went into production with a validation base that rarely accompanies a new feature.
Are you going to approve something without validating it?
Before you build,
verification.
A 60-minute UX Business Audit identifies if you're building in the right direction. Before it takes months to develop, the hypotheses have to be tested.