With almost 1,000 responses we now have sufficient data to consider some improvements. But first, a summary:
Closed questions
| Question | Strongly agree | Agree | Disagree | Strongly disagree |
|---|---|---|---|---|
| Told me what I needed to know | 19% | 61% | 13% | 7% |
| Found page interesting | 29% | 59% | 9% | 2% |
| Page was easy to use | 31% | 51% | 12% | 6% |
| Clearly identified my next steps | 20% | 55% | 19% | 6% |
Clearly identified next steps by role
| Role | Strongly agree | Agree | Disagree | Strongly disagree |
|---|---|---|---|---|
| Secondary school student | 22% | 53% | 21% | 4% |
| University student (UG) | 18% | 59% | 18% | 5% |
| University student (PG) | 21% | 62% | 15% | 2% |
| University staff member | 16% | 40% | 25% | 19% |
| Working in the education sector | 14% | 64% | 13% | 9% |
| Other | 20% | 46% | 26% | 8% |
Respondents
| Role | |
|---|---|
| Secondary school student | 18% |
| University student (undergraduate) | 31% |
University student (postgraduate) | 27% |
| University staff member | 8% |
| Working in the education sector | 8% |
| Other | 15% |
With almost 1,000 responses we now have sufficient data to consider some improvements. But first, a summary:
| Description of improvement and benefit/value | Effort estimate | Priority (MoSCoW) | Decision | Done | Checked |
|---|---|---|---|---|---|
| From survey: Clearer calls to action / pathway through to degree obscure (Paul: People seem confused with 'actions' being on second tab and third tab being a 'dead end'.) Often requested. Benefit would be greater 'conversion' and lower bouncing out. Team ideas include:
| tba | Must | Act | ||
From survey: Performance, slow loading, needs to load quicker, why spinner spins for so long? Often requested. Benefit is greater conversion, better feeling towards us, etc. Caching work has helped, but do we need a plan to improve further? Team ideas include:
| Must | Watch | |||
From survey: Easier path to faculty/staff/key people Most often requested. Benefit is that many visitors want to learn about staff and get there quickly. This might best be developed with 'search' but maybe a placeholder could be a 'staff in responsible school' widget. Team ideas include:
| Must | Analyse | |||
From survey: Link to all courses in a subject. (Paul: One of three use cases that a course listing widget could meet, maybe increasing the benefit from this feature). Often requested. Benefit is promoting courses better, or at least increasing their visibility. Course details also enrich subject/degree pages, as the detail does matter to many people. Team ideas include:
| N/a | Ignore | |||
From survey: UG/PG next to each subject on About tab. (Paul: Could do same on navigation/taxonomy page) Often requested. Benefit is earlier signposting of suitability for the reader. Team ideas include:
| Should | Act | |||
From survey: Paul: Confusion on why the degrees, requirements and courses are not profiled here. How do we signpost when people browser browse study areas and when they go to degrees? Often requested, but in many different wordings. Benefit is user clarity Team ideas include:
| Should | Watch | |||
From survey: Ken Ryan: When people use the 'read full story' button it would be good once they have ready the story to have a button that will take them back to where they were reading before they clicked it. Team ideas include:
| Should | Wait | |||
Introduce a 'compare majors' function (Paul: Would this be best on a degree page? Would it pull 'subject' info and requirements? Do we wait for a search solution or a new app?). Team ideas include:
| Could | Wait | |||
| From survey: Headings all at the same level. More levels would make reading/understanding easier | Could | ||||
| From survey: Add in a 'Click here if you want to:' drop-down of shortcuts to most commonly performed actions. | Would | ||||
| From survey: Side bar or alternative navigation to change subjects quickly on the Study options tab | Would | ||||
| From survey: |