Probabilistic Thinking

Two Trains, One Wedding

Kavya checked her phone one last time before boarding. 6:10 train, Ludhiana to Chandigarh, reaching by nine. Rohan's wedding function started at eleven. Plenty of buffer, she thought, tucking her dupatta over her shoulder. She had planned this two days ago, checked the train's punctuality record, even asked her uncle who traveled this route every week. "That train is never late," he'd said. She felt sure.

Two platforms away, Rohan — no relation to the groom, just a friend from college, same name as half the boys in their batch — was boarding a later train, the 7:40. He'd thought about the early one too, but decided against it. "Why rush at dawn," he told his roommate, "the 7:40 gets in by 10:15, still an hour to freshen up." He'd also checked the punctuality record. He also felt sure.

Both of them, on that platform that morning, would have told you the exact same thing if you'd asked: I've thought this through, I'll be fine.

Kavya's train left on time. She settled into her window seat, already picturing the shagun she'd give, the aunties she'd greet. Somewhere past Rajpura, the train slowed. Then stopped. Signal failure, the coach attendant said, shrugging like it was weather. Forty minutes became ninety. Kavya sat there watching her buffer disappear minute by minute, her phone battery draining faster than her patience, texting the family WhatsApp group apologies she hadn't earned yet.

Rohan's train, meanwhile, ran exactly on time. He walked into the wedding hall with twenty minutes to spare, hair combed, gift wrapped, completely unaware that anything dramatic had happened two hours behind him on the tracks.

Kavya arrived just as the couple was garlanding each other, slipping into the back row, out of breath, cheeks hot with embarrassment. Later, over lunch, her cousin laughed and said, "You should've taken the later train like Rohan did, na? Smarter choice." Kavya nodded along, feeling foolish, replaying her decision like she'd made some obvious error. Rohan, sitting across the table, felt a small private glow of having "read it right."

But that night, lying awake, Kavya kept returning to something that didn't quite fit. She pulled up both punctuality records again, out of habit more than anything. Both trains had near-identical histories. Both had similar odds of running late. She had checked what there was to check. So had Rohan. The only difference between her morning and his was a signal box near Rajpura deciding to fail on one particular Tuesday — something neither of them could have read in any timetable.

She wasn't sure anymore whether she'd actually done anything wrong. She just knew how it looked from the outside.

• Explain why treating a decision as a set of possible outcomes with different likelihoods is more honest than expecting one guaranteed result.
• Distinguish between judging a decision by the quality of reasoning at the time versus judging it only by how it eventually turned out.
• Recognize that weighing possibilities and likelihoods before deciding is a general life habit that applies beyond money and trading.

You already know what it feels like to be "sure" and then get blindsided — Kavya was sure her train would make it. Rohan was sure too, about a different plan. Both of them were reasoning carefully. Only one of them got the outcome they expected. That gap between feeling sure and actually knowing is where most people get stuck, either freezing until they feel certain (which almost never happens), or picking one hoped-for outcome and hoping hard.

Here's the more honest way to think: almost nothing in life comes with a guarantee. What feels like "sure" is really just "very likely" wearing a more confident costume. Once you notice that, the useful question changes. Instead of asking "what do I hope happens?" you start asking "what are the possible outcomes here, and how likely does each one feel?" That's probabilistic thinking — treating a decision as a spread of possible results, each with its own likelihood, rather than one guaranteed ending. You may have met a version of this already, back when you learned to calculate expected value for trades. That formula was just training wheels. The mindset underneath it — weigh the possibilities, don't chase one outcome — works for any decision: which job offer to take, whether to leave early for an interview, how much to save this month.

Judge the thinking, not the outcome — that's the real test of a good decision.

This shift changes how you judge decisions too, not just how you make them. If quality is measured by outcome alone, then Kavya "got it wrong" and Rohan "got it right" — but they reasoned the same way that morning. The only difference was a signal failure near Rajpura, something neither of them could have known. So the fairer standard is process-based judgment: ask whether the possibilities were honestly weighed at the time, not which single outcome later showed up. A well-reasoned decision can still turn out badly — that's bad luck, not bad thinking. A careless decision can still turn out well — that's good luck, not good thinking.

Judge the thinking, not the outcome — that's the real test of a good decision.

Put together, these two ideas protect you from two opposite traps: freezing because you can't be certain, and beating yourself up (or congratulating yourself) for things that were never really in your control. You act on likelihoods. You judge yourself on reasoning.

A week after the wedding, Kavya is booking a flight for a work trip to Mumbai. There's an early morning flight and an afternoon one. Her first instinct is the old one: "Which one is guaranteed to get me there on time?" Then she catches herself — nothing is guaranteed, she just relearned that the hard way on a train platform.

So she asks the better question instead: what could actually happen with each flight, and how likely does each possibility feel? The early flight has a slightly higher chance of fog delays this time of year, but she has more buffer before her meeting if she takes it. The afternoon flight almost never gets fog-delayed, but if it's late by even ninety minutes, she'll walk into her meeting straight from the airport with no room to breathe. She weighs it out, checks the airline's on-time record for both slots, and books the early flight — not because it's "guaranteed" to work, but because, given everything she actually knows, it's the option she can defend with reasoning.

Before she closes the app, she makes herself a quiet promise: if the flight still gets delayed and she's late anyway, that won't mean she chose badly. It'll mean she got an unlucky outcome — a different thing entirely from a bad decision.

Point: Applying the DecisionLens question to a real, everyday choice and pre-deciding to judge the choice by the reasoning, not just whatever happens next.

Back in Level 6, you learned to calculate expected value — multiplying possible outcomes by their odds to get one honest number for a trade. That formula still matters when you're trading. But notice what it was really teaching underneath the math: don't fixate on one hoped-for result, spread your attention across what could realistically happen. Strip away the numbers and the trading context, and that's exactly what probabilistic thinking is — the same habit, worn without the formula, usable anywhere. This isn't guessing. Guessing means you have nothing to go on. Probabilistic thinking means you're using whatever you actually know — a punctuality record, a weather forecast, past experience — to weigh outcomes honestly. It's more disciplined than a shrug and more honest than false confidence.

• Deciding a choice was 'wrong' just because it turned out badly (or 'right' because it turned out well). — The outcome is loud and immediate — you feel it right away. The quality of your reasoning at the time is quiet and easy to skip checking, so people default to whatever feedback is easiest to see: the result. Fix: Before judging a past decision, ask what you actually knew and weighed at the time — not what you know now with hindsight. If the reasoning was sound, a bad result is bad luck, not bad thinking.
• Assuming that thinking in probabilities means you're 'just guessing' because you can't be 100% certain. — Without certainty, it feels like there's no solid ground — so uncertainty gets confused with ignorance, as if not knowing everything means knowing nothing. Fix: Remind yourself that probabilistic thinking uses everything you do know — past patterns, known risks, your own experience — to weigh outcomes. That's informed judgment, not a coin flip.
• Treating 'I'm sure' and 'this is very likely' as the same thing. — Strong confidence feels identical to certainty from the inside, so the mind quietly upgrades 'likely' to 'sure' without noticing the swap. Fix: Catch yourself saying 'sure' before a decision, and swap it for 'likely' out loud. Hearing the word change is often enough to remind you that other outcomes are still possible.

• "Sure" almost always means "very likely," not "100% certain" — real certainty is rare.
• Before deciding, ask: what could happen here, and how likely does each outcome feel?
• Judge a decision by the reasoning behind it at the time, not just by how it turned out.
• A good decision can still have a bad outcome (unlucky), and a careless decision can still have a good outcome (lucky).
• This mindset works for any uncertain choice in life, not only trades or money.

Q1. When someone says they feel "sure" about how a decision will turn out, what does that feeling most often actually represent?

• A guarantee that the outcome will happen
• A strong likelihood, not 100% certainty
• A calculation that has been mathematically proven
• A guess with no real information behind it Answer: A strong likelihood, not 100% certainty — Real certainty is rare. What feels like "sure" is almost always a strong likelihood dressed up as certainty — that's the whole reason it's worth pausing to think in probabilities instead.

Q2. Kavya's train was delayed by a signal failure while Rohan's later train ran on time. Based on what both of them knew that morning, was Rohan's choice actually the "smarter" one? Answer: False — Both had checked similar punctuality records and reasoned in a similar way. The only difference was an unpredictable signal failure — luck, not better thinking, separated their outcomes.

Q3. Rahul makes a well-reasoned decision to invest in a company after checking its financials carefully, but the stock drops due to an unexpected event no one could have predicted. According to process-based judgment, how should Rahul evaluate his decision?

• He decided badly, since the outcome was bad
• He decided well, because his reasoning was sound at the time — the bad result was unlucky, not a sign of poor thinking
• He should wait for future results to know if his reasoning was good
• He can't judge the decision at all since the outcome doesn't match the reasoning Answer: He decided well, because his reasoning was sound at the time — the bad result was unlucky, not a sign of poor thinking — A single outcome is just one sample. If the possibilities and likelihoods were honestly weighed beforehand, a bad result afterward is bad luck — not proof of bad thinking.

Q4. An investor says: "I've done the probability analysis, there's a 90% chance this trade wins, so I'm putting in my entire savings." Is treating 90% as safe to bet everything on sound reasoning? Reveal: Weak: yes, 90% is very likely, basically safe. Strong: probabilistic thinking weighs likelihood and the size of the downside together — a 90% chance of a small gain next to a 10% chance of losing everything is a very different bet than 90/10 on a moderate loss.