Apply to my task
arXiv:2606.04057 ★ 83 Jun 2, 2026

The Invisible Lottery: Random Words in Your Prompt Secretly Pick the Approach for You

Key result

The paradox: you ask it to solve a problem, and the model silently decides how, based on random words in the context rather than your requirements. Naming the approach explicitly gets you a predictable result instead of a lottery. Name the method, structure or tone you want right in the prompt, and the model stops guessing from context. Neutral words shift the choice of approach by ~26 percentage points. Meaningful ones, by 40-100 points.

01

TL;DR

Every word in your prompt is a vote for some approach. You ask an LLM to solve a problem, and the model silently decides how to do it, and that decision is driven not by your requirements but by incidental context: the words around the task, the tone, the details you happened to mention. The researchers call this the "invisible lottery": you get one of many possible approaches, but you don't know which one won or why.

The problem is that any complex task has several equally correct solutions with fundamentally different properties. Ask about a negotiation strategy and you'll get a hardball or a soft one, depending on whether you mentioned a "startup" or a "corporation" earlier in the conversation. Ask for an article structure: "for readers" gives you one thing, "for a conference" something else entirely. You didn't choose; the context chose for you.

The study's key insight: naming the approach you want outright is the only reliable defense. The more precisely you state what exactly you want, the less the model has to guess on your behalf.

Want this for your own case? Apply this study to your task: AI adapts its method to what you are working on and writes the prompt.

02

Phenomenon Blueprint

A typical request:
[incidental context] + [task] → the model picks an approach on its own → ?

What happens inside:
The word "prototype"   → a lightweight, fast approach
The word "production"  → a robust, complex approach  
The word "academic"    → theoretically correct but fragile approach
Random words           → a ~26 pp shift even with no meaning attached

Defense:
[task] + [explicit name of the approach you want] → a predictable result

No explicit instruction: a lottery. With one: control.

03

Example in Practice

Task: Write an investor pitch for a meeting at a startup competition.

A typical prompt plays the lottery: if the conversation earlier included "quick," "draft," "rough sketch," you'll get an informal version. If it included "important meeting," "serious people," you'll get a different one. Neither is necessarily what you need.

Prompt that names the approach explicitly:

Write an investor pitch for Techstars Demo Day.

My product: [product description]
Audience: venture partners, typical check size $500K–$2M
Format: 3-minute spoken pitch + one slide

Approach: problem → solution → market → traction → team → ask.
Tone: confident, no jargon, no unnecessary hedging.
Don't suggest alternative structures; use exactly this one.

Result: The model will use the structure you gave it instead of guessing the format from context. You'll get a pitch with exactly the sequence of blocks and the tone you named, not the one that "won the lottery" because of the word "Techstars" or some other incidental context.

04

Why It Works

The LLM doesn't know which of the equally correct approaches you need. When a task allows several solutions (which is almost always), the model looks for signals in the context. It was trained on a vast body of text where "prototype" usually came with one kind of solution, "interview" with another, "academic" with a third. That's not a bug; it's what the model learned from.

The problem is that your prompt always contains incidental context: previous messages, the system prompt, the style of the question, the details you mentioned. All of it is signal. The study showed that even clearly neutral words (a team name, a color scheme) shift the choice by 26 percentage points on average. Meaningful words (a constraint, a role, the task context) shift it by 40–100 points.

Naming the approach works because it removes the ambiguity. The model doesn't hunt for signals; it's been told directly. It's not magic and not a trick, just a precise instruction instead of guesswork.

Control levers: - Name the approach/structure/method explicitly → eliminates the guessing - Rule out alternatives ("don't suggest other options") → locks in the choice - Remove incidental context (start a new chat for an important task) → resets the accumulated signals - Audit the prompt (ask the model which words in it could quietly influence the choice of approach) → makes the lottery visible

05

Prompt Template

{Task}

Audience/context: {who it's for / under what conditions}

Use exactly this approach: {name of the method / structure / style / logic}.
Don't choose an approach yourself; I've already specified what I need.
If my description is incomplete, ask before you start.

What to fill in: - {task}: the specific request, without extra context - {who it's for / under what conditions}: only what genuinely matters for the result - {name of the method / structure / style / logic}: an explicit description of the approach you want: "STAR structure," "firm tone with no hedging," "argue from data to conclusion," "three blocks: problem, solution, call to action"

Audit template (if you're not sure whether your prompt has hidden signals):

Read this prompt and find words or details that could 
quietly nudge you toward a particular style, structure 
or method, even if I didn't ask for it:

{paste your prompt}

For each such signal, explain what it pushes you toward 
and how to change it if I need a different approach.

🚀 Quick start: paste this into the chat:

Here's a template for controlling which approach an LLM picks. 
Adapt it to my task: [your task].
Ask me questions to fill in the fields.

[paste the template above]

The LLM will ask which approach you want and what exactly it shouldn't pick on its own, because the template doesn't work without that: explicit naming is the whole point of the method.

06

Limitations

⚠️ Only works when you know the approach you need: If you're not sure yourself which method/structure/style you need, you can't name it explicitly. In that case, first ask the model to list the options and explain how they differ, then choose.

⚠️ Doesn't protect against built-up context in a long conversation: If the previous 20 messages created a strong contextual signal, one explicit instruction may not outweigh it. For critical tasks, it's better to start a new chat.

⚠️ Behavior depends on the model: The same words affect GPT, Claude and Gemini differently. What shifts the choice by 80 points in one model might shift it by 20 in another. Explicit naming works everywhere, but specific signals vary.

07

How They Studied It

The idea was simple: take tasks that have several correct solutions with different properties, then watch what the model chooses when only the incidental context around the task changes.

The researchers ran 46,535 experiments across 11 tasks and 15 model configurations (GPT-5, Claude Sonnet 4, Gemini 3 Flash and others). The task always stayed the same; only the "incidental" context changed: a word at the start of the prompt, a mentioned role, the import style, a timestamp. The output was classified by the type of solution chosen, based on code-structure analysis: not whether it was right or wrong, but which of the correct options the model picked.

The surprise: even words with no meaning attached (random identifiers, color schemes, team names) shifted the choice by 26 percentage points on average. Meaningful words made up to a 100-point difference. Practically no model was immune, though the strength of the effect varied. A curious detail: at temperature 0 (which many consider "deterministic"), 21% of cells still produced different results on repeated requests. The lottery doesn't go away even without randomness.

The study confirmed: the problem isn't code quality; almost everything passed the tests. The problem is an invisible selection policy shaped by context. For chat users this means the same dynamic applies to any request with several equally valid answers.

08

Adaptations and Extrapolations

💡 Adaptation for Analysis and Decision-Making

The principle applies anywhere a task has several equally logical answers.

Analyze the situation: [description].

Use exactly this analysis framework: SWOT.
Don't switch to other models. Don't draw a "what to do" conclusion; 
just a structured analysis across the four quadrants.

Without explicit naming, the model might apply PEST, a risk matrix, or narrative analysis: all correct, but not what you need.


🔧 Technique: Audit for Hidden Signals Before an Important Request

Before you send a critical prompt, check it:

Find words and details in this prompt that could quietly 
steer you toward a particular approach, tone or structure.
For each signal, say what it pushes you toward.

Prompt to check:
[paste your prompt]

This makes the "invisible lottery" visible, and you decide whether to keep the signals or remove them.


🔧 Technique: "Reset the Context" Before an Important Task

If you've been working in a long conversation, start a new chat. Then:

For this task I want a neutral start with no accumulated context.
Confirm that you're starting from a clean slate before I describe the task.

Especially useful when the previous conversation was in a different tone or domain.

09

Resources

Paper title: The Invisible Lottery: How Subtle Cues Steer Algorithm Choice in LLM Code Generation

Authors: Akanksha Narula, Mofasshara Binte Rafique, Laurent Bindschaedler

Institutions: Max Planck Institute for Software Systems (MPI-SWS), Saarbrücken, Germany; Independent Researcher, Switzerland

Publication: Proceedings of the 43rd International Conference on Machine Learning (ICML 2026), Seoul

Contact: [email protected]

Research digest

Key result

The paradox: you ask it to solve a problem, and the model silently decides how, based on random words in the context rather than your requirements. Naming the approach explicitly gets you a predictable result instead of a lottery. Name the method, structure or tone you want right in the prompt, and the model stops guessing from context. Neutral words shift the choice of approach by ~26 percentage points. Meaningful ones, by 40-100 points.

Principle

The model was trained on a vast body of text. There, "prototype" came with one kind of solution, "production" with another, "academic" with a third. It sees a new request and looks for familiar signals. The kicker: the words "color scheme" have nothing to do with the algorithm, yet they still change the choice of approach. Explicit naming shuts that search down. Not a trick, just a precise instruction instead of guesswork.

Why it works

A complex task usually has several correct solutions with different properties. The model doesn't know which one you need. It looks for hints everywhere: previous messages, the style of the question, random details. Everything becomes a signal. Neutral words move the choice by ~26 points. Meaningful ones, by 40-100. Without an explicit instruction you get one of the options, but you don't know which one or why. Name the approach directly and the signal-hunting stops.

When to apply

Any task with several equally correct solutions → specifically pitches, articles, negotiation scripts, report structures, code, especially when a particular style or structure matters, not just "something good." NOT a fit if you don't know which approach you need: first ask the model to list the options and explain the differences, then choose one and name it explicitly.

Mini recipe

1. Decide which approach you need yourself: Don't hand that decision to the model. Think: "STAR structure," "firm tone with no hedging," "argue from data to conclusion." 2. Name it explicitly in the prompt: Add the line "Use exactly this approach: [name]. Don't choose on your own." 3. Rule out alternatives: The phrase "Don't suggest other options" locks in the choice. Without it, the model may still offer "or you could do it this way." 4. For important tasks, use a new chat: A long conversation accumulates signals. A critical request is better made in a clean window. 5. Audit the prompt (if needed): Ask the model to find words in your request that quietly pull toward a particular approach: `Read this prompt and find words that could nudge you toward a particular style or structure, even if I didn't ask for it: [paste prompt]. For each signal, explain what it pushes you toward.`

Examples

[BAD]: `Write an investor pitch for a startup competition` [GOOD]: `Write an investor pitch for Demo Day. Audience: venture partners. Use exactly this structure: problem → solution → market → traction → team → ask. Tone: confident, no jargon, no unnecessary hedging. Don't suggest alternative structures; use only this one.`

In plain words

Here's the deal: an LLM isn't a calculator, it's a giant association machine that's constantly playing an invisible lottery. When you give a model a task that can be solved more than one way, it doesn't pick the best one. It latches onto random marker words in your prompt that subconsciously pull it one way or another. The researchers proved that the model settles on a strategy before it even starts writing code or text, simply because you happened to say "fast" instead of "efficient."

It's like asking a carpenter to "make a stool," and he glances at your sneakers and decides it should be ultra-modern. Technically he did the job, but you wanted a classic oak one. Models work the same way: the tiniest nuance in tone or context becomes the deciding factor that steers the selection algorithm. You think you're running the show, but you're really just flipping a coin whose outcome depends on how you said hi to the bot.

In coding this shows up in the harshest way: implicit cues make the model choose between lean code and bloated "enterprise" code purely based on whether you mentioned a "prototype" or "business logic." If your prompt hints at an academic style, the model will hand you an elaborate structure even when it's completely unnecessary. This isn't a deliberate choice of the optimal path; it's statistical drift toward the data it was trained on.

The study looked at code generation, but this principle is a fundamental law of working with context. It applies everywhere, from writing pitches to legal advice. If you don't set firm boundaries, the model will fill them in for you based on junk signals in your own text. Every extra adjective isn't just decoration; it's a control lever you're pulling without even noticing.

Bottom line: if a result looks weird to you, it's not that "the model is being dumb"; it's that you won a lottery prize you didn't want. To stop depending on luck, you have to burn out every bit of ambiguity and lock in the approach explicitly, or the model will keep reading tea leaves in your vocabulary. Controlling context isn't about politeness, it's about predictability, and without it any work with AI turns into a casino.

AI lab assistant

Apply this study to your task

Describe what you're working on. AI takes the method and the measured results from this paper and adapts them to your case, or writes a ready prompt built on them.

Based on The Invisible Lottery: Random Words in Your Prompt Secretly Pick the Approach for You arXiv:2606.04057

Sign in to apply this study New accounts get 50 free credits.