# I am GPTed: "Prompt Engineering for People Who Actually Use AI"
---
**[INTRO MUSIC FADES]**
Hey everyone, it's Mal—your Misfit Master of AI, and welcome back to "I am GPTed," the show where we take all that fancy AI stuff and translate it into something you can actually use without needing a computer science degree.
So here's the thing about AI—it's like having a really smart friend who'll do exactly what you ask, no more, no less. And if you ask vaguely, they'll give you vague answers. Asking clearly? That's where the magic happens.
Today we're talking about **role-playing prompts**, and I promise this isn't about pretending to be a dragon in a D&D campaign. Though honestly, if that's your use case, AI's got you covered too.
## The Technique: Role-Playing Prompts
Here's how this works: instead of just asking your AI to help, you tell it to *be* something—an expert, a professional, a specific type of thinker. The AI then filters its response through that lens.
Let me show you the difference.
**Before:** "Help me write an email to my boss about my project."
Okay, you'll get something. Probably generic. Probably sounds like a robot wrote it.
**After:** "You're a senior strategist known for clear, confident communication. Help me write an email to my boss explaining why we need to pivot our project timeline."
Suddenly, you're getting answers that sound like they come from someone who actually knows what they're doing. The AI mimics the confidence, the structure, the reasoning of that role.
## Where This Actually Matters
Here's a practical one: let's say you're freelancing and need to pitch a client. You don't need another AI. You need your AI to *be* the kind of person who wins clients. So instead of "write me a pitch," try: "You're a seasoned consultant who specializes in making complex projects sound exciting but achievable. Write a 3-paragraph pitch for developing a custom dashboard for a small e-commerce company."
Boom. Different energy entirely.
## The Beginner Mistake (And Yeah, I've Made It)
People think more detail equals better results. Wrong. They throw entire documents at the AI and say, "Fix this." Then they get confused when the answer's mediocre.
I did this constantly. I'd dump three paragraphs of messy notes and wonder why the output was all over the place. The problem? The AI didn't know *what I actually wanted*.
The fix is simpler than you'd think: be specific about the outcome. "Fix this document" becomes "You're an editor focused on clarity. Tighten this copy so it sounds conversational and cuts the word count by 20%."
## Your Practice Exercise
Try this today—pick something you normally ask AI to do. Now rewrite that prompt with a role attached. Spend two minutes on it. See what changes. You'll notice the difference immediately, and that's how you build intuition about what works.
## Evaluating What You Get Back
Here's your checklist: Does it sound like *you*? Does it actually answer what you asked? Would you be embarrassed to send this to someone? If yes to the first two and no to the last—you're good. If the tone feels off, refine the role. Tell the AI exactly what kind of expert you need.
---
Thanks so much for listening to "I am GPTed." If you found this useful, please subscribe wherever you get your podcasts.
And remember—this has been a Quiet Please production. Head over to quietplease.ai to learn more.
Now go prompt something. You've got this.
**[OUTRO MUSIC]**
For more check out
https://www.quietperiodplease.com/and for some great deals go to
