JSTOR Daily
Improving navigation and usefulness on the JSTOR Daily publication website for readers.
The problem 🤔
Readers looking to satisfy their desire for intellectual content, educators looking for interesting and credible content to share with their students;
How can we best help readers find useful and interesting content on JSTOR Daily?
JSTOR Daily is a free online publication operated by JSTOR, a digital library, that aims to bring insights from academic research to both scholarly and general audiences.
Due to the unorganized structure of the website and inefficient search functionality, key users face significant challenges with navigation and content discoverability.
Academic readers, such as educators, struggle to locate relevant articles, and casual readers are overwhelmed by the large catalog, leading to lower retention rates and underutilized content.
Our team at the University of Michigan School of Information was tasked with:
Attracting and retaining readers
Improving content discovery and accessbility
Emphasizing resources such as Teaching Resources and JSTOR Collections
Project objectives and goals 🎯
We identified the main objectives that would help us address the problems and opportunities of this project:
1) Optimize Navigation
How do users currently navigate JSTOR Daily's website?
2) Increase Retention Rates
What factors influence user satisfaction and likelihood of returning to JSTOR Daily?
3) Improve Content Accessibility
How effective is the current search functionality in helping users find relevant content?
4) User Goals and Motivations
What are users' primary goals when visiting JSTOR Daily?
Six research methods 👥⚙️
Click/press on image to expand.
Research findings
I will only be discussing the findings of a select few research methods in consideration of the length of this case study, but a full discussion of results can be found in our final report, which is accessible at the bottom of this page.
Surveys: Focus areas and opportunities for improvement
We used affinity mapping to analyze survey responses from both readers and non-readers, and revealed common themes among users that presented opportunities on what areas to focus on, and specific opportunities for improvement as we developed our redesign.
Competitive analysis: Drawing inspiration from competitors
We observed and noted how competitors, some of which were mentioned by research participants, organized their content and layout.
Analyzing what worked about competitors' layout choices would help inform our own design, drawing inspiration from best practices.
User journey: Seeing through users' POVs
Across interview participants, we noticed two common groups of users that we could target in our improvements: educators and casual readers.
In addition to personas, we created a user journey map for each user group to better understand how we could best help them find what they need, and enhance their reading experience.
We talked to several educators who enjoy JSTOR Daily’s content and want to incorporate it in their lessons.
Our main question: How can we help them find content for their students and emphasize teaching resources?
We also talked to many casual readers who enjoy the intellectual nature of JSTOR Daily’s articles and read them in the pursuit for more knowledge.
Our main question: How can we help them find diverse content that interests them and improve engagement with JSTOR Daily?
Walking through a specific scenario for each user group from their perspective helped us pinpoint specific opportunities for improvement.
Usability tests: Uncovering usability issues
Usability tests with familiar and non-familiar users revealed the following specific usability issues:
Search results were not relevant to what users were looking for
Unintuitive location for the search bar
Unclear language that confuses users (e.g. collections vs. series)
Newsletter signup is memorable
Turning user insights into ideas
Design requirements: From research to tangible features
With the sheer amount of information we gained from our many research methods, we had to hone in on what would be most important and impactful to users.
Brainstorming and creating a list of features would serve as a guide while we redesigned the JSTOR Daily website, and serve as a future resource to JSTOR Daily as well after handoff.
Our rapid ideation session—what features would be most helpful to users based on our research insights?
Low fidelity wireframes: Developing and testing functionality
We focused on redesigning three main components: The homepage, the navigation bar, and the article page.
We started out with low-fidelity wireframes to firstly focus on functionality and layout. This initial draft proved useful as we were able to obtain user testing feedback on these early stage ideas, easily adjusting and iterating as we continued to design.
For example, the mobile article menu was adjusted based on the following feedback:
Feasibility: JSTOR Daily could not implement an account system to allow users to save articles.
Accessibility: The menu was moved to the bottom of the screen for more convenient access.
Key design elements
Our final design was informed by both user feedback and needs, as well as JSTOR Daily's business goals. After multiple cycles of feedback with the JSTOR Daily development and editing team, and various types of users, we developed the final redesign with the following themes:
Simplified Information Architecture
Enhanced Content Discovery
Improved Navigation System
Strategic Use of Visual Elements
Clear Calls-to-Action
We saw significant improvements in task completion time (i.e. sharing articles, finding topic-specific content) on our prototype compared to the original website. Four out of five tasks had at least an 80% increase in task efficiency.
Below is a more detailed explanation of what we changed and why in the three main components: the home page, navigation bar, and article page.
Home page
Navigation bar
Article page
Handing it off
To allow the JSTOR Daily to easily reference our recommendations and findings after our time together, we created the following materials for their team:
User flow
Maps out each interaction and the paths a user can take within the redesign.
Click/press on image to expand.
UX Specification
Clearly defines layout, interactions, and behaviors of the redesign user interface for developers.
Click/press on image to expand.
Reflections and next steps
This project could only be so fulfilling because of the people I worked with—my teammates with their collaborative, dedicated, and creative spirit, and the JSTOR Daily team for their helpful feedback, support, and direction. I will not forget the late night work sessions with the team and Google Meet calls where JR's cat would say hello!
I learned a lot from the nature of the project—since it was client-based, consistent communication, emphasis on business goals, and evaluation of feasibility was necessary for the project's success. The sheer amount of user feedback and engagement during the project was amazing. I met all kinds of readers, and was inspired by their dedication to knowledge. It was fulfilling to hear the many different ways of what JSTOR Daily meant to them.
Moving forward, I would like to improve on one aspect:
Design systems: Although we created a dedicated asset system used throughout the redesign, I would like to further explore creating a more structured and granular design system to allow for streamlined designing.
Thanks to my teammates—Olive, Liam, Mida, and Connor—and the JSTOR Daily team—JR, Johnathan, and Anjanette—for making this such an amazing experience!
Final prototype
Try out our interactive prototypes of the JSTOR Daily redesign! Check out our final project report and UMSI expo poster as well.
