The DNF Dilemma: Giving Yourself Permission to Abandon a Book

There's a particular kind of guilt that comes with closing a book you've decided not to finish. It sits on the nightstand for a few days, then migrates to the bottom of a stack, and eventually finds its way back to the shelf—unread, unfinished, quietly accusing you every time you pass it. Many readers treat abandoning a book as a personal failing, as though endurance were the same thing as appreciation. But the longer I've spent in reading communities, the more convinced I am that knowing when to put a book down is one of the most valuable skills a reader can develop.

Think about how we talk about books we didn't finish. We say we "couldn't get into it," as if the fault lies with us. We apologize for it at book club. We promise ourselves we'll try again someday. Rarely do we simply say: this book and I were not meant for each other right now, and that's fine. The language we use shapes how we feel, and the language around unfinished books is almost always a language of shame.

The Hidden Cost of Finishing Everything

Reading time is finite. That's the plain arithmetic of it. If you read thirty books a year—a solid pace for most people juggling work and life—then every book you force yourself through is a book you didn't get to read instead. The sunk cost fallacy applies to books just as much as it does to anything else: the hundred pages you've already read are gone regardless of what you do next, so the only real question is what you want to do with the pages ahead.

There's also a subtler cost. When we treat finishing as the default, we start choosing books defensively. We gravitate toward the safe, the familiar, the reliably engaging. We stop taking chances on translated fiction, on strange structures, on voices that might take fifty pages to click. The ability to quit makes us braver readers, because it lowers the stakes of every experiment.

None of this means you should abandon books at the first dull chapter. Some of the best reading experiences are slow to unfold. A useful rule of thumb: if a book hasn't given you anything by page fifty—a sentence you want to underline, a question you want answered, a character you're curious about—it's fair to consider whether the two of you are a match. And if you're past a hundred pages and reading feels like homework, that's usually your answer.

How to Quit Well

If you're going to put a book down, do it deliberately. Some readers write a short note on the last page they read—why they stopped, what they were hoping for—so the book becomes a record rather than a loose end. Others pass it along to a friend who might connect with it better. There's something generous in that: acknowledging a book isn't for you doesn't mean it isn't for anyone.

It also helps to separate the book from the moment. Some books are simply wrong for the season you're in. A dense family saga during a chaotic month at work, a bleak novel during a hard winter—timing matters more than we admit. You might return to it in a year and find it transformed, though really it's you who has changed.

The readers I admire most aren't the ones with the longest finished lists. They're the ones with the clearest sense of what they're looking for, and the confidence to move on when a book isn't providing it. A library, after all, is not a to-do list. It's a conversation, and you get to choose which voices to keep listening to.