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 to my Substack at: https://christianleadership.now