Lesson 16 of 25
The Seed of a New Idea (Brainstorming)
Brainstorming with an AI only works when you give it somewhere to push against. An open request - "suggest some names" - returns the most average answer in existence, because average is exactly what a prediction engine is built to produce. You get genuinely useful raw material by asking for volume, giving the model a specific brief to generate against, sorting the output into categories you chose, and banning the obvious answers by name.
Separate the brief from the task with tags - <brief>, <categories>, <exclusions>, <output_format> - so the constraints read as constraints rather than as suggestions buried in a paragraph. The move that pays off most on this platform is asking it to work in two stages inside one answer: a <thinking> block where it maps out the territory before generating, then the list, then a <critique> where it marks its own weak entries. It will genuinely criticise its own output, which is the half of brainstorming you normally have to do alone.
- Tag the brief, the categories and the exclusions separately.
- Ask for <thinking> before the list, then <critique> after.
- Have it mark which of its own ideas are derivative.
- Paste competitor or prior-attempt lists first, instruction last.
- Ask it to flag anything it cannot verify.
Instead of
What should be the name for my new coffee shop in Kondapur?
Perplexity version
<brief> An upscale coffee shop opening in Kondapur, Hyderabad. Customers: IT professionals from the surrounding tech parks, 25 to 40, coffee-literate, rushed on weekdays and lingering at weekends. The identity is modern and minimalist with a real thread of South Indian warmth - filter coffee served properly beside a pour-over bar, not as a novelty. </brief> <exclusions> Do not use: Brew, Bean, Grind, Roast, Cup, Daily, Co., & Co. These appear on nearly every independent coffee shop in India and the list should begin past them. No names formed by deleting a vowel. No puns. </exclusions> <categories> 1. Modern and tech-adjacent - at home next to the companies my customers work for, without being clever about it. 2. English blended with Telugu or Hyderabadi Urdu - real words with real meanings. Give the meaning and the pronunciation for each. 3. Elegant and sophisticated - short, speakable, no wordplay. </categories> <task> Work in four stages, in this order. <thinking> Before generating anything, map the territory: what naming conventions already dominate specialty coffee in Indian metros, what the predictable move would be for each of my three categories, and what a name would have to do to escape that. I want to see this reasoning - it tells me whether you have understood the brief or are about to give me the standard list. </thinking> <names> 20 names, sorted into the three categories above. </names> <critique> Go back through your own list and mark: - Every entry you consider derivative, and of what. - Every entry that is hard to spell, hard to say, or likely to be misheard. - Every entry in category 2 whose meaning you are not confident about. Be strict here - a wrong gloss on a Telugu or Urdu word is the most expensive error available in this task, because it ends up painted on a signboard. </critique> <recommendation> The three you would actually open with, and for each the one-line story the name tells someone standing on the pavement. Then state plainly what you cannot check: trademark status in Telangana, domain availability, whether an existing Hyderabad shop uses it. Do not guess at any of these - just name them as the checks I have to run. </recommendation> </task>
Instead of
Solve the traffic problem in Hyderabad.
Perplexity version
<context> The problem: peak-hour congestion on the Outer Ring Road in Hyderabad, roughly 8 to 11 AM and 5 to 8 PM. A large share of it is IT commuting between the western tech corridor and the rest of the city, which means a small number of employers control a large share of the trips. </context> <role> A panel of four: an urban transport planner, a behavioural economist, a technologist, and a city politician whose job is to say what will not survive a council meeting. Let them disagree. The disagreement is the useful part. </role> <exclusions> Off the table entirely: more flyovers, metro expansion, road widening, "encourage carpooling" with no mechanism, "more buses" stated generically. Every existing report contains these five and I am not asking for them again. </exclusions> <task> <thinking> First, before any ideas: why have the obvious interventions not solved this? Induced demand, the geography of the western corridor, the fact that the ORR is a ring rather than a radial. Then say which of my four levers - technology, policy, behaviour, employer-side - is most under-used in Hyderabad specifically. I want the diagnosis before the list, because fifteen ideas generated without it will all be apps. </thinking> <ideas> 15 unconventional interventions, spread deliberately across technology, policy and regulation, behavioural change, and employer-side obligations. For each: two or three sentences, then <kill_risk> naming the single thing most likely to stop it - usually political cost, cost recovery, or enforcement. </ideas> <panel_disagreement> Where the four panellists would split. Name at least two ideas the planner likes and the politician would bury, and say why. This is where the real information is. </panel_disagreement> <shortlist> The three cheapest to pilot, with what a pilot on one stretch of the ORR would look like. Then the one idea most likely to work and least likely to happen, and what makes it impossible. </shortlist> <uncertainty> Be direct about this. Where are you describing how Hyderabad works from general knowledge rather than from data? Do not state commuter volumes, travel times or costs as though sourced - if you need a number to make an idea legible, mark it illustrative. A flagged guess is useful; a confident invention wastes my time twice, because I will act on it. </uncertainty> </task>
Instead of
Write a blog post about the importance of saving for retirement.
Perplexity version
<context> I am writing a blog post for young Indian professionals - late twenties, first or second job, saving irregularly - on why starting retirement savings early matters more than the amount you start with. I need raw material to write from, not the post itself. </context> <task> 10 analogies for compound interest, each grounded in something an Indian reader already has intuition for. </task> <constraints> - Draw from genuinely different wells, so they are not one analogy in ten costumes. Candidates: cricket and a strike rate compounding over overs; a mango or banyan tree planted by a grandparent; the monsoon filling a tank night by night; a chit fund or recurring deposit; dough rising; a family business handed down; a WhatsApp forward spreading. - No numerical examples and no invented return percentages. I will build the maths separately. </constraints> <output_format> For each analogy: <analogy> - two or three sentences, written as I could say it out loud. <what_it_captures> - which specific property of compounding: that time beats amount, that growth compounds on growth, that a five-year delay costs more than it feels like it should. <where_it_breaks> - every analogy misleads somewhere. If the mango tree implies you only plant once, say so. I would rather know than have a reader catch it. </output_format> <then> <best_three> - ranked, for a 27-year-old in Hyderabad who has heard this lecture from a parent and tuned it out. <the_liability> - which of your ten is most likely to read as a promise of guaranteed returns. In a post about money that is a real risk, and I would rather cut it than caveat it. <inverted> - one analogy for the cost of delay rather than the reward of starting. Loss lands harder than gain and I may open the post with it. <honest_note> - if you think a metaphor is the wrong instrument here and this audience would be moved more by one blunt number than by ten images, say so. I have assumed analogies are what I need and I may be wrong about that. </then>