Lesson 17 of 25

The Language of Simplicity

A prompt is an instruction, not a conversation. Pleasantries, hedging and apologies for the length of your request all have to be read past before the actual task begins - and figures of speech like "knock it out of the park" or "give it 110%" carry a meaning for you that they do not reliably carry into the output. Say what you want in direct, literal language, and name the thing precisely: not "the important stuff" but "the net profit figure and the top three products".

Reach for it whenWhen the answer you got is vaguely in the right area but not what you meant - almost always because what you asked for was itself vague, or because you asked for it through an idiom.

Simplicity has a sharper edge here than on the other three, because the sprawling prompt does not just produce a vague answer - it produces the wrong searches. Every clause in your prompt becomes a query, so "pretty long", "the important stuff" and "something about Q3 sales" send it hunting for published Q3 sales reports rather than reading yours. State one clear research question per prompt in literal terms, and name the kind of source you want.

Worth knowingTwo of these three examples are not research tasks at all. It cannot analyse your private sales report - there is nothing to search - and a motivational email to your own team has no sourceable content; Perplexity will return an article about motivating sales teams, with citations, which is not an email. The script example is a genuine fit, because what you actually need is current information about a live website, and that is exactly what this tool has over the others.
  • One literal research question per prompt - clauses become queries.
  • Name the source type you want, not "good sources".
  • It cannot read your private documents - no analysis there.
  • Best here for checking live site structure and rules.
  • Keep a recurring research thread in a Space.
The Meandering Request vs. The Direct Command

Instead of

Hey Gemini, so I've got this report here and it's pretty long, to be honest. I don't really have time to go through all of it, so I was wondering if you could help me out by just pulling out the important stuff. Something about the Q3 sales figures would be great. Thanks.

Perplexity version

This one does not belong here, and the reason is worth understanding. A private Q3 sales report has nothing for a search engine to find - and the vague version of this prompt is actively harmful on this tool, because every loose phrase becomes a query. "Something about the Q3 sales figures" sends it looking for published Q3 results from other companies, and you get a sourced answer about somebody else's numbers. Extract from your own report in ChatGPT, Claude or Gemini.

What is worth asking here is the question that comes after the extraction - what the numbers mean against the market.

1. What has been reported about sector-wide sales performance in Q3 in India for [MY SECTOR]? Cite industry bodies, published quarterly results from listed comparators, and trade publications, with dates.
2. Which listed companies in my sector have reported Q3 results, and what did they report on revenue growth and margin? Cite the filings or results releases directly rather than news summaries of them.
3. What is reported about the main cost pressures in this sector this quarter - input costs, freight, wages? Cite sources with dates.
4. What external factors in Q3 would plausibly show up in Indian sales figures - festival season timing, monsoon, GST changes, any regulatory shift affecting my sector? Cite them with dates.
5. What are the standard metrics companies in my sector report alongside net profit, and which does the market actually watch? Cite analyst or industry sources. If my report omits the metric everyone else leads with, I want to know.

Cite every figure with its source and date. Distinguish audited reported results from estimates and projections. Where coverage is only press releases rather than filings, say so.

Replace [MY SECTOR] before running this. Save it in a Space so next quarter's comparison builds on this one rather than starting over.
Open Perplexity 1,876 characters
Avoiding Idiomatic Confusion

Instead of

I need to write an email to my team. We really need to hit the ground running this quarter and knock it out of the park. So, whip up something that tells them to give it 110%.

Perplexity version

Do not write the email here. There is nothing to search: the Q3 numbers are yours, the team is yours, and an answer engine will hand you a sourced overview of sales motivation practice with citations attached. Write it in ChatGPT, Claude or Gemini.

There are two research questions behind it, though, and the second one may change the email entirely.

1. What does the research actually say about which messages improve sales performance, and which backfire? Specifically: does framing a quarter as "the most important of the year" raise performance or raise attrition? What is documented about pressure framing, public target-setting and individual recognition in sales teams? Use Academic focus and cite the studies. My draft email does three things this literature may say are counterproductive, and I would rather find that out before sending it than from the exit interviews.
2. What is documented about goal-setting conversations - does a short structured manager conversation measurably change outcomes, and what makes one work? Cite the research. My call to action is a 15-minute meeting and I want to know whether that is a real intervention or a ritual.
3. What is reported about Indian sales team compensation structures and quarterly target practice - how common is Q4 weighting, and what is documented about its effects? Cite industry sources with dates.
4. On the idiom problem specifically: what is written about business clichés and employee communication - is there evidence that this language reduces how much of a message is retained? Cite what exists, and say plainly if the honest answer is that there is commentary but little evidence. I would rather know my ban list is a matter of taste than be told it is science.

Cite everything with dates. Do not cite sales-training vendors' content marketing as neutral evidence - name it as interested if you use it.

Then write the email elsewhere. Use answer 1 to decide whether "Q4 is the most important quarter of the year" is a line you want in it at all.
Open Perplexity 2,025 characters
Clarity in Technical Requests

Instead of

Can you give me some Python code that gets stuff from a website? I need it to grab the headlines from a news site.

Perplexity version

This is the one example in this chapter where Perplexity is the right tool first, and the reason is specific: what the script needs is not better code, it is current information about a live website. The other three tools will write you a confident scraper against an HTML structure they are guessing at. This one can look.

I want to scrape headlines from `https://timesofindia.indiatimes.com/` using Python with `requests` and `BeautifulSoup`.

1. What is the current HTML structure of that homepage's headline sections? Are headlines in `<h2>` tags, and what class names do they carry? Cite what you find. If the structure has changed recently, say so.
2. Is the homepage content present in the initial HTML response, or rendered client-side by JavaScript? This determines whether `requests` plus BeautifulSoup can work at all, and it is the single most important answer on this list. If the content is JavaScript-rendered, say so plainly rather than describing a selector that will never match.
3. What does that site's robots.txt currently disallow, and what do its terms of use say about automated access and content reuse? Quote and cite them. Do not reassure me - if it is disallowed, say so.
4. Does the publication offer an RSS feed, sitemap or official API? If so, give me the endpoints with sources. A documented feed is better than any scraper and this question makes the whole exercise unnecessary if the answer is yes.
5. What is the legal position on web scraping in India - the relevant provisions of the IT Act and the Copyright Act, and any judgments on scraping or database rights? Cite the provisions and cases with dates. Then say explicitly that this is not legal advice.
6. What is documented about this site's rate limiting or bot detection, and what request intervals do practitioners report as workable? Cite the discussions, and flag anything that is a forum claim rather than documentation.

Cite everything with dates and distinguish official documentation from community reports.

Then take answers 1 and 2 to another tool to write the script - but if answer 4 produces a feed, write a feed reader instead and skip the scraper entirely. That outcome is the best use of this prompt.
Open Perplexity 2,212 characters