Halfway There

Episode 3 • September 25, 2026 • 00:22:14
Halfway There
Passing the Mantle
Halfway There

Sep 25 2026 | 00:22:14

/

Hosted By

Dr Peter Frost, PhD

Show Notes

How do you keep going when leadership development feels like a long journey—and you can’t see how far you’ve come or how much farther you have to go?

In this episode of Passing the Mantle, Dr. Peter Frost explores the slow, intentional work of preparing the next generation of leaders. Drawing on Moses and Joshua’s time on Mount Sinai in Exodus 24 and the crisis of the golden calf in Exodus 32, he considers how proximity, patience, and experience helped prepare Joshua for leadership. Peter also reflects on the moments when leaders lose momentum, why developing even one person matters, and how the influence you pass on can continue long after your own handoff.

View Full Transcript

Episode Transcript

Welcome back to Passing the Mantle. I'm Peter Frost, and this is the podcast where we talk about biblical succession planning through intentional leadership development. If you've been with me from the beginning, you know this isn't a book about finding a warm body to fill a chair when you leave. It's a book about the long, deliberate, often invisible work of preparing someone to carry what you've been carrying — and about the God who has been doing that work since the book of Exodus. Last episode, we looked at how leaders arise from unexpected places. We saw Joshua appear out of nowhere, ready to lead Israel into its first battle, and we talked about how people with leadership qualities get noticed by those who are seeking God's direction. Today I want to ask a question that comes up on almost every long journey I've ever taken — and I mean that literally and figuratively. How much farther? Let's get into it. I have told my children, and now my grandchildren, a phrase that is probably older than I am. It comes out automatically whenever a small voice from the back seat asks, "How much farther?" "Halfway there." Now, I want to be honest with you — sometimes that was true. Sometimes it was not. Sometimes "halfway there" was a pastoral statement. But the point is real: being halfway is sometimes a good thing, especially when you are progressing to a point. Halfway means you're not where you started, and it means the destination is still in front of you. There's a joke I like that makes this point a little too well. Three felons have escaped from prison and are attempting to swim to freedom. The first felon swims about a quarter of the way, realizes he cannot make it, and swims back. The second felon swims about a third of the way, realizes he cannot make it, and swims back. The third felon swims about two-thirds of the way to freedom and turns back. When he gets back, the other two ask him, "Why did you come back? You were almost free!" He says, "I got tired, so I came back." And there it is. That's not just a prison joke. That's a leadership development joke. That's a succession planning joke. Because I have watched people get most of the way to something — most of the way to readiness, most of the way to handoff, most of the way to a legacy that would outlast them — and turn back. Not because they were wrong. Because they got tired. Here's the truth: succession planning is a long process. We may not know exactly when we are halfway there, but we don't want to turn back to where we came from. I want you to sit with that for a second. The danger in leadership development is rarely a dramatic failure. It's attrition. It's the slow loss of momentum. It's the leader who starts mentoring someone and then gets busy. It's the organization that launches a development program and then quietly stops funding it, or stops promoting it, or stops requiring participation. It's the person being developed who gets discouraged because they can't see the finish line. And notice the felon's problem wasn't the distance. It was that he couldn't tell how much distance was left. He had no idea where halfway was. That's the question I want to explore today. To know where halfway is, we need to know the beginning and the end. That sounds obvious, and yet so much of our leadership development work is done without a clear sense of either one. Sometimes we know what the end is. We want to leave a leadership legacy. We want someone to assume the mantle of leadership. We want to have an organization that has a culture of developing leaders — not just one successor, but an ongoing pattern of raising people up. Sometimes we can look back and see where we started. We can see where we were mentored, coached, and given opportunities. We can see where we have invested in others and watched them move up in the organization. That's a gift — being able to trace the line from there to here. But sometimes — and I think this is more common than we admit — we are standing around looking for the place to start. We know we want to develop someone. We just don't know where to begin. In Episode 2, we saw that leaders arise from unexpected places. So let me lower the bar for you, in a good way. You may not be in a position to impact the entire organization. But can you change your team? Can you develop one person? That's a beginning. And once you have a beginning and an end in view, you can start to estimate where halfway is. When I announced that we would not be returning to Papua New Guinea in 2021, I received an email from a friend that pointed to three leaders in the organization that I had developed and placed into leadership roles. I didn't know, in the moment, that I was halfway. Honestly, I'm not sure I ever knew where halfway was during those years. But someone else could see the line from beginning to end. And even if you can only develop one person to be your successor, the lessons you teach may be passed on — and then passed on again. I was fortunate, and I tell about it in the book, Passing the Mantle, that one of the ladies had taken over my role as Senior Manager over two years before I left. But halfway there was already in the past before I knew it. Now let's open the Scriptures, because the Bible gives us a picture of what it looks like to be halfway — and it's a picture of a man standing on the side of a mountain. [HOST reads Exodus 24:9–18, CSB] 9 Then Moses went up with Aaron, Nadab, and Abihu, and seventy of Israel's elders, 10 and they saw the God of Israel. Beneath his feet was something like a pavement made of lapis lazuli, as clear as the sky itself. 11 God did not harm the Israelite nobles; they saw him, and they ate and drank. 12 The LORD said to Moses, "Come up to me on the mountain and stay there so that I may give you the stone tablets with the law and commandments I have written for their instruction." 13 So Moses arose with his assistant Joshua and went up the mountain of God. 14 He told the elders, "Wait here for us until we return to you. Aaron and Hur are here with you. Whoever has a dispute should go to them." 15 When Moses went up the mountain, the cloud covered it. 16 The glory of the LORD settled on Mount Sinai, and the cloud covered it for six days. On the seventh day he called to Moses from the cloud. 17 The appearance of the LORD's glory to the Israelites was like a consuming fire on the mountaintop. 18 Moses entered the cloud as he went up the mountain, and he remained on the mountain forty days and forty nights. Analysis from the dissertation. There's a detail here that is easy to skim past. Before Moses heads up the mountain again, we are told that seventy-four people see God — Moses, Aaron, Nadab, Abihu, and the seventy elders. Maybe seventy-five if we consider Joshua as being present. I don’t think Joshua is one of the 70 elders. They saw him, and they ate and drank. That's an astonishing sentence. But then the narrative narrows. Moses arises with his assistant Joshua and goes up the mountain of God. And here's what the scholars notice: Joshua doesn't go all the way. He waits halfway up the mountain. Stuart explains that Moses brought Joshua part way up the mountain, and that if God was not pleased with this decision, he could send Joshua back down. The fact that God did not send Joshua back down reveals more of God's plan for Joshua. That's a remarkable thing to consider — that God's silence on the matter was itself a form of direction. Look at Acts 16:6-8. Paul and his team were not told where to go until they got to Troas. They were told where NOT to go. Mackay infers that Moses suspected he would be on the mountain a long time, and that having Joshua nearby would let Moses rely on messages more quickly or learn of disturbances from the camp. Ryken, Wilhoit, and Longman put it beautifully: Joshua is an example, in the good sense, of a follower of a human leader. Where Moses goes, there goes Joshua, even ascending the mountain of the Lord. Joshua is so diligent and faithful to Moses that he waits on the mountainside for him, staying forty days and forty nights until Moses returns with the tablets. White notes that it is reasonable to infer Joshua remains present with Moses for the forty days, while Aaron is below — and consequently, Joshua does not participate in the golden calf incident. White even observes that Joshua typologically prefigures Jesus, who is with Moses in the cloud of divine glory on Mount Sinai. Notice, too, the timing. Moses had to wait six days before he could enter into the Lord's presence. Six days of cloud. Six days of glory settling on the mountain. Six days of waiting before the seventh-day call. And down the mountain — halfway down, really — a man named Joshua is waiting too. Analysis from Passing the Mantle. In the book, I make the point that Joshua began his leadership journey by gaining experience and observing Moses in action. And this moment on the mountain is one of the clearest examples of that. Halfway up the mountain was not a delay. It was a protection. It was a preparation. It was a position. Joshua's role as Moses's assistant is not like the modern role of an assistant. Joshua was not "second in command." Joshua represents the next generation of leadership for Israel. He is about thirty-five years younger than Moses. Throughout the remaining years of wilderness wandering, Joshua was probably near Moses, observing how Moses handled situations and how he communicated with the LORD. That's what development looks like. It's proximity over time. But the mountain doesn't stay quiet. While Moses is up there, the camp down below falls apart. This is interesting because before Moses went up the mountain, the children of Israel response to the reading of the covenant 40 days earlier is, “We will do and obey all that the LORD has commanded.” 40 days. Not even six weeks. Let's read what happens when Moses and Joshua come back down. [HOST reads Exodus 32:7–25, CSB] 7 The LORD spoke to Moses: "Go down at once! For your people you brought up from the land of Egypt have acted corruptly. 8 They have quickly turned from the way I commanded them; they have made for themselves an image of a calf. They have bowed down to it, sacrificed to it, and said, 'Israel, these are your gods, who brought you up from the land of Egypt.'" 9 The LORD also said to Moses, "I have seen this people, and they are indeed a stiff-necked people. 10 Now leave me alone, so that my anger can burn against them and I can destroy them. Then I will make you into a great nation." 11 But Moses sought the favor of the LORD his God: "LORD, why does your anger burn against your people you brought out of the land of Egypt with great power and a strong hand? 12 Why should the Egyptians say, 'He brought them out with an evil intent to kill them in the mountains and eliminate them from the face of the earth'? Turn from your fierce anger and relent concerning this disaster planned for your people. 13 Remember your servants Abraham, Isaac, and Israel — you swore to them by yourself and declared, 'I will make your offspring as numerous as the stars of the sky and will give your offspring all this land that I have promised, and they will inherit it forever.'" 14 So the LORD relented concerning the disaster he had said he would bring on his people. 15 Then Moses turned and went down the mountain with the two tablets of the testimony in his hands. They were inscribed on both sides — inscribed front and back. 16 The tablets were the work of God, and the writing was God's writing, engraved on the tablets. 17 When Joshua heard the sound of the people as they shouted, he said to Moses, "There is a sound of war in the camp." 18 But Moses replied, It's not the sound of a victory cry and not the sound of a cry of defeat; I hear the sound of singing! 19 As he approached the camp and saw the calf and the dancing, Moses became enraged and threw the tablets out of his hands, smashing them at the base of the mountain. 20 He took the calf they had made, burned it up, and ground it to powder. He scattered the powder over the surface of the water and forced the Israelites to drink the water. 21 Then Moses asked Aaron, "What did these people do to you that you have led them into such a grave sin?" 22 "Don't be enraged, my lord," Aaron replied. "You yourself know that the people are intent on evil. 23 They said to me, 'Make gods for us who will go before us because this Moses, the man who brought us up from the land of Egypt — we don't know what has happened to him!' 24 So I said to them, 'Whoever has gold, take it off,' and they gave it to me. When I threw it into the fire, out came this calf!" 25 Moses saw that the people were out of control, for Aaron had let them get out of control, making them a laughingstock to their enemies. Notice the interaction between Joshua and Moses in verses 17 and 18. Joshua demonstrates his military background with his comment — "There is a sound of war in the camp." He hears noise, and his training tells him it's a battle. Mackay observes that Moses did not tell Joshua what the Lord had revealed to him. Joshua interpreted the noise as fighting because of his experience. Moses had more information, and he corrected Joshua. Stuart agrees — Joshua's role as military leader caused him to misinterpret the noise as a battle. Hamilton concurs. And then there's this line from Mackay that I find so honest: perhaps Moses was singularly focused on resolving the problem and did not consider telling Joshua, or perhaps he wanted to know how Joshua would respond. Either way, the information gap is real. Joshua is standing right next to the man of God, and he still doesn't know what God said. Bruckner observes that the mention of Joshua helps to validate his future leadership role — his focus on war is typical. In other words, the very thing that made Joshua misread the moment is part of what made him the leader he would become. In the book, I draw this out: Moses and Joshua descend the mountain together in Exodus 32. Joshua's response was based on his experience. He did not know what the Lord had told Moses. Joshua being halfway up the mountain prevented him from participating in the Golden Calf incident — but it also meant he missed the conversation between God and Moses. Scholars agree Joshua's presence on the mountain is significant. From Joshua's reaction in Exodus 32:17, we can deduce that Joshua spent the entire time on the mountain with Moses. His response was based on his experience. He did not know what the Lord had told Moses. And here is the sentence I want you to hold onto: Joshua being halfway up the mountain prevented him from participating in the Golden Calf incident. This is the tension of development. You want the person you're developing close enough to be protected and formed. But close is not the same as informed. Joshua was geographically near and informationally far. And Moses had more information that he did not share immediately with Joshua. I'll say more about that in a moment, because it's one of the most practical lessons in this entire episode. So what do we take with us? Two lessons, and they're connected. First: those we are developing do not have our experience and our information. We need to share it with them. Joshua heard the sound of singing and called it war. That wasn't a character flaw. It was an information gap. He had the training, he had the proximity, he had the track record — but he did not have what God had said to Moses on the mountain. And Moses, for whatever reason, didn't tell him right away. If you are leading someone, remember that they are working with less than you are. Less history. Less context. Less access. They will misread situations that seem obvious to you. Your job is not to be annoyed by that. Your job is to close the gap. Tell them what you know. Tell them why you're doing what you're doing. Let them hear the conversation, not just see the decision. And notice: Boers reminds us not to rush the development of Christian leaders. The gap closes over time, not overnight. Second: we need to bring those we are developing with us whenever we can. Moses brought Joshua up the mountain. He didn't have to. He could have gone alone. But he took Joshua part way up — far enough that Joshua was separated from the sin in the camp, far enough that he was near the presence of God, far enough that he was being formed for what was coming next. Joshua spent forty years being developed as Moses's successor. Development happened in proximity. In shared space. On the same journey. So bring them with you. To the meeting. To the hospital visit. To the hard conversation. To the mountain. You don't have to give them your chair. You just have to let them stand where you stand. Here's what I want you to remember as you go back to your week. The felon who turned back wasn't defeated by the distance. He was defeated by not knowing where halfway was. And if you're in the long, slow work of developing someone — and I hope you are — you may not know exactly where halfway is either. It may surprise you to know that you are almost finished—in a good way. But you can know your beginning. You can name the end. And you can keep bringing someone with you, and keep telling them what you know, until the mantle passes. I think about that email from my friend, pointing to three leaders I had developed and placed into leadership roles. I didn't see it coming. Halfway there is often invisible while you're standing in it. Next time, we're going to follow Joshua one step further — to the Tent of Meeting outside the camp, in Exodus 33, where a young man who would not leave the tent shows us what nearness to God looks like over the long haul. Until then — keep passing the mantle.

Other Episodes

Episode 1

September 24, 2026 • 00:19:55
Episode Cover

Introduction to Passing the Mantle

In the opening episode of Passing the Mantle, Dr. Peter Frost introduces a biblical vision for succession planning — the intentional work of preparing...

Listen

Episode 7

November 13, 2026 • 00:18:15
Episode Cover

Episode 7 - But It's Not Christian

Is succession planning a business idea—or can it serve the work of God? In this episode of Passing the Mantle, Peter Frost, PhD, turns...

Listen

Episode 6

November 06, 2026 • 00:23:24
Episode Cover

Episode 6 - When It's Time To Go

In Episode 6, "When It's Time to Go," we ask the question every leader eventually faces: when — and how — do you transition...

Listen