SKIVA
Admin Flow
previous work: SKIVA
Overview
I began work on the Skiva project as part of my first courses at MICA. For the first portion of the project, I tackled the gameplay flow.
For the next step of this app, and my MICA capstone project, I turned my focus to league creation and the admin user type. I explored how a player might become an admin for a small league.
Role
Research
Product Design
Prototyping
Branding
UX/UI Design
Timeframe
8-Week Project
March – May 2022
Project Plan
This project took place over 8 weeks of classwork. I outlined the tasks to be done using a Gantt chart in order to ensure I stayed on schedule during the tight timeframe.
Research
Problem Statement
Disc golfers need an easy way to create leagues, add players, digitally distribute tags, and track exchange.
Provisional Persona
During the gameplay flow creation, I focused mainly on the Player, who I call Avery.
And for the next phase, I thought I would be focusing on my Admin, Drew. But, by conducting expert interviews, I realized I was actually designing for a new user persona, Page, a player turned admin.
Paige
new admin
Goals
Fitness + Outdoor time
Develop Friendships
Track Status Effectively
annoyances
Time Spent In App Is Time Not Playing
Keeping Rankings Straight and Fair
Tag Hoarders Keeping Low Tags All Season
Wants + Needs
easy pick-up rounds with friends
encouragement to get outside and play
the competitive rush of friendly play
statistics tracked over entire season easily
high community involvement
Problems To Solve
Creation
Name the league + describe
Add the players
Set home course
Set league night and time + place
Set First Tags date and place
Management
Add / remove players
Modify name + description
Modify home course
Modify league night
Change players tag numbers
Mid-Fidelity / User Testing
Discovery
For my first attempt at a flow for the admin prototype, I tested to discover some basic things:
Does the league creation location make sense?
Is league creation easy?
Are edits to the league easy to make?
Critique + Revisions
SEASON DATES +
INTERNAL JARGON
Feedback
Determining the start and end date during the flow created a feeling of anxiety.
Users didn’t know when their friends might want to start or when a good end date might be.
Users newer to disc golf had trouble understanding internal jargon like PDGA.
Iteration
Version 02 simplified season start and end dates by providing pre-determined season options.
Tag distribution is broken onto another screen to relieve some cognitive load.
Jargon, like PDGA, is called out in a tooltip with a link to more information.
version 01
version 02
version 01
version 02
SEASON DATES + INTERNAL JARGON
Feedback
Determining the start and end date during the flow created a feeling of anxiety.
Users didn’t know when their friends might want to start or when a good end date might be.
Iteration
Version 02 simplified season start and end dates by providing pre-determined season options.
HI-FIDELITY
High Fidelity Prototyping
This final prototype balances clean, friendly design with my research findings for a full admin league creation flow.
Reflection + Next Steps
01
Next Features
With this admin flow roughed out, there are still a few key features to be added before MVP is achieved. I want to look at Challenges, History, and the User Profile. I feel confident in iterating on these features because of the strong foundation of these first two flows.
02
Maintain Focus
As with the first flow, I learned that by taking the project slow and focusing on the MVP, I can create space to focus on the essence of a project and make meaningful progress.
03
Continue
My next steps would be to continue building out the remaining elements, hand off to the engineering team, and get a working bata out to users for next season.