Building a product is a journey. Sometimes you build the right things, sometimes you don’t.

You can usually categorize features into three two categories:

Asset - It’s making the company money

Neutral - It’s doing nothing Debt - It’s making the company spend money

Neutral features doesn’t exist, here’s why.

Keeping a feature in your product means you need to:

Maintain its code

Maintain its unit tests

Maintain its automated tests

Verify it works with manual QA (If you have these creatures in your company)

Update your FAQ section with up to date information for it

Answer support calls for it

New features has to play nicely with it

A feature should be awesome++ing your product and company, so don’t leave meh features - they’re costing you.

I treat code as debt. The less code I own that provides the same output the better. Same goes for features, treat them as debt and your product will benefit.

Find me on Twitter @ketacode