PMM DBaaS Platform
Redefining Open-Source Database Management with Percona's DBaaS Solution
I had the unique opportunity to spearhead a team focused on redefining open-source database management. Our mission was to launch Percona's groundbreaking Database as a Service (DBaaS) solution. This case study delves into the intricate process, the challenges we overcame, and the triumphant outcomes.
The database management landscape is fraught with complexities, often requiring specialized knowledge and extensive time investment. Our challenge was to simplify this process, making it accessible and efficient for IT organizations, database professionals, and DevOps teams.
Research and Planning: Jobs to Be Done (JTBD)
JTBD Interviews
To kick off our research, we conducted JTBD interviews focusing on four key areas:
Functional Jobs: Understanding the primary tasks users aim to accomplish.
Pain Points and Obstacles: Identifying challenges and frustrations.
Context and Triggers: Recognizing the events or situations that prompt users to seek a DBaaS solution.
Emotional and Social Jobs: Understanding the emotional and social factors that influence users' decisions.
Stakeholder Interviews
We also conducted interviews with internal stakeholders, including the CEO, Database Admins, Developers, and Product Managers, to gather insights on customer complaints, platform failures, market demands, and competitor insights.
Data Analysis
After several rounds of interviews and data collection, we held a crunch session to aggregate all the findings. We categorized the topics and identified key problems that were not being addressed by existing solutions.
Design Principles
Based on our JTBD research and interviews, we formulated three core design principles:
Simplicity: Easy navigation
Efficiency: Quick task completion
Scalability: Adaptability to various user needs and database complexities
Design Sprint
I led a week-long design sprint that included various stakeholders. We used the insights from the JTBD research to inform our design decisions. The sprint was a collaborative effort involving the CEO, Database Admins, Developers, and Product Managers.
Initial Hallway Testing
After creating our initial prototypes, we conducted hallway testing within the organization. The feedback revealed some usability issues, which we iteratively improved upon.
Final Customer Testing
We conducted remote user testing sessions with two of our biggest clients. The results were promising; users were able to complete the tasks we proposed, validating our design decisions.
Final Design and Launch The final design was a collective effort, especially given the cross-functional nature of the team. Upon launch, the redefined DBaaS solution was well-received, meeting the project's initial goals and user needs.
Outcomes and Reflection
The project was not without its challenges, but through iterative testing and customer validation, we were able to deliver a product that met and exceeded user expectations. As the lead designer, this project stands as a career milestone, contributing not just to the company but also to the broader fields of database management and beyond.
