UX research conducted with 24 academic library users — findings, personas, user journeys, and a site map derived directly from the data.
An academic digital library is meant to provide authentication, source management, and access to restricted content. In practice — the traditional interface burdens both types of users and leaves them frustrated.
Research Question: What barriers do library users experience, and what actions can new design take to resolve them?
Research was conducted via structured survey distributed to 24 users — from first-year students to faculty. Each participant was asked about usage frequency, academic confidence, main pain point, and desired feature.
Not invented — built on the distribution the data dictated. Two groups with entirely different needs.
| Attribute | Noa | Eitan |
|---|---|---|
| Average age (group) | 23.2 | 37.8 |
| Academic Confidence | 2.0 / 5 | 4.7 / 5 |
| Tech Skills | 4.3 / 5 | 3.0 / 5 |
| Primary Pain Point | Filter Overload | No Workspace |
| Core Need | Simplicity + Guidance | Management + Speed |
Two entirely different paths — one searches to succeed quickly, the other comes to work.
Information architecture derived from the personas — a direct path for Noa, a deep workspace for Eitan, and one article card that serves both.
No more search engine. A conversational interface that knows the user, clarifies the question before showing results, and serves as the command center for the entire site.
When a user logs in — the interface recognizes them. Dynamic placeholder, chips of recent searches, and instant access to what worked last time.
When a user asks a broad question, the AI doesn't dump 2,847 results. It negotiates briefly — 4 clear options, with an escape hatch always available.
The chat isn't just a search engine — it's the "command center" of the whole site. Help, navigation, explanations — all through natural conversation.
Five core screens for both personas — every design decision derived directly from the pain points surfaced in the research.
What the user actually sees. Every screen is built on one principle: fewer options, more power.
The full research translated into a clickable product. Navigate the search results, open a book, save it to your library, and read inline — the complete user journey in one prototype.
Each feature plotted by research citation frequency (impact) versus relative development effort (effort). The top-right quadrant is the MVP.
Single search field, year badge, smart defaults (last 5 years), direct PDF inline — four features, all derived from the 24 user pain points. Low dev effort, maximum immediate impact.
Batch citation export, personal library folders, and related articles. High impact for PhD students and faculty, but require backend infrastructure and auth.
The research with 24 users points to four clear design principles. Each one translates directly into a feature in the new interface.
"Good design is when the user doesn't feel like someone designed something — they just find what they need."
24 users · 4 core pain points · Clear path from research to solution