WorkUnifyUXR
I noticed an Excel bottleneck, so I built the tool that removed it.
Our researchers merged UserZoom exports by hand, again and again, and it took hours or days. I turned the normalization and weighting rules into one upload-and-results workflow, built it in Angular, and deployed it. It's still in regular use.
| taskTask Name | success %Task Success (%) |
|---|---|
| T1 Find a testFind a test | 78.078 |
| T2 Order suppliesOrder supplies | 64.064 |
| T3 View resultsView results | 88.088 |
| tasktask_id | success %success_rate |
|---|---|
| T1 Find a testT1_find_test | 61.00.61 |
| T2 Order suppliesT2_order | 50.00.50 |
| T3 View resultsT3_results | 83.00.83 |
| taskTask | success %Completed |
|---|---|
| T1 Find a testTask 1 | 70.021/30 |
| T2 Order suppliesTask 2 | 60.018/30 |
| T3 View resultsTask 3 | 90.027/30 |
Three exports, three dialects.
Each study came out of UserZoom with its own column names, its own scale, and its own names for the same tasks. Before UnifyUXR, a researcher reconciled them by hand in Excel, every time:
- Paste each export into a master workbook
- Rename columns so they match
- Convert 0–1 decimals and x/n counts into percentages
- Work out that “Task 1” and “Find a test” are the same task
- Weight each study by its participant count
- Re-check every formula before sharing
- The hard part
- Every export used its own column names and scales. The weighting rules lived in people's heads and their spreadsheets.
- The decision
- Don't build a dashboard. Build a standard upload-and-results flow: one clear input and one result you can trust.
- Where it stands
- It's deployed through Docker, Kubernetes and Jenkins, and researchers still use it regularly.
The recurring cost
Every study ended the same way: raw UserZoom exports in different formats, and a researcher rebuilding the same weighted analysis by hand in Excel. It took hours, sometimes days, every time.
The design move
I mapped the real workflow first: upload, normalize, combine, weight, read the result. The interface follows that pipeline directly, so the tool explains its own process. Designing and building it myself meant nothing got lost between the design and the code.
How it runs
Angular on the front end, containerized with Docker, orchestrated on Kubernetes and delivered through Jenkins CI/CD. It's internal software held to production discipline.
What changed
Recurring analysis that took hours or days now takes seconds. Five UX researchers and additional designers use it, and it's still in regular use.