Celebrating your wins sounds like it should be the easy half of gratitude practice โ you did the thing, you enjoyed the thing, job done. In my experience it's the harder half by a distance. I can tell you the exact layout of three meetings that went badly in the last six months. I had to scroll back through my own journal this morning to remember one that went well, and even then I'd described it in eleven words and moved straight on.
That asymmetry isn't a personality flaw, and it isn't modesty either, whatever it feels like from the inside. It's a well-documented feature of how memory works, and the fix isn't "try to feel proud of yourself" โ that instruction has never once worked on me. The fix is closer to a procedure, with a specific order of steps, and most of it comes from research that has nothing to do with gratitude journalling at all.
Why is it so hard to celebrate your own wins?
Part of the answer is the same negativity bias behind most of what I've written about journalling before: bad events get priority storage, good ones don't. But there's a sharper version of it specific to success and failure. Before people are trained to review their own performance properly, their mental picture of what went wrong is already far more detailed than their mental picture of what went right. Failure gets replayed in high definition. Success gets a thumbnail.
I recognise this from running workshops for a living. A session that flops gets dissected in the car home โ what I said, the exact moment the room went quiet, what I should have done instead. A session that lands well gets "that went well" and then I'm on to tomorrow's agenda. I used to think the dissecting was professionalism and the shrugging-off was just being hard on yourself in a productive direction. It isn't. It's an accounting error, and it means you learn less than half of what actually happened to you.
What happens when you actually review something that went right?
The clearest demonstration of this I've found comes from a study that has nothing to do with journalling. Ellis and Davidi ran Israeli soldiers through repeated navigation exercises and varied how they debriefed afterwards. Some reviewed only their failed attempts, in the usual after-action-review style. Others reviewed both their successful runs and their failed ones. The group that reviewed successes alongside failures improved more โ and did so specifically by building a richer, more accurate picture of what they'd done right, not just what they'd done wrong.
That's a study about map-reading under time pressure, not about a gratitude practice, and I'd be overselling it if I implied otherwise. But the mechanism generalises further than the setting: reviewing a success is not something that happens automatically just because the success happened. It's a separate act, and if you skip it, you're operating on half the available evidence about your own competence.
Why does it matter whose win it actually was?
Here's the part I found most useful, and also the part I find hardest to do. Albert Bandura's work on self-efficacy โ your belief that you're capable of doing the things you're attempting โ puts mastery experience, the direct memory of having succeeded at something, above every other source of that belief. Above encouragement from other people, above watching someone else do it, above being told you're capable. Your own remembered successes are the strongest building block there is.
But the crucial detail, easy to skim past, is that this only works if you attribute the success to yourself. "It went well" builds nothing, because "it" isn't you. "I prepared for the question I was dreading and it paid off" is a completely different sentence, doing completely different work. I found this genuinely uncomfortable to write for the first few months โ crediting myself on a page nobody else would read still felt like showing off to an empty room. The discomfort is worth pushing through anyway, because the alternative is quietly starving the one input that self-efficacy actually runs on.
A real one from my own log: "Client renewed the contract." True, and useless. The version that actually did something was "Client renewed โ because I flagged the delivery risk three weeks early instead of hoping it would resolve itself, and that's the second time being upfront early has saved a relationship rather than damaged it." Same event. One sentence teaches you something you can use again; the other is a fact you'll have forgotten by Friday.
Does it help to tell someone?
There's a second finding that changed how I do this, and it's the one I'd have guessed wrong beforehand. Gable and colleagues found that sharing a positive event with someone else โ and having them respond with genuine enthusiasm rather than a polite nod โ produces benefits beyond the event itself, on top of whatever good feeling the event already gave you. Researchers call this capitalisation: the good thing gets bigger, not smaller, when it's shared well.
I'd assumed telling people about a win was mostly for their benefit, a courtesy or a boast depending on your mood. It turns out it's doing something for you too, and it's also the moment you notice who actually shows up for the good stuff, not just the bad. Reviewing a win properly surfaces the person who helped โ the colleague who read a draft at 11pm, the friend who talked you out of pulling the pitch โ and that's usually worth a message on its own, separate from thanking them in the moment.
So what does actually reviewing a win look like?
What I do now, and what ended up shaping the Wins practice inside Kansha, splits into two moments rather than one. Log it in a sentence the second it happens โ ten seconds, no reflection required, just don't let it evaporate. Then, later, when you've got five calm minutes, go back and tell it properly: what happened, what you specifically did well, one thing you'd do differently next time, who helped, and โ deliberately last โ what you enjoyed most about it.
The order isn't arbitrary. Ending on a criticism, even a mild forward-looking one, is how a good memory quietly turns into an unpleasant one to revisit, which is exactly the kind of thing you stop doing after a few tries. Ending on what you enjoyed is the version you'll actually come back to. This is a lot of why I built Kansha in the first place โ I kept a detailed record of what went wrong without ever noticing I'd stopped recording what went right.
What this doesn't do
I want to be straight about the limits, because a page that only lists upsides is just advertising. None of the research above tested a wins journal specifically โ Ellis and Davidi studied soldiers, Bandura's account is theoretical rather than an experiment, and the capitalisation research used real-time conversations, not written entries read back later. Assembling them into a five-step routine is a reasonable inference from well-supported pieces, not a tested intervention in its own right. This is a coaching tool, not a clinical one, and it won't do much for someone who's burnt out or genuinely can't locate a single thing that went right this week โ that's a different problem, and it deserves a different kind of help.
For everyone else, it's a fairly small habit with an oversized blind spot behind it. You already have a highly detailed record of everything that's gone wrong recently โ your brain built it without being asked. The wins don't get that treatment unless you build it yourself, deliberately, in an order that makes you want to do it again.