The initial design for the BETA release has the following pages:
- start page
- DfE sign-in
- internal start page
- a list of the self-assessment categories
- 5 self-assessment questions
- check your answers
- recommendations and maturity rating (low, mid or high)
- action points on how to meet the recommendations
These were created to enable user research to evaluate a complete user journey during the research cycle as well as the features, functionality and content.
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 1 prototype.
https://plantech.herokuapp.com/a
Start page
We used the standard GDS pattern, explaining who the service is for and what it’s for. Our service uses DfE sign-in so the button says ‘go to DfE sign- in’ rather than ‘start now’.
Above: Start page describing purpose of the service
DfE sign-in
This is standardized content which cannot be changed.
Above: Standard DfE Sign in stages
Internal start page
We included a rubric that explains how the service works. We explain that the school’s answers will not be shared with government. There’s a button that takes users to the question categories.
Above: Post login landing page
A list of the self-assessment categories
We gave further details about who may be best placed to answer the questions. There is a progress indicator. There is a call-out explaining that users can save and pause their progress. There is a hyperlinked list of all the categories with tags on categories which have been started or not started. 5 self-assessment questions (broadband)
Above: Technology self assessment categories page where users can initiate Q&A process in or out of listed sequence
We used the standard GDS question page design pattern. The questions are designed to assess how digitally mature a school is.
Above: Single page GDS pattern based entry pattern with additional question sequence positional indicator
The questions are also sequenced to assess a school’s maturity as quickly as possible. For example, if we determine a user may be low digital maturity, the user automatically exists the self-assessment and is taken to the recommendations.
Check your answers
We used the standard GDS pattern but also include how many questions the user answered and what category is next. Because our service is not a linear transaction, there’s a button that allows users to go to the recommendations or a hypertext link so they can continue answering self-assessment questions.
Above: Check your answers display adapted for long string text legibility
Recommendations and maturity rating
We gave users a digital maturity level rating (low, mid or high). We explain that there are actions the user can complete to increase their digital maturity. The actions are structured so that the most important ones are first.
Above: Recommendations display with maturity rating and list in order of impact (high to low) of recommendations. Also Note that global navigation becomes active when recommendations available
Actions points
We gave the users a specific action, for example, install fibre broadband (if the user said they had copper broadband). We explain how users can do this by breaking the action point down into specific tasks using the numbered list component. We also give contextual information about why the recommendation is important
Above: Recommendation page with points of action