ICT or classical technical analysis: what actually changes
Triangles, head and shoulders and RSI on one side; order blocks, liquidity and killzones on the other. The difference is not fashion, and it is not tribal: it is a difference in the question you ask the chart. And it has very concrete consequences for how you place a stop.
Two ways of answering the same question
All chart analysis tries to answer one question: where is price most likely to go next, and at what point will I know I was wrong? Both approaches aim at that target. They simply come at it from opposite ends.
Classical technical analysis starts from shape. Over a century of charts it catalogued configurations that have statistically preceded certain moves: a tightening triangle, a double bottom, a moving-average cross. The reasoning is inductive: this has often been followed by that, so watch for this.
ICT reading starts from mechanism. It assumes that a participant who has to fill significant size needs a counterparty, and that the counterparty sits where orders pile up — which is to say where other participants put their stops. The reasoning is causal: price has a reason to go and take that zone, so let us see whether the zone is there.
Read next: Market structure · Liquidity (buy-side / sell-side)
What classical analysis does well, and gets unfairly denied
It has become fashionable in ICT circles to treat classical technical analysis as superstition. That is unfair, and it is bad teaching. The notion of trend, spotting support and resistance, the idea that a level touched several times matters more than one touched once: all of that is solid, and all of it survives inside ICT reading, sometimes under a different name.
Its real strength is being immediately legible. A beginner can learn to draw a trendline in an afternoon. That is a genuine entry point, and I have never met anyone who learned to read a chart without going through it.
Its limit is not that it is wrong, it is that it is silent on the “why”. When two patterns contradict each other — and they will — the catalogue gives you no criterion for deciding. You end up picking whichever pattern confirms what you already wanted to do. That is where most accounts get emptied.
What ICT adds: a reason, and therefore an invalidation
The concrete gain from ICT is not being right more often. It is knowing, before you enter, what would make your idea wrong — and exactly where that point sits on the chart.
An example. You see price break a high and you want to buy the continuation. In classical reading your stop goes “below support”, an approximate zone you pick by eye. In ICT reading you first ask why price went up to that level at all: if it just swept a cluster of stops sitting above the high, the move may have had no other purpose, and there is no continuation to buy. Your invalidation becomes a factual question rather than an intuition.
The same holds for the entry. A zone left behind by an impulsive move — an order block, an unfilled imbalance — gives you an entry with a tight stop and an identifiable target, because you know what the zone represents. The distance between your entry and your invalidation gets small, and that distance is what sets your position size, and therefore your return at constant risk.
Put differently: the value of ICT is less in prediction than in the geometry of the trade. You do not guess better; you risk less for the same idea.
Read next: Order Block · Imbalance · Stop Hunt / Liquidity Grab
The real friction point: indicators
This is where the two genuinely part ways. Most classical indicators are mathematical transforms of past price: a moving average is an average of what just happened, an RSI is a normalised measure of the same thing. They contain no information price does not already contain — they smooth it, with a lag.
So ICT reading works on naked price, and that often grates at first: the chart looks empty, there is no green arrow telling you what to do. It is uncomfortable, and that is the point. A moving-average cross hands you a signal without handing you a reason; going without one forces you to state the reason.
That does not make every indicator useless. A tool that draws sessions, time windows or the previous day’s levels is useful, because it shows you facts rather than a computed opinion. The distinction is not “indicator or no indicator”: it is “does this show me a fact, or an opinion derived from price?”.
Read next: Killzone
What ICT does not do better
Let us be clear, because this part is almost always left out by people selling ICT courses — myself included if I am not careful. ICT does not hand you a guaranteed higher win rate. It does not remove losing streaks. It does not work better on an illiquid asset, where there is simply no participant large enough to leave the traces you are trying to read.
Above all, it is considerably easier to misapply. The vocabulary is rich and the concepts are many: on any chart, if you look hard enough, you will always find an order block, an imbalance and a liquidity grab that justify the trade you already felt like taking. A beginner in classical analysis is wrong visibly; a beginner in ICT is wrong while sounding knowledgeable, which is more dangerous.
The safeguard is the same in both cases and it is not seductive: a trade journal, re-read every week. It is not the method that makes you profitable, it is seeing in writing that you keep taking the same bad trade on Friday afternoons.
Read next: Inducement
Do you have to choose?
In practice, no — and the traders I see improve fastest do not choose. They keep trend reading and the levels that matter from classical analysis, and borrow the “why” and the stop placement from ICT. The two do not contradict each other: a classical support and a liquidity zone often point at the same place, for different reasons.
If you do have to pick a starting point, though, my recommendation is unambiguous: learn market structure first, and add the ICT vocabulary afterwards. Structure read cleanly is enough to rule out most bad trades. Every concept that follows rests on it, and applying them without it is decorating an argument that is not there.
Read next: Break of Structure (BOS) · Change of Character (CHoCH)