What is Routeam?

pronounced “Roo·team”

Let’s face it - living with roommates during college can be fun, but coordinating household responsibilities and managing finances? Not always a walk in the park. Here’s how we turned chaos into collaboration.

Routeam

Our group began by identifying a common issue among college students living together: the challenge of managing household responsibilities, including chores and finances.

We embarked on an extensive design process to address the communication challenges among college students living together.

Our approach was multifaceted, incorporating:

  • Competitive analysis, user research, persona development, storyboarding, and the creation of prototypes at various levels of fidelity.

    • This recognition stemmed from observations, surveys, personal experiences, and initial discussions with our target demographic, leading us to formulate our problem statement!

Problem Statement:

"How might we improve communication about household responsibilities for college students living together so that residents can better manage their finances and chores?"

Competitive Analysis

We conducted a competitive analysis to understand the existing solutions in the market.

Market Solutions:

  • We analyzed several existing apps and platforms aimed at shared living arrangements (e.g., Splitwise, Roomie, and others).

  • Most apps primarily focused on either financial management or basic task coordination but lacked a comprehensive approach to addressing all aspects of shared living.

  • We wanted to emphasize shared understanding.

User Research

Our user research involved interviews with 10 interviewees who were undergraduate UCI students that shared a living space with other people which provided us with invaluable insights into the daily lives, preferences, and frustrations of college students managing shared living spaces.

1. Those who established ground rules early on in their living arrangements found it easier to maintain their responsibilities.

2. Participants expressed reluctance to address upfront their expectations regarding chores, financial reimbursements, and noise levels with their roommates.

3. Users shared that they were comfortable sharing their schedules with their roommates to notify them of their general whereabouts.

Affinity Diagram

By mapping our findings, we gained a clear view of the key pain points faced by our target audience.

This helped us prioritize design solutions that addressed these issues.

Scenario Task Flows

Direct User Quotes

“I love my roommates, but since I feel like I’m a friend more than a roommate, I feel a little lame bringing up the chores and finances, especially since I’m a generally non-confrontational person. It would help.”

— Interview Participant

“This app would be especially useful during the beginnings of moving in, when everyone isn’t as familiar or comfortable with each other at the start… it’s a great jumping off point. I would use it during move in weeks.”

— Interview Participant

“I feel bad because I’m the only one who’s out of the house the most, so I feel bad that I might not be contributing to chores as much as the others. I would love to have a way to be notified about something like that.”

— Interview Participant

User Personas

User Persona #1

Main Insight: Vicky’s persona reflects struggles with shared expenses, reimbursement delays, and apartment organization challenges.

  1. Key Traits: Proactive, responsible, and a problem-solver seeking technology-driven solutions.

  2. App Features: Expense tracking, automated reimbursement, and tools for efficient apartment management.

  3. Outcome: Alleviates frustrations and improves Vicky’s experience managing shared living arrangements.

User Persona #2

Main Insight: Dean’s persona reflects frustrations with misalignment on shared spaces and the need to constantly remind roommates about cleanliness.

  1. Root Cause: Discrepancies in expectations arise from differing lifestyle habits and choices.

  2. App Features: Clear communication tools, cleaning schedules, and chore management systems.

  3. Outcome: A structured approach reduces frustration and fosters a harmonious living environment.

Sketches & Storyboards

The research findings were synthesized using affinity diagrams to organize and categorize collected data, revealing patterns and themes. These insights guided the design direction and feature prioritization based on user needs. The design process involved creating wireframes and prototypes at different fidelity levels seen here!

Storyboard

Mid Fidelity

Low Fidelity

Page Flow of Routeam

Intuitive Flow:

The page flow visually represents the intuitive structure and navigation we designed to streamline household management.

Home Screen: Access Settings, Finances, Chores, and Notifications.

1. Settings: Customize roles, adjust preferences, and edit ground rules.

2. Finances: Manage payments, budgeting, and shopping lists.

3. Chores: Add, assign, and track tasks with flexible options.

What I Prioritized:

Clear Pathways: Guides users through decisions, ensuring efficient household management.

My Design Philosophy: Simplifying complex tasks while offering flexibility for diverse needs.

Being Data-Driven: Scenario task flows informed feature accessibility and real-life use cases.

Prototyping: Sketches, storyboards, and wireframes helped refine the user journey and design throughout the entire process.

Consolidated Screen Flow

Final Prototype

Throughout the quarter, our team followed a user-centered design process, using personas, storyboards, and prototypes to address user needs.

Through continuous iteration and refinement, we developed a final prototype that aligns with the core needs and preferences of our target audience.

  • Created multiple prototypes with increasing fidelity to refine features.

  • Continuously iterated based on user feedback and insights.

  • Delivered a final prototype that effectively meets user needs and preferences.

Final Prototype Evaluations

  • Issue 1

    During testing, it became evident that users often overlooked the 'Skip for Now' options within the app. This oversight led to frustration among users who preferred to defer certain tasks or decisions to a later time.

    Impact: The lack of visibility for these options could discourage users from engaging further with the app, especially if they feel compelled to make decisions or perform tasks they are not ready for.

  • Issue 2

    Users reported feeling overwhelmed by the amount of information presented on the 'Finances' and 'Chores' screens. The high information density led to cognitive overload, making it difficult for users to quickly grasp the information or decide on the next steps.

    Impact: This overload could significantly reduce the efficiency of user interactions with the app, potentially leading to disuse if the users find it too cumbersome to navigate.

  • Issue 3

    Feedback indicated confusion regarding how rules and agreements are shared and communicated among roommates within the app. Users were unsure of the mechanism through which these rules were established and disseminated.

    Impact: The lack of a clear rule-sharing mechanism could undermine the app's goal of facilitating collaboration and shared responsibility, as it may hinder effective communication and agreement on household norms.

  • Issue 4

    Some users found certain icons within the app to be non-intuitive, leading to a learning curve where they had to deduce the icons' meanings through trial and error.

    Impact: While not a significant barrier to using the app, inconsistent iconography could slow down the initial user experience and lead to minor frustrations as users familiarize themselves with the interface.

  • Issue 5

    The notifications page was critiqued for not clearly differentiating the urgency of various notifications. This ambiguity could make it challenging for users to immediately identify which notifications require prompt attention.

    Impact: Although this issue is unlikely to prevent users from reading and responding to notifications, it may lead to less efficient management of tasks and communications within the app.

Here’s what I learned!

  • This project showcased not only my design process and problem-solving skills but also underscored the collaborative nature of UX design for me! Through close collaboration with my team, we delved into user research, prototyping, and iterative design to create a solution tailored to the needs of our target demographic. Our team had a lot of ideas of where to take this app, so we learned how to communicate our ideas, schedule meetings to work on deliverables, and manage our time efficiently. Being mindful of what we needed to accomplish instead of what we wanted to accomplish helped us keep our goals in mind. By mapping out our priorities from the outset, we were able to maintain focus and successfully bring our app to completion.

  • Throughout this process, I gained proficiency in conducting user interviews, a cornerstone of user-centered design, which provided me with invaluable firsthand insights into user needs, preferences, and pain points. Collaborating within a team setting was another pivotal aspect of my learning journey. Working alongside fellow designers, I discovered the power of collective ideation, leveraging diverse perspectives to fuel creativity and innovation. Due to the shorter time limit we had as well as having other academic commitments, we had to keep in mind what features we wanted to prioritize, and what we may not have had time to do, like gamifying the chores feature as a reward for a completed task. We pivoted from a lot of ideas and took a while to hone in on our main features. I became adept at implementing design changes based on user feedback and iterative testing. Each iteration served as a stepping stone towards refining the user experience, a testament to the iterative nature of the design process.

  • I had a great experience working with my group and I found that I worked well under the deadlines that the professors gave me. Out of my entire team, I had the most experience with Figma and was able to lead the team’s design process. It came in handy to have experience in design software, and I gained more by being able to teach it to others. I do wish that we had a larger audience to conduct a survey to gain statistics to base our work off of, instead of having to conduct more personal interviews just to gain some experience in doing statistical analysis. However, we were still able to gain valuable information from our research. My main takeaway from this entire project was solidifying my knowledge of a structured design process, communicating ideas and most importantly, working with a team.

Thank you for checking out Routeam !