Leading the integration and improving the discovery experience of LOC Stacks, Catalog, and Loc.gov as part of the University of Maryland iConsultancy and UMC HCI Masters program.
Our Team: Xiaodi Sara Hu, Shireen Patel, Tulika Mohanti, Rajin Suchdev, Jocelyn Sun
Introduction
📋 Overview
The Library of Congress (LOC) is embarking on a multi-year project in collaboration with the UMD iConsultancy to replace its integrated library system, which includes the main page (loc.gov), the catalog, and Stacks. LOC would like to better understand the user experience that patrons have with the existing ILS, specifically the discovery layer, and develop design concepts based on this research. To help LOC achieve these objectives, we are performing five design sprints - iterative cycles of research, design, and evaluation - to ideate and generate product concepts and high-level designs, and create a clickable prototype of the redesign.
The Challenge How might we improve users discovery experience while navigating the Library of Congress platforms?
📋 Goal
The ultimate objective is to enhance users' discovery experience when navigating between loc.gov, the
LOC catalog, and Stacks. This will be achieved by refining the presentation of various functionalities,
guiding the users to the appropriate platform that caters to their specific requirements.
→ Replace its integrated library system (ILS)
→ Better understand patron’s user experience with the existing ILS
→ Develop design concepts based on this research
Breaking down our long-term goal into five distinct sprints is a strategic approach to ensure that we
achieve our objective of improving the users' discovery experience. By dividing the project into sprints,
we can dedicate our attention to each aspect of the project, while ensuring that each step aligns with
our overall goal.
Each sprint will have its own focus, with the aim of developing a specific component of the end
product. This approach enables us to carefully consider every detail, from the presentation of
functionalities to the user interface design.
By taking a methodical and step-by-step approach, we can ensure that the final product meets the
needs and preferences of our target audience, and provides an enhanced user experience. Through
each sprint, we will take into account feedback from users, stakeholders, and our own team members,
to continuously refine our approach and ensure we are on track towards achieving our long-term goal.
⚔️ Competitive Analysis
We did a competitive analysis with 4 direct and 1 direct competitor to understand more about the industry and requirements for the platforms. This analysis was done for all LOC platforms and is used across all five sprints.
→ Direct Competitors: JSTOR, NASA, EBSCO, British Library
→ Indirect Competitor: Wikipedia
🎨 Style Guide and Component Library
We have established a style guide that outlines specific fonts and colors to ensure consistency across all of our designs. Additionally, we have developed a component library, which allows us to streamline the design process and maintain a high level of consistency throughout all of our projects. By implementing these tools, we are able to create designs that not only look professional, but are also efficient and effective in achieving our goals.
The Design Sprint Process
We will be using The Design Sprint to work through our client's needs. The sprint requires a team with specific roles and schedules to go through the problem, research, solutions, prototyping, and testing. The goal of a design sprint is to create and test possible solutions for a problem in a limited period of time. A description of each step in the sprint is listed below, as well as a link to the official design sprint guide.
Mapping (1/5)
🤔 Key Questions & HMW
We picked a target by defining key questions, setting long-term and short-term goals, and consulting experts. The design team lists out our questions and concerns, then brings in the client to vote on our top points. Next, we interview experts from our sprint team to discuss vision, user research, and previous efforts. We will use this information to capture "How Might We" notes.
➡️ User Flow
In order to better understand the user experience on our platform, we begin by mapping out the current user flow. This detailed map allows us to visualize the process that users undergo when interacting with our product. By identifying pain points, blocks, and overlaps, we gain valuable insight into the user experience and can use this information to inform our future design process.
By taking the time to create a detailed user flow map, we are able to gain a deeper understanding of our users and their needs, and can use this understanding to create a more user-friendly and effective platform. This process is a critical step in our design process and helps ensure that we are creating a product that truly meets the needs of our users.
Sketching (2/5)
⚔️ Competitive Analysis
To gain a comprehensive understanding of the industry and the platform requirements, we conduct a competitive analysis with both direct and indirect competitors. This analysis helps us identify the strengths and weaknesses of our competitors and provides us with insights on how we can improve our own platform. During the analysis, we utilize individual brainstorming, independent solutions, and critical thinking to identify areas where we can improve.
To ensure our design sprint process is effective and successful, we carried out one competitive analysis at the very beginning. This analysis encompasses all LOC platforms and helps us identify the key areas where we can focus our efforts. By having a thorough understanding of the industry and the competition, we are better equipped to problem-solve and develop innovative solutions.
⚡ Lightning Demos
To improve our ideas for the Library of Congress, our team conducts thorough research on our competitors and other sources. We take inspiration from design and organizational concepts that could be beneficial to the Library of Congress. Using this knowledge, we create Lightning Demos, which are collections of images that we handpick. These demos showcase our ideas and provide visual representations of what we could potentially implement to improve the Library of Congress. By doing this, we are able to provide a more detailed roadmap for the Library of Congress's future development.
Deciding (3/5)
⚔️ Solution Sketches
Using inspiration from the Lightning Demos, we create Solution Sketches that address our Key Questions and How Might We's. Solution Sketches are individual storyboards that the team creates based on the Lightning Demo.
We display our Solution Sketches as an Art Museum by putting them up side by side. We then silently review the sketches and do a speed critique. Our stakeholders join us to label our favorite ideas with a sticker, creating a heat map.
💡 Stakeholder Ideas
Using the input and the following spotlighted ideas from our stakeholders, we created a storyboard of the potential user flow.
Prototyping (4/5)
🗒 Low Fidelity Prototype
In order to bring the storyboard to life, we create a low fidelity prototype that can be tested and evaluated for any necessary improvements. This prototype serves as a stepping stone towards the finished product, allowing us to visualize and test out different features and functionalities before committing to a final design. By testing the prototype, we gain valuable insights into how users interact with the product, which can inform our decision-making as we move towards creating a more polished final product. This process of prototyping and testing helps us to refine our ideas and ensure that the final product meets the needs and expectations of our users.
Testing (5/5)
👥 User Testing
To ensure the prototype meets the needs of the intended users, we conduct extensive user testing to gather feedback. In addition to user testing, we also carry out multiple user interviews to obtain a more comprehensive understanding of user preferences and pain points. Using the information gathered from the feedback, we generate affinity notes to identify patterns and themes. These affinity notes are then used to create two affinity diagrams, which help us visualize the relationships and connections between different user needs and preferences. Furthermore, based on the insights gained from the affinity notes and diagrams, we create a persona, which represents our ideal user and guides our decision-making throughout the design process. By following this rigorous user-centered approach, we are able to ensure that the final product meets the needs of our target audience and delivers a superior user experience.
Stacks
11.07.2022 → 12.09.2022
As the Visual Designer for the Stacks System, my responsibilities included creating and adhering to a comprehensive style and brand guide for the entire ILS system. Working alongside the UX Designer, I facilitated brainstorming sessions to generate innovative ideas and developed visual concepts that aligned with the established guidelines. I also collaborated with researchers to ensure their needs were successfully integrated into the design.
Challenge How might we improve users discovery experience while navigating the Library of Congress platforms?
Mapping (1/5)
🤔 Key Questions
How do we design for the entire experience… if there were no problems identified?
❓ How Might We
🔄 User Flow
➡️ Pain Points, Blocks, and Overlaps
→ Poor visual design and visualizations, creating little enticement for users
→ No interaction for Stacks at a Glance
→ Lack of queue, resulting in users not being able to easily access currently unavailable resources
Sketching (2/5)
I started this stage with the following in mind:
Our objective is to improve the overall user experience when navigating through the multiple platforms
of the Library of Congress. To achieve this, we aim to enhance the visibility and accessibility of the
stacks by presenting information in a more dynamic and visually appealing way. Furthermore, we aim
to implement a system that provides real-time updates on which resources are currently in use and
their expected availability, making it easier for users to plan their research accordingly.
⚡ Lightning Demos
Deciding (3/5)
⚔️ Solution Sketches
💡 Stakeholder Ideas
After speaking to our stakeholder, we were able to identify the following ideas that they felt were
important to include in our prototype.
→ Stacks: Side titles search needs to be reworked
→ Data Sorting: figure out optimum data sorting, high level to lowest level, eg type of medium >
language > date > etc
→ Data Visualizations: think through the order of operations for each data visualization to minimize
confusion and relation to each other item
Client’s highlighted features from my sketch:
→ Thinking through the order of operations for each data visualization to minimize confusion and
relation to each other item
→ Including interactions and animations when you click on a specific item
→ Resource visualization with abstraction of books while maintaining the concept
Prototyping (4/5)
📖 Storyboard
I was responsible for drawing the storyboard for the Stacks system. I collaborated with my team to
brainstorm ideas and concepts that we wanted to incorporate . We discussed the platform's primary
goals, the user experience we wanted to create, and the key features we wanted to include.
I needed to ensure that the design was user-friendly, efficient, and aesthetically pleasing, while also
being functional and meeting the platform's goals. It was important to incorporate all of the ideas and
suggestions from my team members, so I made sure to consult with them throughout the process.
Throughout the feedback and modification process, I made sure to listen carefully to my team's
suggestions and incorporate them into the final storyboard. This collaborative approach ensured that
the final product met all of our goals and objectives, while also being visually appealing and easy to
understand.
The final storyboard was a detailed and comprehensive visual representation of the Stacks platform,
including all of its features and functionality. It served as a valuable reference throughout the design
process, allowing us to ensure that every aspect of the platform was accounted for and implemented
properly.
🗒 Low Fidelity Prototype
Testing (5/5)
👥 User Testing
We collected qualitative data via three expert interviews and prototype tests. We created two affinity diagrams based on our expert testing as well as two user journey maps.
🗺️ Journey Maps
💬 What We Learned
Prototype Testing
- The new data visualization designs encourage users to explore the homepage and site
- Both the “trending now” section and the counter remind people that Stacks is dynamically changing
- User prefers a layout that is clean and easy to understand
Contextual Interviews
- Users want the current design of Stacks’ homepage to be more interactive, and more intuitive information architecture
- While experts know that loc.gov, the LOC Catalog, and Stacks are three different systems, casual users might do not have the same clear mental models
- Expert users might begin their search on external sites to maximize their efficiency
- It might be reasonable to integrate Stacks into LOC Catalog, but keep loc.gov separate
🤔 User Needs
CRS Researchers want efficiency
- to be able to find information with a short deadline
- to use external resources (Google Scholar, Amazon, etc.) to speed up search process
- to know what they are doing → only switch systems when required
Casual Users wants differentiation
- to understand the difference between loc.gov, the LOC catalog, and Stacks
- a clear discovery layer to guide user to the most appropriate search system which suit their needs
- clear, straightforward search results
Lessons For the Future
⚖️ Balancing Aesthetics & Usability
The development of the Stacks platform was a complex and demanding process that required us to overcome several challenges. One of the biggest challenges we faced was the limited access we had to the system. We had to rely on screenshots, guidance, and our client's experience to develop the platform. Despite these limitations, we were able to create a highly functional, user-friendly, and visually appealing system that met the needs of our client.
One of the key features of the Stacks platform is the data visualization designs we implemented. These designs were created with the goal of encouraging users to explore the site and interact with it. By using simple yet captivating interactions, we were able to make the platform more engaging and user- friendly. This, in turn, helped drive user engagement and usage.
Through the development process, I learned several important lessons about designing digital platforms. One of the most significant lessons was the importance of creating clean, intuitive layouts that are easy to navigate. Users prefer platforms that are straightforward and easy to use, and they're more likely to engage with platforms that are visually appealing. Thus, it's crucial to consider both visual aesthetics and usability when designing digital platforms.
In addition to designing the platform, we also had to ensure that it was accessible to all users, regardless of their abilities. Accessibility is an important consideration for any digital platform, as it ensures that all users can benefit from the platform's features and functionality. We worked closely with our client to ensure that the Stacks platform was accessible to all users, and we implemented several features to make it easier for users with disabilities to use the platform.
In conclusion, developing the Stacks platform was a challenging but rewarding experience. By overcoming the challenges we faced and implementing new design features, we were able to create a platform that is user-friendly, visually appealing, and accessible to all users. I learned valuable lessons about designing digital platforms that I will carry with me into future projects. Ultimately, the success of the Stacks platform demonstrates the importance of collaboration, creativity, and attention to detail in the development of digital platforms.
Catalog
09.19.2022 → 10.27.2022 and 01.26.2023 → 02.23.2023
As the Project Manager of the Catalog System, I oversaw the planning, organization, and direction of the project's completion. Working closely with the client, I ensured that our work was delivered within the specified timeframe and met the agreed-upon scope.
Challenge Create a visually organized Catalog homepage that clarifies navigations without endless clicking.
Mapping (1/5)
🤔 Key Questions
Will we have enough time to distill research insights?
❓ How Might We
How might we detangle the search system based on the feedback from sprint 1 and reorganize the
functionality?
🔄 User Flow
➡️ Pain Points, Blocks, and Overlaps
→ Lacking enticing and informative home page
→ Inaccurate results scrolling needed to find the information requested
→ Cannot use resources without registration but registration is inaccessible
→ Difficult registration process. Online pre-registration was unavailable and all in-person appointment scheduling was delayed
→ No clear guidance about how to use the catalogs and why
Sketching (2/5)
⚡ Lightning Demos
Google Drive → Expandable menu on umbrella platform with sub-platforms
Wikipedia → Homepage with varying extensions showcased with collective search
NASA → Visualization showing contents of the database
EBSCO → Option to filter the search eliminates the display of search options
British Library → Clear explanation of what people can expect from the search bar
JSTOR → Show search categories allows users to narrow down their search
→ "Just search for" for casual browsing
→ One collective advanced search with includes keyword search and filters
Deciding (3/5)
⚔️ Solution Sketches
💡 Stakeholder Ideas
After speaking to our stakeholder, we were able to identify the following ideas that they felt were
important to include in our prototype.
→ Search Facets allowing users to narrow down their input and output
→ Screen Reader friendly focusing on inclusivity with a greeting and/or introduction
→ Actively updated resources statistics (total, trending, current, etc)
→ “I am, I need” search function with suggestions tailored to users
→ Featured Section for resources → updated with statistics
→ Interactive database exploration for users
Prototyping (4/5)
📖 Storyboard
I worked closely with the team to develop a visually compelling storyboard that was both engaging
and user-friendly. This involved guiding the design process, including overseeing the prototyping and
creation of the layout structure. I worked to ensure that all design elements were in line with our
overall vision and goals, and that they resonated with our target audience.
In addition to my supervisory role, I also took on the important task of ensuring that our style guide
was followed and that our designs remained consistent across all platforms. This involved careful review
and editing of all design elements to ensure that they met our established standards and guidelines.
By maintaining consistency in our designs, we were able to work towards create a cohesive and user-
friendly experience for our users, regardless of where users accessed the catalog system.
🗒 Mid Fidelity Prototype
Testing (5/5)
👥 User Testing
We completed user testing to get feedback on the prototype and carried out three user Interviews. Using the affinity notes we created with information from the feedback, we created two affinity diagrams as well as a persona.
Affinity Diagrams and Findings
💬 Concept Suggestions
Contextual Interviews
Establishing correct mental models. Correctly describing what each online resource does, what types of items are being searched for, and how the items being displayed in search are ranked is essential to increasing the usability of the LOC catalog and loc.gov and is an immediate need when unifying the systems under the Integrated Library System.
On Loc. gov. Improve the navigation bar and general layout in order to give clear guidance to different resources. Define search categories on the loc.gov search, e.g. “everything” and have better search result ranking and explain the ranking
On the Catalog. Have a welcome section to explain what people can find in Catalog, and a link to all catalogs categories by alphabet and item types. Have a filter sidebar, and reconsider the wording of “Quick Search” to make it more intuitive for users.
Prototype Testing
Accessibility. Signifiers should always be designed with at least two differentiate factors (text + color, shape+ color, etc.) for accessibility
Consistency. Use terms which the users are familiar with, even if those might not be the best defining terms. Designs need to be consistent throughout to meet the users’ expectations (e.g., having all filters at the same place).
Provide more guidance up-front and on all essential features
Lessons for the Future
🧑🏿🤝🧑🏻 User Centered & Intuitive Design
In order to better understand the user experience, I referred to the extensive research done by our research team to identify and address common obstacles that users face when interacting with our system. One of the main challenges I discovered was that users often have misconceptions about the functionality of each resource and how to navigate the systems, which leads to confusion when trying to decide which system to use and for what purpose.
To overcome this challenge, I realized that it was necessary to develop a strategy that clarifies the functionality of each resource and enhances the overall usability of the system. This involved taking a user-centered approach to design that focused on aligning with users' mental models and providing an intuitive and seamless experience.
I recognized that designing an intuitive system was crucial, as users may not always understand the reasoning behind a particular design decision. Thus, I emphasized simplicity and ease of use in my design approach, prioritizing the user experience above all else. By doing so, I was able to create a clear path for users to achieve success and minimize confusion, ensuring that the system is more accessible and user-friendly for a wider range of users.
My research and design approach have enabled me to develop a user-centered system that aligns with users' mental models, enhances usability, and prioritizes simplicity and ease of use, which is a focus I will utilize in the future. This ensures that our users have a clear path to success and can easily navigate and utilize our system with confidence.
Loc.gov
02.27.2023 → 04.03.2023
As Lead UXUI Designer, my role involved storyboarding and implementing a prototype that aligned with the proposed objectives. I ensured the design was user-friendly and single handedly incorporated necessary revisions based on the research team's findings to meet our target audience's needs and preferences.
Challenge Create clear and visually-appealing layouts to show activities/services,
differentiate search systems, and explain available resources to users in a non-intrusive way.
Mapping (1/5)
🤔 Key Questions
How can we create clear and easy navigation to different resources without making the page too
overwhelming?
❓ How Might We
How might we create a visually appealing layout for the activities displayed on the homepage without
overwhelming the users with the information
🔄 User Flow
➡️ Pain Points, Blocks, and Overlaps
→ Users with an incorrect mental model did not understand the navigation bar located under the hero
section. As a result, they either 1) thought they had exhausted the search results or 2) assumed that the
search results contained the catalog and/or everything that LOC offers, causing them to stop searching
or use Google instead.
→ Users who don’t bother to try to search for an item, service, or event on the LOC and instead go
directly to external search engines such as Google, Google Scholar, or Amazon Books to search for their keywords along with "LOC" to get the expected results. These users may feel satisfied with the external
search results and may not return to our platform.
→ Users with the correct mental model face explore function challenges due to excessive information
and images. Searching for "Online Catalog" or additional collections can reveal the limitations of our
platform, encouraging users to look for other sources.
Sketching (2/5)
⚡ Lightning Demos
The British Library → choose between search in library website or catalog
Westerville Public Library → explicitly state parameters users are searching within
HM Magazine → contextual labeling of search bar w/ interesting quick-links
GE → integrated dashboard with brief descriptions of each service
Deciding (3/5)
⚔️ Solution Sketches
💡 Stakeholder Ideas
After speaking to our stakeholder, we were able to identify the following ideas that they felt were
important to include in our prototype.
→ "Search in" is very friendly and concise
→ Highlighting the visuals for search results
→ Balancing the visual with the textual data to make it easy to use
→ New homepage should show frequent updates and be made a living page
→ Should be more utilitarian
→ Wants homepage to showcase the richness of the items that the LOC has and provides controls to
do a search but retains the showcase of images
→ Increase thumbnail (point of frustration with users is the search results page because the thumbnails
are so small)
Client’s highlighted features from my sketch:
→ Balancing the visual with the textual data to make it easy to use
→ Highlighting the breadth of events happening
→ Gridded calendar for events (currently there is no grid view since there are too many elements to
incorporate on the page.)
Prototyping (4/5)
📖 Storyboard
After collaborating with Jocelyn Sun I took on the task of designing the Loc.gov homepage, using the
first storyboard we created as a foundation. Keeping in mind the importance of consistency and
cohesiveness across the platform, I incorporated design elements from the Stacks and Catalog pages
into the Loc.gov homepage. This ensured that users could easily recognize and navigate through the
different pages of the platform, without any confusion.
One of the most significant challenges in designing the homepage was the Events section. To create a
dynamic and engaging user experience, I brainstormed and developed an interactive grid and list that
allowed users to toggle between dates to view relevant events. I ensured that the design was intuitive
and user-friendly so that users could quickly and easily browse through the events and find the ones
that suited their interests.
Incorporating interactive elements into the design was crucial to me, as I believe that user engagement
is an essential aspect of a successful platform. By creating an interactive and dynamic Events section, I
aimed to make the user experience more engaging and encourage users to explore more of the
platform.
We initially designed an ILS page (storyboard 2), but decided not to pursue it further due to limitations in
time and resources.
🗒 Mid Fidelity Prototype
Testing (5/5)
This sprint, we did two rounds of testing to ensure we could receive and incorporate as much feedback as possible into our final prototype. Round one was done with the sketch & low fidelity prototype, and Round Two was done with the mid fidelity.
Round One Testing
🗒 User Interviews + Card sorting
Testing the prototype & contextual inquiries
→ 40% of users expected to find information about the Library’s location and logistics in the
“About” section in the header
→ 80% of users expressed that they wanted the daily hours as well as location of the LOC in the
page footer
→ In the search bar portion with “I need help” , 40% of users expected to find “Ask a Librarian”
→ 40% of our users expected to find information about the LOC history and what is does in the
hero image
After conducting preliminary design testing (Prototype Draft Testing - Tasks), we received positive
feedback on our navigation bar. Testers successfully completed the discovery tasks using it,
indicating that it was effective. Users also expressed and demonstrated that their discovery
experience was improved with the addition of the bottom navigation footer, which acted as a site
map and provided clear navigational information. This allowed us more flexibility in what
information is displayed in the top navigation bar, as we could prioritize the most frequently
accessed and guiding information. Moving forward, we will aim to ensure that the most important
information is given the highest priority, based on user needs and feedback.
In our preliminary design testing (Prototype Draft Testing - Card Sorting), we used MaxDiff Analysis
to gain insight into users' priorities for the content we provided. This analysis helped us better
understand which elements of our design were most important to users and informed our decision-
making moving forward. By leveraging this method, we were able to gather meaningful data that
guided our design choices and helped us create a user-centered product.
📝 Contextual Findings
Visually with screenshots from the prototype
Of Our Users...
→ 80% of the users used the general search bar when asked to search within the library catalog
→ 60% of users expressed they want to see more options in the nav bar (eg.drop down format)
→ 10% of users liked the image usage and felt they seemed authentic
All Users:
→ All users liked the general layout of the current loc.gov homepage
→ All users them scrolled past the Event Section when asked to find events happening in the later
weeks → no title
→ All users expect to see information related to a Library of Congress visit at the top ( eg. hours,
location, booking passes, reading rooms availability)
→ All users preferred that the navigation bar was located above the image carousel
General
→ Overall navigation and discoverability is weak → not friendly to the general public
→ The LOC address and hours were expected to be displayed in the page footer
Round Two Testing
🔍 Search Bar/Header User Feedback
→ the names on the nav bar is confusing (need to consult with UX writer for improvement)
→ inconsistency in menu (4 drop downs, need to edit about to differentiate OR add drop down)
→ difficult for users to differentiate between dropdown and search bar (edit menu color)
💡 Featured & Catalog User Feedback
→ “view all events” button is not salient enough and does not appear clickable (edit color/button to improve make more intuitive)
→ event section is only seen when users scroll (this cannot be remedied, as it is only the 3rd item on
the page)
⬇ Footer User Feedback
→ The LOC address and hours were expected to be displayed in the page footer
→ information can be condensed (bottom 3 options on the 2nd column are related)
→ wants consistency with social media icon colors (not needed, as we use their branding colors)
→ more prominent “subscribe to newsletter” needed (will be emphasized in footer OR moved to
header)
Lessons for the Future
🗒 UX Copy + Information Architecture
When initially working on Catalog (primarily the search function) and Stacks, we used placeholder text instead of real content from the live site due to time and resource constraints.
While working on the loc.gov system, we worked with the real architecture of the site, which was a valuable experience that helped us handle practical constraints. While working with placeholder text gave us more creative freedom, we realized that it also meant deferring practical constraints to later systems, given that we were working on an existing site. This trade-off was necessary due to the structure of the capstone course and limited time.
Through the process of designing navigation systems, I realized the crucial role of information architecture in enhancing or hindering design efforts. I learned the importance of good information architecture and how it can make it easier for users to navigate and find information, and this is a lesson I’ll carry through my career.
In order to ensure that our project aligns with the Library of Congress' brand and tone, and that our design effectively guides users, we will be working with a UX Writer. This expert will provide guidance on the text and tone of our content, and help ensure that our design provides clear and intuitive directions for users. By leveraging the skills and expertise of a UX Writer, we aim to create a user- friendly and cohesive product that meets the needs of our target audience.
Integration
04.07.2023 → 05.12.2023
As the Project Manager, I assumed responsibility for the seamless integration of three systems. Utilizing Miro and Figma, I meticulously organized and finalized our deliverables, and confidently led the final handoff of these deliverables to the client.
Challenge Final handoff for effectively integrate the three library systems and optimize their navigation to enhance users' discovery experience.
Miro / Research and Design Sprint Process
Over the course of the past seven months, our team has been utilizing Miro, a collaborative online whiteboard platform, to effectively organize and manage our sprints. I was tasked with the responsibility of overseeing the process of streamlining our procedures and ensuring that our client could easily access and retrieve the information they required.
The Breakdown:
- Established an organized, succinct structure to arrange the research findings.
- Supplied an all-inclusive summary of the advancement made and key insights gained.
- Utilized straightforward language and visual aids to communicate intricate ideas.
- Furnished the client with a complete and thorough summary of the project.
I dedicated myself to creating a clear and concise organizational structure for our research findings. Through a meticulous categorization process, I divided all of our discoveries into different stages and sub-stages, providing a comprehensive overview of our progress and key insights
In addition to this, I ensured that all of the information we gathered was presented in an easy-to-understand manner, using clear language and visual aids to convey complex ideas and concepts. I aimed to provide our client with a comprehensive and detailed overview of our work, allowing them to make informed decisions and take proactive steps towards achieving their goals.
Figma / Designs and Interactive Prototype
As the project manager for the Loc.gov System and Integration Process , I oversaw the entire project from its conception to completion. In addition to my management role, I also served as the lead visual and UI designer for all sprints. With this dual role, I was able to ensure that both the design and development aspects of the project were being handled smoothly and efficiently.
Throughout the integration process, my team and I conducted multiple rounds of testing and research to gather feedback on our designs and prototypes. We meticulously evaluated all feedback received, making necessary edits to our designs to improve their functionality and overall user experience. I was particularly focused on ensuring that the designs were not only visually appealing but also intuitive and user-friendly. Once the feedback had been collected and the necessary changes made, it was up to my team members to implement these changes.
As the lead visual designer, it was my responsibility to:
- Ensure that designs adhered to established branding guidelines
- Collaborate with stakeholders to prioritize accessible and user-friendly visual elements
- Establish a set of guidelines for all future designs and implementations
- Solidify design system and style guide for consistent, efficient design with fewer errors
- Achieve a more cohesive and professional look and feel for the project
Google Drive / Reports and Logistic
Our presentations offer a thorough look into our design process, emphasizing the research and iterative methodology we employed in sprints 1-5 for each LOC system. Our goal is to showcase our user-friendly designs and provide a clear understanding of our process and successful outcomes.
As the person responsible for organizing the content of our final presentation and client handoff, I had to consider several factors to ensure that each slide contained relevant and useful information.
🔎 Content Evaluation
I began by reviewing the research we conducted and the iterative design approach we employed, and then carefully selected the most important and impactful findings to include in the presentation. This involved evaluating the effectiveness of each finding and determining how it could best be presented.
🧑🎨 Aesthetics & Organization
Once I had organized the content, I worked on establishing an aesthetic that would accurately reflect our design vision. This included selecting appropriate fonts, colors, and imagery that would help to convey our message effectively. I also made sure that the visual elements of each slide were consistent with our prototype, creating a cohesive and professional look that would resonate with our audience.
In addition to creating a visually appealing presentation, I implemented seamless animations to help emphasize key points and keep the audience engaged. These animations were carefully selected and timed to enhance the overall flow and impact of the presentation.
⌛ Time Management
To ensure that our presentations were completed on time, I delegated roles to team members and established a timeline for completion. This involved assigning specific tasks to each team member and setting clear deadlines to ensure that everything was completed in a timely manner. I also oversaw the finalization of the presentations, making sure that all information was accurate and relevant and that the presentations were ready for presentation to the client.
Lessons for the Future
🗒 Task Delegation & Feedback
During this sprint, our team was faced with a daunting challenge - an overwhelming amount of work that needed to be completed within a very tight deadline. As a team, we knew that we had to be efficient and productive in order to deliver the project on time. To help us achieve this, I implemented a strict and straightforward work delegation system that assigned specific tasks to each team member.
As the project manager, I recognized that it was my responsibility to ensure that every team member was contributing equally and making progress towards the project's goals. I understood that every individual had their own unique strengths and skill sets, and that it was important to leverage these skills in a way that benefited the team as a whole.
To achieve a fair and equal distribution of tasks, I carefully monitored each team member's progress and provided constructive feedback and criticism that helped them improve without feeling discouraged. I made sure to communicate clearly and respectfully, highlighting areas of strength and offering suggestions for improvement. I also made myself available to answer questions and provide guidance when needed.
Through this experience, I learned that effective communication is essential for successful teamwork. I also learned that fairness and equality are key components of a productive team dynamic. By ensuring that every team member had an opportunity to contribute their skills and expertise, we were able to work together seamlessly and achieve our goals within the tight deadline. Overall, this sprint taught me valuable lessons about leadership, teamwork, and effective communication that I will carry with me throughout my career.
The Final Product
Complete Interactive Prototype & Designs