Company / IBM
Role / Designer working with 2 other designers, a UX researcher, 3 product managers, a content developer, a visual designer and 3 squads of developers
Tools / Figma, Invision Freehand, Adobe Illustrator, UserTesting.com, Amplitude, Mural, Github, Slack, Box, WebEx
Timeline / 12 months
1. PRODUCT OVERVIEW
Users / Infrastructure Builders, Infrastructure Administrator and Cloud Engineers. These users utilise IBM RedHat Openshift (ROKS) to build, manage and upgrade their clusters within a managed service.
OBJECTIVE / As a product team, we wanted to create a seamless ROKS cluster provisioning experience in the GUI.
Competitive landscape / RedHat Openshift console, Azure RedHat Openshift, AWS ROSA.
Updated GUI experience allowing users to configure and provision desired Openshift clusters
2. DESIGN + UX REVIEW
methodology / Product was reviewed by six IBM Design and UX (D+UX) practitioners to review the product in areas of usability, content design, visual design and discoverability.
result / 56 D+UX issues opened.
TARGET / Close 80% of opened issues within 1 quarter.
ACTIONS / Worked individually and as a team to mock-up high-fidelity solutions in Figma for handover to Development teams. I worked with Visual designer to ensure consistency with Carbon Design System guidelines. I organised and led D+UX stand-ups call for March with wider team, Dev and PM to ensure we met 80% target by month end.
Outcomes / Team closed 89% of issues within one quarter. Working with Product management, I designed further improvements in areas such as networking, master service endpoints and error messaging updates.
Mid-fidelity Invision prototype used for testing
3. USABILITY TESTING
Needs / We tested updated experiences with 5 internal users that aligned with our personas.
Collaboration / I worked with a User Researcher on usability testing using UserTesting.com. We collaborated with Product Owners to utilise feedback to update the product roadmap.
ResultS /
1. Design and UX improvements implemented reduced the time to provision a cluster significantly and reduced the previously high error rate.
2. Usability testing identified a gap in current experience with user workflow. This created an opportunity to allow the integration of other IBM Cloud services within the cluster provisioning flow page.
Synthesis of research findings
4. FURTHER IMPROVEMENTS
opportunity / Users could not connect, create, enable or disable existing integrations without leaving the cluster provisioning page. Users would create other service instances separately and then link them to their cluster post provisioning. This could lead to issues when estimating cost of cluster and integrations.
proposed / Design a new component to allows users to enable and configure multiple integrations in one or two clicks. This would also allow users to get an improved estimated cluster cost inclusive of added integrations.
New instance created using toggle
Wide and narrow component (Disabled state)
5. COMPONENT DESIGN
SOLUTION / I designed a component with support from a Visual Design lead. The component allowed users to enable and configure multiple integrations within a cluster provisioning flow. We made the component flexible (wide and narrow) so other infrastructure teams could use it in their own 'Create' flow. Component styling aligned with Carbon Design system. When integrations are enabled, configurations and create functions are returned to the parent component via callback.
DETAILS /
1. Order summary reflects instance details
2. Existing platform instance is automatically found and connected
3. Existing instances can be found by user in dropdown
4. User can also choose to create a new instance through dropdown. User can edit details of this new instance in a side-panel.
2. Existing platform instance is automatically found and connected
3. Existing instances can be found by user in dropdown
4. User can also choose to create a new instance through dropdown. User can edit details of this new instance in a side-panel.
Details of new component within provisioning flow