Reimagining Enterprise Onboarding @ VBG
When enterprise customers bring existing devices onto a new wireless plan, they face flows originally shaped by single-device consumer assumptions: one identity, one device, one decision. Real business users have ten devices, multiple stakeholders, and hidden constraints the system never asks about.
Here is how we fixed a fragile enterprise onboarding flow by looking past the visual layer and rebuilding the system architecture from the ground up.
The Challenge: Where B2B Conversion Goes to Die
Multi-device B2B onboarding is notoriously difficult. The legacy system suffered from three core breakdowns:
Multi-Device Complexity: Simultaneous device entry with zero clear guidance caused massive drop-offs right at initial setup.
Cognitive Overload: All plan tiers were presented at once without any filtering by compatibility or user role.
Validation Error Loops: Manual entry of long alphanumeric strings without inline validation drove frustrated users straight to support.
The Approach: Modular Architecture
True enterprise design is rarely fixed by changing colors or tweaking typography. The architecture is the product.
We reframed the problem as structural, building a modular architecture based on three foundational rules:
Standardized: Components follow consistent patterns so users learn the system once and navigate effortlessly.
Self-Contained: Each module handles one single task end-to-end, ensuring no partial states cross boundaries.
Interchangeable: Modules can be reordered, reused, or swapped without rewriting underlying system logic.
Pro Tip: Where AI Actually Earns Its Keep
AI for its own sake adds zero value. AI earns its place only where the alternative is fundamentally broken.
Instead of forcing users to type error-prone alphanumeric strings under pressure manually, we introduced camera-based device identification to handle capture seamlessly. Furthermore, generic device labels dynamically updated to specific models the moment scanning completed, ensuring users never lost track of which device mapped to which line.
The Polish: Removing Friction Points
Beneath the structural architecture, we optimized four critical areas to protect working memory:
Spatial Control: Removed disorienting auto-scrolls that previously caused users to lose their place.
Visual Hierarchy: Standardized heading sizes, label weights, and body copy to meet strict WCAG AA accessibility minimums.
Design Systems: Replaced hardcoded styles with semantic tokens, unifying error, success, and warning states across every form module.
Interaction Flow: Added micro animations for module expand and collapse states, skeleton loaders, and inline success confirmations after each completed step.
Key Takeaways for Stakeholders
The architecture is the product: When a flow breaks down, the solution is rarely a surface-level redesign. It is about questioning the foundational assumptions the system makes about its users.
Senior design is mostly negotiation: The hardest work on this engagement wasn't drawing wireframes. It was aligning product, engineering, and business stakeholders around a structural overhaul when a superficial patch looked easier.