Streamlining the journey to public cloud

Streamlining the journey to public cloud

JPMorganChase - September 2024 to February 2026

JPMorganChase - September 2024 to February 2026

Streamlining the journey to public cloud

JPMorganChase - June 2025

JPMorganChase - June 2025

Migrating applications from private to public cloud is complex.

Migrating applications from private to public cloud is complex.

Migrating applications from private to public cloud is complex.

JPMorganChase has a proprietary platform it has used since 2018 to connect developers to AWS, manage accounts and run applications.


With the second iteration of this platform, self-service cloud infrastructure provisioning and greater architectural ownership addressed many technical pain points, but user experience challenges remained. Frequent context switching, slow approvals and limited visibility into deployment progress continued to frustrate engineers.


UX was brought in to help cloud architects, application owners and development teams onboard to the cloud platform, streamlining their journey and providing contextual support to drive applications to production.

My role

My role

My role

I was the lead UX designer, on a team of 4 UX designers, embedded within a cross-functional team of 30 developers, working closely with product and design leadership.

Beyond design, I took an active leadership role across the full project lifecycle — moderating usability testing sessions, contributing to the user testing guide and interview discussion guides, and iterating rapidly on designs as consensus emerged from research.

I collaborated directly with engineering to write design specs, and worked with product and design leadership to prioritise which improvements would have the most impact within our tight delivery window.

Timeline

Timeline

Timeline

Lorem ipsum

Methodology

Lorem ipsum

Solutions

Solutions

Solutions

Defining service blueprints

Defining service blueprints

Defining service blueprints

Lorem ipsum

Outcomes

Lorem ipsum

Switching terminology to match user mental models

Switching terminology to match user mental models

Switching terminology to match user mental models

Lorem ipsum

Outcomes

Lorem ipsum

Landing first-time users in a more meaningful location

Landing first-time users in a more meaningful location

Landing first-time users in a more meaningful location

Lorem ipsum

Outcomes

Lorem ipsum

Tradeoffs

Tradeoffs

Tradeoffs

Lorem ipsum

Results

Results

Results

Journeys that reduced cognitive load, dramatically cutting the number of tools engineers needed to create cloud infrastructure and onboard to mandatory resiliency tooling. To use an example from Cloud Chaos Resiliency onboarding, optimized journeys highlighted the following improvements:

8 -> 1

Separate products touched

3 -> 1

Separate developer requests

3 -> 1

Separate approvals needed

Designs which gave engineers flexibility in how and where they initiated cloud onboarding activities.

Lessons learned

Lessons learned

Lessons learned

Map assumptions, investigate, then organize around opportunities.

Map assumptions, investigate, then organize around opportunities.

Map assumptions, investigate, then organize around opportunities.

Lorem ipsum

It's possible to expose complexity without causing overwhelm.

It's possible to expose complexity without causing overwhelm.

It's possible to expose complexity without causing overwhelm.

Lorem ipsum

Observe support teams to learn about your customers.

Observe support teams to learn about your customers.

Observe support teams to learn about your customers.

Lorem ipsum

UX can prove its value by capturing metrics on simplified journeys.

UX can prove its value by capturing metrics on simplified journeys.

UX can prove its value by capturing metrics on simplified journeys.

Lorem ipsum

© 2026 Max McVeigh