Use Role-Play Prompts for Better Results

5 min read

There's one trick that consistently produces better output from your AI PA, and it takes about five seconds to use. Tell it who to be. "You're a senior lawyer." "Write this like a CFO." "Pretend you're a wedding planner." It sounds silly. It works ridiculously well.

Why Roles Change Everything

When you tell your PA "draft an email about the overdue payment," it'll write something perfectly fine. Professional, clear, gets the job done. But when you say "you're a senior partner at a law firm — write a firm but professional follow-up to a client who's 60 days overdue," the output transforms.

Suddenly the language is tighter. The tone carries authority. The structure follows what an actual law firm partner would write. Your PA isn't guessing at the register — you've given it a clear frame to work within.

This isn't some prompt engineering hack. It's just how communication works. When you tell a human writer "write this like a CEO would say it," they immediately adjust their vocabulary, sentence length, and level of directness. Your PA does the same thing, just faster.

Roles That Actually Work

Not all roles are equally useful. Here are the ones our users get the most mileage from:

The Tough Professional. "You're a senior corporate lawyer." Perfect for demand letters, overdue payment reminders, contract negotiations, or any communication where you need weight behind the words without being aggressive. The output will be precise, confident, and structured.

The Warm Connector. "You're a hospitality director at a 5-star hotel." Use this for client onboarding emails, welcome messages, or thank-you notes. The output becomes gracious and personal without crossing into saccharine.

The Strategist. "You're a McKinsey consultant." Want to analyze a business problem, structure a proposal, or create a SWOT analysis? This role produces structured, analytical, jargon-appropriate output. It thinks in frameworks.

The Creative. "You're a copywriter at an award-winning ad agency." Social media posts, marketing copy, pitch decks, event descriptions. The output gets punchier, more visual, more memorable.

The Explainer. "You're a teacher explaining this to a 12-year-old." Surprisingly powerful for simplifying complex documents, summarizing legal contracts in plain language, or helping you understand something technical. If your PA can explain it to a kid, you'll understand it too.

Combining Roles With Context

The real power comes from stacking a role with specific context. Compare these two:

The second version gives your PA a persona, a situation, and constraints. The output will be dramatically more useful — specific, appropriately toned, and structured like someone in that actual role would write it.

This Isn't Prompt Engineering

We know what you're thinking. "Didn't you just tell me I don't need prompt engineering?" Correct. Role-playing isn't prompt engineering. It's context setting.

When you brief a human assistant on a task, you naturally give them context: "This is for a formal audience" or "Keep it casual, it's for my buddy." A role is just shorthand for a bundle of context — tone, vocabulary, structure, level of formality — delivered in three words instead of thirty.

You don't need a course to do this. You don't need a template. You just need to answer one question before you give an instruction: who should be writing this?

Quick-Start: Try These Today

Next time you need something from your PA, try prefixing it with a role:

Five extra words. Dramatically better output. No engineering degree required.