CISCO VISION LOCAL CONTROL
The Local Control app is a consumer facing product intended to give suite and other area guests the ability to control their surroundings. Some main actions the app would provide included controlling TVs within a suite or area, viewing replays provided by the venue, ordering food and merchandise, requesting maintenance or other assistance needed, viewing stats, social media postings, and events.
There is also opportunity for ad or content placement as well as full brand customization of the app. In order to grant venue employees control of these areas and decrease continual revision efforts by the Local Control team, an admin portal was also in development at this time.
Time on Project: 6 months
I led the design and research efforts for this project as well as contributed to collateral development, project planning, product roadmap, and backlog management. I was responsible for the experience strategy, UX/UI design, research facilitation, and analysis for this product.
An important piece to this process was the ability to showcase sports teams and venue branding within the Local Control prototype. This re-skinning of the prototype displayed a real world use of the application to potential customers. By utilizing InVision, Craft, and Sketch libraries, other team members could quickly and easily create a custom prototype for their target audience.
While there were many interested parties based on the Local Control concept, the UX team was dismantled before continuation and completion of the app. Below is the process of that concept development.
Design Review Docs
Sketch + Craft
InVision: Prototyping App
Adobe Illustrator & Photoshop
JIRA: Project Management Tool
VERSION ONE: SAN FRANCISCO 49ERS
Coming into the project, there were some apparent navigation and UX issues. The team was working on the first release of Local Control at Levi's Stadium, then referred to as Suite Control, with a third-party development company overseas. I reviewed the app design and additional requests from Levi's with my UX manager and software developer before beginning the revision process.
Below are screenshots of the app as it was when I joined the team. Additional requests from Levi's included maintenance and utilities request pages with integration to the 24/7 API, ability to call a suite attendant for assistance, and a secret button for employees to exit the app or enter a different suite PIN.
INITIAL DESIGN UPDATES
Since the 49ers had already started their season, the initial focus was on implementing the additional feature requests and improving the basic navigation and flow of the app. This was done by adding a feature selection page which could be accessed from the main image carousel as well as including back buttons on each page.
UX/UI DESIGN OVERHAUL
In order to improve the user experience of Local Control and maintain consistency across our incubation products, the sidebar navigation and titlebar components were implemented. From there, I designed the feature pages with a more modern, user-friendly approach.
Roadmap features were included and displayed on the sidebar but their content was not shown to user testing participants.
Unlike many other Cisco products which are enterprise related, Local Control was a consumer facing product with a much broader user base. This enabled us to recruit participants and test the prototype with much more ease. However, confidentiality and internal legal requirements were still a factor. Because of this, we chose to test with internal Cisco employees and external parties who had an NDA signed by their company and stored on file.
FINAL DESIGN DIRECTION
After the user testing sessions, I discussed proper UI component building with our lead front-end engineer and revised the design based on an 8px grid in order to ensure responsive layouts. This is the design of Local Control the development team was working towards while I took on other projects. When time came to build out the rest of the features, I would be brought back for design, research, and grooming. Unfortunately the team would not have the chance to complete this project, though I do believe that if Cisco were to continue its development in the future, they would have both the design and development documentation needed to do so.