Case Study 04

Locus

Study smarter, together. Locus helps UT students find and rate study spots that actually fit their needs, from noise level to outlet availability, instead of guessing and showing up disappointed.

Role
Product Designer, TPEO
Tools
Figma, Maze
Timeline
6 Agile sprint cycles
Outcome
Shipped to a 250 user beta

Problem

"How might we help students navigate campus life with more confidence by guiding them toward environments that fit their personal needs and preferences?"

The why

Before a single screen was designed, student interviews surfaced the same frustration: no way to know whether a study spot would actually work, noise, seating, outlets, before showing up. That gap between walking somewhere and knowing it would work is what Locus set out to close.

Who I designed for

M
Megan, 28

The overwhelmed night owl

Studies late, needs to know what is open and what the vibe will be before she leaves her apartment.

A
Adam, 19

Group coordination chaos

Constantly texting friends back and forth to find a shared study spot that works for everyone.

Mapping the journey

Journey mapping research process, sticky note flow from gauging time to sitting down to study

Hypothesis

If students could see noise, lighting, seating and outlet availability before they left for a study spot, they'd stop wasting trips on ones that don't actually fit.

How AI shaped my process

AI → Problem exploration → Feature ideation → Prototype

With six sprint cycles and a hard beta deadline, AI helped me move faster through the exploration phase so more time could go toward testing with real students.

Study space discovery behaviors Feature possibilities Group coordination Edge cases Interaction models

AI helped me

Explore a wider range of possibilities and pressure test concepts before deciding what was actually worth building.

I decided based on

20 user interviews, what students told us they needed, and what the team prioritized as most feasible to ship.

Features from findings

Discovering spaces from preferences

Filter by noise, lighting, seating and outlets

Study circle tracking

See where friends are studying in real time

Rating spaces for the community

Crowdsourced reviews keep listings honest

Final screens

Scroll to see all seven →

Locus map and discovery screen, showing a selected study spot with friends nearby

Map view: a selected spot's card, with friends studying nearby surfaced right on the pin

Locus spot detail screen with photos, lighting, seating, noise level and reviews

Spot detail: photos, amenity tags and real reviews, all in one scroll

Locus rate a spot screen with noise, temperature, outlets, wifi, cleanliness and lighting categories

Rating a spot across six categories, each optional so partial ratings still count

Locus rating submitted confirmation screen

Confirmation after submitting: a clear thank-you, with an easy path to rate another spot

Locus focus session timer with pause and end session controls

A running focus session, with the timer surviving if you leave the app

Locus preferences screen with noise, lighting, outlets, temperature, seating, aesthetics and cleanliness rows

Preferences: every factor Locus uses to rank spots, in one place

Locus saved spots list

Saved spots, bookmarked in one tap from anywhere in the app

Prototype walkthrough

Discovering, filtering and saving a study spot in the live prototype

Results

250
students in the live beta
6
Agile sprint cycles shipped
20+
high fidelity iterations tested

What I learned

Key learnings

  • Fewer taps beat cleaner structure. The accordion-style preferences screen looked tidy, but switching to a flat checklist in later iterations cut friction without losing clarity.
  • Interview findings outperformed assumptions. Features built directly from the 20 interviews, like study circles, tested better than ideas the team carried in from day one.

What I would do differently

  • Test earlier, not just at the end. With six sprint cycles and a hard beta deadline, usability testing landed late; I'd pull it earlier next time.
  • Protect testing time when scope grows. Adding study circle tracking mid-build was the right call based on interview feedback, but I'd protect testing time for it better next round.

Let's talk

Designing something that could use a fresh set of eyes? I'd love to hear about it.

Currently looking for Summer 2027 product design internships.