ibm

Cloud transformation

IBM Cloud App Management | Project Winterfell | Released June 2018

dependency map hero

challenge

How might we help customers transition away from outdated monitoring software?

outcome

A monitoring platform that met current customer needs and guide them towards future technologies

role

Design Lead • scope, team process, design direction, and delivery

challenge

Information overload

The opportunity was clear: if we empower our customers throughout the upgrade process we could prepare them for future technology changes and reduce the fear that comes with such change.

[legacy] Our starting point, IBM’s Tivoli monitoring product many of our customers still use.

outcome

Infrastructure first

Through a collaborative process we delivered a cloud platform that addressed the primary needs for IT Operators (administration, thresholds and resource management) while motivating them to transition from on-premise to cloud native environments, one step at a time.

[information architecture] We needed to define the scope of the platform and establish the right navigation flow that would enable us to deliver for short-term but plan for the long-term. Research drove the organization and terminology of the final version.

[resources] Since our customer’s monitoring environments contain hundreds of resource types, we explored a hierarchical flow that provided performance data at each level—from groups to individual resources—guiding users to the right insight at the right time.

[getting started] Because the learning curve for the platform was broad enough, we delivered an onboarding experience—with kick ass illustrations—that guided our users to the required steps and showed the value of each configuration step before they began.

[prototypes] Creating thresholds was painful process for our users. So, the team iterated around a natural language approach maintained context throughout the configuration flow. Via quick prototypes, we also tested the comprehension of the nav and end-to-end flow.

resource main view

[infrastructure view] This consolidated design allowed our users to manage and organize their various resources at scale and pinpoint problematic areas that need their attention. Below, visual design for additional views of the platform.

Dashboard showing all infrastructure elements for the user
Empty state prompting the user to start creating thresholds for their Cloud elementsDetailed view of a timeline with alerts, issues, and problems that occured

[ux design] Lauren Goldstein // [ux engineering] Jamie Skinner // [visual design] Natalie Caudell // [research] Troy Bjerke

< previoustopnext >