Risks of not building something
In some cases, we may end up not meeting some functionality, because the cost of building is too high. Yet not building something might have a negative effect on the product experience. For instance, providing an unsubscribe option in a user's profile might involve higher development effort. This might increase the rank of this card from three to five (on a scale of ten). So, we decide that this is not the most critical functionality to build at the moment. The success criteria are not dependent on the ability to unsubscribe, but compliance requires us to offer the option. So, we are incurring a risk by not providing this option. We have to agree to invest in the cost of building this option the perfect way, or ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access