The feature nobody needed
A founder reached out because his team was exhausted. Three months of building, one major feature launch pending, and user engagement was flat. Worse — nobody could figure out why.
He was proud of what they’d built. A beautiful analytics dashboard with real-time metrics, custom reports, and exportable data. His early customers had asked for it. The team executed well. So why wasn’t anyone using it?
One conversation changed everything.
The call
I asked him to walk me through the user journey from signup to “aha moment.” He pulled up the product and started clicking.
It took 45 seconds just to get through the onboarding flow. Then another screen. Then a modal asking for preferences. Then a “quick tour” — five tooltips in a row. Then they land in the dashboard, faced with a wall of charts and metrics.
I stopped him and asked: “When did you last go through this yourself?”
Silence.
The real problem
It wasn’t the analytics. Users weren’t churning because they couldn’t see their metrics. They were churning because onboarding took 45 minutes.
The founder had been so heads-down building the feature customers asked for that he’d neglected the thing customers actually needed: a 2-minute onboarding experience that showed them value immediately.
Here’s what the usage data showed:
- 70% of new signups never completed onboarding
- Of the 30% who did, 80% never came back to the analytics dashboard
- The feature page had a 90% bounce rate
But nobody was looking at this data because the team was too busy building.
The redirect
I told the founder to stop all analytics work. Not pause — stop. Ship what they had (it was functional), mark it “beta,” and redirect the entire team to onboarding.
We designed a three-week sprint:
- Week 1 — Strip onboarding to the absolute minimum: email + password, connect your data source, you’re in. Everything else is post-signup.
- Week 2 — Add a “magic moment” experience: when a user completes onboarding, show them one immediately useful insight from their data. Not a dashboard. One sentence: “Your top customer this week is X.”
- Week 3 — Add progressive disclosure: instead of a tour, surface features as users need them. Contextual help, not a firehose of tooltips.
The result
Three weeks later, the numbers told a different story:
- Onboarding completion went from 30% to 78%
- Activation rate (users who reached value within 48 hours) doubled
- The analytics feature? Nobody complained it was “beta.” Nobody asked for more features. Because analytics wasn’t the problem.
The founder told me: “I spent 3 months building something I believed in, and 3 weeks fixing something I’d been ignoring. I wish I’d had someone call me out sooner.”
What I learned
Customers are great at describing their symptoms and terrible at diagnosing their disease. “We need analytics” usually means “we don’t understand our users.” The feature request is a solution to a different problem than the one they think they have.
The most valuable thing I do for founders is ask the question nobody else will ask: “What if this feature is a distraction?” Sometimes the best thing you can build is the thing you decide not to build.