Hook
Mike Johnson has now brought the FISA reauthorization bill—a renewal of certain U.S. surveillance powers—to the House floor three times. Two votes failed. Now there’s a third plan, with new provisions, new compromises, new vote counts. Most people see this pattern and think: chaos, gridlock, failure. But that interpretation misses what’s actually happening.
Why does Congress vote on the same bill multiple times, and what happens in between those votes that turns a failure into a pass?
Teaching 1
When a bill fails on the House floor, it doesn’t die. It goes back into negotiation. Leadership—in this case, Speaker Johnson—sits down with faction leaders, counts votes again (this process is called a “whip count”), and asks: what would it take to get you to yes?
Here’s the mechanic most people don’t see: a failed vote is information. It tells you exactly where the opposition is. Some members vote no because the bill goes too far. Others vote no because it doesn’t go far enough. The first vote reveals the gap. The second vote tests whether the first set of compromises worked. The third vote—usually—is the one that passes, because by then leadership knows what every faction needs.
Bills fail for three reasons. First, not enough votes from your own party. Republicans control the House, but factions within the party—privacy hawks, national security hawks, moderates—want different things. Second, not enough votes from the opposition. Democrats might support the bill in concept but oppose specific provisions. Third, both. The FISA bill failed twice because Johnson couldn’t hold his own coalition and couldn’t peel off enough Democrats to compensate.
Between votes, leadership makes moves. They offer amendments—changes to the bill text—to win over holdouts. They make procedural promises: “Vote yes now, we’ll address your concern in the next piece of legislation.” They trade favors: “Support me on this, I’ll support you on that.” This isn’t corruption. It’s how you get 218 people—a House majority—to agree on anything.
The process is public, loud, and iterative. Each failed vote happens on the floor, on the record, with every member’s position visible. That visibility is the point. It forces negotiation into the open. Leadership can’t guess what members want—they have to ask, offer, adjust, and ask again.
Teaching 2
Now zoom out. This problem—how do you get consensus when people have different priorities?—isn’t unique to Congress. It shows up in corporate boards, academic committees, nonprofit coalitions, treaty negotiations, anywhere a group of equals has to make a collective decision.
Parliaments solve it through iteration. They vote, fail, negotiate, vote again. The failed votes aren’t wasted effort. They’re information-gathering. They reveal who objects, why they object, and how strong their objection is. A member who votes no but signals openness to compromise is different from a member who votes no and won’t budge. The first vote sorts those groups.
Democratic systems are designed to surface disagreement early, loudly, and repeatedly. Authoritarian systems suppress disagreement or punish it. Rubber-stamp systems ignore it. But systems built on debate and voting treat disagreement as data. The friction tells you where the real divisions are.
This is why failed votes don’t mean the system is broken. They mean it’s working. A bill that passes on the first try either had unanimous support (rare) or didn’t face real scrutiny (common). A bill that fails, gets amended, and passes on the third try has been stress-tested. The final version reflects actual consensus, not assumed consensus.
Organizations that skip this step—that avoid public disagreement or rush to yes votes—make worse decisions. They either enforce false unanimity, which breeds resentment, or they fragment, because unresolved objections surface later as sabotage or exit. Congressional procedure forces the conflict early, in a structured format, with rules for how to resolve it.
Teaching 3
There’s a pattern to how this unfolds. First vote: testing the waters. Leadership brings the bill to the floor with a rough sense of support but no certainty. The vote fails. Now they know which members are movable and which aren’t.
Second vote: trying adjustments. Leadership offers amendments, changes a few provisions, and tries again. If this vote passes, great. If it fails, they now know the first set of compromises wasn’t enough. They know which new objections emerged and which old objections held firm.
Third vote: usually the compromise that works. By now, leadership has iterated twice. They’ve offered multiple rounds of concessions. They’ve identified the minimum viable coalition—the smallest set of changes that gets them to 218 votes. This vote tends to pass because the negotiation space has narrowed. Holdouts know this is the last offer.
You see this pattern everywhere. Corporate boards vote down merger proposals, then vote them through after renegotiating terms. Academic committees reject grant applications, then approve revised versions. Treaty negotiators walk away from talks, then return with adjusted language. The structure is the same: fail, learn, adjust, try again.
The friction is the feature. Systems that pass everything on the first try are either authoritarian—one person decides, everyone else complies—or rubber stamps—the real decision happened elsewhere, the vote is theater. Systems that fail repeatedly before passing are doing the work of consensus-building in public.
This doesn’t mean every failed vote leads to a better bill. Sometimes the compromises make the bill worse. Sometimes leadership gives away too much to one faction and loses another. But the process itself—the visible, iterative negotiation—is how groups of equals make collective decisions without coercion.
Close
Next time you see a headline that says “Congress fails to pass bill,” read it as “Congress discovering where the disagreement is.” The messiness is proof the system is working as designed—forcing compromise by making agreement hard.