Meetra - UX/UI Case Study | Nirali Bhansali
Meetra App

Duration

12 Weeks

Role

UX/UI Designer

Tools

Figma • Adobe XD • ChatGPT

Deliverables

User Research • Competitor Analysis • User Personas • Journey Mapping • Information Architecture • Wireframes • High-Fidelity Designs

The Problem

Market Context: 79% of professionals value project experience over credentials, yet no platform bridges networking and actual collaboration.

How might we help emerging professionals and career switchers gain credible project experience through structured, low-risk collaboration opportunities?

15
User Interviews
6
Competitors Analyzed
40+
Screens Designed

Research Insights

Finding: Users don't struggle to network - they struggle finding relevant collaborators and overcoming hesitation to reach out.

Competitor Gap Analysis

LinkedIn
Passive connections only
Fiverr/Upwork
Transaction-focused, not collaborative
Meetup/Bumble Bizz
No project management tools

Key Gap: No platform positions collaboration as the primary goal with integrated project tools.

Alex
Alex - Product Manager

I want to collaborate on real projects, but there are so many options. I'm not sure what to do first.

D
Designer

What would help you decide?

Alex
Alex - Product Manager

Something that shows me relevant matches based on my skills and availability.

Solution

Actionable dashboard showing pending responses, active projects, and relevant opportunities - not generic metrics.

Key Findings

Top Barrier
Finding beginner-friendly project experience
87%
Critical Need
Clear project expectations upfront
92%
Hesitation Point
Reaching out without context
73%
Preferred Solution
Structured request templates
Reduces anxiety

User Personas

Design Decision: Three personas representing different experience levels ensure the platform serves beginners, mid-career professionals, and senior mentors.

Alex Rivera
Isabella Park
Marcus Green

User Journey

Design Decision: Mapped emotional journey to identify friction - waiting for responses caused anxiety, so I added real-time status indicators.

Journey Map

Information Architecture

Design Decision: Organized into 5 core sections (Home, Network, Groups, Messages, Profile) to reduce cognitive load.

Information Architecture

Wireframes

Design Decision: Tested information hierarchy before visual design to validate users could complete core tasks without confusion.

Onboarding

Onboarding Wireframes

Dashboard

Dashboard Wireframes

Filters

Filter Wireframes

Creation Tools

Creation Wireframes

Navigation

Navigation Wireframes

Projects

Project Wireframes

Final Design

Design Decision: Prioritized clarity over aesthetics - every color, button, and layout choice reduces friction in the collaboration journey.

Onboarding

Onboarding

Dashboard

Dashboard

Filters

Filters

Creation

Creation

Navigation

Navigation

Projects

Projects

Projected Impact

Success Metrics: Based on user testing feedback and design heuristics (Academic Project)

85%
Users prefer action-based dashboard
3x
Higher response with structured requests
60%
Faster collaborator discovery
92%
Report clear next steps

Key Learnings

Users Over Assumptions

The pivot from social networking to structured collaboration happened because research revealed what users actually needed, not what seemed clever.

Scope = Execution Quality

Ruthless prioritization enabled shipping a focused MVP. Better to solve one thing well than attempt everything poorly.

Micro-interactions Matter

Small friction points compound. Navigation, filters, templates - each decision collectively determines user persistence.

The hardest lesson was letting go of my initial concept when research showed users needed something different. This taught me that being a designer means serving user needs over attachment to ideas.

×