Community product concept

ConcertConnect

Verification before matching

Research showed concertgoers wanted connection, but safety had to come before every match.

Role: Product designer; led research, testing, and presentation
Timeline: 6-week product sprint
Methods: Surveys, interviews, testing, synthesis
Tools: Figma, AI-assisted research

ConcertConnect mobile screens on a dark presentation background

41survey responses synthesized

7user interviews

7usability tests on the prototype

The demand was real. Trust was the blocker.

Our survey found that people shared music taste with close friends, yet often had no one available for a concert. Interviews added the missing context: meeting a stranger felt risky, and users needed proof that a potential companion was real.

AI helped synthesize all 41 responses, draft interview questions, and accelerate competitor research. That left more time for testing and decision-making.

Survey results showing 87, 79, and 97 percent findings — The strongest signal was not a lack of interest. It was a lack of trusted, concert-specific ways to connect.

Identity verification moved to the front of onboarding.

The concept changed from a matching-first experience to a trust-first flow. Photo and ID verification happen before personality and music preferences shape recommendations.

Profiles show compatibility, shared taste, and mutual connections. Community spaces sit apart from direct messages so people can build familiarity before committing to one-to-one contact.

ConcertConnect home and matching interface screens — The matching experience pairs compatibility cues with identity and community context.

Testing removed ambiguity and visual noise.

Seven usability tests exposed confusing navigation icons, an unclear community and direct-message toggle, and gradients that felt overwhelming rather than polished.

We simplified the visual system, clarified navigation, and made the relationship between community and private conversation easier to understand.

Usability testing findings for ConcertConnect — The design changed where testers hesitated, not where the team simply preferred a different style.

The next iteration starts with what I learned.

A live prototype and real-time coordination notifications would be the next steps toward testing this as a product in the context of an actual event.