The Media Manager. UX Case Study
Name: The Media Manager
Discipline: Desktop version
Industry field: Digital media advertising
Timeline: April-May 2019
Tools: Axure, Figma, Miro, Excel
PRODUCT OVERVIEW
The Media Manager — is an admin panel for managing advertising display screens.
Our client is engaged in the installation and maintenance of advertising display screens in the apartment buildings hallways next to elevators. They are used to display ads, info blocks for residents and so on. But there was not any tool to control content shown on such screens.
The Media Manager solves such problem in next ways:
• helps to manage hardware
• enables the creation of content.
THE CHALLENGE
We faced with a problem that every single advertising display screen in different buildings through the city showed the same info and ads for their residents with totally different needs.
After discovery and interviews we found out that in most cases info on screens didn’t match requests, needs and wishes of residents — people didn’t find anything that concerned them and comment it just like
“time-killing screen while waiting for the elevator”.
The Media Manager is intended to help Admins create really useful content, relevant to every resident of the exact building.
DISCOVERY & RESEARCH
Activities
1. Requirements gathering
2. User Interviews
Interviews were conducted to collect information about people’s needs and factors that influence to pay attention to what is happening on the display screen. It gave us an understanding of the resident portrait in general. But the most important part was talking with potential Admins which allowed us to figure out their pain points, needs and wants.
Analyzing all the data we’ve received and business requirements we conclude that admin panel for managing hardware and content was a must.
IDEATE
Activities
1. User Stories
2. MVP requirements definition
3. User Flow
4. Use Cases
5. Role Matrix
First of all, we needed to organize everything and gave a structure to the product — based on received information User Stories, Use Cases, Role Matrix was described and so on.
On the stage of MVP requirements definition, we’ve selected main features from the long list and set the priority to each of them (based on the scale of the level of criticalness to the User and Business, and the complexity of implementation).
Then, User Flow was built to show the different processes involved in accomplishing a task from MVP — manage the content.
PROTOTYPING & TESTING
Activities
1. Wireframing
2. Prototyping
3. Corridor Testing
Quick wireframe sketching helped us transform all previous documentation into visual layouts and understood what gaps we had in the flow.
After that, we created a clickable prototype to check and test all our hypothesis and to study the way how people are interacting with the product on a Corridor Testing.
All problems and suggestions were described in a report and implemented in layouts.
CONCLUSION
To develop the best solution, we have focused on the UX Architecture of the future system and its consistency.
In a quite short time, 2 months, we have designed 2 different interfaces — for the Local admin and Super admin roles.
It allowed the Client to start the development process earlier than he planned.
This project is a good example of the productive cooperation of high-level professionals to create a decent MVP in a short time.