B2B Complex System
NINA Manager
NINA is a smart liquor pourer that locks onto any bottle, allows paying for the exact amount poured.
NINAs are deployed across stadiums and VIP venues. Clients scan a QR code, select their spirit, and pour their drink on demand.
The app enables venue operators to monitor devices, track patterns, perform operations, and access real-time insights.
6 months
CTO, Developers, Operations Team
Redesign of The Home Page
Before
After
Problems
Outdated Interface
Text-heavy and visually dated, creating immediate cognitive overload.
Irrelevant Metrics
A flat list with no visual hierarchy or actionable UI patterns, forcing operators to manually scan for urgent issues.
Lacks Simplicity
The interface wasn't optimized for mobile contexts that venue operators needed - like quick status checks.
Focuses on Problems
The home screen highlighted system alerts, priming operators to expect issues.
Solutions
Modern Look
Refined color contrast and card layouts reduce noise and improve hierarchy.
Minimize Attention
Financial KPIs in a top widget for quick tracking and color-coded status indicators fo rapid venue assessment.
Improved Architecture
Home screen split into three scrollable sections that declutter the interface and center high-frequency tasks.
Component System
The most-trafficked screen is to highlight revenue and operations first, to prime problem-solving.
The Design Process
My Role
- Sole product designer in an agile startup environment, reporting directly to CTO and CEO with end-to-end ownership of the design process.
- Collaborated with frontend, backend, and embedded engineering teams to balance feature ambition with technical constraints and hardware limitations.
- Conducted user interviews and stakeholder sessions with Operations teams to validate design decisions and inform product priorities.
Product Discovery
- Venue operators required rapid status checks and quick actions while moving throughout their locations during high-volume service periods.
- Business stakeholders needed the platform to demonstrate NINA's ROI and revenue impact to potential clients.
- User research revealed a clear task hierarchy: high-frequency maintenance actions (device swaps, bottle replacements) versus lower-frequency configurations.
- Feedback sessions with Operations identified a critical gap: device firmware updates caused unexpected bugs that required technical context operators didn't have on hand.
User Personas
- High engagement - venue operators that monitor NINAs across their venues, require quick status updates and make a lot of actions regularly on the app.
- Low engagement - Venue managers who interested in revenue and consumption patterns. Mostly enter the home page only for a quick view.
Device Management
The Devices Page
- The interface mirrored the physical NINA stand for quick scanning the app along the stand.
- The interface mirrored the physical NINA stand for quick scanning the app along the stand.
- Information hierarchy prioritized 2 main operations: swapping depleted bottles and low battery devices.
Bottle Service
Bottle Service Page
- A guest calls an operator and pays for every drink in the room to enjoy, like an open tab.
- Guests no longer need to use the application to pour, since another guest pays for the drinks.
- Bottle images are important to quickly identify drinking trends.
- It's crucial to let operators know the consequences of stopping Bottle Service.
Next Case Study
NINA - Commercial Drinking Experience
B2B Complex System
NINA Manager
NINA is a smart liquor pourer that locks onto any bottle, allows paying for the exact amount poured.
NINAs are deployed across stadiums and VIP venues. Clients scan a QR code, select their spirit, and pour their drink on demand.
The app enables venue operators to monitor devices, track patterns, perform operations, and access real-time insights.
6 months
CTO, Developers, Operations Team
Redesign of The Home Page
Before
After
Problems
Outdated Interface
Text-heavy and visually dated, creating immediate cognitive overload.
Irrelevant Metrics
A flat list with no visual hierarchy or actionable UI patterns, forcing operators to manually scan for urgent issues.
Lacks Simplicity
The interface wasn't optimized for mobile contexts that venue operators needed - like quick status checks.
Focuses on Problems
The home screen highlighted system alerts, priming operators to expect issues.
Solutions
Modern Look
Refined color contrast and card layouts reduce noise and improve hierarchy.
Minimize Attention
Financial KPIs in a top widget for quick tracking and color-coded status indicators fo rapid venue assessment.
Improved Architecture
Home screen split into three scrollable sections that declutter the interface and center high-frequency tasks.
Component System
The most-trafficked screen is to highlight revenue and operations first, to prime problem-solving.
The Design Process
My Role
- Sole product designer in an agile startup environment, reporting directly to CTO and CEO with end-to-end ownership of the design process.
- Collaborated with frontend, backend, and embedded engineering teams to balance feature ambition with technical constraints and hardware limitations.
- Conducted user interviews and stakeholder sessions with Operations teams to validate design decisions and inform product priorities.
Product Discovery
- Venue operators required rapid status checks and quick actions while moving throughout their locations during high-volume service periods.
- Business stakeholders needed the platform to demonstrate NINA's ROI and revenue impact to potential clients.
- User research revealed a clear task hierarchy: high-frequency maintenance actions (device swaps, bottle replacements) versus lower-frequency configurations.
- Feedback sessions with Operations identified a critical gap: device firmware updates caused unexpected bugs that required technical context operators didn't have on hand.
User Personas
- High engagement - venue operators that monitor NINAs across their venues, require quick status updates and make a lot of actions regularly on the app.
- Low engagement - Venue managers who interested in revenue and consumption patterns. Mostly enter the home page only for a quick view.
Device Management
The Devices Page
- The interface mirrored the physical NINA stand for quick scanning the app along the stand.
- The interface mirrored the physical NINA stand for quick scanning the app along the stand.
- Information hierarchy prioritized 2 main operations: swapping depleted bottles and low battery devices.
Bottle Service
Bottle Service Page
- A guest calls an operator and pays for every drink in the room to enjoy, like an open tab.
- Guests no longer need to use the application to pour, since another guest pays for the drinks.
- Bottle images are important to quickly identify drinking trends.
- It's crucial to let operators know the consequences of stopping Bottle Service.
Next Case Study
NINA - Commercial Drinking Experience
B2B Complex System
NINA Manager
NINA is a smart liquor pourer that locks onto any bottle, allows paying for the exact amount poured.
NINAs are deployed across stadiums and VIP venues. Clients scan a QR code, select their spirit, and pour their drink on demand.
The app enables venue operators to monitor devices, track patterns, perform operations, and access real-time insights.
6 months
CTO, Developers, Operations Team
Redesign of The Home Page
Before
After
Problems
Outdated Interface
Text-heavy and visually dated, creating immediate cognitive overload.
Irrelevant Metrics
A flat list with no visual hierarchy or actionable UI patterns, forcing operators to manually scan for urgent issues.
Lacks Simplicity
The interface wasn't optimized for mobile contexts that venue operators needed - like quick status checks.
Focuses on Problems
The home screen highlighted system alerts, priming operators to expect issues.
Solutions
Modern Look
Refined color contrast and card layouts reduce noise and improve hierarchy.
Minimize Attention
Financial KPIs in a top widget for quick tracking and color-coded status indicators fo rapid venue assessment.
Improved Architecture
Home screen split into three scrollable sections that declutter the interface and center high-frequency tasks.
Component System
The most-trafficked screen is to highlight revenue and operations first, to prime problem-solving.
The Design Process
My Role
- Sole product designer in an agile startup environment, reporting directly to CTO and CEO with end-to-end ownership of the design process.
- Collaborated with frontend, backend, and embedded engineering teams to balance feature ambition with technical constraints and hardware limitations.
- Conducted user interviews and stakeholder sessions with Operations teams to validate design decisions and inform product priorities.
Product Discovery
- Venue operators required rapid status checks and quick actions while moving throughout their locations during high-volume service periods.
- Business stakeholders needed the platform to demonstrate NINA's ROI and revenue impact to potential clients.
- User research revealed a clear task hierarchy: high-frequency maintenance actions (device swaps, bottle replacements) versus lower-frequency configurations.
- Feedback sessions with Operations identified a critical gap: device firmware updates caused unexpected bugs that required technical context operators didn't have on hand.
User Personas
- High engagement - venue operators that monitor NINAs across their venues, require quick status updates and make a lot of actions regularly on the app.
- Low engagement - Venue managers who interested in revenue and consumption patterns. Mostly enter the home page only for a quick view.
Device Management
The Devices Page
- The interface mirrored the physical NINA stand for quick scanning the app along the stand.
- The interface mirrored the physical NINA stand for quick scanning the app along the stand.
- Information hierarchy prioritized 2 main operations: swapping depleted bottles and low battery devices.
Bottle Service
Bottle Service Page
- A guest calls an operator and pays for every drink in the room to enjoy, like an open tab.
- Guests no longer need to use the application to pour, since another guest pays for the drinks.
- Bottle images are important to quickly identify drinking trends.
- It's crucial to let operators know the consequences of stopping Bottle Service.
Next Case Study
NINA - Commercial Drinking Experience