top of page

Your AI Assistant Doesn't Need a Personality. It Needs a Job Description.

Yazarın fotoğrafı: Faruk Komur
Faruk Komur
4 saat önce
3 dakikada okunur

Open the settings of almost any AI assistant and you'll find a familiar menu: friendly or formal, witty or concise, "act as a world-class marketing strategist." People spend real time on these dials. Here's the contrarian take: for getting good work out of an assistant, most of that time is wasted. The dials that matter are scope and examples, and they're much less fun to set.

What the research says about personas

A team of researchers tested whether giving a model a persona improves its answers. Their paper, published at EMNLP 2024, tried 162 different roles across four families of language models and 2,410 factual questions. Their conclusion: adding personas to system prompts did not improve performance compared with a plain control, and which persona helped on a given question looked largely random.

That's one study on factual questions, so don't over-read it. A persona won't make a model smarter. But it also cuts against the popular advice that telling a model it's "an expert" unlocks hidden skill. The model already knows what it knows. A costume doesn't add knowledge.

Where personality does matter

Tone isn't worthless. If you want an assistant that writes friendly customer replies, or explains things to a ten-year-old, a style instruction works well, because style is exactly what such instructions control. The mistake is expecting style to do the job of substance. "Warm and professional" tells the assistant how to sound. It says nothing about what to do when a customer asks for a refund outside your policy window.

That's the gap that causes most disappointing results: the assistant sounds great and does the wrong thing, confidently.

What to spend setup time on instead

Anthropic's prompting guidance and most other major providers' advice say much the same thing: be clear and direct, explain the context, and show examples. In practice, a useful setup has three parts.

Scope. Say what the assistant is for and, just as important, what it should leave alone. "Draft replies to billing questions. Never promise a refund; flag those for a human" beats any persona.

Examples. Paste two or three real inputs with the outputs you'd be happy with, including one tricky case. Examples carry detail that's hard to put into adjectives, like length, structure, and what counts as "good enough."

Edge-case rules. List the three situations where you'd normally have to step in, and write down what you'd want to happen. Every rule you write once is a correction you stop making forever.

Notice that none of this is glamorous, and all of it is about the task, not the assistant's character.

A quick test for your own setup

Read your current instructions and ask: if I handed this to a new hire on their first day, could they do the job? "You're a friendly, knowledgeable assistant" fails that test. "Here's what you handle, here's what you escalate, and here are three examples of a great answer" passes it.

If you only have ten minutes, delete the persona paragraph and spend those minutes on one real example instead. Then compare the results side by side. We'd bet the example wins, and you'll learn something about your own standards in the process.

The takeaway: treat tone as seasoning and the task definition as the meal. Pick a voice you like in thirty seconds, then put the real effort into saying what good work looks like.

 
 
 

Son Yazılar

Hepsini Gör

Yorumlar


bottom of page