Customer Meeting Notes #1

Customer Meeting Notes 1

Date: 18.02.2026 16.35-17.05
Participants:

• Akif Emre Biçen
• Furkan Kaan Biçer
• Beyza Nur Deniz
• Kutay Eroğlu
• İbrahim İlter
• Enes Hamza Üstün
• Alper Vural

---

1. Agenda

1. Decide the time and location scopes
2. Define the target audience
3. Clarify whether there would be a login system
4. Clarify whether the system would be interactive (commenting, liking, saving)
5. Clarify how to validate incorrect or irrelevant information
6. Ask should the system motivate the people to create content
7. Clarify whether people can upload general historical information

---

2. Key points discussed

• Discussed what is the time and location scopes
• Discussed how to implement a validation system and what to restrict
• Discussed about where focus more such as, core functionalities, stories and emotions
• Discussed about interactivity

---

3. Decisions

• Decided there would not be time and location restrictions. Generally, restrictions should be minimized. (1.1)
• Decided that the main focus would be the stories. People should upload the information they emotionally engaged. Therefore, the focus will be on more specific and small areas. (e.g. Not the stories about the conquest of Istanbul, but the park that someone used to play) (1.1, 1.7)
• General, brief, and verifiable information can be added about the locations where people share their stories, but this factual data must not overshadow the personal stories and emotions themselves. (1.7)
• Validation requires active human intervention. Therefore, a community-driven validation system should be utilized. It is acknowledged that completely preventing the sharing of irrelevant content is impossible. (1.5)
• Interactive features (engagement functions) must be included. Also, there should be a system to motivate the people to upload content. (1.4, 1.6)

4. Suggestions

• The primary focus must remain on the core functionalities.
• A clear distinction needs to be established between data representing a specific "point in time" versus a "time period," and we must decide how to integrate this distinction into the system.
• The labeling/tagging structure for posts must be defined, along with how different content entries will be linked or correlated with one another. This is also the basis of the recommendation system.