2.27 Incorporate Value Testing Into Each Major Release-Cycle

Occasionally, you may find that features you have developed for a product or service have little to no active users or could be better implemented to bring better value. Undertaking research to identify redundancy allows you to optimize your codebase (and reduce emissions).

Criteria

Usage Changes: Visitor feedback, adoption, and churn rates are monitored of product or service features and their insights incorporated into future releases.

Impact

Medium

Effort

Low

Benefits

Environmental:
Feedback can help product teams make choices that improve a product or service’s environmental impact, a clear example of this would be ensuring that frequently used features are more visible than lesser used features, thereby reducing the burden of findability. Which helps visitors spend less time attempting to achieve their goals.
Performance:
User-testing allows you to focus on your product goals, ensuring that you maintain a minimum viable product and not one overburdened with complexity. In doing so, your product or service will be lightweight and run quickly.
Economic:
If you can avoid wasting development time building features that bring little value to the consumer, your precious resources can be better spent where it will provide a better return.
Conversion:
Feedback often improves conversion rates because it ensures that your product or service reflects the needs of your audience.

GRI

materials: Medium
energy: Medium
water: Medium
emissions: Medium

Example

Qualitative usability testing will help authors gain critical feedback about in-use features.

Resources

View the Guideline