Customer Insights Report of Milestone 1 Meeting - bounswe/bounswe2025group5 GitHub Wiki

Customer Insights Report of Milestone 1 Meeting

Overall, the presentation went smoothly without any technical issues, and both the client and their assistants seemed visibly pleased throughout by smiling and reacting positively. At the end, the client commented, “Great, nice, scenarios are good also,” showing general satisfaction with the flow and content of our demo. We also received a few valuable feedback points that will guide our next iterations:

Customer Feedback:

  • The client focused on how challenge creation ideas emerge, suggesting that users might organically propose new challenges (e.g., someone posting “Kilyos is a mess could trigger a cleanup challenge).
    • Our Q&A clarified that this is already supported through the “this place needs cleaning” feature.
  • For impact visibility, they mentioned that users are often motivated by seeing the results of their actions. For example, knowing “what difference did my challenge make?”.
    • We presented the Mobile → Profile → Reduction Statistics(Mock) section, which could be expanded in later milestones to visualize long term significance (e.g., total cleanups, reduction metrics).
  • Final feedback from the client was that “They covered everything,” confirming that all main expectations were met.

Internal Team Feedback:

  • For example, after completing a Bottle Cap Challenge, the impact could be highlighted more clearly by showing a visual like “Challenge completed: a wheelchair has been donated with a picture.”
  • The impact section could be enhanced by designing mock data with before–and–after representations.
  • We had already planned to implement a Report feature — adding a structured form with categories and optional fields would make it more effective.
  • If we include a color-blind–friendly palette, it should not compromise functionality or visual hierarchy.
  • The importance of supporting both Turkish and English versions across all pages was emphasized.
  • We noted to stick with potential performance aspects to improve, such as server RAM usage and mobile loading time, which drew our attention before the presentation.