DESIGN SPRINT: IA and DASHBOARD
Participate in a four day Google-style Design Sprint to determine how to quickly give Acquia customers value in products.
In a total of four days, redesign the site architecture of Acquia’s main web-management product, and add in a Dashboard allowing users to more easily reach their goals of assessing site health and status.
Acquia’s product team (including UX) took part in a Google-style design sprint to determine a roadmap for its desired new product. The team took part in this four day process to brainstorm how to give our current users more value. While the entire concept of onboarding (or lack thereof in Acquia’s products) was determined to be a major problem, there were huge opportunities to improve value and faster learning in the product. These screens tackle the user’s need to see how the multiple sites they may be managing with this product (here called “Acquia Factories”) are performing and quickly address any issues.
For more information on this process, check out: https://www.thesprintbook.com/
The current “Acquia Cloud” does not have any onboarding directly in the UI to set up content like sites and applications. While other designers tackled this challenge, the current Information Architecture of Acquia Cloud needed to be reassessed.
Acquia Cloud’s interface consists of two main tabs. “Develop” and “Manage. The Develop tab allows the user to choose from their applications. (An appication is a single codebase that may be shared by many sites.)
The “Manage” tab allows a user to choose an organization for which to edit user and permissions. This is confusing to users because Organizations are actually collections Teams (Users) and Applications, yet they appear in the same hierarchy as applications when referencing the develop tab, and these definitions are explained nowhere.
A much more common desire for users is to see the health of individual applications or sites, rather than manage users, yet this real estate is not utilized for these tasks.
Another major user problem is the lack of “site awareness.” After an application is chosen with a click, a user can see their environments but nowhere can they navigate to a site or view information about it.
Two solutions were created to add immediate value to the user of the new product concept “Acquia Factories.”
Each UX Designer was tasked with designing high-fidelity screens in the final two days of the sprint. Following are the resulting solutions for the issues mentioned on the previous tab that are further outlined below.
This prototype was tested with users who gave extremely high ratings of their opinion of the funtionality, UI and usability of the product based on these designs. (An average of 6 on a scale of 1-7, 7 being most positive.)
After completing the onboarding process and being led through the creation of their first site, a User will land on a page similar to the current “Applications” page, but will only see their sites. They will see a modal similar to the one shown here if it is their first time on the page.
Here they can see top level information about their site or sites’ performance and navigate or star commonly used sites. The right nav shows placeholder content but the user should see helpful onboarding information or tips to fully utilize this page.
When clicking on their second tab now called “Monitor,” the user sees another introductory modal. (The UI styles should match eachother on the Develop and Monitor tab in the final design, but we were testing preferred styles.)
The functionality of this page is now suited for the user’s desire to see top level site health. It defaults to showing data for all sites across all applications, within a user’s organization. (The user should only have one organization on first log in).
Info icons assist when clicked for any section a user cannot understand.
When tested, users preferred that these panels are draggable to their preferred view order. Some preferred to see dummy information populated on the panels where no information was yet available, and to some it was confusing. In the final design it would be removed.
The “usage” tab was also a bit confusing, as the current structure of “applications” and “subscriptions” as well as the pricing model at Acquia is not clearly defined internally, making it difficult for UX to externally communicate.
A large quick-win for the new “Acquia Factories” is the “Mega Nav.”
This solves the user’s problem of confusion over definitions of terms like “Application” and “Organization,” by visually nesting each term. It also allows for the user to view very specific subsets of information about their sites and applications from anywhere and without being overwhelmed by excess information.
For example, if a user wanted to view data about the Production Environment for their one site “Pied Piper USA, they could click it in the site column of the nav here, and be directed to the page below.
Where there is the potential for user sot have hundreds of sites within an application, a Search bar should be added to the final design similar to this navigation in Google Analytics.
Data shown for individual sites would also show a “Tasks” panel, and include a left hand nav so that users could easily redirect to a specific panel on that page without scrolling.