2.0 KiB
2.0 KiB
Intake — mandatory questions before starting AI work
Ask (or confirm from context) before producing anything. Do not guess on 1-6.
Problem & value
- What exact decision or task should the system improve — and what happens today without it (baseline process, baseline numbers)?
- What does success look like as a measurable target (metric + threshold + evaluation window), and who signs it off?
- Is ML/AI actually required, or would rules, search or a simple heuristic meet the target? What was already tried?
- What is the cost of a wrong output (annoyance vs. money vs. safety/legal)? Which error direction is worse (false positive vs. false negative)?
Data
- Which data exists for this task (sources, volume, label quality, freshness)? Who owns it and may we use it for this purpose?
- Does the data contain personal or sensitive information? Which legal basis, retention and anonymization rules apply (GDPR, sector rules)?
- How will the production input distribution differ from the historical data (seasonality, new segments, upstream system changes)?
Solution constraints
- Latency, throughput and cost budgets per request? Online or batch?
- Where must it run (cloud/provider constraints, on-prem, edge)? May data leave the environment — is a hosted API (e.g. OpenAI/Anthropic) allowed, or is self-hosting required?
- Build strategy preference: prompt an existing model, RAG over private data, fine-tune, or train classically? Any hard vetoes?
Operations & governance
- Who operates the system after launch (on-call, retraining ownership), and which monitoring/alerting stack must it integrate with?
- Which oversight is required: human-in-the-loop, audit trail, explainability duties, EU AI Act risk class of the use case?
- How do users get informed they interact with AI, and how do they report bad outputs?
Existing material
- Which models, pipelines, feature stores, eval sets or prompts already exist in the company and must be reused or replaced?