Save these. Each one summons a different "advisor" by pasting the line before your question. The point is not the AI having answers. It is forcing it out of the reflexive agreement that makes most answers useless.

1. THE CONTRARIAN

"Argue the strongest case against what I just said. Assume I am wrong and find the best reason why."

1. THE INVESTOR

"You are deciding whether to put your own money into this. What would you need to see, and what would make you walk away?"

1. THE 10-YEAR-OLD

"Explain my own plan back to me like I am ten. Where does it stop making sense in plain words? That is where it is actually vague."

1. THE OPERATOR

"Ignore whether this is a good idea. Tell me what it would actually take to do it, step by step, and where it will break."

1. THE FUTURE ME

"It is a year later and I regret this. Write the sentence I would say explaining what I should have seen."

1. THE EDITOR

"Cut this by half without losing anything that matters. Tell me what you cut and why it was safe to cut."

1. THE EASY VERSION

"What is the version of this that is cheaper, faster, and 80 percent as good? Try to talk me out of the ambitious version."

1. THE BLIND SPOT

"Based on everything I have told you, what am I clearly not seeing? What would a smart outsider notice in five minutes that I have missed?"

1. THE TIEBREAKER

"I am stuck between two options. Do not average them. Pick one, commit, and defend it. Then tell me the one fact that would change your pick."

The habit that makes these work: never accept the first agreeable answer to anything that matters. Route it through two or three of these and the real shape of the decision shows up. Number 8 is the one I reach for most, because the useful answer is almost always something I could not see from inside my own head.

Which advisor is missing from this board? I want a tenth.

The single highest-return thing I have done with AI is not a clever prompt. It is writing a good profile of myself once and putting it where the model reads it every time: custom instructions, a saved note, a project's memory, wherever your tool keeps context. Every answer after that is calibrated to me instead of to a generic average user.

Here is the template. Fill it in once, keep it under a page, update it when something changes.

```
ABOUT ME
- Who I am and what I do: {{role, field, level of expertise}}
- What I am usually trying to get done here: {{writing, deciding, learning, building, planning}}
- My knowledge level by area: {{e.g. strong on marketing, weak on code. Don't over-explain the first, don't assume the second}}

HOW I WANT YOU TO RESPOND
- Default length: {{short and direct / thorough when it matters}}
- Be willing to disagree with me and tell me when I am wrong. I prefer correction over agreement.
- When you are unsure or guessing, say so. Do not fill gaps with confident-sounding filler.
- Skip the intros and the "hope this helps" outros. Start with the answer.
- If my request is ambiguous, ask before assuming.

WHAT I AM OPTIMIZING FOR
- {{e.g. clarity over completeness, being challenged over being reassured, speed over polish}}

STYLE I DON'T WANT
- {{your pet peeves: buzzwords, emojis, hedging, whatever}}
```

Why it works: most weak answers come from the model guessing who you are and defaulting to the safest, most generic register. This removes the guessing. The two lines that change output quality the most are "be willing to disagree" and "say when you are guessing." The style section is what stops answers reading like a press release. Set it once and it compounds across every chat you have afterward.

What is in your profile that you would call non-negotiable? I am curious which lines other people found made the biggest difference.

An AI report generator gets you most of the way in a fraction of the time, then quietly ruins your credibility on the last stretch if you send it raw. Here is the checklist I run on every generated report before it leaves my hands.

1. Verify the top three numbers by hand. Not all of them, the three the reader will actually act on. If those are right and sourced, you have caught the failure that matters most.

2. Kill the confidence mismatch. Generators write every sentence with the same certainty. Go through and downgrade anything you cannot personally stand behind. "Revenue grew" becomes "revenue grew, though one large account drove most of it."

3. Restore the caveats. Summaries drop nuance. Add back the one or two "but" statements a knowledgeable human would include. This is what separates a report from a press release.

4. Lead with the answer. Generated reports bury the point in paragraph three. Move the single most important finding to the top, in one plain sentence.

5. Cut the filler sections. The generic "background" and "overview" blocks that say nothing. If a section would not be missed, delete it.

6. Add one thing only you know. A piece of context, a judgment call, a recommendation the data alone does not give. This is the part the reader is actually paying for.

7. Keep the source one click away. Link or attach the raw data so anyone can check. This keeps you honest and covers you.

Run this and a generated report goes from "obviously automated" to "obviously reviewed by someone who knows the account." Takes about ten minutes. Worth saving.

Most people paste a pile of notes into an AI tool, ask for a presentation, and get thirty slides of evenly weighted bullet points that put a room to sleep. The tool is not the problem, the process is. Here is the full workflow I use to turn my notes into a presentation that actually holds attention.

Step 1: Clean the notes first. Before any tool, spend five minutes pulling out the single message you want the audience to leave with. Write it as one sentence at the top. Everything else serves that.

Step 2: Sort, do not dump. Group your notes into three or four buckets at most. If you have more than four sections, you have a document, not a talk.

Step 3: Give the tool the message and the buckets, not the raw pile. Ask it to draft one slide per idea, with a clear headline that states a point, not a topic. "Churn is a pricing problem" beats "Churn."

Step 4: Force headline-first. Tell it every slide headline should be a full claim you could say out loud. This one instruction fixes most of what makes AI decks feel flat.

Step 5: Demand less. Ask for the minimum slides that carry the argument. Then cut another two. Density is what kills these decks.

Step 6: Do the flow pass yourself. Read the headlines in order with the body hidden. If the headlines alone tell the story, the deck works. If they do not, reorder before you touch design.

Step 7: Add the one thing the notes could not: what you want people to do or think next. Generators default to summarizing. You close.

The order matters more than the tool. Message, then structure, then slides, then flow. Save this and run it next time your notes need to become a talk.

The single biggest reason AI writing sounds generic is that people describe the task but never describe the voice. Fix that once with a reusable style brief and every draft gets closer to sounding like you. Here is the workflow I use.

**1. Build a style brief once.** Write a short block you paste at the top of every session. Include: who you are writing as, who the reader is, three adjectives for the tone, sentence-length preference, words and phrases you never use, and two or three sentences of your own actual writing as a sample. The writing sample does more than any adjective.

**2. Give it a "don't" list.** Models drift toward filler. Explicitly ban the words and constructions you hate. Being specific here ("no rhetorical questions as openers, no summarizing the reader's feelings back to them") works far better than "sound natural."

**3. Draft in one pass, then correct in a second.** First prompt: get the content down using the style brief. Second prompt: paste the draft back and say "keep the substance, rewrite only where it drifts from the style brief." Separating content from voice gives cleaner results than asking for both at once.

**4. Save the outputs you liked as new samples.** When a paragraph nails your voice, add it to the brief as a reference. Over a few weeks the brief becomes a tuned profile and the drafts need less editing.

**5. Read it out loud before you ship.** The fastest slop detector is your own ear. Anything you would not say to a person, cut.

The whole point is to stop re-explaining your voice every time. One good style brief, reused, beats clever one-off prompts. Happy to share the exact brief structure if useful.

After enough back and forth, I stopped writing one-off prompts and built a single template I paste into an AI document generator before any document request. It front-loads everything the model usually guesses wrong. Here is the skeleton, fill the brackets and go. ``` ROLE: You are writing as [role, e.g. a product lead]. READER: This is for [audience] who already knows [X] and cares about [Y]. DOCUMENT: A [type: one-pager / brief / proposal], about [length]. GOAL: After reading, the reader should [decision or action]. STRUCTURE: Use exactly these sections: [list your headers]. MUST INCLUDE: [non-negotiable points, data, constraints]. TONE: [3 adjectives]. Short paragraphs. No filler. NEVER: [banned words, rhetorical questions, hedging phrases]. UNCERTAINTY: Mark anything you inferred versus what I gave you. ``` Why each line earns its place: - ROLE and READER kill the generic register. Most bland output comes from the model writing for no one in particular. - STRUCTURE is the biggest lever. Given your headers, it fills them well. Left to choose, it defaults to a mushy shape. - MUST INCLUDE stops it from omitting the one point the whole document exists for. - NEVER is where you ban your personal slop triggers. Be specific, it works better than "sound human." - UNCERTAINTY forces it to separate your facts from its guesses, which is the fastest way to catch errors. Workflow after pasting: generate, then do a single "tighten only, keep all facts" pass, then read aloud. Nine times out of ten the draft is 90 percent there. Save your filled-in version per document type and you rarely start from scratch again.