Stakeholder Meeting Notes #1

Stakeholder Meeting Notes 1

Date: 09.03.2026 20.00-20.40
Participants:

• Utkan Gezer
• Muhammed Mustafa Öztürkmen
• Muhammed Efe Özavcı
• Akif Emre Biçen
• Furkan Kaan Biçer
• Beyza Nur Deniz
• İbrahim İlter
• Enes Hamza Üstün
• Alper Vural

---

1. Agenda

1. Present the current concept and core features of the application to the customer
2. Clarify the geographical scope of the platform (global vs. local)
3. Discuss how stories will be structured (location-based, event-based, or timeline-based)
4. Clarify how multiple stories at the same location will be displayed on the map
5. Discuss how users can interact with stories (comments, collaborative storytelling)
6. Explore ways to motivate users to create and share content
7. Discuss anonymity options for users sharing stories
8. Discuss systems to prevent misuse or low-quality content

---

2. Key points discussed

• The team presented the application concept.
• The main concern discussed was how to motivate users to post stories.
• The possibility that users may hesitate to share stories under their real identity was raised, suggesting that anonymous or pseudonymous posting options may be useful.
• The idea of temporal concentration of stories was discussed (e.g., stories related to war periods or specific historical events). Visualizing this as a story density map similar to a weather map was suggested.
• The concept of collaborative storytelling was discussed, where users could extend an existing story (e.g., “I was also there”).
• Concerns about map usability were discussed if there are too many pins (e.g., hundreds of thousands in large cities).
• Possible solutions such as region-based grouping or clustering of pins were discussed.
• Several engagement mechanisms were discussed to motivate users to contribute content.

---

3. Decisions

• The platform will remain location-based, and stories related to the same place will be grouped under the same location.
• Multiple stories associated with the same location should be viewable as a list or chronological flow.
• The system should support rich media stories, including text, audio, images, and video.
• The interface should support map clustering or region-based grouping to avoid overwhelming the user with too many pins.
• Users should be able to comment on stories, potentially contributing additional perspectives to the same narrative.
• Some form of anonymity option should be considered to encourage users who may hesitate to share stories under their real identity.

4. Suggestions

• Implement story density visualizations that show when stories are concentrated in certain time periods (e.g., similar to a heat map or weather map).
• Consider supporting collaborative storytelling, where comments can evolve into extended story contributions.
• Use gamification mechanisms to motivate users: Badges for contributing frequently in a topic or location, reputation systems similar to social platforms.
• Introduce notification mechanisms to encourage engagement (e.g., responses to posts, reactions).
• Allow users to create personal collections or bookmarks of stories they find interesting.
• Consider allowing private notes or personal story logs, although this may reduce public participation and should be evaluated carefully.
• Implement a reputation or reporting system to reduce misuse and low-quality content.
• Ensure the map interface supports clustered pins or region-based exploration, so users can easily explore stories in dense areas.