Writing Effective Prompts

Now that you’ve picked a task for AI, the next move is harder and more useful: asking for the output in a way the model can actually deliver. A vague prompt produces a vague draft, which will then waste twenty minutes editing—the exact time you were trying to save. A strong prompt brings the important details upfront so the first output is much closer to usable. This unit gives you a checklist for writing strong prompts, a method for turning fuzzy HR requests into specific deliverables, and a habit for improving prompts after a weak first try.

By the end, you’ll be able to:

• Use the Effective Prompt Elements checklist to structure clear, complete prompts.
• Translate vague HR requests into specific AI-ready deliverables.
• Refine weak outputs by tightening the prompt instead of simply asking the model to “try again.”

Treat every prompt like a brief you'd hand to a sharp new contractor who's never seen your organization. To get consistent, high-quality responses, include the seven Effective Prompt Elements—a checklist designed to eliminate guesswork.

• Task (what to do): State the exact job using a clear, directive verb. Instead of "look at this," use "draft," "summarize," "critique," or "announce."
• Context (background and goal): Provide the situation and why it matters—the policy, the company moment, the goal. This is where you supply what the model can't know, like your actual parental-leave terms.
• Audience (who it's for): Name exactly who will read it—all employees, just people managers, or external candidates. A nervous new hire and a seasoned manager need different framing.
• Constraints (what to avoid or limit): Spell out the guardrails: sensitive topic, no commitments beyond approved policy, no eligibility claims that aren't confirmed, no invented credentials, dates, or sources.
• Output Format (structure, length, tone): Specify the shape—a 200-word intranet announcement, three manager talking points, a confident-but-warm tone.
• Examples (samples of desired style): Paste two or three lines of real, on-brand copy as a style reference. This matches your voice better than any pile of adjectives.
• Success Criteria (how to judge the output): Define what "good" looks like—for instance, "a reader can name the policy, who's eligible, and the effective date after one read, with zero unconfirmed claims."

The reason this works ties back to how language models operate: they predict based on the context you give them. Sparse context leads to generic, off-policy predictions. A structured prompt that hits all seven elements leads to sharper, on-message results.

The checklist works for any prompt, but two elements are where HR prompts live or die. Skip them and you get fast, confident, unusable—or unsafe—drafts.

• Constraints are non-negotiable. Because the model will happily invent credentials, eligibility rules, awards, and policy details, spell out the fence every time: "Use only the facts and policy terms I provide. Do not invent statistics, certifications, dates, or sources, and do not promise eligibility or benefits beyond what's stated." That single sentence is often the difference between a draft you can send and a claim that lands a candidate or employee with the wrong information.
• Context carries your real policy. "Write something about parental leave" gets you the model's generic, plausible-but-wrong guess at a policy. Pasting your actual, approved policy terms (or labeling clearly-marked assumptions) is what makes the draft match your organization instead of the internet average.

Most HR requests show up vague. Your manager forwards a one-liner, or a stakeholder drops "can you draft something for the team" in Slack. The instinct is to type that vague phrase straight into the AI.

Don't.

Translate the vague request into the Effective Prompt Elements before you write the prompt. Let's look at an example:

• Natalie: Can you draft something for employees about the parental-leave policy change?
• Dan: Happy to. Quick check so I get it right the first time: what’s the goal here (Task), and who exactly is reading it (Audience)?
• Natalie: It’s an intranet announcement to all employees, about 200 words (Output Format). We need to explain the new leave length without promising any eligibility that isn't confirmed (Constraints).
• Dan: Got it. Should it sound like a warm peer or a more formal policy voice (Output Format/tone), and what counts as a good version (Success Criteria)?
• Natalie: Warm but clear. Good means a reader knows the new length, who qualifies, and the start date after one read.

Notice Dan didn't open the AI tool yet. He pulled the missing Task, Audience, Output Format, Constraints, and Success Criteria out of Natalie in thirty seconds. Because he has the elements ready, his first draft will be significantly more accurate and on-policy.

Even a strong prompt rarely lands perfectly. The first output is diagnostic data, not a verdict. Read it and ask which element was thin:

• If the tone is off: your Output Format or Examples were too vague.
• If the model missed the point: your Task wasn't specific enough.
• If it included a policy detail or credential it shouldn't have: your Constraints were too loose, or your Context lacked the real facts.
• If it's the wrong length or aimed at the wrong reader: your Output Format or Audience needs tightening.

Don't argue with the model in chat or ask it to "try again, better." Rewrite the prompt itself, tightening the elements that failed, and re-run. This gives you a reusable prompt for the future. Save the strong version in a team prompt library. Future-you (and the rest of the People team) will thank present-you. And remember the HR AI Safety Checkpoint: a human still verifies every fact before anything is recorded, shared, or sent.

The takeaway: prompts are briefs, not questions. Structure your request using the seven Effective Prompt Elements, then refine based on what the first output reveals. Next, you'll move into a live practice session where you'll apply these elements to a sensitive HR scenario.