Prompt engineering lets you shape AI output to match your professor's style quickly through examples and instructions, while fine-tuning requires more data but captures deeper patterns in how they prioritize arguments and structure thinking. Prompt engineering suits most courses; fine-tuning makes sense when a professor's preferences are intricate and consistent.
When AI isn't working quite right for your needs, you have two options: prompt engineering (change how you ask) or fine-tuning (retrain the AI on your specific data). They sound similar but work completely differently, and most productivity users will only need the first.
Prompt engineering is adjusting the question, context, and instructions you give to the AI. It's free, instant, and changes only how the existing model responds to you. Fine-tuning is taking an AI model and retraining it on examples of your specific work so it learns your patterns. It's expensive, takes hours or days, and results in a customized version of the model.
For 95% of productivity work, prompt engineering solves your problem. If the AI isn't giving you what you want, it's usually because your instruction wasn't clear enough or the context was missing. Better prompts fix this instantly.
Example: AI is summarizing your meeting notes poorly. Instead of fine-tuning, try: "Summarize this meeting using three sections: decisions made, action items with owners, and blockers to resolve. Keep each section under three bullets." That specificity often solves the problem without retraining anything.
Prompt engineering handles 90% of "but it doesn't quite work for me" complaints. Unclear outputs? Add examples to your prompt. Too long? Specify length. Wrong tone? Describe the tone you want. Missing context? Include it upfront.
Fine-tuning is for edge cases where the model fundamentally doesn't understand your domain. Maybe you work in highly specialized field with unique terminology, and the AI constantly misunderstands. Or you have a very specific output format (like a unique project planning template) that you apply 100+ times and want the AI to learn automatically.
Real example: A design agency might fine-tune a model on past project briefs so the AI generates briefs in their exact format and language automatically. But they're doing this for hundreds of projects. For one person trying to organize their tasks better? Fine-tuning is overkill.
Another factor: fine-tuning requires clean training data. You'd need dozens or hundreds of examples of the exact work you want the AI to replicate. Most individuals don't have that volume of historical data organized well enough to train on.
Fine-tuning typically costs money per usage and requires API access. OpenAI charges for fine-tuning. Anthropic offers it but it's not cheap for casual use. Meanwhile, prompt engineering is free. Before even considering fine-tuning, you should have exhausted every prompt engineering approach.
The sweet spot: use prompt engineering first, always. Build custom instructions (often free) for your AI tool. Only if you're repeatedly running the same task and the AI keeps missing something despite good prompts, then explore fine-tuning. For most people, that never happens.
Try this: Think of an AI task that feels slightly off. Instead of redesigning your approach, redesign your prompt. Add one of these: specific examples of what you want, the exact format you need, constraints on length or tone, or step-by-step instructions. See if that fixes it without changing anything else.
Peri can explain this concept, give practical examples, help you decide whether it applies to your situation, or recommend a journey if appropriate.
Explore related journeys or tell Peri what you're working through.