Reduced the number of errors in database related workflow by 81.8%
Increased productivity of database admins and application developers by improving workflow efficiency
Hercules

Simplifiying database management for T-mobile

USER RESEARCH · PRODUCT DESIGN · ENTERPRISE SAAS
Database admins and developers were relying on multiple tools and spread sheets to track, manage and maintain T-Mobile's databases was causing decreased productivity and increased risk of errors.
Vax cover image that consists of the latest design changes and a few components

Project Overview

Company

Project duration

Summer 2022 (6 weeks)

Role

Product Designer
I co-led the entire design track from requirements gathering to developer handoff. This was a zero to One product.

Contribution

Formative Research
Interaction Design
Usability Testing
Visual Design

Collaboration

Senior Product Manager
Principal Designer
Product Designers
Engineers
Database Admins
Visual Designers

Disorganized database management

Multiple tools and spreadsheets were used for database workflow

Application Delivery Teams and Database Admins at T-Mobile relied heavily on spreadsheets to manage, maintain, and track database-related details. Additionally, depending on database technologies such as Oracle, SQL, and Cassandra, they had to refer to dedicated software to obtain more details. This resulted in occasional application downtime caused by human errors and developers spent time fixing these issues.
Vax customer journey - A flow chart of how vax works
Need for streamlining database workflow
The business wanted to build a tool that unifies all the database related workflows into a new tool called Hercules. Our goal was to design a database management inventory tool that helped both database admins and  application owners find databases and applications details at one place.
Problem statement

How might we design a centralized dashboard to simplify database management for T-mobile

Approaching with a strong disbelief

Though our team had prior experience designing database-related workflows and a strong technical background, we recognized the need to approach the stakeholder requirement with fresh eyes without any preconceived bias.

Hence, we crafted a research plan with the subsequent objectives in order to foster collaboration with database admins, product managers, application owners, and developers.

Research Goals

1. Understand the needs and pain points of end users
2. Unbiased perspectives from both database admins and application owners
3. End-to-end workflow analysis to identify bottlenecks, redundancies, and areas where the tool could streamline processes
4. Consider scenarios where users face difficulty and inefficiency

Focus groups instead of traditional interviews

While developing tools for internal teams, we recognized the domain expertise held by database administrators and developers in influencing design decisions, which can be affected by their individual biases. Our objective was to gain a comprehensive perspective on user requirements over individual stakeholder needs. Therefore, we arranged focus groups that involved representatives from both the user groups and stakeholders, with the aim of gathering diverse perspectives.

Subsequently, we conducted semi-structured interviews with database administrators to grasp the intricacies of the database technology's structure. Additionally, a competitive analysis was performed to uncover strategies employed by competitors or industry leaders. After sifting through numerous insights through sticky notes, we distilled the findings into key themes that could potentially simplify the database workflow.
01
Database inventory and details
02
Database visualization
03
Database operations
04
Application inventory and details
05
Database report generation
06
DB Patching and decommissioning
Prioritizing features for maximum impact
As users had a lot of requirements, we had to prioritize problems/opportunities that should be solved for our first phase of release. We used thoughtful execution framework to identify the opportunity mountains that has biggest impact and immediate need for the user.
Vax customer journey - A flow chart of how vax works

Establishing the guiding principle

View only tool to find database details for the first phase

We needed to find the perfect balance among a diverse set of user needs; achieving this was a task, as each of them had different expectations from individuals' end.

Constraints

01
Quickly able to find information with minimal interactions
02
Clear and to the point details in minimal space
03
6 weeks deadline and limited developer efforts

Goals

01
Improve database management workflow
02
Enhance efficiency of the users
03
Streamline tracking and retrieval of database information
Generating ideas through crazy 8
We conducted a 'Crazy 8' workshop with an expanded team to delve into the perspectives of designers at various levels and how they would tackle this challenge. Several of these exploratory exercises unveiled new ideas that significantly influenced the outcome of our final product.
Finding the right approach
Instead of directly adopting a predetermined approach recommended by stakeholders and end users, we embarked on a journey of exploring four distinct approaches, guided by the principles of the thoughtful execution tree. This method facilitated a comprehensive exploration of individual concepts, enabling us to integrate insights from each approach while placing a strong emphasis on mindfulness and strategic decision-making.
Vax customer journey - A flow chart of how vax works
Prototyping concepts into wireframes
We started exploring problems and opportunities by prototyping each concepts showcased these wireframes to internal stakeholders and end users. As expected, Most users wanted a table dashboard over other exploration. However, they did
Vax customer journey - A flow chart of how vax works

Key takeaways from the above exploration

We gained valuable insights from each individual hypothesis, although there were also trade-offs to consider. The table-based approach received favorable feedback from most stakeholders and users. While search functionality was deemed important and necessary, it was not the primary action someone would perform every time they visited the site.
01
Table with defined columns that enables sorting options
02
Flexibility to rearrange columns and filters
03
Emphasis on scalability and space utilization
Prioritizing newly discovered Challenge

Users wanted a flexibility to rearrange columns according to their specific use case

Striking a balance between efforts and usability

We began by examining interaction design patterns employed by products with similar use cases, such as Monday.com, Asana, and ClickUp, among others. These products have evolved progressively over time, and their interactions have required significant developer input.

Collaborating with the Product Manager and developers, we assessed the intricacy of implementing column-level operations, which demanded substantial developer effort. I devised a sidebar that enables users to toggle columns and rearrange column items within a draggable window, introducing an entirely new interaction pattern that needed lower developer efforts and contributed to enhancing the end user's column customization experience.

Usability Testing findings

How well it was recieved and task completion rate

The ability to rearrange columns without having complex interaction was well-received by end users, developers and stakeholders. We conducted a usability testing with defined scenarios, where there was 94.3% success rate among users.
Crafting final designs
Incorporating feedback from end users, we meticulously crafted our ultimate visual designs, aimed at empowering users to concentrate on their tasks without being hindered by unexpected bottlenecks caused by human errors.
FINAL DESIGN

Outcome that I helped drive

01%
Increased productivity of database admins and application developers by improving workflow efficiency
02
Reduced the number of errors/escalations in database related workflow by 81.8%

Learnings

Balancing act of designing for two different user groups in internal teams
Leveraging principles of thoughtful execution tree through strategic prototyping