Lesson 15 of 25

The Power of the Negative Command

Naming what you do not want removes a whole class of wrong answers at once - the slang, the tourism paragraph, the mention of flooding. It works best paired with the positive instruction, because "do not do X" leaves the model to guess what to do instead. The strongest version of this technique is a ban plus a replacement: not "avoid jargon" but "no jargon - say what it does for the reader instead".

Reach for it whenWhen you keep getting the same unwanted element - the same filler phrase, the same irrelevant section, the same cheerful tone - no matter how you rephrase the request.

Keep the structure the original used, with the bans in a clearly marked section, and add the two things the platform gives you: a Gem that holds a ban list you reuse - which is the natural home for banned words and house-style prohibitions - and a destination for the output. For the comparison table, the useful additional instruction is where to ground and where not to, since the business figures need sourcing and the city-pride language comes straight from ungrounded search results.

Worth knowingSearch grounding fights negative constraints. Ask for a city comparison with grounding on and tourism content walks in through the sources - the top results for "Hyderabad vs Bangalore" are lifestyle articles. Either tell it not to search and accept unsourced relative statements, or ground it and ban the content again explicitly at the point you ask for sources.
  • Hold a reusable ban list in a Gem.
  • Repeat the ban where you ask it to search - grounding smuggles things in.
  • Ground the figures; ban the language the sources are written in.
  • Send the output to the Doc where it will be used.
  • Do not search at all for creative work with bans.
Example 1: Sculpting a Professional Tone

Instead of

Write an email to a client who has missed a payment deadline.

Perplexity version

### THE TASK ###

A professional email to a client whose payment is 15 days overdue. Firm but polite. The goal is a payment date, not a won argument - I want to keep this client.

### DO NOT - each with what to do instead ###

* **No emotional or accusatory language.** No "you have failed to", "we are disappointed", "as you are well aware". Instead: state the facts and the ask neutrally.
* **No informalities, slang or contractions.** "Do not", never "don't". Instead: plain professional English.
* **No passive-aggression.** The real failure mode, and it hides in polite wording: "just following up again", "I'm sure this is an oversight", "per my previous email", "gentle reminder". Instead: say what is outstanding and what you want.
* **No threats or implied threats.** No legal action, late fees, suspended work, escalation. Instead: make the ask clear enough to need no consequence.
* **No over-apologising.** Instead: courteous, not deferential.

### DO ###

Open on the specific invoice - number, amount, original due date. One line acknowledging invoices get missed. A direct ask for a payment date. A line offering to clear any blockage, such as a missing purchase order or a wrong invoice detail, which is often the real cause. Subject line. Under 150 words.

### DO NOT SEARCH ###

Do not ground this in Google Search. Search results for overdue payment emails are templates built on exactly the passive-aggressive phrasing I have banned, and grounding will import it.

### USE MY ACTUAL DATA ###

Pull the invoice number, amount and due date from the invoice tracker Sheet I am attaching - the row for this client. Do not invent any of them, and tell me if the row looks wrong or incomplete. If you cannot find the row, use placeholders and say so.

### THEN ###

1. "Ban check" - quote any phrase in your draft that comes near the DO NOT list, including ones you revised out. Be strict on passive-aggression; it survives rewriting because it reads as polite.
2. One line on how this reads to a client who is late because of cash flow trouble - the most likely reason.
3. One line: if the ban on implied consequences leaves the email with no reason to act on, say so. I would rather know it is too soft than have it ignored for another fifteen days.

### OUTPUT ###

Draft it into Gmail, saved as a draft, not sent. Save the ban list as a Gem called "Client email style" - every client email I write needs these same prohibitions and I do not want to retype them.
Open Perplexity 2,479 characters
Example 2: Carving Out Irrelevant Information

Instead of

Compare Hyderabad and Bangalore as cities for a tech startup.

Perplexity version

### THE TASK ###

A comparison table for a tech entrepreneur choosing between Hyderabad and Bangalore as a startup headquarters.

### ROWS ###

At minimum: Office Space Cost, Talent Pool Availability, Government Incentives. Add rows only if strictly business - commute time's effect on usable working hours, ecosystem density, airport connectivity for client travel - with one line each on why it affects the decision.

### DO NOT INCLUDE - each with what to do instead ###

* **No tourism, nightlife, food or lifestyle.** Not as rows, not as asides, not in the summary. Instead: where something lifestyle-adjacent has a business consequence, state only the consequence.
* **No "quality of life" row.** Lifestyle in a business suit.
* **No weather,** unless it is data centre cooling cost - and say so explicitly if it is.
* **No city-pride language.** No "vibrant", no "Silicon Valley of India", no "up-and-coming". Instead: what is measurable.

### GROUNDING - READ THIS CAREFULLY ###

Use Google Search for the figures. I need real numbers, not your recollection of them. But this is the exact place the platform works against me, so:

* Search for office rentals, talent data and government schemes. Cite each with its source and date. Prefer Telangana IT department and Karnataka IT-BT department pages, Startup India scheme pages, and published commercial property reports over general articles.
* **The ban applies to the search results too.** The top results for "Hyderabad vs Bangalore" are lifestyle and tourism articles, and if you ground in those, nightlife and food will walk straight into my business table. When a source is primarily lifestyle content, do not use it, and tell me you discarded it.
* **Ban the language of the sources, not just their topics.** Property consultancy reports and state IT pages are written in promotional register. Extract the number; leave the adjectives behind.
* Government incentive schemes change. Give me the date of every scheme and flag any you cannot confirm is current. A lapsed scheme stated confidently is the most costly error available here.

### FORMAT ###

Four columns: Factor | Hyderabad | Bangalore | Source and date.

### AFTER THE TABLE ###

1. "Which factor decides it" - which row actually determines the answer for most early-stage companies. A table implies equal weight; they are not equal.
2. "What a table cannot hold" - where your first customers are, where your co-founder lives, your own network. If one of those should outweigh the whole table, say so.
3. "Lifestyle check" - confirm nothing lifestyle-related got in, and name any source you rejected for being lifestyle content.

### OUTPUT ###

Put the table into a Google Sheet called "HQ comparison" with the source column intact, so I can check the links and update it as schemes change.
Open Perplexity 2,819 characters
Example 3: Removing Undesired Creative Elements

Instead of

Write a short poem about the monsoon in Hyderabad.

Perplexity version

### THE TASK ###

A four-stanza poem about the arrival of the monsoon in Hyderabad.

### WHAT IT IS ABOUT ###

The relief of the first rain after long heat. Petrichor - the smell of earth taking water. The green that follows within days. Positive and celebratory throughout.

### DO NOT - each with what to do instead ###

* **No traffic, flooding, waterlogging, potholes or power cuts.** Instead: the poem lives in the hour of arrival, not the week after.
* **No turn into melancholy.** Monsoon poems default to nostalgia and loss. Instead: present tense, and in the body - heat, then water, then green.
* **No sadness in the final stanza.** That is where a positive poem collapses into wistfulness. Instead: end on the green, or on a next-morning image.
* **No "pitter-patter", "Mother Nature", "liquid gold", "thirsty earth".** Instead: one specific image a Hyderabad reader would recognise.
* **No landmarks as scenery.** No Charminar, no Hussain Sagar dropped in for atmosphere. Instead: let the city arrive through sensory detail.
* **No rhyme scheme you cannot hold.** Instead: free verse if rhyme is bending the lines.

### DO NOT SEARCH ###

Do not use Google Search at all for this. Searching monsoon poetry will give you the entire cliche inventory I have just banned, and grounding a poem is how it ends up sounding like every other poem on the subject.

### USE MY IMAGES INSTEAD ###

I am attaching photographs I took of my own street in the first ten minutes of last year's first rain. Work from those rather than from a general idea of monsoon. Name two specific details you took from the photographs - this is the one thing that will keep the poem out of the cliches, because my street is not a stock image.

### AFTER THE POEM ###

1. "Ban check" - quote any line that drifted toward the negative, the melancholic or the cliched, including lines you revised out. Where the pull was strongest is what I want to know.
2. "Where the constraint fought you" - I have banned every difficult thing about the monsoon and the melancholy the form reaches for. Say where that made the poem weaker or less true. If you think the honest version would be the better poem, say so and show me one stanza of it.

### OUTPUT ###

Keep it in the chat; I will iterate on it before it goes anywhere. Save the ban list as a Gem called "Poem bans" - the cliche prohibitions apply to everything I write.
Open Perplexity 2,397 characters