When is an adjacent feature "listening to customers" and when is it scope creep?
Users of a focused tool naturally ask for the next thing next door — and often they already have the data in your product to do it. Saying yes feels like listening. Saying yes ten times is how a sharp tool becomes a bloated one that does everything adequately and nothing well.
The tempting version is when the adjacent feature uses the exact data the user already entered, to answer the very next question they were about to ask elsewhere. That feels less like creep and more like finishing the job. But that is also what every scope-creep decision feels like from the inside.
For those who have been on both sides of this: what is your actual test for whether a requested adjacent feature belongs in the product or is the first step toward losing focus? Did you ever add one you regretted, or cut one you should have kept?
Replies
That’s the tricky part with these decisions. A simple A/B test can show whether an adjacent feature moves the overall metric, but what happens when the overall impact isn’t statistically significant?
Do we remove it, even though some users adopt it and clearly benefit from it? Or keep it, knowing it adds complexity for everyone else?
There’s no silver bullet here. The decision gets much harder when you look beyond the headline metric.