Update creating-a-vds-ucd-monthnote.md

Added bolding

Author: martom90

app/posts/vaccinations/2025/07/creating-a-vds-ucd-monthnote.md

@@ -20,11 +20,11 @@ With 11 different teams and more than 30 UCD professionals, this is not an easy
 
 In planning the VDS UCD update, we identified several critical factors:
 
-1.	Frequency: determining the optimal frequency for sharing updates (e.g., weekly, bi-weekly, monthly, quarterly).
-2.	Format: deciding on the most effective format for the update (e.g., Slack, Word, PowerPoint, email).
-3.	Content: deciding the essential content to be included.
-4.	Structure: organising the information in a clear and logical manner.
-5.	Reach: deciding whether the update should cover only VDS updates or include the entire DPSP.
+1.	*Frequency:* determining the optimal frequency for sharing updates (e.g., weekly, bi-weekly, monthly, quarterly).
+2.	*Format:* deciding on the most effective format for the update (e.g., Slack, Word, PowerPoint, email).
+3.	*Content:* deciding the essential content to be included.
+4.	*Structure:* organising the information in a clear and logical manner.
+5.	*Reach:* deciding whether the update should cover only VDS updates or include the entire DPSP.
 
 ## Learning from past attempts
 
@@ -36,14 +36,14 @@ Before finalising the current format of the update, we had two previous attempts
 
 ### Challenges identified
 
-* Formatting issues: the PowerPoint format was cumbersome and difficult to complete.
-* Time-consuming: it was labour-intensive to follow-up with people for their updates.
-* Limited engagement: readers told us they only focused on information relevant to their own programme - without engaging with DPSP-wide updates.
+* *Formatting issues:* the PowerPoint format was cumbersome and difficult to complete.
+* *Time-consuming:* it was labour-intensive to follow-up with people for their updates.
+* *Limited engagement:* readers told us they only focused on information relevant to their own programme - without engaging with DPSP-wide updates.
 
 ### What worked well
 
-* Enhanced visibility: the update provided clear insights into the activities of different teams, fostering better understanding and collaboration.
-* 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.
+* *Enhanced visibility:* the update provided clear insights into the activities of different teams, fostering better understanding and collaboration.
+* *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.
 
 ## Best practices from other teams
 
@@ -58,13 +58,13 @@ We then reached out to UCD colleagues in other teams across Product and Platform
 Based on our learnings from past attempts and insights from other teams, we formulated a strategy for our VDS UCD updates.
 Here’s what we decided:
 
-1.	Frequency: we chose to share the updates monthly to ensure they are comprehensive yet manageable.
-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.
-3.	Content and structure: we are including:
+1.	*Frequency:* we chose to share the updates monthly to ensure they are comprehensive yet manageable.
+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.
+3.	*Content and structure:* we are including:
 -	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.
 -	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.
-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.
-5.	Feedback loop: we are explicitly asking for feedback to continuously improve the updates based on user input.
+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.
+5.	*Feedback loop:* we are explicitly asking for feedback to continuously improve the updates based on user input.
 
 ![](monthnote-slack.png)