Navigating Hope: Turning Experience Into Design
A case study showing how lived experience became a blueprint for a mobile-first tool designed to help people in crisis find accurate, up-to-date support. The project is currently at prototype stage, awaiting investment to move into full development.
Where It Began
For months, I lived without stable housing. This was not through any fault of my own, but the reality of a housing crisis that shut me out of secure accommodation. Rough sleeping, couch surfing, and even nights in a shed, all while finishing my degree in Design and Visual Communications.
When I needed help, the information was scattered, outdated, and unreliable. One number was disconnected, another rang out, the next sent me in circles. The issue was not that support did not exist. It was that finding it was harder than it should have been.
The impact is not just logistical, it is cognitive. When you are exhausted, unsafe, and running on low battery, you do not have the bandwidth for vague instructions or multi-step research. You need a clear next move that works on the first try.
That lived reality became the product lens. Navigating Hope is built for the moment people are most likely to abandon the search, not because they do not want help, but because the system has made help feel inaccessible.
Research shows that 61% of people stop using services after one bad experience. That is not a motivation problem. It is a systems problem.
What the Research Revealed
Western Australia saw a 39% increase in requests for homelessness assistance in 2022. Behind those numbers are families locked out of rentals, young people leaving state care, survivors of violence, and older adults forced into unsafe conditions.
I immersed myself in reports, spoke with community workers, and leaned on my lived perspective. The same story kept surfacing: people arrive at a service only to learn it closed weeks earlier, or walk kilometres because they cannot confirm if a food service is still running.
That failure is not small. It breaks trust and it wastes effort. In crisis conditions, one dead end can be enough for someone to stop reaching out entirely. So the product strategy had to prioritise reliability over novelty.
Strategically, the insight is simple: if information fails, the pathway fails. So the product needs a trust mechanism, not just a directory.
That means designing for verification, update cadence, and clarity on eligibility, not just UI polish. A pretty interface that points to closed services is still harm.
Clarifying the Problem
Everything I learned pointed to the same issue: services exist, but people cannot reliably reach them when it matters. Directories, PDFs, and word of mouth all break down under stress. The design challenge was not to add another list. It was to create a single, trusted path to help.
In product terms, the problem is friction plus uncertainty. People are forced to interpret service language, guess eligibility, and take risks on whether something is open. That is a decision tax applied to people who already have the least capacity to pay it.
That set the product bar: current information people can believe, plain language instead of service jargon, and a flow that works quickly on a phone in the real world. If it does not reduce confusion and decision time, it does not ship.
of providers were forced to close their front doors, leaving many people without access to critical support services nationwide.
of providers were unable to answer calls during operating hours, leaving people in crisis without help when needed most.
of providers could not respond to emails, delaying housing referrals and urgent requests. This is system-level friction.
Listening Before Designing
Before any screens, I spoke with people who had lived experience of homelessness, along with community workers and support staff. I asked how they look for help, what slows them down, and what would actually make it easier.
One participant put it plainly: "Do not make me feel stupid for not knowing the words. Just show me food if I am hungry."
The patterns were consistent: people search by need rather than service names, trust increases when they can see how recently information was updated, and directions only help if they show whether something is open and who it is for. Those insights drove the IA, the labels, and the trust cues.
This was also a trauma-informed design problem. The research approach avoided interrogation, avoided forcing disclosure, and focused on practical barriers. The goal was to translate lived experience into product requirements without turning people into case studies.
The output was a clear set of UX priorities: reduce decision time, reduce jargon, increase visibility of service status, and make the next step obvious for someone operating under stress.
Brand Identity
Navigating Hope needed an identity that builds trust fast and holds up in stressful, real-world conditions. The brand system is designed for clarity, legibility, and accessibility, with decisions that support the product strategy rather than decorate it.
This is a functional brand, not a mood board. Every element has a job: reduce confusion, support navigation, and keep people oriented when they are overwhelmed. If a visual choice does not improve comprehension, it is a liability.
Colour - Green (#A8CF3D) signals safety and progress; deep navy (#172E52) anchors the system with stability; red (#C81113) is reserved for urgent cues such as location pins; neutrals support balance and contrast.
Typography - Headings use Rubik One for quick recognition. Body and interface copy uses Montserrat for familiarity and legibility across devices.
Voice - Plain, direct, need-first. Labels prioritise what matters in the moment: food tonight, somewhere to sleep, medical help.
Accessibility - Colour is never the only signal. Icons are paired with labels, type scales are generous, and tap targets are sized for real-world use under stress.
The goal is brand consistency across partners, print, and digital. It should look credible in a government office, a library, or a shelter wall without needing explanation.
Turning Research Into Early Prototypes
The first design concepts were built around a clear principle: support should be found in as few steps as possible. Early wireframes tested a simple flow: start with the question "What do you need right now?" and guide people quickly toward food, shelter, medical help, or hygiene services.
Instead of building a feature-heavy product, the focus was on operational clarity. This means predictable navigation, large tap areas, high-contrast layouts, and labels that match how people speak, not how organisations write.
The goal was not feature sprawl. It was performance under pressure: plain language over jargon, low cognitive load, and UI that still works when someone is tired, stressed, and using a phone one-handed in a public space.
Early prototyping also tested practical realities like low-bandwidth states and imperfect GPS. The product has to degrade gracefully. If the map fails, the list view must still deliver outcomes.
Audience Testing
Testing focused on two core user journeys in the high-fidelity prototype: finding food and finding shelter. Community service workers and people with lived experience trialled the flows, then provided feedback through observation and short surveys.
Even at prototype stage, changes like clearer labels and visible "last updated" signals increased trust and reduced confusion. That is real traction, not theory.
Sessions were run as simple, scenario-based tasks because that is how people actually use this kind of tool. Participants were asked to find support as if they needed it right now, on a phone, under pressure. I watched where hesitation showed up, which labels caused second-guessing, and where people expected the next step to be. The goal was not to impress anyone with design, it was to stress test the pathway and expose friction fast.
The clearest insight was that trust is a product feature, not a nice-to-have. People wanted instant clarity on whether a service was open, who it was for, and how recently the info was confirmed. Where that context was missing, confidence dropped and users started backtracking. That feedback directly shaped the next iteration priorities: stronger “open now” cues, clearer eligibility notes, and a tighter verification approach so the app can scale without turning into another outdated directory.
The testing also reinforced a strategic truth: users do not want to learn a system. They want the system to adapt to them. That is why the navigation is need-led and why service detail screens prioritise the answers people are actually looking for.
Iterating on Feedback
Iteration was not about adding more. It was about tightening the pathway. Jargon was swapped for human language. Buttons were shifted lower for one-handed use. A list view became the default for low-bandwidth states. A short onboarding tutorial was added, shown once, but always available later through Help.
The key decision was to remove uncertainty wherever possible. If a screen makes users guess, it fails. The iteration work prioritised what people need to know first: is it open, can I use it, how do I get there, and what do I need to bring.
A lot of “nice ideas” got cut. Optional complexity was stripped back in favour of repeatable patterns. Navigation stays consistent across categories so users are not re-learning the interface every time they switch from food to shelter to medical.
Every change came from what people told me during testing. The outcome is a cleaner decision flow with fewer points where people freeze or bounce.
The next iteration phase is about system readiness: strengthening the verification model, designing partner workflows for updates, and defining the minimum data standard so the directory stays trustworthy at scale.
From Concept to Community
Alongside the prototype, I developed outreach concepts to show how Navigating Hope could meet people where they are: food vans, shelters, libraries, and transport hubs. Posters and cards with QR codes were mocked up as examples of how information could be shared quickly, with service providers positioned as key distribution partners once built.
This matters because not everyone is searching online. People often find support through physical environments and frontline relationships. The outreach strategy treats those locations as product touchpoints, not an afterthought.
I also built the "Day in Their Shoes" campaign as a concept, pairing interactive posters with lived-experience narratives to show how empathy can drive awareness and support. The strategy is simple: reduce friction, make the next step obvious, and keep the message consistent.
The commercial logic is clean: partner-led distribution increases reach, reduces acquisition costs, and builds trust through credible channels. That is how this moves from a prototype to a real-world service.
Branding Collateral
Practical assets designed for frontline distribution and fast understanding. The objective is consistency and scanability so the message stays steady across partners and environments.
These assets are built to do one job: help people take the next step quickly. That means readable typography at arm’s length, clear hierarchy, and minimal copy that still answers the real questions.
Collateral also plays a governance role. When partners share consistent messaging, the product feels legitimate. It reduces confusion and creates a unified entry point regardless of where someone first discovers the app.
Business Cards
Compact card with logo, tagline, and QR. Built for service providers and volunteers to hand over fast.
Tri-fold Brochure
Outside: mission and how it works. Inside: features, eligibility notes, and a central QR for quick access.
A5 Flyers
Front: what it is for. Back: key services, simple steps, and QR. Built for low cognitive load.
Future-ready consideration: these formats can be templated for multiple regions and translated without breaking the hierarchy. That supports scale without reinventing the wheel.
Merchandise
Wearables and accessories that turn the mission into everyday visibility. The play is simple: create conversation starters that extend the brand beyond the screen.
Merchandise here is not about chasing revenue for the sake of it. It is about visibility, volunteer identity, and normalising the conversation in everyday spaces. People ask questions when they see it, and that creates reach without paid ads.
The direction also supports partnership activation. When organisations run events, consistent branded materials improve trust and make the project feel established, not experimental.
Tote Bag
Durable carry-all designed for daily use while keeping the message visible in public spaces.
Supporter Tees
Volunteer-friendly shirts that make the project visible at events and in community settings.
Branded Mugs
Everyday items that turn routine moments into awareness touchpoints for partners and hubs.
If this moves beyond concept, the ethical bar stays high: no exploitative messaging, no poverty porn, and clear rules on where profits go if fundraising is introduced.
Scalability and the Future Vision
Navigating Hope was never designed as a static project. It was built with growth in mind. Its modular architecture means it can expand to new regions, scale with changing needs, and evolve alongside the communities it serves.
Scalability is not just adding more listings. It is operational governance: who verifies data, how updates are submitted, what gets flagged, and how outdated information is retired. Without that, scale becomes risk.
With the right investment and partnerships, the prototype can move into full development and become a permanent tool for crisis navigation. The strategy is partnerships with non-profits, local governments, and community organisations. Not just survival in crisis, but long-term empowerment.
The next phase roadmap is straightforward: build the verification workflow, implement partner dashboards for updates, establish data standards, and launch a controlled pilot region before expanding.
What I Learned
Navigating Hope taught me that design is proven in practice, not in presentations. Lived experience gave the urgency. Research gave the direction. Testing kept me honest. Iteration made it usable.
It also reinforced that good intentions do not protect people. Only systems do. If a tool claims to help but sends users into dead ends, it is part of the problem. That mindset raised the bar on what “done” means for this project.
The biggest lesson: simplicity is not a lack of ambition. It is the hardest, most human design choice. This started as a university brief, but it became a blueprint for a real product that can restore clarity, dignity, and connection when people need it most.
Going forward, the priority is execution with integrity: build the trust model properly, pilot it with the right partners, and make sure the product earns credibility through outcomes, not claims.
Let's Build This Together
Navigating Hope is ready to move from prototype to reality. With the right partners, investment, and community backing, this can become the tool that ensures no one has to face crisis alone.
Get Involved Today
Social Media Examples
A three-post set covering awareness, empathy, and action to build understanding and drive engagement.
Social content is positioned as an education and partnership channel, not just marketing. The aim is to shift public understanding, reinforce credibility, and give community organisations assets they can confidently share.
The structure is intentional: awareness builds context, empathy humanises the issue, and action creates a clear next step. This keeps messaging consistent while still allowing variation in storytelling and campaigns.
Awareness
Statistic-led tile to surface the scale of the issue and shift public understanding.
Empathy
Lived-experience message that humanises the problem and invites reflection.
Action
Direct callout: homelessness does not discriminate. No age, no gender, no exemptions.
In rollout, this becomes a partner pack: pre-written captions, accessible alt text guidance, and a consistent CTA that points back to the same trusted entry point.