Key Goal  Using several key findings from the original software, design an easy to learn application that users could trust the data integrity.   Devices  Web- Responsive   Responsibilities  Research, UX Design, UI Design, Design System, Frontend D

Eventlink - School Datebooks

Research, UX Design, UI Design, Frontend Development
Web - Responsive

  Key Goal  Using several key findings from the original software, design an easy to learn application that users could trust the data integrity.   Devices  Web- Responsive   Responsibilities  Research, UX Design, UI Design, Design System, Frontend D

Key Goal
Using several key findings from the original software, design an easy to learn application that users could trust the data integrity.

Devices
Web- Responsive

Responsibilities
Research, UX Design, UI Design, Design System, Frontend Development

Roles & Responsibilities

Roles & Responsibilities

I was working remotely from Chicago while I collaborated with one other UX Designer, a team of web developers, and a team of iPhone and Android developers. All team members were remote. I wrote scripts for users interviews and research, facilitated white boarding session, and created interactive prototypes. We collaborated using slack, google hangouts, and an online white boarding app. I was also in charge of the design system.

The Process

The Process

Stakeholders were looking for a customizable and flexible product so everyone from athletic directors, secretaries, to coaches could personalize it for their specific needs. The company had bought an older product that wasn’t working well for their clients. We started with research to find out who are users are. We sat down and interviewed current clients to find out how they work, the pain points with the current software, and what sort of features would they like to see.

From there I started with several whiteboarding sessions to generate concepts, paper sketches, and wireframes. After selecting the two best designs I created interactive prototypes and began to test them with users. I was interested to know which one users preferred and which one they were able to move through quicker. Since our team was not centrally located, documentation was key throughout the process. I created and maintained a design system and documented all of the final design patterns, styles, and animations. It also served as a key part of our communication with both development teams.

eventlink.png