TimeSync
Our product is a scheduling and calendar tool designed to assist remote workers in coordinating meeting schedules across different time zones.
Problem Background
At the onset of the course, we attempted to schedule our availability for meetings. However, we quickly realized that the two options needed to be clearer lacked user intuitiveness, and could have indicated our available times. Additionally, navigating the browsers proved to be challenging.
User Pain Points & Research Insights
Using Google Forms in the Co.Lab Discord chat and across our social platforms, we identified various categories of prospective users. Over 11 user interviews revealed a common challenge: many cross-functional teams struggle with time zone meeting management. This finding underscores the pressing need for a solution that streamlines scheduling across diverse time zones, ensuring efficient collaboration and eliminating the frustrations associated with coordinating meetings.
Feedback
Based on the user survey, another conclusion we can draw is the importance of user-friendly and intuitive scheduling tools. Users may have expressed frustration not only with time zone management but also with the complexity and lack of clarity in existing scheduling options. This suggests a need for solutions that prioritize simplicity, ease of use, and clear communication of availability to facilitate smoother coordination of meetings.
Solution Explanation
Based on our target users' pain points, we recognized the importance of addressing their needs with the following key features:
- An intuitive and easy-to-use interface for seamless navigation and efficient scheduling.
- Integration of time zone management to facilitate smooth coordination of meetings across different regions.
- Automatic email notifications confirming meeting times in the designated time zone, ensuring clarity and minimizing scheduling errors.
Lofi & Hifi Mockups
LoFi
MidFi
High-fi Prototype: LINK
Iterative Design Learnings
1. Shaping the MVP: I began by crystallizing our Minimum Viable Product (MVP), identifying core functionalities essential for user engagement. This process illuminated the importance of prioritizing features that directly address user pain points.
2. From Lo-fi to Hi-fi Designs: Transitioning from low-fidelity wireframes to high-fidelity designs was a pivotal phase. It underscored the significance of visual appeal and user experience, ensuring that our interface resonates with users intuitively while maintaining functionality.
3. Active User Testing: Engaging in rigorous user testing on our current UI was enlightening. It reinforced the value of user feedback in refining our product iteratively. By observing how users interact with our interface, we gained valuable insights into areas for improvement and optimization.
4. Incremental Growth: Witnessing our vision gradually materialize, step by step, has been incredibly inspiring. Each iteration brings us closer to our goal, reinforcing the iterative nature of the design process. Embracing this iterative approach allows us to evolve our product organically, aligning it more closely with user needs and preferences.
5. Refinement and Incorporation of Feedback: Our focus shifts towards refining our product based on user feedback. This phase underscores the importance of responsiveness and adaptability in the design process. By incorporating user suggestions and refining our solution iteratively, we can ensure that "Time Sync" evolves into an even better version, tailored to meet the diverse needs of our users.
In essence, it has been a testament to the power of iterative design. With each iteration, we inch closer to realizing our vision, propelled by continuous learning and refinement. As we embark on the next phase of our journey, we remain committed to the principles of agility, empathy, and collaboration, knowing that our collective efforts will pave the way for a more seamless and efficient meeting experience with "Time Sync."
Technical challenges
- What was the hardest part of development? The most difficult part is time constraints
- Does your app have any scaling issues? No
- What are some key takeaways? It is still a work in progress, I am looking forward to implementing more functionality and having some takeaways from the project when it is finished, right now I am enjoying the process of making it.
Implementation Details
Technical Implementation:
- The application is currently hosted on Firebase. The frontend is developed using React, utilizing JavaScript for scripting. Backend development is ongoing, and specific frameworks and technologies for this aspect are yet to be determined.
High-Level Journey of a Request:
- Utilizing React as the frontend framework was a strategic choice due to its familiarity and versatility among the development team. While the backend is still under development, the frontend serves as the primary interface for users, facilitating actions such as creating, retrieving, updating, and deleting data within the application.
Technical Challenges:
- Time constraints emerged as the most significant challenge during the development phase. Despite this hurdle, progress has been made in creating a functional frontend interface. At present, the application does not encounter any scaling issues. As development progresses, insights gained from the project's evolution will inform future enhancements.
Future Steps
Incorporating a video call feature stands as a pivotal advancement, fostering seamless collaboration and enhancing meeting management capabilities within the application. Moreover, extending the existing reminder feature offers the potential to address user needs more comprehensively, ensuring timely meeting notifications and enhancing overall productivity. Feedback from users will guide the prioritization and implementation of these enhancements, aligning with our overarching goal of supporting remote workers and optimizing collaborative workflows.
Images Mock-ups
Sign-up process & Monthly, Weekly and Daily View of Calendar
Time zone view & Add availability feature
Learnings
Product Manager Learnings:
Tami Oluwaseyi
Designer Learnings:
Sua Lee
Designer Learnings:
Jo Sturdivant
- Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
- Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
- Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.
Developer Learnings:
Catrina Ryan
Developer Learnings:
Vanady Beard
&
As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.
Developer Learnings:
Stephen Asiedu
&
As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.
Developer Learnings:
&
Developer Learnings:
Maurquise Williams
&
- Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
- Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
- Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.
Developer Learnings:
Jeremiah Williams
&
All in all this experience was very awesome I learned that in coding with others being transparent is key
Developers Learnings:
Justin Farley
&
I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.