Learning from Mistakes

The Fabric That Kept Getting Cheaper

Kiran had waited for this moment since Diwali.

Every year, the fabric wholesaler near Lohar Chawl dropped prices in the off-season, and every year Kiran watched the pattern before buying — never too early, never too late. This time felt right. The supplier, a man Kiran had bought from for six years, leaned in and said, "Buy now, prices won't fall further this season." The old ledger backed him up too — the last three years all showed the same dip-then-rise pattern around this week.

So Kiran did the math, counted out the savings, and bought forty metres of cotton and linen blend for the shop, enough to last through the wedding season orders. It felt like the smart move. The disciplined move.

Nine days later, a customer mentioned, almost in passing, that the fabric market two lanes down was selling the same blend for twelve rupees less per metre.

Kiran sat very still behind the counter for a moment, the ledger still open to that week's entry.

Twelve rupees. Times forty metres. Kiran did that math too, faster than the first time.

"I should've waited," Kiran said out loud, to no one, since the shop was empty on a slow Tuesday afternoon. "I always do this. I rush in and then regret it."

Meera walked in just then, dropping by to return a stitched kurta she'd picked up the week before. She noticed Kiran staring at the ledger like it had insulted her.

"You look like the sewing machine broke," Meera said.

"Worse. I bought fabric too early. Prices dropped again after I bought."

Meera raised an eyebrow. "How early is too early? Didn't you check with your supplier, and the old records, like you always do?"

"I did all of that. Doesn't matter now, does it? I still lost money I didn't need to lose."

"So what are you going to do next season?"

Kiran didn't even have to think about it. "Not buy in bulk before the season starts. Just wait and see what happens, buy whatever's cheapest whenever I need it."

Meera picked up a loose thread from the counter, rolling it between her fingers, thinking. "Can I ask you something odd?"

Kiran nodded, still frowning at the ledger.

"That day you bought — the discount, the supplier's tip, the three years of price history — if I'd asked you then, right before you paid, whether you were making a good decision... what would you have said?"

Kiran opened her mouth to answer quickly, then stopped.

She genuinely didn't know what she would have said today, sitting here with the twelve-rupee number burning a small hole in her mind.

• Explain why a decision's quality should be judged by whether it was the right call at the time, not by whether it made or lost money.
• Use two simple questions to separate a genuine process error from an unlucky outcome (variance) after a financial decision goes wrong.
• Apply the 'would I make this call again knowing only what I knew then' test to decide what, if anything, actually needs to change next time.

Here's the trap Kiran fell into, and it catches almost everyone: the moment a decision loses money, the mind treats the loss as proof the decision was wrong. But a decision and its outcome are two different things, made at two different times, with two different amounts of information. You make a decision today with whatever you know today. The outcome shows up later, shaped by things you couldn't have known — a competitor dumping stock, a market shift, plain luck. Judging today's decision by tomorrow's outcome is like grading an exam answer using facts the student didn't have when they wrote it.

This is the Process vs Outcome split: a decision's quality depends on whether it was the right call given what was knowable at the time — not on whether it made or lost money. A careful, well-reasoned decision can still lose because of pure variance (the random part of any outcome that no amount of good thinking can control). And a careless, poorly-reasoned decision can still win by dumb luck. Neither result tells you, by itself, whether the thinking behind it was sound.

If the outcome doesn't tell you whether you made a mistake, what does?

So if the outcome doesn't tell you whether you made a mistake, what does? This is where the Honest Debrief comes in — a short review with exactly one job: change your next decision, not judge your last one. It runs on two questions. First: was the process sound — did you use the information reasonably available at the time? Second: was the outcome just variance — did something unpredictable, not a flaw in your thinking, cause the result? A fast way to check the first question is the "would I make this call again" test: knowing only what you knew back then, not what you know now, would you make the same decision? If yes, your process was probably fine and the bad result was ordinary bad luck — worth noting, not worth panicking over. If no — if there was information you ignored or a step you skipped — that's a real process error, and that's the one thing worth fixing.

Notice what this debrief is not. It's not about deciding who's to blame, and it's not about deciding whether you're "good" or "bad" with money. Money lost through a decision is paid-for information — but only if you actually run the debrief and extract the lesson, instead of either drowning in shame or shrugging it off as fate.

A few days later, Kiran sits down at the counter again, ledger open, and this time doesn't just react — she actually runs the debrief.

First question: was the process sound? She goes back over what she knew before buying. The off-season discount was real. Her supplier of six years had told her prices wouldn't fall further. The last three years of her own ledger showed the same dip-then-rise pattern around that exact week. Given all of that, buying was a reasonable call — not a guess, not a rush.

Second question: was the outcome just variance? The extra price drop, she learns, happened because a competitor two lanes over had dumped surplus stock into the market right after her purchase — something no supplier tip or three years of history could have warned her about. That wasn't a flaw in her thinking. That was bad luck landing on a good decision.

She picks up her pen and writes one line in the ledger: "Process: sound. Outcome: bad luck. Keep the same buying approach next season."

She doesn't swear off bulk buying, the way her first instinct told her to. She also doesn't pretend the twelve rupees per metre didn't sting. She just walks away with something more useful than either regret or denial: a specific, honest answer about what to repeat and what to leave alone.

Point: Running the honest debrief turns a loss into a specific, forward-looking decision (keep the process) rather than a vague verdict of shame or excuse — showing the Honest Debrief and the 'would I make this call again' test in concrete action.

• Assuming that because a decision lost money, the decision itself must have been wrong. — Losses feel bad immediately, and the outcome is the most visible signal available, so it's natural to judge the decision by the result instead of by the reasoning behind it. Fix: Separate the two questions on purpose: ask what you knew when you decided, not what you know now, and judge the decision only against that.
• Treating a review of a mistake as a search for who or what to blame. — Blame feels like closure, and many people's early experience of being reviewed — at school, at home, at work — was really punishment dressed up as feedback. Fix: Remind yourself the debrief has one job: change the next decision. Labeling something a process error is only useful if it changes future behavior, not to assign fault.
• Concluding that if a bad outcome was just bad luck, there's nothing to learn and no reason to reflect. — Calling it luck feels protective — it avoids the discomfort of examining your own choices, so it's tempting to stop there. Fix: Run the debrief anyway. Confirming the process was sound is itself a useful conclusion — it tells you to keep doing what you're doing, which is worth writing down.

• A bad outcome doesn't automatically mean a bad decision — review the decision separately from how it turned out.
• Ask two questions after any financial setback: was the process sound, and was the outcome just variance (ordinary bad luck)?
• The 'would I make this call again, knowing only what I knew then' test is a quick way to judge process without being biased by hindsight.
• A review's only job is to change your next decision — not to hand out blame or an excuse for the last one.
• A loss becomes paid-for information only if you actually run the debrief and extract the lesson from it.

Q1. According to the Honest Debrief idea, a financial decision's quality should mainly be judged by:

• Whether it made or lost money
• Whether it was the right call given what was knowable at the time
• Whether a friend or family member approved of it
• Whether the same decision worked last time Answer: Whether it was the right call given what was knowable at the time — A decision and its outcome are two different things. Judging the decision means looking at the reasoning and information you had when you made it, not the result that showed up later.

Q2. What is 'variance' in the context of reviewing a financial decision?

• A mistake caused by not checking enough information before deciding
• The random, unpredictable part of an outcome that even a sound decision can't control
• A guaranteed sign that the process used was flawed
• A method for calculating exact investment returns Answer: The random, unpredictable part of an outcome that even a sound decision can't control — Variance is the ordinary, unpredictable element in any outcome. A well-reasoned decision can still run into bad variance and lose money without the process itself being flawed.

Q3. A shopkeeper checks reliable price patterns, gets a trusted supplier's tip, and buys stock at what seems like the best time. A few days later, prices fall further because a competitor unexpectedly dumps surplus stock into the market. Using the 'would I make this call again' test, what's the most reasonable conclusion?

• The process was flawed, since a careful buyer should have predicted every competitor's move
• The process was likely sound, and the extra price drop was probably ordinary bad luck
• There's nothing to review here since the outcome was just luck either way
• The shopkeeper should stop buying stock in bulk altogether from now on Answer: The process was likely sound, and the extra price drop was probably ordinary bad luck — Knowing only what was known at the time, the purchase was reasonable. An unpredictable event (competitor's surplus stock) caused the extra drop — that points to variance, not a process error, so the approach is worth keeping.

Q4. A trade lost money. Looking back with hindsight, the investor says: "It's so obvious now I should have sold earlier, I can't believe I missed that." Is "obvious now" a fair way to judge the original decision? Reveal: Weak: yes, if it's obvious in hindsight, the original call was clearly wrong. Strong: this is hindsight bias — information obvious after the outcome wasn't necessarily available before it; the fair question is what a reasonable person would conclude with only what was known at the time.