Confirmation Bias
Confirmation bias is the human tendency to seek, favour and remember evidence that supports a belief you already hold, which in backtesting leads researchers to design, interpret and report tests in ways that confirm a strategy they are already attached to.
Quick answer: Confirmation bias is the human tendency to seek, favour and remember evidence that supports a belief you already hold, which in backtesting leads researchers to design, interpret and report tests in ways that confirm a strategy they are already attached to.
In simple words
Confirmation bias is looking for reasons you are right and skimming past reasons you are wrong. In backtesting it makes you run the test that flatters your idea, notice the good results, and explain away the bad ones. It is not a data problem but a human one, and it quietly steers every other bias in a favourable direction.
Purpose
This concept exists because backtesting is done by humans who become attached to their ideas, and that attachment shapes which tests are run and how results are read, making confirmation bias the psychological engine behind many of the technical biases.
Professional explanation
What confirmation bias is
Confirmation bias is a well-documented cognitive tendency to favour information that supports what we already believe and to discount information that contradicts it. In research it manifests as asking questions likely to yield a supportive answer, weighting confirming evidence more heavily than disconfirming evidence, and remembering hits while forgetting misses. It is not deliberate dishonesty; it operates below awareness, which is exactly what makes it dangerous in a discipline that depends on ruthless self-scrutiny.
How it corrupts a backtest
A researcher attached to an idea will, often unconsciously, choose the instrument, period and parameters that make it look good, stop searching once a favourable result appears, and interpret ambiguous outcomes charitably. Losing trades get explained away as anomalies while winning trades are taken as proof. The test is nominally objective, but the choices surrounding it are steered toward the desired conclusion, so the backtest measures the researcher's hopes as much as the strategy's merit.
Why it is the engine behind other biases
Confirmation bias supplies the motive that turns technical pitfalls into actual errors. It is why you keep tweaking until the curve looks good, which is curve fitting; why you test only the market where the idea worked, which is selection bias; why you stop the parameter search at the flattering peak, which is data snooping. Each of those biases requires a human decision to stop looking or to look in a particular place, and confirmation bias is the tendency that makes those decisions favour the prior belief.
The asymmetry of scrutiny
A tell-tale sign is asymmetric scrutiny: results that support the idea are accepted quickly, while results that contradict it are examined for bugs until they go away. This ratchet systematically pushes conclusions in the favourable direction, because errors that help are kept and errors that hurt are hunted down. Genuine science demands the opposite discipline, scrutinising favourable results at least as hard as unfavourable ones, which is psychologically uncomfortable and therefore rare without deliberate structure.
Guarding against it with process
Because willpower alone does not defeat a subconscious bias, the defences are structural. State the hypothesis and the success criteria in advance, so you cannot move the goalposts after seeing results. Pre-register the test design and the parameter ranges. Reserve out-of-sample data and commit to using it once, whatever it shows. Actively try to falsify the idea rather than confirm it, seeking the conditions under which it should fail. Where possible, have a colleague review the design blind to your hopes, and keep an honest log of every variant so you cannot quietly forget the failures.
The role of adversarial thinking
The most effective antidote is to adopt the stance of a sceptic trying to disprove your own strategy. Ask what would have to be true for the edge to be an illusion, then test for exactly that: check the look-ahead timing, widen the sample, degrade the parameters, add realistic costs. A strategy that survives a sincere attempt to kill it is far more trustworthy than one that merely survived a search for reasons to believe it. Confirmation bias is beaten not by trusting yourself less in the abstract but by building tests designed to prove yourself wrong.
Practical example
Illustrative example (Indian market)
You are convinced a particular Nifty breakout pattern works, so you test it first on the two years you remember it working well, on capital of Rs 5,00,000, and it looks strong. A weaker result on other years you attribute to unusual conditions, and a losing stretch you dismiss as a data glitch you never quite investigate. Because you stopped looking once the idea was confirmed and scrutinised only the disappointing results, your conclusion reflects your prior belief. A confirmation-resistant process would have fixed the test period and success criteria in advance, examined the good years as sceptically as the bad, and committed to a single out-of-sample verdict, which typically deflates the original enthusiasm.
Retail trading communities often amplify confirmation bias: a popular Bank Nifty setup is shared with screenshots of its winning trades, and members test it expecting success, notice the wins and overlook the losses. The collective belief that it works makes each individual more likely to design a backtest that confirms it and to quietly drop the runs that did not.
Limitations
- It is subconscious, so awareness alone does not remove it and self-report cannot detect it
- Structural defences like pre-registration are harder to enforce in informal retail research
- An honest process can still be undermined if success criteria were vague to begin with
- It interacts with every technical bias, so it cannot be isolated and fixed on its own
- Even adversarial testing can be gamed if the researcher secretly wants the idea to survive
Why it matters in practice
- It is the psychological driver that turns technical pitfalls into real backtest errors
- It biases which tests are run and how results are read, upstream of any calculation
Common mistakes
- Running first the test most likely to confirm the idea, then stopping once it does
- Scrutinising losing results for bugs while accepting winning results uncritically
- Explaining away contradictory periods as anomalies without investigating them
- Moving the success criteria after seeing the results to keep the conclusion
- Remembering the winning trades and forgetting the losing ones when judging a setup
- Adopting a community-favoured setup and testing it expecting, and finding, success
Professional usage
Rigorous researchers assume they are biased toward their own ideas and build process to counteract it. They pre-specify the hypothesis, success criteria and parameter ranges, reserve out-of-sample data for a single honest verdict, and deliberately try to falsify the strategy rather than confirm it. Many invite blind review from a colleague and log every variant so failures cannot be forgotten. The governing principle is that a strategy is trustworthy only after a sincere attempt to disprove it has failed, not after a search for supporting evidence has succeeded.
Key takeaways
- Confirmation bias is favouring evidence that supports a strategy you already believe in
- In backtesting it steers which tests you run and how you read the results
- It is the psychological engine behind curve fitting, selection bias and data snooping
- Its signature is asymmetric scrutiny of favourable versus unfavourable results
- Beat it with pre-specified criteria, out-of-sample discipline and adversarial testing
Frequently asked questions
What is confirmation bias in backtesting?
How is confirmation bias different from the technical biases?
Why is confirmation bias so dangerous in research?
How does confirmation bias drive other biases?
What is asymmetric scrutiny?
How do I guard against confirmation bias?
What is adversarial testing?
Can I remove confirmation bias by being aware of it?
How does confirmation bias affect how I read results?
Does trading in a community increase confirmation bias?
How does pre-registration help?
Is confirmation bias the same as overfitting?
Why should I try to disprove my own strategy?
How does confirmation bias relate to why backtests fail?
Voice search & related questions
Natural-language questions people ask about Confirmation Bias.
What is confirmation bias in simple terms?
Why does confirmation bias hurt my backtesting?
How is confirmation bias linked to overfitting?
How do I fight confirmation bias?
Can I just be aware of confirmation bias to avoid it?
Does following trading groups make confirmation bias worse?
Sources & references
Last reviewed 11 July 2026. Educational content only — not investment advice. Markets and rules change; verify current conventions with SEBI, NSE/BSE and your broker.