esonux_logo-01.png

ESPN UX

Defining/implementing an iterative design process

BACKGROUND:

ESPN UX is a small team that was brought together to create the best experiences possible for sports fans. Over the course of 4 months the Senior Director of Design and I worked to set up guidelines for the UX Design team. From these meetings, we created a tactical process to follow, then disseminated this documentation to our colleagues to understand our iteration on ideation. Working with our Project Management team, we implemented this design system into our everyday workflow.

My ROLE:

Over the course of 4 months the Senior Director of Design and I worked to set up guidelines for the UX Design team.

COMPONENTS:

Guiding Principles, High-Level Documentation, New Project Checklist, Prototype Checklist, Tech Integration

 

 

 
espn-ux_guiding principles-001.png

1) Guiding principles

A main component of establishing our team was creating a set of principles to follow throughout our work. These principles are meant to drive our process and culture of UX. We tied these ideals back the mission of 'Serving sports fans anytime, and anywhere'.

 

 

2) High Level Documentation

This was our first documentation of the process as a basic standard to achieve. With each project we leverage these components and adapt based on project needs, resources and deadlines: process can always be changed.

espn-process-highlevel-document.jpg
espn-ux-process-documentation-001.png
 

 

3) New PROJECT CHECKLIST

For further integration of UX into the design process my team and I created a project checklist to allot for tactical management of all new projects. This organization has allowed us to easily acquire all requirements from partners and create achievable deadlines.

Photo Nov 15, 5 06 22 PM.jpg
 

4) PROTOTYPE CHECKLIST

We established a prototype checklist to achieve all goals for user testing and better integrate prototyping.

Photo Nov 15, 5 06 34 PM.jpg
 

 

5) TECH INTEGRATION

For our final component of the process we developed a plan for when to incorporate our tech partners. We experienced a lack of communication early on and sought to solve this by mapping our where and when we can include QA and Development to gain their insights as well as understand limitations we may experience during implementation. The earlier we can leverage their knowledge the better experiences our team can create.