Paciolan – Stanford's Mobile App

Case Study

Back

Paciolan, a leader in ticketing, fundraising, marketing solutions and #1 for college athletics and performance art software white labels their products and among their main ticketing platform provides customers with native apps and websites.

Problem to Solve:

Stanford, a large customer for Paciolan was up for contract renewal and submitted an RFP with an update to date ticket purchasing app for their students/alumni/fans to interact with Standord athletics and buy tickets

Proposed Solution & Goals

Turn around a quick solution in the form of a mobile app to demo to Stanford and get feedback on, demonstrating our commitment to their program and our quick design process. Upon approval and contract renewal, hand over to mobile dev team to start work, and deliver to customer.

Targeting Users

Paciolan offered multiple products relating to ticket sales but affecting different user types. It was important to spearhead the users that would interact with this most and build for them. This also aligned the dev teams to see who the users they were building this for and why we did certain things the way we did them.

Design Process

Being a part of the conversation early on helped UX deliver quick design, we were in the meetings with Sales and the customer to go over the RFP, the features needed and their pain-points with their current solution.

We took a look at their current app, competitors as well as out of market inspiration and created a basic redline flow to ticket purchase as this is the main goal for the customer. We then jumped into information architecture, sitemaps and flows and pieced the entire puzzle together.

High fidelity mocks were constructed after feedback of the flows and look from Stanford and we created multiple prototypes for them to explore.

Validation

Sales was a big part of our feedback loop for this project, the sales director was involved in the process throughout the project and kept the customer in the loop. When getting into prototypes the customer came into the conversation and shared analytics with us that helped drive decisions.

Outcome

Even before the finished design was presented to the customer the contract was renewed, the customer was so happy with how we handled their account and the turn around time as well as quality of the design.

We then documented spec for the developers, created assets and handed the project over to Engineering for development. We remained in a support for to answer questions and provide flows for unexpected situations that arise from QA tests and engineering feedback.

  • Customer engagement led to quick turnaround
  • Design only renewal led to validated code
  • Big account helped brand recognition
Return To Work

Contact me via the links below: