Team

Angelica Anderson

UI/UX Designer

Gia Nguyen

UI/UX Designer

Atticus Wong

Developer

Tarun Rawat

Developer

Design Process

Problem

Solutions

Reflection

User Research

Understanding the Challenge

Context: Fourth & Hope provides services for individuals facing housing insecurity, but it is challenging for them to track service usage and client demographics.

SWOT Analysis

Interview with Fourth & Hope Staff

No service tracking

Fragmented workflow

No measurable outcomes for grants

Poor communication

Karla

“We support more than just overnight guests, but there’s no reliable way to log or document those daily services.”

“Each team uses their own system or spreadsheet, there’s no unified way to manage client information.”

“When applying for grants, we struggle to show the impact of our services since we don’t track it.”

“Without a shared system, there is confusion on who’s waiting or when they arrived”

Problem Statement

Fourth & Hope lacks a unified system for managing client services, leading to inefficiencies in daily operations, difficulty measuring outcomes, and challenges in securing funding.

Design Challenge

How might we create a centralized platform that improves visibility across departments?

How might we help staff document services quickly and accurately?

How might we provide measurable outcomes that support funding efforts?

Ideation - Low-Fidelity Designs

Mid-Fidelity Designs

Solution

A centralized CRM that:

1. Combines service tracking, client profiles, and reporting tools
2. Improves communication across teams
3. Supports data collection for measurable outcomes

Reflection

• Limited time to design for both mobile and web�
• Difficulty generating outcome reports via Gemini for grant applications�
• Complexities in structuring data and visual hierarchy for efficiency

• Highly available systems with well-defined API endpoints will improve data security and flow

​

• Aligning on components and design systems early prevents inconsistencies

​

• User research directly shaped our design decisions and validated features

Challenges

Takeaways

Reflection

Next Steps

• Develop a mobile-compatible app with a dedicated case management microservice�
• Migrate the platform’s backend to a SQL database�
• Finalize high-fidelity mobile wireframes�
• Prototype remaining features like Messages (for internal communication) and Announcements (for system-wide notifications)

Thanks!

Do you have any questions or feedback?

Devpost Site | Figma Project