junecaldwell5
commented
1 year ago I recently ran a service naming workshop with my team, for the proxy application service. At the time, we had tested two service names with users (one using the word "proxy") and neither worked well.
I spoke about this workshop in a recent Show and Tell. I'll share screenshots of my slides.
Workshop participants included team members from all disciplines (product managers, BAs, URs, service designers etc.).
We started off by completing activities to get into the right frame of mind for coming up with names. These got us thinking about our users and our service.
I then ran through what we've tried already and the feedback we got. We looked at some service name inspiration and best practice for naming services.
We used the Thesaurus and Google Trends.
We then came up with names, referring back the activities and inspiration we looked at. Our service has two user groups, so we pretended we were naming two individual services. This made it a little easier to then pull them into one service name.
Finally, we went through all of our suggestions and refined our options. We then voted on our top 2 favourites and took these into our most recent round of user testing.
Feedback from user testing was that the two options need to be refined further and taken into another round of user testing. One is short and snappy but it doesn't explain what the service does well enough. The other is much clearer and preferred by users but is very long.
Hope this is useful. Let me know if you have any questions.
Here's the GOV.UK guidance on naming your service: https://www.gov.uk/service-manual/design/naming-your-service.
Please share any NHS-specific guidance here. Also ways of approaching agreeing a service name and user research insights into service names.