Nobody changes the brief. The project changes anyway.
A brief is written at a single point in time, when everyone in the room agrees on the same version of the truth. A book project runs for months. Somewhere between the brief and delivery, a sales conference reshuffles priorities, an author delivers a manuscript that's different from the one that was pitched, a new team member joins without the context everyone else built up gradually, or an assumption that felt obvious in the kick-off meeting quietly stops being true. None of that means the brief was wrong. It means the brief was a photograph, and the project is a film.
Most of the friction we've seen on projects doesn't come from a single bad decision. It comes from alignment that was real on day one, gently decaying, unnoticed, until the gap between what everyone thinks is happening and what's actually happening becomes too large to ignore quietly. By the time it surfaces, it usually does so as a difficult conversation about a finished piece of work, rather than as a five-minute correction three weeks earlier.
That's the actual argument for regular, unglamorous check-ins — not as project management theatre, but as the mechanism that catches drift while it's still cheap. A short recurring call that asks four plain questions does most of the work: What's changed since we last spoke? What's blocked? Are the priorities we agreed still the priorities? Does everyone understand what happens next? None of those questions are sophisticated. They don't need to be. Their value is in being asked on a schedule, rather than only when something has already gone wrong enough to prompt one.
This matters most on projects with a lot of moving parts and more than one stakeholder feeding in — which describes most trade and education publishing at any real scale. A commissioning editor juggling a dozen live titles, or an art director reviewing a season's worth of covers, doesn't have the bandwidth to notice quiet drift on every project individually. A short, regular alignment habit does that noticing for them, and it does it before drift becomes a delay.
A brief will always be a snapshot. The strongest publishing partnerships don't try to make the snapshot more detailed — they build in the habit of checking it against reality, on a schedule, before the gap has to be discovered the hard way.