top of page
EDA 3 1.png

Web based event platform

My role

Lead UX designer

UI designer

Stakeholder Manager

Responsibilities

Solution designer

Collaboration with BAs

Designing user flows

Prototyping & UX reviews

Framing the UX strategy

Testing and iterative design

Project duration

9 month

Goal of project

A strategic redesign of an outdated event management platform used by both internal administrators and external participants. The new solution aimed to:

  • Streamline internal workflows for event administrators,

  • Modernize the participant registration experience,

  • Deliver a maintainable and scalable system that replaces the legacy tool.

Problem & Context

The existing platform was working for last 20 years, it was outdated with the goal of functionality. Since the support of product was stopped several years before the end of product life-cycle, the current state of the product did not meet the user's expectation, anymore. Therefore, stakeholders prioritized a secure, scalable, and future-ready solution. The goal of the project is to design a desktop-first platform that enables staff to manage events efficiently and empowers participants to register with clarity and confidence. This created the need for a user-centered design approach to:

  • Align business and technical requirements,

  • Deliver intuitive workflows,

  • Respect regulatory constraints.

Research & Understanding

Given the limited direct access to end users, I adapted the research strategy to rely on indirect insights and close collaboration with SMEs and expert stakeholders:

Stakeholder Interviews

I conducted sessions with:

  • Subject matter expert from client (SME),

  • Project manager and product owner.

These conversations uncovered the main pain points of the current system and clarified internal expectations for the redesign.

Process & Workflow Analysis

  • Identified steps that were redundant or confusing.

  • Prioritized improvements based on frequency of use and scope of MVP/post-MVP (e.g., registration confirmation and event publishing).

Requirement Translation

I collaborated with RE to translate business rules into UX requirements, identifying:

  • Role-based access needs,

  • Conditional flows based on event access types,

  • Data security modal, mapped with user access (user and role management).

Design Strategy & Decisions

The design approach was set in efficiency, and scalability, finding the thin line between user needs with technical feasibility.

Strategic Focus Areas

Based on research insights, I prioritized three experience pillars:

  1. Simplify event creation workflows with clear steps that ensures learnability and self-explanatory of product.

  2. Confidence for participants – Provide clear, feedback-driven registration flows with appealing visual hierarchy.

Designing for Privacy & Role Separation

  • Created role-specific interfaces: Admins, Event managers, and External Users.

  • Ensured no user data was ever exposed in public views.

Iterative Reviews in Place of Testing

Due to lack of direct access to end users, traditional usability testing wasn’t possible. Instead:

  • I conducted weekly design reviews with RE and developers to simulate edge cases.

  • Worked closely with developers to ensure feasibility and fidelity through UX check-ins at key milestones.

Key Features

The platform was designed as a desktop-first application with a focus on administrative efficiency and user clarity. Key features were defined and prioritized based on:

  • Event Creation:  Simplifies a previous process and ensures consistency across events.

  • Participant Self-Registration: Enhances user trust and reduces back-office workload.

  • Role-Based Dashboards: Data privacy and ensures users only see what’s relevant to their role.

  • Overview & Tracking Panels: Enables fast decision-making and proactive support before the event.

Prototyping Process

Due to the project's confidentiality and tight timeline, I adopted a lean prototyping approach—building just enough to align with business goals, validate flows, and guide development.

High-Fidelity UI Prototypes

  • I used the Oblique design system as a basis of our design identity, and mapped the business needs with the component-based high-fidelity designs in Figma.

  • Designed for desktop-first usage, with attention to accessibility and readability.

Collaboration & Iteration

  • Shared designs regularly in UX/dev/BA/SME syncs to identify edge cases early.

  • Maintained a version history to track iterations and decisions.

Design Handoff

  • Structured designs in Figma with clear naming and auto-layout.

  • Created UX review sessions during implementation to support front-end devs.

Reflection

Designing the platform challenged me to balance quality UX work with limited access to end users. What I’m proud of:

  • I established a strong design process under constraint, using weekly collaboration with different stakeholders for real-world testing.

  • I introduced role-based UI logic that made a complex system feel simple to each user group.

What I would improve

  • I’d invest in better documentation for long-term scaling, especially for future teams unfamiliar with the behind design decisions.

Final thoughts

This project reminded me that UX maturity is not about ideal conditions, but about delivering quality outcomes in real-world constraints. It sharpened my skills in stakeholder alignment, design diplomacy, and decision-making—key capabilities for a senior designer. 

Outcome & Impact

The project delivered a functional and intuitive platform that modernized the way to organize and manage events.

Some outputs

  • 100% replacement of the outdated legacy system with a streamlined, role-based event platform.

  • Significant reduction in manual effort: Event creation and participant management processes are now fully digital.

  • Reduced number of support tickets for the team.

Stakeholder Feedback

  • Product Owner and BA praised the consistency and reusability of design file, which helped reduce discussion time.

  • Developers appreciated the design based on design system, leading to smoother implementation cycles.

  • Internal testers noted that the registration and dashboard flows felt “straightforward” and “game-changer”.

Strategic Value

  • The new platform is scalable for future other departments or institutional uses. The Product is already adopted by organization to be adopted as an internal tool.

bottom of page