Thought Experiments: How to Test Ideas Without Leaving Your Chair

What is a thought experiment?

A thought experiment is an imagined test. You set up a scenario, apply the rules you believe, and reason through what would happen. If the outcome contradicts itself or common sense, something in your starting assumptions is wrong.

Its power is that it is free and fast. You do not need a lab, a budget or permission. You need a clear setup and the discipline to follow the logic where it leads, even when it leads somewhere you would rather not go. That second part is the hard bit, because the human tendency is to stop reasoning once a conclusion feels comfortable.

For decisions, thought experiments let you test a plan before you pay for it. “What happens in month three if our biggest customer leaves?” is a thought experiment. So is “Would I still take this job if the salary were the same as now?”

Where it comes from

Philosophers used imagined scenarios long before anyone named the method: Zeno’s paradoxes and Plato’s Ring of Gyges are ancient examples. The German word Gedankenexperiment is usually credited to the physicist Ernst Mach in the 19th century.

Two physics examples show how strong the method can be.

Galileo’s falling bodies. Aristotle’s physics held that heavier objects fall faster than lighter ones. In Two New Sciences (1638), Galileo offered an imagined counterexample. Tie a heavy stone to a light one. If heavier things fall faster, the light stone should drag on the heavy one, so the pair falls slower than the heavy stone alone. But the pair is heavier than the heavy stone alone, so it should fall faster. The same theory predicts both outcomes, so the theory is broken. Galileo concluded that, apart from air resistance, they should fall at the same rate.

Einstein’s light beam. In his Autobiographical Notes, Einstein recalled wondering, at about 16, what he would see if he could travel alongside a beam of light. By the physics of the time, he should see a frozen electromagnetic wave, which seemed impossible. He later described this puzzle as an early seed of special relativity (1905).

Other famous examples include Schrödinger’s cat (1935), Maxwell’s demon in thermodynamics, and the trolley problem introduced by philosopher Philippa Foot in 1967.

How to use thought experiments

1. State the belief or plan precisely. “Our customers care most about price” or “Moving cities will make me happier.” Vague beliefs cannot be tested, even in your head.
2. Build a concrete scenario. Pick a specific person, day or situation. “A customer with a budget who finds a competitor 20% cheaper but slower to deliver.” Specifics force the logic to run.
3. Push to an extreme. Ask what happens if the variable goes to zero, doubles or becomes infinite. Galileo combined two stones; you can double your price or remove your main feature. Extremes expose hidden assumptions.
4. Follow the consequences, not your hopes. Walk through what happens next, and next after that. This is second-order thinking in imagined form.
5. Look for the contradiction or surprise. If your scenario produces a result you would reject, find which assumption caused it. That is your finding. Then, where possible, check it against the real world.

3 real-world examples

Business

Say a founder believes users want more features. A thought experiment: imagine the product with twice as many features. What does the first screen look like? How long does onboarding take? Which support tickets arrive? Running it through makes it obvious that more features would bury the core one. The founder then asks the reverse: what if we removed half? That version is easier to picture working, and it becomes a real test. (A hypothetical example.)

Personal life

Choosing between two job offers, you can imagine a specific Tuesday in each role a year from now. When do you wake up? Who do you talk to? What are you worried about at 4 p.m.? A concrete imagined day often reveals more than a pros and cons list, because it forces you to picture the parts you would otherwise skip, like the commute or the manager.

Tech

Engineers use thought experiments constantly, often without calling them that. “What happens if this server receives ten times the usual traffic?” or “What if two users edit the same record at the same instant?” are imagined tests that reveal design flaws before any code is written. Asking how a system behaves under extreme or simultaneous conditions is the engineering version of Galileo’s tied stones.

Common mistakes

• Building the scenario to confirm what you already think. If you choose the setup to produce your preferred answer, you are running confirmation bias, not an experiment.
• Leaving the scenario vague. “Imagine things go badly” produces nothing. “Imagine our top client cancels on March 1” produces a plan.
• Mistaking a thought experiment for evidence about the world. It can expose contradictions and sharpen questions. It cannot tell you what customers will actually do.
• Stopping at the first step. The value usually comes from the second and third consequences, not the first.
• Dismissing the absurd result. When a scenario produces something strange, the instinct is to say “that would never happen.” Often the strangeness is the point.

Thought experiments vs real experiments

The two are partners: thought experiments decide which real experiments are worth running.

The Mentarium take

The thought experiment is the cheapest tool in this library, and the most skipped. People go straight from idea to action because imagining feels like not doing anything. We think it belongs in the Stress-test step of the Mentarium Decision Loop, in a specific form: before you commit, imagine the decision made and walk through one concrete day, one month later. Write down the first thing that goes wrong.

Two pairings make it sharper. A pre-mortem is a thought experiment with a fixed setup: the plan has failed, now explain why. First-principles thinking supplies the raw material: once you have broken a problem into basic facts, a thought experiment lets you recombine them and see what follows. Galileo did both at once. He took the basic claim (heavier falls faster), built a concrete case and followed it until it broke.

A practical habit: keep a short list of your favorite setups and reuse them. “Double it,” “remove it,” “do it for ten years,” “do it to everyone,” “explain it to a newcomer” and “imagine the best-informed critic watching.” Each is a lever that pushes an idea into a corner. Most ideas survive one or two levers; the ones that survive all of them are usually worth testing for real. The ones that break save you the cost of finding out the expensive way.