Dec 30, 2020

Feature requests are stupid business activity

When the company’s leadership doesn’t give a space for uncertainty, the team often gets a feature request.

As soon as the request was committed, it’s almost impossible to change them.

The problem with feature requests is that the team can’t pivot even if they found it does not solve customer problems. It happens because the leader already had the expectation the team will deliver that specific feature.

The team will focus on the output instead of the outcome. They will start to celebrate success when they deliver features instead of delivering value to the customer.

The feature request is stupid as a culture and as a business activity.

But why does the company’s leader fall into this mindset? That’s for another time.

The alternative is to set the objective, not hand down the solution. Leaders should be strategic, communicate the vision, define the strategic intent, and remember you don’t always right. Allow the team on the ground to explore and do some experimentation. Feature request is mostly a hypothesis. Don’t invest and execute it right away. You’re gambling.

Set the objective. Give space to discover unknown unknowns. Focus on the outcome, not the output.

ask me question illustration

Ask a question

Send your question about the most recent post. If I can, I'll answer it on the blog. (This will open your email client)

ask me question illustration

Subscribe to newsletter

Get the post right into your inbox every time a new post is published or get a weekly email, you choose.