Good, bad, and horrible reasons to build a feature

Prioritizing a successful product roadmap

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.

Did you find this article helpful?

Subscribe to get updates whenever I post a new article or video.

Thank you—you're subscribed!
Oops! Something went wrong while subscribing... try again in a minute?

Infrequent emails, no junk. Unsubscribe anytime.

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.

Read this article before it's published

Leave your email and I'll send you an early draft

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Related