What Losing Teaches You (That Winning Never Will)
I've lost a lot of Commander games. More than I've won, probably. And I've come to believe that's exactly why I'm still playing this game after all these years, and why I've gotten better at it.
Winning doesn't teach you much — it's just the game working as intended. You built a deck, you executed a plan, you won. Great. But you don't learn a lot from that outcome, because "it worked" doesn't tell you which part worked, or whether it'll work again against a different table.
Losing is different. A loss gives you something specific to look at:
- You can usually pinpoint the exact moment or decision that cost you the game
- That specificity means you can fix the actual problem instead of guessing
- It keeps you from overcorrecting — you're not gutting the whole deck, you're addressing one real weak point
- Over enough losses, that adds up to genuine improvement instead of just spinning your wheels
It's a lot like chess that way. I'm not good at chess either. Doesn't matter what your rating is — the games you lose are the ones that actually teach you something, if you're willing to look at them honestly instead of just chalking it up to bad luck.
This mindset is part of why I've stuck with Commander long enough to build up any kind of experience worth sharing. I didn't quit after a few rough nights. I took the losses, figured out what they were telling me, and kept building.
Three decks, three lessons
None of this is a masterclass — I'm not a pro, and these aren't super high-powered decks. But I think they're a decent illustration of three different stages of deck-building philosophy, because I built them at different points in my own learning curve.
Beginner tier — Elas il-Kor, Sadistic Pilgrim
This one keeps it simple: it wins through combat and basic gameplay, no elaborate engine to learn or maintain. The one twist is lifegain — it's not the win condition itself, it's the buffer that buys you enough time to close the game out through combat. That's a good beginner-level lesson in its own right: you don't need a combo or a complicated plan, you need a way to survive long enough for your straightforward plan to work.
Intermediate tier — Kudo, King Among Bears
This is the one where I started leaning into the mechanics on purpose instead of building around raw stats — a Selesnya fight-tribal build. It's closer to a glass cannon than I'd like to admit, but the idea is that it's got enough flexibility built in that it can be tuned up or down depending on the playgroup you're sitting down with. That adaptability is the actual lesson here: a deck that can't flex to the table it's playing against is going to keep losing the same way, over and over.
Advanced tier — Sharuum, the Hegemon
This one's personal. Early in my return to Magic, my friends and I missed the entire Eldrazi era while we were away from the game — and we came back just in time to get repeatedly pub-stomped at our LGS by someone running an Eldrazi deck. That's a story about revenge, and revenge is a dish best served cold. (More on that another time.)
Sharuum is my answer to that. It's not a commission build — it's just for me, and it's built for nostalgia as much as function. Rather than swinging for six-plus mana on a commander every game, it leans on combo pieces to win more quietly. It's less "beat you over the head" and more "you didn't see it coming." That's a different kind of lesson than the other two decks: sometimes the fix for getting run over isn't building bigger, it's building smarter.
The takeaway
You'll learn more from a loss than a win, every time — if you're willing to actually look at why you lost instead of writing it off. Don't overcorrect. Don't gut the whole deck over one bad night. Find the specific thing that went wrong, fix that, and keep playing.
Morning Show: https://www.youtube.com/live/1WKk9Lnzeo4?si=qQDwHweUCXOCLfdi
YouTube Video: https://youtu.be/vg0ggFHMbM8
Thanks for reading — and if you haven't seen the episode this is based on, the video's linked above. New subscribers, welcome. If any of this was useful, let me know in the comments. If it wasn't, tell me that too — I'd rather hear it.

Comments
Post a Comment