Dashboard

A new landing experience

Teletory is an object management platform designed for telecom practitioners. Users can perform tasks like network planning, equipment maintenance, breakdown monitoring, etc. However, the platform was designed to be object centered instead of task centered. To perform a task, the users had to first search for relevant objects and then work on each of them. This process was not intuitive and cause lots of pain. My team and I built this dashboard to provide the users with a more intuitive way of completing their work.
*This project is protected by NDA. Images and names were modified.*

Duration June 2016 - September 2016
Role UX Designer, Project Owner
Tasks Interaction Design, Visual Concepts, Prototyping, Project Management
Team 1 UX Researcher, 1 UX Designer, 4 Developers
Result High fidelity wireframes

DESIGN PROBLEM

How can Teletory help users to perform tasks more easily and effectively with a landing experience?

Problem Space

The homepage of Teletory was mainly a search feature. It was the start of any kind of task. This design was not a natural routine for people to do their work. For a user, what came to mind first would be: I want to do A, instead of I need an X . The lack of CTA has caused a very steep learning curve. Only experienced users could perform well on the product.

Persona Highlight

Gary Rimes, Network Planner

"I have 10 years of experience in telecommunication industry. Usually I need to plan resources for certain sites. Sometimes I adjust resources among sites to import new customers and make sure everything's working fine."

User Needs and Goals

Based on user research, Gary's goals were to:
First, Monitor the physical objects he is responsible for. Second, Check his new tasks. Third, Finish the planning for certain services.

Ideas and Conversations

With what users want in mind, I started to brainstorm solutions. During this process I used lots of sketches to collect insights from my colleagues, who have been in telecom industry for years. The basic framework emerged quickly. The dashboard would directly provide actions that a user can take, important objects that a user need to monitor, today's tasks, etc.

Workflow & Interactions

While generating as many ideas as possible, I also took a step back thinking about how this landing experience works. I illustrated the workflow on UI and the system workflow, which helped explain how interaction will be triggered technically. These workflows helped the team communicate right to the point and kept everyone on the same page.

Rapid Iteration

Starting with rough sketches, I kept tweaking the details and simplifying content on the dashboard. The iteration was rapid and tense. I kept communicating with internal users and got lots of input from them. One take-away from this process was that it's important to figure out what material will serve the best when asking for a design critique. People could get distracted by visual details, which makes communication inefficient.

Key Feature - Location Panel

Location panel helps network planner to monitor the services at certain locations. It consists of all the locations assigned to this user. I designed two views for this panel. The list view helps the user to quickly spot any capacity issues and edit a location by clicking on its name. The map view helps the user to get a sense of the geographical distribution of these services. When planning for a new location, the user can also take geographical factors into consideration to make a valid decision.

A challenge - Integrating the new feature

One of the challenges emerged when I tried to integrate Dashboard and existing homepage. For enterprise product, it's very important that the new feature does not affect users' work but also attracts the users to explore about it. Since the Dashboard would be the first landing experience in the future, I needed to make sure that users can understand the feature without feeling deprived of the routine that has already been established. So I compared three solutions and adopted the last one, which proved to be valid in the usability study.

Outcomes, Compromises & Future Steps

The usability studies have proved that the Dashboard is a successful solution of the design problem. However, due to the tight timeframe and technical limits, I made several compromises: The size of the panels are all fixed instead of responsive. Users cannot ‘design‘ their own panel. In the future, the panels will be customizable and responsive to different screen sizes. A user can tailor the content they'd like to show on the dashboard and customize an efficient experience. The selected panels will adapt themselves to different screen sizes to bring more flexibility.