← Back to all articles Communication

Talking to AI Is a Communication Skill, Not a Prompt Engineering Trick

Search "how to write better AI prompts" and you'll find hundreds of lists promising secret techniques: magic phrases, formatting tricks, special incantations that unlock better answers. Most of this framing is wrong in a specific way. It treats talking to AI as a technical skill, closer to learning a command line than learning to communicate. It isn't. The people who get consistently good results from AI aren't better at finding secret phrases. They're better communicators, full stop, and the skill transfers directly from how they'd brief a new coworker or explain something to a stranger.

This matters because "prompt engineering" as a phrase has scared off a lot of people who are already good at the actual underlying skill. If you can write a clear email, give useful instructions to a new hire, or explain a problem to someone unfamiliar with it, you already have most of what you need. The gap usually isn't technical. It's that people apply less care to an AI conversation than they would to a human one, and then wonder why the result feels generic.

Most "prompting tips" are just communication basics with a new name

Look at almost any popular prompting guide and you'll find the same handful of recommendations: be specific, give context, say what you want the output to look like, provide an example if you can. None of this is new. It's the same advice you'd give someone writing a work request, a design brief, or instructions for a contractor. The only thing that changed is who's on the receiving end.

Here's a small test. Imagine handing a stranger a note that just says "write something about the product." They'd have to guess the audience, the tone, the length, the purpose, and probably guess wrong on at least one. Now imagine a note that says "write a two-paragraph description for our website's homepage, aimed at first-time visitors who don't know our brand yet, focusing on what makes us different from competitors." The second note isn't a trick. It's just a person doing the basic work of communicating clearly, and it gets a better result from a human assistant and an AI one for exactly the same reason.

"The gap usually isn't technical. It's that people apply less care to an AI conversation than they would to a human one."

Why the parallel to human communication actually holds up

An earlier piece on this site looked at Paul Grice's Cooperative Principle, the idea that conversation works because both people assume the other is trying to be helpful, relevant, and clear. That framework applies here too, just from the other direction. When you write a prompt, you're the speaker setting up the cooperative conditions. If you leave out context a reasonable listener would need, you can't really blame the listener, human or AI, for filling the gap with a guess.

Think about how you'd brief someone temporary: a freelancer you've never worked with, a new employee on their first week, a contractor who can't read your mind about unstated preferences. You wouldn't say "make it good." You'd say what "good" means in this specific case, who it's for, what's already been tried, and what the finished thing needs to do. That's not over-explaining. That's just what clear delegation looks like when the other party doesn't already share your context. AI never shares your context by default, which makes it exactly the situation where this skill matters most, not a special exception to it.

Where the analogy breaks down, and why that matters

The comparison isn't perfect, and the difference is worth knowing because it changes where the responsibility sits. A good human collaborator pushes back when something is unclear. They ask a follow-up question before doing an hour of work on a guess. Most AI systems, by contrast, will often just guess and proceed, confidently, even when the honest answer is "I'm not sure what you mean." That's not a moral failing, it's a structural fact about how these systems are built to be helpful by default rather than to interrupt you with questions.

The practical result: you have to do more of the clarifying work upfront than you would with a sharp human assistant, because the system won't always stop and ask. This is also exactly where iteration helps. Unlike a one-shot instruction to a contractor, you can respond to a first attempt with "close, but make it more X" the same way you'd redirect a colleague's first draft. Treating an AI conversation as a single perfect instruction, rather than a back-and-forth like you'd have with a person, throws away one of the actual advantages of talking to a machine instead of mailing a letter.

What this means in practice

  • Brief it like a new hire, not a search engine. State the audience, the purpose, and any constraints you already know matter, the same information you'd give a new team member on day one.
  • Show, don't just describe, when you can. An example of the format or tone you want does more work than three extra sentences trying to describe it abstractly.
  • Use the follow-up turn. Don't try to perfect the instruction before sending it. Send a reasonable first attempt and correct from there, the same way you'd redirect a first draft rather than rewriting the brief five times before anyone starts.
  • Say what "good" means for this specific case. "Make it professional" means something different in a legal filing than in a startup's social post. Naming the actual standard beats hoping it's inferred correctly.

None of this is a trick, and that's the point. The people who seem to have a knack for getting good results from AI are usually just applying ordinary communication discipline somewhere they'd forgotten to apply it. Getting better at talking to AI and getting better at talking to people turn out to be the same skill, practiced in two different rooms.