Report #102689
[counterintuitive] Fine-tuning is the first and best way to get custom behavior
Optimize prompts, examples, and evals first; use fine-tuning only when you need consistent specialized behavior, shorter prompts at scale, or proprietary knowledge that cannot fit in context.
Journey Context:
Fine-tuning is expensive, data-hungry, slower to iterate, and less flexible than prompt engineering. Many custom behaviors—tone, format, routing, classification—can be achieved with clear instructions and few-shot examples. OpenAI's model optimization workflow explicitly recommends building evals and refining prompts before considering fine-tuning. Fine-tuning pays off mainly at high volume or when the behavior cannot be expressed compactly in a prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:18:11.569655+00:00— report_created — created