We’re moving to a more cadenced way of working. This is to allow everyone in the team to feedback on the user research findings so we can:
- prioritise what we want to do next
- create hypotheses and other documentation
- discuss design solutions, have more time for crits
- test hypotheses
- validate what we know
- keep iterating so we can design at pace
A Heroku based prototype was built of the MVP product design created in the Projects Alpha phase, the elements feature in the entry were all captured from the iteration c prototype.
https://plantech.herokuapp.com/c
Changing the start page will make it more engaging to users
In iteration 2 we found that users reacted well to the highly structured content on the start page. The headings made it much clearer for users to find the information they needed.
Above: Version C Revised Start Page
However, we think that some of the contents aren’t quite right. For example, some users think that the service is for procurement. Some users are still not sure what the benefits of the service are.
We will now test whether changing the language to specifically mention benefits helps as well as putting it at the top also makes it clearer what the service is for.
Changing how and where we tell users what info to increase engagement
We’re removing the new page we created on the information users need. Users said the contents were helpful but users didn’t see the link to it on the start page.
We’ll now use the details component both on the start page and in context on the self-assessment pages. We’ll test which location is more relevant to our users as well as the suitability of the details component.
Renaming the self-assessment ‘categories’ to mirror our users’ language
We’ve removed the word categories because we noticed that this wasn’t a word users were using. We’re now just calling it self-assessment.
Above: Category selection page with supporting help information included
Making the user journey clearer so users know what to do next
Once users have completed part of their self-assessment, we’ll return them to the self-assessment page instead of getting them to look at their recommendations. This is because it’s still unclear whether users want to see their recommendations straight away or whether they want to continue with their self assessment.
We’ll also test using a success badge (notification banner) with a link to their recommendation. This gives users a chance to ‘self-serve’ and us a chance to test what they want to do next.
Above: Categories (self assessment) main page with success call out and progression indicators
Adding content to recommendations to make them easier to read and complete
We’ve added descriptive headers to break up the recommendations. We’ve also added hypertext links to third party content to give some of the actions more context.
Above: Recommendations list page with descriptive headers
We now want to test whether users value having the recommendations presented together as one piece of content (like a checklist) or whether for comprehension and accessibility reasons, we will need to look at other ways of breaking down this content.
Above: Recommendation page using simpler headers and structure