1. Schools autocomplete

    An autocomplete for selecting partner schools quickly

  2. Location labels and survey research

    First attempts to understand location with a classification exercise

  3. The location problem

    Location is a complex issue, we begin to break it down

  4. Hide discontinued training locations

    Do not show these locations to avoid confusion

  5. Edit a course outcome

    Allow providers to choose an outcome, instead of using our inferred one

  6. Course statuses – 15 October iteration

    We have uncovered more complexity around course statuses on UCAS

  7. Copy content – 14 September iteration

    Make the copy feature easier to find

  8. Copy content from another course (Live)

    We changed this feature when we built it

  9. Welcome email

    The email we send when users first sign in

  10. Enrichment release – 6 September

    Publish courses, as it was released with the course enrichment feature

  11. Contact details

    Allow users to edit their contact details

  12. Iteration – 24 August

    Split homepage into tasks, Step 1 and Step 2

  13. Iteration – 23 August

    Trying to bring ‘About your organisation’ into the user journey

  14. User research – 22 August

    Testing markdown, SimpleMDE and publishing workflow

  15. Who did what and when

    The beginnings of an audit trail for content

  16. Preview course

    Different preview states depending on course type and state

  17. Terms agreement

    A user must agree to terms before enriching

  18. Fields we ask for and why

    Documentation of needs around each course field

  19. Copy content from another course

    Design for copying form values from one course to another

  20. Formatting

    Paragraphs, lists and links

  21. No more course folding

    Reasoning behind not folding courses and unfolded course designs

  22. Success messaging

    Messages we show after a successful save or publish

  23. Course statuses – 3 August iteration

    A more indepth look at UCAS course status and how it will affect publishing

  24. Story map – 1 August 2018

    Screenshots of the end to end journey from publish courses to search and compare

  25. Validating on publish

    How validation works when a user tries to publish without the required fields

  26. UCAS course status

    An iteration on the onboarding design (read-only) to include course status

  27. Salary and fees

    Designs for different fields for salaried and fee paying courses

  28. When a user is not recognised

    Designs for when a user’s email is not in our whitelist

  29. Templates

    Use templates to share information between courses

  30. Shared organisation details

    Share organisation information between courses and split the organisation page across tabs

  31. Managing multiple organisations

    Some users will be responsible for courses from multiple organisations. eg SCITT-schools

  32. Request access

    Request access for users

  33. Iteration 28 June 2018

    Add character counts and refine preview

  34. 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

  35. Iteration 26 June 2018

    Separate courses by accrediting provider. Provide explicit fields for each course offered.

  36. Draft of a read only version

    An initial pass at what a read only view of the service could have looked like

  37. Draft of the QA process

    Submit to QA and example pass and fail emails

  38. School direct view – Iteration

    An iteration of the school direct view tested with Kingston School Direct

  39. School direct view

    School Direct routes are the most complex. List schools, show multiple UCAS courses per subject, show folded course summary.

  40. A university’s view

    Universities are the simplest provider. There are no schools to apply to and no course folding.

  41. 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

  42. Contextual guidance on course fields

    A first pass at providing some guidance for each course field. Starting from the original onboarding guidance

  43. Sign-in: User registers themself

    We send users a sign-up link so they can register and then be forwarded on to our service

  44. 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

  45. Course folding and UCAS course details

    Following the definition of a course, documentation on how we might fold courses based on UCAS data

  46. Course with variants and field guidance

    Exploration of a course page with fields to capture variants of a course and the differences between them

  47. What is a course?

    Work to define our definition of a course

  48. Courses and tabs

    Exploration of a home page view with tabs for courses, schools, default course and organisation details

  49. Original onboarding

    The spreadsheet sent to providers rendered as a single page form

  50. Course with parts

    Experimental designs looking at breaking course fields onto different pages, based on a theme