BACK TO PLATO

TESTING & CONCLUSIONS

Final usability check

I ran a quick validation round with teachers and visitors on two core tasks: Buy a ticket and Book a class, and captured a Single Ease Question (SEQ) after each. “Buy a ticket” scored in the easy - very easy range; “Book a class” landed around neutral - easy, mainly due to questions about availability and group size.

What I asked & what the user said

  • “How clear is the path from the homepage to What’s On?”
    Clear, especially with the card layout; the 3D hero was engaging but some wanted a tiny tooltip to explain hotspots.

  • “Where did you hesitate in checkout or booking?”
    Date/slot clarity and capacity info; a few expected invoice fields and accessibility notes earlier.

  • “Does the interface feel like PLATO?”
    Yes, neon, rectangles, crisp type carried through.

  • “Anything missing for teachers?”
    Filters for suitable age/subject, option to state language preference, and invoice/VAT details up front.

Where PLATO can keep improving

Aesthetically the identity holds, but the bigger wins are in flow depth:

  • Exhibitions & Archive: add filters/sort (Year, Artist, Medium, Theme, Venue) and quick search, so discovery scales beyond scrolling.

  • Programme: Book a class: offer more options at selection time (group size tiers, language CZ/EN, accessibility needs, learning goals, invoice/VAT toggle) and clearer slot capacity.

  • Hero 3D: add a brief hotspot guide + reduced-motion fallback to keep it inclusive.

  • Microcopy & states: reinforce empty/waitlist states and confirmation details (teacher pack, arrival checklist).