New UX Quality Method
Managment Ops
Role: Head of UX
2023-2034
Overview
During this time, Wix prioritized raising overall product quality—across performance, SEO, accessibility, and UX. To support this effort, the UX Guild introduced a quarterly “UX Quality Blitz” (1–3 days) focused on tackling usability issues. Each group was encouraged to embed the initiative within its development teams and address quality gaps directly in their own products.
The Blitz marathon was very successful and fun and allowed UXers to be creative and create themed days such as the Harry Potter Blitz, Mexican Blitz, etc.
Sweets for the OS Blitz (my group)
The Challange
Early on, identifying small yet impactful tasks was challenging for teams like ours that provide broad, platform-level solutions. The complexity was often underestimated, and cross-team dependencies created unexpected friction—leading to frustration instead of the sense of pride and progress we aimed for.
For example, the modal fix shown below ended up taking two months of development and required coordination across three different teams within Wix.
Before: The Business manager editor modal. No modal controls are available for our users while loading⤴
_gif.gif)
After: The Business manager editor modal with controls⤴
The Approach
Following a failed blitz—where a seemingly simple modal improvement ended up taking two months—our research revealed the need for better stakeholder alignment and more realistic scoping.
In response, I chose to return to our classic product methodology and adapt it to fit seamlessly into the day-to-day routines of the development teams.
_gif.gif)
Step 1
Create a Quality Backlog
Step 2
Prioritize Issues
Step 3
Prepare Necessary Resources
Step 4
Organize a Dedicated Quality Epic in Jira
Step 5
Engage Developers in a New Way
Step 6
Celebrate Small Wins
Key Insights
-
The blitz-style sprints fell short for platform products groups—lacking stakeholder input and proper lead time planning, “Small” UX fixes often had hidden complexity and dependencies across teams.
-
We realized that even minor improvements require a structured approach, one that integrates quality tasks into the daily workflow. The real shift came from instilling a quality-first mindset within the everyday culture of our development teams.
The Results
Pivoting to a sustainable “New OS Quality Methodology” involving:
-
A shared quality backlog with multidisciplinary contributions.
-
Quarterly prioritization sessions in each product squad.
-
Pre-allocated resources (assets, BI setup, content).
-
Quality improvements tracked via Jira Epics, completed by developers during slack periods or onboarding.
-
Regular celebrations of small wins to boost morale stavstein.com.
Outcome: 32 quality tasks completed in 3 months, measurable UX gains (e.g., a 2% drop in support calls), and an adaptable, collaborative process .
Here are a few examples of high-quality tasks that were successfully resolved using the new methodology:
Before: Users could navigate between recently opened sites.
After: Users can now search for the site they want to navigate to.
