I recently finished rereading all seven Harry Potter books, and I have to admit: I spent the next several weeks in a bit of a funk. Not because I disliked the ending. I just wasn't ready for it to be over.
The first time I read Harry Potter, I was a kid. I read the books because they were magical and exciting and funny and terrifying, and because I needed to know what happened next. Hogwarts felt like a real place. Harry, Ron, and Hermione felt like friends. The books were simply something I loved.
This time, though, I read them as an adult—and as an editor. That changed the experience in a way I wasn't expecting.
I was still completely absorbed in the story. I still loved the characters. I still had that strange, almost physical feeling of returning to a place from childhood and finding that it was still there waiting for me. But now I was also noticing the construction.
I noticed the foreshadowing, the long-term character arcs, the way information was withheld and revealed, the escalation of the stakes, the recurring details that became important much later, and the way Rowling gradually expanded the wizarding world as Harry himself grew older and understood more about it.
I kept thinking, That's really clever.
And then, occasionally, Wait. What?
That, I think, is one of the strange gifts of becoming an editor. You don't stop being a reader. You just start seeing what the author is doing. And sometimes, you see the seams.
First, let me say this: Harry Potter is remarkably well constructed.
Before I get into the things that made my editor brain twitch, I want to make something clear: I love these books. Rereading them actually made me appreciate the craft behind them more, not less.
The long-form storytelling is strong. Details planted early become meaningful later. Characters who seem peripheral become essential. The world expands as Harry grows, and the tone matures with him—from a magical children's adventure to a story about war, loss, sacrifice, and survival.
Rowling's control of information is particularly impressive, too. She doesn't simply tell us everything she knows. She controls what Harry knows, what we know, what we suspect, and when we're finally allowed to understand why something mattered.
One of the things I appreciated most on rereading was the sheer amount of setup and payoff. As a child, I could enjoy a mysterious object, an odd bit of dialogue, or a seemingly insignificant detail without knowing whether it would ever matter again. As an adult editor, I found myself noticing how often those details eventually had a purpose.
That kind of long-term planning is difficult to pull off, and Harry Potter executes it beautifully. Good editing isn't simply about finding what's wrong. Sometimes it's about recognizing why something works so well that you shouldn't touch it.
Then there were the moments that made me pause.
Because no book is perfect. Not even one I love this much.
One example that caught me completely off guard involved Hogwarts's gamekeepers.
We learn in Philosopher's Stone that Hagrid was expelled during his third year at Hogwarts. In Chamber of Secrets, we later discover the circumstances surrounding his expulsion: Tom Riddle accused Hagrid of opening the Chamber of Secrets in 1943, and Dumbledore persuaded Headmaster Armando Dippet to let Hagrid remain at Hogwarts and train as a gamekeeper.
That becomes interesting when Molly Weasley visits Hogwarts in Goblet of Fire. Molly reminisces about Ogg, the gamekeeper she remembers from her own time at Hogwarts.
My first thought was: Wait. How does that work?
Hagrid was only a few years behind Tom Riddle at Hogwarts, so his expulsion happened roughly fifty years before the events of Chamber of Secrets. By the time Molly would have attended Hogwarts, Hagrid had already been at the school for decades after his expulsion and had been working toward his role as gamekeeper. Yet Molly remembers Ogg as the gamekeeper from her own school days.
There is a plausible way to reconcile the two pieces of information. Perhaps Hagrid initially worked under Ogg as an apprentice or assistant and didn't officially take over the position until later. In fact, that would make the timeline work.
But the books never actually tell us that.
And that's what made me stop as an editor.
The problem isn't necessarily that the timeline is impossible. It's that the reader has to supply a piece of the history to make the two passages fit together. One sentence establishing that Hagrid worked under Ogg for a time would have resolved the question completely.
And that's the kind of thing I notice now that I wouldn't have noticed as a child. Not because it ruins the story—it doesn't—but because an editor learns to ask:
Where is the reader being asked to supply connective tissue that the manuscript could provide?
Sometimes that connective tissue is unnecessary. Sometimes readers enjoy filling in the blanks. And sometimes one sentence would make the whole thing cleaner.
But not every moment that made me pause was a continuity issue. Sometimes the problem was less about whether something worked and more about how naturally it moved the story forward.
The Taboo on Voldemort's name in Deathly Hallows raised a slightly different question for me. The mechanism itself works: Voldemort's forces have placed a Taboo on his name, so anyone who says it can be located. Harry has spent years being one of the people willing to say Voldemort's name, so it makes sense that this eventually puts the trio in danger.
What bothered me was how conveniently the mechanism arrives.
By this point in the book, Harry, Ron, and Hermione have spent a long stretch hiding in the woods, moving from place to place and struggling to figure out what to do next. The story has deliberately isolated them from Hogwarts and from most of the other characters we've come to know. That isolation creates tension, but it also slows the plot considerably.
Harry says Voldemort's name. The protective enchantments around their location are breached. Death Eaters arrive. The trio is captured and taken to Malfoy Manor, where the story suddenly has a new setting, new dangers, and a new chain of events waiting for them.
It works. But on rereading, I couldn't help noticing how perfectly everything falls into place. The Taboo breaks the stalemate in the woods, brings the Death Eaters straight to the trio, and delivers them directly into the next major sequence of the story.
As a reader, I went with it. As an editor, I could see the convenience of the mechanism. It felt less like something that naturally grew out of the story and more like a particularly efficient way to get the characters where they needed to be.
I wouldn't necessarily cut it. The Malfoy Manor sequence is important, and the Taboo does make sense within the world Rowling has created. But I might have asked whether the transition could feel more organic.
Because that's another distinction editors have to make:
Something can work logically and still feel mechanically convenient.
A plot device doesn't have to be a contradiction to make a reader feel the author's hand on the wheel. Sometimes the question isn't “Does this make sense?” but “Does this feel like the most natural thing that could happen next?”
A different version of that question came up for me with Moody's eye.
When Harry discovers that Mad-Eye Moody's magical eye has ended up embedded in the door of Umbridge's office, my immediate response was logistical:
- How did that happen?
- Who recovered it?
- How did it get here?
But then I realized something important: the logistics aren't really the point of the scene.
The image itself is doing enormous symbolic work. Umbridge has literally turned Moody's eye into a surveillance device, taking the magical eye of a man famous for “constant vigilance” and using it to spy on Ministry employees.
That's effective.
So even though my editor brain noticed the gap, my reader brain understood that the gap didn't matter.
And that's another thing I want to remember when I'm editing someone else's book: Not every unanswered question is a problem. Sometimes the reader needs an explanation. Sometimes the reader needs to be allowed to wonder. The trick is knowing which is which.
But the ending left me wanting something different.
I loved so much of the climax: Harry choosing to sacrifice himself, the revelation about the piece of Voldemort's soul inside him, the return to Hogwarts, Neville's moment, Molly and Bellatrix, the final confrontation, the resolution of the Elder Wand, and finally Voldemort's defeat. There is so much payoff packed into those final chapters.
Still, when I finished the book, I felt strangely unsatisfied. Not because I disliked what happened, but because I wanted to stay there longer.
I think what I was missing was falling action.
We often talk about stories as having a beginning, middle, and end, but there's a useful distinction between the climax, the falling action, and the resolution:
- The climax answers the central question: Who wins?
- The falling action gives the reader a chance to process what just happened: What does this mean?
- The resolution establishes the new normal: What does life look like now?
Deathly Hallows gives us an enormous climax and then moves fairly quickly toward the resolution. There is some immediate aftermath, of course. Harry speaks with Dumbledore's portrait, the Elder Wand's allegiance is resolved, and the survivors begin to reckon with the end of the battle.
Then we get: Nineteen years later.
And that's where I felt the loss.
I didn't need another hundred pages. I needed room to breathe.
The ending wasn't necessarily too short. The emotional transition simply needed more room.
Voldemort is dead. The external conflict is resolved. But the emotional questions haven't all been answered yet.
What does it mean to survive a war at seventeen? What does Hogwarts look like after everything that happened there? How do these kids begin rebuilding their lives? How do they grieve the people they lost? Who are they now that the thing they've been fighting for seven years is finally over?
I wasn't looking for an explanation of every character's career, a chapter about every wedding or funeral, or another three books. I simply wanted more space between Voldemort is dead and nineteen years later.
I'd spent seven books growing up alongside these characters. I'd watched them lose people, make mistakes, become braver, repair broken friendships, fall in love, and become responsible for one another. Then they survived a war.
I wanted to see what came next—not in exhaustive detail, but enough to feel the transition.
That's the distinction I kept coming back to: informational resolution isn't always the same as emotional resolution.
The epilogue gives us information. Harry and Ginny are married. Ron and Hermione are married. They have children. Their children are going to Hogwarts. Neville is teaching there. Draco has a son. Teddy Lupin is growing up. Harry's scar hasn't hurt in nineteen years.
We're told, essentially: They're okay.
And I loved that.
I just wanted to see how they got there. To sit with the survivors for a little while. To feel the strange quiet after the battle. To see what Hogwarts looked like after everything that had happened there. To watch these characters begin to become the adults the epilogue eventually shows us.
I didn't need every detail. I needed the journey from war to ordinary life to feel lived-in.
And I think that's part of why some of the deaths bothered me, too.
I'm not arguing that these deaths shouldn't have happened. This is a story about war, and death is part of the reality of war. In fact, the way some of these deaths are handled may have been very intentional.
Lupin and Tonks are a good example. We don't even witness their deaths. Harry discovers their bodies afterward, lying among the casualties of the Battle of Hogwarts.
And there's something almost brutally realistic about that. In a real battle, people die while you're somewhere else. You don't necessarily see it happen. You don't always get a final conversation or a moment of closure. Sometimes you simply find out afterward that someone you loved is gone.
The same is true of Harry's experience in that moment. He is still in the middle of a battle. Voldemort is still alive. Harry still has a mission. There is no time to stop and process every loss before the story drives him toward the final confrontation.
From a storytelling standpoint, I understand the choice. From an editor's standpoint, I can even appreciate it.
And yet, as a reader, it hurt.
Lupin was one of the first adults at Hogwarts to treat Harry with genuine kindness and respect. He taught Harry the Patronus, gave him a connection to his parents that went beyond stories and photographs, and became one of the few adults Harry could trust. Then, suddenly, he's gone. Tonks is gone, too, leaving their infant son without either parent.
Fred's death hit me in a similar way. We spent years getting to know him, and his death carried enormous emotional weight. But the battle doesn't stop for us to process it. There is no time to sit with the grief before the plot pushes forward.
And maybe that's exactly the point.
The world doesn't stop just because something devastating has happened.
I understand that.
I just wasn't emotionally ready to move on.
And that's where my editor brain and my reader brain actually do meet—not in disagreement over whether the choices work, but in recognizing that what works structurally isn't always the same thing as what feels satisfying emotionally.
That made me wonder, as an editor: How much narrative space should a loss receive in proportion to the emotional weight of the relationship that came before it?
I don't think there's a universal answer. Sometimes the shock is the point. Sometimes lingering over a death would weaken it. Sometimes the most powerful choice is to let a character disappear from the story almost as abruptly as death itself does.
But sometimes the reader needs space to grieve, even when the character doesn't have that space.
You can love a book and still notice its flaws.
In fact, I think loving a book can make you a better critic of it.
I could see both things at once: the kid who was completely enchanted by the story and the editor who was mentally pulling out a red pen. I noticed the seams and the places where I would have asked for another sentence, another beat, another moment to breathe.
And somehow, none of that destroyed the magic. Maybe it made the magic more impressive.
Because editing has taught me something I didn't understand when I was a kid: A book does not have to be perfect to be extraordinary.
Every book has decisions, compromises, and places where the author could have taken another route. One reader might think, Brilliant, while another might think, I would have handled that differently. Neither response means the book has failed. It's simply part of storytelling.
That's something I want to remember when I'm editing someone else's book.
I'm not looking for reasons to tell an author their book doesn't work. I'm looking for the places where the reader might stumble.
I'm asking questions like:
- Where might the reader lose the thread?
- Where has the author asked the reader to make an inference the manuscript could make clearer?
- Has the emotional payoff been earned?
- Does the pacing give important moments enough room to breathe?
- Is an unanswered question creating intrigue—or simply creating confusion?
And sometimes the answer is simply: Leave it alone.
It’s a part of editing I think people sometimes misunderstand.
An editor isn't supposed to make every book sound like it was written by the editor. The job is to help the author make their book as strong as it can be.
Sometimes that means adding a sentence. Sometimes it means cutting a paragraph. Sometimes it means questioning an entire chapter. And sometimes it means saying, This works. Don't touch it.
That's what I took away from rereading Harry Potter as an editor.
More than anything, the experience left me with an even greater appreciation for the craft behind a story that could follow a generation from childhood to adulthood and make us feel as though we'd grown up alongside its characters.
I also finished the series wishing there were another book.
For all the seams I noticed, the magic was still there.
