Skip to content

Commit a67dc30

Browse files
committed
MYA - improving create availability
1 parent 8ce99ac commit a67dc30

File tree

3 files changed

+34
-0
lines changed

3 files changed

+34
-0
lines changed
75 KB
Loading
38.6 KB
Loading
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: Improving the create availability journey
3+
date: 2024-11-21
4+
---
5+
6+
We knew from our previous research on creating availability, that the concept of availability periods didn’t fit well with our users mental models. We’d found that users expected to create availability sessions, and publish these straight away.
7+
8+
## What we did
9+
10+
We removed availability periods as a concept, and allowed users to create sessions that either:
11+
12+
- repeated every week
13+
- did not repeat
14+
15+
16+
## The design
17+
18+
We removed the column displaying the ‘published’ vs ‘unpuplished’ status, and just listed the sessions that the user had created to date.
19+
20+
![Screenshot that shows the list of availability sessions that have been created](periods.png)
21+
22+
We added some inset text on the ‘check session details’ page, to inform the user that the availability will be published to the National Booking Service (NBS) when they hit save.
23+
24+
![Screenshot of a page which lists existing availability periods, with a button to create more](cya.png)
25+
26+
## Findings
27+
28+
The majority of users found the new design straightforward and understood that they would be able to create multiple sessions to set their campaign up.
29+
30+
Users understood that saving the sessions would publish the availability to NBS, and that this would mean people could book vaccination appointments.
31+
32+
Users expressed a need to create more flexibility, including adding multiple breaks within a session.
33+
34+
Based on these findings, we concluded that creating sessions one by one worked better for our users, but that we needed to consider how we might add more flexibility to the journey

0 commit comments

Comments
 (0)