Homie Mobile Interface Presentation

Homie

Mobile App design for a platform that offers seamless roommate dynamic navigation ensuring harmonious cohabitation and streamlined interactions.

MY ROLE

As a Senior UX Designer I was responsible for user research , stakeholder interviews, contextual inquiry, synthesis, product strategy, workflow design, information architecture, wireframing, usability testing, stakeholder facilitation, and design leadership

THE TEAM

UX Designer & Strategist (Me)
2 Junior UI/UX Designers
Product Manager
3 Developers
Legal & operational stakeholders

SKILLS

UX Research
UX Design
Design Strategy
Service Design

TIMELINE

6 Months



A fragmented system of emails, spreadsheets, folders, and manual follow-ups supported more than 500 legal professionals across teams and 1,000+ cases every week.

I led the research, strategy, and experience design of a centralized Document Management System that connected documents, people, and workflows and gave legal teams greater visibility, control, and confidence.

60%

reduction in document
retrieval time

3x

faster workflow
coordination & handoffs

80%

improvement in
document discoverability

01

Research & Discovery

A growing law firm held together by emails

Every legal matter moved through multiple departments before completion. But there was no shared system supporting that movement.

Documents were exchanged over email. Progress was tracked manually. Important context remained trapped in inboxes. Version histories depended on individual memory, and managers frequently followed up to understand where work stood.

As case volumes increased, this informal system began creating real operational risk.

Found in Spam: A short story about one case, too many emails, and a missing document
1 New Case Arrives
2 Passed to Filing
3 Here Comes the Manual Work
4 Sent for Review
5 Version 2. Version 3. Version...?
6 One More Handoff
7 One Week Later...
8 The Search Begins
9 Found in Spam
10 But Which Version?
11 The Deadline Doesn't Wait
12 Just Another Day at the Firm

Understanding the workflow before designing the tool

Rather than beginning with features, I investigated how documents, information, and responsibility moved across the organization.

The research combined stakeholder perspectives with direct observation of everyday work.

06

Stakeholder Interviews

12

User Interviews

03

Contextual
Observation Sessions

200+

Observations

03

Rounds of Usability
Testing

To truly understand how work happened at the firm, I stepped into the day to day realities of the people doing it. I Interviewed, listened, observed, and mapped what I saw

I shadowed employees as they received cases, created documents, searched for files, transferred work between teams, and responded to status requests.

1.User Research

What employees experienced?

  • Documents were difficult to locate.
  • Multiple versions circulated without a clearly approved file.
  • Teams repeated work because previous actions were not visible.
  • Ownership became unclear when documents crossed teams.
  • Administrative tasks consumed time that could have supported legal work.

The first reframing

Leadership initially believed the firm needed a better document repository.

The early workflow analysis suggested a broader challenge:

Documents were not simply difficult to store. They were difficult to move, track, govern, and act upon across teams.

User Personas
User Personas Grid
User Journey Maps
User Journey Maps Matrix
02

Analysis & Synthesis

Scenario Mapping
Scenario Mapping Whiteboard Sessions
Observations
DMS Structured Observations Table
Affinity Mapping
DMS Affinity Mapping Clustering
From 200+ observations to five recurring themes

After each interview and observation session, I captured quotes, behaviors, breakdowns, workarounds, and opportunities.

Across 18 research sessions, this produced more than 200 observations.

I synthesized the evidence through affinity mapping and thematic clustering, identifying five interconnected themes:

Information access

Finding the correct document depended on knowing where someone had stored or shared it.

Manual processes

Repeated data entry slowed employees down and introduced avoidable errors.

Version management

Employees lacked confidence that they were viewing or editing the most current file.

Workflow visibility

Once work moved to another department, its status and ownership became difficult to trace.

Collaboration

Important decisions and context were distributed across emails, conversations, and individual tracking methods.

These themes shifted the project from feature thinking to systems thinking.

Five Key insights that changed the product

01

Finding information was harder than creating it

Design Response: Contextual search.
02

Administrative work was consuming time

Design Response: Reusable templates.
03

Version confusion created operational risks

Design Response: Version history and audit trails.
04

Workflow ownership was invisible

Design Response: Assignment management and workflow tracking.
05

Teams needed a shared source of truth

Design Response: Centralized workflow ecosystem.

The firm did not only have a document-management problem.
It had a workflow-coordination problem.

That realization became the foundation of the product strategy.