Apstra Blueprints
From Spreadsheets to Guided Network Design
Designing the 'new network' workflow — how you take a blank data center and define a fully-validated fabric before a single cable is plugged in.
Principal Product Designer (sole designer)
Blueprint creation, rack/device design, cabling topology, Day 0 intent capture
Apstra → Juniper Networks → HPE
90% faster
Deployment speed
Self-serve
Onboarding
$450M
Acquisition
The Problem
No single source of truth
Before Apstra, designing a data center network was a manual, fragmented process. Network architects used spreadsheets, Visio diagrams, vendor-specific CLI documentation, and informal tribal knowledge to plan a fabric.
No single source of truth existed between design intent and deployed state. The process of capturing a new fabric design required intimate knowledge of Apstra's data model. Onboarding a new customer meant a multi-day engagement with professional services just to create a first Blueprint.
Design Approach
Structured build order
The biggest early problem was that all configuration options had equal visual weight. I restructured the Blueprint creation flow around a natural build order: define device types, assemble rack types, define the fabric topology, assign real hardware, preview and commit.
Each step unlocked the next, removing decision paralysis and making the right path obvious without hiding advanced options. Topology templates cut Day 0 setup from hours to minutes for standard deployments.
- Color-coded state indicators: Staged (amber) / Active (green) / Anomalous (red)
- Rack canvas with drag-to-assign device placement
- Blueprint diff viewer showing exactly what will change before commit
- Inline validation at every step, not just at commit time
The Mental Model
Staged vs. Active
One of the most important UX decisions: making the Staged/Active state duality explicit and always visible. Staged equals what you intend. Active equals what's deployed. The UI always shows which context you're in, preventing engineers from accidentally making live changes when they think they're in design mode.
This pattern became foundational across the entire product.
Outcomes
90% faster deployment
Day 0 deployment time reduced by up to 90% for standard topologies using templates. Onboarding new customers no longer required professional services for initial Blueprint creation.
The Staged/Active model became a foundational UX pattern used across the entire product. Blueprint architecture contributed directly to the 'single source of truth' positioning that Juniper cited in the acquisition.
Reflection
The Blueprints work taught me that workflow design for experts requires a different kind of progressive disclosure — not 'hide complexity from beginners' but 'sequence complexity so experts can move fast without making preventable mistakes.' The difference sounds subtle. It changes everything about the information architecture.