neuk · 2026 · Product Design
Infrastructure for shared media rituals
At a glance
Problem
Watching together is socially valuable, but the coordination overhead of finding a place, aligning schedules, and hosting often outweighs the experience itself.
Insight
This is not primarily a content problem. It is a coordination and environment problem.
Product
A platform for booking private watch rooms that integrates venue discovery, scheduling, QR-based room access, remote control, and in-session ordering.
Primary signal
Ability to define product direction across physical service infrastructure and digital product surfaces, not just execute UI.
Hero visual: use the pod room environment image, not UI. The story starts with the physical experience Neuk makes possible.
Product Overview
neuk turns fragmented social planning into a bookable system.
Streaming made content abundant but made shared viewing harder. Friends still want to gather for weekly episode drops, sports games, premieres, and themed watch nights, but current options break down in predictable ways: homes are cramped, theaters are inflexible, and bars optimize for noise and alcohol rather than intentional viewing.
neuk reframes shared viewing as a systems problem. Instead of asking users to manually coordinate a social event across group chats, calendars, streaming platforms, and physical venues, the product packages those dependencies into a single workflow.
Core framing shift
The highest-value design move in this project was redefining the problem from “book a room” to “reduce the coordination cost of gathering.”
Why this problem exists
Three structural forces are breaking shared media rituals.
Streaming fragmentation
Content is distributed across multiple services, so deciding what to watch now requires cross-platform coordination before the event even begins.
Urban living constraints
In dense cities, most apartments cannot comfortably host the kind of group viewing experiences people actually want.
Social friction
Group chats are a poor operating system for planning. Scheduling, splitting costs, invites, and logistics create enough friction to kill the plan.
Use your “Learnings” and “Opportunities” synthesis boards here. They prove the problem is broader than a UI gap and grounded in a service opportunity.
System definition
The product is a coordination layer connecting users, venues, and in-room infrastructure.
Neuk is not just a booking app. It is a service system with three interdependent layers:
User layer
Discovery, scheduling, booking, invites, ticketing, and account history.
Venue layer
Physical pods with room attributes, availability, seating types, AV capabilities, and operating constraints.
Session layer
QR-based check-in, room access, in-session remote controls, food ordering, reminders, and reset logic after the visit.
Primary system visual: use the full System Map asset. This is the most important diagram in the case study because it signals systems thinking immediately.
Secondary system visual: use the Service Blueprint directly after the system map to show customer journey, frontstage touchpoints, backstage operations, and support processes.
Product decisions
I prioritized product direction decisions that made the concept operational, not just appealing.
Decision 1 — Design for physical gathering, not remote viewing
A weaker version of this concept could have become another remote watch-party tool. Research showed the real unmet need was not access to content, but access to the right environment for sharing it together.
Users consistently described homes as too small, theaters as too inflexible, and bars as too public or distracting.
The MVP had to center around bookable private viewing environments, not merely scheduling software.
Evidence
Product implication
Decision 2 — Build a coordination workflow, not a single booking screen
The hard part of the experience happens before playback starts: agreeing on where to go, when to go, and who is actually coming. I structured Neuk around the full path from discovery to confirmed group plan.
Your interviews and affinity maps showed repeated pain points around coordination, scheduling, and splitting costs.
Discovery, booking, QR ticketing, room access, and post-session management had to be one connected system.
Evidence
Product implication
Decision 3 — Treat the phone as the room interface
Instead of making the app stop at booking, I extended it into the session itself. QR-based pairing turns the user’s phone into the operating layer for the room: entry, control, and ordering.
The PRD and blueprint both required room access, session controls, reminders, and operational resets after the event.
The remote is not an extra feature. It is the bridge between digital booking and physical service delivery.
Evidence
Product implication
Use the competitive analysis positioning map and the differences/similarities boards here. They justify why this product category should exist at all.
Core product flows
The product translates a messy social process into a repeatable sequence.
Use these visuals together: Browse home, search results, room listing, and filter screen.
1. Discover and evaluate rooms
Users browse nearby rooms by capacity, equipment, price, and availability. This is where venue characteristics become a product surface rather than a backend constraint.
- Search and filter by location, date, room size, streaming support, seating, and AV quality.
- Expose room attributes that materially affect group decisions, not just cosmetic details.
- Show availability inline so the evaluation step reduces planning back-and-forth.
Use payment, confirmation, and QR ticket visuals as a vertical sequence.
2. Convert intent into a committed plan
The booking flow turns loose interest into a confirmed session with payment, ticketing, and room-level logistics. This is where Neuk reduces dropout caused by fragmented tools.
- Users move from room detail to payment with a clear cost breakdown.
- The QR ticket becomes both proof of purchase and the operational key for entry.
- Booking details persist inside My Bookings, creating continuity across the session lifecycle.
Show the remote flow with the physical room image visible nearby. This is the key digital-to-physical transition in the product.
3. Extend the product into the room
After arrival, the product shifts from marketplace to operating system. Scanning the on-screen QR code activates the room remote, giving the user control over playback, volume, lighting, and eventually food ordering.
- The room is not passive context; it is part of the designed system.
- Remote control is a service layer that links booking data, room state, and in-session actions.
- This step is what elevates Neuk from booking app to service infrastructure.
Use bookings and account screens to show the retention layer of the system.
4. Preserve continuity after the session
Post-session screens turn a one-off event into a repeatable behavior. Booking history, favorites, rebooking, and saved preferences support ritual retention rather than one-time novelty.
- My Bookings structures sessions across active, upcoming, and past states.
- Favorites and account preferences make subsequent booking faster.
- This supports the product’s long-term retention model: repeated social rituals, not one-off usage.
Research to product translation
I translated insight artifacts into system priorities, not just inspiration.
The strongest research signal was that people were not asking for “bigger screens.” They were asking for a middle ground between the intimacy of home and the quality of theaters, without the friction of hosting.
That led to a product definition with three priorities: remove coordination overhead, make the environment itself part of the value proposition, and support repeat behavior rather than special-event novelty only.
Best visual to use here
Use the interview insight synthesis diagram, the affinity mapping board, and one or two participant concept testing boards. These show clear translation from research signal → product requirement.
Success model
Without shipped metrics, I framed success around whether Neuk reduces friction and creates repeat rituals.
Primary metric
Coordination-to-booking conversion
Of users who begin evaluating rooms, how many reach a confirmed session? This is the clearest proxy for whether Neuk meaningfully reduces planning friction.
How I would talk about impact in interviews
I would frame Neuk as a service-system product that creates value by lowering the coordination threshold required to gather. The long-term business question is not simply “will people book a room?” but “can the product make shared viewing repeatable enough to behave like karaoke, bowling, or other social entertainment categories?”
Brand system
The name and logo direction reinforce the product’s core promise: your own corner of the city.
The Neuk brand exploration drew from the idea of a nook: a small, protected, personal place. That concept aligns directly with the product itself — a private environment carved out of the city for shared media rituals.
Use one logo sketch sheet here. This section should stay short; it supports the product concept but should not dominate the case study.