2021 to 2023
Designing multi-service cloud solutions
I led the design of pre-built architectures that made deploying 20 to 30 integrated cloud services feel like choosing a template.
- Role
- Lead Product Designer
- Team
- 11 designers across 2 initiatives
- Duration
- 25 months
- Scope
- Catalog to automated onboarding
- 30 minTime to deploy
- Down from 2 to 3 weeks
- 78%Architecture adoption
- Up from 15%
- $2.4MNew platform revenue
- Annual recurring revenue from zero
- 47Certified architectures
- Across 8 industries
Make many services feel like one decision
- Problem
- Production cloud architectures required 20 to 30 services, deep Terraform knowledge, and 2 to 3 weeks of manual integration.
- My decision
- I led a dual-presentation system that showed the same architecture as a visual diagram for directors and as Terraform for cloud architects.
- Tradeoff
- Neither the diagram nor the code was enough on its own. Keeping both views connected added design work, but it let technical and business teams make the same decision together.
- Shipped result
- We made certified architectures deployable from the IBM Cloud catalog in 30 minutes.
Show the full decision before deployment
One architecture
A single catalog record brought the services, configuration, and deployment path together.
Cost and compliance before deployment
Teams could review the resource mix, estimated cost, and compliance requirements before they committed.
One view for architects and directors
The diagram was generated from the Terraform that would ship, so technical and business reviews stayed connected.
Design for how teams evaluate solutions
Research showed that people needed to compare the architecture, cost, and business fit before they could move forward.
