Is this feature worth building?
Something has been requested enough times that it’s getting hard to say no. Four questions separate a real need from a loud request, and give you a reason you can say out loud to the person who asked.
Everything runs in your browser. Nothing is sent anywhere, and the answer gets its own link you can send to your team.
About this check.
How do I decide if a feature is worth building?
Look at who asked and whether it was unprompted, what those people do about the problem today, and what measurably happens if you never build it. Several users who each built their own ugly workaround is a need. One loud voice with no workaround behind it’s a preference, and preferences do not belong on a roadmap.
Should I build what a big customer asks for?
Only if you can find the same need in people who are not that customer. A large account can fund a feature and still be the only place it’s ever used, which leaves you maintaining it forever. The question that settles it’s what they do about the problem today, if the answer is nothing, they’re describing a preference with a budget attached.
How do I say no to a feature request?
Say what you would need to see to say yes, and mean it. “Nobody who asked for this has built a workaround for it, so we do not think the need is there yet, if that changes, tell me” is refusable, checkable, and does not sound like a brush-off. A vague “it’s not on the roadmap” invites the same request again next month.
Is it free, and where do my answers go?
Free, with no account and no email. Everything runs in your browser, nothing is sent to a server, nothing is stored, and I never see what you clicked.
Other checks.
-
Why is nobody using your product?
Which of the five you’re in, why the other four are not it, and the cheap test that confirms it.
-
Was that feedback real, or just polite?
A verdict on that one conversation, and the cheapest next move for it.
-
Should you decide this now, or think longer?
How much of your time this decision deserves, and the one check to run before you commit.
-
Can you charge for this yet?
Whether you’re ready to charge, and what to fix first if you’re not.
-
Why does your team keep redoing the same work?
Which of four things is causing it, and the smallest change that stops it.