-
Notifications
You must be signed in to change notification settings - Fork 4
Closed
Labels
taskforce-uxThis issue affects the UX taskforce.This issue affects the UX taskforce.
Milestone
Description
THIS IS NOT A PROPOSAL!
Continue discussion with a due date of November 1, 2025.
Revised
2.28 Verify that real-world users can successfully use your work
Run usability tests to determine if the impact of the project can be further iterated to reduce friction points.
Success Criterion: Usability testing
Incorporate usability testing into product cycles and routinely measure the impact of these tests for 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
Restructure
- This feels very similar to 2,27 - could they be merged?
- Measurement??
- Cross over to 2.25 here - how do we verify? We look at analytics, we do evaluations, we do usability testing.
- That covers this and also 2.25 IMO.
- 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
- Agree with Mike. This could be merged and potentially pushed to product level
Comments
- Agree that this can fit under 2.27, as usability testing is a way to ensure features provide max value for impact
Metadata
Metadata
Assignees
Labels
taskforce-uxThis issue affects the UX taskforce.This issue affects the UX taskforce.