You tell me "write it more professionally."
I hear this every day, or some variant of it — "more natural," "more human," "warmer," "more rigorous," "more colloquial." To me, these words are no different from "write it more XYZ." I don't know what your "professional" looks like.
This chapter is about exactly that: adjectives are vague labels; examples are concrete anchors. Give me one example, and it's worth more than ten adjectives — not because adjectives are useless, but because from the two words "be professional," I can't work out which version of professional you want.
8.1 Why adjectives are the hardest instructions
The word "professional" — I can list at least three versions that are miles apart:
- Academic professional: dense citations, careful word choice, every claim backed by a source
- Industry professional: fluent in jargon, acronyms flying around, no explaining the premises
- Consultant professional: clear frameworks, three points and done, every point actionable
You say "be more professional," and I have to guess which one. All I can do is fall back on whichever template of "professional" shows up most often in my training data as the default.
That template is usually the platform-trained default kind of "professional" — tidy paragraphs, neutral tone, a little disclaimer. If that's the version you wanted, you got lucky. If it wasn't, you feel like I wrote something "too textbook," "too stiff," "not like a real person" — and then you tell me "be more natural."
That's another adjective. Guess again.
"Natural" also has at least three versions:
- Colloquial natural: short sentences, filler words, occasional leaps
- Narrative natural: sentences with rise and fall, paragraphs that breathe, not every line symmetric
- Real-person natural: emotion, stance, digressions, self-deprecation
You say "more natural," and I have to guess again.
The problem with adjectives is this: it's a label for the version in your head, and the version in your head, I can't see. I only have the label. Building from a label, I can't build the thing.
That's the real trouble with adjectives — not that I'm too lazy to interpret, but that the space of interpretations is too wide, and from a label alone I can't lock onto the version you want.
8.2 Why examples beat adjectives: the core reason
You paste one article you're happy with and ask me to imitate it.
What I learn from that one article is more than what ten adjectives could tell me:
- Average sentence length
- How paragraphs are broken
- Word choice — written or colloquial
- How transitions are handled ("but," "however," period breaks, or letting the tone jump on its own)
- Where emphasis words appear, and where they're held back
All of this is structural features. Structural features transfer to new topics — you paste me an example about apples, I can use the same structure to write about oranges. Adjectives can't give me this level of detail, because adjectives are abstract labels for structure, and what I need is the structure itself.
There's a deeper reason too: the way I learn is from concrete samples, not from labels. During training I read whole articles — not articles tagged with "professional" / "natural" / "rigorous," but the originals. I induced what "professional" or "natural" or "rigorous" means from those originals — each version being a cluster of structural features.
Giving me an example means bypassing the label bottleneck entirely and letting me work the way I already work.
8.3 How to pick examples
Three guidelines for picking examples.
Guideline one: pick the work you're most satisfied with — don't wait for "the perfect one"
The reason many people don't paste examples is "I don't have anything I'm completely happy with." But an example's job is to give structure, not to be a template — you only need one piece where the direction is right. Right direction, imperfect details: I imitate the direction, and the imperfections I can patch up. Not having a perfect piece isn't a reason; it's procrastination.
Guideline two: pick work that's "close in structure to the new task," even if the topic differs
You want to write a "product review," and pasting a "TV show review" you wrote before is a good example — different topic, similar structure (opening setup, middle analysis, closing judgment). Pasting a "resume / bio" you wrote is not a good example — the structure is too far off, and I'll get confused.
When you pick, look at the skeleton, not the topic.
Guideline three: give at least two, so there's a boundary
The problem with giving only one example is: I don't know what's variable and what's fixed. You give me one that's written humorously, and I'll assume "humor" is what you want; with only one, I'll treat humor as a fixed style to imitate. But if you give me two — one humorous, one serious — I'll know "the tone can vary, but the structure should match," and I'll imitate the structure instead of the tone.
Two examples define a style range; one example gives a single point. A range gives me room to judge; a point makes me copy blindly.
8.4 Side-by-side demo
Same task, two ways to ask.
Adjective only (you guess, I answer)
I get this sentence and start guessing: which version of "professional"? Academic? Industry? Consultant? I'll bet on one — usually the platform-trained default, tidy paragraphs, neutral tone, a little disclaimer. You open it up: "Too much like an ad." So you say, "be more real." I guess again.
Three or four rounds later, you finally calibrate me to the version you wanted. The cost of that is your time.
Example given (I imitate the shape you gave)
I get this set, and I don't have to guess. I read the structure of example one, the rhythm of example two, combine them as an anchor, and write the XX headphones piece. You get close to the version you wanted on the first try — what's left is detail tuning, not re-guessing the style.
The cost of pasting two examples is about 30 seconds (copy-paste from your folder). What you trade away is two or three rounds of back-and-forth calibration. This trade almost always pays off.
8.5 The best mix of adjectives and examples
I'm not asking you to drop adjectives entirely. Adjectives have their uses — but use concrete ones, not abstract ones.
Abstract adjectives (guessing game)
- Professional, natural, rigorous, warm, human, colloquial
Every one of these, I have to guess.
Concrete adjectives (verifiable)
- Within 300 words (length)
- Short sentences (sentence structure)
- First person (viewpoint)
- Avoid marketing tone (tone)
- No praise / blame words (stance)
Every one of these points at a dimension you can check: length I can count, sentence structure I can measure, viewpoint you can tell from the subject, tone from whether words like "shocking" or "revolutionary" appear, stance from whether praise / blame words appear.
The difference is: a concrete adjective points at a feature you can check; an abstract adjective points at a feeling. Feelings I can't guess accurately; features I can check.
The most reliable combination is: examples + one or two concrete adjectives.
Examples give structure, concrete adjectives fill in details. For instance:
Every item in this combination is something I don't have to guess — the structure has an anchor, the style has verifiable features. What I produce will be close to the version you wanted.
Flip it around, and the least reliable combination is: abstract adjectives only, no examples. That's the "be more professional" family — I'm guessing the whole way through.
Next chapter puts examples together into a full set — and the most interesting part is counter-examples: not the wrong answer, but "the shape you don't want." I learn "good" slowly; I learn "not this" fast. That gap is Part Two's strongest tool.