Campus Wayfinder

A Campus Map Kiosk System

Approach: Lean UX

Lean UX, a methodology that focuses on rapid, iterative design based on user feedback. Lean UX begins with assumptions, which are then validated through measurable testing and refined through continuous iteration.

Duration: 8 weeks.

Objectives:

  • Enhance user accessibility to bus schedules and routes.

  • Implement real-time tracking to improve reliability and trust.

  • Streamline the user interface for seamless navigation.

App Idea: A transit app designed to simplify bus navigation and provide real-time tracking for commuters.

Prototype Overview
The Wayfinder App is a user-friendly prototype redesigned campus navigation prototype tailored to meet the needs of students, faculty, and visitors at Kennesaw State University. With enhanced accessibility, real-time location tracking, and optimized route suggestions, this app makes navigating a busy college campus more efficient and stress-free.

Design Process

Sprint 1: Foundation & MVP Development

The goal was to identify user pain points with campus navigation and create an actionable Sprint Backlog that guided the design and testing of our Minimum Viable Product (MVP).

  • Business Problem: Users struggle with campus navigation.

  • User Problem: Confusing layouts and lack of real-time navigation tools.

  • Key Assumptions: Users prefer a filtered map, real-time tracking, and a clear search function.

  • Hypotheses: A real-time campus map will improve navigation efficiency and adoption.

Sprint 2: Refining the WayFinder Campus Map

Sprint 2: Persona Updates

  • Refined existing personas (students, visitors, commuters)

  • Introduced a transfer student persona, highlighting unique navigation challenges

MVP Development & User Testing

Created a low-fidelity clickable prototype with:

  • Search bar for buildings/landmarks

  • Map display with real-time location

  • Basic route planning

  1. User Research and Testing
    We conducted interviews with different participants like; Current students and visitors.

    Questions:

    • What challenges do you face with existing tools like printed maps or apps?

    • What features would make navigation easier?

    Key Insights:

    • Most users relied on pressing on the buildings rather than using the search button.

    • A “You Are Here” marker for better orientation

Sprint 2: Alterations

UI Refinements: Reduced clutter, clearer icons, and improved search

  1. Accessibility Enhancements: Prioritized inclusive features for a broader audience

  2. Usability Testing: 8 participants confirmed improvements but emphasized further refinements for event-based navigation

Retrospective

✅Frequent user testing helped refine the design
✅ Prioritizing assumptions kept the team focused
❌ Broad usability tests diluted insights—future tests needed to be more targeted

Sprint 2 : Challenges & Solutions

Challenges and How We Overcame Them:

  • Challenge: Balancing simplicity with feature requests.
    Solution: Introducing optional toggles for advanced features helped maintain a clean interface while accommodating diverse user needs.

  • Challenge: Shifting MVP focus based on unexpected user feedback.
    Solution: Reprioritizing our backlog allowed us to pivot quickly without losing momentum.

  • Challenge: Managing differing team expectations.
    Solution: Retrospectives provided a space to align goals and improve communication moving forward.

Proto-Persona Updates:
In Sprint 1, we created two Proto-Personas:

  1. Isaak Toribio: A current student navigating campus, Forgetful and flaky- Always late to class.

  2. Nelly Alberta: Freshman who’s new to campus, Lives with her parents and commutes to campus.

Sprint 2 updates included:

Diane Huang persona was refined to include Transfer student who’s new to campus Lives in an apartment off-campus, but near a KSU bus route.


Lessons Learned & Future Improvements:

🔹 User feedback drives design—iterating early prevents major pivots later
🔹 MVP scope must be narrow to maintain focus and efficiency
🔹 Team communication is crucial—clearer role definitions improve workflow