Owned the Analytical Tool Hackathon

Product Ownership

Owned and led a one-day business hackathon, driving the development and launch an MVP of an admin panel for analytical events and a Figma plugin for annotating layouts with events.

Owned the Analytical Tool Hackathon

Product Ownership

Owned and led a one-day business hackathon, driving the development and launch an MVP of an admin panel for analytical events and a Figma plugin for annotating layouts with events.

Owned the Analytical Tool Hackathon

Product Ownership

Owned and led a one-day business hackathon, driving the development and launch an MVP of an admin panel for analytical events and a Figma plugin for annotating layouts with events.

Owned the Analytical Tool Hackathon

Product Ownership

Owned and led a one-day business hackathon, driving the development and launch an MVP of an admin panel for analytical events and a Figma plugin for annotating layouts with events.

interface of event admin panel and Figma plugin

My role

As the Owner of the Business Hackathon, I led the initiative to develop and launch an MVP of an admin panel for analytical events and a Figma plugin for event markup. I defined the hackathon goals, aligned cross-functional teams, and ensured the successful delivery of both projects within 1 day. After the launch, I conducted training sessions for analysts, designers, and product owners to ensure smooth adoption and effective use of the new tools.

Skills applied

Product Ownership, Cross-functional Team Leadership, MVP Development, Problem Solving and Decision Making, Training and Knowledge Sharing.

Project type

Business Hackathon

Role

Project Manager

interface of event admin panel and Figma plugin

My role

As the Owner of the Business Hackathon, I led the initiative to develop and launch an MVP of an admin panel for analytical events and a Figma plugin for event markup. I defined the hackathon goals, aligned cross-functional teams, and ensured the successful delivery of both projects within 1 day. After the launch, I conducted training sessions for analysts, designers, and product owners to ensure smooth adoption and effective use of the new tools.

Skills applied

Product Ownership, Cross-functional Team Leadership, MVP Development, Problem Solving and Decision Making, Training and Knowledge Sharing.

Project type

Business Hackathon

Role

Project Manager

interface of event admin panel and Figma plugin

My role

As the Owner of the Business Hackathon, I led the initiative to develop and launch an MVP of an admin panel for analytical events and a Figma plugin for event markup. I defined the hackathon goals, aligned cross-functional teams, and ensured the successful delivery of both projects within 1 day. After the launch, I conducted training sessions for analysts, designers, and product owners to ensure smooth adoption and effective use of the new tools.

Skills applied

Product Ownership, Cross-functional Team Leadership, MVP Development, Problem Solving and Decision Making, Training and Knowledge Sharing.

Project type

Business Hackathon

Role

Project Manager

interface of event admin panel and Figma plugin

My role

As the Owner of the Business Hackathon, I led the initiative to develop and launch an MVP of an admin panel for analytical events and a Figma plugin for event markup. I defined the hackathon goals, aligned cross-functional teams, and ensured the successful delivery of both projects within 1 day. After the launch, I conducted training sessions for analysts, designers, and product owners to ensure smooth adoption and effective use of the new tools.

Skills applied

Product Ownership, Cross-functional Team Leadership, MVP Development, Problem Solving and Decision Making, Training and Knowledge Sharing.

Project type

Business Hackathon

Role

Project Manager

Problem

The company had multiple development teams, each working independently on different parts of the product. This sometimes led to inconsistencies in certain processes. The analytics team requested help in creating unified standards for storing and managing analytical events.

Key problems to be solved:

Lack of a convenient tool

There was no efficient way to create and modify events, making the process cumbersome. The existing event table was overloaded and difficult to navigate, leading some teams to maintain their own separate lists.

Lack of a convenient tool

There was no efficient way to create and modify events, making the process cumbersome. The existing event table was overloaded and difficult to navigate, leading some teams to maintain their own separate lists.

Lack of a convenient tool

There was no efficient way to create and modify events, making the process cumbersome. The existing event table was overloaded and difficult to navigate, leading some teams to maintain their own separate lists.

Inconsistent naming

Event names weren’t standardized. Every team labeled them differently. This resulted in numerous duplicates, making it hard to find the right events and keep them up to date.

Inconsistent naming

Event names weren’t standardized. Every team labeled them differently. This resulted in numerous duplicates, making it hard to find the right events and keep them up to date.

Inconsistent naming

Event names weren’t standardized. Every team labeled them differently. This resulted in numerous duplicates, making it hard to find the right events and keep them up to date.

Challenges in event monitoring

Without a clear tracking system, it was hard to monitor events in the event table, leading to release delays. Checking event history was difficult, and there was no easy way to confirm if an event was created. Some events also lacked a design preview, making validation even harder.

Challenges in event monitoring

Without a clear tracking system, it was hard to monitor events in the event table, leading to release delays. Checking event history was difficult, and there was no easy way to confirm if an event was created. Some events also lacked a design preview, making validation even harder.

Challenges in event monitoring

Without a clear tracking system, it was hard to monitor events in the event table, leading to release delays. Checking event history was difficult, and there was no easy way to confirm if an event was created. Some events also lacked a design preview, making validation even harder.

Ideas

During a brainstorming session in the design team, we came up with an idea for two tools that could address all the identified challenges:

box with files

Event admin panel

The admin panel could become a single source for storing and editing events.

box with files

Event admin panel

The admin panel could become a single source for storing and editing events.

box with files

Event admin panel

The admin panel could become a single source for storing and editing events.

Figma icon

Figma plugin

With the Figma plugin, events in the admin panel could be linked to design mockups, ensuring that every event had a preview.

Figma icon

Figma plugin

With the Figma plugin, events in the admin panel could be linked to design mockups, ensuring that every event had a preview.

Figma icon

Figma plugin

With the Figma plugin, events in the admin panel could be linked to design mockups, ensuring that every event had a preview.

Since event management was an urgent issue, we decided to speed up the process by organizing a one-day hackathon. The event brought together designers, front-end and back-end developers, and an analyst. After a full day of focused collaboration, we successfully developed and launched both tools while also standardizing event naming and parameters.

Solution

1. Event naming conventions

The first step was to establish consistent naming rules for events. We based our approach on the principles used in design systems, where elements follow a structured hierarchy from the smallest (atoms) to the largest (pages).

This method ensured unique event names and clearly indicated the path to the UI element each event was assigned to. Below is an example of how event names were structured for a filtering component.

description of event name structure based on design system principles
description of event name structure based on design system principles
description of event name structure based on design system principles

Event naming diagram

2. Admin panel for analytical events

The admin panel became the single source of truth for analytical events across all company projects. It also solved the issue of duplicate events and inconsistent parameters. Now, analysts could only select from a predefined set of parameters, moderated by a super admin.

list of events in admin panel
list of events in admin panel
list of events in admin panel

Admin panel for analytical events

3. Figma plugin

With our internal Figma plugin, we linked design mockups to the event admin panel. This allowed teams to quickly check if all necessary events were added to a design. Thanks to the integration, users could jump directly from a Figma file to a specific event in the admin panel. Additionally, the panel now displayed a preview of the UI component associated with each event.

figma plugin interface
figma plugin interface
figma plugin interface

Annotating layouts with analytical events

Results

The MVP we launched in just one day successfully tackled the key issues related to event storage, editing, and management:

  • Standardized naming conventions eliminated duplicate events.

  • Standardized naming conventions eliminated duplicate events.

  • A unified event database and restricted parameter selection sped up event creation and verification, reducing the time required to release new features.

  • A unified event database and restricted parameter selection sped up event creation and verification, reducing the time required to release new features.

  • The integration between the event admin panel and Figma ensured that all UI events had previews, making it easier to visually confirm that every required event was included.

  • The integration between the event admin panel and Figma ensured that all UI events had previews, making it easier to visually confirm that every required event was included.

The solution was well received by the analytics team and company leadership. After launching the MVP, I organized and conducted training sessions for designers, analysts and product owners. Next steps included adding filtering, search and grouping features to the admin panel.

Results

The MVP we launched in just one day successfully tackled the key issues related to event storage, editing, and management:

  • Standardized naming conventions eliminated duplicate events.

  • A unified event database and restricted parameter selection sped up event creation and verification, reducing the time required to release new features.

  • The integration between the event admin panel and Figma ensured that all UI events had previews, making it easier to visually confirm that every required event was included.

The solution was well received by the analytics team and company leadership. After launching the MVP, I organized and conducted training sessions for designers, analysts and product owners. Next steps included adding filtering, search and grouping features to the admin panel.

  • Let's connect.

khristina.kuklina@gmail.com

Khristina Kuklina ©️ 2025

  • Let's connect.

khristina.kuklina@gmail.com

Khristina Kuklina ©️ 2025

  • Let's connect.

khristina.kuklina@gmail.com

Khristina Kuklina ©️ 2025

  • Let's connect.

khristina.kuklina@gmail.com

Khristina Kuklina ©️ 2025