To simplify this process, we added an "Add to Timeline" icon. This approach users to navigate to the page "Add to timeline" with only one click.

While we had a UI system that accelerated design and supported consistency, a more comprehensive system could have reduced the time spent explaining component usage to developers. Even though building it would require significant upfront effort, it would streamline workflows, allow for quicker usability testing, and ensure consistency across iterations.

During user interviews, I discovered the challenge of designing unbiased questions, particularly when discussing personal experiences. Additionally, giving examples could introduce another type of leading question, as participants may tend to answer in a way they think aligns with what we want to hear.

During the feedback loop with developers, I learned that no matter how detailed the documentation, there can still be discrepancies between the design and the final output.  Continuous discussion and close collaboration with developers are essential to minimizing these discrepancies and ensuring the design is implemented as intended.

While our collaboration was productive, sustaining momentum without a profit-driven incentive proved challenging. In future side projects, I’d establish clearer milestones, regular check-ins, and defined ownership early on to keep a volunteer-based team engaged and moving forward.