Validation Sessions¶
Purpose¶
These sessions were not all project-management meetings, but they generated inputs used in scoping, planning and monitoring. They capture qualitative evidence from consumers, digital experts, logistics / recycling contacts and informal external feedback.
The goal of this page is to keep validation evidence separate from the coordination meeting log while still making it traceable for the MVP / pre-event phase.
Interview and validation log¶
| Date | Type | Participants | Agenda | Summary and impact |
|---|---|---|---|---|
| 2026-05-08 | Consumer interview | Giada, consumer participant | Understand whether consumers scan QR codes and what product information they actually value. | The interview confirmed interest in clear product information, but also resistance to long explanations. This supported the rule that PackyTrace must return value quickly and avoid turning the scan into a reading task. |
| 2026-05-12 | Consumer interview | Giada, consumer participant | Test reactions to product scan, personal goals and expiry tracking. | The feedback supported personalization and expiry management as more concrete than generic sustainability claims. The team used this to strengthen the "does this fit me?" direction. |
| 2026-05-15 | Domain interview | Team member, logistics / warehouse contact | Explore traceability, product data, supply-chain information and operational pain points. | The interview helped the team understand that supply-chain traceability is valuable but too large for the MVP. It remained useful background for future B2B work, while the MVP stayed consumer-first. |
| 2026-05-20 | Consumer interview | Giada, consumer participant | Explore food goals, sustainability interest, label comprehension and app expectations. | The session reinforced that users want concise, actionable guidance rather than exhaustive DPP data. This contributed to excluding long product pages from the first experience. |
| 2026-05-27 | Consumer interview | Giada, consumer participant | Validate target range, scan motivation and perceived usefulness of Fridge / expiry features. | The interview supported the idea that users may scan only when the benefit is immediate. Fridge and expiry tracking were kept because they connect the purchase moment to home use and waste reduction. |
| 2026-06-03 | Digital expert interview | Mounir or team representative, digital expert participant | Collect feedback on data interoperability, ecosystems and DPP technical feasibility. | The discussion confirmed that data integration is a risk and should be handled through adapters and standards rather than hard-coded brand-specific logic. This influenced the architecture and technical planning. |
| 2026-06-06 | Informal user feedback | Team members, CERN / external contacts | Test whether external people understand the app idea and the AI-assistant angle. | Some people understood the scan-and-guidance value, but the full AI assistant was less clear. The team moved the AI assistant out of the MVP and treated it as a future option. |
| 2026-06-13 | Sustainability / recycling interview | Team member, recycling or DPP-related contact | Explore recycling, packaging information and DPP value beyond food choice. | The feedback was useful for long-term positioning, but it did not change the MVP priority. Sustainability remained part of the story, while personal usefulness and waste reduction stayed central. |
Impact on project management¶
| Finding | Management impact |
|---|---|
| Users want product information only if it is concise and useful at the decision point. | The MVP focused on scan speed, concise verdicts and a thin end-to-end consumer flow. |
| Generic sustainability and traceability information is not enough to drive repeated scans. | The project moved from a broad DPP-information concept to a consumer-first personal-utility concept. |
| Expiry and waste reduction are easier for users to understand than abstract DPP value. | Fridge and expiry tracking stayed inside the MVP scope. |
| Data integration is a technical and organizational risk. | The architecture adopted adapters, standards and controlled fallback behavior. |
| The full AI assistant was not clearly understood by external participants. | The AI assistant was moved out of the MVP and treated as a later option. |
| Supply-chain traceability is relevant but too large for the first phase. | Industrial traceability remained future B2B context, not MVP scope. |