Lesson 5: Set the Tone, Structure, and Standard
Lesson overview
Getting AI to produce something technically correct is the easy part. Getting it to produce something that sounds right, is organized the right way, and meets your actual quality bar — that requires guidance. This lesson teaches you how to give that guidance clearly without micromanaging every sentence.
What this means
Every piece of writing has a tone (how it feels), a structure (how it is organized), and a standard (how good it needs to be). If you do not specify these things, AI picks defaults. The defaults are safe, generic, and usually not quite what you needed.
Tone guidance tells AI how the writing should feel: formal or conversational, warm or direct, urgent or measured.
Structure guidance tells AI how to organize the content: short paragraphs or long form, headers or flowing prose, bullet points or narrative.
Standard guidance tells AI what quality level to aim for: plain and functional, polished and tight, punchy and opinionated, or something else entirely.
Why it matters
Without tone guidance, AI tends to default to a slightly formal, slightly bland register that fits nothing in particular.
Without structure guidance, AI makes layout decisions based on what is most common for the request type — which may not be what you need.
Without quality standards, AI aims for completion rather than excellence. It stops when the task is technically done, not when the output is actually good.
All three of these are controllable — and adjusting them makes a significant difference in what comes back.
What most people do wrong
Saying "make it good" without defining what good means
"Make it professional" or "make it better" or "improve the tone" are not useful instructions unless you define the target. Professional to one person means stiff to another. Better by what standard?
Not preventing the things you do not want
Most people focus on describing what they want. Equally important: describing what you do not want. "Avoid hype" and "do not use bullet points" and "no jargon" are legitimate instructions and they work.
Leaving structure up to AI entirely
AI will make reasonable structural choices — but reasonable may not be right for your context. If you need a specific format (short introduction, three supporting points, one clear action), say so.
Accepting padded writing without asking for tightening
AI often writes more than is needed. Extra sentences that restate the obvious, closing paragraphs that echo the intro, transitional filler that exists to fill space. You can ask for this to be removed explicitly.
What better looks like
Tone, structure, and standard guidance does not have to be long. A few well-placed words do most of the work.
Examples of practical tone guidance:
- "Tone: direct and plain. No corporate softening."
- "Write this the way a knowledgeable colleague would explain it in a meeting, not the way a press release would describe it."
- "Warm but professional — like a good customer success manager, not like a generic FAQ."
- "Conversational. Short sentences. No fluff."
Examples of practical structure guidance:
- "Two short paragraphs, no headers, no bullets."
- "Three sections: what changed, why it matters, what to do next."
- "Lead with the most important point. Keep each paragraph to no more than three sentences."
- "One-sentence summary at the top. Details in bullet points below."
Examples of quality standard guidance:
- "This should be tight. Cut anything that does not add meaning."
- "Avoid phrases like 'in today's fast-paced world' or 'in conclusion.' Get straight to the point."
- "Every sentence should earn its place. If removing it does not change the meaning, cut it."
- "Aim for the reading level of a smart non-expert. No jargon, no over-explaining."
Weak example
Write an update for our stakeholders about the project.
What is missing: No tone direction. No structure. No quality bar. The output will be adequate and generic — probably three to five paragraphs of neutral corporate language that no one will remember.
Strong example
Write a brief stakeholder update about a delayed software release. Context: the delay is two weeks due to unexpected QA findings. Audience: internal leadership who are supportive but want to know the facts and the plan.
Format: Three short paragraphs — what happened, what we found, what the updated timeline is. No bullet points. Tone: candid and confident, not apologetic or defensive. Under 200 words. Avoid hedging language like "it seems" or "we believe."
What is better: The tone is described in terms of what it should feel like and what it should not. The structure is specified. The length limit prevents padding. The constraint on hedging language prevents a common AI tendency toward over-qualification.
Practical exercise
Take this draft and improve it by adding only tone, structure, and quality guidance. Do not change the underlying content — only the instructions to AI about how it should be written.
Original prompt:
Write a one-page summary of the benefits of our new employee wellness program.
Rewrite this prompt with:
- A specific tone instruction (describe what it should feel like and what to avoid)
- A specific structure instruction (how should it be organized?)
- A quality standard instruction (what makes this a good version of this piece?)
Compare the output from the original prompt vs. your improved version.
Reflection prompt
- What is the default tone that AI tends to produce for your most common tasks? Is that the tone you actually want?
- Is there a format you prefer for certain work outputs that you rarely specify in advance?
- What words or phrases do you commonly delete when editing AI output? Can those become "avoid" instructions?
Key takeaway
Tone, structure, and quality standards are not stylistic details — they determine whether the output is actually useful. Specifying them saves you editing time and produces writing that is closer to what you actually need.