Good, bad, and horrible reasons to build a feature

You can’t build a great product if you build the wrong features.

This should be obvious. And yet, I’m often surprised how little thought founders put into choosing which features to build. Often entire teams spend months working off little more than the whim.

Even successful startups rarely look back at their releases and ask themselves the big question:

Of all the things we COULD have built, are the things we DID build the ones with the best possible impact on our customers and business?

If you’re not sure, read on.

🚫 Horrible reasons to build a feature

Just say no.

‍

Are you struggling to make your product beautiful and easy to use? I work with Series-A startups to rebuild their design systems from the ground up. See how it works →

Don't miss any future posts:

Related