AI Competency Centre · design round 1 · 7 November 2026

Canvas experience: design sampler

Three ways to organise the Canvas site and three visual styles, for Dominik and Ella to choose from. Structure and style are separate choices: pick one of each, or combine parts.

How to review

  1. Open each candidate. A Review button at the bottom right of every candidate lists all its screens and states, including the phone view and the slide reader with scripts turned off.
  2. Structure candidates (UX) are deliberately grey: judge the routes, not the look. Style candidates (V) share one layout: judge the look, not the routes.
  3. The slide reader is the screen that started this round. Every candidate restyles the same 16 slides from the BETT 2023 talk.
  4. Scores come from four independent model judges (two Claude Sonnet 5.5, two GPT-6.1 Sol) who did not build anything, using these journeys and constraints. They are a signal; your choice decides. Every score with its reason.
  5. Record your choice at the bottom and paste it into Teams or an email.

Structure: how the site is organised

Who finds what, in how many steps. Each serves the same nine journeys: revisit a session, read slides, choose and book, search, ask for help, share a session, give feedback, maintain the site, and cope with failures.

UX-A Front desk: home screen at laptop width

UX-A

Front desk

Task-first. The home asks what you came to do and offers four doors: materials from a session, find and book training, help for your team, give feedback.

8.2 / 10 judges' overall, range 8–9, 4 seats -0.1 since round 0

Journeys served7.8
First visit8.8
Back to my slides8.5
Not busy7.5
Clear for maintainers8.5
Canvas and phone8.5
What judges would keep and fix

Keep

  • The attendee-first homepage and session page's complete materials list combine clear starting guidance with fast access to the intended resource.
  • Keep the plain-language task entry points and session page that places the slides action beside a complete materials list.

Fix next

  • Preserve the originating session in standalone-reader return and feedback links instead of sending every deck back to the default session.
  • Carry the originating session into each standalone reader's return and feedback links so slides, recording and notes remain connected.

Open UX-A Slide reader Design notes

UX-B Programme: home screen at laptop width

UX-B

Programme

Time-first. Just added, coming up and bookable, and an archive by month and series. The session page is the single unit holding everything.

7.3 / 10 judges' overall, range 7–7.7, 4 seats +1.0 since round 0

Journeys served7.5
First visit8.0
Back to my slides7.0
Not busy7.2
Clear for maintainers8.5
Canvas and phone7.5
What judges would keep and fix

Keep

  • The five-record explanation, MondAI publishing sequence and expandable missing-material checks make the maintenance consequences of the design unusually clear.
  • Keep the calendar's separation of dated and month-only sessions, explicit Canvas escape route and course-to-past-session relationship.

Fix next

  • Carry the originating session identifier into each standalone reader and its return and feedback links so opening slides preserves the route to that session's recording and notes.
  • Preserve the typed query in a results history entry before opening a live suggestion, so Back restores the search.

Open UX-B Slide reader Design notes

UX-C Library: home screen at laptop width

UX-C

Library

Browse-first. One library workspace: collections and filters on the left, a searchable list, and a preview of the selected item.

7.2 / 10 judges' overall, range 7–7.7, 4 seats +0.8 since round 0

Journeys served7.0
First visit7.2
Back to my slides7.5
Not busy6.5
Clear for maintainers8.2
Canvas and phone8.5
What judges would keep and fix

Keep

  • URL-encoded search and filter state, removable filter chips and a clear reset action make browsing and recovery understandable.
  • Keep the visible filter chips, recoverable empty search state and maintainer inventory showing missing materials.

Fix next

  • Restore the dated-event calendar with a separate month-only list as another view of the existing library records.
  • Make each session row open its session directly and provide a direct slides action, removing the desktop preview as a required intermediate step.

Open UX-C Slide reader Design notes

Visual style

The same home, session page, slide reader and components, styled three ways. All keep Oxford blue as the anchor and must work inside the Canvas frame, on a phone, and without scripts.

V1 Oxford editorial: reader screen at laptop width

V1

Oxford editorial

A quiet academic publication: serif headings, warm paper, Oxford blue and a little gold. Slides read like numbered figures in a journal.

8.6 / 10 judges' overall, range 8.3–9, 4 seats +0.2 since round 0

Slide reader8.5
Hierarchy8.2
Oxford, light, calm9.0
Consistent system8.5
Designed states8.8
Access and phone8.0
What judges would keep and fix

Keep

  • The numbered editorial reader, framed figures and quiet original-slide links turn converted slide content into a readable publication.
  • The numbered editorial slide panels, quiet original-slide links and restrained warm-paper, navy and gold identity.

Fix next

  • Compact the phone reader introduction so the contents control and meaningful slide content appear sooner, while retaining the session title and recording route.
  • Give pale extracted icons a contrasting navy backing in both reader implementations while retaining their restrained figure size.

Open V1 Slide reader Design notes

V2 Centre signal: reader screen at laptop width

V2

Centre signal

The approved pink and navy event-library identity, made calmer. Pink becomes the accent; slides sit on a stage as slide-shaped panels.

7.8 / 10 judges' overall, range 7–8.3, 4 seats +0.4 since round 0

Slide reader7.5
Hierarchy7.8
Oxford, light, calm7.8
Consistent system8.5
Designed states7.8
Access and phone7.8
What judges would keep and fix

Keep

  • Restrained pink selection markers preserve the Centre's identity while pale panels and white reading surfaces keep the interface light.
  • The restrained pink active markers, explicit slide number bands and small navy-backed illustrations that remain visible without scripts.

Fix next

  • Reduce the reader's typographic intensity by reserving bold condensed type for major headings and using the regular body face for contents and supporting labels.
  • Reserve the heaviest condensed type for major headings and use a lighter, more open treatment for slide headings, contents entries and supporting labels.

Open V2 Slide reader Design notes

V3 Calm studio: reader screen at laptop width

V3

Calm studio

A light, contemporary product feel: one sans family, white panels on a cool background, and a colour code for material kinds.

8.0 / 10 judges' overall, range 8–8, 4 seats +1.0 since round 0

Slide reader8.0
Hierarchy8.0
Oxford, light, calm7.5
Consistent system8.2
Designed states8.2
Access and phone8.0
What judges would keep and fix

Keep

  • Material pills combine colour, icon and text, making resource types easy to distinguish without relying on colour alone.
  • The unavailable-material panel's direct recovery buttons and the clearly labelled, optional feedback slot with a compact five-point rating.

Fix next

  • Use a light first-slide panel beneath the navy reader introduction to reduce the visual weight of the repeated title and bring the opening into the white-panel reading system.
  • Condense the phone reader's introductory title band so the repeated title treatment leaves more room for slide content and navigation.

Open V3 Slide reader Design notes

Questions the candidates raise

These came up in the builders' notes and the judges' reports. They hold whichever candidates you pick.

  1. Courses and events: one list or two? UX-C mixes them in one library. UX-A and UX-B keep "sessions we ran" and "training you can book" apart.
  2. Feedback: which service? Every candidate shows only a slot. The choice is an Oxford Microsoft Form or an approved conversational assistant. Each candidate's design notes say which it mocked and why.
  3. Typefaces: V1 and V3 pair a serif for headings with a sans for the interface, and V2 keeps the current Barlow. Should the University typeface guidance decide this? Whichever we choose would be hosted with the site rather than loaded from Google.
  4. Centre pink: V2 keeps it as a small accent, and V1 and V3 drop it. Should the Centre's pink stay visible?
  5. Dates: should the archive group sessions by Oxford term or by calendar month? The content has no term dates yet.
  6. Presenters: event records do not list presenters, so no candidate can show "who ran this". Should presenters be added to the records?

Decided already, not a question: each of the 62 slide readers becomes its own page in Canvas, with a contents list, slide numbers and previous/next generated from the existing markup. Every candidate's reader works with scripts turned off.

Today, for comparison

The current unstyled slide reader in the sandpit

The current sites were scored on the same rubric: 4.5 for structure and 3.6 for style. Two homes grew separately (the course-first sandpit and the pink and navy event library), and the 62 converted slide readers have no styling.

Event library home · Event page · Sandpit home · Sandpit slide reader

Your choice

Nothing is sent anywhere. This builds a short text for you to copy.

Structure
Style