UX Case Study · University Library Systems
Role
UX Designer
Duration
8 Weeks
Tools
Figma
Type
Personalized Dashboard

Overview
With LibraryOS, I wanted to explore what happens between needing information and knowing where to find it. A student might arrive with a topic, an approaching deadline, or simply no idea where to begin. How could the library help them take that first step and keep moving?
I brought resource discovery, borrowing, and librarian support into one experience, with the aim of making the journey from an initial question to a useful resource feel more manageable.
Problem
Students were not failing because they lacked motivation. They were losing time to scattered services, unclear terminology, and interfaces that did not adapt to their intent.
Search-first discovery
Students must know exactly what keywords to search before they can find relevant books, journals, or databases.
Fragmented library tasks
Renewing loans, booking study rooms, and requesting books are spread across multiple pages and systems.
Low long-term engagement
Students often use the library only when assignments are due, with little encouragement to return or build consistent study habits.
Hidden librarian support
Many students are unaware that librarians provide research guidance beyond basic circulation services.
Overdue reminders arrive too late
Due dates are easy to miss, creating unnecessary stress, fines, and last-minute renewals.
Manual citation workflow
Creating citations requires switching to external tools or manually formatting references outside the library experience.
Poor first-time experience
New users receive little guidance or personalization, making it difficult to discover relevant resources from the start.
Librarians spend time on repetitive queries
Routine questions about renewals, room bookings, and catalog navigation reduce the time librarians can spend supporting research.

Design decisions
Each screen addresses a different part of the library experience—from discovering resources to managing loans and getting research support.
Design Focus: Help students discover relevant resources without already knowing what to search for.
Design Focus: Collect enough information to personalize the experience while keeping setup short and transparent.




Design Focus: Bring the most relevant information into one place so students know what to do next.

Design Focus: Support both exploratory and targeted search without increasing interface complexity.

Design Focus: Reduce friction in common library tasks.

Design Focus: Help students stay aware of their learning without making progress feel like a requirement.

Design Focus: Make research support easier to discover.

Students
Find relevant resources, manage loans, and access research support more easily.
Librarians
Make research guidance more visible and help students resolve routine tasks independently.
Universities
Make existing library resources and services easier to discover and use.
What I’d Test Next
Resource discovery: Can students find a useful resource for an unfamiliar assignment and understand its availability?
Everyday tasks: Can students check a due date, renew a loan, and find librarian support without help?
Accessibility: Can students complete these tasks using a keyboard and screen reader?
Designing LibraryOS made me think about the connections between tasks. Finding a useful book is one step; understanding its availability, borrowing it, and keeping track of its due date all shape the experience.
It also raised a question I’d carry into testing: does bringing more services together make the library easier to use, or create more information to navigate? I’d use that learning to decide what belongs on the dashboard and what can sit one step deeper.


