top of page

ScavengerShip 

Designing for People
Responsive and Local 

 

Date

August 2023-October 2023

Skills Used 

- Interviewing 

- Primary research 

- CoDesign 

- Wire Framing 

- Ideating 

- Storyboards 

​

​

Team 

Kara Pearson 

Dean Carroll 

Joe Maddux

​

​

Brief

 Engage in research in order to determine a community that has a problem that can be solved. Focus on your team’s co-design activities, activity outcomes, design insights, and project roadmap accompanied by a design rationale. 

​

Role

Co-Team Lead  

​

​

Personal Contribution:

I helped facilitate the co-design workshop and actively contributed to the ideation process. This involved the development of wireframing designs and the implementation of coding for the interactive prototype. 

Finding a Campus Problem

Before identifying a problem space, we aimed to explore various communities in the area, seeking one with a solvable problem. Our selection was based on personal experiences, interviews, and observations, emphasizing an unbiased approach to identifying the community's problem space for our project.


We determined the following communities. We spoke to our friends that were a part of these groups and attempted to find any problems, but there weren’t any relevant or tangible enough for us to create our project.

 

 

 

 

 

 

 

After speaking to some of these communities, we decided to take a walk around campus to see if we could observe any issues… On Snapchat, we also noticed multiple people posting inquiring about items they’ve lost or found. We decided to dig into this issue.

Screenshot 2023-11-28 at 11.02.54 AM.png
Screenshot 2023-11-28 at 11.02.48 AM.png

Primary Interviewing and Observation

Our group made a trip to the lost and found desk at WALC to speak with an employee who deals with the lost and found. Our goal was to understand the lost and found system. She said that around 40% of items go unclaimed and that items stay at lost and found 2-4 weeks before being sent to the surplus center.

​

​

​

​

​

​

​

​

 

The Purdue Surplus Store process involves items moving from individual lost and founds to a central location, where they're held for six weeks before being placed on store shelves. Despite this process, there's no online system. In interviews with Purdue students, it became evident that many were unaware of the central lost and found or the existence of a separate lost and found for expensive items. Some students expressed frustration, giving up on finding lost items, while others shared stories of encountering their lost items with others. Additionally, the idea of people posting lost items on Snapchat stories caught the team's attention for future consideration.

​

​

​

​

​

​

​

​

​

Ultimately, from these interviews and observation we concluded that there is a lack of knowledge and information for students on lost items, especially on such a large campus.
 

Screenshot 2023-11-28 at 11.11.19 AM.png
Screenshot 2023-11-28 at 11.11.30 AM.png
Screenshot 2023-11-28 at 11.14.51 AM.png

Storyboarding and Sketching 

We created these initial storyboards and sketches to help assist with our co-designs, mainly to get a starting point for our co-designers to critique and evaluate.

​
 

Screenshot 2023-11-28 at 11.21.43 AM.png
Screenshot 2023-11-28 at 11.21.32 AM.png

CoDesign 

​

CoDesign Goals: 

- Determine one’s mental and physical processes after losing an item. 

- Determine the viability/layout of a potential website and what should be included on it. 

​

CoDesign with Students

We first wanted to find out what a person would do if they lost something, and asked to be walked through this process. If they hadn’t lost something, we asked them to assume what they would do. 

Though our questions that we asked the students we found out that most students often just give up when losing their items, even if they really want them back, it almost seems pointless to them.

 

Next we had them  described the following item. We did this so we could understand what features would be distinctive for a website search.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

From the item description activity we found that item and color is the most important, as well as random distinctive features, like the dent. We were surprised that the brand wasn’t as important.

​

CoDesign with Front Desk Employee

We then wanted to understand the interaction between the front-desk employee and the student who had lost an item. We asked them to walk us through a typical process.

​

Her Process:
1. Student comes up to me
2. Tell them to look around in the pile of items
3. If they can’t find it they usually walk away … sometimes they inquire more
4. Ask them about the item
5. If it’s an expensive item - check clipboard/paperwork
6. If I have it I ask for more information (when they lost it, where, any key             features)

​

From her process we found that students are quick to give up when looking for an item, even if they appear to look stressed or worried.

We also wanted the Front Desk Employee to participate in the item description activity, just to make sure their descriptions would align with that of the students.

​

​

​

​

​

​

 

 

 

From her description, we were glad to hear that it aligned with that of the students. We found that using descriptors like color, item, and brand would be helpful on our website.

 

 

CoDesign with Lost and Found Coordinator

The lost and found coordinator wasn't very interested in our idea. She said she had too much work and didn't want to switch to a new system. Despite this, she walked us through how she handles lost and found calls and joined our item description activity. To make things easier for her, we decided that after two weeks in the front desk lost and found, the item's location would automatically update on the Purdue Surplus store, helping students without causing extra work for the coordinator.

​

Co-Design Conclusions: 

Our co-designs helped us understand user preferences and improve the lost and found workflow. We learned valuable lessons about effective co-design methods. Initially, a ranking activity proved unhelpful, so we shifted to having participants describe how they would label lost items, providing crucial insights into important website characteristics. This information guided us in creating an updated sketch, which was then transformed into a wireframe design.
 

Screenshot 2023-11-28 at 11.28.59 AM.png
Screenshot 2023-11-28 at 11.39.54 AM.png
Screenshot 2023-11-28 at 11.28.59 AM.png

Wireframes 

Screenshot 2023-11-28 at 11.48.26 AM.png

Hi Fidelity & Interactivity

Screenshot 2023-11-28 at 11.50.26 AM.png
Screenshot 2023-11-28 at 11.50.31 AM.png
Screenshot 2023-11-28 at 11.50.37 AM.png

User Testing 

We decided to do some final user testing in the form of usability testing with our interactive website. The goal is to make sure users can easily navigate the website and would be able to easily claim an item. We made a script of tasks to ask the testers, such as finding an item, trying to claim an item, and applying filters.

​

User Testing Script:
- Scroll through the lost items and find the Duck
- Claim the “Nice” Mug for yourself
- Filter to only show the Water Bottles
- Undo this Filter
- Navigate to the Found tab
- Find what day the keys were found
- Navigate back to the Home Page

​

User Testing Results:
- It’s not immediately clear that the home page is the home page.
- Filters work and as the users expected
- The claim system can be completed quickly

- The only change we made following user testing was to add a link to the homepage on the found items page, so you can quickly get back to the grid of lost items. 

Next Steps

If we were to continue work on this project or pass it off there are a few things that should come next:

  • Conduct further usability testing and iterate on our designs

  • Work with stakeholders to design input user process

Personal Contribution

I helped facilitate the co-design workshop and actively contributed to the ideation process. This involved the development of wireframing designs and the implementation of coding for the interactive prototype. 

bottom of page