The Exigence Problem Most People Get Wrong
You read a speech or an op-ed and someone mentions the exigence without really explaining what that means in practice. I've seen this cause real trouble in rhetorical analysis classes and in professional communications work. The textbook definition says an exigence is an issue, problem, or situation that can be changed through discourse. That's accurate and useless at the same time. It's the specific condition that makes communication necessary in the first place. Bitzer defined it as something imperfect but capable of being improved through words. The key word there is imperative - an exigence demands a response. It's not just any topic you could discuss. It's the thing that actually pushes someone to speak or write at a particular moment. I learned this distinction the hard way. A few years back I was consulting on a crisis communications project for a mid-sized tech company. Their PR team had drafted a statement about a data breach, and it was getting zero traction. No one was engaging with it. I looked at what they'd written and realized the problem immediately. They'd described the breach technically. They hadn't identified the actual exigence. The exigence wasn't the data loss itself. It was the erosion of user trust. Those are different things, and addressing one while ignoring the other made the whole message miss.
We rewrote it. Instead of opening with server specifications and incident timelines, we led with the fact that customers' personal information had been exposed and that the company understood why people were upset. Engagement went up significantly. Not perfect, but better. The exigence was clear once we stopped describing symptoms and started naming the real problem that needed addressing through discourse. Here's the counter-intuitive part that most people miss: an exigence must be urgent enough to demand action but not so urgent that action becomes impossible. When both conditions aren't met, you don't have a true exigence. You have either noise or paralysis. In practice this shows up constantly. A startup founder pitching investors about a market opportunity doesn't have an exigence until there's actual evidence of market failure or competitive threat. The opportunity itself is interesting. The exigence is the proof that the status quo is breaking. Another thing that trips people up is assuming every problem has a corresponding exigence. Sometimes a situation is genuinely problematic but doesn't create any rhetorical opening. If nobody can see the problem, or if addressing it wouldn't actually change anything, you're working with a grievance, not an exigence. The difference matters because it determines whether rhetoric will be effective or wasted.
I've also seen this fail in academic settings where students treat any topic as an exigence. Writing about climate change isn't automatic. The exigence would be something specific like a local school board vote on curriculum changes. That's concrete. That creates a moment where discourse can actually shift something. Climate change broadly is too diffuse. It's a context, not an exigence. The workaround I use now is to ask three questions before treating anything as an exigence: Who is affected? What specific change is being demanded? Can discourse realistically produce that change? If you can't answer all three clearly, you probably don't have an exigence yet. You might have a topic, a concern, a theme, but not the kind of rhetorical situation that Bitzer was describing. There's also the timing dimension that people overlook. An exigence can emerge, intensify, and dissipate. A local news station covering a city council decision has a time-sensitive exigence. Once the council votes, the exigence shifts or dies. The rhetoric that worked before the vote may not work after. Recognizing when an exigence is active versus when it's fading is part of knowing when to communicate and when to stay quiet.
Get the Full Details

If you're trying to identify one in your own work, start by finding the gap between what is and what should be. The exigence lives in that gap. Not in the description of the current state, not in the vision of the ideal state, but in the tension between them. That tension is what makes words matter.