The assigned passage is Nehemiah 8:5–10. Here is a brief excerpt from verse 8 in the New Living Translation:

“and clearly explained the meaning of what was being read, helping the people understand each passage.” (Nehemiah 8:8, NLT, excerpt)

The setting is Jerusalem after the return from exile, with the wall now finished. The people request the Law of Moses, God’s instruction for Israel. Ezra reads before men, women, and children able to understand. They stand, worship, and receive instruction from the Levites. When the reading brings tears, Nehemiah, Ezra, and the Levites direct them toward the joy appropriate to this holy day, including sharing food. Later in the chapter, further study leads to observing the Festival of Shelters. This is Israel being formed by God’s covenant Word. Ezra is a priest and scribe, not an executive announcing his own strategy. The Levites explain a truth that governs them too. Their responsibility is faithful understanding, not securing approval for a leader’s preferences.

That distinction must travel with us into the workplace. Your business plan does not carry the authority of God’s Law, and disagreement with your interpretation of a deadline is not disobedience to God. Christian leadership becomes dangerous when it borrows the seriousness of Scripture to protect ordinary decisions from examination. The application here concerns how we serve people with words. Paul gives a related standard in Ephesians 4:11–16 and 29: Christ provides ministry that equips his people for maturity, and believers should speak in ways that benefit their hearers. His immediate subject is the church’s life in Christ. Christians bring that responsibility for truthful, helpful speech into their professional conduct without turning their team into a church or their instructions into revelation.

Understanding requires us to notice the distance between what we know and what another person has been given. A specialist has months of context behind a sentence that a new colleague encounters for the first time. A manager knows which previous decision still applies and which exception has quietly changed. The people listening may have neither piece of information. Technical language can be necessary, but necessary terms still need explanations suited to the audience. Complexity becomes a leadership problem when we use it to avoid the harder work of making our reasoning accessible. Ask yourself what your listener would need to know to make the next responsible decision. The explanation might need a definition, a concrete example, or a sentence connecting the decision to its purpose. It might need a quieter conversation with someone who cannot comfortably ask in a large meeting. Choose the form that helps the actual listener. A longer document is useful only if the extra detail answers a question the person needs resolved. That question gives expertise a useful task. It also exposes how often an apparently obvious instruction depends on knowledge we have never shared.

Consider a hypothetical customer support team receiving a revised refund policy. The manager announces that exceptions require approval and assumes the instruction is clear. One employee interprets that as a ban on every refund outside the standard period. Another thinks a supervisor’s informal agreement counts as approval. A third keeps customers waiting because nobody named the person authorized to decide. Repeating the original sentence more firmly will not resolve those differences. The manager needs to explain what counts as an exception, who can authorize one, and what the employee should tell the customer while waiting. A worked example can reveal the missing detail. Ask someone to walk through a realistic request using the policy, then listen for the point where the written instruction stops helping them act responsibly.

That conversation depends on the way you receive uncertainty. The Relational Gates chapter in The Decision Fortress describes the weight a leader’s words carry. An impatient response can make the next honest question harder to ask. If someone admits confusion and you answer with a remark about how simple the policy is, you have made understanding more expensive. The person now has to risk embarrassment to get the information the work requires. Try taking responsibility for the explanation instead: “Show me where my instructions leave you guessing.” Follow the answer without interrupting to defend what you meant. Thank the person for identifying the gap. Your response should make the correction useful to everyone who encountered the same uncertainty but did not yet know how to name it.

Clarity also requires honesty about what remains undecided. You do not serve people by reducing a complicated situation to a confident sentence that hides a real limitation. If a deadline depends on a supplier’s answer, name that dependency. If a policy has two competing obligations, explain who will help resolve the conflict. If you do not know an answer, identify how you will find it and when people can expect a response. The Work Gate in The Watchman’s Protocol for Men challenges the habit of making professional achievement the foundation of identity. That examination belongs here as well. A leader who needs to appear indispensable may resist explaining enough for others to act without constant rescue. Bring that desire before God. Shared understanding can require surrendering the satisfaction of being the only person who knows.

The response in Nehemiah 8 reaches beyond acquiring information. People move from hearing to understanding, rejoicing, sharing, and practicing what they have learned. Those are responses within Israel’s covenant life, not promised outcomes of a good presentation. Our workplace check should be modest and concrete. Can the person explain the decision in their own words? Can they use it in an ordinary situation? Can they identify when they need help? Invite those answers as feedback on your explanation, not a public test designed to expose the weakest listener. Understanding also leaves room for disagreement. Someone may explain your policy accurately and then identify a flaw in it. Receive that information seriously. Clear communication has served its purpose when it makes a real problem visible, even if the problem is yours to repair.

Choose one instruction your team must use this week and review it with someone who actually carries it out. Ask them to describe the next decision it requires and the point at which they would seek help. Revise one confusing sentence or missing step together, then put the corrected guidance where the team can find it. This continues yesterday’s concern with stewardship beyond a finished project: the person receiving responsibility also needs usable understanding. Tomorrow, Stand and Rebuild turns to Nehemiah 9 and the truthful memory that prepares a people to renew their commitments. Today, take time to discover what your words have made clear and what they have left uncertain. Pray for humility to hear the answer. Give one person an explanation they can use, and welcome the question that helps you make it better.

Leadership Challenge

Which instruction leaves your team guessing? Ask one person to explain how they would use it, listen without defending your wording, and correct one gap together.

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

In Nehemiah 7:1–5, the wall is finished and its doors are installed. Nehemiah’s account turns immediately to appointments, including gatekeepers, singers, and Levites. He entrusts Jerusalem’s governance to his brother Hanani and to Hananiah, the fortress commander. These are responsibilities within Israel’s covenant community after exile, where restored worship and shared life matter alongside security. Hananiah receives a description worth pausing over. The passage identifies more than his position or his connection to the work. Here is the closing description from verse 2 in the New Living Translation:

“for he was a faithful man who feared God more than most.” (Nehemiah 7:2, NLT, excerpt)

The next instructions concern the gates and the residents’ watches. Specific people will guard specific places. The city remains sparsely populated, with houses still awaiting rebuilding. Nehemiah then credits God with prompting the registration of the community and consults an earlier record of the returning exiles. The rest of the chapter names families and responsibilities, addresses questions of ancestry and priestly service, and records contributions. We may hurry through those names to reach the next dramatic event. Their presence reminds us that Jerusalem’s restoration concerned an actual people with a history before God. The wall served their life together. Completing the structure did not remove the need to order that life faithfully, and the next administrative step was itself something Nehemiah attributed to God’s initiative.

This is not a command to organize a company like ancient Jerusalem. We should not turn priestly ancestry into a hiring policy or use the watch arrangements to justify making employees permanently available. The narrative shows what Nehemiah did in a particular setting. The wider Christian obligation is to use what God entrusts to us in service to others. Peter addresses believers facing suffering and teaches them to pray, love, offer hospitality, and exercise God’s gifts with the strength God provides. Within that instruction he writes, “Use them well to serve one another.” (1 Peter 4:10, NLT, excerpt). The immediate setting is the believing community, not a corporate operating model. Its account of gifts received for service should still shape the Christian who takes responsibility for other people’s work.

A finished project gives that responsibility a new form. During construction, the pressing question may be whether the thing can be built. After completion, someone must understand how to care for it, recognize trouble, and respond without waiting for the original leader to rescue every situation. The Decision Fortress develops this concern in its chapter on what a leader leaves standing. People need to grow capable of carrying responsibility beyond the leader’s immediate presence. That growth requires more than announcing trust at the celebration. Have you explained the decisions they can make? Have you given them access to the information those decisions require? Have you made time for them to practice while help is available? A handover becomes credible when the receiving person can describe the responsibility in their own words and has the means to carry it.

Character belongs in that conversation alongside competence. Hananiah’s description should prompt Christian leaders to examine their own reverence for God; it does not authorize a religious test for colleagues. In a workplace, look at the conduct you can actually evaluate. Who reports an emerging problem before being asked? Who keeps commitments when the audience has moved on? Who can receive correction without making the person offering it regret speaking? The discussion of hiring for character in Christian Leadership in the Professional World asks us to notice how people respond to challenge and to being right. Those questions remain useful when assigning responsibility to someone already on the team. Technical ability matters, and trustworthiness needs evidence. Familiarity, enthusiasm, and the willingness to agree with you cannot carry the whole judgment.

Imagine a team that has just launched a customer scheduling service. This is a hypothetical example. The project lead thanks everyone and begins the next assignment. The person expected to manage the service has access to the calendar but cannot change a broken booking rule. Customer support knows whom to contact during launch week, but no one has agreed on what happens afterward. The service works until a customer encounters the first exception. Then several people spend an afternoon discovering that each thought someone else owned the decision. The missing work was small enough to sound administrative: name the responsible person, agree on their authority, show them the known problems, and establish where unresolved decisions go. Without that conversation, the people depending on the service inherit uncertainty that the launch team could have reduced.

The answer does not need to be a large manual. Before closing the project, sit with the person receiving it and walk through one ordinary day and one plausible problem. Ask them to show you where they would find the information, what they could decide themselves, and when they would need help. Let their questions expose the gaps. Record the answers in a place the next person can find, then agree on a first review date. If the assignment exceeds their time or authority, repair that mismatch before calling the transfer complete. A document cannot grant an authority you still refuse to release. A named owner cannot supply capacity you have already committed elsewhere. The practical test is whether a real person can carry the work under the conditions you have actually provided.

Continued care must also make room for people to stop working. The Work Gate in The Watchman’s Protocol for Men examines what happens when professional achievement becomes the source of identity. A leader can keep every decision nearby because being needed feels reassuring. Another can pursue the next launch so quickly that maintenance feels beneath their attention. Both habits deserve an honest examination before God. Responsible delegation allows people to rest because support is shared and limits are understood. It allows the original team to celebrate a completed assignment without pretending its ongoing needs have disappeared. The goal is neither endless personal supervision nor a hurried exit. It is a clear transfer of responsibility, with enough preparation and support that people are not left carrying an obligation they never knowingly accepted.

Choose one recently completed project today and have the handover conversation you have been postponing. Ask the person expected to maintain it what they believe they own, what they can decide, and what still depends on someone else’s help. Listen for one gap you can close this week. Thank them for making that gap visible, then put the agreed responsibility and support in writing. Yesterday’s passage pressed us to protect attention long enough to finish the assignment. Today’s asks us to care about what happens once the milestone is behind us. Tomorrow, Stand and Rebuild moves to the public reading and explanation of God’s Law in Nehemiah 8. The people’s formation continues. Today, let your completed project receive one more act of care: make sure the person carrying it forward has what they need.

Leadership Challenge

Who is carrying a project you have already marked complete? Meet with that person, clarify their authority and support, and resolve one gap before the week ends.

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

In Nehemiah 6:1–9, Jerusalem’s wall has no remaining gaps, though its gate doors are not installed. Sanballat and Geshem ask Nehemiah to meet them away from the city. He recognizes a plot to harm him and refuses. They repeat the invitation four times; his answer holds. Nehemiah is serving among God’s covenant people after exile, helping restore Jerusalem, not protecting a private career ambition. The reply belongs to that assignment. Here is a brief excerpt from verse 3 in the New Living Translation:

“I am engaged in a great work, so I can’t come.” (Nehemiah 6:3, NLT, excerpt)

The invitation then becomes intimidation. An open letter alleges rebellion and royal ambition, threatening to carry the report to the king unless Nehemiah meets with his opponents. He rejects the accusation and continues working. The pressure is aimed at more than his schedule. It seeks control over his response. A leader worried about reputation can become easier to redirect than a leader worried about the work. We should recognize that temptation without assuming we can read every colleague’s motives. In this narrative the hostile purpose is stated. In an ordinary workplace, irritation with a request is not evidence of a plot. We have to examine what is being asked, what facts support it, and whether the proposed conversation can accomplish anything responsible. That examination protects both our time and the people we might otherwise dismiss unfairly.

The rest of the chapter makes the issue sharper. Another attempt uses a false prophetic warning to lure Nehemiah into a compromising act. He refuses, brings the opposition before God, and the wall is completed. The surrounding nations recognize God’s help in the work. Those details prevent us from reducing the passage to the power of personal determination. Nehemiah’s opponents wanted fear to make him abandon responsibility or violate it. His faithfulness involved dependence on God and limits on what he would do to protect himself. A project does not become sacred merely because its leader feels strongly about it. We cannot borrow Nehemiah’s confidence while discarding his accountability to the God whose people he served. The outcome gives us reason to honor God’s help, not permission to promise that every firm refusal will produce a successful project.

Paul gives Christians a wider principle for making these judgments. In Ephesians 5 he teaches believers how to live in the light, with love, wisdom, and dependence on the Spirit. Within that setting he writes, “Make the most of every opportunity in these evil days.” (Ephesians 5:16, NLT). This is instruction about faithful living, not a command to maximize the number of tasks completed before dinner. An opportunity can require concentrated work. It can also require listening to someone who has been hurt. Wisdom asks what faithfulness requires here, with these people and these responsibilities. A calendar packed with activity may reveal very little about that question. The Christian leader’s aim is to spend attention in ways consistent with Christ, including when doing so costs approval, convenience, or the pleasure of having the last word.

That is why yesterday’s consideration of internal harm matters beside today’s passage. A complaint about exploitation is not a distraction simply because it arrives near a deadline. A team member identifying a broken promise may be helping you recover the purpose of the work. Focus becomes dangerous when the leader treats every challenge as interference. Before declining a difficult conversation, ask whether it contains a fact that could change your decision, a harm you are responsible to address, or an obligation you have left unmet. Invite someone who can disagree with you to examine your answer. The counsel described in The Decision Fortress should make us more accountable, not provide another way to certify our preferences. Your conscience deserves attention, but it does not turn your first interpretation of a colleague’s motives into a revelation from God.

Imagine a team preparing to hand over a system its customers depend on. The testing lead raises an unresolved failure that could prevent customers from using it. At the same time, another stakeholder requests a fourth discussion of a naming decision already approved, without identifying new evidence or a decision that needs to change. These requests should receive different treatment. The testing concern deserves a prompt hearing because it bears directly on the responsibility being carried. The naming discussion can begin with a request for the specific unresolved issue in writing. If there is a real problem, address it. If there is no new issue, explain the decision and return to the handover. This is a hypothetical example, but the distinction is practical: protect room for information that matters while refusing to let repetition alone establish priority. The goal is a sound decision, not the satisfaction of winning a contest over access to you.

A useful standing order is to require a clear purpose before reopening a settled decision. You might say, “Please send the new information and the decision you need from me. I will review it before we schedule another meeting.” That response leaves a door open to correction and puts a reasonable boundary around the process. It also gives you a test you can apply when your pride wants to say no or your anxiety wants to say yes. If a claim is false, correct it plainly for the people who need the truth. If a concern is valid, repair what needs repair. You do not have to answer every allegation through the process preferred by the person making it. You do have to remain truthful, accessible through appropriate channels, and willing to reconsider when the evidence changes.

Protecting an assignment also means knowing where it ends. The Work Gate in The Watchman’s Protocol for Men challenges the habit of turning professional achievement into identity. Today’s passage cannot serve as an excuse to neglect family, avoid rest, or make a team permanently available. A leader who invokes important work to justify every late night may be refusing a different responsibility altogether. Ask God to expose that confusion before you congratulate yourself on your focus. The work can matter deeply without becoming the measure of your worth. A faithful boundary might protect an afternoon needed to finish a customer commitment. It might also protect the evening you already promised your family. Neither decision becomes wise merely because it is forceful. Each needs an honest account of what you owe and whom you are serving.

Before Monday’s meetings begin, choose one invitation you feel pressured to accept and write down the purpose it would serve. Name the responsibility it would advance, the decision it could change, and the cost of taking attention away from what is already entrusted to you. If those answers reveal necessary correction, make room for it. If they reveal a repeated conversation with no responsible next step, decline courteously and state how new information can reach you. Then use the recovered time for the work or person you said needed it. That last action keeps focus honest. Tomorrow, Stand and Rebuild turns to what remains after the wall is finished: trustworthy people and continued stewardship. Today, practice the boundary that allows you to carry your present responsibility without becoming unavailable to truth.

Leadership Challenge

Which meeting are you accepting out of pressure rather than responsibility? Identify its purpose, check whether it contains necessary correction, and set one boundary that preserves both focus and accountability.

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

That moment creates a difficult leadership choice. The leader can protect momentum, postpone the conversation, and promise to address the strain after the launch. The leader can also stop long enough to listen, examine the problem, and repair what is happening inside the team. Nehemiah chose the second path, even while Jerusalem’s wall remained unfinished.

The crisis in Nehemiah 5 did not come from the enemies outside the city. It came from people within the community who raised serious complaints about the burden they were carrying. Nehemiah listened, became angry, thought carefully, confronted the leaders involved, and required a concrete remedy. His response begins this way:

“When I heard their complaints, I was very angry. After thinking it over, I spoke out against these nobles and officials. I told them, ‘You are hurting your own relatives by charging interest when they borrow money!’ Then I called a public meeting to deal with the problem.” (Nehemiah 5:6-7, NLT)

Later, Nehemiah required action rather than a vague expression of concern:

“You must restore their fields, vineyards, olive groves, and homes to them this very day. And repay the interest you charged when you lent them money, grain, new wine, and olive oil.” They replied, “We will give back everything and demand nothing more from the people. We will do as you say.” Then I called the priests and made the nobles and officials swear to do what they had promised. (Nehemiah 5:11-12, NLT)

This passage belongs to Israel’s covenant life after exile. Nehemiah was governing a community with responsibilities and relationships that do not map directly onto a modern company. We should not turn every action in the chapter into a management technique. The leadership principle is still clear and consistent with the wider witness of Scripture: visible progress does not excuse preventable harm inside the community entrusted to a leader’s care.

Yesterday, Nehemiah taught the people to keep building while guarding against an external threat. Today, he shows that vigilance must face inward too. A leader can watch the horizon, answer critics, protect the strategy, and still miss the strain spreading through the team. Walls do not protect a community if the people inside them cannot trust one another.

Nehemiah’s response offers four movements worth noticing. He listened. He slowed his anger long enough to think. He named the problem publicly. He required measurable repair. Each movement matters because leaders often skip the one that feels least natural.

Listening came first. Nehemiah did not dismiss the complaints as a distraction from the mission. He did not ask the people to wait until the wall was complete. Their concerns became part of the work because the people were not expendable inputs in a construction plan. They were the community the wall was meant to serve.

This is where modern leaders can become confused by their own metrics. A delivery date is visible. Team fatigue is harder to measure. Revenue appears in a report. A growing reluctance to speak honestly often does not. Leaders naturally defend what they can count, especially when the finish line is close. Healthy leadership makes room for information that arrives through conversation rather than a dashboard.

Anger came next, but Nehemiah did not let anger make the decision for him. The text says, “After thinking it over.” That phrase is easy to pass by, yet it holds the difference between moral clarity and impulsive reaction. He allowed the complaint to matter, then considered how to respond before he confronted anyone. His anger signaled that something was wrong. Reflection shaped that signal into responsible action.

Leaders need both. Indifference can make us tolerate conditions we should address. Unexamined anger can make us accuse people before we understand the facts. Nehemiah neither ignored the concern nor exploded without thought. He listened, felt the weight of it, and considered his response.

Naming the problem followed. Nehemiah did not hide the issue inside a private note that protected everyone from discomfort while protecting no one from recurrence. He addressed the leaders responsible and then brought the matter before the community. Public accountability made sense because the consequences were public. The repair had to be visible enough to restore confidence.

Not every workplace concern belongs in a public meeting. Confidentiality, dignity, and fair process matter. The principle is not that leaders should announce every failure. The principle is that the scope of accountability should match the scope of the impact. A private misunderstanding may need a private conversation. A team-wide practice that has damaged trust usually needs a team-wide acknowledgment of what will change.

Concrete repair completed the response. Nehemiah did not stop at, “We hear you.” He identified what had to be restored, set a clear expectation, and secured a commitment. The people could tell whether the promise had been kept. This is what separates concern from leadership. Concern feels bad about a problem. Leadership accepts responsibility for the next faithful action.

A modern repair may look different. It might mean resetting an impossible deadline, returning authority that was quietly taken from a team, correcting an uneven workload, or changing a meeting culture that punishes honest disagreement. It may require a leader to say, “I approved this approach, and I did not see what it was costing you. Here is what changes now.” Specific repair builds trust because people no longer have to guess whether their concern mattered. The goal is not symbolic concern. The goal is a healthier way to continue the work together.

The hardest time to make that correction is when the project is going well. Poor results force a review. Visible success gives harmful patterns a place to hide. A leader can convince himself that the pressure is temporary, the tension is normal, and the people will recover once the milestone passes. Sometimes a short demanding season is necessary. Repeatedly spending people to protect a schedule is not a sustainable leadership model.

Nehemiah refused to define success as a completed wall alone. The wall mattered, but the community inside it mattered more. His assignment was not simply to stack stone. He was helping restore a people. Stopping to address internal strain did not interrupt the mission. It protected the reason the mission existed.

Take one practical step this week. Ask your team a question that the normal status report cannot answer: “What is making this work harder than it needs to be, and what part of that is within our control?” Listen without defending the plan. Think before promising a solution. Name what you can responsibly name. Then choose one repair people can see.

Tomorrow, Nehemiah will face invitations designed to pull him away from the work. His answer will be focus. Today establishes what focus is not. Focus is not the refusal to hear anything uncomfortable. Faithful focus protects the assignment by caring for the people entrusted with it.

Leadership Challenge: What concern inside your team have you postponed because visible progress made it easier to wait? What specific repair can you begin this week to show that the people carrying the mission matter as much as the milestone?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

Nehemiah found a third way, and he built it into the hands of every worker on the wall. Each laborer held a tool in one hand and a weapon in the other. The work continued. The guard never dropped. He called it neither retreat nor war. He called it the way you finish something worth finishing when people want it to fail.

By the middle of Nehemiah 4, Jerusalem’s wall stood at half its height, and that progress is exactly what provoked the crisis. Here is how Nehemiah describes the response he organized:

“Then as I looked over the situation, I called together the nobles and the rest of the people and said to them, ‘Don’t be afraid of the enemy! Remember the Lord, who is great and glorious, and fight for your brothers, your sons, your daughters, your wives, and your homes!’ When our enemies heard that we knew of their plans and that God had frustrated them, we all returned to our work on the wall. But from then on, only half my men worked while the other half stood guard with spears, shields, bows, and coats of mail. The leaders stationed themselves behind the people of Judah who were building the wall. The laborers carried on their work with one hand supporting their load and one hand holding a weapon. All the builders had a sword belted to their side. The trumpeter stayed with me to sound the alarm.” (Nehemiah 4:14-18, NLT)

The threat was not imaginary. Sanballat, Tobiah, and their allies had watched the gaps in the wall close, and they plotted a coordinated attack on the workers. The people were exhausted. The rubble was heavy, the enemy was loud, and fear moved through the camp faster than any spear. Nehemiah had two problems at once. He had a wall to finish and an attack to survive, and he could not solve one by ignoring the other.

His first move had already set the pattern. When the threats began, Nehemiah wrote, “But we prayed to our God and guarded the city day and night to protect ourselves” (Nehemiah 4:9, NLT). Notice the shape of that sentence. Prayer and a posted guard, in the same breath, with no sense that one made the other unnecessary. He did not pray instead of guarding. He did not guard instead of praying. He did both, because he believed God would protect the city and he still put watchmen on the wall.

This is the discipline the passage teaches, and it is easy to name and hard to hold: integrated vigilance. Protect the mission without abandoning the mission. The trowel stays in one hand. The sword hangs at the side. Neither one replaces the other, and neither one gets dropped when the pressure rises.

Two failure modes wait on either side of this discipline. The first is the leader who becomes all sword. Every criticism gets a response. Every rumor gets a meeting. Every threat becomes the new priority until the opposition, not the assignment, is running the calendar. That leader feels busy and even brave, but the wall stops rising. The enemy does not have to defeat a mission he can persuade you to abandon. Permanent combativeness is not vigilance. It is a slow surrender disguised as a fight.

The second failure mode is the leader who becomes all trowel. This leader hears the threat and decides that acknowledging it would look weak or faithless. The head goes down, the work continues, and the guard never gets posted. Denial wears the costume of focus. Then the attack lands on an undefended wall, and the people who trusted the leader pay for the pretending.

Nehemiah held both hands open. He told the people the truth about the danger, then anchored them in something larger than the danger. “Don’t be afraid of the enemy,” he said. “Remember the Lord, who is great and glorious.” He named the threat and named God in the same speech. Only after that did he reorganize the work, stationing half the people as guards while the other half kept building. Fear got honest treatment, not denial and not panic.

That reorganization cost him something real, and the text does not hide it. Only half his men worked the wall from that day forward. Integrated vigilance is slower than full production. A team that has to watch the horizon builds less than a team that can give everything to the task. Nehemiah accepted a slower wall because a finished wall built by a slaughtered crew was no victory at all. Leaders who refuse to pay the cost of protection usually pay a higher one later.

Underneath the practical arrangement sat a conviction the whole month has been building. Solomon put it plainly in the wisdom of the Psalms: “Unless the Lord builds a house, the work of the builders is wasted. Unless the Lord protects a city, guarding it with sentries will do no good” (Psalm 127:1, NLT). That verse names both halves of Nehemiah’s day, the building and the guarding, and places God underneath each one. This is wisdom literature, a general truth about how life works rather than a promise that removes human effort. Nehemiah still built. He still posted the guard. He simply refused to believe the outcome rested on his tools and his weapons alone.

Bring this into a normal week. Every leader eventually runs a project under threat. A competitor targets your best account. A reorganization threatens the team you have built. A campaign of criticism, sometimes fair and sometimes not, starts to circle the work you are trying to finish. The two ancient temptations show up on schedule. You can turn every day into a war room, answering critics until the actual work stalls. You can also decide the threat is beneath your attention and keep shipping until it blindsides you.

Integrated vigilance asks for both hands. Name the threat honestly, first to God and then to the people who are counting on you, the way Nehemiah did before he changed a single work assignment. Then post a real guard. The guard might be a documented decision trail, a communication plan, a trusted ally who watches the flank while you keep your hands on the work. Put it in place, and then return to building. Do not let the opposition set your agenda. A guard that runs in the background protects the mission. A guard that becomes the mission has already handed the enemy the win.

Yesterday’s article watched Nehemiah hand every family a section of the wall, turning one leader’s burden into a whole people’s work. Today that shared work comes under fire, and the same leader shows how to defend it without deserting it. Tomorrow the story turns to a harder threat. The gravest danger to the wall was not the army outside. It was the injustice inside, where the people building the wall together were exploiting one another. A leader can guard the perimeter perfectly and still lose the city to what is happening within it.

Here is the concrete move for this week. Find the one threat you are handling badly, and diagnose which hand is failing. If you are all sword, spending your energy fighting the opposition while the work stalls, sheathe it, post a reasonable guard, and get back to the wall. If you are all trowel, pretending the threat will pass while your team waits for someone to name it, pick up the sword and post the guard you have been avoiding. In either case, do the thing Nehemiah did before he did anything else. Remember the Lord, who is great and glorious, and get back to work.

Leadership Challenge: Think of the one threat you are currently handling badly. Are you all sword, letting the fight against it consume the work you were supposed to protect, or all trowel, pretending it will pass while your team waits for you to name it? What is the one guard you need to post this week so you can get both hands back on the wall?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

Here is how the work begins.

Then Eliashib the high priest and the other priests started to rebuild at the Sheep Gate. They dedicated it and set up its doors, building the wall as far as the Tower of the Hundred, which they dedicated, and the Tower of Hananel. People from the town of Jericho worked next to them, and beyond them was Zaccur son of Imri. The Fish Gate was built by the sons of Hassenaah. They laid the beams, set up its doors, and installed its bolts and bars. Meremoth son of Uriah and grandson of Hakkoz repaired the next section of wall. Beside him were Meshullam son of Berekiah and grandson of Meshezabel, and then Zadok son of Baana. Next were the people from Tekoa, though their leaders refused to work with the construction supervisors. (Nehemiah 3:1-5, NLT)

Read the whole chapter aloud and a rhythm emerges. Next to them. Beyond them. Beside him. Next. After him. The phrase repeats more than thirty times, section after section, name after name, all the way around the city. It is the least quotable chapter in the book and one of the most instructive.

By this point the hard front-end work is done. The king had granted safe passage and timber. The people had answered Nehemiah’s honest appeal with a single sentence: “Yes, let’s rebuild the wall!” (Nehemiah 2:18, NLT). Enthusiasm, though, does not lay stone. A crowd that agrees to build is not yet a workforce that knows what to do. Between the yes and the finished wall stood a management problem: how does one man turn a shared burden into a thousand specific tasks?

Nehemiah could not build the wall himself. No leader carries a city-sized assignment alone. Generations earlier, Moses learned the same limit when his father-in-law watched him try to judge every dispute in Israel single-handed and warned him plainly:

“You’re going to wear yourself out—and the people, too. This job is too heavy a burden for you to handle all by yourself.” (Exodus 18:18, NLT)

Nehemiah’s answer to that limit fills chapter 3. He did not clone himself or work faster. He divided the wall into sections and gave each one a name.

This is the principle hidden in the dull list: shared ownership requires clearly defined sections. The wall did not rise because Nehemiah delivered an inspiring speech. It rose because every family knew exactly which stretch of stone was theirs to repair. The priests took the Sheep Gate. The sons of Hassenaah took the Fish Gate. The people of Jericho worked one length, Meremoth worked the next, Meshullam the next after that. No section belonged to everyone, which is another way of saying no section belonged to no one. Clarity is what turned a willing crowd into a working city.

Look closer at who built where, and a second pattern appears. Many people repaired the section of wall nearest their own homes.

Above the Horse Gate, the priests repaired the wall. Each one repaired the section immediately across from his own house. (Nehemiah 3:28, NLT)

The same note repeats for Zadok, for Shemaiah, for Meshullam: each rebuilt the wall across from where he lived. There is wisdom in that arrangement. A man who repairs the wall protecting his own family works with a care no hired laborer can match. Nehemiah did not assign sections at random. Where he could, he placed people where they already held a stake, where the finished work would guard something they loved. Faithful leaders look for that overlap between a person’s assignment and a person’s investment, because ownership is strongest when the work protects something that matters to the one doing it.

Notice, too, who is holding the tools. The high priest starts the work. Goldsmiths and perfume-makers and merchants take their turns on the wall. These were not day laborers. They were people of standing who could have supervised from a distance and instead set their own hands on the stone. Nehemiah 3 is a portrait of leaders who work, not merely leaders who assign. The section a leader is unwilling to touch is a section the team quietly learns it can neglect.

The chapter is honest about the exception. In the middle of the roll call comes a quiet sting: the people of Tekoa built their section, “though their leaders refused to work with the construction supervisors” (Nehemiah 3:5, NLT). Their nobles would not stoop to the labor. The detail is left there without comment, a permanent record that some who should have led would not lift a stone. What is striking is what happened anyway. The common people of Tekoa built their assigned length, then went back and repaired a second section that others had left undone (Nehemiah 3:27). The wall rose through the willing. A leader cannot force the unwilling to own their part, but a clear assignment means their refusal is visible, and the work does not have to stop because a few withhold their hands.

The pattern in the rubble matches a pattern Paul later described for the church. He wrote about how a healthy body actually works:

He makes the whole body fit together perfectly. As each part does its own special work, it helps the other parts grow, so that the whole body is healthy and growing and full of love. (Ephesians 4:16, NLT)

Its own special work. That is the engine of both a wall and a team. Growth and completion come not from a few heroic builders doing everything but from each part doing the specific thing it was given. The leader’s task is to make sure every part knows what its part is.

This is where most leaders lose the wall. The vision is cast, the room says yes, and then the work gets handed to “the team” rather than to a person. A task owned by everyone is a task owned by no one. The report nobody finishes, the account nobody calls, the broken process nobody fixes: trace it back and you will usually find a section of wall that was never assigned to a name. Clarity is not micromanagement. It is the difference between a crowd that agrees and a workforce that builds. This week, take the initiative you care about most and ask a blunt question of every piece of it: whose section is this? If you cannot name the person, the wall is not being built there, no matter how many people agreed it should be.

Nehemiah carried the burden alone in chapter 1. He wept alone, prayed alone, and inspected the ruins alone at night. By chapter 3 the burden has a hundred names attached to it, each one bent over a defined length of wall. That is the movement faithful leadership makes. The weight begins with the leader, but the work belongs to the people, and it belongs to them because the leader took the trouble to divide it, define it, and hand it over. A leader is not the one who builds the whole wall. A leader is the one who makes sure every stretch of it has a name beside it.

Tomorrow the work meets its first real resistance. Sanballat and his allies will move from mockery to the threat of violence, and Nehemiah will have to teach the same builders to hold a tool in one hand and a weapon in the other. A divided wall is a beginning. Defending it is the next test.

Leadership Challenge: Take the initiative you care about most right now and walk it piece by piece. Which section of that work is currently owned by “the team” instead of a named person? Name the one part that has no name beside it, and assign it this week before you announce anything new.

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

What happens in the next breath is one of the most compressed leadership moments in Scripture.

The king asked, “Well, how can I help you?” With a prayer to the God of heaven, I replied, “If it please the king, and if you are pleased with me, your servant, send me to Judah to rebuild the city where my ancestors are buried.” (Nehemiah 2:4-5, NLT)

Give that sequence a moment before mining it. The king asks how he can help. Nehemiah prays. Then Nehemiah speaks. Two verbs, one after the other, under the highest pressure of his life.

The order is the lesson. Nehemiah prayed, and then he made a specific request. He did not choose one over the other. He did not pray as a substitute for preparing, and he did not prepare a request as a substitute for praying. He did both, in sequence, in seconds. Prayer and preparation are partners, not competitors. The leader who believes he must pick between depending on God and doing the hard work of getting ready has misread how faithful leadership actually functions.

Notice how short the prayer was. Nehemiah calls it a prayer to the God of heaven, offered in the half-second between the king’s question and his own answer. A prayer that brief only works when it grows from prayer that was long. Four months earlier, in the month of Kislev, Nehemiah had already wept, fasted, and prayed over this exact request. His prayer then ended with a plea:

O Lord, please hear my prayer! Listen to the prayers of those of us who delight in honoring you. Please grant me success today by making the king favorable to me. Put it into his heart to be kind to me. (Nehemiah 1:11, NLT)

The arrow prayer in the throne room was aimed by months of prayer in private. Between Kislev and Nisan, roughly four months passed. Nehemiah held the burden that long without forcing an opening, serving the king’s wine day after day and waiting for a door only God could open. The waiting was not idleness. It was the slow work of letting a plan mature and a heart stay ready. Yesterday we watched the ruin of Jerusalem break his heart. Today we see what that grief had been doing the whole time. It had been teaching him to pray before it taught him to plan.

When the king opened the door, Nehemiah walked through it with a defined request, not a vague hope. He named the outcome he wanted, which was permission to go and rebuild. Then he kept going. He asked for letters guaranteeing safe passage through the provinces west of the Euphrates, and he asked for timber from the king’s own forest to rebuild the gates, the walls, and a house for himself. He had thought through the supply chain before the conversation began. Nehemiah credits the result to God without pretending he showed up empty-handed: the king granted the requests, “because the gracious hand of God was on me” (Nehemiah 2:8, NLT). Faith did not make his ask fuzzy. It made him ready with a specific one.

With royal approval in hand, Nehemiah could have arrived in Jerusalem and immediately called an assembly. A lesser leader, fresh off a win with the king, would have. Instead he waited.

I slipped out during the night, taking only a few others with me. I had not told anyone about the plans God had put in my heart for Jerusalem.(Nehemiah 2:12, NLT)

He surveyed the broken walls at night, quietly, before he described them to anyone. He wanted to see the damage with his own eyes rather than build a plan on a secondhand report. Jesus later named this discipline directly:

“But don’t begin until you count the cost. For who would begin construction of a building without first calculating the cost to see if there is enough money to finish it?” (Luke 14:28, NLT)

A leader who builds on someone else’s summary inherits someone else’s blind spots. Nehemiah refused to announce a vision he had not yet verified. He walked the rubble, measured the ruin, and let the true condition of the ground correct any picture he had carried from a thousand miles away.

Only after praying, asking, and inspecting did Nehemiah gather the people and call them to build.

But now I said to them, “You know very well what trouble we are in. Jerusalem lies in ruins, and its gates have been destroyed by fire. Let us rebuild the wall of Jerusalem and end this disgrace!” (Nehemiah 2:17, NLT)

Observe what he did not do. He did not open with his credentials or wave the king’s endorsement as leverage. He told them the truth about their shared trouble, then he grounded the invitation in what God had already done: “Then I told them about how the gracious hand of God had been on me” (Nehemiah 2:18, NLT). The response was immediate. They said, “Yes, let’s rebuild the wall!” and started the good work.

Most leaders know this sequence and reverse it anyway. The reflex under pressure is to speak first. Announce the initiative Monday morning, rally the room, then sort out the prayer, the plan, and the real state of the ground later. The wall rarely rises that way. Excitement without inspection collapses at the first obstacle nobody surveyed. A plan without prayer runs on the leader’s own strength until that strength runs out. Both failures feel like decisiveness in the moment. Both leave the people holding an assignment their leader never fully counted.

Nehemiah’s model is slower and sturdier. Pray over the burden until it becomes more God’s assignment than your ambition. Prepare the request until it is specific enough to grant. Walk the actual ground before you describe it to the people you are asking to work. Speak last, when you have something true and tested to say. The delay is not indecision. It is the difference between a leader who moves a room for an afternoon and a leader who finishes a wall.

The cupbearer had four months of prayer, one sentence to the king, one quiet night among the ruins, and one honest speech to a discouraged people. None of it was rushed, and none of it was passive. That is the shape of faithful leadership when the assignment is larger than the leader. Tomorrow we will watch Nehemiah hand out sections of the wall, turning his private burden into a whole city’s shared work. He could give the people their sections only because he had already done the hidden work first.

Leadership Challenge: What is the initiative you are about to announce, and have you actually walked its ground yet? Before your next big ask or launch, name the one thing you have been describing from a secondhand report, and go see it for yourself this week.

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

We are pivoting this month. These past two weeks we followed Elijah, the prophet who stood against a king and called down fire. Now we meet a cupbearer in a foreign palace who wept before he ever made a request of a king. Two different men, two different assignments, the same dependence on God. Elijah’s courage was public and confrontational. Nehemiah’s begins in private grief.

Nehemiah served as cupbearer to Artaxerxes, king of Persia, hundreds of miles from Jerusalem. It was a position of trust and access, comfortable and secure. When his brother arrived from Judah, Nehemiah did not ask for good news. He asked for the truth.

They said to me, “Things are not going well for those who returned to the province of Judah. They are in great trouble and disgrace. The wall of Jerusalem has been torn down, and the gates have been destroyed by fire.” (Nehemiah 1:3, NLT)

His response was not a strategy session.

When I heard this, I sat down and wept. In fact, for days I mourned, fasted, and prayed to the God of heaven. (Nehemiah 1:4, NLT)

Only after days of grief did Nehemiah pray, and his prayer reveals where his hope actually rested.

Then I said, “O Lord, God of heaven, the great and awesome God who keeps his covenant of unfailing love with those who love him and obey his commands, listen to my prayer! Look down and see me praying night and day for your people Israel. I confess that we have sinned against you. Yes, even my own family and I have sinned!” (Nehemiah 1:5-6, NLT)

He rehearsed God’s promise to Moses, that a scattered people who returned would be gathered again. Then he ended with a specific and risky request.

“O Lord, please hear my prayer! Listen to the prayers of those of us who delight in honoring you. Please grant me success today by making the king favorable to me. Put it into his heart to be kind to me.” In those days I was the king’s cup-bearer. (Nehemiah 1:11, NLT)

Notice what Nehemiah owned. The wall was not his fault. He did not tear it down, and he had likely never lived inside it. This was roughly 445 BC, decades after the first exiles returned from Babylon. Nehemiah could have received the report, felt a passing sadness, and gone back to filling the king’s cup. Instead he took a burden that belonged to no one in particular and let it become his own. He confessed a national sin as though it were personal, because he understood that leadership sometimes means carrying grief you did not create.

Here is the principle, drawn from the narrative rather than commanded by it: the burden comes before the vision statement. Faithful plans begin when a leader is willing to feel the true condition of the people and place it before God. Nehemiah’s weeping was not a technique to manufacture, and this passage is not a call to perform sorrow so others can watch. The point is subtler. Nehemiah did not insulate himself from the truth, and he refused to treat that truth as merely a problem to be solved before lunch. He let it land. He let it break his heart, and the breaking came before the building.

Most leaders are trained to move from information to action without pausing to feel the weight of what the information means. That reflex is often good. A leader who dissolves into grief at every setback cannot function. Sometimes, though, the rush to a plan is a way of avoiding the cost. It is easier to assign action items than to sit with the reality that people are hurting, that trust is broken, that something real has been lost. The whiteboard becomes a place to hide.

Two moves follow from Nehemiah’s example. The first is to ask for the honest report. Nehemiah asked, and the people told him the truth because he wanted it. Many leaders never hear the real condition of their team because they have made honesty expensive. If the last three updates you received were all encouraging, consider the possibility that you are not hearing the truth. You may be hearing what people have learned you can tolerate. Nehemiah’s brother told him the wall was down and the gates were burned. Nobody softened it. Somewhere in your organization, a person knows the wall is down and is waiting to see whether you actually want to know.

The second move is to let the report land before you fix it. Before the plan, sit with the actual condition of the people you lead. The attrition number is a list of names. The missed deadline is a team that is exhausted. Paul told the church in Rome to “weep with those who weep” (Romans 12:15, NLT), and that instruction is not a detour from the work of leadership. It is part of it. A leader who has genuinely felt the ruin will build differently than one who only measured it.

This is where honesty about difficulty matters. Grief that never becomes a plan is its own failure. Nehemiah wept, and then he acted. He did not stay under the weight forever, paralyzed by the size of the problem. Two weeks ago we watched Elijah collapse under a broom tree and ask to die, and God met him with sleep, food, and a next assignment. The lesson there was not that leaders should stay in despair. The lesson here is the mirror image: the plan that forms in the presence of God, out of a heart that has actually felt the loss, is a different plan than the one scribbled in the first ten minutes. One is built on real ground. The other is built on the leader’s need to look decisive.

Nehemiah’s prayer did not stay a prayer. It ended with a concrete ask, that God would make the king favorable to him. The grief became a request, and tomorrow the request becomes a plan and an inspection. Watch the sequence, because the sequence is the whole point. He felt the ruin, he confessed, he prayed, and only then did he turn toward the king. He did not reverse the order. He did not lead with the ask and pray about it later.

The leaders we remember for building something rarely started with the blueprint. They started by refusing to look away from what was broken until it had cost them something. Nehemiah’s wall would eventually rise in fifty-two days, but the wall began here, in a palace far from home, with a man who heard the worst and let it break his heart before he lifted a single stone.

Leadership Challenge: What honest report have you avoided asking for because you already suspect it will hurt? This week, ask the one person most likely to tell you the true condition of your team, and before you reach for a plan, sit with the answer long enough to actually feel it.

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

The story begins the moment Elijah comes down from Horeb. Yesterday we watched God meet the exhausted prophet in a gentle whisper and hand him a new assignment that included three names to anoint. The last of those names was his own replacement. Elijah walked off the mountain of despair carrying instructions to raise up the man who would take his place.

So Elijah went and found Elisha son of Shaphat plowing a field. There were twelve teams of oxen in the field, and Elisha was plowing with the twelfth team. Elijah went over to him and threw his cloak across his shoulders and then walked away. Elisha left the oxen standing there, ran after Elijah, and said to him, “First let me go and kiss my father and mother good-bye, and then I will go with you!” Elijah replied, “Go on back, but think about what I have done to you.” So Elisha returned to his oxen and slaughtered them. He used the wood from the plow to build a fire to roast their flesh. He passed around the meat to the townspeople, and they all ate. Then he went with Elijah as his assistant. (1 Kings 19:19-21, NLT)

Consider what the scene refuses to make dramatic. There is no fire from heaven here, no showdown with false prophets, no royal audience. There is a man in a field behind twelve teams of oxen, which tells us Elisha was prosperous and had plenty to lose. Elijah walks over, drops his cloak across the younger man’s shoulders, and keeps walking. The cloak is the mantle, the visible sign of the prophetic office. A tired prophet identifies his successor and begins the handoff before he has any idea how much time he has left.

Elisha’s response is worth watching. He asks to say goodbye to his parents, then he goes back and slaughters the very oxen he was plowing with and burns the equipment to cook them. He does not keep the farm as a fallback. He burns the plow so there is nothing to return to, feeds the town, and follows Elijah as his assistant. The word translated assistant is the language of apprenticeship. Elisha does not start by parting rivers. He starts by serving, watching, and learning under a leader who will not always be there.

Here is the principle the day is built on. Leadership that outlives the leader requires two things at once, and most leaders are tempted to pick only one. It requires moral courage in the present, the willingness to keep telling the truth while you still hold the office. It also requires the deliberate preparation of the person who will carry the work after you are gone. Elijah did both. He confronted a king, he raised a successor, and he understood that the mantle on his shoulders was never his property to keep.

Look first at the courage. Calling Elisha did not send Elijah into a quiet retirement. Two chapters later God sends him back into the hardest room he knows, the presence of King Ahab, this time over a murder dressed up as a real estate transaction. Ahab had wanted Naboth’s vineyard, Naboth had refused to sell his family inheritance, and Jezebel had arranged to have him killed on false charges so the king could take the land.

Give him this message: “This is what the Lord says: Wasn’t it enough that you killed Naboth? Must you rob him, too? Because you have done this, dogs will lick your blood at the very place where they licked the blood of Naboth!” “So, my enemy, you have found me!” Ahab exclaimed to Elijah. “Yes,” Elijah answered, “I have come because you have sold yourself to what is evil in the Lord’s sight.” (1 Kings 21:19-20, NLT)

Ahab greets him as an enemy, which is exactly what a truth-teller becomes to a leader who has sold himself to what is wrong. Elijah does not soften the message to protect what little influence he has left. He names the theft and the blood. This is legacy work too, though it does not look like it. A leader who spends his final seasons managing his reputation and avoiding costly rooms leaves his successor a diminished office. Elijah handed Elisha a mantle that still meant something, because he never stopped using it for its purpose.

Then comes the release. Years later the two men walk together toward the Jordan, and Elijah knows he is about to be taken.

When they came to the other side, Elijah said to Elisha, “Tell me what I can do for you before I am taken away.” And Elisha replied, “Please let me inherit a double share of your spirit and become your successor.” “You have asked a difficult thing,” Elijah replied. “If you see me when I am taken from you, then you will get your request. But if not, then you won’t.” (2 Kings 2:9-10, NLT)

Notice what Elijah does not do. Elisha asks for a double portion of his spirit, and Elijah does not pretend the gift is his to hand out. He calls it a difficult thing and places the outcome entirely in God’s hands. The mantle was never Elijah’s possession. He wore it on assignment. The power behind it belonged to God, and the succession would be God’s to grant. A leader who believes the anointing is his own will cling to it. A leader who knows it was only ever on loan can let it go.

What follows is one of the strangest scenes in Scripture, and I will not tame it into a tidy management lesson. A chariot of fire and horses of fire come between them, and Elijah is carried into heaven by a whirlwind. Elisha cries out, tears his clothes, and then does the one thing that matters for everything after.

Elisha picked up Elijah’s cloak, which had fallen when he was taken up. Then Elisha returned to the bank of the Jordan River. He struck the water with Elijah’s cloak and cried out, “Where is the Lord, the God of Elijah?” Then the river divided, and Elisha went across. (2 Kings 2:13-14, NLT)

The cloak that started in a field is now on the ground, fallen from a leader who is gone. Elisha picks it up and asks the only question that matters. Not where is Elijah, but where is the God of Elijah. The mantle was never the point. The God behind the mantle was. When the river parts a second time, the watching prophets say the spirit of Elijah now rests on Elisha, and they bow. The office continued because the leader prepared someone to carry it and then got out of the way.

Paul says the same thing to Timothy in plainer language, and last month’s series lived inside that relationship.

You have heard me teach things that have been confirmed by many reliable witnesses. Now teach these truths to other trustworthy people who will be able to pass them on to others. (2 Timothy 2:2, NLT)

Four generations sit inside that one verse. Paul, Timothy, the trustworthy people, and the others they will teach. The measure of Paul’s leadership was never the size of his own platform. It was whether the truth kept moving after he was gone. That is the test the whole month has been circling. Faithfulness, not visible success, is the real measure, and faithfulness includes what you leave in someone else’s hands.

Land this where you actually lead. The hardest part of succession is not choosing the person. It is releasing the control. Most leaders will happily mentor someone as long as the final decision, the real authority, and the visible credit stay with them. That is not raising a successor. That is keeping an assistant. Elijah threw the cloak and walked away. He let Elisha follow, watch, and eventually ask for more than Elijah could give.

Ask the uncomfortable questions. If you were taken out of your role tomorrow, who picks up the cloak? Can you name the person, or have you avoided naming anyone because being irreplaceable feels like security? Have you handed that person real weight, actual decisions with actual consequences, or only the tasks you did not want? Are you still using your own influence for its purpose in the present, or have you slipped into protecting a reputation instead of telling the truth?

This closes the first half of the month. Across two weeks we have followed Elijah from a hidden brook to a public mountain, through collapse and a whisper, and now to a cloak passed into younger hands. Tomorrow the series changes leaders entirely. We leave the solitary prophet and meet a cupbearer named Nehemiah, who hears that a city lies in ruins and weeps before he ever picks up a tool. Elijah’s assignment was to stand, confront, and then release. Nehemiah’s assignment will be to rebuild. Different callings, different tones, the same dependence on the same God.

Elijah’s greatest act of leadership may not have been the fire on Carmel or the confrontation with Ahab. It may have been a quiet moment in a field, dropping a cloak on a plowing farmer and trusting God to make it fit. The leaders we remember longest are not the ones who held on the tightest. They are the ones who did their work with courage, named the person who would come next, and then let the mantle fall from their shoulders into stronger and younger hands. What you build with your own hands ends when you do. What you hand to someone else can outlive you by a generation.

Leadership Challenge: If you were pulled out of your role tomorrow, who is ready to pick up the cloak, and be honest about whether you have actually handed that person real authority or only kept them close as an assistant? What is the one decision, relationship, or piece of visible credit you could release to them this week to begin a handoff instead of guarding an office you will not hold forever?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

Before public authority comes private formation. Following his initial stand, Elijah is sent east to Kerith Brook, dependent on ravens for food and a ravine for water. When the brook dries up, he learns to release a temporary method without confusing the provision with the Provider. Moving into Gentile territory at Zarephath, Elijah relies on a destitute widow whose dwindling flour and oil are supernaturally sustained. When her son dies soon after, Elijah demonstrates leadership that stays for the crisis. He refuses to protect his image or offer shallow slogans, carrying the child’s body upstairs to lay the tragedy directly before God until life returns.

On Mount Carmel, the narrative reaches its watershed moment as Elijah challenges Israel’s divided allegiance between God and Baal. Before praying for fire, he repairs the torn-down altar of the Lord, showing that structural repair must precede new initiatives. His prayer seeks God’s identity and the people’s return rather than personal status. Public victory and persistent prayer yield torrential rain, yet Elijah soon collapses under a broom tree in deep exhaustion after a death threat from Jezebel.

In this place of depletion, God meets human frailty not with immediate correction, but with physical care through food, water, and rest. Journeying to Mount Horeb, Elijah encounters God not in the dramatic windstorm, earthquake, or fire, but in a gentle whisper. God dismantles Elijah’s isolating distortion that he is the only faithful leader left by revealing 7,000 who have not bowed to Baal. Elijah then receives his next concrete assignment, which includes anointing leaders and raising up his successor. Ultimate endurance in leadership relies on quiet dependence, truthful correction, and preparing others to carry the work forward.

Subscribe now

Share Christian Leadership by Justin Wilson

There he came to a cave, where he spent the night. But the Lord said to him, “What are you doing here, Elijah?” Elijah replied, “I have zealously served the Lord God Almighty. But the people of Israel have broken their covenant with you, torn down your altars, and killed every one of your prophets. I am the only one left, and now they are trying to kill me, too.” “Go out and stand before me on the mountain,” the Lord told him. And as Elijah stood there, the Lord passed by, and a mighty windstorm hit the mountain. It was such a terrible blast that the rocks were torn loose, but the Lord was not in the wind. After the wind there was an earthquake, but the Lord was not in the earthquake. And after the earthquake there was a fire, but the Lord was not in the fire. And after the fire there was the sound of a gentle whisper. When Elijah heard it, he wrapped his face in his cloak and went out and stood at the entrance of the cave. And a voice said, “What are you doing here, Elijah?” He replied again, “I have zealously served the Lord God Almighty. But the people of Israel have broken their covenant with you, torn down your altars, and killed every one of your prophets. I am the only one left, and now they are trying to kill me, too.” Then the Lord told him, “Go back the same way you came, and travel to the wilderness of Damascus. When you arrive there, anoint Hazael to be king of Aram. Then anoint Jehu grandson of Nimshi to be king of Israel, and anoint Elisha son of Shaphat from the town of Abel-meholah to replace you as my prophet. Anyone who escapes from Hazael will be killed by Jehu, and those who escape Jehu will be killed by Elisha! Yet I will preserve 7,000 others in Israel who have never bowed down to Baal or kissed him!” (1 Kings 19:9-18, NLT)

Elijah has walked forty days to reach the same mountain where God once met Moses, and the first thing God does is ask a question He already knows the answer to. “What are you doing here, Elijah?” The question is not a trap. It is an invitation to say out loud what the running and the despair have been saying all along. Yesterday we watched God meet an exhausted prophet with sleep, bread, water, and presence under the broom tree. Today we follow him to Horeb, where care gives way to conversation, correction, and a new assignment. The sequence matters. God fed him first. God does not leave him fed and directionless.

The setting is loaded with meaning. Horeb is Sinai, the mountain of the covenant, where Israel first received the Law. Elijah arrives alone, hides in a cave, and answers God’s question with a speech that is equal parts truth and distortion. He has served zealously. That part is true. Israel has broken covenant and killed the prophets. Also true. Then comes the distortion: “I am the only one left.” A hundred prophets were hidden by Obadiah two chapters earlier, a detail we covered on the seventh. Elijah knows better, but exhaustion and isolation have collapsed his vision down to a single point. Me, alone, hunted. Fear does that. It narrows the field until a leader cannot see anyone else still standing.

What happens next is easy to misread. God tells Elijah to stand on the mountain, and a windstorm tears the rocks loose, an earthquake shakes the ground, and a fire passes by. The text is careful each time to say the Lord was not in the wind, not in the earthquake, not in the fire. After the spectacle comes the sound of a gentle whisper. I want to resist the tidy sermon that God always speaks in whispers and never in power. This is the same God who answered by fire on Carmel one chapter earlier. The point is not that quiet is holier than loud. The point is that on this mountain, in this moment, the display was not where God had chosen to deliver His word. Elijah had to be quiet enough to hear it.

Here is the detail I keep returning to. God asks the same question after the whisper that He asked before the windstorm, and Elijah gives the exact same answer, word for word. The earthquake did not change his mind. The fire did not reorient him. He walked out of the cave saying precisely what he said walking in. I am the only one left. Spectacle did not heal his distortion. What finally moved him was not a bigger display. It was a specific word carrying specific instructions, and a correction he could not manufacture on his own.

This is the principle worth carrying into the week. God’s word to a depleted, isolated leader is rarely more noise. It is direction and truth. When a leader finally tells God the honest version, that he is exhausted, that he feels alone, that he has had enough, the faithful next step is seldom another dramatic event. It is quiet enough to hear a real word, honest enough to receive correction, and concrete enough to act on the next assignment.

The prophet Isaiah put this into a single line, though he spoke it as an indictment rather than a comfort. “Only in returning to me and resting in me will you be saved. In quietness and confidence is your strength.” (Isaiah 30:15, NLT) Isaiah was rebuking a nation that wanted alliances and armies instead of trust in God, and the verse ends with the people refusing the very rest He offered. I cannot flatten it into a slogan about slowing down. It does tell me that strength for God’s people has always been located in quiet dependence rather than in the loudest option available. A leader addicted to spectacle will keep staging bigger events and keep hearing nothing.

God then corrects the distortion directly. Elijah is not the only one. “Yet I will preserve 7,000 others in Israel who have never bowed down to Baal or kissed him.” The number is a rebuke to the loneliness Elijah has been nursing. Paul reaches back for this exact scene when he writes to the Romans about the faithful remnant. He recalls Elijah’s complaint, “Lord, they have killed your prophets and torn down your altars. I am the only one left, and now they are trying to kill me, too,” and God’s answer, “No, I have 7,000 others who have never bowed down to Baal!” Then Paul draws the point forward: “It is the same today, for a few of the people of Israel have remained faithful because of God’s grace” (Romans 11:3-5, NLT). The faithful are preserved by grace, not by the leader’s heroic solitude. Elijah felt alone. He was factually wrong.

Picture a leader coming off the season we described yesterday. The crisis is contained or the launch shipped, everyone called it a win, and now she is convinced the whole thing rests on her and only her. She cannot name a single person who could carry her load. So she stages another all-hands, another late-night push, another visible act of leadership, and none of it touches the thing underneath. What she needs is not another event. She needs an hour of genuine quiet away from the noise, a trusted person who will tell her the truth, and someone to say plainly that she is not the only one who can do this. The belief that “I am the only one” feels like clear-eyed realism. Usually it is exhaustion editing the facts.

I would ask the depleted leader to name the distortion out loud, because it loses power once it is spoken. No one else understands this. It all falls apart without me. There is nobody I can hand this to. Then I would test each claim against reality the way God tested Elijah’s. Is it true that no one else has been faithful here? Name the seven thousand. Who has quietly kept the standard when nobody was watching? Who has carried weight without credit? The leader who cannot see them is not seeing clearly, and clear sight tends to return in the quiet rather than in the next big meeting.

God does not end the encounter with comfort. He ends it with work. Go back the way you came. Anoint Hazael. Anoint Jehu. Anoint Elisha to replace you as prophet. The recommissioning includes naming a successor, which means the assignment God gives an exhausted leader includes preparing the person who will carry the work after him. That is where we go tomorrow, when Elijah casts his cloak over Elisha and begins the handoff that outlives him. Today it is enough to see that God’s answer to despair was a specific direction, a truthful correction, and a name to raise up. Direction, not more noise.

Elijah went up the mountain bracing for God in the earthquake and came down carrying a whispered assignment and the knowledge that seven thousand others had never bent the knee. The spectacle he expected was not where God was working. The quiet he did not seek was where he finally heard. Leaders running on fumes rarely need another performance from themselves. They need to get quiet enough to hear a real word, honest enough to let it correct the story they have been telling, and willing enough to act on the next concrete step, including naming the people who will carry what they were never meant to carry forever.

Leadership Challenge: What distortion has your exhaustion been telling you: that you are the only one who can carry this, that no one else has stayed faithful, that it all falls apart without you? Where will you build enough quiet this week to test that story against the truth, and who is the one person you will name as capable of carrying part of what you have been carrying alone?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

When Ahab got home, he told Jezebel everything Elijah had done, including the way he had killed all the prophets of Baal. So Jezebel sent this message to Elijah: “May the gods strike me and even kill me if by this time tomorrow I have not killed you just as you killed them.” Elijah was afraid and fled for his life. He went to Beersheba, a town in Judah, and he left his servant there. Then he went on alone into the wilderness, traveling all day. He sat down under a solitary broom tree and prayed that he might die. “I have had enough, Lord,” he said. “Take my life, for I am no better than my ancestors who have already died.” Then he lay down and slept under the broom tree. But as he was sleeping, an angel touched him and told him, “Get up and eat!” He looked around and there beside his head was some bread baked on hot stones and a jar of water! So he ate and drank and lay down again. Then the angel of the Lord came again and touched him and said, “Get up and eat some more, or the journey ahead will be too much for you.” So he got up and ate and drank, and the food gave him enough strength to travel forty days and forty nights to Mount Sinai, the mountain of God. (1 Kings 19:1-8, NLT)

The prophet who stood before Ahab, watched fire fall, prayed for rain, and ran to Jezreel is now asking God to let him die. Scripture places those scenes beside each other without protecting Elijah’s reputation. Yesterday, we followed his persistence after the public victory. Today, a threat from Jezebel sends him running for his life. I need the honesty of this sequence. Courage in one moment does not make a leader immune to fear in the next. A visible answer to prayer does not erase exhaustion. Collapse after sustained pressure does not prove the earlier faithfulness was fake. Elijah is neither a flawless hero nor a cautionary tale about weak resolve. He is a servant of God whose limits have become impossible to ignore.

The setting keeps me from making this into a tidy lesson about taking a day off. Ahab reports Elijah’s actions on Carmel, including the killing of Baal’s prophets, and Jezebel answers with a credible death threat. That violent judgment belongs to Israel’s covenant crisis and Elijah’s prophetic office; it is not a leadership technique for modern conflict. Elijah crosses into Judah, leaves his servant in Beersheba, and continues into the wilderness alone. By the time he reaches the broom tree, fear has narrowed into isolation and despair. The text tells us what he says, but it does not give me enough information to assign him a modern clinical diagnosis. It gives me more than enough reason to take his words seriously. A man who asks to die does not need a motivational speech about everything he accomplished yesterday.

God’s first recorded response is not a rebuke, a new strategy, or a reminder of the fire on Carmel. Elijah sleeps. An angel touches him, directs him to bread and water, and lets him sleep again. The care comes twice. The angel even names the physical reality: the journey ahead will be too much for him without food. God will question Elijah, correct his belief that he is alone, and give him another assignment later in the chapter. None of that happens first. I see a leadership principle here without pretending every exhausted person needs the same sequence: human limits are not spiritual failure. Care can precede correction. Rest can come before the next decision. Receiving help can be part of faithfulness rather than evidence that faith has failed.

David’s praise in Psalm 103 gives this pattern a teaching foundation beyond Elijah’s story: “The Lord is like a father to his children, tender and compassionate to those who fear him. For he knows how weak we are; he remembers we are only dust.” (Psalm 103:13-14, NLT) The psalm celebrates God’s mercy toward His covenant people. It does not promise that food and sleep will resolve every form of despair, nor does it make fragility the whole truth about a person. It tells me that God knows our weakness and responds with compassion. I often reverse that order in leadership. I notice a limit, label it a lack of commitment, and offer care only after the person proves worthy of it. The psalm will not let me call contempt for human weakness a sign of spiritual seriousness.

Picture a director who has led a team through a cyber incident for three days. She has managed executive calls, customer updates, technical handoffs, and an investigation while sleeping in fragments. The immediate threat is contained, and everyone tells her she saved the week. Later, a colleague finds her alone in a conference room saying she does not care whether she wakes up tomorrow. I would not ask her to finish the incident report before seeking help. I would ask directly whether she is in immediate danger, stay with her, and involve trusted personal and professional support. Emergency or crisis services belong in the response when safety is uncertain. A statement about wanting to die is not material for a coaching exercise. The person matters more than the leader’s desire to keep the operation looking stable.

Not every exhausted leader is facing an immediate safety crisis, but ordinary depletion still deserves an honest response. I would not answer a trembling hand, repeated confusion, or three nights without meaningful sleep with praise for dedication. I would create a handoff for the next critical decisions, cancel what can wait, make sure the person can get home safely, and name when we will reconnect. Food, sleep, medical care, counseling, prayer, and lighter workload are not interchangeable cures. Each may belong in a responsible plan. The broom tree does not give me a formula. It challenges the reflex to demand insight, productivity, or spiritual composure from a person whose present need is care.

Paul makes mutual responsibility concrete when he writes, “Share each other’s burdens, and in this way obey the law of Christ.” (Galatians 6:2, NLT) He is writing to a church about gentle restoration and life together, not prescribing a corporate leave policy. The principle still confronts the culture I create around leadership. Burden sharing must take operational form if it is going to mean anything on Tuesday afternoon. Someone needs authority to run the meeting, access to the necessary information, and permission to make a decision without waiting for the depleted leader to approve every detail. A team that celebrates only the leader who never stops will eventually teach honest people to hide what the work is costing them.

Receiving that help can feel harder than offering it. I may believe my presence protects everyone while ignoring the errors my exhaustion is creating. I may call myself indispensable when I am afraid the team will discover it can function without me. Elijah’s story does not praise isolation. God meets him in it, provides what he needs for the next stretch, and later sends him toward people and work he cannot complete alone. Anyone still exploring faith can practice the same humane leadership without pretending to share Elijah’s convictions: take despair seriously, protect the person before the schedule, and build enough depth that one exhausted employee can step away. The Christian reader sees something further. Dependence on God includes accepting that I am made of dust and may need another person to carry part of the load.

Today, I would identify one person whose recent output has hidden the cost of producing it. I would ask what can come off that person’s shoulders for the next forty-eight hours, then make one concrete handoff before offering advice. If that person is me, I would tell one trusted person the unedited truth and release one responsibility with enough information for someone else to carry it. If words about death or immediate danger are present, the next move is direct safety support, not another work conversation. Tomorrow, we will follow Elijah to the quiet voice and the next assignment. The God who recommissions him is the same God who first lets him sleep under a tree. I do not need to rush a depleted leader past the place where God chose to meet His servant with bread, water, touch, and time.

Leadership Challenge: Whose strong performance may be hiding serious depletion right now, including your own? What responsibility will you remove or hand off in the next forty-eight hours so honest care can begin before the next demand arrives?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

Then Elijah said to Ahab, “Go get something to eat and drink, for I hear a mighty rainstorm coming!” So Ahab went to eat and drink. But Elijah climbed to the top of Mount Carmel and bowed low to the ground and prayed with his face between his knees. Then he said to his servant, “Go and look out toward the sea.” The servant went and looked, then returned to Elijah and said, “I didn’t see anything.” Seven times Elijah told him to go and look. Finally the seventh time, his servant told him, “I saw a little cloud about the size of a man’s hand rising from the sea.” Then Elijah shouted, “Hurry to Ahab and tell him, ‘Climb into your chariot and go back home. If you don’t hurry, the rain will stop you!’” And soon the sky was black with clouds. A heavy wind brought a terrific rainstorm, and Ahab left quickly for Jezreel. Then the Lord gave special strength to Elijah. He tucked his cloak into his belt and ran ahead of Ahab’s chariot all the way to the entrance of Jezreel. (1 Kings 18:41-46, NLT)

The fire has fallen, but the fields are still dry. Elijah leaves the public confrontation and bends toward the ground to pray. I find that transition harder to absorb than the dramatic answer beside the altar. Yesterday, we considered a prayer aimed at God’s honor and the people’s return rather than the leader’s reputation. Today, the same prophet stays dependent after receiving an unmistakable answer. The extraordinary moment does not finish the work. Israel still needs rain. The people who watched the sacrifice burn still face a land damaged by drought. A public win can change what everyone says about a leader without changing everything the people need. Elijah does not confuse the two.

The rain belongs to a promise God made before the confrontation began. The chapter opens, “Later on, in the third year of the drought, the Lord said to Elijah, ‘Go and present yourself to King Ahab. Tell him that I will soon send rain!’” (1 Kings 18:1, NLT) Elijah is not choosing a preferred forecast and trying to pray it into existence. God has spoken. The drought and its ending belong to the Lord’s dealings with Israel, whose king and people have turned toward Baal. This is a question of covenant allegiance, the people’s relationship with the God they have abandoned, not a lesson in producing favorable weather. I need that context before borrowing Elijah’s confidence for my own plans. His certainty rests on God’s word, not on the strength of his desire.

Within that setting, his posture matters. The man who has stood before a king now bows low with his face between his knees. His servant looks toward the sea and returns without evidence of rain. Elijah sends him back. The text records seven trips, not seven precisely worded prayers or a method for making God answer. It gives no transcript of Elijah’s prayer here. I should not invent one or turn the number into a formula. What remains plain is the persistence: the lack of a visible change does not end his dependence. The principle reaches beyond this particular mountain. A visible answer to prayer does not make continued prayer unnecessary. Receiving help yesterday is a reason to return to God today, not a credential that makes me self-sufficient.

James makes the connection explicit for ordinary believers. Writing about prayer amid hardship, sickness, and the shared life of the church, he says, “Elijah was as human as we are, and yet when he prayed earnestly that no rain would fall, none fell for three and a half years! Then, when he prayed again, the sky sent down rain and the earth began to yield its crops.” (James 5:17-18, NLT) James draws attention to Elijah’s humanity, not his membership in an unreachable class of spiritual experts. Prayer matters because God acts, not because the person praying has become superhuman. I cannot reduce this to positive thinking or a calming exercise. James describes an answer with consequences for the earth and its harvest. His encouragement invites believers to pray, not to calculate how many requests will compel the answer they want.

That distinction protects people when I bring this passage into leadership. A budget approval is not God’s promise of rain. A successful launch does not establish that every next step has His endorsement. I can pray earnestly for a struggling department without telling its staff that the desired outcome is guaranteed. Consider a hypothetical operations director whose team receives funding to repair a customer service backlog. The presentation succeeds. Executives approve temporary staff, and the director thanks everyone for the hard work. Two weeks later, customers are still waiting. Training has taken longer than expected, and experienced employees are spending much of their time helping new colleagues. The announcement was a real win. It was not the same thing as relief for the people still opening unanswered requests each morning.

At the next review, an analyst says the waiting time has not improved. This is where I would want the director to protect the report rather than protect the celebration. Ask what the numbers show, which requests carry the most risk, and where the new arrangement is failing. Thank the analyst for telling the truth. Elijah’s servant reports what he sees; the narrative does not describe him manufacturing an encouraging answer to satisfy the prophet. I would not turn their exchange into a complete management model, but it exposes a temptation I recognize. Once I have announced progress, I can start treating accurate bad news as disloyalty. A team then learns to supply little clouds on demand. Continued prayer should leave me more willing to face the facts, not more demanding that other people validate my confidence.

The director needs a repeatable response, not another victory speech. I would set one short review for the following week, assign someone to examine the oldest unresolved cases, and decide who can adjust training or coverage before then. Alongside that work, I would return privately to a specific request: “God, help us see what is hurting people. Give us wisdom to respond, and keep me from defending a plan that needs correction.” That is my proposed prayer, not a quotation from Elijah. Returning to it is not empty repetition if the need remains real. The words give the unfinished work a place before God while the review gives it accountable attention. Neither substitutes for the other. The next report may still be discouraging, but the people affected should not have to wait for my enthusiasm to recover before receiving help.

Persistence also needs an honest boundary. A leader can keep praying while changing the plan, ending an ineffective program, or admitting that an assumption was wrong. Elijah has a particular promise about rain. I ordinarily have incomplete information, a responsibility to people, and a proposal that deserves examination. Calling every delay a test of faith can make correction almost impossible. If the temporary staffing arrangement increases errors or exhausts the team, the director should act on that evidence rather than demand another round of sacrifice. A faithful prayer might ask for courage to stop what the leader once celebrated. Anyone still exploring faith can practice this distinction without pretending to pray: remain committed to the people and the underlying responsibility while holding the method open to correction. Belief should never become a condition for an employee’s report to be heard.

When the small cloud finally appears, Elijah does not stay folded over on the mountain. He sends a warning to Ahab, and the narrative moves into wind, rain, and travel. Waiting has not made him unavailable for action. I also notice where the passage puts the credit for his run to Jezreel: the Lord gives him special strength. This is not a recommendation to push the body past its limits after every demanding day. The next chapter will make the limits of this same man impossible to ignore. Today’s rain is real, and tomorrow’s distress will be real. A leader needs room for both truths. Prayerful endurance is not the ability to remain at the intensity of a public victory indefinitely. It includes responding when the situation changes and receiving help rather than claiming to be beyond needing it.

Today, I would choose one responsibility that slipped out of attention after its successful announcement. Write down what remains unresolved, return to God with that specific need, and put a time on the calendar to hear an unvarnished report from the person closest to it. Keep the appointment even if there is nothing impressive to share. This is our next step in Stand and Rebuild: dependence that continues after recognition arrives. Tomorrow, in The Leader Under the Broom Tree, we will stay with Elijah when persistence gives way to exhaustion and despair. Today I want to remain on this mountain long enough to notice who still needs rain. The people living with the unfinished work need more than my memory of a successful day. They need a leader willing to pray again and hear what has not changed.

Leadership Challenge: Which responsibility have you neglected since its successful announcement, and when will you return to it in prayer and hear an honest progress report from the person closest to the unfinished work?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

At the usual time for offering the evening sacrifice, Elijah the prophet walked up to the altar and prayed, “O Lord, God of Abraham, Isaac, and Jacob, prove today that you are God in Israel and that I am your servant. Prove that I have done all this at your command. O Lord, answer me! Answer me so these people will know that you, O Lord, are God and that you have brought them back to yourself.” Immediately the fire of the Lord flashed down from heaven and burned up the young bull, the wood, the stones, and the dust. It even licked up all the water in the trench! And when all the people saw it, they fell face down on the ground and cried out, “The Lord—he is God! Yes, the Lord is God!” (1 Kings 18:36-39, NLT)

The crowd falls on its face, but nobody chants Elijah’s name. The answer to his prayer makes the Lord unmistakable. I want to notice that destination before making this passage a lesson about getting prayers answered. Yesterday, we stayed beside the altar Elijah repaired. Today, the wood and offering are ready, water fills the trench, and the prophet steps forward. Hours of calling on Baal have produced no answer. Elijah addresses the God of Abraham, Isaac, and Jacob, placing this moment inside Israel’s relationship with the God who called its ancestors. This is a confrontation over worship, not a contest between two leadership brands. The people have divided their allegiance. Elijah asks for an answer that will bring them back to the Lord, not gather them around a more impressive version of himself.

There is a complication worth keeping. Elijah does ask God to establish that he is God’s servant and has acted at God’s command. I cannot honestly read the prayer as though his credibility never enters it. His prophetic authority matters because the people need to know whether his message comes from the Lord. The distinction is what that credibility serves. Elijah does not ask to become indispensable, escape every future criticism, or enjoy watching his opponents admit defeat. The prayer moves toward God’s identity and the people’s return. Its final concern reaches beyond the prophet’s reputation. That gives me the principle I need: ask for the truth to become clear in service of God and the people, rather than making their recognition of my rightness the purpose of the answer. Credibility can serve the assignment without becoming the assignment.

I need that distinction when I pray about a disputed decision. Asking God for help is not automatically the same as surrendering my preferred result. I can want the problem solved and want everyone to remember who predicted it. I can want a colleague to recover and want the recovery to establish how much that colleague needs me. Those desires can occupy the same prayer without announcing their differences. The question is what I would accept as a good answer. Would I welcome a solution that helps the people involved but gives someone else the credit? Would I receive correction if the truth exposes a mistake in my own reasoning? A prayer that makes the leader smaller does not ask for humiliation. It releases the demand that every good outcome also improve the leader’s standing.

Paul gives this direction a clear teaching foundation beyond Elijah’s particular assignment. Writing to the Corinthians about his ministry, he says, “You see, we don’t go around preaching about ourselves. We preach that Jesus Christ is Lord, and we ourselves are your servants for Jesus’ sake.” (2 Corinthians 4:5, NLT) The surrounding passage rejects deception and distortion of God’s word. Paul identifies Christ as the message and himself as a servant, not the attraction around which everything must turn. He is describing gospel ministry, not writing a corporate mission statement. Still, the principle directly challenges a Christian leader’s appetite for becoming the center. If my faith points to Jesus as Lord, I cannot use that faith to make loyalty to me the measure of another person’s integrity. Serving for His sake gives me a reason to help people who may never admire me.

Consider a hypothetical department head who warned that reducing support coverage would leave customers waiting. The executive team chose the reduction anyway. Now unresolved requests are piling up, and a major customer is threatening to leave. The department head has the earlier recommendation, complete with the date, ready for the emergency meeting. The warning was sound. The decision deserves review. The danger appears when the department head begins treating the customers’ frustration as useful evidence in a personal appeal. I would not tell this leader to bury the record or pretend every decision was equally reasonable. I would ask what the meeting needs to accomplish first. Customers need responses, exhausted staff need relief, and the people authorizing resources need an accurate picture. None of those needs requires a speech designed to make the executive team feel foolish.

The department head can enter with two distinct responsibilities: stabilize the work and establish an honest record. The immediate request might be temporary coverage, a named owner for urgent cases, and a deadline for contacting affected customers. The earlier warning belongs in the review of how the decision happened, not as a weapon attached to every request for help. I would put a date on that review so humility does not become an excuse for avoiding accountability. A leader who repeatedly ignores evidence should face appropriate scrutiny. The department head can explain the facts without withholding assistance until someone offers an apology. Helping now does not erase what happened. It refuses to make other people’s continued difficulty the price of getting the recognition the leader deserves.

Before that meeting, I would write a private prayer short enough to expose what I am asking: “God, help me tell the truth without using these people to prove myself. Give us wisdom to protect the customers and the staff. Correct what I cannot see, including anything I have contributed to this problem.” Those words are not a method for controlling the room. They give my motives somewhere honest to stand before I speak. Then I would change one observable part of my preparation. Put the current harm and the proposed response before the slide documenting the old disagreement. Ask a colleague to check whether the proposed fix addresses the need or mainly restores my influence. Prayer belongs with evidence, preparation, and correction. It does not replace them, and nobody attending the meeting needs to hear the private prayer for it to shape my conduct.

If you are exploring faith, the practical question remains available without pretending to share my convictions: can you work for a good outcome that does not increase your status? A team should not have to adopt a leader’s religion to receive fair treatment. The Christian reader has a further responsibility here. Claiming God as the source of our work should make us more careful about the authority we claim for our preferences. Elijah identifies himself as acting at God’s command. I cannot borrow that sentence to declare my staffing proposal beyond challenge. A strong business case is still a business case, open to examination. Invoking divine backing where I have professional judgment makes disagreement spiritually dangerous for the people around me. The prayer that reduces self-importance should leave more room for honest questions, not less.

Carmel also refuses to become a promise that this approach will produce a visible rescue. God sends fire in this particular confrontation over Israel’s worship. The passage does not authorize me to stage a test and require Him to vindicate my plan. A company may still lose the account. A truthful leader may still face an unfair review. Wanting God’s honor does not turn prayer into leverage over Him. Neither does making the leader smaller mean allowing false accusations or unsafe conditions to continue. I can document harm, challenge a damaging decision, or seek independent review without making revenge my purpose. The distinction will not always feel clean. When motives remain mixed, I can admit that before God and choose the next action that protects people rather than waiting until I feel perfectly generous.

This afternoon, take the decision you most want others to admit you were right about. Name the person who needs something from you before that admission arrives. Offer one concrete piece of help without attaching a demand for recognition, while keeping any necessary accountability process intact. That is today’s work in Stand and Rebuild: courage that serves a purpose larger than the courageous person’s reputation. Tomorrow, Elijah returns to prayer for rain, where an extraordinary public answer gives way to repeated waiting. Later, Nehemiah will bring prayer into requests, plans, and shared work. Today I am listening to what the people say when the fire falls. Their confession names the Lord. I want my leadership to leave people better able to see the truth and receive the help they need, even when my name becomes a smaller part of the story.

Leadership Challenge: Whom will you help today before they acknowledge you were right, and what specific action can you take without making recognition the price of that help?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

Then Elijah called to the people, “Come over here!” They all crowded around him as he repaired the altar of the Lord that had been torn down. (1 Kings 18:30, NLT)

Before there is fire, there is a broken altar in front of a watching crowd. Elijah stops to repair it. I want to pay attention to that work because the dramatic answer can make the stones seem like scenery. Yesterday’s passage confronted Israel’s divided allegiance. Today’s passage, 1 Kings 18:30-32, brings that confrontation down to something Elijah can put his hands on. The prophets of Baal have spent hours calling for an answer that has not come. Elijah gathers the people near the Lord’s damaged altar. His next action is neither another argument nor a stronger appeal for excitement. In summary, the following verses describe him taking twelve stones, representing Israel’s tribes, rebuilding in the Lord’s name, and digging a trench around the altar. The gathering will witness something extraordinary. First, it witnesses repair. A neglected place of worship cannot remain background rubble while everyone waits for God to act.

The stones belong to a story older than Elijah. Israel’s covenant is the relationship God established with His people, calling them to belong to Him and worship Him alone. Under Ahab, that allegiance has been compromised by Baal worship. The twelve stones point to the whole people God named and claimed, even amid the kingdom’s division. Elijah does not assemble a monument to his own courage. He restores an altar to the Lord. I need to distinguish the text’s claim from the language I might bring to it: this altar has been torn down, not merely left untidy by people with crowded calendars. The passage does not name the person who destroyed it. It does place the ruin within a public confrontation over abandoned faithfulness. Calling this a lesson about maintaining better habits would be too small. The deeper question is whom the people belong to, and whether their worship will reflect that allegiance again.

That distinction changes the leadership principle I draw. Before asking people to invest in a new initiative, examine the faithfulness the next initiative assumes. Is it actually there? A team cannot build honest collaboration on a promise of safety its leader keeps breaking. A ministry cannot treat neglected care as an unfortunate detail while celebrating a larger attendance goal. Those are applications, not hidden meanings of the twelve stones. My organization is not covenant Israel, my strategic plan is not God’s word, and my employees do not owe me religious allegiance. The passage challenges my responsibility before it gives me anything to ask of them. I also test the application against Jesus’ teaching. In paraphrase, Matthew 5:23-24 directs a worshiper to seek reconciliation with an offended person rather than carry on with the offering as though the relationship does not matter. Worship cannot serve as a respectable cover for refusing the repair within my responsibility.

Consider a hypothetical ministry director preparing to recruit volunteers for a new outreach program. The plan addresses a genuine need. The budget is modest, and the launch date fits the calendar. Several dependable volunteers have stopped answering messages, though. During the previous program, the director repeatedly extended their shifts without asking. When one volunteer raised the problem, the director described the concern in a team meeting as a lack of commitment. Now the recruitment announcement promises a healthy, sustainable way to serve. The words sound reasonable. The people who carried the previous program have reason to doubt them. I would not begin by improving that announcement. I would begin with the gap between the director’s promise and the volunteer’s experience. A new program may deserve support, but it cannot erase the obligations left behind by the last one. Asking for fresh enthusiasm before acknowledging that history makes the wounded relationship someone else’s obstacle to overcome.

The repair starts with language specific enough to be checked. The director can ask for a conversation without making attendance a test of forgiveness. In that conversation, the director can name the extended shifts, acknowledge the public criticism, and withdraw the claim that raising a workload concern showed weak commitment. An apology should not carry a request to sign up for the new program at the end. That would make the conversation another recruitment tool. I would separate those decisions completely. The volunteer needs freedom to decline future involvement without the director treating that choice as evidence the apology failed. Public harm also requires an appropriate public correction. The director can tell the same team the earlier characterization was wrong without exposing private details from the conversation. Repair costs control over the account of what happened. The leader no longer gets to remain the reasonable person in every version of the story.

Words alone will not rebuild what repeated decisions damaged. The director needs an agreed end time for shifts, permission to refuse extensions, and another person who can receive concerns without routing every complaint through the leader involved. Those changes should exist before the next appeal for volunteers. I would ask someone affected by the old practice to review them, while making clear that person is not responsible for designing the entire solution. The purpose is to find what the director still cannot see. A week later, the meaningful evidence may be an ordinary decision: a volunteer leaves on time while an unfinished task remains. The director covers the gap or reduces the work instead of making the volunteer feel disloyal. Trust grows through evidence people can observe. Even then, it may return slowly. Some people may choose not to return at all. Faithfulness means honoring the correction without demanding a favorable response as payment.

My own worship belongs in this examination, too. A neglected prayer life is not identical to a damaged volunteer schedule, but both can expose what I have allowed urgency to displace. I can restore a time for prayer and Scripture without announcing a renewal campaign. I can tell God the truth about the approval I want and the conversation I fear. The danger is turning even this return into a bargain: I will become more disciplined so God will make the launch work. Carmel gives me no permission to negotiate that deal. In the chapter’s later prayer, Elijah identifies himself as God’s servant acting at God’s command. The Lord answers; Elijah does not activate Him. Repairing the altar is an act within that particular prophetic assignment, not a sequence any leader can repeat to secure a miracle. Worship acknowledges God’s worth and authority. It does not place Him under an obligation to reward my preparation with the outcome I prefer.

Christian hope also gives me a different starting point from earning my way back through improved performance. We come to God through Christ, receiving mercy we could not manufacture. Repentance means turning from the wrong, not accumulating enough repaired habits to purchase acceptance. That mercy makes an honest return possible. It does not make harmed people responsible for restoring my position or reputation. This matters wherever a leader has used spiritual language to avoid consequences. Serious misconduct can require safeguarding, independent investigation, or removal from leadership, not a private apology followed by a relaunch. Rebuilding trust cannot mean sending vulnerable people back into the same conditions with instructions to believe harder. If you are exploring faith, you do not have to adopt my beliefs to recognize the practical distinction. A leader who claims to have changed should welcome appropriate scrutiny. The Christian claim should deepen that accountability, never provide an exemption from it.

There is another temptation worth naming: postponing all useful work until every relationship feels repaired. That can become avoidance with a thoughtful explanation. Rebuild the altar first does not mean every initiative must wait for perfect trust or that urgent care should stop while a leader reflects. I would distinguish work that protects people now from expansion that depends on the trust I damaged. The director can continue serving current needs while delaying a recruitment push long enough to correct the volunteer arrangements. The repair needs a next action and a date, not an indefinite season of good intentions. This afternoon, open the plan for one initiative and name one existing commitment it relies on. Ask the person who bears its cost whether your conduct has honored it. Listen without defending the calendar. Then make one observable correction before asking that person for a larger commitment. Keep the correction even if the initiative never launches.

Tomorrow, Stand and Rebuild turns toward Elijah’s prayer and the request that makes the leader smaller. Today I am staying beside the damaged altar. Its repair directs attention toward the Lord to whom Israel belongs, not toward Elijah’s ability to produce a spectacle. Nehemiah will later help us consider the organization of shared work. This moment asks whether we are willing to address what new work can distract us from seeing. The answer may look like a corrected accusation, an honored boundary, or a return to prayer without an audience. None of those actions guarantees applause, restored influence, or fire from heaven. They leave room for a different kind of progress: a leader tells the truth, a person no longer carries the same preventable harm, and worship ceases to be an argument for getting our way. I can leave the outcome with God without leaving the broken commitment for someone else to repair.

Leadership Challenge: Before your next initiative asks more of people, which neglected commitment will you repair, and what observable change will the person affected be able to see this week?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

So Ahab summoned all the people of Israel and the prophets to Mount Carmel. Then Elijah stood in front of them and said, “How much longer will you waver, hobbling between two opinions? If the Lord is God, follow him! But if Baal is God, then follow him!” But the people were completely silent. (1 Kings 18:20-21, NLT)

The mountain is full of people, and nobody answers the question. Before there is fire on Carmel, there is a silence nobody can mistake for agreement. I want to stay in that silence before moving to the spectacle. Yesterday we followed Obadiah, the palace official who protected God’s prophets inside Ahab’s administration. Today Elijah stands before the gathered people, and the issue moves from hidden faithfulness to public allegiance. Ahab has already accused Elijah of causing Israel’s trouble. Elijah has answered that the king and his family abandoned the Lord’s commands and worshiped Baal. This is not a disagreement about presentation style. Israel belongs to the Lord by covenant, the relationship in which God has bound this people to Himself and called for their faithful obedience. The people are trying to live without settling whom they will follow. Elijah refuses to begin anywhere else.

The question exposes something more serious than ordinary indecision. Israel is not choosing between two reasonable plans for surviving a drought. The people are wavering between the Lord and Baal. Elijah does not present both as equally valid options. He brings their divided worship into the open and calls them to follow the true God. I can miss that distinction when I read this passage looking for a lesson about making faster decisions. Speed is not the point. A quick commitment to the wrong master would not solve their problem. Neither would a more inspiring leader who helped them feel united while leaving their divided allegiance untouched. The question is not whether they can agree on a tactic. It is whether they will obey the God to whom they belong. That comes before any discussion of what happens next on the mountain.

This is where I draw the leadership principle, carefully: when two loyalties demand contradictory conduct, a leader needs to name the conflict rather than ask people to keep satisfying both. That does not turn an office into ancient Israel. My team has no covenant obligation to treat my strategy as God’s command. Disagreeing with me is not the same as worshiping Baal. Elijah speaks as a prophet responding to God’s assignment, not as an executive borrowing religious authority to win an argument. The distinction protects everyone who works for a Christian leader. It also protects the passage from becoming an excuse for domination. The useful application begins with my own allegiance. What do I claim governs my decisions? What actually gets the final say when obeying that conviction threatens something I want to keep? A declaration costs little until another loyalty sends an invoice.

Consider a hypothetical operations director preparing a customer report. Her company promises accurate delivery forecasts. Her boss also expects every account to appear on schedule until a delay becomes impossible to hide. A project manager brings evidence that a shipment will miss its date. The director has enough information to tell the customer, but she asks the team to keep the report green until Friday’s executive review. She calls this giving the team time to recover. The project manager now has two instructions: communicate accurately and preserve the appearance of success. Both sound manageable until they require different answers in the same box. I do not need to assume the director enjoys deception. She may fear losing the account, damaging her reputation, or exposing people to an angry executive. Those pressures explain the temptation. They do not make the report accurate. Her silence about the conflict leaves the least powerful people to absorb it.

Jesus addresses competing allegiance directly in His teaching about money and possessions: “No one can serve two masters. For you will hate one and love the other; you will be devoted to one and despise the other. You cannot serve God and be enslaved to money.” (Matthew 6:24, NLT) His subject is not the inconvenience of having two supervisors. He is teaching about devotion, treasure, and trust in the Father. Money becomes a master when its demands govern obedience. I cannot reduce that warning to a clever management slogan about competing priorities. It asks whether financial security has gained the authority to overrule God. In the director’s situation, revenue is a legitimate concern. Preserving revenue by concealing a known delay gives that concern a different role. It becomes permission to abandon the truth. Jesus does not condemn responsible planning. He refuses the claim that I can give God my allegiance while reserving the decisive vote for money.

The director’s first task is therefore not a speech about the team’s courage. It is an honest account of the rule she has been enforcing. I would start with the instruction she gave: keep the report green despite the evidence. Naming that instruction matters more than announcing a new commitment to integrity. Her people already know the official commitment. They need to know which instruction survives when commitments collide. She can acknowledge that she asked them to present confidence the facts did not support. She can correct the report, identify what remains uncertain, and take responsibility for telling her boss why the status changed. None of that guarantees a grateful customer or a reasonable executive. She may lose something she hoped to protect. The point is not that truth creates a painless outcome. It is that the team no longer has to guess whether accuracy applies only when it is convenient for her.

I would also look at what happens after the correction. If the director tells people to report risks early and then punishes the first person who does, the old master still runs the room. A team learns from the person who loses an opportunity after bringing unwelcome information. It learns from the exception a leader makes for a profitable account. The director needs to protect honest reporting without suspending accountability for the delayed work. She can ask what caused the slip, who owns the recovery, and when the customer will receive another update. Those questions belong together. Accuracy does not excuse poor execution, and poor execution does not justify an inaccurate report. The correction becomes credible when she can hold both responsibilities without asking someone else to conceal one. That is harder than changing a color on a dashboard. It requires changing the decisions that taught people which color was safe.

There is a danger on the other side, too. A leader can call every complicated tradeoff a test of loyalty and stop listening. I want no part of that shortcut. Two honest people may disagree about an estimated delivery date. One may see evidence the other missed. Checking that evidence is not wavering between God and Baal. Neither is protecting confidential information or refusing to promise an outcome nobody can guarantee. The moral conflict begins when I know what the facts support and ask someone to represent something else. A useful question is whether I am gathering information that could change the decision or delaying a decision because I dislike its cost. The spiritually curious reader can ask that without pretending to share my faith. The Christian reader has a further reason to ask: loyalty to God should make me more accountable for my conduct, not less open to correction.

Carmel does not teach me to manufacture a dramatic moment to force agreement. In the chapter’s larger movement, God answers and turns attention back to Himself. Elijah is not the source of the fire, and the people’s allegiance is not a prize for his performance. This matters when I imagine the conversation waiting at work. I do not need a roomful of applause before correcting a false expectation. I do not need to humiliate the person who helped create it. I need to say what I know, name the instruction that contradicts it, and stop asking people to obey both. The crowd’s silence on the mountain leaves Elijah’s question unanswered; silence in a meeting should not become my evidence that everyone consents. People may need a safer way to tell me what my instructions have been costing them. I can begin by taking responsibility before asking them to speak.

This afternoon, take one active decision and write down the two expectations you cannot honestly satisfy together. Identify the person who currently pays for that contradiction. Then have the conversation that removes the false instruction, including your own part in giving it. That is today’s work in Stand and Rebuild as we begin Elijah’s week of courage, limits, and legacy. Tomorrow we return to Carmel and the broken altar Elijah repairs before he prays for fire. Later, Nehemiah will show us courage expressed through planning and shared work rather than a prophet’s public confrontation. Today I am staying with the unanswered question. I cannot promise the correction will preserve the account, the approval, or the opportunity. I can stop passing the cost of my divided loyalty down to the person filling out the report.

Leadership Challenge: Which instruction have you given that asks someone to protect your preferred outcome at the expense of the truth, and what will you say today to withdraw it and take responsibility for the cost?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

Three years into the drought, King Ahab did not send his palace administrator to find prophets. He sent him to find pasture. The horses still mattered. The mules still mattered. The God of Israel had shut the rain, and the court was managing livestock. Yesterday Elijah stayed in a Sidonian house with a dead child in his arms. Today the story moves inside Ahab’s system, to a man most leadership books skip on the way to Carmel. Later this month another palace official, Nehemiah, will weep over a broken wall. Today the official inside the palace is keeping prophets alive.

So Ahab summoned Obadiah, who was in charge of the palace. (Obadiah was a devoted follower of the Lord. Once when Jezebel had tried to kill all the Lord’s prophets, Obadiah had hidden 100 of them in two caves. He put fifty prophets in each cave and supplied them with food and water.) (1 Kings 18:3-4, NLT)

Let that sit. Obadiah runs the house of a king who has made Baal the official explanation for rain. Jezebel has been hunting the Lord’s prophets. The man with the keys has been running a second operation: two caves, fifty men each, food and water in a famine. “Devoted follower of the Lord” is not palace piety. It means he belonged to the God of Israel while drawing a paycheck from a court that did not. He used access, supply lines, and silence to keep a hundred people alive inside a system that wanted them gone. The text does not call him a coward for remaining in Ahab’s house. It calls him devoted. Then it shows you the cost.

Ahab splits the land with him to search for grass. Obadiah walks alone and meets Elijah, the man the king has been forcing other nations to swear they cannot find. Elijah’s instruction is simple. Go tell your master Elijah is here. Obadiah hears a death sentence.

“Oh, sir,” Obadiah protested, “what harm have I done to you that you are sending me to my death at the hands of Ahab? For I swear by the Lord your God that the king has searched every nation and kingdom on earth from end to end to find you. And each time he was told, ‘Elijah isn’t here,’ King Ahab forced the king of that nation to swear to the truth of his claim. And now you say, ‘Go and tell your master, “Elijah is here.”’ But as soon as I leave you, the Spirit of the Lord will carry you away to who knows where. When Ahab comes and cannot find you, he will kill me. Yet I have been a true servant of the Lord all my life. Has no one told you, my lord, about the time when Jezebel was trying to kill the Lord’s prophets? I hid 100 of them in two caves and supplied them with food and water. And now you say, ‘Go and tell your master, “Elijah is here.”’ Sir, if I do that, Ahab will certainly kill me.” (1 Kings 18:9-14, NLT)

Obadiah is afraid. The caves did not make him fearless. Hidden work does not cancel the knowledge of what Ahab does to people who fail him. He has served the Lord since youth, protected a hundred prophets, and still believes this errand will get him killed. Elijah does not shame him for the fear. He swears by the Lord in whose presence he stands that he will present himself that day. Then Obadiah goes.

But Elijah said, “I swear by the Lord Almighty, in whose presence I stand, that I will present myself to Ahab this very day.” So Obadiah went to tell Ahab that Elijah had come, and Ahab went out to meet Elijah. (1 Kings 18:15-16, NLT)

This is narrative, not a career path you copy. God preserved prophets through a palace official who feared Him more than he feared unemployment, and who still trembled when the public prophet asked him to walk back into the throne room. I will not bless every compromise as “faithful presence,” and I will not treat every quiet assignment as cowardice. The passage shows a third thing most rooms never count. God’s work required Elijah’s coming confrontation and Obadiah’s years of hidden protection. One man will stand on a mountain. The other kept a hundred people alive until that day arrived.

Here is the principle. Faithful leadership is not only the moment people can see. God uses public truth-tellers and people who serve Him inside difficult systems at real personal risk. Visibility is not the measure. Faithfulness is. Most of us would rather be remembered for fire than for food runs to a cave. Paul writes to workers in Colossae whose names would never carry the announcement: “Work willingly at whatever you do, as though you were working for the Lord rather than for people.” (Colossians 3:23, NLT) The true audience of Obadiah’s caves was not Ahab. It was the Lord. The writer of Hebrews says the same thing to tired believers who wondered whether unseen work counted: “For God is not unjust. He will not forget how hard you have worked for him and how you have shown your love to him by caring for other believers, as you still do.” (Hebrews 6:10, NLT) God does not forget the food carried to a cave. He does not require a mountain to notice it.

The failure mode is easy to name because I have run it. We treat the Carmel moment as the only real work. The all-hands speech. The public stand. The resignation letter that makes a story. Meanwhile the person who has been shielding a team, feeding a process, or telling the truth in rooms that never get minutes looks like a supporting character. Some leaders despise that assignment in themselves. They delay obedience until the work looks like Elijah. Other leaders hide behind “I am working from the inside” as a way to never risk anything Obadiah risked. Both misses are the same miss. They let visibility define faithfulness.

I have sat in organizations where the person who kept people standing was not the one on the keynote. A director who quietly moved a targeted employee off a vengeful executive’s radar. A plant manager who refused to fake a safety number and took the heat in a closed-door review so the floor did not have to. A chief of staff who absorbed a volatile leader without becoming the volatile leader. None of that will trend. All of it costs. If you follow Christ, the first question is not whether the work will be seen. It is whether the Lord is the one you are serving while you do it. If you are still exploring faith, the first question is still honest: who in your system is doing necessary work that your metrics cannot see, and have you treated that work as optional because it does not photograph?

Bring this to Tuesday afternoon. Name your assignment as it actually is this season. Are you being asked to stand in public, or to protect people inside a hard system without a stage? Write the name of one person whose faithfulness is invisible to the room that hands out credit. If that person is you, stop treating the caves as a waiting room for a better story. If that person reports to you, say the sentence this week that tells them you see it. Hidden work still has a cost. Obadiah still had to walk back to Ahab. The point is not that you stay forever in a place that is destroying you. The point is that you stop ranking the work God has given you by how many people will watch it.

This will not look like leadership to people who only measure fire. Caves look like delay. Palace administration looks like compromise until you count the hundred lives. Elijah is about to stand on Carmel and ask a nation how long it will waver between two opinions. That public question arrives tomorrow. It will matter more because men like Obadiah kept prophets alive while the drought did its work. Phase 1 of Stand and Rebuild closes here, in a dry valley, with a palace official nobody came to applaud. The month still builds toward the paid field guide at the end of September. Today’s piece of that work is simple and easy to skip. Do not despise the leader nobody sees. God already knows the caves.

Leadership Challenge: Who is doing necessary work in your system that never reaches the all-hands? If that person is you, what would you do differently this week if you stopped treating the hidden assignment as a lesser one? If that person reports to you, what specific sentence will you say that tells them you see it?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

The widow who fed a prophet through a drought is standing in her own house with a lifeless son and a charge against the man of God who lives upstairs. The flour did not fail. The oil did not fail. The child failed, and the woman who had begun to trust this God of Israel now has a corpse in her arms. Provision did not purchase immunity. The hidden house in Zarephath is about to test whether Elijah’s leadership was a successful season or a presence that stays when the season turns.

Some time later the woman’s son became sick. He grew worse and worse, and finally he died. Then she said to Elijah, “O man of God, what have you done to me? Have you come here to point out my sins and kill my son?”

But Elijah replied, “Give me your son.” And he took the child’s body from her arms, carried him up the stairs to the room where he was staying, and laid the body on his bed. Then Elijah cried out to the Lord, “O Lord my God, why have you brought tragedy to this widow who has opened her home to me, causing her son to die?”

And he stretched himself out over the child three times and cried out to the Lord, “O Lord my God, please let this child’s life return to him.” The Lord heard Elijah’s prayer, and the life of the child returned, and he revived! Then Elijah brought him down from the upper room and gave him to his mother. “Look!” he said. “Your son is alive!”

Then the woman told Elijah, “Now I know for sure that you are a man of God, and that the Lord truly speaks through you.” (1 Kings 17:17-24, NLT)

Let that sit. The drought is still on. Baal still owns the official story of rain in Sidon. This Gentile widow has already watched a Hebrew prophet eat from her last handful, and she has watched the jars refill. Now her son is gone, and she does what grief does: she reaches for a cause. She names Elijah. She names her sin. She names God as the one who came close enough to kill. This is not a tidy faith moment. It is a mother accusing the guest who was supposed to be a gift.

Elijah does not protect his image. He does not remind her about the flour. He does not offer a sentence about God’s timing. He says four words: “Give me your son.” He takes the body from her arms. He carries it to the room God assigned him. He cries out to the Lord with a question that would fail a branding workshop. He does not polish the prayer. He tells God the truth about a widow who opened her house and a boy who is no longer breathing. Then he stretches himself over the child and asks for the boy’s life back. The Lord hears. The boy lives. The widow’s last word is not a leadership technique. It is recognition that the Lord truly speaks through him.

I will not turn the stretching or the three cries into a protocol. This is narrative. God restored a child’s life in a Sidonian upper room under a word Elijah did not invent. You and I are not authorized to promise a resurrection we have not been given. The miracle belongs to the Lord. What the passage shows, without turning description into a command, is the shape of a leader who stays. Elijah does not leave the house. He does not hide behind the previous miracle. He does not correct the widow’s theology before he carries her grief. He takes the crisis upstairs and tells God the truth about it.

Here is the principle. Faithful leadership does not disappear when yesterday’s success is followed by today’s pain. Presence is not a slogan you send from the next meeting. It is remaining in the room, receiving the accusation without defending the brand, and carrying what you cannot fix before God. Paul later names the same posture without a dead child in the scene: “Be happy with those who are happy, and weep with those who weep.” (Romans 12:15, NLT) Weeping with those who weep is not a softer leadership style. It is refusing to skip the human cost because the dashboard still looks like a win.

The failure mode is familiar. A vice president spends six months pulling a division through a turnaround. The quarter closes. The board sends a note. Then the operations manager’s teenage son lands in the ICU on a Tuesday night. The VP’s calendar is already stacked with victory-lap reviews. The cheap move is a text, a gift basket, and a sentence that sounds like care while protecting the win: “Let me know if you need anything.” “Everything happens for a reason.” “We’ll cover you. Stay strong.” James would not call that listening. “Understand this, my dear brothers and sisters: You must all be quick to listen, slow to speak, and slow to get angry.” (James 1:19, NLT) Slow to speak is hard when your reflex is to manage the moment so it does not stain the story you finished telling upstairs.

I have watched leaders vanish in that gap. The win made them visible. The crisis made them busy. They told themselves the team needed their composure more than their presence, which is often a polite way of saying they needed the room not to see them without an answer. The widow did not need Elijah to be impressive. She needed him to take the boy. God is the one who comforts. Paul writes, “All praise to God, the Father of our Lord Jesus Christ. God is our merciful Father and the source of all comfort. He comforts us in all our troubles so that we can comfort others. When they are troubled, we will be able to give them the same comfort God has given us.” (2 Corinthians 1:3-4, NLT) Comfort is received before it is given. You cannot outsource it to a slogan and call that comfort. If you follow Christ, the first move in someone else’s pain is not a verse you have not prayed. If you are still exploring faith, the first move is still honest: stay, listen, and do not pretend you can reverse what you cannot reverse.

Bring this to Tuesday afternoon. Name the crisis that arrived after a win. A person. A failure. A diagnosis. A resignation that followed the celebration. Write the sentence you have been using to keep it at arm’s length. Then write the act of presence that would cost you something on the calendar. Cancel the victory-lap meeting. Sit in the waiting room without filling the silence. Take the accusation without correcting it in the hallway. Carry the name upstairs, which is to say, tell God the truth about a person you cannot fix. Presence is not a guarantee that the boy lives. Elijah’s prayer was heard because the Lord heard it, not because presence is a technique that forces outcomes. The work in front of you is narrower and heavier than a miracle you have not been promised. Stay in the house.

This will not look like leadership to people who only measure movement. Staying looks like lost time. Carrying grief upstairs looks like a leader who should have already moved on. The jars in this house were a daily mercy. They were not a shield against the next sorrow. Tomorrow the story widens. Obadiah serves God inside Ahab’s corrupt court and hides a hundred prophets where nobody is watching. Visible confrontation is not the only faithfulness God uses. The month still builds toward Stand and Rebuild, the paid field guide at the end of September. Today’s piece of that work is simpler than Carmel and costlier than a well-timed quote. When the crisis follows the provision, do not protect the win. Stay.

Leadership Challenge: Who is in a crisis that arrived after a win you wanted to protect? What sentence have you been using to keep it at arm’s length? What is one concrete act of presence this week that does not require you to fix what you cannot fix?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

The request sounds small until you hear her answer. She swears by the Lord his God, not hers, that the house is empty. She is a Sidonian woman in Jezebel’s country, gathering fuel for one last cake, and a Hebrew prophet has arrived with an empty stomach and a word. Most leaders would read the room and walk on. The math does not work. There is not enough.

Yesterday the method ended at Kerith. God closed the ravine and named this village. Today the assignment has a face, and the face is a woman who thinks she is about to die.

So he went to Zarephath. As he arrived at the gates of the village, he saw a widow gathering sticks, and he asked her, “Would you please bring me a little water in a cup?” As she was going to get it, he called to her, “Bring me a bite of bread, too.”

But she said, “I swear by the Lord your God that I don’t have a single piece of bread in the house. And I have only a handful of flour left in the jar and a little cooking oil in the bottom of the jug. I was just gathering a few sticks to cook this last meal, and then my son and I will die.”

But Elijah said to her, “Don’t be afraid! Go ahead and do just what you’ve said, but make a little bread for me first. Then use what’s left to prepare a meal for yourself and your son. For this is what the Lord, the God of Israel, says: There will always be flour and olive oil left in your containers until the time when the Lord sends rain and the crops grow again!”

So she did as Elijah said, and she and Elijah and her family continued to eat for many days. There was always enough flour and olive oil left in the containers, just as the Lord had promised through Elijah. (1 Kings 17:10-16, NLT)

Let that speech sit before you start mining it. God is the one who promised flour and oil. Elijah is the messenger. The widow is the one who has almost nothing. The drought Elijah announced in Ahab’s court has reached a Sidonian kitchen. Baal was supposed to own the rain. The jars are empty on schedule. The God of Israel is about to feed a Gentile household in Jezebel’s neighborhood, and He will do it without turning the prophet into a man who lives off the poor.

I will not turn this into a giving formula. This is narrative. It tells us what God did for this prophet and this widow under this word. It does not authorize a leader to walk into a strained household, ask for the last reserve, and call the request faith. Elijah does not invent the ask. Before he reached the gate, the Lord had already said, “Go and live in the village of Zarephath, near the city of Sidon. I have instructed a widow there to feed you.” (1 Kings 17:9, NLT) The instruction came from God. You and I do not get to copy a sentence we were never given. Remove the Lord’s promise from the scene and the ask becomes theft with religious language.

Here is the principle. When there is not enough, faithful leadership depends on God’s provision and refuses to manufacture supply by squeezing the people with the least. Obedience in scarcity is not a technique for forcing a miracle. The jars fill because the Lord promised they would. The leader’s work is to tell the truth about the shortage, to refuse the easy extraction, and to take the next obedient step without confusing himself with the Provider. God remains the actor. Elijah speaks a word he was given. The widow obeys a word she was given. None of that is a template for a capital campaign.

The dangerous line is the one leaders love to quote out of order: “make a little bread for me first.” Read without the promise, it sounds like spiritualized self-interest. James will not let that reading stand. “Pure and genuine religion in the sight of God the Father means caring for orphans and widows in their distress and refusing to let the world corrupt you.” (James 1:27, NLT) James is writing to believers who could talk a holy game while ignoring people in actual distress. If your scarcity plan begins with the intern, the contractor, the vendor who cannot float you, or the family member with the smallest voice, you are not walking in Elijah’s steps. You are walking past James. God fed the widow. He did not use her as fuel for the prophet’s reputation.

I have watched scarcity make otherwise decent leaders ugly in two directions. A director staring at three payrolls of runway starts cutting the people who cannot push back, while the travel budget and the executive search stay intact. She calls it stewardship. It is extraction with a cleaner name. The other failure is panic dressed as faith. A founder treats an empty account as proof the work is over, or as a test he can pass by announcing a vision he has not been given. Hebrews talks to both. “Don’t love money; be satisfied with what you have. For God has said, ‘I will never fail you. I will never abandon you.’” (Hebrews 13:5, NLT) The writer is not promising a jar that refills on demand. He is promising presence. Scarcity can be a season. It is not automatically a verdict. Love of money shows up as hoarding. It also shows up as using someone else’s last handful so yours never has to be the one that runs out.

Bring this to Tuesday afternoon. Write the shortage in one line. Cash. Headcount. Time. Attention. A pipeline that used to feed the work. Then write the name of the person who would pay first if you solved it the easy way. That name is the test. The director with three payrolls of runway already knows it. She has been circling it in meetings without saying it. This week she writes it down, then writes what she will cut instead, something that belongs to her comfort rather than someone else’s rent. Do not dress a squeeze as a faith opportunity for them. If you follow Christ, ask whether God has actually given a next step, or whether you are trying to force a sequel to Kerith. If you are still exploring faith, the next move is still honest. Tell the truth about the number to the people who deserve it. Cut something you can cut before you cut someone who cannot absorb it. Take one obedient action that does not require a miracle you have not been promised.

This will not feel like leadership on a dashboard. Refusing to raid the last jar looks like inaction to people who only measure movement. The flour and the oil never became a strategy Elijah could take on the road. They remained a daily mercy in a house that was still hungry enough to need tomorrow’s portion. Tomorrow the story gets harder. The boy dies, and Elijah does not protect his image or offer a slogan. He stays in the crisis. The month still builds toward Stand and Rebuild, the paid field guide at the end of September. Today’s piece of that work is narrower than fire and more expensive than a motivational verse about jars. When there is not enough, do not confuse dependence with extraction. God can feed a household in a drought. He has not authorized you to empty one.

Leadership Challenge: Where is there not enough this week? Write the shortage in one line, then write the name of the person who would pay first if you solved it the easy way. What is the next obedient step that does not require squeezing that person or inventing a miracle you have not been promised?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson

Yesterday I stayed at Kerith while the water still ran. God had sent Elijah east after the bravest public sentence of his life and fed him with birds. Hidden was not abandoned. Today the same story turns a harder corner. The provision was real. It was also temporary.

But after a while the brook dried up, for there was no rainfall anywhere in the land. Then the Lord said to Elijah, “Go and live in the village of Zarephath, near the city of Sidon. I have instructed a widow there to feed you.” (1 Kings 17:7-9, NLT)

Read the reason the verse names: “there was no rainfall anywhere in the land.” That drought is the word Elijah carried into Ahab’s court. The method ended because the assignment was working. Baal was supposed to own the clouds. The land is thirsty on schedule. God is not reversing Himself. He is keeping the word His prophet announced, and the prophet is not exempt from the weather that word created.

The next instruction still matters. Zarephath sits near Sidon, in the region Jezebel came from, in the religious neighborhood of the storm god Elijah had publicly defied. God does not send him back to a safer brook. He sends him deeper into Baal country, to a widow He has already instructed. Elijah does not invent the next plan while staring at dry stone. The Lord speaks. The next assignment has a name, a village, and a person. The first move after a dried brook is not hustle. It is attention.

I will not turn this into a relocation promise. This is narrative. It tells us what God did with this prophet when this particular supply ended. It does not guarantee that your next closed door will open onto a widow in Sidon. The miracle is not a career path you can copy. The miracle is that the God who commanded ravens can also close a brook without leaving the man He sent there.

Here is the principle. Faithful leaders must release a method when God changes the assignment, without confusing the method with the Provider. The brook was a gift. The ravens were a gift. Neither of them was God. When a leader treats the last thing that worked as the source, every change feels like abandonment. When a leader remembers who sent the ravens, a dry brook can be an instruction instead of a verdict.

James draws the line Elijah is standing on. “Whatever is good and perfect is a gift coming down to us from God our Father, who created all the lights in the heavens. He never changes or casts a shifting shadow.” (James 1:17, NLT) James is writing to scattered believers who were ready to accuse God of being two-faced in their trials. Gifts come down. Lights move. Shadows shift. The Father does not. That is not a slogan for ignoring loss. It is the reason you can tell the truth about a dried brook without deciding God has moved. The gift can end. The Giver remains.

I have watched this fail in both directions. A VP whose entire pipeline ran through one enterprise relationship keeps flying to that account after the champion has left, calling the trips loyalty. The method is dead. She is watering a dry cut in the rock and naming it perseverance. A founder whose first product was the company treats every signal to sunset it as a personal rejection. The product was a gift. It is not the source. A pastor whose Wednesday night used to fill the room keeps running the same format for a room that is gone, because stopping would feel like admitting God left with the crowd. None of them would say they are worshiping a brook. They would say they are being faithful to what worked. Faithfulness to a method after God has closed it is not faithfulness. It is nostalgia with a spiritual vocabulary.

The other failure wears the opposite costume. A leader hits one hard quarter and torches every process, every relationship, every practice that used to hold the work, then baptizes the panic as obedience. Elijah did not abandon Kerith because he got bored. The brook dried. The Lord spoke. Discernment still has to do its job. Some of what you want to call a dried brook is a channel you neglected. Some of it is a market that moved for ordinary reasons. Some of it is God. Do not dress a restless exit in Elijah’s clothes. Do not cling to a corpse and call it Kerith either. The test is the same one we used yesterday: assignment. Has the word changed, or have you?

Paul learned this without ravens. “I know how to live on almost nothing or with everything. I have learned the secret of living in every situation, whether it is with a full stomach or empty, with plenty or little.” (Philippians 4:12, NLT) He is writing from hardship to a church that had supported him, and he is careful not to treat their gift as the thing that keeps him alive. The secret is not a technique for keeping the brook full. The secret is a life attached to Christ in plenty and in empty. I am not mapping a Roman cell onto your P&L. I am noticing what Scripture says a leader can learn. The circumstance is not the source. Plenty is not proof you were right. Empty is not proof you were abandoned. Both can be seasons in a life that is still held.

Bring this to Tuesday afternoon. Name the method you have been treating as the source. Write it in one line. A sponsor. A channel. A meeting. A title. A product. A donor. A way of working that used to carry you. Then tell the truth about its condition. Is the water still running, and you are tired of drinking it? Is it actually gone? If it is gone, do not invent the next village in the next hour. Elijah received a word before he moved. Put one hour on the calendar this week to ask what the next assignment is, without announcing a reorg to cover the grief. If you are a believer, ask God whether He is closing a method or whether you are. If you are still exploring faith, the next move is still honest. Consider whether you have been treating every ended provision as evidence that you are finished. Some of what you call collapse is a change of supply. The work may still be yours. The old way of feeding it may not.

This will not feel like faith on a dashboard. Releasing a method looks like loss before it looks like obedience. Tomorrow we walk with Elijah into Zarephath, into a widow who thinks she is preparing a last meal. Scarcity is about to get more personal, and the passage will not let us turn a hungry household into a fundraising technique. The month still builds toward Stand and Rebuild, the paid field guide at the end of September. Today’s piece of that work is simpler than fire and harder than a strategy offsite. When the brook dries, do not confuse the creek with the One who sent you there.

Leadership Challenge: What method have you been treating as the source? Write it in one line. Has that method actually ended, or are you tired of it? If it has ended, what would it look like to wait for the next assignment this week instead of inventing one to cover the grief?

I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.

Subscribe now

Share Christian Leadership by Justin Wilson