There's one mistake that gets repeated constantly in PR: waiting for a negative story to break before taking any action.

Reactive response is structurally disadvantaged. Once a frame has already been set in the media, saying "actually, that's not how it is" tends to backfire. Negative impressions, once embedded, require several times the effort to undo.

Flip the logic, and the solution is simple. Most negative coverage is predictable.

Why It's Predictable

Journalists' attention tends to come from three broad areas: Is there a group being harmed by a new service or policy? Does it look like you're copying an established player or encroaching on their territory? Is it connected to a controversy that has come up before?

Run any service or announcement you're planning through these three lenses, and you can usually see where the attacks will come from. This isn't about trying to persuade journalists — it's about learning to see through their eyes before they do.

Two Pillars of Proactive Response

The first is deflation. This means turning potential attack points into already-public information. Quietly burying a sensitive issue makes it explode more dramatically when it eventually comes out. But if you release the relevant context first, by the time a journalist tries to write about the same material, it becomes "a story everyone already knows."

The second is frame capture. The same facts read entirely differently depending on the context in which they're first introduced. If you can establish a product in the press as "a new user experience" before it gets labeled a "copycat," readers will already have a different frame of reference when critical coverage appears later.

Build the Scenario Document First

Here's the actual workflow:

  1. Before launch, list out every angle from which this service could be attacked
  2. For each angle, draft the kind of story a journalist might actually write
  3. Prepare messages and supporting evidence to address each scenario
  4. Plan the strategic timing and sequence of disclosure

It sounds complicated, but the core is simple: having the team honestly ask, "If a critical journalist were covering this, what would they write?"

Why Pre-emptive Response Is Hard to Execute

Within organizations, this work tends to break down for largely psychological reasons. When a team is excited about a new service they expect to succeed, raising the possibility that it "might get criticized" feels uncomfortable. It can seem like you're pumping the brakes on a launch everyone wants to accelerate.

But that is precisely where PR belongs. Writing the bad story before the journalist does. Running the uncomfortable imagination exercise inside the team first.

Once a team has been through this process, their perspective shifts. Pre-emptive response doesn't slow things down — it eliminates the firefighting that would otherwise come later.

← All Posts