A homepage system to bring Culture Amp together into a cohesive platform
Using the success of 1-on-1s on Home to lead future design direction
Created a system to represent different modules in Culture Amp on the homepage
Discovery and definition
A consistent theme in my customer feedback from interviews as well as G2 reviews was that users found navigating and using Culture Amp to be a challenge. This difficulty was mirrored in our products' low adoption rates, contributing to an increased churn rate.
The '1-on-1s on Home' project demonstrated the Homepage's effectiveness in engaging and activating customers to different modules in Culture Amp. Given its success, expanding the Home page with more relevant content presented as a promising opportunity. My design challenge was to create a scalable system that could present a diverse range of Culture Amp content in a relevant, accessible and user-friendly way.
Concept development and testing
I began by examining the existing structure of the homepage, considering how it could accommodate additional content. I added more content to the homepage in a way that was cohesive with its existing design. I took the revised concept directly to our customers to understand their perception of the new layout and how the added information impacted the experience.
Wireframe & high-fidelity explorations
Users were critical of using prime home page space for less essential content like spotlight messages.
Managers emphasized the need for chronological information to help them for the week ahead on the homepage.
Based on the feedback, I felt like the existing layout which created a section for each area of the product would not be scalable in terms of showing the most relevant information at that time. I explored different ways to display this information by doing a lot of iterations. I also focused on presenting information clearly without overwhelming users.
A sample of some iterations I explored
I decided to implement a 'feed' concept for the Culture Amp homepage, a strategic choice aimed at minimizing user interaction while maximizing access to the most important insights. To validate this approach, I created a prototype based on the feed concept and tested it with customers to gather their feedback.
This prototype wasn't just a functional change; it also introduced newer interface elements. In collaboration with my manager, I explored these elements as part of a broader vision, contemplating a future look and feel for Culture Amp.
"I quite like that as feedback comes in, that you can quickly see what was said and if it is feedback that needs to be discussed, that you can add it to the one-on-one. I think that's a logical thing, right? You get some feedback and say cool, we need to talk about that. I like that a lot."
The design tested with customers
Users expressed strong approval for being able to access relevant stories directly on the homepage, eliminating the need to navigate through different sections of the product.
The feature allowing users to add a topic to a 1-on-1 discussion directly from the Homepage, such as a blocked goal, was especially well-received.
Customers began to view the Homepage as a guide for their next actions. Three customers specifically suggested replacing the “Recently viewed” section with a “What’s coming up” feature for better task prioritization.
Updates regarding blocked and inactive goals were deemed crucial. Managers highlighted that these prompts on the Homepage would aid in regular goal updates, addressing the challenge of consistently maintaining goal progress.
Going from concept to execution
Since the changes in the concept were so far from what the current Culture Amp experience is, I adjusted the designs to better match Culture Amp's current design language, while also laying the foundation for larger future changes by creating slices that could get us there in the future.
Three key slices leading to the final concept
Customer testing & technical conversations
Recognizing that these designs were becoming strong candidates for our roadmap, I initiated discussions with the technical team to determine how it could be delivered. This collaboration was crucial to ensure that our vision for the product's evolution was both technically feasible and aligned with our long-term objectives. I worked closely with our technical team to identify risks, advocate for features that were important for the user experience as well as adapting the design to fit technical constraints.
I also took the adapted designs to customers to get more feedback. This resulted in a further iteration to the design that which eventually made it to implementation. As this is still yet to be released, I anticipate that these changes will improve the user experience by encouraging user adoption and retention by making our platform more efficient and valuable.
"I think as a leader, you want things here that are gonna prompt you to ask questions. And this does that. Seeing people that have received feedback and seeing that Javier has an inactive goal gives me the prompt to ask a question. This is great."
Designs for the first release
Tenancies Act Bot
Thanks for visiting my little corner of the internet.
Made with ❤ in Melbourne, Australia