Improving Tournament Check-in

Overview:

One of the many benefits of the Sift system is that all employee data is centralized for clients. Client side Software Engineers often request to get access to their companies employee data through API to run reports on Skills, Headcount, New Hires etc. The API request involved Sift engineers to handle the task becoming time consuming and costly.

Collaborating with the head of engineering, I led the overall design of the workflow that would allow client-side Software Engineers to request and develop their own API tokens.

Problem to solve:

Players who are registered for tournaments are not attending the event on time leading to no shows and smaller prize pools.

1. This leads to divisions with many inactive members which makes tournaments less fun 2. raises tournament cost due to unnecessary added divisions.

Hypothesis

By having users check into their tournaments, we can improve overall participation rate.

Current State

The tournament registration window begins when Ops creates a tournament and ends at the registration cutoff time. This leads to an automated/manual starter process and division-making before the tournament starts time. Then the tournament starts.

New Check-in flow and logic

Below is the flow for registration to the tournament start time. In the current flow, players are not required to check in, and this gap causes a drop in players starting on time. Furthermore, it makes the tournament pool difficult to predict if players are not attending games.

The option 1 & 2 adds the “check-in” step into the process and the timing of events.

Below is the full system flow for tournament signup through the check-in process. This helped determine how the UI should support the proposed tournament signup flow.