Proposal: 2.24 Get users and contributors invested in the project

[jenstrickland]

THIS IS NOT A PROPOSAL!

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

Revised

2.24 Get users and contributors invested in the project

Document how you test new features with real users and validate the results, ensuring resources and training are provided to maintain the project's viability.

Success Criterion: New features and perspectives
Outline processes used to prototype and test new features, product ideas, and user interface components. Test with real users who represent different perspectives and user constraints.

Success Criterion: Resourcing and viability
Ensure prototyping and testing processes are sufficiently resourced to support long-term viability and avoid project abandonment.

Success Criterion: Training and onboarding
Produce or provide, training materials to properly educate and onboard new contributors.

Success Criterion: Testing and validation
Conduct regular and extensive testing alongside user interviews to validate whether released features meet internal goals and audience needs.

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

Clarification

• This may simply need rewording - but I feel we should ensure the section title refers to usability more directly, otherwise it "feels" more like a business thing.
• I think this should focus on "non- typical" stakeholders (e.g. "nature")
• UX principles must be in place to engage stakeholders effectively? (This ensures Usabliity and accessibility are both explicity referred to)
• Must be inclusive of internal and external stakeholders and include the planet as a stakeholder too

Restructure

• How is this UX's job? I don't object to talking to stakeholders, but creating overall policies like "all stakeholders must pay attention to sustainability" is way above the product teams grade.
• SC (Training and onboarding) merge with either 5.1
• (Onboarding new members) or 5.3
• 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
• Similar like documentation part, it should be valid for all teams, so maybe move this to business or product (depending on the scope)

Comments

• Changing wording away from stakeholders helped - but I still have issues with the non-user avatar, planet etc. - that gets confusing and feels like it needs instructions/background.
• I wonder if guidance might be that UX principles are clearly communicated and aligned upon — that way all
  understand/are invested?
• Once we get out of the roles based WSG structure, maybe this will be clearer.
• Depending on an org's structure, some UX folks do st*keholder engagement. l know I have. Compelling storyteller is part of the job.

Google sheet of feedback

[fershad]

Moving the Training and onboarding SC into 5.8 Implement sustainability onboarding guidelines feels sensible.

Likewise the Resourcing and viability SC can be moved into 5.1 Have an ethical and sustainable product strategy because it also feels more like a business rather than a UX concern.

With those gone, this then effectively turns into a user testing themed guideline, and the wording can be adjusted along those lines.

[awright1979-alt]

Moving the Training and onboarding SC into 5.8 Implement sustainability onboarding guidelines feels sensible.

Likewise the Resourcing and viability SC can be moved into 5.1 Have an ethical and sustainable product strategy because it also feels more like a business rather than a UX concern.

With those gone, this then effectively turns into a user testing themed guideline, and the wording can be adjusted along those lines.

I think the remaining success criteria make sense after that, but I'd propose a title change to 2.24 Involve users and contributors early in the project to reflect that.

[jenstrickland]

Notes: Incorporated above feedback. Changed "Document how you test" to "Document the test process" since I didn't see "you" the other 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.24 Involve users and contributors early in the project

Document the test process for new features with real users and validate the results, ensuring resources and training are provided to maintain the project's viability.

Success Criterion: New features and perspectives

Outline processes used to prototype and test new features, product ideas, and user interface components. Test with real users who represent different perspectives and user constraints.

Success Criterion: Testing and validation

Conduct regular and extensive testing alongside user interviews to validate whether released features meet internal goals and audience needs.

[hidde]

Sorry to suggest it at this stage, but I would suggest removing this entire guideline as it has no clear relationship with sustainability.

We could scope it to “users in areas disproportionately affected by climate change” to make it more sustainability specific, but that would make it harder to achieve.

[AnneFaubry]

@hidde I would nuance what you say: the phrasing is not specific to the environment but the guideline has a great relationship to sustainability as this methodlogy allows to avoid waste, stick to the minimal need... Maybe this should be hightlighted then?

[kazuhito-kidachi]

In my understanding, if we can involve users and contributors early in the project, that would be minimize rework which would be bad for sustainability. That's the relationship between the guideline and sustainability.

[jenstrickland]

Incorporating the feedback of @hidde @AnneFaubry @kazuhito-kidachi below, and ready for @TzviyaSiegman @AlexDawsonUK.

Proposed Guideline: 2.24 Involve users and contributors early in the project

Document the test process for new features with real users and validate the results, ensuring resources and training are provided to maintain the project's viability and minimize rework.

Success Criterion: New features and perspectives

Outline processes used to prototype and test new features, product ideas, and user interface components. Test with real users who represent different perspectives and user constraints.

Success Criterion: Testing and validation

Conduct regular and extensive testing alongside user interviews to validate whether released features meet internal goals and audience needs.