Brief

Jazz manages the deployment and upkeep of server-less applications built within the T-Mobile Ecosystem. It's a simple yet powerful platform where developers can select from preconceived templates designed to jumpstart the deployment process while guiding developers around best practices.

The Problem

Developers needed more guidance on best practices for service creation. Before the sever-less marketplace developers who wanted to utilize sever-less deployment in their projects found it frustrating to debug known limitations, between platforms, plug-ins and coding languages.

‍Process

I coordinated a team of designers and developers across time zones to take this project from strategy to deployment. Working with a team in India posed some time challenges and long nights.

We began by identifying the opportunity in the form of "How Might We' questions. We also jumped into a comprehensive analysis of other platforms.

We defined two main user groups, T-Mobile Developers and application managers, both with specific needs within the application. ‍

‍Outcome - What does success look like?

Because this is a relatively new project the data aren't in yet... So in the meantime I've set up a structure to know what we should look for.
‍
At least 30% of newly created applications should be made from templates
‍
A reduction of 50% month over month, in questions to Jazz management in the form of slack messages, emails and help requests.

A 50% increase in successful deployments on the first attempt

‍

Solution

To land at a seamless solution we mapped the journey of a typical service creation.

We found these key insights which resulted in our high fidelity design