One connected operating layer.
Replace fragmented tools with one shared source of truth for the whole night.
The jam, in order.
A real-time queue app for open mic and jam nights. Performers discover the right room, prepare their set once, and see exactly when they’re on.
3D is unavailable in this browser, so the case study shows without its animated backgrounds.
The real problem was not event discovery alone. It was uncertainty at every handoff between interest and performance.
Details live across social posts, venue pages and word of mouth. Performers can’t tell what’s required or whether they’re confirmed. Lineups change live without giving everyone the same view, and the connections made after a set disappear when the night and the chat end.
Rather than testing isolated features, the research followed the rhythm of a real open-mic night, from first discovery to the connection made after a set. Each design decision traces back to a real handoff, role or uncertainty in the room.
A night-in-the-life study · small venues and open-mic operationstime horizons: before the venue, during the wait, and after the set.
core perspectives: performer, collaborator and host, in one night.
critical handoffs: discovery, commitment, preparation, arrival, queue, connection.
Where information appears, what creates trust, and what stays unclear before committing.
How performers share their set, understand status, and respond to live changes.
What turns one performance into confidence, collaboration or another opportunity.
Adjacent products solve important slices of the night. None is built around the performer’s complete open-mic experience, from choosing a room to seeing a live place in line and carrying a connection forward.
Replace fragmented tools with one shared source of truth for the whole night.
Five capabilities across the adjacent products. Events and networking are covered in pieces; preparing a set and following a live performer queue are missing everywhere.
| Capability | Open Stage Jam | Meetup | Eventbrite | Vampr |
|---|---|---|---|---|
| Discover live events | Open Stage Jam✓ | Meetup✓ | Eventbrite✓ | Vampr✕ |
| Musician network | Open Stage Jam✓ | Meetup◐ | Eventbrite✕ | Vampr✓ |
| Prepare a set | Open Stage Jam✓ | Meetup✕ | Eventbrite✕ | Vampr◐ |
| Live performer queue | Open Stage Jam✓ | Meetup✕ | Eventbrite✕ | Vampr✕ |
| Post-set connection | Open Stage Jam✓ | Meetup◐ | Eventbrite✕ | Vampr✓ |
Desk research reflects each product’s current positioning, not an exhaustive feature audit.
Vocalist · Austin, TX · 2–4 open mics a month
“I’m ready to perform. I just need to know what happens next.”
The emerging performer. Talented enough to perform, but still building the confidence, network and repeatable stage experience needed to grow.
Design opportunity · replace anxious waiting with preparation, status and connection
The highest friction happens after a performer commits but before the lineup becomes visible. They have invested time, arrived and prepared, yet still can’t answer: “Am I actually on?”
Confidence rises while Alex discovers and chooses a night, drops sharply after joining, bottoms out while waiting with no visible status, then recovers on stage and peaks when connecting afterward.
Alex’s goal never changes: find the right room, arrive prepared and earn stage time. What changes is the amount of uncertainty the experience asks them to carry.
Venue details, requirements and start times conflict.
No reply means arriving without knowing whether there’s space.
Songs, collaborators and needs are explained again.
Lineup changes live, but status stays invisible.
Energy spent managing uncertainty
Venue, atmosphere, time and performer fit live together.
Identity, lineup type and expectations are explicit.
The set and technical notes are already shared.
Now playing, up next and queue status stay visible.
Energy reserved for the performance
Identity travels forward
Performer and host stay aligned
Connections continue afterward
Before the screens had a look, they had a structure. Sign-up sets the role and lands on home. Alex joins the lineup, says what they play and who with, picks a song and confirms; the host approves, runs the queue and calls people up. Every handoff between the lanes syncs live.
ScreenRole splitLive sync
Each stop on the line is a screen. Scroll to follow Alex from walking in to taking the stage.
Alex signs in with Google, Facebook or as a guest, then sets a lightweight identity and role.
DesignA quick wizard with social login, so joining takes seconds at the door.
Alex searches songs, picks the set, and adds collaborators and stage needs.
DesignEntered once, shared with the host, so no one repeats the set at check-in.
The host approves the request, and Alex sees their confirmed place in line.
DesignApproval keeps the host in control without leaving performers guessing.
Alex’s phone shows now playing, up next, and their place in line.
DesignA clear on-deck moment ends the hovering by the stage.
The host approves, reorders and calls people up from one dashboard.
DesignOne live source of truth, synced to every phone in the room.
Scroll through the flow. Each state carries one design decision.
Social login and a three-step profile replace the pen and paper.
Songs, collaborators and technical notes are shared with the host before the night starts.
A live list everyone sees, with the performer’s own place highlighted.
A full-screen on-deck state tells performers when to get ready.
Approvals, order and the next call-up, all in real time.
Real screens from the product. Scroll or drag sideways to turn through the flow.Scroll or swipe sideways to turn through the flow.
The live Open Stage Jam app, in three clips: joining tonight’s lineup from the + button, the guided tour a first-timer gets, and moving between home, the queue, community and profile.
The two calls that shaped the product most, what I chose, and what I let go.
Requests go to the host for approval before joining the queue.
An open list anyone can add to.
Why. An open list is fast but gets gamed and cluttered. Approval keeps the night curated while the performer still sees their status instantly.
Google, Facebook, login or guest entry, then a lightweight identity and role.
Asking for set details and logistics before the performer knows the product.
Why. The opening sequence reduces commitment anxiety. Performers understand the product, choose how to enter, and establish their role before being asked for logistics.
Same three decisionsresolved with confidence
The manager dashboard mirrors the performer app in real time, so every change the host makes reaches every phone in the room.
Illustrative recreation · names and songs are sample data
Joining gives each performer a check-in code. Show it at the entrance and the host confirms the arrival and the song.
Tap any musician to connect, send a message or ask to jam together.
Reached from home and from community: venue, time and the vibe, with the lineup one tap away.
Raw energy, disciplined hierarchy. The system borrows the atmosphere of a small venue without sacrificing usability: red marks action and live status, black holds focus, and warm white gives an editorial counterpoint.
A microphone held in a spotlight ring. The wordmark pairs a clean sans with a hand-drawn “Jam” in Live Red, the same energy as a flyer taped up by the stage.
Bebas Neue is condensed and loud, built for the stage. DM Sans is a neutral sans that stays easy to read in a dark room.
Action and live status
Canvas
Surfaces and cards
Editorial text
These specimens reproduce the component behavior, labels, state colors and hierarchy of the production build, not a parallel concept system.
Source · open-jam-v31.html · recreated from production class names and state logic
Open Stage is used in low light, with loud music, often with an instrument in one hand.
White on the near-black stage UI measures 19.8:1, and the yellow chord text 10.9:1.
Large targets within thumb reach, for someone holding a guitar.
Your place is always written out, from “You’re #3 on the list” to “You’re up next!”, because sounds get lost in the room.
Chords and lyrics open in a large, bold, high-contrast view you can read from a mic stand.
These are product targets for the next validation cycle, not tested results. Each one translates the contextual research into a behavior the live product can measure.
for performers to understand whether they’re confirmed, waiting or up next
Validation target · status clarityrepeated set entry: role, songs, collaborators and needs travel forward once entered
Workflow targetfewer “when am I on?” interruptions during an active room
Operational targetmore post-set collaborations that continue beyond the venue
Community targetTreating the live queue as the core of the product, not a feature, shaped every screen around one shared truth.
Most of the hard problems only show up in the room: glare, noise, and people with their hands full.
Shipping the product myself made me design for real states, like waiting, errors and slow connections, not just ideal screens.
Next: venue accounts for multiple hosts, a projector view so the whole room can see the queue, and reduced-motion support.
This is a design case study; the outcomes above are research-based estimates, not measured results.