Frame a business problem as a machine learning project
Turns a business goal into a well-posed ML problem with target, unit of prediction, success metric, baseline, and a go or no-go check.
The prompt
Help me frame a business problem as a machine learning project before I build anything.
Business goal: [e.g. "reduce churn among annual subscribers"]
How a prediction would be used: [who acts on it, when, and what they do differently]
Data available: [sources, history length, rough volume, label availability]
Constraints: [latency, interpretability needs, regulation, team skills, budget]
Work through:
1. Is ML needed? Could rules, a heuristic, or a simple analysis solve this? Say so if yes.
2. Prediction target: the exact label definition, the unit (customer, order, session), the prediction time, and the outcome window. Flag label leakage risks and ambiguous cases.
3. Problem type: classification, regression, ranking, forecasting, clustering - and why.
4. Metrics: an offline model metric that fits the use (e.g. precision at the top 10% if only 10% can be contacted) and the business metric it should move. Explain the cost of false positives vs. false negatives.
5. Baseline: the simple benchmark the model must beat.
6. Data requirements: features likely available at prediction time, class balance, and how to split data (time-based if appropriate).
7. Risks: feedback loops, fairness or bias concerns, drift, and what happens when the model is wrong.
8. Proof of value: how to test impact (pilot, holdout group, A/B test).
Return a one-page project framing doc with these sections, plus a go / no-go checklist and open questions marked [CONFIRM].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Data & Analysis prompts
What to fill in
- e.g. "reduce churn among annual subscribers"
- who acts on it, when, and what they do differently
- sources, history length, rough volume, label availability
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Identify the leading and lagging indicators for my business or teamSorts your metrics into leading and lagging indicators, links each lead to the outcome it predicts, and fills gaps in early-warning measures.
- Pick the three insights and five numbers my executives needRanks your findings down to the single most important insight, the top three, the five numbers to watch, and the biggest surprise.
- Break down why a number changed between two periodsA driver breakdown and bridge that shows exactly which segments, volume, price, or mix effects caused a metric to move.
- Check whether my data shows causation or just correlationSeparates trend, correlation, and possible causation in your analysis and gives you the strongest claim you can honestly make.