Role-Playing Alien Minds

“Pretend you’re a marketing expert.” This is, give or take, the most common role-playing prompt on the internet. It is also almost completely useless. Not because role-playing is a bad technique — it’s an extraordinarily powerful one — but because “pretend you’re a marketing expert” is the cognitive equivalent of asking someone to “think differently.” It’s a direction without a destination.

This chapter is about constructing genuinely alien cognitive perspectives and using AI to inhabit them with enough fidelity to produce insights you couldn’t reach on your own. Not surface-level role-playing, where the AI adopts a label and generates slightly different phrasing for the same ideas. Deep structural role-playing, where you specify a worldview, a set of experiences, a collection of biases, and a characteristic way of processing information — and the AI produces thinking that is recognizably from that perspective.

The difference is not subtle. It’s the difference between asking “what would an economist say?” and asking “what would someone say who spent twenty years at the Fed watching monetary policy decisions that looked rational in the moment produce cascading failures years later, and who now believes that the biggest risk in any system is the interaction effects between individually reasonable decisions?”

The first gives you Economics 101. The second gives you something you might actually learn from.

Why Thin Personas Produce Thin Thinking

When you tell an AI to “think like an economist,” you’re invoking a stereotype. The AI produces something that sounds vaguely economist-like — references to incentives, trade-offs, market dynamics — but it’s drawing from the average of all economic thinking in its training data. You get a smoothed-out, median perspective that lacks any of the edges, quirks, or hard-won insights that make real expert thinking valuable.

This is exactly analogous to what happens when you ask a non-expert human to “think like an economist.” They produce their impression of economic thinking, which is a caricature built from popular articles and half-remembered textbook concepts. The actual thinking of a working economist is nothing like this caricature. It’s shaped by specific experiences, specific failures, specific intellectual traditions, and specific arguments with specific colleagues over specific papers.

The same principle applies to every domain. “Think like a designer” produces generic design thinking. “Think like someone who trained under Edward Tufte and now believes that 90% of visual design in business is actively misleading because it prioritizes aesthetics over information density, and who evaluates every dashboard by asking ‘what decision would this display cause someone to make, and is that the right decision?’” produces thinking that’s actually useful.

The specificity is the technique. The richer and more detailed the cognitive profile you construct, the more alien and therefore more valuable the perspective becomes.

A Taxonomy of Useful Alien Minds

Over two years of systematic experimentation, I’ve identified several categories of alien minds that are consistently useful across domains. Each represents a fundamentally different way of processing information, and each produces insights that the others miss.

The Hostile Auditor

Core perspective: Everything is potentially fraudulent, incompetent, or self-deceptive. The Hostile Auditor assumes that the person presenting the plan is, at best, unconsciously biased toward optimism and, at worst, actively hiding problems. They look for what’s not being said, what numbers don’t add up, and what narrative convenience is doing the work of actual evidence.

When to use: Any time you’re evaluating a plan, a proposal, or a claim — especially your own. The Hostile Auditor is particularly valuable when you’re feeling confident, because confidence is when your guard is lowest.

Prompt template:

I want you to adopt the perspective of a forensic auditor who has spent 25
years investigating corporate failures. This person assumes that every plan
contains at least three things the planner is either hiding or genuinely
doesn't see. They are not cruel, but they are relentless. They follow the
money, the incentives, and the unstated assumptions.

Their approach:
- What numbers have been presented without context?
- What narrative is being used to explain away potential problems?
- Where are the incentives misaligned with the stated goals?
- What questions would the planner prefer not to be asked?

Apply this perspective to the following:
[YOUR PLAN OR PROPOSAL]

The Naive Newcomer

Core perspective: Nothing is obvious. The Naive Newcomer has no domain knowledge, no insider vocabulary, and no sense of “how things are done.” They ask the questions that everyone in the room stopped asking years ago because the answers seemed obvious. Except sometimes those answers aren’t obvious — they’re just unexamined.

When to use: When you suspect your plan is based on “that’s how we’ve always done it” thinking. When you’re in a mature industry or organization where assumptions have calcified into facts. When you need to rediscover the first principles underneath layers of institutional habit.

Prompt template:

I want you to adopt the perspective of an intelligent person who has never
worked in this industry and has no preconceptions about how things should
be done. They are smart, curious, and slightly confused by things that
insiders take for granted.

For each element of what I describe, this person asks:
- Why does it work this way?
- What would happen if you just... didn't do that?
- Who decided this was the right approach, and when?
- Is there evidence this is optimal, or is it just familiar?
- This seems complicated — is the complexity necessary or accumulated?

They are genuinely trying to understand, not being difficult. But they
refuse to accept "that's just how it works" as an answer.

Here's what I'd like them to examine:
[YOUR SYSTEM, PROCESS, OR PLAN]

The Cross-Domain Expert

Core perspective: “We solved this problem thirty years ago in [different field].” The Cross-Domain Expert sees structural similarities between your problem and problems that have been thoroughly analyzed in another domain. They import solutions, frameworks, and failure modes from that other domain — some of which are directly applicable and some of which are usefully provocative even when they don’t directly apply.

When to use: When you feel stuck in your domain’s conventional approaches. When the problem feels familiar but the solutions don’t seem to work. The Cross-Domain Expert is most valuable when the source domain is structurally similar but superficially different from yours.

Prompt template:

I want you to adopt the perspective of someone who is a deep expert in
[SOURCE DOMAIN] but has just encountered [TARGET DOMAIN] for the first
time. This person keeps seeing parallels between the two domains.

Their expertise in [SOURCE DOMAIN] gives them the following lenses:
- [KEY CONCEPT 1 from source domain]
- [KEY CONCEPT 2 from source domain]
- [KEY CONCEPT 3 from source domain]
- [CHARACTERISTIC FAILURE MODE from source domain]

They look at my problem and say "This reminds me of..." and then draw
specific, structural parallels. They are not making loose metaphors —
they are identifying genuine structural similarities that suggest
specific approaches.

My problem:
[YOUR PROBLEM]

For example:

I want you to adopt the perspective of someone who is a deep expert in
epidemiology but has just encountered software security for the first
time. This person keeps seeing parallels between the two domains.

Their expertise in epidemiology gives them the following lenses:
- Disease transmission networks and how single nodes become superspreaders
- The difference between containing an outbreak and preventing one
- Herd immunity thresholds and what happens just below them
- The way individual rational behavior (avoiding vaccination costs)
  produces collectively catastrophic outcomes

They look at my security architecture and say "This reminds me of..."
and then draw specific, structural parallels.

My problem:
[YOUR SECURITY ARCHITECTURE]

The Historical Figure

Core perspective: The weight of a specific intellectual tradition and personal history. This isn’t “what would Feynman say?” — it’s a reconstruction of how a specific historical thinker would process your problem given their known methods, values, and characteristic approaches.

When to use: When you want a specific, well-documented thinking style applied to your problem. Historical figures work best when their thinking methods are well-documented (through biographies, letters, recorded interviews) and when those methods are genuinely different from your own.

Prompt template:

I want you to adopt the thinking style of [HISTORICAL FIGURE], but not
in a superficial way. I want you to apply their characteristic METHODS,
not just their conclusions.

Key elements of their approach:
- [METHOD 1: e.g., "Feynman's habit of reducing problems to the simplest
  possible example before attempting a general solution"]
- [METHOD 2: e.g., "Feynman's insistence on being able to explain any
  concept to a first-year student as a test of genuine understanding"]
- [METHOD 3: e.g., "Feynman's suspicion of elegance for its own sake —
  a beautiful theory that doesn't match experiment is wrong, period"]

Apply these methods — not their personality or mannerisms — to the
following problem:
[YOUR PROBLEM]

The key distinction is between impersonation and method application. Impersonation is fun but useless — you get an AI doing a bad impression of Einstein. Method application is genuinely powerful — you get a specific, well-tested approach to thinking applied to your problem.

The Future Archaeologist

Core perspective: It is fifty years from now, and this person is studying our time period the way we study the 1970s — with the benefit of hindsight, with amusement at our blind spots, and with genuine curiosity about why smart people made the choices they did.

When to use: When you want to escape the assumptions of the current moment. When you suspect that something everyone takes for granted now will look obviously wrong in retrospect. The Future Archaeologist is particularly useful for strategic decisions, because strategic errors are almost always visible in retrospect.

Prompt template:

I want you to adopt the perspective of a historian writing in 2075 about
the decisions being made in our industry/field right now. This person
has the benefit of knowing how things turned out. They are sympathetic
but clear-eyed about the systematic errors of our era.

From their future perspective:
- What are we currently doing that will look obviously misguided in
  hindsight?
- What are we ignoring that will turn out to have been critical?
- What assumptions are we making that are products of this specific
  moment in time rather than timeless truths?
- What would they identify as the characteristic blind spot of
  decision-makers in our era?

Apply this perspective to:
[YOUR SITUATION OR DECISION]

The Failure Librarian

Core perspective: “I have read every post-mortem, every case study of failure, every after-action report. I don’t predict success or failure — I match patterns. And I’ve seen your pattern before.”

When to use: When you’re about to make a big bet and you want to know if there’s historical precedent for how it might go wrong. The Failure Librarian doesn’t tell you not to do something — it tells you how similar attempts have failed in the past, so you can avoid repeating their mistakes.

Prompt template:

I want you to adopt the perspective of someone who has spent their career
studying why plans, projects, and strategies fail. They are a walking
encyclopedia of failure modes. They are not pessimistic — they believe in
learning from failure — but they have an encyclopedic knowledge of how
things go wrong.

When they look at a plan, they automatically pattern-match against known
failure modes:
- What historical failures does this plan resemble?
- What category of failure is this most vulnerable to? (e.g., planning
  fallacy, coordination failure, misaligned incentives, capability gap,
  market timing, etc.)
- What did the people in those historical cases wish they had done
  differently?

Analyze this plan:
[YOUR PLAN]

Building Custom Alien Minds

The taxonomy above covers the most generally useful perspectives, but the real power of this technique is in building custom alien minds tailored to your specific situation. Here’s the framework for constructing them:

Step 1: Identify what you’re missing. What kind of thinking would be most useful right now? Are you missing skepticism? Cross-domain insight? Historical perspective? Practical experience? Theoretical rigor?

Step 2: Specify the experience base. Don’t just name a role — describe the experiences that would shape this perspective. What has this person seen? What have they learned from it? What are they cynical about? What are they optimistic about?

Step 3: Specify the characteristic methods. How does this person think? Do they start from first principles or from historical precedent? Do they focus on details or systems? Do they trust data or narrative? Do they look for what’s present or what’s absent?

Step 4: Specify the biases. Every useful perspective has productive biases. The Hostile Auditor is biased toward finding problems. The Naive Newcomer is biased toward simplicity. These biases are features, not bugs — they’re what makes the perspective different from your own.

Step 5: Give the AI explicit instructions about depth and specificity. Tell it to be specific, to cite patterns, to provide examples. Without this instruction, even a well-constructed persona tends to drift toward generality.

The master template:

I want you to adopt a specific cognitive perspective for this conversation.

EXPERIENCE BASE:
[What has this person seen, done, and learned over their career?]

CHARACTERISTIC METHODS:
[How does this person approach problems? What do they look at first?
What questions do they always ask?]

PRODUCTIVE BIASES:
[What is this person systematically biased toward noticing? What do
they tend to overweight? What do they tend to ignore?]

COMMUNICATION STYLE:
[How does this person express their analysis? Are they blunt?
Methodical? Narrative-driven?]

INSTRUCTIONS:
Maintain this perspective consistently throughout our conversation.
Be specific — reference patterns you've seen, cite examples, provide
detailed analysis. Do not break character to provide balanced
assessments. I want this perspective in its full, biased, useful form.

Here's what I'd like you to analyze:
[YOUR TOPIC]

A Worked Example: The Alien Minds Panel

One of my favorite techniques is to run the same problem through multiple alien minds in sequence and then synthesize their perspectives. Here’s a condensed example.

The problem: A mid-size company is considering whether to build or buy a critical piece of internal tooling. The build option is cheaper long-term but requires diverting engineering resources for six months. The buy option is more expensive but immediate.

The Hostile Auditor says: “The six-month estimate for the build option is a lie. Not intentionally — it’s a planning fallacy. I’ve never seen an internal tooling project that came in on time. Double the estimate as a starting point, then ask yourself whether a twelve-month diversion of engineering resources is still acceptable. Also: who made the cost comparison? If it’s the engineering team, they’re biased toward building because building is interesting and buying is boring. Follow the incentives.”

The Naive Newcomer says: “I’m confused about something basic. You say this tooling is critical, but you’ve apparently been operating without it until now. How critical is it really? What are you doing instead right now, and why does that need to change? I also notice you’re framing this as build vs. buy, but is there a third option — don’t build, don’t buy, and solve the underlying problem differently?”

The Cross-Domain Expert (from construction project management) says: “In construction, we learned decades ago that build vs. buy decisions are almost never about the direct costs. They’re about the opportunity cost of management attention. While your engineering team is building this tool, who is making decisions about it? Who is changing requirements? Who is managing scope? In construction, the biggest cost of custom-building anything is the management overhead that nobody budgets for.”

The Future Archaeologist says: “From 2075, it’s clear that the mid-2020s were a period where companies dramatically overinvested in internal tooling because they underestimated how quickly the commercial tooling market would mature. Many of the custom tools built in this era were obsolete within three years as commercial alternatives became both cheaper and better. The characteristic error was believing that your needs were more unique than they actually were.”

Four perspectives. Four completely different analyses. None of them is “right” in isolation, but together they surface at least three considerations that a single-perspective analysis would miss: the planning fallacy on the build estimate, the false binary of build-vs-buy, and the probability that commercial alternatives will improve faster than expected.

This is why the technique works. Each alien mind sees something the others miss. The synthesis is where the insight lives.

The Specificity Gradient

There’s a direct and measurable relationship between the specificity of your persona construction and the quality of the output. I think of this as the Specificity Gradient:

Level 0 — Label only: “Think like a doctor.” This produces generic output indistinguishable from a Google search.

Level 1 — Role plus domain: “Think like an emergency room physician.” Slightly better. The AI focuses on ER-specific considerations: triage, time pressure, information scarcity.

Level 2 — Role plus experience: “Think like an ER physician who has been practicing for 20 years in an underfunded urban hospital.” Now we’re getting somewhere. The experience base shapes the thinking in useful ways — resource constraints, dealing with systemic failures, pragmatism over idealism.

Level 3 — Role plus experience plus methods: “Think like a 20-year ER physician who has developed a personal heuristic: ‘When in doubt, assume the situation is more severe than it appears, because the cost of overreaction is almost always lower than the cost of underreaction.’” This is genuinely useful. The specified heuristic produces a specific analytical lens that generates specific insights.

Level 4 — Full cognitive profile: The master template above. Experience base, characteristic methods, productive biases, communication style. This is the level that consistently produces thinking you couldn’t have reached on your own.

The effort to construct a Level 4 persona is nontrivial — it takes ten to fifteen minutes of thoughtful prompt construction. But the output difference between Level 1 and Level 4 is not incremental; it’s categorical. Level 1 gives you something you could have thought of yourself. Level 4 gives you something you genuinely could not.

Common Mistakes

Asking the AI to play a real, living person. “Pretend you’re Elon Musk and analyze my startup idea.” Beyond the obvious ethical issues, this doesn’t work well because the AI’s model of a living person is built from public statements, media coverage, and other filtered sources. You get a caricature, not a perspective. Specify thinking methods, not identities.

Breaking the persona too quickly. People construct a detailed persona, get one response, and then immediately break frame to ask “okay, but what do you really think?” The value of the persona is in sustained engagement. Stay in frame for at least several exchanges before stepping back to evaluate.

Using only one alien mind. Any single perspective, no matter how well-constructed, has blind spots. The panel approach — multiple alien minds analyzing the same problem — is consistently more valuable than any single perspective.

Constructing personas that are too close to your own. If you’re a software engineer and you construct a persona of a slightly different kind of software engineer, you’re not getting an alien mind — you’re getting a minor variation on your own thinking. Push further. The most valuable alien minds are the ones that make you slightly uncomfortable because they see the world so differently from you.

Forgetting to specify what you want from the persona. A well-constructed persona with no specific question or task will produce generic musings. Pair a detailed persona with a specific analytical task: “Analyze this plan,” “Evaluate this decision,” “Identify what I’m missing.”

The Deeper Point

Role-playing alien minds isn’t ultimately about the AI. It’s about the limits of your own perspective and the difficulty of escaping them. Every time you construct a detailed persona that sees the world differently from you, you’re acknowledging — concretely, practically — that your way of seeing things is one way, not the way.

The alien minds don’t have to be right. They don’t even have to be realistic. They have to be different enough from your own thinking to break the grip of your default perspective. The AI is the medium, but the message is epistemic humility: you can’t see everything from where you’re standing, and the things you can’t see might be the things that matter most.

The prompts are in this chapter. The taxonomy is a starting point. The real skill is in learning to construct personas that complement your own blind spots — and that requires knowing what your blind spots are, which is, of course, the fundamental challenge this entire book is about.