-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Updated the Your community index * Update user-centred-design.md
- Loading branch information
Showing
2 changed files
with
18 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,13 +3,13 @@ layout: "layouts/guidance.njk" | |
section: "Community" | ||
title: "User-centred design" | ||
description: "Anyone in a user-centred design role in Defence can join the community. Find out how to get involved." | ||
dateUpdated: 2024-03-05 | ||
dateUpdated: 2024-06-06 | ||
eleventyNavigation: | ||
key: "Your community" | ||
url: "/your-community/" | ||
--- | ||
|
||
Anyone working on digital services in Defence is welcome to join the user-centred design (UCD) community. | ||
Anyone working on digital services in Defence can join the user-centred design (UCD) community. | ||
|
||
## Who you will meet | ||
|
||
|
@@ -23,53 +23,34 @@ In this community, you will meet: | |
|
||
## Community calls | ||
|
||
Join the UCD community call on the third Thursday of the month at 2pm. | ||
Join the UCD community call on the third Thursday of the month at 2pm. | ||
|
||
Calls are 55 minutes. We discuss things like accessibility, tools available in Defence and cross-government collaboration. | ||
|
||
{{ component('inset-text', { | ||
html: 'You must only share OFFICIAL information. <a href="/security-classifications/">Find out about security classifications</a>.' | ||
html: 'You must only share OFFICIAL information on community calls.<br><a href="/security-classifications/">Check how to classify information</a>.' | ||
}) }} | ||
|
||
### Ask for an invitation | ||
|
||
You need to work in Defence to join the community calls. | ||
You need to work in the Ministry of Defence to join community calls. | ||
|
||
Using your Ministry of Defence email, send a message to: | ||
[[email protected]](mailto:[email protected]?subject=Join%20UCD%20community%20calls). | ||
Using your Ministry of Defence email, send a message to: [[email protected]](mailto:[email protected]?subject=Join%20UCD%20community%20calls). | ||
|
||
Include your full name, your role and the project you’re working on. | ||
Include your full name, your role and the project you are working on. | ||
|
||
## Ask for feedback | ||
## Get feedback | ||
|
||
Community calls are a great place to ask for feedback on your service, a feature or an issue. Here are a few things to remember. | ||
You can ask the user-centred design community to give you feedback on your service, a new feature or an issue. | ||
|
||
### Set the context | ||
For example, you have a new feature and you are not sure which GOV.UK or Defence design patterns you should use. | ||
|
||
Without taking too long, tell the story of your service. Start with what your service does, who your users are and what they are trying to do. | ||
Check [how to ask for and give feedback](/your-community/ask-for-and-give-feedback). | ||
|
||
### Say what kind of feedback you want | ||
## Join other communities | ||
|
||
Tell people what you want to find out. For example, if there are existing patterns you can reuse or how close you are to meeting the GOV.UK Service Standard. | ||
You can join more than one community. You might find these communities useful: | ||
|
||
### Do not be defensive | ||
|
||
Feedback is about your service, not you. Avoid deflecting questions, it is okay to say that you are not sure. Take notes so that you do not need to respond to every point. | ||
|
||
## How to give feedback | ||
|
||
You are expected to give feedback in a kind and respectful way. | ||
|
||
### Give specific and actionable feedback | ||
|
||
All feedback should be constructive. Include details of what you are thinking, what you would change and why. Avoid phrases like "I don't like it" or "That never works". | ||
|
||
### Be kind and respectful | ||
|
||
You can be honest and specific without using hurtful or aggressive language. Start sentences with phrases like “Have you considered”, “You might like to try” or “Think about”. | ||
|
||
### Keep an open mind | ||
Everyone has different experiences and opinions. Remember that your feedback is just one perspective. Be willing to consider feedback that differs from your own. | ||
|
||
### Be present | ||
The team presenting their service deserves your full attention. Try not to be distracted by other work. In remote sessions, have your camera on and show that you are actively listening. | ||
- [content](/your-community/content/) | ||
- [product](/your-community/product) | ||
- [software development](/your-community/software-development) |