Corellium

Device creation is the most critical flow in the platform. It's how every user starts their work. If this flow is painful, the entire product feels painful.

I first identified the friction through patterns in Intercom survey responses, then mapped the existing flow to make it tangible for the product team. The existing experience required a minimum of 6 steps, and no changes were saved between steps. Going back to change something as simple as which project a device belonged to would revert all your selections, adding up to 6 more steps. That's 12 steps worst case for a flow every single user hits. Unclear decision points, redundant inputs, and a structure that punished users for changing their mind.

I advocated for this redesign for over a year. It was consistently deprioritized because the roadmap favored feature additions that kept us ahead of competitors and that existing customers were actively requesting. Foundational UX work rarely has a customer asking for it by name. The opportunity came when a PM's roadmap had capacity and I could demonstrate how the fix would solve pain points for his user segment. I presented first to him and the head of front-end engineering, then shared it with the wider product team. Timing and alignment mattered as much as the solution.

The goal was to reduce cognitive load and eliminate unnecessary steps without sacrificing flexibility. I redesigned the flow down to 3 steps. In the new design, one click gives you the latest iOS, Android, or IoT device with smart defaults. Power users can still customize everything, but the common path is fast. Changing your mind no longer punishes you with extra steps: device type, OS version, project, and advanced options can all be adjusted without starting over.

A flow that took up to 3 minutes drops to an estimated 10 to 30 seconds depending on complexity. I designed the system to be modular, handling complex IoT devices with unique configuration requirements just as easily as standard iOS or Android setups. Future device types can be added without rearchitecting the experience, whether for new use cases or entirely new revenue lines.

The redesign is fully designed and approved, but a major internal shift reprioritized the roadmap before it reached engineering, and it's currently queued for implementation. That outcome reinforced the lesson at the heart of this project: in enterprise B2B, foundational UX work has to be re-sold as priorities change, not just sold once.

In B2B enterprise, customer requests translate directly to revenue, which means platform-wide UX improvements often lose the prioritization battle. Find the intersection between what users need and what a PM can justify on their roadmap to get foundational work prioritized.

Beyond this project, I partnered with the head of front-end engineering to lead the WCAG accessibility initiative that unblocked enterprise sales. He handled engineering, I handled design, and together we aligned the entire design system. I also standardized the product design process across 3 PMs, 2 POs, and their teams, replacing one constantly out-of-sync file with a system that kept design specs current for specific tickets and bodies of work.