UX/UI Working Group Charter - 2025
This document is a Work in Progress. Contact the UX-UI facilitators for details.
Description: The 2025 mission of the UX-UI Working Group is to test and iterate the existing service patterns with current GovTech practitioners as well as other GovStack Building Blocks, and identify and develop new service patterns.
Charter Status | Active |
|---|---|
Specifications under observance | |
Start date | Jan 1, 2025 |
End date | Dec 31, 2025 |
Facilitators | @Laurence Berry, Komo International @Betty Mwema, Gov.uk @Stefan Draskic, Casavi |
Communication Channels | [Link to public page] - @Ali González to complete |
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. Objectives and Activities
We have identified three main objectives for this phase, detailing roles, activities, and prioritisation plans based on research feedback.
Objective 1: Testing content
Lead: Betty Mwema / Stefan Draskic
Roles Needed: User researchers, Service and UX Designers, individuals implementing or using our guidance and tools
Activities:
Engage consultants and government designers to use patterns
Gather feedback and conduct user research with GovStack specification users
Conduct remote or in-person usability testing workshops with volunteers from different countries/consultancies to evaluate design patterns
Write case studies of successful pattern implementations/
What we need to make this a success:
People/orgs who want to try using the content
To create a research plan…
Coordinate with implementation team
Change log to keep track of what people have used and learned to show this is a living community
Working area in Mural: Test and Learn
Objective 2: Iterate content
Lead: Betty Mwema Stefan Draskic
Roles Needed: Interaction designers/UI, Content designers/ creative writers, individuals implementing or using our guidance and tools, individuals creating design systems or working in design system teams
Activities:
Refine and revise existing patterns
Present patterns (e.g., through Digital Island prototypes)
Improve the experience for using our guidance, tools and patterns
What we need to make this a success:
Change log to keep track of what people have changed and why
Publish tools on Figma community
Working area in Mural: Iterating content and patterns
Objective 3: Develop patterns
Lead: Laurence Berry, laurence@wearekomo.com
Roles Needed: Interaction designers/UI, Content designers
Activities:
Develop templates, processes, and guidance for contributing new patterns
Audit existing BBs and their corresponding user flows and page patterns
Develop missing patterns in core journeys (related to bbs - payments/identity/wallet)
What we need to make this a success:
Access to building block
Contributor guide / deck / figma page
Focus on one done well at a time
Someone who is good with UI and figma
Time with the building blocks to understand
Change log to keep track of what changed and why
Guidance for contributing to a pattern
2.1 Out of scope
The following features are out of scope, and will not be addressed by this (Working|Interest) group.
3. Timeline
4. Deliverables
TBD
4. Success Criteria
TBD
5. Coordination
TBD
6. Participation
TBD
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
TBD
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