top of page

The
Metro Musicians

Designing for Fairness, Visibility, and Community in Montreal’s Metro Performance System

Role: Research, UX/UI Design, Prototyping

Timeline: 1 Month

Context

As a former metro violinist in Montreal and Iran, I experienced firsthand the informal and often chaotic process of booking performance spots. Before STM digitized reservations, musicians physically signed up at 6 a.m., leading to competition, conflict, and inequity.

Although STM later introduced an online booking system, it solved scheduling — but not community.

Design Principles

Problem

 

The current system allows digital booking but does not support:

  • Musician visibility (who is performing when)

  • Collaboration between performers

  • Digital tipping or social linking 

  • Transparency in scheduling behavior

The result: musicians operate in isolation within a shared space.

Community Before Competition

The system should encourage collaboration rather than intensify booking rivalry.

Transparent & Accountable

Availability, scheduling, and performer visibility must be clear and enforce fair use.

Reduce Friction, Not Expression

Technology should simplify logistics without interrupting the performance experience.

Hybrid Presence

The platform bridges physical metro performance and digital identity.

Solution

Metro Musician introduces three core systems:

1️⃣ Musician Profiles

  • Bio, instrument, preferred stations

  • Sample audio

  • Booking schedule

  • Discoverable by genre or instrument

2️⃣ Booking Interface

  • View available spots

  • See who is performing

  • Receive reminders

  • Cancel bookings

3️⃣ Collaboration Tools

  • Discover compatible musicians

  • Connect for joint performances

  • Encourage genre-based pairing

Full interface exploration used to test navigation, booking flow, and musician discovery.

Iterative Design Process

I explored multiple interface structures and user flows in Figma to test how musicians would navigate booking, discover performers, and manage profiles.

 

Beginning with low-fidelity wireframes focused on core functionality, I gradually refined hierarchy, layout, and interaction patterns to improve clarity and usability across the system.

bottom of page