Prompt engineering basics for non-developers.
You do not need a CS degree to write good prompts. You need a frame for what a prompt actually is. Here it is.
6 min read
Most people treat a prompt like a Google search. They type a question and accept the first answer they get. That works about as well as it sounds.
A prompt is not a search query. It is an instruction to a system that processes language. The difference between those two mental models is the difference between mediocre output and exceptional output.
The instruction frame
When you write a prompt, you are giving instructions to a tireless, talented junior staffer who knows everything you have ever asked a teacher but has no context for your specific situation. Everything in your prompt is the universe they have to work with. Everything not in your prompt is invisible.
That mental model produces better prompts.
The five elements of a good prompt
A workmanlike prompt has five things. Not all five are required for every prompt, but if your prompt is producing garbage, check whether you missed one.
1. The role: "You are a senior procurement analyst at a federal agency..." 2. The task: "Read the attached SOW and produce a one-page summary..." 3. The audience: "...for the contracting officer's review..." 4. The constraints: "...in plain English, under 400 words, no jargon..." 5. The format: "...as a Markdown document with three sections: Scope, Risks, Recommendation."
That is the entire formula. Practice it on real work tasks until it becomes automatic.
The most common mistake
Asking a question and accepting the first answer. The model is not trying to be right; it is trying to be useful given what you gave it. If the answer is bad, the prompt was bad. Iterate.
The iteration loop is: write prompt → read response → identify what is wrong → revise prompt → repeat. Three iterations is normal. Five is fine. If you are still iterating after ten, the problem is upstream of prompting.
What to do this week
Take one prompt you wrote this week. Add the role. Add the audience. Add the format. Re-run. Note the difference. That is the entire skill.
The book Prompt to Product is fifteen chapters of exactly this, at depth.