Proposal: 2.27 Evaluate feature use, value, and impact

[jenstrickland]

THIS IS NOT A PROPOSAL!

Continue discussion with a due date of November 1, 2025.

Revised

2.27 Evaluate feature use, value, and impact

Factor the ways people use the project into your decision making and consider how this can be optimized for both people and the planet.

Success Criterion: Usage changes
Monitor user feedback, adoption, and churn rates in relation to different features and incorporate these insights into future releases.

Previous

I no longer have access to the previous document. Earlier version: https://w3c.github.io/sustainableweb-wsg/#display-any-variables-that-have-a-negative-impact-on-your-project

Discussion

Clarity

• This feels like it belongs higher up. Better to assess this before development, but also monitor.
• Needs clarification
• This feels like it should contain information that relates to the entire product 'lifecycle' i.e. before development during requirements gathering, during the design phase and then continuous improvement rather than just after deployment.

Restructure

• Combine 2.24, 2.27, and 2.28 - Iterative Design
• Feedback - Rationale: Form a new guideline on iterative validation and continuous improvement driven by user and stakeholder feedback. https: // github.com/ w3c/ sustainableweb- wsg/ issues/ 64
• Maybe better at product level
• Measurement??

Comments

• Validate value and usability during design phase and after, right? Combine with 2.28 to clarify how the validation should support sustainability, etc.

Google sheet of feedback

[jenstrickland]

Please see this issue, w3c/sustainableweb-wsg#64, with input from @mgifford and @thorstenjonas on consolidating.

[jenstrickland]

Notes: Consolidating 2.27 and 2.28. In a future revision or the editorial review, it might be possible to subsume this into another one of the earlier guidelines.

📣 Please review and provide input using the reactions. 👍 if approval, 👎 if not, and be sure to provide comments before Dec. 3rd.

--

Proposed Guideline: 2.27 Evaluate and validate feature use, value, and impact

Factor the ways people use the project into your decision making and evaluate how this can be optimized for both people and the planet.

Success Criterion: Usage changes

Monitor user feedback, adoption, and churn rates in relation to different features and incorporate these insights into future releases.

Success Criterion: Usability testing

Incorporate usability testing into product cycles and routinely measure the impact of these tests for future releases to reduce friction points.

[hidde]

Would the sustainability benefit of this guideline be the removal of features that aren't used or useful? If so maybe we can add it to the guideline text.

Proposal for guideline text: “Factor the ways people use the project into your decision making and consider removing features that are not used or enjoyed* by users.” (* needs a better word, not such which?)

And instead of “to reduce friction points” we could say “to reduce functionality that users do not [like/want/enjoy].”

[jenstrickland]

Incorporated @hidde's proposal, ready @TzviyaSiegman @AlexDawsonUK. @hidde I didn't incorporate the last item about replacing friction points as in usability testing it is the friction that we observe that needs to be evaluated for potential removal. In some cases friction is a good thing (slow the user down so they are attentive) and in other situations it should be removed (checkboxes that are not aligned for scalability and ease of use). In trying to name the proposal, though, I wonder, is it the same as the Usability testing SC?

Proposed Guideline: 2.27 Evaluate and validate feature use, value, and impact

Factor the ways people use the project into your decision making and evaluate how this can be optimized for both people and the planet.

Success Criterion: Usage changes

Monitor user feedback, adoption, and churn rates in relation to different features and incorporate these insights into future releases.

Success Criterion: Usability testing

Incorporate usability testing into product cycles and routinely measure the impact of these tests for future releases to reduce friction points.

Success Criterion: Name to come

Factor the ways people use the project into your decision making and consider removing features that are not used or valued by users.