Head-hopping

Head-hopping is switching whose private thoughts we are in, mid-scene, without a break. The narration starts inside one character's head (what she fears, what she notices, how she reads the room) and slides, without a scene break or any signal, into another character's head in the same continuous scene.

It gets flagged constantly in critique, and the reason it reads as an error is subtler than rule-breaking: the reader has been led to build a single point of view and then feels the floor move. The scene's questions (whose scene is this, whose judgment can I trust) lose their answer.

Head-hopping is not omniscient narration

The distinction matters and is often missed. In true omniscient narration, a single, consistent, all-knowing narrator moves between minds deliberately: the narrative voice stands above all the characters and dips into each with the same authority, in the same tone. In head-hopping, the narration is written as if limited (deep in one perspective) and then jumps without that narratorial stance. Omniscient reads as a controlled camera move; head-hopping reads as a stumble.

The practical test: can you point to the narrator? If the prose has one voice that visits everyone, it is omniscient. If the prose mostly belongs to one character and then, for a paragraph, suddenly belongs to another and then returns, it is head-hopping. (Omniscient, limited, deep limited and the other points of view are worth knowing as a set before deciding which one a scene is in.)

Where it comes from

Almost always from good instincts: the writer knows something another character feels, and wants it on the page now. The usual carriers are emotion verbs attached to the wrong character ("he felt his stomach drop" while we are in her point of view), and reaction shots during dialogue ("John didn't believe her" when John's interiority is closed to us).

How to fix it

1. Declare the scene's owner. Before writing, decide whose scene it is. One viewpoint per scene is the cleanest discipline; one per chapter is looser and common in serial fiction.
2. Break honestly. If you truly need the other character's take, end the scene and start a new one from their side. A scene break is a cheap, honest signal.
3. Externalize the other minds. Instead of entering John's head, give her something to read: John's knuckles, the pause before he answers, the joke that lands wrong. This is also simply better prose for it: one character's interpretation of another is characterization.
4. Commit to omniscient, if that is the book. A consistent omniscient narrator may visit anyone, but the voice must stay recognizable, and it must establish that authority early, in chapter one, so the reader knows the rules. The failure mode is switching stances late.
5. Check transitions in revision. Search the draft for emotion and cognition verbs and check whose head each belongs to. Slips cluster at dialogue tags and scene middles.

A special case: rotating viewpoints

Web serials and multi-lead novels often rotate viewpoints by chapter, marked with the character's name. That is not head-hopping; the signal is the format. The discipline still applies inside each unit: once a chapter is in Zane's head, it stays there for the scene. The unmarked mid-scene jump is what reads as error, not the existence of multiple viewpoints.

Keeping POV consistent at length

Point of view is a canon fact about your project, like tense: it is either a rule or it is not, and drift usually starts small (one paragraph in the wrong head, once, at 2am). Two records help: a single line in your project notes declaring the POV scheme (whose heads, in what rotation, with what marks), and a revision pass that reads only for stance. In Kanonara's terms this is exactly a story bible fact: write the rule down, and deviations become findable instead of deniable.