Case Study #1 (Product Owner/Designer)
28 December 2021
Summary
Boost Test Planner (AKA NightRider) was an automated testing platform designed specifically for testing cinema websites for the Boost devision of the Box Office Company. Tests covered everything from ticketing, concessions, seating, gift cards and loyalty accounts.
Test Planner began solely as an internal project for the Boost ticketing platform that was used by over 100 cinema chains worldwide. As they were all using the same code with branding and custom features enabled via a CMS, I pointed out that automated tests could be used to ensure all the different scenarios were being tested with each deployment. After setting these up, these proved successful and it wasn’t long before I was asked to demo the tests to the CTO of a major cinema chain in the UK who expressed an interest in buying into the idea if we chose to expand on it.
For developing the idea into a client facing interface, I was made responsible for conceptualising the product functionality, developing the product roadmap and designing the user flow and user interface.

Problem Statement
As an organisation, I want to be able to schedule automated tests for my cinema website that are tailored to my specific user journey
Approach
As I already had the automated tests set up to cover the different scenarios running through the consol, the challenge then became developing the user interface that would enable users with less techincal abilities to use the product. I began by speaking with cinemas externally as well as the internal QA team to identify the use cases. I then reviewed existing automated testing platforms to get an idea of the user flow and broke down the different requirements:
• It would need to be used internally for scheduling tests for multiple cinemas.
• It would need to be used externally for scheduling tests for individual cinemas.
• It would need to be used both internally and externally for viewing and comparing test results.
This allowed me to prioritise the roadmap based on what I currently had vs what I considered to be a finished product. This was broken down in such a way that would allow me to release parts of the product sooner rather than later but would also allow for me to scale it up as it grew.
• Develop a prototype user interface where an internal user could log in and view the test results for multiple cinema chains.
• Develop a dashboard for external users to access their test results to track the progress of any bugs identified with the product.
• Expand the tests so they covered more scenarios ranging from the different payment providers to booking fees etc.
• Integrate the ability to schedule and run tests through the dashboard for internal users so they no longer relied on the tests being run through the consol.
• Make the scheduling and running of tasks available to external users.

Results
The Boost Test Planner proved a highly successful internal tool that showed great potential for becoming an external product we could sell to the masses. Unfortunately, before we were able to reach the stage where we could sell this externally, the COVID pandemic hit cinemas worldwide and the company were no longer able to invest in the product as they moved their focus towards trying keep cinemas open.
For me the most enjoyable part of the experience was the enthusiam others had for what started out as a personal project of mine that grew into it’s own team. The biggest challenge, however, was finding the balance between a tool that could be used internally by developers with a techincal background and those external users with no initial understanding of the process.
The experience of conceptualising and designing this product is what inspired me to move forward as a product designer with Giki and expand my design skills further.