You Might Not Need a Shiny New Feature

Before shipping a new software feature, try asking the following questions:

  • Does the feature really add value beyond the marketing potential of a shiny new thing?
  • Will it really benefit our customers, or do they only think they need it?
  • Will the new feature add more complexity and confusion to the product’s interface?

--

--

--

I write about creating and marketing with a goal to inspire you to take action and make a difference. Currently building css-weekly.com & inspiration-bits.com.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to Bring a Horse Racing Business to the Next Level!

Use this one simple hack for good online shopping deals

Factors of on page seo to rank your website on first page

Sales Velocity: The metric sales teams are overlooking

Beginner’s Guide to Choosing A Marketing Agency

Gmail Inbox Delivery — Evolutions and Predictions for 2019

True Customer Service is our Magic Formula

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Zoran Jambor

Zoran Jambor

I write about creating and marketing with a goal to inspire you to take action and make a difference. Currently building css-weekly.com & inspiration-bits.com.

More from Medium

Google Is Creating A New Core Web Vitals Metric

Miro Vs. Dojoit — Which is Best Online Whiteboard?

Goal setting for software teams: 99% of your problems are goal problems

Agile Anti-Pattern: The Knowledge Silo