|
| 1 | +--- |
| 2 | +title: How we are approaching guidance |
| 3 | +description: How we provide help and guidance for users |
| 4 | +date: 2025-03-20 |
| 5 | +tags: |
| 6 | + - service |
| 7 | + - prototype |
| 8 | + - content |
| 9 | + - user research |
| 10 | + - help |
| 11 | + - guidance |
| 12 | +--- |
| 13 | + |
| 14 | +SPI is built to be intuitive and easy to navigate. |
| 15 | + |
| 16 | +We continually test how users interact with the tool to identify where additional support is needed. |
| 17 | + |
| 18 | +Guidance was created throughout the SPI build and this is regularly updated as we make improvements and add new features to SPI. This ensures users feel confident when creating or editing campaigns. If a user encounters a problem, they can easily self-serve by accessing step-by-step guidance. |
| 19 | + |
| 20 | +During testing, we assess whether users can: |
| 21 | + |
| 22 | +- Identify help content |
| 23 | +- Understand the information |
| 24 | +- Follow the instructions to complete tasks |
| 25 | +- Navigate to the help content |
| 26 | +- Successfully complete tasks |
| 27 | + |
| 28 | +Previously, campaigns were created using JSON configuration files, which used technical language. While much of this terminology was carried over to the SPI UI, we're simplifying the language and adding helpful support explanations for technical terms. |
| 29 | + |
| 30 | +To support users in independently creating campaigns, we've explored several support content methods: |
| 31 | + |
| 32 | +## Inline support |
| 33 | +We provide inline guidance directly within the UI, to assist users when there are technical terms, or complex tasks and features. This support appears alongside the task, so users can easily access help without having to leave SPI. |
| 34 | + |
| 35 | +### Inline support content example |
| 36 | + |
| 37 | + |
| 38 | + |
| 39 | +## Long-form guidance |
| 40 | +We've developed detailed guidance documentation so novice users can self-serve. This step-by-step content walks users through the campaign creation process, offering additional instructions to help them complete each task. Currently hosted in Confluence and linked from SPI, this documentation will be moved to a more accessible location in the future. |
| 41 | + |
| 42 | +### Long form guidance example |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | +To ensure version control and support clinical risk assessments, we maintain a document management section. This tracks updates and provides an audit trail of changes over time. |
| 47 | + |
| 48 | +## Future considerations |
| 49 | +We're exploring the possibility of moving the long-form guidance from Confluence directly into SPI. Each page would feature a small help circle (shown below), which, when clicked, will open a pop-up with task-specific guidance relevant to the user's current step in the journey. This will allow new and novice users to access additional support as they create a campaign, all without leaving the UI. We will test this feature with both novice and expert users to ensure its effectiveness and accessibility. |
| 50 | + |
| 51 | +### Pop-up support content example |
| 52 | + |
| 53 | + |
| 54 | + |
| 55 | + |
0 commit comments