The Persona Pattern (how assigning AI a role changes output quality)
Assign specific functional roles to unlock deeper perspective, vocabulary, and professional critique.
Key Takeaways
- Vague personas produce buzzwords; strong personas define function, worldview, and priorities
- Specify what the persona cares about most (the metric or goal)
- Include what the persona actively looks for — skepticism and bias
- Define the vocabulary level and how practitioners at that level communicate
- An adversarial persona stress-tests proposals better than any review checklist
The Diagnostic Context
When you ask an AI model to "review this proposal," you will usually get surface-level grammar checks and polite encouragement. This happens because the model has no standard for critique. Assigning a sharp, defined persona gives the model an operational worldview, a distinct lens through which to evaluate information, and the vocabulary of a specialist.
The Core Technique
A weak persona is vague: "Act as an expert marketer." This produces buzzwords. A strong persona defines function, worldview, and priorities:
- Perspective & Priority: What metric or goal does this persona care about most?
- Skepticism & Biases: What flaws will this persona actively look for?
- Tone & Vocabulary: How do practitioners at this level speak to peers?
Compare these two framing methods:
- Standard Prompt: "Review this feature roadmap."
- Persona Pattern: "Act as a cynical B2B SaaS Chief Technology Officer focused entirely on technical debt and server scalability. Review this feature roadmap. Identify which 3 features pose the highest maintenance risk and explain why our engineering overhead could spike."
The second prompt suppresses generic cheerleading. It primes the model’s attention mechanism to search for vulnerabilities, edge cases, and architectural trade-offs.
Try This Right Now
Take an email, pitch, or memo you are working on. Paste it into an AI chat with this prompt: "Act as an impatient procurement director who has 90 seconds between meetings. Read this memo and list the top three reasons you would reject or delay this request." Review how the pointed critique highlights gaps you missed.
Tip: Knowledge only becomes capability once you run the prompt yourself.