UX - Testing Purchase Paths

Hey y'all! hope everyone's weeks are starting well this cloudy Monday. I'm trying to develop a process for testing that may require enlisting more members of my organization in the process. It's not that I have difficulty on the programming side - much :D - it's that I can't always catch when a part of the ticketing request is missing something that makes the purchase journey less intuitive for visitors. We're a new, general admission venue, but we are developing more and more ticketed events. Do y'all use a check list for testers to sign off on, where they double check that the programming and messaging makes sense from a buying perspective? We definitely improve each time we host something big, but I'd like to be more proactive with addressing this before events go live. Thanks in advance! 

  • We definitely have others testing, including Guest Services managers/supervisors and the person(s) requesting the ticket build. We don't require a sign off but have the testers email  any issues they find.

    Here are the basics of what we test and review in Live before an on sale:

    • Performance dates and times
    • Available price types
    • Titles
    • Complete orders in app and web
    • Promo Codes, if any
    • Review of printed tickets (text and design), Boca and mobile
    • Testing of member benefits/entitlements
    • Review of starting and ending timeslots, and timeslot increments on sample days if using timed tickets
    • For long run admissions, e.g. for an exhibition, we review and test each day of the week for week 1 before copying to all subsequent dates
    • For programs like films, lectures, etc. we also compare the date and time of the performance to what’s listed on our web calendar as a double check, have caught more than one issue that way
  • Thanks so much Neda! We're such a new organization, every single event is a new experiment in ticketing. Your experience is really helpful.