Device Provisioning Tool Editor Redesign

Device Provisioning Tool Editor Redesign

Device Provisioning Tool Editor Redesign

Faster fleet edits with feature parity at enterprise scale.

Faster fleet edits with feature parity at enterprise scale.

Image of Device Provisioning Tool dashboard.
Image of Device Provisioning Tool dashboard.
Image of Device Provisioning Tool dashboard.

Summary

Summary

Led the end-to-end redesign of a mission-critical provisioning tool during its transition from desktop to cloud. The new editor transformed multi-step workflows into a streamlined experience that made large-scale fleet updates faster and easier while preserving power-user depth. Shipped on schedule with the cloud release and included in a FedRAMP-authorized rollout used by U.S. federal agencies.

At a Glance

At a Glance

Role: Senior UX Designer (project lead for editor redesign)

Users: System administrators and provisioning specialists managing large device fleets

Problem: Increasing configuration complexity required a faster, more scalable editing model to support enterprise-scale fleet management.

Solution: A streamlined, cloud-based editor that simplified complex workflows while maintaining expert-level control

Key Features: Guided editing flow; improved sequencing; validation clarity; explicit review step; consistent labeling and grouping

My Contributions: Discovery, stakeholder workshops, IA and flows, 150+ screen high-fidelity prototype, daily collaboration with PM and engineering, and direction of a UX researcher and intern

Tools: Figma, FigJam, company design system, Google Workspace

Outcomes: Significantly faster edits; on-time delivery with the cloud release; part of a FedRAMP-authorized rollout; prototype adopted as the single source of truth for engineering and product alignment

The Opportunity

The Opportunity

As a major device-provisioning tool transitioned from a desktop client to a cloud-native web app, the move presented a chance to modernize key workflows. System testing and stakeholder feedback highlighted opportunities to make frequent configuration updates more direct and efficient while maintaining the flexibility power users relied on.

With a fixed release deadline, I led a focused redesign to deliver those improvements without sacrificing capability or parity with the legacy tool.

My Role: Lead Designer & Strategic Partner

My Role: Lead Designer & Strategic Partner

  • Owned the end-to-end redesign of the editing experience on an accelerated timeline.

  • Ran a multi-day whiteboarding workshop at headquarters with engineering and architecture to align constraints, tradeoffs, and success criteria.

  • Proposed and secured budget; hired and onboarded a UX researcher and a UX design intern to increase velocity.

  • Led research synthesis, user stories, flows, wireframes, and a 150+ screen high-fidelity prototype. I designed every screen, pattern, and state; interns helped stitch it into a complete click-through for daily reviews with product and engineering.

The Problems We Solved

The Problems We Solved

  • High effort in frequent tasks – Routine updates involved many sequential steps that added time and cognitive load.

  • Repeated input – Some details appeared across multiple steps, increasing the effort required for large-scale changes.

  • Limited feedback clarity – Administrators wanted clearer cues on whether their inputs were valid and ready to apply.

  • Navigational depth – Within multi-layer configurations, it was difficult to maintain orientation or see progress through the workflow.

Our Solution: Configuration Profiles

Our Solution: Configuration Profiles

Introduced a reusable configuration approach that reduced repetition and simplified complex updates at scale. This eliminated rebuild-from-scratch work and made complex updates manageable without taking power away from expert admins.

  • Clear sequencing - Condensed and reordered steps to remove unnecessary back-and-forth.

  • Review before apply - An explicit confirmation shows exactly what will change across the fleet prior to sending.

Result: the editor remained as powerful as the legacy tool, but became far faster, easier to follow, and scalable for large deployments.

Research & Validation

Research & Validation

  • QA teardown with the team to catalogue redundant steps and dead ends.

  • Focused customer reviews on the editor concept to verify it solved repeated-configuration pain.

  • Cross-functional sign-off on scope and readiness to build - on time and on budget.

  • Interactive prototype reviews (150+ screens) with product and engineering to exercise edge cases and confirm end-to-end coverage before build.

  • Internal UX critique (heuristic pass) to tighten labeling, grouping, and affordances across the editor.

Results & Impact

Results & Impact

  • Edit speed – Long, multi-screen sessions collapsed into a short, guided flow that completes in minutes.

  • On-time delivery – Shipped with the cloud release and included in a FedRAMP®-authorized rollout, enabling U.S. federal agencies to deploy and program fleets more efficiently.

  • Shared alignment – The 150+ screen prototype served as the shared artifact for engineering and PMs throughout build, reducing ambiguity and rework.

What Stakeholders Said

What Stakeholders Said

“His prototype and walkthrough gave us the exact feedback we needed. Engineering keeps praising the clarity it provided.”
- Director of Software Engineering

“Joe jumped in during crunch time, led daily design sessions, and delivered a [new editor model] the business approved on first pass.”
- Senior Product Owner

Reflections

Reflections

  • Solve end-to-end - Mapping the journey surfaced the exact steps to remove without sacrificing capability.

  • Hire for leverage - A small, high-trust UX strike team multiplied throughput when timelines were tight.

  • Prototype to align - A realistic, clickable prototype collapsed debate, exposed edge cases early, and accelerated decisions.

  • Design under constraints - Even with thousands of variables, a clear editor model can make complex work feel simple, exactly what mission-critical environments require.

Authenticity & Confidentiality
This case study reflects real design work. Certain labels, visuals, and data are anonymized, generalized, or reconstructed from public references. No non-public, confidential, or proprietary information, nor any third-party proprietary information, is disclosed.

© 2025 by Joe Balich — All Rights Reserved

© 2025 by Joe Balich — All Rights Reserved

© 2025 by Joe Balich — All Rights Reserved