Show video description

Show video description

Show video description

Show video description

Streamlining event access permissions

Timeframe:

December 2023 (3 weeks)

Team:

PM

+

FE

+

BE

+

QA

🎯 Problem framing

🎯 Problem framing

🎯 Problem framing

🎯 Problem framing

🔍 User research

🔍 User research

🔍 User research

🔍 User research

🖌 Design iteration

🖌 Design iteration

🖌 Design iteration

🖌 Design iteration

🔁 Handoff & QA

🔁 Handoff & QA

🔁 Handoff & QA

🔁 Handoff & QA

📊 Metrics tracking

📊 Metrics tracking

📊 Metrics tracking

📊 Metrics tracking

TL;DR

When managing a large number of roles in an event, configuring their permissions one by one was inefficient. I introduced bulk editing and smart defaults to streamline setup and mange access at scale.

📊Impact

Business outcome

  • 70% faster setup when configuring access for large events (based on reducing repetitive steps across 30–50 roles)

  • Eliminated on average 5 support emails per month related to access misconfigurations

  • Reduced role editing time from 28 minutes to 3 minutes when updating 30 roles

Business outcome

  • 70% faster setup when configuring access for large events (based on reducing repetitive steps across 30–50 roles)

  • Eliminated on average 5 support emails per month related to access misconfigurations

  • Reduced role editing time from 28 minutes to 3 minutes when updating 30 roles

Business outcome

  • 70% faster setup when configuring access for large events (based on reducing repetitive steps across 30–50 roles)

  • Eliminated on average 5 support emails per month related to access misconfigurations

  • Reduced role editing time from 28 minutes to 3 minutes when updating 30 roles

Business outcome

  • 70% faster setup when configuring access for large events (based on reducing repetitive steps across 30–50 roles)

  • Eliminated on average 5 support emails per month related to access misconfigurations

  • Reduced role editing time from 28 minutes to 3 minutes when updating 30 roles

User feedback

  • The user satisfaction score of this feature improved from 2.3 on average to 4.6

  • " This looks fantastic! So much easier to navigate and understand"

  • "I used to manually edit roles when they were created by clients, to make sure they don't have too much permission. The new solution works for me like a dozen times easier."

User feedback

  • The user satisfaction score of this feature improved from 2.3 on average to 4.6

  • " This looks fantastic! So much easier to navigate and understand"

  • "I used to manually edit roles when they were created by clients, to make sure they don't have too much permission. The new solution works for me like a dozen times easier."

User feedback

  • The user satisfaction score of this feature improved from 2.3 on average to 4.6

  • " This looks fantastic! So much easier to navigate and understand"

  • "I used to manually edit roles when they were created by clients, to make sure they don't have too much permission. The new solution works for me like a dozen times easier."

User feedback

  • The user satisfaction score of this feature improved from 2.3 on average to 4.6

  • " This looks fantastic! So much easier to navigate and understand"

  • "I used to manually edit roles when they were created by clients, to make sure they don't have too much permission. The new solution works for me like a dozen times easier."

🎬Long story short

📍Customer Success (CS) team flagged the inefficiency of the attendee permission system as a time sink, but it wasn’t on the roadmap since it only affected internal users.

📍Customer Success (CS) team flagged the inefficiency of the attendee permission system as a time sink, but it wasn’t on the roadmap since it only affected internal users.

📍Customer Success (CS) team flagged the inefficiency of the attendee permission system as a time sink, but it wasn’t on the roadmap since it only affected internal users.

📍Customer Success (CS) team flagged the inefficiency of the attendee permission system as a time sink, but it wasn’t on the roadmap since it only affected internal users.

📊 So I took the initiative by gathering data on time spent per project and the number of projects affected. Then I translated it into estimated costs in dollars to make a business case to the product team.

📊 So I took the initiative by gathering data on time spent per project and the number of projects affected. Then I translated it into estimated costs in dollars to make a business case to the product team.

📊 So I took the initiative by gathering data on time spent per project and the number of projects affected. Then I translated it into estimated costs in dollars to make a business case to the product team.

📊 So I took the initiative by gathering data on time spent per project and the number of projects affected. Then I translated it into estimated costs in dollars to make a business case to the product team.

👥 With the data, I was given the green light. I conducted ongoing interviews with the CS team, collaborated with developers to understand feasibility, and iterated on prototypes.

👥 With the data, I was given the green light. I conducted ongoing interviews with the CS team, collaborated with developers to understand feasibility, and iterated on prototypes.

👥 With the data, I was given the green light. I conducted ongoing interviews with the CS team, collaborated with developers to understand feasibility, and iterated on prototypes.

👥 With the data, I was given the green light. I conducted ongoing interviews with the CS team, collaborated with developers to understand feasibility, and iterated on prototypes.

🚀 When I pitched the solution and its business impact to management, they agreed to implement the solution. After it shipped, anecdotal feedback showed that it saved half hour per project on average.

🚀 When I pitched the solution and its business impact to management, they agreed to implement the solution. After it shipped, anecdotal feedback showed that it saved half hour per project on average.

🚀 When I pitched the solution and its business impact to management, they agreed to implement the solution. After it shipped, anecdotal feedback showed that it saved half hour per project on average.

🚀 When I pitched the solution and its business impact to management, they agreed to implement the solution. After it shipped, anecdotal feedback showed that it saved half hour per project on average.

Curious how I got here? 🦊

Interested in my work?

Whether you're building a UX team or just want to exchange ideas, I’d love to connect.

Crafted with 🦊 curiosity, caffeine, and debug tears.

© 2025 Celine.Li.

Interested in my work?

Whether you're building a UX team or just want to exchange ideas, I’d love to connect.

Crafted with 🦊 curiosity, caffeine, and debug tears.

© 2025 Celine.Li.

Interested in my work?

Whether you're building a UX team or just want to exchange ideas, I’d love to connect.

Crafted with 🦊 curiosity, caffeine, and debug tears.

© 2025 Celine.Li.

Interested in my work?

Whether you're building a UX team or just want to exchange ideas, I’d love to connect.

Crafted with 🦊 curiosity, caffeine, and debug tears.

© 2025 Celine.Li.