In order to better understand our target population and
the issues they faced in regards to subletting, we conducted
interviews on 3 different people. We found that:
1. Finding a sublet is difficult as there is no centralized platform for this.
2. It is hard to avoid scams as there is no way to verify the validity of what is posted.
3. Subletting is anxiety inducing for a variety of different reasons.
Our interview notes can be read
here.
After collecting data from the interviews, my team and I
constructed an affinity diagram to synthesize our findings.
We began by noting general findings and comments made by our participants
during our contextual inquiries
on yellow post-its. We grouped them into categories labeled on
purple post-its. From there, we were able to group those into
our final groups labeled on blue post-its.
Affinity diagramming gave us valulable insights and allowed us
to refine our problem statement:
In order to brainstorm different approaches to solving our problem,
each team member drew out a different storyboard. Below is the idea we
moved forward with: a Tinder-like interface which gamifies
the subletting experience through swiping. All 5 storyboards
can be found here.
We investigated design solutions that can be viewed as
competing alternatives to our own by describing what these
solutions do well and where they are deficient for solving
our users’ problem.
We concluded that subletting can be divided into 3 categories:
We conducted a user study using the Wizard of Oz technique.
A random participant tested out our lo-fi prototype as someone
looking for a sublet. We aimed to test the effectiveness,
straightforwardness, and ease of our model. Read more about
our user study and takeaways here.
We developed high-fidelity prototypes incorporating feedback
from user testing. These prototypes included more detailed visual
elements and functionality, providing a clearer representation of the final product.
We selected a participant who had already gone through the
process of finding a sublet to test out our prototype. We gave
them a scenario, and they looked for an appartment on our
prototype which corresponded to it. Read more about our user
study and takeaways here,
and click on the prototype below to explore more screens.
After several stages, we were ready to code our final design solution! We used HTML, CSS, JavaScript, Python (Flask), React, and SQL. Download Lettr here, and watch our team video below!