Posts
-
Schools autocomplete
An autocomplete for selecting partner schools quickly
-
Location labels and survey research
First attempts to understand location with a classification exercise
-
The location problem
Location is a complex issue, we begin to break it down
-
Hide discontinued training locations
Do not show these locations to avoid confusion
-
Edit a course outcome
Allow providers to choose an outcome, instead of using our inferred one
-
Course statuses – 15 October iteration
We have uncovered more complexity around course statuses on UCAS
-
Copy content – 14 September iteration
Make the copy feature easier to find
-
Copy content from another course (Live)
We changed this feature when we built it
-
Welcome email
The email we send when users first sign in
-
Enrichment release – 6 September
Publish courses, as it was released with the course enrichment feature
-
Contact details
Allow users to edit their contact details
-
Iteration – 24 August
Split homepage into tasks, Step 1 and Step 2
-
Iteration – 23 August
Trying to bring ‘About your organisation’ into the user journey
-
User research – 22 August
Testing markdown, SimpleMDE and publishing workflow
-
Who did what and when
The beginnings of an audit trail for content
-
Preview course
Different preview states depending on course type and state
-
Terms agreement
A user must agree to terms before enriching
-
Fields we ask for and why
Documentation of needs around each course field
-
Copy content from another course
Design for copying form values from one course to another
-
Formatting
Paragraphs, lists and links
-
No more course folding
Reasoning behind not folding courses and unfolded course designs
-
Success messaging
Messages we show after a successful save or publish
-
Course statuses – 3 August iteration
A more indepth look at UCAS course status and how it will affect publishing
-
Story map – 1 August 2018
Screenshots of the end to end journey from publish courses to search and compare
-
Validating on publish
How validation works when a user tries to publish without the required fields
-
UCAS course status
An iteration on the onboarding design (read-only) to include course status
-
Salary and fees
Designs for different fields for salaried and fee paying courses
-
When a user is not recognised
Designs for when a user’s email is not in our whitelist
-
Templates
Use templates to share information between courses
-
Shared organisation details
Share organisation information between courses and split the organisation page across tabs
-
Managing multiple organisations
Some users will be responsible for courses from multiple organisations. eg SCITT-schools
-
Request access
Request access for users
-
Iteration 28 June 2018
Add character counts and refine preview
-
Check your UCAS data (Initial launch)
A read-only version of the tool where users can validate their imported courses and request access for users
-
Iteration 26 June 2018
Separate courses by accrediting provider. Provide explicit fields for each course offered.
-
Draft of a read only version
An initial pass at what a read only view of the service could have looked like
-
Draft of the QA process
Submit to QA and example pass and fail emails
-
School direct view – Iteration
An iteration of the school direct view tested with Kingston School Direct
-
School direct view
School Direct routes are the most complex. List schools, show multiple UCAS courses per subject, show folded course summary.
-
A university’s view
Universities are the simplest provider. There are no schools to apply to and no course folding.
-
Show details from UCAS
Indicate the raw information we’ve received from UCAS, begin to explain where this must be edited and how we are handling that information
-
Contextual guidance on course fields
A first pass at providing some guidance for each course field. Starting from the original onboarding guidance
-
Sign-in: User registers themself
We send users a sign-up link so they can register and then be forwarded on to our service
-
Sign-in: Invite a user
This is the approach we attempted first. Because of limitations with the invite email and users ending up at a dead-end, we switched to self-registration
-
Course folding and UCAS course details
Following the definition of a course, documentation on how we might fold courses based on UCAS data
-
Course with variants and field guidance
Exploration of a course page with fields to capture variants of a course and the differences between them
-
What is a course?
Work to define our definition of a course
-
Courses and tabs
Exploration of a home page view with tabs for courses, schools, default course and organisation details
-
Original onboarding
The spreadsheet sent to providers rendered as a single page form
-
Course with parts
Experimental designs looking at breaking course fields onto different pages, based on a theme