Designing a Guided Execution Wizard for a Distributed QA Platform
Overview
This case study focuses on designing a guided execution flow for a distributed QA platform used to manage automated and semi-automated testing operations.
The original execution setup flow was heavily implementation-driven. Multiple tabs, fragmented forms, and inconsistent configuration logic made the experience difficult to understand — especially for new users.
My goal was not to simplify the system itself, but to redesign how users move through complexity.
The final solution became a structured multi-step wizard called Start Execution, focused on clarity, progressive disclosure, and reducing cognitive overload during execution setup.
Interactive Prototype
The prototype below presents the complete Start Execution flow, including setup, workflow selection, device configuration, execution types, advanced settings, and final review.
Context
The execution flow was part of a much larger enterprise QA ecosystem used to manage testing operations across multiple projects, workflows, devices, and execution types.
The system supported:
- reusable execution templates,
- distributed device allocation,
- configurable workflows,
- execution monitoring,
- multiple execution strategies,
- shared configuration management.
Because of this complexity, execution setup became one of the most critical interaction points in the entire platform.
The Problem
The original flow exposed system architecture instead of supporting user decision-making.
Users had to:
- navigate disconnected configuration layers,
- understand technical dependencies,
- remember relationships between selections,
- manually track setup progress,
- switch context between unrelated settings.
The experience was especially difficult for:
- new team members,
- occasional users,
- cross-functional QA roles,
- users unfamiliar with platform logic.
At the same time, the system itself could not be oversimplified because advanced configuration was still necessary for complex testing scenarios.
The challenge was not reducing functionality.
The challenge was making complexity understandable.
Design Goals
The redesign focused on five major goals.
1. Reduce cognitive overload
Instead of exposing all configuration layers simultaneously, the flow guides users step by step.
2. Improve learnability
Users learn the system progressively through interaction rather than documentation-heavy onboarding.
3. Preserve advanced functionality
Advanced configuration remains available without overwhelming less experienced users.
4. Create predictable navigation
Users can move freely between steps while maintaining clear awareness of progress and structure.
5. Increase execution confidence
The final review screen provides a structured summary before execution starts.
Solution
The final solution introduced a dedicated multi-step execution wizard with a persistent sidebar stepper and contextual configuration views.
The flow included:
- Execution setup
- Project & Release
- Workflows
- Devices
- Execution type
- Configuration
- Advanced
- Review
Each step focused on a single decision layer.
Instead of asking users to understand the entire system at once, the interface progressively revealed only relevant information.
Execution Setup
The first step introduced reusable execution templates.
Users could:
- select previously saved templates,
- upload external configuration files,
- skip templates entirely and configure everything manually.
This was an important design decision because the platform could not safely assume that predefined templates were always correct or contextually appropriate.
The system intentionally supported decision-making instead of automating critical setup choices blindly.
Contextual Configuration
One of the key UX decisions was making configuration adaptive to user choices.
For example:
- selecting Localization and Performance dynamically changed visible configuration sections,
- irrelevant settings were hidden entirely,
- advanced configuration remained optional.
This significantly reduced visual noise while preserving flexibility for experienced users.
Instead of exposing every possible option simultaneously, the system responded to user intent progressively.
Stepper Navigation
The vertical sidebar stepper became one of the most important structural elements of the flow.
It allowed users to:
- understand overall progress,
- navigate between steps,
- maintain orientation inside the wizard,
- track completed configuration stages.
Unlike horizontal steppers commonly used in smaller forms, the vertical layout scaled better for longer enterprise workflows inside modal-based interfaces.
Validation Strategy
The flow intentionally avoided large error states and aggressive validation patterns.
Instead:
- validation happened continuously,
- incomplete steps naturally blocked progression,
- users never encountered overwhelming error summaries at the end of the flow.
This reduced friction and created a more stable setup experience.
Review Experience
The Review step acted as a structured execution summary rather than an editable form.
Users could verify:
- workflows,
- devices,
- execution types,
- configuration settings,
- advanced options.
Instead of introducing another confirmation modal, optional actions such as:
- saving templates,
- exporting configuration files
- were integrated directly into unused layout space inside the Review screen.
This reduced unnecessary interruption before execution launch.
Execution Feedback
After starting execution:
- the wizard closes automatically,
- the user receives a lightweight toast notification,
- execution progress becomes available in the Executions section.
This helped preserve flow continuity without forcing users into additional confirmation screens.
Outcome
The redesigned flow transformed a fragmented implementation-driven process into a guided execution experience focused on clarity, confidence, and progressive learning.
The final wizard:
- reduced setup complexity,
- improved navigation clarity,
- preserved advanced system capabilities,
- supported both new and experienced users,
- created a scalable foundation for future execution workflows.
Design Reflection
One of the most important lessons from this project was understanding that enterprise UX is rarely about removing complexity.
In many systems, complexity is unavoidable.
The real challenge is designing interfaces that help users move through complexity without becoming overwhelmed by it.
Context
This project is part of a larger distributed QA platform redesign exploring enterprise workflows, onboarding systems, dashboards, execution management, and testing operations.
© Zofia Szuca 2024
Brand and product designer