All work

Case study

Server activation

Making one of the hardest steps for a systems engineer, first-time setup and management, simpler and more reliable.

Role
Design lead
Product
Compute Ops Management + iLO
Partners
Solution architects, partners, engineering, PM
Outcome
50% faster activation
Server activation welcome screen in the iLO interface

Intentional listening

Setting up a server for the first time and turning on management is one of the most technically complex jobs a systems engineer faces. Our challenge was to make it simpler and take less effort while keeping confidence that onboarding would succeed.

I led early sessions with customers to understand their workflows and needs in detail. I then brought in solution architects, partners, engineering and product management to develop the proposed experiences, and worked with executive leadership to keep them aligned with business goals.

Flowchart of the server activation workflow
Mapping the end-to-end activation flow
Workshop notes and sticky-note clusters
Synthesis from customer sessions

Building a design strategy

I led several workshops with a global group of stakeholders, including pre-sales, solution architects and product management, where we tested onboarding workflows for first-time server setup.

The sessions reinforced the value of user-centered product development. I combined customer insights, stakeholder feedback and executive guidance into a prototype for testing.

Workshop board for discovery and configuration experiences with sticky notes
Workshop boards: discovery and configuration/activation
iLO screen with a dialog to connect to Compute Ops Management
iLO screen with an activation key dialog
Compute Ops Management overview with an activation dialog

Complex challenges

One of the team's biggest challenges was simplifying how two management systems connect: a legacy system that lives on the server hardware, and HPE's cloud service for server management and monitoring. Connecting them raised security concerns, conflicting workflow practices and strongly held executive directives, which made it hard to agree on product direction.

I started a collaboration with the HPE human factors lab to test the proposed direction, which challenged one of the executive requirements. Despite the study's results, that requirement stayed.

Where I could make a difference was simplifying the whole activation workflow. Working with two UX and engineering teams, we cut activation time by 50% and delivered APIs customers can use to script activation and onboard at larger scale.

50%less time to activate a server
APIsso customers can script activation jobs and onboard at scale
2 teamsof UX and engineering aligned on one workflow
Server management welcome screen
Compute Ops Management connection settings in iLO

Contact

Have a complex system that needs to feel simple?

I'm glad to talk about product design leadership roles, infrastructure and developer-facing products, or design strategy work.