Silhouette of person standing at crossroads

Sanballat (Opposition)

Internal Struggle

Opposition

Sanballat was a Samaritan official who did everything in his power to stop Nehemiah from rebuilding Jerusalem’s walls. He mocked, threatened, spread rumors, sent false messages, and tried multiple times to get Nehemiah away from the work long enough to trap or discredit him. He never succeeded. His story is included in Scripture not as a profile of a complex internal struggle but as a map of exactly what sustained opposition to meaningful work looks like, and how Nehemiah navigated every tactic without stopping.

What Happened?

When Nehemiah arrived in Jerusalem and began organizing the rebuilding of the walls, Sanballat and his allies Tobiah and Geshem immediately began opposing the work. They mocked the builders and questioned whether the wall would hold. When the work continued, they plotted a military attack. When Nehemiah organized armed guards and the work continued, they tried to meet with him, four times, and he refused each time. They sent a letter claiming he was rebuilding the walls to rebel against Persia and make himself king, and that it would be reported to the king. Nehemiah sent back a denial and kept working. They hired a false prophet to frighten Nehemiah into hiding in the temple in a way that would discredit him. He refused. The wall was completed in fifty-two days (Nehemiah 2; 4; 6).

How Did Sanballat’s Opposition Affect the Work?

  • The opposition created genuine fear among the workers that required Nehemiah to reorganize the entire workforce around both building and defense
  • The threats were credible enough that families were warning workers about danger and some workers had abandoned the project
  • The false accusation letter was designed to trigger political consequences from Persia that could shut the work down officially
  • The false prophet’s message was designed to make Nehemiah look cowardly or impious, which would have undermined his leadership
  • Each tactic was designed to either physically stop the work or remove the person who was sustaining it
  • The opposition failed at every stage not because it was weak but because Nehemiah refused to come down from the wall

The Tragedy

Sanballat’s story ends with the wall complete and himself outside it. He had invested significant effort, political capital, and repeated attempts over fifty-two days into preventing something he could not stop. The text records his tactics in detail, which means they are instructive, but his outcome is simply that the thing he opposed got done anyway. He is remembered entirely for what he tried to prevent rather than for anything he built. His opposition made Nehemiah’s leadership more visible, his prayers more documented, and his methods more instructive than they might have been without the resistance.

The Pattern That Led to Destruction

  1. Identified something being built that threatened his position or his region
  2. Started with mockery and escalated to physical threat when mockery did not work
  3. Tried to pull the leader away from the work through repeated requests for meetings
  4. Used political accusations designed to trigger external intervention
  5. Hired internal agents to frighten the leader from within
  6. Failed at every stage and is remembered entirely for the opposition rather than for anything he built

Practical Steps for Facing Opposition

  • Recognize that mockery is usually the first tactic used against meaningful work, and the appropriate response is to keep working
  • Organize your team around both the work and the resistance rather than assuming you can ignore the opposition
  • Refuse repeated invitations to leave the work for meetings designed to distract, delay, or discredit you
  • Deny false accusations clearly and briefly rather than spending the energy required to defeat them fully
  • Be suspicious of spiritual or personal advice that is designed to make you look bad if you follow it
  • Ask whether the thing being opposed is worth the cost of staying in it, and if yes, stay in it
  • Let the opposition make the work more documented and your methods more visible rather than using it as a reason to stop

Similar Posts