Automated Bulk Edits. Manage data-heavy processes with minimal effort.
Enterprise event teams were spending hours manually updating timeslots and ticket types. I designed a bulk-editing system that automated those updates, cutting operational time and saving clients hundreds of hours per month.
90% Time Saved
Compared to individual editing flows, going from what used to take hours on average to less than 5 minutes.
88% Accident Free
By optimizing against user error with intuitive error handling, automation, and clear auditing via changelog.
75% Adoption
Showing users trusted the bulk editing solution when committing more than 1 action.
Decreased Help Requests
Clients were more likely to commit their own changes than asking for help from Universe support teams.
Role
Lead Product Designer
Responsibility
Stakeholder management, design approach, leading usability testing, prototyping, and release.
Team
Product Manager
3 Frontend Developers
Skills
0-1 feature creation.
Designing with incomplete data.
Cross-team collaboration.
Problem
Clients were wasting time and risking potential revenue trying to action complex edits to their events.
They feared making mass changes perceived as irreversible, where one mistake can have a ripple effect on their event operations.
How could we create an intuitive, error preventative bulk editing feature that could promote autonomy with our clients?
what i owned
As this project had a quick turn around time, I prioritized testing iterations over extended discovery sessions.
I used Figma prototypes and leveraged my design team’s stand-up hours to conduct micro usability testing on major iterations. Whenever possible, I included my product manager and lead developer to ensure viability.
Research
Timeslot edits were the most tedious and error prone. They affected ticket visibility and price, and thus revenue.
Enterprise clients managing hundreds of timeslots and multiple ticket types needed a way to update price, quantity, and availability in bulk, but the system only allowed one‑by‑one edits, leading to frequent errors and bugs.
Organizers had to update every ticket and time slot one by one, turning large events into hours of error-prone manual work and creating operational strain, delays, and churn risk as event complexity grew.
DEcisions
An iterative release strategy.
In the end, we successfuly released bulk editing incrementally to validate performance, adoption, and usability in real time.
Launched a focused first version that enabled consistent edits across tickets and timeslots, then added change tracking for clear accountability, expanded bulk editing to handle complex ticket groups and multiple edit types in a single flow, and finally introduced scheduled edits so teams could automate updates during business hours.
Solution
Users could now action, automate, and audit changes across multiple tickets, groups and timeslots.
They could choose all of the values they wanted to edit in one flow, quickly understand what was changing, allow for automatic edits, and review past changes without workarounds.
TAKEAWAYS
Iterating with prototypes made alignment seamless, and is a powerful way to design with confidence under ambiguity.
I made intentional tradeoffs to accelerate design, using emerging tools like Figma Make to incorporate feedback in real time and shape decisions through to release. At the time, I thought designers had to always validate strategy with extensive discovery, but this project challenged that paradigm for me.
Next up
