Overview
Waggle is an AI co-pilot that helps managers know exactly what to do and when to do it to drive their team to perform, by leveraging untapped data, behavioral science learnings and management best practices.
Waggle is currently working on a go to market strategy and as part of that effort they are seeking support to redesign the website calendar page to create a clear call to action that results in an increase to user engagement.
Introduction
To enhance the user experience, our team will analyze the latest design through competitive and heuristic evaluations, aiming to uncover challenges and identify ways to simplify the process. Based on our findings, we will propose redesign recommendations to demonstrate how the user experience can be improved. Then we will conduct additional testing and make iterative refinements. Finally, designers will compile all the deliverables and findings into an easily comprehensible package, facilitating their integration into future projects.
Problem Statement
Waggle has designed a product to assist new managers in organizing their day, however it is burdened by issues of drop-off and user engagement, hampering its ability to effectively support and engage users. Resolving these challenges is crucial to deliver a more valuable and impactful solution for new managers seeking efficient time management and organizational support.
Roles and Responsibilities
Throughout the project, every team member actively participated in all activities, making significant contributions in various key areas. The following highlights their noteworthy involvement:
- Clayton Lunce:
- Interview Guide
- Persona development
- Cody Cameron:
- Prototyping
- Heuristic research
- Hannah Caruso:
- Wireframing
- User testing
Research
In our project, we aimed to improve the calendar page by focusing on two key areas: helping users recognize, diagnose, and recover from errors, and enhancing the flexibility and efficiency of use. We proposed using clear and user-friendly error messages, expressed in plain language without error codes. These messages would precisely indicate the problem and provide constructive suggestions for a solution, enabling users to understand and resolve errors effectively.
Heuristic Evaluations Full Report
User Persona
-
Design the employee management system with an intuitive interface to support new managers who may be unfamiliar with its features and functionalities.
-
Possible Unorganized Users: Include task management, reminders, and scheduling tools to help users stay organized. Emphasize efficient data organization and retrieval for improved productivity.
-
Provide comprehensive training resources, such as user guides, video tutorials, onboarding sessions, and ongoing technical assistance. Ensure clear and concise documentation for quick reference.
Wireframes
Original Screen
Our initial focus was on the calendar page, which we deemed to be the most significant screen. From there, our objective was to seamlessly incorporate some dashboard features into the overall design. This approach allowed us to strike a balance between the functionality of a dashboard and the visual appeal of the frame.
First Low Fi Screen
We identified four crucial sections to concentrate on during our discussion, which included the header, two sections of the body, and the bottom corner. This was the outcome of our brainstorming session, where we generated ideas and explored various possibilities.
High Fidelity
As a team, our focus was on enhancing the visual hierarchy in our user interface (UI) design for the Create Event feature, Getting Ready for Your Day, and the overall performance score. To maximize visual real estate, we initially utilized a meeting density button instead of a banner.
In our ongoing efforts, we further enhanced the gamification aspect of the performance score by incorporating additional tabs and relocating the meeting density feature to the top. Additionally, we introduced an emoticon to allow users to express their feelings about their day, ensuring a more comprehensive and engaging experience.
Lastly, we refined the performance score by converting it into a percentage that represented the number of meetings completed per day, while simplifying the emoticons at the top. We recognized that creating a performance tab would require a separate dashboard, which we planned to address in future developments.
User Testing
Critical Changes
1. Rename "Post meeting notes" to "Action Items" - Participant 1 from Clayton Lunce's group suggested that the term "Action Items" would be a more appropriate name for the feature. This change can improve clarity and align with user expectations.
2. Improve clarity on the source of "Focus" data - Participant 1 from Clayton Lunce's group expressed confusion about the origin of the "Focus" data. Providing clear information about where this data comes from can help users understand and trust the feature.
3. Allow saving notes during meetings - Participant 2 from Clayton Lunce's group asked if users could save their notes as they go during a meeting. Enabling this functionality can enhance user experience and ensure that important information is not lost.
4. Clarify note sharing capabilities - Participant 3 from Clayton Lunce's group inquired about the ability to share notes. Providing a clear explanation of how users can share their notes will improve collaboration and the usefulness of the application.
Low Priority Changes
1. Overwhelming event title screen - All participants mentioned that the event title screen appeared overwhelming initially. Consider redesigning this screen to provide a more user-friendly and intuitive experience.
2. Visual hierarchy - All participants noticed a visual hierarchy issue where the emphasis shifted from "Waggle" to "Well-being" and then to "Your Day." Ensure that the visual hierarchy aligns with the importance and relevance of the elements.
3. Clutter in frames during meetings - Participant 1 from Clayton Lunce's group expressed that reducing clutter in frames improved their reaction to creating and launching a meeting. Evaluate the meeting interface to minimize unnecessary elements and enhance the user's focus.
4. Meeting feedback specificity - Participant 4 from Cody Cameron's group felt that the end-of-meeting feedback needed more specificity to be valuable. Consider providing clear guidelines or prompts to elicit more specific feedback from participants.
5. Storage and sharing of notes - Participants from both groups expressed confusion or curiosity regarding the storage and sharing of notes. Provide clear information and intuitive features to address these concerns and improve the usability of the note-taking functionality.
6. Well-being action tool - Participant 5 from Cody Cameron's group found the well-being action tool helpful. Consider refining and promoting this feature to enhance user engagement and well-being.
Final Prototype
Changes? or what we would do next time?
Introduction of User Flows
Improving Task Completion: If we had focused on creating user flows from the beginning, it would have greatly benefited our project. Visualizing the steps users need to take to achieve their goals through user flows would have allowed us to identify any unnecessary complexities or obstacles that could hinder task completion. This early understanding of the user journey would have helped us prioritize what was most important to focus on and ensure a smoother and more efficient user experience.
Collaborative Design and Communication: Looking back, incorporating user flows into our project would have greatly facilitated collaborative design and communication among team members. This would have fostered better communication and collaboration throughout the design and development process, enabling us to work together seamlessly and make informed decisions based on a clear understanding of the user experience.