Three questions before you build any feature
Will anyone buy, hire or stay because of it? Can a page test it first? Does it keep the promise?
By Hassan Ed-dyb · · 1 min read
Short answer: before building a feature, ask three questions. Will anyone buy, hire or stay because of it? Can a simple page test the demand first? Does it keep the product's core promise? A no to any of them is a reason to wait.
1. Will anyone buy, hire or stay because of it?
If not, it's decoration. "See who viewed your profile" sounds great in a meeting. It moves nothing. Tie every feature to a behavior that matters to the business.
2. Can a page test it first?
A page takes a day. A feature takes a month. Publish the page that offers it, and the people who sign up tell you what to build, and whether to build it at all.
3. Does it keep the promise?
Every product makes one promise. RemoteMaroc's: every job on the platform is open to someone in Morocco. So every listing that isn't gets dropped. Fewer jobs, more trust. A feature that weakens the promise costs more than it adds.
Great products aren't built faster. They're built by teams that say no more often.