Horizon
A kiosk application developed to coordinate services in homeless shelters.
Muhammad Bilal - Team Leader
Connor Friden - Researcher/Designer
Seb Gonzalez - Researcher/Designer
About
At the beginning of the Fall 2019 semester, teams were tasked with brainstorming project ideas to eventually prototype and create an application. Our team leader, Muhammad, came up with creating a kiosk interface that would allow the homeless to gain access to services that they need. My role was that of a designer and researcher. I took notes during interviews, created prototype mockups, and gave a pitch for our project during our first sprint.
Horizon is a kiosk application that will allow the homeless to acquire services that will address their basic needs for food, shelter, and medical attention. Our team utilized the Lean UX process as a guideline for our project, and we had to keep up with a schedule and meet specific deadlines. Lean UX ensured that our small team was highly collaborative and very focused on the problems at hand. Our project was broken up into two “Sprints” and two “Design 0” weeks at the beginning of each sprint. The Lean UX process involved our team creating prototypes that would constantly change based on user testing and interviews feedback.
The Process
PRODUCT PROBLEM STATEMENT (SPRINT 1)
We started the process by creating a product problem statement. In this statement, we determined the current state of the market, the opportunities we intend to exploit, and our strategy to market the application.
ASSUMPTIONS (SPRINT 1)
We started by filling out our assumption sheets individually, and then we came together to create a group assumption sheet. Here are some of our assumptions:
- Initial users will be social workers and volunteers
- Kiosks are located at shelters, religious organizations, libraries, college/university care centers.
- Revenue by leasing application to private-run organizations, as well as sponsors for ads.
AFFINITY MAPPING (SPRINT 1)
The next stage in our project involved creating affinity maps that would allow us to discover any patterns based on our assumptions. The maps allowed us to understand the mindset of each team member moving forward. Through affinity mapping, we narrowed down four basic needs for our primary user: Food, Showers, Shelter, and Medical.
PRODUCT BACKLOG/HYPOTHESIS TABLE (SPRINT 1)
As a team, we created a product backlog and multiple hypothesis statements that we knew would change as we progressed through the project. Based on our hypothesis statements, we came up with business outcomes that would get our product out into the market and make it a viable business. Our product backlog underwent many changes throughout Sprint 1 and was finalized during Sprint 2. Once we conducted interviews and did more research, we could complete the backlog and remove anything that didn’t belong.
PROTO PERSONAS (SPRINT 1/SPRINT 2)
With the information gathered from our assumption sheets, affinity maps, and product backlog, we came up with three proto personas for our kiosk.
Borris and Rachel were the only personas that experienced a change in Sprint 2. Borris, our primary persona, simply had his level of education changed, and his primary goal was to have an education rather than a job and an education. Rachel experienced the most change. Rachel’s title went from “Social Worker” to “Case Manager” due to our interview with Must Ministries. Her primary obstacle was changed from outdated government software to the large packets of paper that case managers have to manage.
PROTOTYPES (SPRINT 1)
Next, we have our prototypes. We started with diagraming our key path and determining how our personas would interact with the kiosk.
PAPER FIDELITY
After diagraming our key path, we then drew some paper prototypes. While very basic, they laid out the foundation on how we want our kiosk to appear aesthetically.
LOW FIDELITY
Our paper prototypes led to these low-fidelity mockups, which brought us even closer to a usable prototype.
MEDIUM FIDELITY
Our low-fidelity mock-ups eventually led us to our medium-fidelity prototype, which underwent many changes in both sprints. The images to the left represent the final state of our prototype at the end of Sprint 1.
PROTOTYPES HIGH FIDELITY (SPRINT 2)
Our final prototype was a culmination of the information we gathered in all of our interviews and user testing. Our prototype did not undergo any drastic changes from Sprint 1 to Sprint 2, but the small changes we made were not without much debate and discussion. Here is the current and final state of our prototype:
SECONDARY PERSONA SCREEN
DIAGRAM
INTERVIEWS
The interviews we conducted were instrumental in affecting the decisions we made throughout our project. Before we ran our first interview, we knew a lot less about our project than we had previously thought. We realized that we were incorrect in many of our assumptions about both our primary and secondary personas. Our first interview with CARE Services at Kennesaw State may have been our only interview in Sprint 1, but the information was helpful.
INTERVIEW: CARE CENTER
Our interview with CARE Services was informative. We gathered invaluable information about how CARE services operate at KSU. Our interviewee also gave us feedback by stating that our kiosk would be a valuable asset on a college campus. The kiosk would be handy to have after-hours when CARE employees aren’t around. While the information we gathered primarily pertained to students, we still needed to understand the struggles of the homeless regardless of demographic.
INTERVIEW: CARE CENTER PART 2
We met with one of the directors of CARE Services at Kennesaw State. During this interview, we gained information about the intake process for students and the services they can access. We learned about CARE’s connections with other organizations. We also received feedback about our prototype and some features that we should consider. We knew that our kiosk would need to be explicit in determining the cost of locations, if any, and specifying whether the places are safe to avoid liability. Other features and recommendations the director provided caused debate amongst our team about what was most realistic for us to include.
INTERVIEW: MUST MINISTRIES
Our second and perhaps most important interview of the entire project was with Must Ministries. Using the information we gained from a case manager, we altered our prototype and corrected many of our assumptions. We learned that most of the homeless are literate and many have mobile devices at their disposal. As a result, we replaced laundry with medical services as a priority for our primary personas. Our secondary persona, Rachel Evans, also had her role change from social worker to the case manager due to this interview.
MY CONTRIBUTION
- I took notes during user testing and interviews.
- I created the secondary persona pages and intake form.
- I Filled out an individual assumption sheet.
- I helped organize the product backlog.
- I helped finalize the product problem statement.
- I created paper prototypes.
- I created low-fidelity mockups.
- I helped create an affinity map.
- I created potential workshops that would be used in the prototype.
- I created a script and PowerPoint for the Sprint 1 presentation.
- I presented the state of our project at the end of Sprint 1.
FINAL THOUGHTS
I was nervous going into this semester, but my team members were helpful throughout this project. I am proud of what we accomplished during the semester. I am also proud of our project itself. I knew it would be ambitious and challenging, but I feel good about what we created. I am a better person for working on an app that helps people. The project has opened my eyes to the situation of the homeless. I hope that someday someone will create a kiosk similar to ours. It’s been challenging. The Lean UX process has been intense, and I am a better Interaction Designer because of it.