You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/posts/vaccinations/2025/07/creating-a-vds-ucd-monthnote.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,15 @@ date: 2025-07-03
6
6
7
7
## Purpose of the VDS UCD month-note
8
8
9
-
As the User-centred design (UCD) leadership team in Vaccinations Digital Services (VDS), a key part of our role is to maintain a comprehensive and up-to-date understanding of what UCD work is happening across the programme.
9
+
As the User-centred design (UCD) leadership team in Vaccinations Digital Services (VDS), a key part of our role is to maintain a comprehensive and up-to-date understanding of what UCD work is happening across the programme.
10
10
11
11
This is important for several reasons:
12
12
13
13
* Effectively communicating the value of what our teams' work to senior leadership
14
14
* Identifying and addressing any gaps in our work
15
-
* Optimising resource management and workload distribution
15
+
* Optimising resource management and workload distribution
16
16
17
-
With 11 different teams and more than 30 UCD professionals, this is not an easy job! We therefore decided to create an update that could be shared with everyone every month.
17
+
With 11 different teams and more than 30 UCD professionals, this is not an easy job! We therefore decided to create an update that could be shared with everyone every month.
18
18
19
19
## Key considerations for the VDS UCD update
20
20
@@ -23,24 +23,24 @@ In planning the VDS UCD update, we identified several critical factors:
23
23
1. Frequency: determining the optimal frequency for sharing updates (e.g., weekly, bi-weekly, monthly, quarterly).
24
24
2. Format: deciding on the most effective format for the update (e.g., Slack, Word, PowerPoint, email).
25
25
3. Content: deciding the essential content to be included.
26
-
4. Structure: organising the information in a clear and logical manner.
27
-
5. Reach: deciding whether the update should cover only VDS updates or include the entire DPSP.
26
+
4. Structure: organising the information in a clear and logical manner.
27
+
5. Reach: deciding whether the update should cover only VDS updates or include the entire DPSP.
28
28
29
-
## Learning from past attempts
29
+
## Learning from past attempts
30
30
31
31
Before finalising the current format of the update, we had two previous attempts that were unsuccessful. Recognising the need for improvement, we decided to learn from these past iterations. We began by gathering feedback from contributors and readers of our earlier updates to understand what worked and what didn't.
32
32
33
-
33
+
34
34
35
-
35
+
36
36
37
37
### Challenges identified
38
38
39
-
* Formatting issues: the PowerPoint format was cumbersome and difficult to complete.
40
-
* Time-consuming: it was labour-intensive to follow-up with people for their updates.
41
-
* Limited engagement: readers told us they only focused on information relevant to their own programme - without engaging with DPSP-wide updates.
42
-
43
-
### What worked well
39
+
* Formatting issues: the PowerPoint format was cumbersome and difficult to complete.
40
+
* Time-consuming: it was labour-intensive to follow-up with people for their updates.
41
+
* Limited engagement: readers told us they only focused on information relevant to their own programme - without engaging with DPSP-wide updates.
42
+
43
+
### What worked well
44
44
45
45
* Enhanced visibility: the update provided clear insights into the activities of different teams, fostering better understanding and collaboration.
46
46
* Improved communication: it helped team members identify the right contacts for more information about specific areas of interest, facilitating smoother communication, knowledge sharing and collaboration.
@@ -55,24 +55,24 @@ We then reached out to UCD colleagues in other teams across Product and Platform
55
55
56
56
## Our chosen approach
57
57
58
-
Based on our learnings from past attempts and insights from other teams, we formulated a strategy for our VDS UCD updates.
58
+
Based on our learnings from past attempts and insights from other teams, we formulated a strategy for our VDS UCD updates.
59
59
Here’s what we decided:
60
60
61
61
1. Frequency: we chose to share the updates monthly to ensure they are comprehensive yet manageable.
62
62
2. Format: we opted for a Slack canvas as it is easy to share on different Slack channels and tag people directly. Adding emojis can also make the format more engaging. We decided to keep all the updates in one canvas so that readers can scroll down to read updates from the previous months.
63
63
3. Content and structure: we are including:
64
-
- Updates from the UCD team: announcements relevant to or about UCD ways of working; UCD changes in the programme; reports, blogs or week-notes written by UCD people, and opportunities for people to get involved in UCD activities.
65
-
- Updates from our projects: key things UCD people in each team focused on learned this month, barriers they were facing and opportunities for other teams to help them. The updates are presented in a table where each team has their own row.
66
-
4. Coordination: for the Design and User Research Leads in VDS are coordinating the update each month. We ask people to complete their sections during the last week of the month and then share the update from the previous month on the 1st.
67
-
5. Feedback loop: we are explicitly asking for feedback to continuously improve the updates based on user input.
64
+
- Updates from the UCD team: announcements relevant to or about UCD ways of working; UCD changes in the programme; reports, blogs or week-notes written by UCD people, and opportunities for people to get involved in UCD activities.
65
+
- Updates from our projects: key things UCD people in each team focused on learned this month, barriers they were facing and opportunities for other teams to help them. The updates are presented in a table where each team has their own row.
66
+
4. Coordination: for the Design and User Research Leads in VDS are coordinating the update each month. We ask people to complete their sections during the last week of the month and then share the update from the previous month on the 1st.
67
+
5. Feedback loop: we are explicitly asking for feedback to continuously improve the updates based on user input.
68
+
69
+
68
70
69
-
71
+
70
72
71
-
72
-
73
73
## Next steps
74
74
75
-
The first VDS UCD month-note was released at the beginning of June, and the feedback has been positive, with many encouraging comments and Slack emoji reactions.
75
+
The first VDS UCD month-note was released at the beginning of June, and the feedback has been positive, with many encouraging comments and Slack emoji reactions.
76
76
77
77
However, we identified a misunderstanding regarding the 'Barriers and Opportunities' section. Many thought it referred to user barriers and opportunities rather than those faced by the teams. To address this, we decided to remove and simplify the section.
0 commit comments