Following the transition of the workplace to an online environment, the communication among employees has become challenging, leading to difficulties in establishing a sense of bonding and connection among them.
1. Asynchronous Brainstorm: Foster creativity and idea generation regardless of time zone differences.
2. Disappearing Chat: Engage in spontaneous conversations with a lightweight and informal communication experience.
3. TeamView + Time Zone:
Access detailed profiles of colleagues, including time zones and contact info.
We conducted interviews with six individuals who are currently employed in a hybrid work setting, aiming to gain insights into their experiences within this environment. Our objective was to gather information and determine whether they encounter any challenges while working in a hybrid model. Additionally, we sought to identify the advantages and disadvantages of this work setting and explore potential areas for improvement to enhance their work experience in the hybrid setting.
Some individuals feel disconnected in the hybrid work setup.
Andy highlighted the challenge of forming meaningful connections.
Ryan P Fong expressed frustration over the disappearance of casual interactions and easy chats.
Miscommunication is a significant issue, especially among remote teams in different time zones.
Waiting for responses and the need for clearer communication channels and better planning were highlighted by Jeremy T.
Improved communication tools are needed, with frustration over Slack's overwhelming notifications and channel management expressed by Ryan F.
Finding tools that balance convenience and usability became a priority.
Time zone coordination is crucial, with the importance of clearer channels and better scheduling emphasized by Jeremy T.
Privacy in conversations is a concern, with a desire to avoid sharing every thought on Slack expressed by Ryan F.
Respecting privacy and providing a secure space for discussions are crucial for fostering trust and open communication.
Better ways to initiate and reach out passively
Better ways to manage notification
Privacy in conversation
Explored possible features
We created an information architecture flow to organize and structure information in a logical and user-friendly manner. By developing a clear flow, we aim to enhance the user experience and make it easier for individuals to navigate and find the information they need efficiently.
Final flow for the web app
We created low-fidelity wireframes for the three features we finalized on. Include the disappearing chat, asynchronous brainstorming, and team view. The purpose of creating low-fidelity wireframes was to provide us with a tangible representation of how these features could integrate into a cohesive web app.
Taking inspiration from our wireframe designs, we transformed them into more polished and interactive representations, both in low-fidelity and high-fidelity formats. Starting with the low-fidelity prototypes, we focused on capturing the essence of our design concepts while maintaining a simplified and functional interface. We then create high-fidelity prototypes based on what we’ve already built. At this stage, we incorporate material UI into our design.
The prototype includes several key pages, First, we have a landing page that introduces our SyncMate web app and highlights its key features. Next, we've designed login and sign-up pages to facilitate a seamless onboarding process for new users.
To ensure effortless navigation within the app, we've incorporated a well-designed navigation bar. This feature allows users to switch between the three main features we've developed: the disappearing chat, asynchronous brainstorming, and team view.
When we started the project, we had assumptions about the specific pain points users faced and the potential solutions to address them. However, through our research and user interviews, we discovered new nuances and perspectives that shaped our understanding. This experience highlighted the significance of gathering firsthand insights from users to inform our design decisions, rather than relying solely on assumptions.
If we could do anything differently, we would consider conducting more extensive user research to gather a broader range of perspectives and validate our design choices. Additionally, we would prioritize user testing and iteration throughout the development process to ensure that the final product truly meets the needs and expectations of the users.
If the project continued outside of class, our next steps would involve conducting usability testing with a larger user base and incorporating their feedback to further refine and enhance the features.