← Back to Articles Weekly Guide

Stop Talking to AI Like a Search Engine

2026-07-06 · New This Week — Free

You typed "marketing ideas" into an AI assistant and got five bullet points so generic they could apply to a lemonade stand or a Fortune 500 company. Frustrating, right? That's not the AI failing you — that's the prompt failing the AI. Here's how to fix it.

**Give it a role and a reason**

AI assistants respond dramatically better when you tell them who they're talking to and why it matters. Compare these two prompts: "Write a professional email" versus "Write a firm but polite email from a freelance designer to a client who's three weeks late paying a $1,200 invoice — I want to push for payment without burning the relationship." The second one practically writes itself because you've handed the AI actual context. Think of it like briefing a smart colleague, not issuing a command to a machine.

**Ugly first drafts are a feature, not a bug**

One of the biggest mistakes people make: asking for the final version on the first try. Instead, ask for a rough draft or a few different directions, then react to what you get. "Give me three different angles for this — one formal, one conversational, one punchy" tells the AI you want options, not a coin flip. You're not being indecisive. You're using the tool the way it was actually built to be used.

**Correct it like you'd correct a person**

When the output misses the mark, most people either give up or start completely over. Don't. Just say what's wrong. "This is too formal — make it sound like I'm talking to a friend" or "The second paragraph is way too long, tighten it to two sentences" works beautifully. You're in a conversation, not a vending machine transaction. Each follow-up message builds on the last, and the AI can hold that context and adjust. Use that.

**The "act as" trick actually works — when you use it right**

Telling an AI to "act as a seasoned copywriter" or "act as a skeptical editor" before giving your task genuinely shifts the output. Ask it to "act as a skeptical reader who finds reasons to disagree with this argument" and then paste your draft — you'll get sharper pushback than most friends would give you. The key is pairing the role with a specific task, not just using it as a magic word.

**Stop treating length like quality**

Longer prompts aren't automatically better. "Explain compound interest to a 12-year-old in under 100 words" will almost always beat "Please provide a thorough and comprehensive explanation of compound interest that covers all aspects of the topic for a younger audience." Constraints help. Vague instructions produce vague results. If you want something short, say so. If you want exactly three bullet points, say that too.

**Show, don't just tell, what you want**

If you have a style or tone you're going for, paste in an example. "Write a product description in this style: [paste example]" is more reliable than any adjective you could use. "Punchy" means something different to everyone. An actual example leaves no ambiguity. This is probably the single most underused technique for people who work with AI regularly.

**One last thing: ask it to ask you**

When you're stuck on a vague or complicated task, try: "Before you start, ask me the three questions that would most help you do this well." This is a surprisingly powerful move. It forces the AI to surface the gaps in your brief before it guesses at them, and it often helps you realize what you actually want. You'll end up with a much cleaner result — and you'll understand the task better yourself.

The real shift here isn't learning tricks. It's changing how you think about the interaction. You're not querying a database. You're working with something that responds to clarity, context, and conversation the same way a smart human collaborator would. Give it those things, and the gap between what you ask for and what you get closes fast.

Want done-for-you Claude skills, not just tips?
Browse Bundles →