GOZIO CONTENT MANAGER

Gozio is a healthcare-focused indoor wayfinding company working to improve the patient experience at U.S. hospitals. After 5 years of sustained growth for the company and an evolving group of customers, it was apparent the content management platform (CM) need an update. While the number of customers grew, the original platform mostly supported the smaller healthcare networks of the initial sales cycles. Our aim with this redesign was to create a flexible system that allowed the company to scale and the customers to have more control of their content.

Goals

Create a scalable system for networks large and small
Address design and technical debt
Solve usability and accessibility issues

Contributions

Led design efforts for new content management platform
Established design processes
Created proactive user feedback cycle

Research

Upon arriving at the company, I noticed Gozio lacked a formal feedback loop for user validation. Most feedback from users occurred post-launch in an ad-hoc style.

To better understand Gozio users, I spent much of the first month interviewing the users of CM from different healthcare systems. (Some of these customers also later offered feedback as I worked through different concepts for the platform.) Their feedback helped our team identify the following problem themes:

Navigation and search
System setup and design (customer onboarding)
System messaging and documentation
Content
- Content flexbility
- Content editing
- Location grouping
- Location visualization
- Activity log
- Content hierarchy
- Routing and mapping issues

Explorations

When exploring concepts for CM, there were a number of different approaches to consider. I explored different navigation structures, POI groupings and user flows for different editing paths.

Navigation patterns

Location editing

Design

While working on early explorations, the mobile team was working on search improvements that required heavy CM support. We made the decision to start developing this new functionality on the new platform, rather than building on the old infrastructure. This allowed our team to build the foundation for the next-generation of CM and test some of the new designs in the real world. As I worked through the design for different sections within CM, this feedback was immensely helpful, especially for the editing of locations/POIs (the largest aspect of the redesign).

Navigation

After testing some of the above navigation patterns, we landed on two primary navigation components: app bar and sidebar menus. Both of these are persistent on the screen. The sidebar helps navigate to different sections or profiles of the content manager while the app bar is contextual to the page on which the user is working.

Explore panel programming

One of the most-requested features from customers was better visualization of content changes. We piloted this preview idea with explore panel programming. The explore panel allows app users to discover different locations within a network or specific hospital campus. This programming feature within CM allows customers to manage these groups of locations and alternate between two established template styles for the explore panel. This pattern was later reused for the bottom navigation bar and the dashboard.