Josh Anderson

Information Architect

MSU People Finder App Prototype

The Challenge

How can Michigan State University students quickly locate people on campus and beyond? I conceptualized, tested, and iterated a mobile app concept that provided a solution.


First, I thought up a user scenario:

Jimmy leaves class one cold morning knowing he needs to finish some homework before his next class. His usual study spots – the Union and the library – are far away. Besides, the library is usually too crowded and the Union tends to be too loud for him to get anything done. Jimmy wants to return to his dorm to work at his desk, but he knows if his annoying roommate Mike is there, it will be even harder to do any work than it would be even at the Union or library. Jimmy doesn’t want to walk through the cold to his dorm to find out in person whether or not Mike is there. He also doesn’t want to call or text his roommate to find out where he is because that would be awkward. Instead, Jimmy opens up the MSU People Finder app to check Mike’s location. Thankfully, Mike is all the way across campus doing God knows what. Who cares, anyway? Jimmy starts heading home, smiling with the knowledge that he’ll be undistracted in his dorm.


With that story in mind, I began sketching my first ideas for the app’s interface.

Iteration 1

MSU People Finder I1-1 MSU People Finder I1-2

With only a few minutes to write out my thoughts, I envisioned a search bar with filtering options (by year, major) that would reveal a list of MSU students. Next to each of their names would be a large “Locate” button. Pressing that button would lead to an MSU campus map and a marker showing where the person was. Privacy-conscious users would also have the option to disable their location, as shown by the option next to the second person.

A peer review immediately after the creation of these sketches quickly convinced me that my app idea was too invasive. People wouldn’t want to feel as if they’re being tracked, which I agreed with. That revelation lead to my next iteration…

Iteration 2

MSU People Finder I2-2 MSU People Finder I2-3

Now, users would need to mutually add each other as friends before they could exchange information (similar to how Facebook operates). Users could only request the locations of those with whom they were friends.

Iteration 3

MSU People Finder I3

Iterations 1 and 2 were completed under a strict time limit (10 minutes, give or take). I was allowed to take my time on the third iteration, however. I drew every screen I would need to show a full interaction with the app. This included the home screen (with and without notifications), and a more realistic search progression.

User research

With my drawings, I had all I needed to conduct user research. I brought the drawings before a research participant, noted her interactions, and recreated them in a low-fidelity video…

Interaction with Paper Prototype

In the video, the questions I ask my research participant are left-aligned in white, and her answers are right-aligned in yellow.

The questions I asked guided my research participant down a path slightly different than the one laid out in my original scenario, but the general task (Can you find a specific person?) was the same.


Knowing from my research that my interface was straightforward and usable, I fired up my favorite browser-based prototyping software, Ninjamock, and adapted my drawings into clickable wireframes. That interactive prototype is still accessible, actually. (For the best experience, turn off the “links” option in the top right.)

MSU People Finder Wireframe 1 MSU People Finder Wireframe 2 MSU People Finder Wireframe 3

Interaction with Wireframe

Finally, I recreated my user research session in the wireframe version of my app.


While it was difficult to draw the first iterations of my app in such a brief amount of time, I was pleasantly surprised by how much I was able to design under pressure. The feedback I received immediately after my hasty first iteration proved especially valuable, and prevented me from spending a longer time drawing features of my app that were doomed to be cut. Thus, I gained a newfound appreciation for rapid prototyping.

I also learned the value of presenting user research results via video – even if that video is rough. By creating a brief but eventful video, I could illustrate my user’s interaction with my app in a concise (and maybe even entertaining) way.

I knew that Ninjamock was a quality tool before this project, but now I know that paper prototyping can also be an effective way to sketch, test, and refine my ideas. I have no plans for further developing the MSU People Finder app idea, but the process proved useful and educational nonetheless.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Recent Posts


Upcoming Speaking Dates

STC Rochester Webinar
June 27, 12-2PM EST
“Prompt Engineering”

More info coming soon.

LavaCon 2023
October 14-17, 2023
San Diego, CA
“Microcontent Pipeline to Chatbots and Voice Assistants”

Use microcontent to put your team in the driver’s seat to the next level of content publishing for intelligent chatbots. By now reality has revealed that ChatGPT is not ready to write our product documentation for us. With no control over what the publicly-trained models scrape from our websites and blogs and how it assimilates our documentation with other less-authoritative sources, we’re left to wonder where we go next. If we want reliable bots, we’ll need to train our own models and deploy them to our staff and our customers. Let us show you what we’ve learned so far.


My Spotify Playlists

Create a website or blog at