Mutual Submission amidst Point Leadership

Tensions have long blossomed in leadership-world between the concepts of a flat versus hierarchical organizational structure (click here for a brief summary of each). In church world, this really doesn't seem to be that much different. With a continued focus toward Servant Leadership, people often tend to drift to the mindset that it contradicts a more hierarchical structure. Others dislike a more hierarchical approach because of past abuses generated by the point leader, or the guy at the top of the totem.

However, in a talk about leadership, Andy Stanley argues that just because something has been abused, doesn't mean it's something to be cast out (for example, I'm currently abusing a scarf by having it currently act as my dish towel - however, that wrong act isn't enough to get rid of scarfs altogether... okay, bad example, but anyway...). Andy argues that Servant Leadership, or mutual submission within the organization, is not at odds with Point Leadership, but instead they work together.

A couple points from his talk:

Do for one when you can't do for all

It's not feasible to do everything for everyone... that's just plain reality. However, it's easy to use that as an excuse to in turn do nothing. It's easy to think, "I can't do this for you, because if I do that for you, then I'll have to do that for EVERYONE..." The underlining assumption being made is that it is right to be "fair". However, fairness is not a Biblical value... fairness ended at the Garden of Eden. The desire to be fair often conflicts with the ability to do the right thing. "Should I let my son do this, when I didn't let my other son do that at his age?" A desire to be fair could easily inhibit you from doing the right thing. So, again, you can't do everything for everyone, but you try to do something for someone! You do for the one what you wish you could do for all (if it were feasible).

Systematize top-down service

Random acts of kindness are not enough. Leaders need a systematic, built-in component in which to serve others, which flows into the rhythm of their organization. How do you accomplish this? Well, at the end of the day it all comes down to the leader. The blunt truth is that leaders don't have to serve, but others have to serve them... that's just the nature of being at the top. So, incredible intentionality is needed on the leaders part, or else it will never happen. It starts with the leader. A more practical example? A leader needs to develop an organizational culture with a sustainable pace. Meaning, a leader needs a schedule where he has margin. Otherwise, if there is no cushion or margin, the leader will be so consumed with his own busyness of life that opportunities to serve will never arise. Margin allows us to serve.

Don't pull an Asa!

2 Chronicles 14-16 recounts the life of King Asa of Judah. It is said that he did good in the sight of the Lord. Being a young leader, his reign was peaceful for the first ten years of his leadership.

Then, a mighty army from Ethiopia came out against him. Having no previous warfare experience, he fell before the Lord, praying for deliverance. The Lord, hearing and honoring Asa's prayer and submission, routed the Ethiopian army and gave them into the hands of Judah.

Twenty-six years later, tensions with Israel began to rise. However, at this time, Asa, now having a wealth of experience under his belt and understanding strategies of warfare, sought the help of a nearby king by making a treaty with him. The treaty was enough to make Israel think twice, and they turned and left. Good move Asa, right? Wrong... A prophet from Lord harshly rebuked Asa, unearthing his reliance on his strategies over his reliance on the Lord. Enraged, Asa threw the prophet in prison. Three years later, Asa came down with a severe disease, and once again, "did not seek the Lord, but the physicians."

Leadership application? As a young leader myself, I find myself much like the young Asa. I feel as though I don't have much experience or knowledge, which makes me feel overwhelmed with the issues before me, which is used as the catalyst to draw me to my knees before the Lord. My fear? As I begin to gain knowledge and understanding, my felt dependence on the Lord will diminish.

Reliance on experience and knowledge should NEVER trump humble reliance on the Lord

When problems arise in certain areas, what is my initial response? Am I more inclined to use 15-minutes to read an article or seek an expert, or am I more inclined to spend 15-minutes in prayer before the Lord? Now, I'm obviously not saying books or experts are bad... we are stewards of what we've been given, and as such are responsible to do things in the most strategic way possible. However, it's an issue of reliance... what is it banking on?

Because here's the reality. There's always a better expert than the top expert, and that expert is the creator... or, thee Creator. I'd rather rely on the Creator of psychology than Dr. Phil. I'd rather rely on the Creator of anatomy than the Mayo clinic. And I'd rather rely on the Creator of economy than Warren Buffet.

So, as I continue on this journey of ministry, seeking knowledge and wisdom from countless books and pastors, I need to be reminded that behind everything is the all-knowing and all-powerful God. Continually, I need to stop myself and say, "Don't pull an Asa!"

So it begins...

A friend once told me that journaling is one of the best spiritual disciplines a person can undertake, and is often talked about the least. Through loose experience, I'd have to agree with the benefits that it brings about. However, after countless notebooks, journals, and Word documents, I failed to really find a way to do it efficiently. Do I journal by category or chronology? Books or Scripture? Inspiration or information? I have yet to find a good venue to keep all my thoughts close by with easy accessibility and organization. And if I fail to write things down when those epiphany moments occur, that revelation is as good as lost. So, that is what this blog is... an attempt to fix that problem. Here goes nothing...

(This will likely be a work in progress until I figure all this "blog" stuff out)