Cisco Cloud Control
Nexus Hyperfabric
A SaaS network controller for designing, provisioning, and operating large-scale fabrics. I own product-level UX: what the experience is, where capabilities live, and how the product stays coherent as it grows.
The problem
Network operators need to design a fabric, order it, bring it online, and keep it healthy. The work is dense: devices, routing, ports, cabling, software, and failure states. If the product is only a pile of features, they lose the plot as deployments get larger.
What I did
- Set UX direction for net-new capabilities—including IP SLA, static routing, topology at scale, Fabric Designer, and operations views—from problem framing through shipped software.
- Ran a product-wide heuristic audit (Fabric Designer, provisioning, onboarding, routing) and turned it into a redesign roadmap: import/clone, candidate review, empty states, and shared details-panel patterns.
- Designed for operational scale: topology lens views, device health, cabling at volume, bulk port configuration, and async configuration.
- Encoded Magnetic and Cloud Control guidance as reusable prototypes, review skills, and agent workflows so quality does not depend on one-off reviews.
Selected workflows
The product is not one screen. Operators move from topology to utilization, security, and diagnostics—often under time pressure, often across hundreds of devices.
Outcome
Hyperfabric now has a clearer quality baseline and a shared language for how new capabilities show up in the product. Operators can move from design to operations without the interface falling apart as fabrics get larger.
Selected screens. Some product details omitted.