TL;DR: A 3-step prompt forces AI to list causes, identify lurking variables that could break each theory, and propose experiments to find the real driver. Turns vague trend analysis into something you can actually act on.
Why AI Usually Gets Causation Wrong
Pattern matching is AI’s default mode. Paste a trend, get a confident list of possible causes. None of them tested. None of them accounting for confounding factors. It’s correlation wrapped in a smart-sounding paragraph.
Here’s what that typically looks like. You tell the model your email open rates dropped 15% last month. It comes back with four reasons: subject lines got weaker, send time changed, list quality degraded, inbox placement dropped. All plausible. All equally unsupported. You’re no closer to knowing what to actually fix.
The problem isn’t the model’s knowledge. It’s the framing. When you ask “what caused this,” you’re inviting a brainstorm. The model’s job becomes generating plausible-sounding options, not finding the true answer. Without a forcing function, it will confidently deliver a list and call it analysis. That’s not analysis. That’s an expensive guess with good grammar.
The Logic Architect prompt from r/PromptEngineering addresses this directly. It forces the model through three steps:
- List 3 potential causes for the trend
- For each cause, identify a lurking variable that could invalidate the theory
- Propose an experiment to prove the actual driver
The lurking variable step is where the real value is. It’s not enough for the model to say sales dropped because of X. It has to immediately ask what else could explain this and make X wrong. That’s falsification thinking, and it cuts through a lot of confident-sounding nonsense.
Take the email example. If the model says “open rates dropped because subject lines got weaker,” the lurking variable step forces it to ask: did you change your sending domain, did Gmail update its filtering, did a large segment of your list go cold at the same time? Any of those could produce the exact same dip with no connection to subject line quality at all. The lurking variable check holds the hypothesis up to the light before moving on.
The experiment proposal step closes the loop. It’s not enough to identify what might be true. A good analyst asks what data would prove it. The model has to propose a test with a falsifiable outcome, not just a vague recommendation to “dig deeper.” That structural shift is what makes this prompt worth running repeatedly, not just once as a curiosity.
Use Cases
- 🔍 Marketing: CTR dropped 30% last week. Is it the creative, the audience segment, or an algorithm change? Run the prompt against your campaign data and the model will surface things like recent platform privacy updates or seasonal audience behavior shifts that could invalidate the “bad creative” theory before you brief a designer on a fix that won’t move the needle.
- 📊 Product: Users are churning after day 3. Is it onboarding, feature discovery, or just the wrong users coming in? The lurking variable step often catches acquisition source as the real confound here. Users from paid ads churn faster not because of anything wrong in the product, but because of the promise that brought them in. Fix the ad, not the app.
- 💰 Revenue: Up 20% this month. Real growth or a few large one-off deals skewing the averages? This is where the prompt earns its keep on good news too. Falsification thinking works both directions. Celebrating a trend that isn’t repeatable costs you just as much as misdiagnosing a decline, because you optimize for the wrong thing going forward.
Prompt of the Day
[Describe Trend]. 1. List 3 potential causes. 2. For each cause, identify a lurking variable that could invalidate the theory. 3. Propose an experiment to prove the actual driver.
Paste your trend where the placeholder is. Watch the model pressure-test its own assumptions instead of just confirming them.
A few things that make this work better in practice. Be specific when you describe the trend. Include the timeframe, the magnitude, and any environmental changes that happened around the same time. The more context you give up front, the more targeted the lurking variables become. Vague inputs produce generic outputs. Specific inputs produce something you can actually take into a meeting.
You can also run this more than once with different framings. If you already suspect the cause, describe the trend without hinting at your theory and see if the model lands there independently. If it doesn’t, that’s useful information. If it does, the lurking variable check will tell you whether your theory survives scrutiny before you commit resources to acting on it.
The Takeaway
Asking AI what’s happening is easy. Getting it to explain why and then challenge its own answer is the part most people skip. That gap is the difference between an observation and something worth acting on.
Most AI usage in business analysis stops at the brainstorm phase. Someone pastes a number, gets a list, picks the most plausible item, and runs with it. No test, no falsification, no second-order check. The Logic Architect prompt forces all three steps before you reach a conclusion. That’s not a small upgrade to your workflow. It’s the difference between using AI as a yes-machine and using it as something that actually pushes back on bad reasoning, including its own.
Want more prompts that actually change how AI reasons? Subscribe to Cyber Corsairs. We cover the best ones every week.
Frequently Asked Questions
Q: What exactly is a ‘lurking variable’ and why does it matter?
A lurking variable is a hidden factor that might actually explain a trend better than your initial hypothesis. For example, if you notice coffee sales rising, you might assume it’s weather-related, but the real driver could be a new café opening nearby. By identifying lurking variables, you catch your own faulty assumptions before they end up in your final answer, making your analysis way more rigorous.
Q: How does this prompt differ from just asking AI to explain why something happens?
This prompt forces falsification thinking instead of pattern matching. Regular prompts often accept the first plausible explanation, but this one makes you list multiple causes, challenge each one, and propose an experiment to prove which is real. That extra structure catches the correlation-vs-causation trap that most AI explanations slip into.
Q: Do I need domain expertise to use this prompt effectively?
Nope. The prompt’s structure does the heavy lifting by walking you through logical steps. That said, deeper knowledge of your topic helps you spot lurking variables more naturally. Even without expertise though, the framework will catch obvious mistakes and push you to think critically, which is already better than getting a surface-level answer.
The ‘Causal Inference’ Stress-Test.
by u/Significant-Strike40 in PromptEngineering