naming the service post, and typo fixes

app/posts/2024-06-24-prototype-version-1.md

@@ -21,7 +21,7 @@ screenshots:
     - text: Library of pre-configured exclusion rules
       src: 05-library.png
       caption: |
-        The idea of having a library of exclusion rules that users could pick from was very well recieved. This is similar to how users work now, in that they have documented some common rules on Confluence which they can copy and paste. They saw opportunities for this new service to improve on that process by allowing common rules to be specified per campaign type (e.g. Covid, MMR, etc.) There was less confidence about concept of the "commonly used" section. User weren't certain how this would be populated, whether it was different per user, per campaign type, or some other combination. It wasn't clear that this idea would make it easier to find the right selcetions over a sensibly ordered and well structured list.
+        The idea of having a library of exclusion rules that users could pick from was very well recieved. This is similar to how users work now, in that they have documented some common rules on Confluence which they can copy and paste. They saw opportunities for this new service to improve on that process by allowing common rules to be specified per campaign type (e.g. Covid, MMR, etc.) There was less confidence about the concept of a "commonly used" section. User weren't certain how this would be populated, whether it was different per user, per campaign type, or some other combination. It wasn't clear that this idea would make it easier to find the right selections over a sensibly ordered and well structured list.
     - text: Long lists of options
       src: 06-lists.png
       caption: |

app/posts/2024-06-26-naming-the-service.md

@@ -0,0 +1,47 @@
+---
+title: Naming the service
+description: How we named the service
+date: 2024-06-26
+tags:
+  - service
+  - prototype
+  - content
+  - user research
+---
+
+## Our service
+'Selecting People for Invitations' is an internal service. This means that only NHS staff will use this service and not the public.
+
+Previously, the service was described by the team as ‘Invitation Processor'. The name didn’t clearly explain what the service actually does.
+
+So we needed a new, self-explanatory name that would be explain what this service does, both for members of the Select and Invite team and wider NHSE and NHS staff using the service.
+
+
+## Using the service manual
+The ['naming your service' section of the GDS Service Manual](https://www.gov.uk/service-manual/design/naming-your-service) says we should only ever use descriptive names.
+
+They must describe what the thing is and what it's for. [We use verbs instead of nouns](https://designnotes.blog.gov.uk/2015/06/22/good-services-are-verbs-2/) and names that don't need to change when policy or technology changes, as this would be confusing for users.
+
+![Examples of verbs and nouns](picture1.png)
+![Examples of service names](picture2.png)
+
+## Namestorm
+The next step was to think of possible names. We shared a Mural board with the members of the team, which documented the information we had collated and asked them to add as many names as possible, asynchronously.
+
+![Mural board of suggested names](picture3.png)
+
+Once we had lots of name suggestions we could begin the elimination process. We eliminated anything that:
+- didn't start with a verb
+- wasn't descriptive
+- wasn't self-explanatory
+
+We got down to 11 stickies and did a vote to see which one we liked best:
+
+![Sticky notes with votes](picture4.png)
+
+We made sure that the service name we selected made sense when explaining the service to somebody:
+
+> "Are you aware of the 'Select People for Invitations' service? It's a service run by the Select and Invite team Select People for Invitations, which allows users to send invitations to members of the public."
+
+## Collecting user feedback
+We are currently holding research sessions to collect feedback for the service prototype from users. As part of this, we will collect feedback from users about the new name for the service.