Discovery & Requirement Analysis

This folder holds the instruments and methodology for the discovery phase of the PRIME PRODUCTS AI-first transformation: a structured, ~6–8-week sweep across all 15 departments to establish what the company actually does, where it hurts, and where AI can help — before anything is built.

What discovery produces

Output	Form	Lands in
Validated requirements	One REQ-NNN file per confirmed need	../../02-Requirements/_index.md
Process maps	SIPOC + swimlane (Mermaid), one process per file	05-Processes/ (created when first map lands)
Scored AI use-case candidates	Opportunity scores per the framework’s scoring model	../08-ai-portfolio/ai-use-case-pipeline.md
AI-readiness scores	5-dimension score per department	Department files in ../04-departments/_index.md
Data source inventory	Systems, files, Excel, email, paper per process	Feeds ../05-technical/rag-and-data-pipeline.md
Interview & workshop notes	Interview notes per session (English, per ADR-003)	Vault, via interview template

Documents

Document	Purpose	Audience / scope
requirement-analysis-framework.md	The complete methodology: week-by-week process, interview & workshop method, process mapping, pain-point analysis, scoring models, requirement capture	Discovery team (TPL + PRIME PRODUCTS champions)
questionnaire-all-employees.md	Baseline questionnaire for every employee (~109 people)	All employees, ~20–30 min
questionnaire-department-heads.md	Department-level view: mission, KPIs, process inventory, friction	15 department heads
questionnaire-management.md	Strategic priorities, decision latency, success definition	CEO / executives
questionnaire-technical-it.md	Infrastructure, SoftOne, M365, network, security reality	IT team
questionnaire-process-owners.md	Per-process deep dive — filled once per key process	Process owners
pilot-order-desk-discovery-plan.md	Information-gathering plan for the REQ-014 email-order-desk pilot	TPL discovery team
questionnaire-pilot-order-desk.md	CEO clarification-call agenda for the REQ-014 pilot — ✅ answered on the 2026-07-06 call, per-question answers inline	CEO, ~60 min
questionnaire-pilot-order-desk.el.md	Greek administration copy of the above (ADR-011) — English file is the master	Interviewer, in the room
interview-pilot-cylinders-2026-07-06.md	Phase-0 call done — distilled interview record: cylinders dept identified; process, volumes, pains, success criteria captured (raw transcript kept per ADR-012)	TPL discovery team
sample-order-emails-analysis-2026-07-13.md	Prime key-account discovery note — first sample-corpus batch (6 emails / 5 threads, 8–13 Jul) fully distilled from the underlying PDFs: four-tier party model, worked quote↔order match keys, and a hard technical constraint (M365 search connector doesn’t expose attachment content)	TPL discovery team

How outputs flow

1. Questionnaires (this folder) establish the baseline and flag hotspots.
2. Interviews and workshops (method in the framework) validate and deepen; notes are captured in English via the interview template.
3. Every validated need becomes a REQ-NNN file using the requirement template, with a row added to the requirements register in the same change.
4. Requirements that describe an automation/AI opportunity are scored (framework §7) and enter the AI use-case pipeline; those that graduate to build get an entry in the agent registry.
5. Department findings and AI-readiness scores update the per-department files in ../04-departments/_index.md.

Related

• Program plan and timeline: ../02-program/roadmap-12-month.md, ../02-program/work-breakdown-structure.md
• KPI definitions the discovery baseline must serve: ../02-program/kpi-framework.md
• Change management (discovery is also the first change intervention): ../02-program/change-management-and-training-plan.md