WEB APP

CueKon

I turned wide, hard-to-read production spreadsheets into a readable, filterable, and live-synced Web App, helping performance and production teams work from the same flow data.

Web AppProduct DesignAI-assisted BuildDeploymentVercel
Who It Was For
IndustryStage Production / Live Events

CueKon is built for stage, production, and live-event teams that need to collaborate across roles and stay in sync on site.
These teams often include:

  • Producers, PMs, and stage managers who are responsible for coordinating workflows, roles, and overall progress
  • Technical and on-site crew members who need to quickly find the workflow details and latest status relevant to their role
Main Problem

Overly wide rundowns mixed role-specific details together, making on-site priorities difficult to see at a glance.

  • Director, stage, technical, and support details were mixed into an overly wide table, forcing on-site users to scroll back and forth for key information.
  • Changes in instructions, assignments, and notes between Cues had to be compared cell by cell, making meaningful differences easy to miss.
  • After an update, it was difficult to ensure that everyone was viewing the same latest version.
  • Live progress relied on verbal reminders or manual checks, while role-specific views were difficult to switch between.
Before / After
01

Rundown Reading Load

Before
Google Sheet columns became too wide, forcing the team to scroll horizontally while director, technical, and support notes stayed mixed together
After
CueKon turns flow content into a readable interface across devices, helping teams focus on the current section, key details, and the fields they choose to view
02

Automatic Cue Difference Summary

Before
Differences between Cues had to be checked manually cell by cell, making real changes easy to miss
After
The Cue field automatically summarizes differences between the previous and current Cue, helping stage managers and technicians see what changes next
03

Version Sync

Before
Whenever the rundown changed, the team had to confirm whether everyone was viewing the same latest version
After
One shared data source feeds different role views, keeping the official rundown, technical view, and support view aligned
04

Live Progress Sync

Before
On-site progress depended on verbal reminders or manual checks
After
Live Mode lets the controller advance the flow while the team follows the same progress in sync
How I Solved It

I first broke a traditional rundown into data layers such as events, Cues, role-based fields, and live status. Then I planned the official rundown, technical view, support view, spreadsheet mode, and Live Mode, turning a wide static table into an interface that adapts to role, device, and on-site context.

This case was not just about designing screens. The main work was turning product requirements into a clear usage flow: users can set up events and flow data before production, read and edit through different role views during preparation, and use Live Mode to sync progress on site. I led the feature planning and build, with AI assistance for the homepage and interface, to validate how a production workflow tool could move from concept to public product.

Product FlowTurning rundowns from static documents into editable, filterable, and live-synced on-site tools.
Create EventSet up a performance or production project
Official RundownOrganize Cues, time, and sections
Role ViewsTechnical / support / field filters
Fast EditingSpreadsheet mode
Live SyncLive Mode
What I Delivered
Results
Core OutcomeI completed and deployed a publicly accessible Web App that can be formally used, showing my ability to move from requirement breakdown and feature planning to interface structure and production deployment.
  • Reorganized traditional rundowns into a readable, editable, and role-switchable product flow.
  • Designed and implemented the CueKon core web app, landing page, and support documentation.
  • Planned member invitations, template saving, export formats, and Live Mode so the tool is closer to real product usage.
  • Created a product foundation that could extend into a SaaS, internal tool, or production workflow platform.
Other Case
OPERATIONS AUTOMATION SYSTEM

Video Production Operations System

I helped a small video production team organize the recurring blockers across 6-8 monthly projects, turning kickoff, tasks, files, crew availability, billing, and accounting into one system the team could use every day.

Read this case