Executive Pastor Online Blog

This is my personal blog. I regularly write about church leadership and infrastructure development, including specifics on leadership techniques and the details of implementing systems, processes, and methods that enable the church to succeed.

Infrastructure and Leadership

infrastructure leadership May 01, 2024
Infrastructure and Leadership

Believing That Lack of Solid Infrastructure is a Leadership Issue

 

Truly good leadership is hard to find. Many people in leadership positions (it's been my experience) shouldn't be. It's sad but true. So, when an organization is fortunate enough to have solid leadership, leveraging it is HUGE.

It's all about scalability! How can an organization leverage its leadership? Its knowledge? There are only so many leadership people to go around, and good leaders are extremely difficult to find. So ... building a world-class organization depends on the leader's ability to develop good systems, processes, and methods and to make them known (easy to access, learn about, use, and change as needed) to the entire organization.

Believe it or not, this is a foreign concept to many people in leadership positions. A leader can't build an organization for long on his/her own personal effort. There's only so much time and personal energy to go around. They must figure out how to duplicate themselves, developing other leaders and putting systems, processes, and methods in place that help others to get the job done.

The bottom line is this ... an organization can be boiled down to hundreds of individual and interdependent processes. The key is to decide the best method to do something and to document it in a format that ensures the agreed-upon method is followed every time. Sounds pretty simple, doesn't it? For whatever reason, though, it never is in the trenches day-to-day. Leaders continue to wonder why things don't work as they should, never concluding that they simply haven't communicated how they want something to happen. They've never gotten their employees involved in helping them to decide on a best practice.

And improvement is extremely difficult if the method is not consistent. If everyone does it differently, it is almost impossible to determine what needs to change. But, if everyone has agreed to follow an established method, it's pretty easy to make improvements. A solid, well-documented, and communicated infrastructure is a means to manage and facilitate change for the better.

The issue is growth. An organization's ability to grow will be determined by its ability to develop infrastructure. To grow, a leader must get very good at identifying, developing, training, and deploying people. A solid infrastructure enables this to happen quickly and efficiently. In the words of a leadership friend of mine, "We've already agreed on the best way to do that; now it's just a matter of getting new people up to speed." Organizations that get this concept will grow the strongest and the fastest!

To clarify, though, let me say that we're talking about effective leaders needing to understand something. They don't have to be good at it themselves. Many effective leaders are not good at developing infrastructure. This doesn't make them less effective. However, they need to understand the importance of developing infrastructure.

I have been around many leaders who don't get this fundamental. They are busy getting frustrated with their team(s) "blaming" them for lack of performance when they are to blame. They, as the leader, don't understand why results are not meeting the stakeholder's needs. This is what makes them ineffective as a leader. They will always be frustrated because they "do not understand" what needs to be done to succeed.

If a leader does understand the importance of developing infrastructure but isn't good at doing so, he/she must make it a priority by surrounding themselves with people (preferably leaders) that are good at developing infrastructure. Once this is done, they must continuously reinforce the importance with everyone in the organization. For example, they have to use the language the infrastructure development people are using. They must read, practice, and reinforce systems, processes, and methods as they are developed ... demonstrating the priority and criticality to the rest of the organization.

SUBSCRIBE TODAY!

Receive new posts directly to your inbox.

You're safe with me. I'll never spam you or sell your contact info.