Recently I purchased a new appliance and as part of the agreement, the company agreed to haul away the old appliance when it delivered the new replacement. On the day the appliance was delivered, there was a glitch.
“Sir, we’re going to have a schedule another day to haul away your old refrigerator.”
“Why?”
He pointed at the opening of the back of the truck. “We brought the wrong truck, the clearance is too low. We’re going to reschedule with a larger truck.”
I nodded. “Okay, but how are you going to make sure they know this just for a pickup and not a delivery?”
“Don’t worry, sir. I am calling it in right now and letting them know it is only for a pickup and I am telling them where we are leaving the old refrigerator, right next to this wall by the rubbish cans.”
His confidence and friendliness assuaged my concerns and a few hours later, I received a text message informing me that a pickup would be made the next day. I would be at work but he also reassured me that no one needed to be at my home when they came to pick it up. Right.
On Monday morning, I received a call from the delivery company. “Yeah, we’re here to pick up something but there is no one home.”
Is there a way to roll my eyes over a phone call? “Yes, I told the person who scheduled this that no one would be at home and he assured me that you guys would know what to do.”
“Oh, uh sorry. No one told us. We usually just drop off a new appliance and pick up an old one. We never do just a pickup.”
All organizations follow protocols which are necessary for work to be performed smoothly and accurately. When events arise that are outside the usual course of events, any weaknesses or gaps in existing protocols may be revealed. This recent simple example reminded me of the importance of involving all stakeholders when modifications to protocols are made. At the least it is annoying. At the worst, it can lead to financial loss or lives being hurt or lost. Any change needs to be implemented from the top and communicated throughout the organization.
In ancient Israel, all priests were Levites, descended from their ancestor Levi, one of the twelve sons of the patriarch Israel (Jacob). The Bible presents Jesus Christ as Messiah. He is King, Prophet, and Priest. Yet, when Jesus was presented to many of the Jews, they dismissed this possibility since only descendents of Levi could hold the position of priest. Jesus was from the tribe of Judah, a direct descendent of King David.
For it is evident that our Lord was descended from Judah, and in connection with that tribe Moses said nothing about priests.
Hebrews 7:14 (ESV)
The author of Hebrews anticipated such objections and effectively demonstrated that Jesus did not conform to the established laws and protocols of the Jews. It was a new line of priesthood with Jesus Christ as the High Priest. But the only way Jews would accept this change is if the direction came from the top. It did.
But he holds his priesthood permanently, because he continues forever. Consequently, he is able to save to the uttermost those who draw near to God through him, since he always lives to make intercession for them. For it was indeed fitting that we should have such a high priest, holy, innocent, unstained, separated from sinners, and exalted above the heavens.
Hebrews 7:24-26 (ESV)
God declared that Jesus Christ is the Messiah and uniquely qualified to hold the titles of King, Priest, and Prophet. He sealed this declaration by placing the sins of mankind upon His broken tortured Body, dying on the Cross. Three days later, God raised Him from the dead proving to all creation that by confessing and repenting our sins to the High Priest, Jesus Christ, we would receive salvation and eternal life.
The hapless delivery people who came to my house were never informed of the change in protocol. No one bothered to tell them the truth. There is no confusion or miscommunication when God commands a change in protocol. He has declared His Truth in the Bible and proclaims it to all mankind.
Amen!
Love and trust the Lord; seek His will in your life.
The Bereans Blog 