The gospel library web app is an application used for the study of church doctrines and teaching from its leaders.

Role: Product team member. UX Design, UI and Interaction Design, Research.

Audience: Members and non-members of the church throughout the world, ages 8 and up, with specific focus on people between the ages of 18-34.

Problem: Materials and resources across the church’s website are located in disparate parts of the site and all look and function differently. Also, there is no way for the user to take notes and annotate while studying the site’s content.

Goal: Create a centralized location for all study materials of the organization. Give users the ability to annotate, mark, tag, and share the content. Create an experience that provides an intuitive, accessible, and internationally friendly avenue for study that reflects the gospel library mobile application.

Process: As a product team, we began by evaluating what was out there across the site, gathering requirements from the various product owners and departments, and studying user feedback we had collected and performed true intent studies in order to understand our users better as well as the problems to be solved.

Working with our development partners and product management, we prioritized business and functional requirements and created the project scope and deadlines. Using our agile processes, we divided the work into design, development, and testing sprints.

After understand and defining the problem, we began to whiteboard and sketch out IA solutions including holding affinity sessions with stakeholders, creating site maps, and performing gorilla testing on initial IA structures.

Once we had solidified the IA, we began to design interface concepts and interactions and performed usability testing to confirm our assumptions. Our goal was to create an MVP that we could test and iterate long term as we gathered more feedback and testing results.

We wanted to present a collection based interface that would provide users with a table of contents-like navigation. Our interface would be able to accommodate the use of annotations as well as a way to use content related to the chapter the user would be in.

Once our MVP was created, we’ve been able to set up an A/B testing schedule to help us refine and iterate for a better experience. Early results suggest that this new experience is helping achieve our users’ goals, providing a robust study experience while increasing engagement.