Sometimes the better answer is to not do anything at all. If you can't prove the value of a feature or that the effort to achieve that value is worth it, saying "no" to the idea is often the best course of action.

We also look at scenarios where Product Managers and Engineers can benefit from being users of their own software, as well as the benefits of having competitors you can "borrow" inspiration from.

Join the discussion on Reddit: https://www.reddit.com/r/AcceptanceCriteria/

And on the Discord: https://discord.gg/2Tyj8H9MFF

The post E056: Learning when NOT to build that cool new feature first appeared on Acceptance Criteria.