UX/UI Working Group Charter - 2025
- Ali González
Reference template is currently under construction and open to feedback: WG Annual Charter Template
This document is a Work in Progress. Contact @Ali González or the UX-UI facilitators for details.
Description: The 2025 mission of the UX-UI Working Group is to [do something cool and specific on the WG Topic].
Charter Status | Active OPEN CALL INACTIVE OBSOLETE |
|---|---|
Specifications under observance | |
Start date | [dd monthname yyyy] (date of the "Call for Participation", when the charter is approved) |
End date | [dd monthname yyyy] (Start date + 1 year) |
Facilitators | @Laurence Berry, Komo International @Betty Mwema, Gov.uk @Stefan Draskic, Casavi |
Communication Channels | [Link to public page] - @Ali González to complete Slack channel - UX-UI - @Ali González to fix permanent link (this one’s 14 days expiry) |
Meeting Schedule | We run:
Link to join: meet.google.com/mfn-tjvt-csc [Link to calendar feed] |
How to join | This is an evolving project, you can choose to get involved as much as you like, for example, a contributor may get involved in an ad-hoc basis where a steering group member may expect to commit at least 2 hours a week to the project. SupportIf you have any questions or need support, reach out to Laurence, Betty or Stefan on Slack. |
Past charters | n/a |
1. Motivation and Background
This is a community of over 50 designers, researchers and other professionals in digital government from around the world.
The purpose of this group is to define reusable patterns for government services that can kick-start the development of new services around the world
2. Scope for 2025
We currently have 2 streams of work, develop new patterns and test and learn where we put the patterns into use and get feedback. In each quarter of the project we are focusing on a high level pattern, for example ‘Apply for a thing’
2.1 Develop new patterns workstream
Lead: Laurence Berry, laurence@wearekomo.com
Guidance for contributing to a pattern
2.2 Test and learn workstream
Leads: Betty Mwema, Stefan Draskic
Working area in Mural - Test and Learn, Iterating content and patterns
2.1 Out of scope
The following features are out of scope, and will not be addressed by this (Working|Interest) group.
3. Deliverables
3.1 Activities and Deliverables
All items within the scope should be associated to activities and deliverables. e.g. if sharing real-world experiences regarding the implementation of specifications, please specify what activities are you planing and how can it be documented.
For Charters where the publication of specifications is expected, please use the following format:
Name of the Specification, version number
Link to proposal document
Link to Draft, if existing
Short description for the specification
Expected completion: YYYY-MM-DD or QX-YYYY
3.2 Timeline
[Rough timeline that details per quarter your activities]
4. Success Criteria
Detail here how you expect to measure the success of your charter.
5. Coordination
Detail here, if applicable, other GovStack Working Groups as well as external organizations you expect to coordinate with to achieve the work describe in this charter.
6. Participation
To be successful, this (Working|Interest) Group is expected to have 6 or more active participants for its duration, [_optional_ including representatives from the key implementors of this specification], [_optional in case of specification work_ and active Editors and Test Leads for each specification].
Facilitators are expected to contribute [validate: _half of a working day per week towards the (Working|Interest) Group]. There is no minimum requirement for other Participants.
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication.
[_pending adaptation_ The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the W3C Patent Policy.]
Participants in the group are required (by the GovStack Meta Specification
) to follow the GovStack’s Code of Conduct.
7. Communication
Technical discussions for this (Working|Interest) Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, however.
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the [name] (Working|Interest) Group home page.
Most [name] (Working|Interest) Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
This group primarily conducts its technical work on the [Slack Channel] for the Group, their [Jira space] and [their Confluence Space]. The public is invited to review, discuss and contribute to this work.
8. Decision Policy
[TBD]