PRODUCT ADVISORY COUNCIL
Make restraint explainable
The method
Make restraint explainable
Restraint should follow a reasoned tradeoff about value and experience.
When to use it
- Several candidate requests compete for resources.
Ask yourself
- Should we reject a request just to stay simple?
Put it into action
- Record the user value, evidence, and reason to decline: an invalid goal, poor experience, or a failed experiment.
Keep these limits in mind
- Removing a feature is not automatically right. Check special use cases and the harm or costs that continue when work is postponed.