A good AI brief has three layers, not one: the outcome, the method, and the manner

Most briefs describe the product and stop

Ask an AI to "write a price-increase email" and you have described exactly one layer: the product. So it fills in the other two on its own.

It picks a method (guess your prices, invent a reason, hedge everything) and a manner (corporate, apologetic, 6 paragraphs long). Then you spend 20 minutes fixing a draft you could have shaped in one sentence up front.

The short version of this skill lives in our primer on how to describe what you want to AI: outcome, facts, voice. This is the deeper version. A full brief has three layers, and the middle one, the method, is the layer almost nobody writes down.

• Product is the finished thing. The outcome, the format, the length, the hard constraints.
• Process is the route to it. What steps to take, what to use, what to skip, and whether to check with you before acting.
• Performance is how it feels. The role the AI plays, the tone, how hard it should push back, and when it should ask a question instead of guessing.

Think of it as briefing a new hire. You would not just say "send the customers an email." You would say what the email needs to do, how you want it handled, and how you want them to sound doing it.

Layer 1: the product, or what done looks like

This is the layer you already reach for, so the fix here is precision, not effort. Vague products get vague drafts.

• Name the format and the length. "A 4-sentence email," not "an email." "A 3-row table," not "a summary."
• State the hard constraints. No discount offer. No apology. Under 120 words. One call to action. These are the lines the AI must not cross.
• Point at the facts, do not retype them. Your actual prices, your actual effective date, your policy, not a guess at any of them. If those live in files the AI reads first, your brief just points at them. Pointing instead of retyping is the entire argument for a business knowledge base.

Layer 2: the process, or how it should get there

This is the layer that separates a usable draft from a lucky one. The process tells the AI which route to take, and, just as important, where to stop and ask.

• Say what to use. "Base the reason on the supplier-cost note in the project files, not a generic inflation line."
• Say what to avoid. "Do not quote a specific percentage. Do not promise it will not happen again."
• Say whether to ask first. "If you are not sure which customers are on the old rate, ask me before you draft. Do not guess the list."
• Say when to check in. For a multi-step job, "show me the outline before you write the full thing" saves you from a polished draft built on the wrong plan.

Process is also where you decide how much rope to give. A tightly scripted process is right for anything customer-facing or financial. A loose one is right when you want the AI's judgment, which the next section covers.

Layer 3: the performance, or how the exchange should feel

Performance is the layer people skip entirely, and it is why AI output so often either rambles or drowns you in hedges. You are casting a role.

• Give it a role. "You are my operations manager, not a copywriter." A role sets a hundred small defaults at once.
• Set the tone with an example, not adjectives. Paste a real email you were proud of and say "match this." One sample teaches more than "warm but professional."
• Tell it how hard to push back. "If this price increase reads as too steep, say so." Otherwise it agrees with you by default, which is worthless.
• Tell it when to ask versus proceed. "Ask me a question if anything is unclear" turns a confident guess into a quick clarification. For low-stakes work, the opposite: "just draft it, do not ask."

Before and after: one real brief

The task: email past customers about a price increase for a small landscaping business.

Before (product only): "Write an email to my customers about a price increase."

You get a generic, over-apologetic email with a made-up percentage and a promise you never authorized.

After (all three layers):

• Product. "A 5-sentence email to existing weekly-mowing customers. Announces the new rate takes effect August 1. Under 120 words. One clear line telling them the price and the date. No discount, no coupon."
• Process. "Use the new rates in the pricing file. Base the reason on rising fuel and labor cost, the way I noted it in the project. Do not invent a percentage. If you cannot find the August rate, ask me instead of guessing."
• Performance. "You are the owner writing to loyal customers you know by name. Match the tone of the email I pasted below. Be direct, not sorry. If the wording sounds defensive, flag it."

Same tool. The second version needs one light edit instead of a rewrite, because you shaped all three layers before it wrote a word.

A reusable brief template

Keep this where you write. You will not need every line every time, but the prompts stop you skipping the layers you always forget.

The two ways a brief goes wrong

More detail is not automatically better. Over-brief one layer and you break the others.

• Over-specify the process and you kill the judgment. If you script all 9 steps, the AI cannot use what it is good at. It will follow your bad step off a cliff rather than notice the better route. Tell it the goal and the guardrails, then let it find the path on anything low-stakes. Save the tight script for work where a wrong step costs money.
• Under-specify the performance and it rambles or over-hedges. With no role and no tone, the default is a long, cautious, everything-covered draft padded with "it is worth noting" and "you may want to consider." Naming the role and the tone is what makes it sound like you and get to the point.

Follow one rule: be strict about the product, clear about the guardrails in the process, and specific about the performance. Leave the AI room to think inside those lines.

That balance is the actual skill, and it is the same judgment behind what to hand off and how to check the output that comes back.

How this fits the rest of AI fluency.

The four skills work together: deciding what to hand off (delegation), briefing it clearly (description), judging what comes back (discernment), and owning the result (diligence). You run any of them in one of three modes (automation, augmentation, or agency). The pillar guide ties them together.

The three layers of description here (product, process, performance) adapt the AI Fluency Framework, an open framework by Rick Dakan, Joseph Feller, and Anthropic, published under CC BY-NC-SA. We use it as an organizing idea; the writing and examples are our own. The wider skill set sits in our guide to AI fluency for owner-operators.

Writing the facts down once, so your brief can point at them instead of retyping them, is the job we do in month one. That is what turns a good brief into a repeatable one.