cloudServe
My role
UX/UI designer
and researcher
Timeline
4 months, Shipped Q2, 2024
Team
UX/UI lead
Product manager
Architects
PROJECT OVERVIEW
CloudServe is a platform built to allow users to provision cloud infrastructure accounts; currently supporting AWS, Azure and eventually GCP.
Stakeholders identified a need for users to independently provision cloud account infrastructure. This would look like a centralized cloud account management tool to streamline access and cloud accounts/subscription management, reducing reliance on central IT teams, ensuring faster responses, and minimizing resource allocation bottlenecks. This urgency prompted swift project implementation.
01/
Who are we designing for?
understanding the users & research
We kicked off the discovery phase by conducting semi-structured user interviews that enabled us to explore each user’s unique goals, needs, pain points, and behaviors in detail. Alongside these interviews, we began conducting extensive cloud research.
Our interviews included four participants across three key user roles:
· Cloud Architect: Offered insights into high-level infrastructure needs and strategic planning.
· Engineering Lead: Shared perspectives on team management, workflow efficiencies, and technical requirements.
· Developers: Focused on day-to-day challenges, hands-on processes, and specific pain points within the development environment.
cloud research
We conducted in-depth research on AWS, Azure, GCP, Terraform, and ServiceNow to deepen our understanding of the technical features and workflows used across cloud environments. This research helped us to confirm user behavior patterns, pinpoint key pain points, and identify essential functionality across each platform.
.png)
personas
Using the information we gathered and analyzed from user interviews, we were able to construct 2 user personas. Our users were primarily data architects and software developers so their needs, pain points and behaviors varied.
The quotes included are authentic and sourced directly from real users we interviewed.
02/
Let’s help our users help themselves.
the problem
One of the most exasperating experiences is being unable to perform your job due to lack of information or while waiting for someone else's assistance. Our users were pained with that exact process when it came to getting access and working with the cloud resources they needed to do their job.
the main problem
As GM’s cloud transformation progressed, users faced challenges accessing cloud services (AWS, Azure, GCP) due to unclear processes and standards.
solution statement
cloudServe is...
A centralized GM tool that automates the cloud infrastructure and data request process by empowering users with a seamless experience and integrating them into the cloud community. A platform that provides resources and coding standards to follow so users know what selections to make when provisioning or managing their accounts.
Our aim with this new product was to...
Streamline the process of accessing data
Empower our technical users with self-service analytics
Consolidate resources for our users
Optimize the workflow for cloud management
03/
What will make this product great?
The features critical to ensuring this product’s success were determined alongside our stakeholders. Given the project’s urgency, we needed to have the following features for a minimum viable product.
Defining Features
Optimized Cloud Setup and Cost Management
A comprehensive setup form that simplifies the process of configuring cloud resources on AWS, Azure, or GCP, with a clear breakdown of estimated costs associated with each configuration. This form will present optimized default options for region, scale, etc, to avoid the higher costs associated with unnecessary scaling.
Monitor Status Of Accounts
Users will have access to their account name, a summary of their request, link to their cloud account, and receive informative error messages should their account creation fail.
Provide Access To Resources
Users have the ability to reach all resources that have been created, stored, or input into a configuration management database. This will allow users to make informed choices without over-provisioning resources.
04/
How'd we design with swift turnaround?
design process
Management knew what they wanted, let's use that
Validation checkpoints were critical throughout the process. Once we confirmed alignment, we created a site map to finalize the exact content and structure for each page.
Next was verifying the user flow for the tool. Each ux team member independently created their own version to capture multiple viewpoints. We reviewed our flows, identified any questions, and collaboratively developed a final user flow.
Close communication was key to receiving timely feedback that validated our initial designs. Regular check-ins kept stakeholders engaged and allowed us to confirm alignment early, enabling the team to confidently move forward with higher-fidelity versions.
05/
Several iterations later...
v1 designs
Given the green light on our assumptions and lo-fi mockups, we proceeded to refine the final versions of the designs.
CloudServe seamlessly complemented our recently developed data catalog, so we leveraged the existing design system with some modifications to infuse a distinctive touch into this product.
Screen: Homepage
View, create and manage existing cloud accounts/subscriptions. Resource section with links available to users who do not have enough information to begin.
.png)
Screen: Form
Upon clicking the cta button, users are prompted to complete this form. The UX team aimed to make this as straightforward as possible by asking users to provide only the necessary information required to create a cloud account that would be connected to their work at General Motors. This form includes default region selections, suggested configurations, and transparent cost visibility, allowing users to make informed choices without over-provisioning resources.
Screen: Success/Error Dialog
To prioritize communication with our users, when the form has been submitted, they will receive a dialog that notifies them of the status of the account creation. if the account has been successfully created they will then be able to open the existing account in AWS.
In the event of a failed account creation, users will receive an error notification along with contact information for assistance in resolving the issue.
06/
Meeting project expectations!
outcomes
Version 1 of cloudServe launched for an exclusive team in EDAI
07/
Next up
cloudServe v2
deployment archetypes
Allow users to browse and deploy a set of cloud resources with a predefined, deployment strategy, and template to their Maxis or Azure subscriptions. This would provide more help for first-time users working in the cloud. These archetypes would also help solve the user’s problem of not having access to certain data by presenting preapproved technical architecture diagrams (TADs) and flows.
Next Project
Maxis Workspaces
