Most leadership books treat Exodus 18 as a delegation lesson.
Don't do everything yourself. Trust your team. Empower others.
All true. But there's something more specific happening in this passage. It has direct implications for how a ministry team shares information, and it explains why so many church staffs feel the weight of coordination chaos even when everyone on the team is gifted, faithful, and genuinely trying.
Read the Text Slowly
Moses was sitting from morning to evening hearing disputes. The people stood around him all day. His father-in-law Jethro watched this for one day and asked a simple question:
"What is this you are doing for the people? Why do you sit alone, while all the people stand around you from morning to evening?"
Moses explained: the people come to me when they need God's direction. I settle their disputes.
Jethro's response is worth reading carefully:
"What you are doing is not good. You and the people with you will certainly wear out, for the thing is too heavy for you. You are not able to do it alone."
Then he gave a system. Appoint capable men over thousands, hundreds, fifties, and tens. Let them judge the small matters. Bring only the great matters to Moses. And do one more thing: make the way known. Teach the people the statutes and laws so that they can act with understanding, not just receive rulings.
The result: "You will be able to endure, and all this people also will go to their place in peace."
What Jethro Actually Fixed
Here's what most leadership summaries miss: Jethro didn't just fix Moses's workload. He fixed the information architecture.
Under the old system, Moses was the only point of access to direction. Every question, every dispute, every decision requiring clarity flowed to one person. And that person sat there, from morning to evening, because there was no other way for information to move.
The new system had two components:
-
Clear responsibility. Chiefs of thousands, hundreds, fifties, tens. Each one accountable for their jurisdiction. This is the delegation part, and yes, it matters.
-
Shared information. "Make known to them the way in which they must walk." Tell the leaders what they need to know to lead well. Put the right information in the right hands so each person can make good decisions in their area without routing everything back to Moses.
Both parts are necessary. Delegation without shared information isn't delegation — it's abandonment. You can give someone a role without giving them what they need to fulfill it. That's not the Exodus 18 system. That's just moving the bottleneck one level down.
The Ministry Application
Walk through your typical week and ask: how does information move?
When your senior pastor decides on a series, who finds out? When? How?
Does your worship pastor know the passage before they start planning? Does your kids director know the series theme before they select curriculum? Does your production team know what kind of Sunday it is before they set up the stage?
In most churches, that information lives in one person's head or a single document, and it moves only when someone manually sends it. Which means it moves inconsistently. Sometimes early, sometimes late, sometimes not at all until someone asks.
That's the Moses problem. Moses wasn't failing. The system around him was. He was faithfully doing what the system required: being the only person who knew what to do. And it was wearing everyone out.
Chiefs Need What They're Equipped to Handle — Plus the Information to Do It
Jethro's solution wasn't just "have more leaders." It was: have leaders who have what they need to lead.
The kids ministry director needs to know the teaching theme or series the parents are listening to. How does what the kids are learning align with what the adults are learning? Should it align? Maybe yes, or maybe no. Either way, it shouldn't be an accident.
The worship pastor needs the passage before they plan songs. Not as a constraint, but as a foundation. Is the message landing in contemplation or exclamation? Your closing response song needs to match and your team needs to be prepared.
The production lead needs to know the service direction. Not so they can micromanage the creative, but so they can set up the environment that serves it.
None of these people need to be in every meeting. They don't need to be in the pastor's inner circle of decision-making. They just need the information that flows from those decisions to reach them automatically so they can do their work with confidence and context.
"Make the Way Known"
Exodus 18:20 is worth holding: "You shall make them know the statutes and the laws, and show them the way in which they must walk and what they must do."
Make the way known. This is the pastor's responsibility, and it's not just about preaching. It's about ensuring that the leaders around you have what they need to lead well in their area.
A runsheet makes the way known for a volunteer. A teaching calendar with series and passages makes the way known for the worship pastor. A pre-filled team workspace makes the way known for the kids director before they've had their first cup of coffee Monday morning.
"Make the way known" is not a communication suggestion. It's a leadership obligation. And a good system is what makes fulfilling that obligation automatic rather than heroic.
The Promise at the End
Jethro closes with a promise: "If you do this, God will direct you, you will be able to endure, and all this people also will go to their place in peace."
Two beneficiaries. Two outcomes.
The leader endures. Ministry is long. The goal is not one extraordinary Sunday. It's faithful, sustainable service for decades. A pastor who is the only information hub for their entire team will wear out. It's not a character failure — it's a structural guarantee. When the information flows automatically, when the team has what they need, and when the small matters are handled by capable people who have the context to handle them, the pastor gets their capacity back for what they were actually called to.
The people go to their place in peace. This is the one that often gets cut from leadership summaries. The goal is not an efficient staff meeting. It's a Sunday that actually serves the person in the seat. When the whole team is working from the same vision, with shared context and clear responsibility, the fruit reaches all the way to the person who walked through the door not sure why they came. The worship connects with the message. The kids experience reinforces the theme. The greeters are ready. The whole thing is woven together.
Not by accident. By a system that carried the vision from the pastor's calendar to every team and let each one do their work with confidence.
A Note on What This Isn't
This is not an argument for bureaucracy. It's not a case for adding more meetings, more org charts, or more management overhead.
Jethro's system was elegant because it reduced the coordination cost, not increased it. Each leader had what they needed to act independently. Moses was freed from questions he didn't need to answer. The people got faster resolution. The information flowed from the source without requiring Moses to personally carry it to each chief of ten.
That's the design. Clear roles. Shared information. Information that flows from the source automatically. The leader can lead, the team can act, and the people can go to their place in peace.
We Built This Because We Believed It
Jethro exists because we were convinced that Exodus 18 is not just an ancient management principle. It's a description of how information should move in any team that shares a mission and cares about doing it well.
The name is intentional. We're not building software with a Bible verse on top. We're building a system for the working team behind Sunday — inspired by the conviction that good information flow is a spiritual act, and that the people who work hardest for the mission deserve the tools to carry it without wearing away.
You will be able to endure. And all these people will go to their place in peace.
That's why we built this.