Increasing Efficiency Through Information Architecture Improvements
overview
In 2022, I led a redesign of the Client Profile section of the AlayaCare app (an area visited by thousands of users daily), including improvements to the Information Architecture (IA) and the design of specific pages. I conducted a card sorting exercise, analyzed data analytics, ran internal stakeholder testing, and carried out prototype testing with users. This project resulted in increased user satisfaction across three markets (US, CAN, AUS) as well as increased engagement with and connection to the users via the creation of an online AlayaCare Research Community.
Information Architecture, Card Sorting, Data Analytics, Internal Stakeholder Testing, Prototype Testing, User Testing, Visual Design
software
Optimal Workshop, Amplitude, Miro, Framer
year
2022
What’s a Rich Text element?
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
Static and dynamic content editing
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Persona
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
problem
Upon analyzing the client profile of AlayaCare’s home health/care facilitating application, it became apparent to me that sections of it that I would expect to be grouped together were far away from each other. I considered the consequences of a poor information architecture (IA) and how it could negatively impact the onboarding of new users onto the software, affect user workflow efficiency in general, and cause difficulties in the future as we plan to edit and consolidate related pages.
Could the IA of the client profile be improved?
Information Architecture skeleton of the original client profile
discover
Card Sorting
I set out to test my hypothesis of our IA by first organizing an open card-sorting exercise with some colleagues, whereby each person would sort the different features found in the client profile into categories that they would assign themselves. The results of this exercise would show me how each person would organize the client profile based on their own logic and if there were any patterns emerging from the sortings that could help inform the next iteration of the client profile IA. Also rather than labeling the cards with the exact name of the feature as displayed in the app, I tried to describe the feature’s purpose to help lower any conformation bias.
Results of one of the card sorting exercises
I followed 11 people over Zoom video as they completed the card sorting exercise, asking each to narrate their thought process throughout so I could better understand their logic.
Many similar organization-related patterns emerged from the results of the study between each person. Finally, it became apparent that there was a discrepancy between how the people in my study would organize the client profile and the existing IA in the app.
Data Analytics
To further test my hypothesis, I looked at user behaviour data on Amplitude to see which pages were being most visited above others and to understand the journey users were taking from one tab to another.
miro workspace showing the various user segementation charts I analyzed
The results of the data analytics were substantial: I learned that certain pages could be deleted because of near 0% visits, the logic of the various user journeys showed possible tab/feature groupings which resonated with the results of the card sorting exercise and the order of tabs could be rearranged based on chronological and frequency of use. In short,
My hypothesis was true!
define
After creating a first proposal of a new IA skeleton, I invited key internal product and CS people from different markets to analyze the drafted IA and offer their comments and thoughts. Their feedback informed a second proposal which was now ready to be tested with users.
miro workspace showing first IA iteration and comments from key internal colleagues
test
An online AlayaCare Community was created with the purpose of connecting with current users for feedback on this initiative as well as future design initiatives and testing opportunities.
The first post on this community introduced the client profile IA revamp initiative via a prototype of the latest IA proposal which also leveraged the new design system.
The comments on the post from 12 different users across the different markets informed the next iteration of the IA, and also sparked a flame to work on updating the design of the current “Demographics” section of the app, which users were complaining about upon seeing the prototype.
First post in the Community dedicated to this initiative
Current Demographics Design
Original demographics page design
final skeleton
Deleted Tabs:
Video Conferences: This feature is still available via Scheduling tab of the client profile
Late notification: Not functional and analytics showed close to 0% usage of this area in client profile.
Report notification: Not functional and analytics showed close to 0% usage of this area in client profile.
Clock notification: Not functional and analytics showed close to 0% usage of this area in client profile.
Portal access button via Coordination tab: This is still available from Client Overview
Mobile devices: Not functional and analytics showed close to 0% usage of this area in client profile.
Renamed Tab Titles:
Care Plan -> Care Plans
Document Approval -> Document Approvals (doesn't apply to all)
Visit Signatures -> Signatures
Wound Care -> Wounds
Client Specific Skills -> Required Care Skills
Do Not Send -> Blocked Employees
Notes on Some General Changes:
All of the tabs found under the original “Demographics” primary navigation tab were consolidated into one secondary “Demographics” tab that now lives under “Client Info”
“Medical History” and “Contacts” were brought into “Client Info” as this is all the information that is entered during client intake
final design
The new demographics page now combined all the previous sections into one page, offered more organization of the fields via the accordions, reduced the previous amount of empty space by placing several fields in a row and finally allowed for responsiveness across the different touch points our users use.
Responsive design for the new Demographics screen
measuring success
We received a huge amount of positive feedback of the changes. Here are some of the things people have been saying:
