We've beaten the "why people are bad at estimating prices" question to death already — anchoring, recency bias, survivorship bias. But here's the honest part: I could recite every bias by name and my estimates still didn't get better. Knowing the label doesn't move your hand any closer to the right answer. Good estimation isn't a talent; it's a habit. Here are six of them, in the order you actually use them.

The point is one thing. Turn estimation from a "guess it all in one shot" gamble into a "refine it through several steps" procedure. With a procedure, even a wrong answer shows you where it went wrong. That's how you fix it next time. Let's build the procedure together.

1. Doubt the first number — an anchor is a starting point, not information

"This probably costs around 500 dollars." The moment someone throws that out, your estimate is already tied near that number. That's anchoring. And here's the scary part: an anchor pulls just as hard whether it's a well-grounded figure or a number somebody made up on the spot.

The habit to drive in is simple. When a number lands in your head, ask "where did this number come from?" first. Is it an actual transaction price, an asking price, an ad slogan, or just somebody's gut feeling? If you can't trace the source, knock it down to a "zero-information starting point."

One notch stronger: deliberately estimate again from the opposite direction. If your first impression was "that's expensive," force yourself to ask "what would make this surprisingly cheap?" Poke at it from both sides and the pull of a single anchor weakens. When your mind runs in one direction only, the first number that popped up keeps feeling like the answer; the moment you drag in evidence from the other side, that number starts to wobble.

2. Estimate in ranges, not points — set an upper and lower bound first

Most people pin it to a single point, like "about 300 dollars." But pin something unknown to one point and a hit is just luck, a miss tells you nothing about how far off you were. Good estimators speak in ranges: "at least 200, at most 500, most likely 350."

Two things follow from a range. One, your confidence becomes visible. Wide range means you don't know much; narrow means you're sure. Two, when you later check against the real answer, you get a clean score: "did it land inside the range?"

One practical tip. When you set your bounds, aim for a "90% confidence range" — wide enough that you can say "the chance of being outside this is no more than 1 in 10." This is where everybody gets fooled. People set the range too narrow and miss constantly. It's called overconfidence, and just practicing making your range a little wider noticeably sharpens your estimates.

3. Fermi estimation — break a big problem into small pieces

"How many cafes are in our city?" Taken whole, it feels hopeless. Chop it into small pieces and suddenly it cracks open. This is Fermi estimation, named after the physicist Enrico Fermi.

Here's the trick. Decompose a big number you have no clue about into a product or sum of small numbers you roughly do know. For cafe count, split it like this.

• Roughly what is the city's population
• What share of people go to cafes regularly
• About how many customers does one cafe handle per day
• Combine these and you get a rough number of cafes needed

Same for prices. Say you want to gauge the cost of making a single cafe latte. Estimate the bean cost, milk cost, cup and lid cost, labor, and a share of rent — then add them up. Even if each piece is off, when one runs high another tends to run low, so the errors partly cancel. That makes the result steadier than a single whole-cloth guess. But the real value of Fermi estimation isn't the answer. It's that your starting assumptions become visible. When you're wrong, you can point straight to which assumption broke.

4. Anchor on the base rate first — start from the average and adjust

A base rate is "the typical value of similar things." Before the flashy features of one case sway you, you locate where the average for the same category sits. Skipping this is the mistake called base rate neglect.

Say you're estimating a used car's price. People fixate first on that car's special story — the owner babied it, it's loaded with options. But good estimation runs backwards from that. First set the base rate — "what do used cars of the same year and trim usually sell for?" — and then adjust up or down for the individual features.

Why does this order matter? Because individual features usually move the price less than we think. Let a flashy story pull you too far from the base rate and you'll almost always miss. Make "start from the average and adjust only a little" your default stance. Once the base rate is nailed down first, no matter how convincing an individual feature looks, you calmly weigh "how many percent off the average could this really push things?"

5. Normalize units — comparison only works with the same ruler

The most common mistake in comparing prices: setting things with different units side by side. Which is cheaper, "8 dollars a bottle" or "12 dollars a bottle"? If the bottles are different sizes, the comparison is meaningless. It only holds after you convert to the same unit.

So the good habit is converting every price into a "per-unit value." Depending on the situation, like this.

• Groceries: per 100g, per liter, or per item
• Real estate: per square meter (or per pyeong)
• Subscriptions and plans: per person or per month
• Work or services: per hour

Say your hourly wage is 10 dollars. Then a 30-dollar item converts into "3 hours of me." Reframe in time units and the price feels entirely different. Unit normalization doesn't just make comparison possible; it translates numbers into the units of your own life and wakes up your intuition. That tiny unit-price label on the supermarket shelf exists for exactly this reason.

6. Record your estimate and compare with the answer — close the feedback loop

You can do all five above, but without the last one your skill won't grow. The feedback loop: record your estimate, then later check it against the real value to see where and how far you missed.

The key is not doing this "in your head only." Write the number down the moment you estimate. If you don't, your brain quietly rewrites the memory after the result comes in — "actually, I thought something close to that." That's hindsight bias. Only a written record stops the self-deception.

When you compare, go past a simple "right or wrong" and check like this.

1. How far was my point estimate from the real value
2. Did the real value fall inside the range I set
3. If I missed, which assumption was the problem — the anchor, the base rate, or the unit

Repeat "estimate, record, check the answer, analyze the cause" and you improve far faster than just staring at outcomes. It's well established that recalling something yourself before checking beats simply rereading the answer — it's called retrieval practice. Price estimation is no different. Guess first every time, then check the answer — that order grows your sense of price the fastest.

Six habits as one procedure

To sum up, the flow goes like this. A number arrives — doubt its source (1), set a range instead of a point (2), break it into small pieces if it feels hopeless (3), start from the average rather than the individual features (4), unify units before comparing (5), and finally record it and match it against the answer (6). Don't try to do all six at once. Next time you need to gauge a price, consciously use just one. Good estimation isn't something you're born with — it's a habit built from small moves like these stacking up.