State Street Corp.
Dashboard design to streamline the application process
The current process for State Street developers to onboard the Cloud comprises of filling multiple application forms and sending them via emails for approval. The process is complex, confusing and inefficient.
To solve these problems, I designed a solution which consolidates and automates the application process.
Jun - Aug 2019
Concepting and Prototyping
Cameron Sanders - Developer
Daniel Morales - Developer
Mehrdad Darraji - Developer
Ritambhara Singh - Product Designer
My product owner was located in Boston and my team and I were in touch with her via video conferencing. She explained the current situation of onboarding tenants to the cloud and the challenges associated with it.
Images are blurred out intentionally for security reasons
The current process required the tenant to fill out four complex and long forms in different formats which were difficult to understand. The tenants had to use email to communicate with the Cloud team about each step in this process which was time-consuming and frustrating.
How might we enhance the application process for State Street employees to get access to private Cloud resources?
Since this problem space was very specific to State Street, I thought the best way to understand it would be to interview the direct end-users and then do desk research and comparative studies if relevant.
I conducted three remote interviews.
3 Remote Interviews
1 Cloud Team Member
Based on the information gathered from the interviews we created two personas:
Develops programs for a specific business unit at State Street and want to migrate it to the Cloud.
A streamlined and easy process to move his programs to the Cloud while keeping up with their busy schedule.
Jordin, Cloud Team Manager
Selects which program can be migrated to the Cloud from a pool of applications submitted by developers.
A consolidated platform to view all the applications at one place and keep track of them
After the synthesis of the data collected from the research, we decided on focussing on the following pain points of our users:
Lack of consistency
Lack of transparency
As a team, we started brainstorming for solutions to address those pain points. We sketched our ideas on a whiteboard to externalize our thoughts and build on top of each other's ideas.
We included the product owner in our early discussions also to narrow down on a concept shown below.
I started with low fidelity paper sketches as they are a quick and easy way to explore potential solutions, communicate ideas to the stakeholders and get feedback. It also helps me to get a better vision of the product and uncover dependencies.
Low Fidelity Sketches
1. Landing Page
There was no consolidated touchpoint for users to get information about the Cloud.
My focus while designing the Landing Page to address the business needs:
Communicating State Street Cloud's vision
Using modern design elements to resonate with Cloud Technology
Providing affordances encouraging the user to join the Cloud
3. Admin Portal
This view is for the admin who will be reviewing all the applications of tenants.
Comprehensive overview of different applications
Relevant insights about all the applications
Color coding to make it easier for the admin to differentiate between stages of application
2. User Application Portal
This flow is for the tenant who wants to onboard the cloud. Earlier he had to fill many complex and inconsistent forms.
My solution has:
Replaced long forms with easily digestible broken down forms
Provided adequate feedback to keep the user informed
Provided help and affordances in case the user is lost
The biggest takeaway from this experience was to learn how to work in a corporate setting while collaborating with people and delivering with hard deadlines.
I was responsible for end-to-end design while working with developers. There was a communication gap initially between us as my team members did not have experience with UX Design cycle. To mitigate this, I explained my process and thought process at every step to my team members. Understanding the rationale behind my actions helped us work in tandem as a team.
I was the only designer on two teams. I had to juggle between projects and attend twice as many team meetings. This experience taught me how to manage time well and stay on top of things.
My product owner and end-users were based in Boston. Staying in touch with them remotely was a part of the challenge. However, constantly updating each other on the team and collaborating closely helped me stay on track.