( Context )
Napkin
( Duration )
2021 Fall - Present
( Role )
Founding Designer
prompt
"Design an experience for ArtCenter students to report facilities that need repair or maintenance to improve the upkeep of campus facilities."
challenge
Embarrassingly enough, as a student myself, I rarely report malfunctioning devices while working on campus. 😅
But guess what? Research shows that I'm in good company.
Given our tight schedules and looming deadlines, issue reporting is often perceived as a voluntary and time-consuming task. When we are facing device hiccups, many just simply switching to another device to keep the workflow going.

𝄪   Optional Action

𝄪   Cumbersome Process

𝄪   Competing Priorities

To ensure high user acquisition of an effective reporting system, how might we implement a compelling behavioral trigger that promotes proactive issue reporting while respecting students' time constraints and minimizing effort?
Problem context
I failed to record my Glaze experiments process very well.

Since the lockdown, I picked up a new hobby of experimenting with Ceramic Glazes. 🧪🔥
Each time I fire a piece, it's always a surprise to see the final texture that varies depending on the firing temperature and ingredient ratios. So I've been taking lots of photos and notes with an expectation to see my knowledge grow over time and to create a library of glaze recipes for future reference. But after a while, my motivation to keep track of these experiments was dying out.

Hypothesis

* Too many tools were involved - paper notes/ photos/ web links are scattered everywhere.
* High effort to archive and organize fragmented records.
* Lack of quick and delightful reviewing experience.

behavior analysis


When devices malfunction, students exhibit 2 different behavior patterns under the same ultimate goal - get their work done at max efficiency.
A - Report the issue ASAP
Noops user behavior pattern A

💡Insight:

When students are highly motivated to report, the reporting procedures need to be accessible and transparent, to ease the frictions and anxiety during the waiting periods.

B - Switch to Another Device
Noops user behavior pattern B

💡Insight:

When students feel reluctant to take the extra step, the reporting system needs to be more than a reporting portal. Additional benefits towards students' overall work efficiency is a strong motivation.

What if


Optimize their 'lab & device searching' experience

Put both scenarios together, it becomes apparent that device breakdown is just a small piece of the puzzle.
Students are experiencing tons of frustrations before & after encountering device hiccups - If the system incorporates additional touchpoints that smooths the whole journey, it will seamlessly blend into students' on-campus workflow as a productivity booster, thereby increase the system's user acquisition and reporting rates.

To uncover why seeking a lab and available devices to work with is a headache among students, I conducted 4 semi-structured interviews and received 36 completed surveys.
01.
Fluctuating Location Preference.

Students search for suitable labs and devices across different campuses based on their projects' changing needs. 85% of participants don't stick to one computer lab throughout the term.

02.
Restricted Lab Availability.

Computer labs often host classes with varying schedules that are hard to memorize. All the participants have experienced unexpected disruptions and were forced to relocate when a class arrives.

03.
Unclear Device Status.

Students can't discern a device's functionality before logging in. Previously reported devices aren't visibly marked, leaving them in the dark.

Addressing the struggles in lab & device searching.

Here's a flow chart picturing how the reporting system can bring dramatic value to students workflow.
By promptly reporting device issues, students receive immediate assistance—whether it's technical support with clear anticipation or instant suggestion on alternative workspace / device.

Prototype
Quick Iterations on Key Experiences

I started with grey boxes to test some of the core interactions with students and technicians.

Visual tweaks to enhance usability
Have a try! 👀