Ticketrack

Ticketrack is a ticketing feature designed to manage security issues within a cybersecurity platform.

Role:
UX designer

Duration:
Jun 2023 – Jul 2023


Role:
UX designer

Duration:
Jun 2023 – Jul 2023

Project context:
Yes-security help companies secure their low-code and no-code applications by finding and fixing vulnerabilities.

After stakeholders raised concerns about the lack of a clear process for reporting and resolving potential security issues, I proposed a ticketing system.

Explore the final design


When Sarah, a non-technical user, discovers a potential security issue,
she struggles to find a clear, trustworthy channel for reporting it, leading her to abandon
the effort or send critical information into an unmonitored general inbox.


When Sarah, a non-technical user, discovers a potential security issue,
she struggles to find a clear, trustworthy channel for reporting it, leading her to abandon
the effort or send critical information into an unmonitored general inbox.

The solution

EXPLORING THE NEEDS

I began with secondary research to identify key requirements and competitor practices,
then created initial sketches and gathered stakeholder feedback.
The main needs I identified were:

  • Clear and intuitive for both

infosec and regular users.

  • Designed for collaboration.

  • Easily accessible from

multiple screens

FROM 3 IDEAS TO ONE- WHO MADE THE CUT?

Out of three visualization concepts, we chose the third solution—the sidebar
because it supports multitasking and maintains consistency across the platform.

After deciding to go with the sidebar, I began brainstorming with one entry point and the core details in mind.

Easy access and real-time notifications

As a product that highlights security issues, we wanted to include as many entry points
as possible, allowing users to receive quick notifications or access it easily.

Final design- Turn compliance chaos into clarity

A clear and organized ticketing system that highlights compliance issues, allowing team members
to track progress, collaborate, and stay updated until each issue is resolved.

What else?

  • I joined the company with no cybersecurity background and, within two weeks, immersed myself in the field
    enough to start shaping user workflows with a fresh perspective.

  • Faced challenges with user exposure due to the startup's early stage.

  • Unfortunately, the startup is no longer operating, so the feature wasn’t implemented or tested.
    If I’d had the chance, my next step would have been to conduct usability tests with users/design partners
    to refine the design and make sure it truly met their needs.

Ⓒ All rights reserved - Shir 2026

Ⓒ All rights reserved - Shir 2026

Ⓒ All rights reserved - Shir 2026