Case study · Platonic

We made meeting new people safer and less awkward.

With my colleague Mez Dumas, I built an MVP for a networking app for a Berlin client. The idea: bring people closer through events they organize themselves: no algorithmic feed, no personalization games. The client emphasized that the community, not the individual, sits at the center of the product.

Scope
Aug 2020 – Sep 2020 · With Mez Dumas
Tools
Figma, Prototyping, User Research
Role
Researcher & Product Designer
Platonic hero screens
Problem & outcome

From loneliness to a pitch-ready prototype.

Young professionals relocating to a new city struggle to build a social network, and most existing products feel algorithmic or dating-adjacent. We built a 0→1 prototype our client could pitch to investors, grounded in what users actually told us about meeting strangers online.
Research

Surveys, interviews, and an affinity map.

We ran a Google Forms survey and received 70 responses. Most respondents had already tried non-romantic networking products, most were passively networking, and nearly everyone preferred meeting people with a shared interest over meeting complete strangers. We synthesized the findings in an affinity diagram, distilling everything into three principles.
Affinity diagram
Three research insights
01

People find it challenging to build a social network when moving to a new city.

02

People worry about safety when meeting strangers on apps.

03

People often feel awkward when meeting people through online services.

Ideation

Crazy-eights only got us so far.

We opened with a crazy-eights exercise to generate quick ideas, but nothing jumped out. We didn't want to build another 'meet new friends' app or another LinkedIn. After long discussions we landed on an events-first model: any user can create an event around any topic. An English-speaking expat in Berlin who needs to complete a German registration could team up with others in the same position, skipping the small talk and growing a network casually around a shared task.
Crazy 8s brainstorm
Flow

From feed to event: one continuous loop.

A user starts on her feed, drills into an event, views the creator's profile, joins, gains access to the event-specific chatroom, and eventually creates her own event (description, location, time) before returning to her feed. We limited the prototype to only the essential features, enough to tell the story in a pitch.
User flow diagram
Prototype

From lo-fi to pitch-ready.

With the flow locked we sketched lo- to mid-fi wireframes, iterating quickly between design and testing. We added two screens along the way: a user profile, and a calendar where users can see every event they've joined. A few rounds of fine-tuning later we had a final design the client was ready to bring to investors.
Platonic screen 1
Platonic screen 2
Platonic screen 3
Platonic screen 4
Final screens
Final Platonic screens
Final Platonic screens
Key Takeaways

What this project taught me.

01

User-centered design through community focus.

Protecting autonomy (no personalized feed) forced every other decision into alignment with the brief.

02

Primary + secondary research compound.

The 70 survey responses plus a dozen interviews sharpened decisions much more than either would have alone.

03

Iteration beats cleverness.

Crazy-eights alone didn't yield the answer. Flexible, repeated ideation did.

04

Listen to your users, and your client.

The client's insistence on community-over-algorithm became our north star, and the product is sharper for it.

Next project

Circuit City

Gave a former American retail giant a bold makeover, revamping its user experience and breathing new life into its brand identity.