Let’s pick up from where we left on in Part 1 of this series of articles on adaptive decision making, change, and leadership. Be sure to start by reading Part 1 if you haven’t yet done so.
Over the last century, here’s the reason most churches and organizations have been able to scale and support the growth that they’ve experienced.
It’s because of the modern day “scientific management model,” which rests primarily upon two elements:
- “Absolutely rigid and inflexible standards throughout your establishment.”
- “That each employee of your establishment should receive every day clear-cut, definite instructions as to just what he is to do and how he is to do it, and these instructions should be exactly carried out, whether they are right or wrong.”[1]
I’m not saying that these two elements run the shop in every church and organization today. I’m just saying that they are the foundation that modern day management theory—both inside and outside the church—has been built upon, and it doesn’t work anymore because…
- You can’t just set it and forget it
- You can’t just keep your head down, do your work, and expect to succeed and hit your goals
- Your success isn’t wholly dependent on you
- If the only time you talk about development is the annual performance review, you won’t grow
- If the only time you connect with your volunteers and leaders are on Sunday or in formal training environments, they won’t feel connected
- If the only things you do are the things on your job description, your team won’t win
- In fact, if you’re not revisiting your job description multiple times a year, it will become outdated quick
- And if the only time you talk with your team members is during official team meetings, your team will move too slow
- And if you’re not changing your website every 2-3 years, watch out…irrelevancy is just around the corner
In his book, Accelerate, John Kotter, the well-known change management expert says that there are two different types of organizations: networks and hierarchies.
Here’s how he explains the difference and the progression that organizations make as they move from one to the other:
Virtually all successful organizations on earth go through a very similar life cycle. They begin with a network-like structure, sort of like a solar system with a sun, planets, moons, and even satellites. Founders are at the center. Others are at various nodes working on different initiatives. Action is opportunity seeking and risk taking, all guided by a vision that people buy into. Energized individuals move quickly and with agility.
Over time, a successful organization evolves through a series of stages…into an enterprise that is structured as a hierarchy and is driven by well-known managerial processes: planning, budgeting, job defining, staffing, measuring, problem solving. With a well-structured hierarchy and with managerial processes that are driven with skill, this more mature organization can produce incredibly reliable and efficient results on a weekly, quarterly, and annual basis.”[2]
There are benefits and frustrations to both.
When it comes to the church, networks seem like small churches, don’t they? Or church plants?
And don’t hierarchies seem like larger established churches? Or the megachurch?
However, one is not better than the other. Both are needed.
And today, in order to grow and multiply your church or organization, you actually need both—a dual operating system—where you have hierarchy on the one side and network on the other.
But in order to see this dual operating system functioning well within your church, you need to carefully think through how decisions are made.
Just consider modern day warfare.
Whereas before successful missions were led by armchair generals in cigar smoke filled rooms who made the strategic decisions for everyone on and off the field—and everyone had to do exactly as he said and commanded—today, successful missions are a result of real-time decisions made on the field by commanders and soldiers who know the intent and values of the general, even when they’re not with him.
And this is precisely how General Stanley McChrystal led the U.S. forces when they were battling Al Qaeda in Iraq. Here’s how he puts it in his book, Team of Teams:
AQI was an organization native to the information-rich, densely interconnected world of the twenty-first century. It operated in ways that diverged radically from those we thought of as “correct” and “effective.” But it worked. In the course of this fight, we had to unlearn a great deal of what we thought we knew about how war—and the world—worked. We had to tear down familiar organizational structures and rebuild them along completely different lines, swapping our sturdy architecture for organic fluidity, because it was the only way to confront a rising tide of complex threats. Specifically, we restructured our force from the ground up on principles of extremely transparent information sharing (what we call “shared consciousness”) and decentralized decision-making authority (“ empowered execution”). We dissolved the barriers—the walls of our silos and the floors of our hierarchies—that had once made us efficient. We looked at the behaviors of our smallest units and found ways to extend them to an organization of thousands, spread across three continents. We became what we called “a team of teams”: a large command that captured at scale the traits of agility normally limited to small teams. Almost everything we did ran against the grain of military tradition and of general organizational practice. We abandoned many of the precepts that had helped establish our efficacy in the twentieth century, because the twenty-first century is a different game with different rules. Our struggle in Iraq in 2004 is not an exception—it is the new norm. The models of organizational success that dominated the twentieth century have their roots in the industrial revolution and, simply put, the world has changed. The pursuit of “efficiency”—getting the most with the least investment of energy, time, or money—was once a laudable goal, but being effective in today’s world is less a question of optimizing for a known (and relatively stable) set of variables than responsiveness to a constantly shifting environment. Adaptability, not efficiency, must become our central competency. [3]
In order to grow and multiply your church or organization, it’s mission critical that every one on your team becomes more obsessed with adaptability over efficiency.
This is what’s going to lead you onto the path to become a team of teams, or an organization that networks alongside its hierarchy. After all, it’s nearly impossible to predict the changes that are on their way and plan for them years in advance.
What’s more effective is developing resilience, so that you’re ready no matter what comes around the corner.
Just consider Taipei 101.
It was the tallest tower in the world, with 101 floors, until the completion of the Burj Khalifa in Dubai in 2010. In Taipei 101, you go from the 5th to the 89th floor in 37 seconds, going 60.6 km/hr (37.7mph).
But just imagine the kind of architecture that needed to go into this to withstand the typhoons and earthquakes that are common to this area of Taiwan. In fact, Taipei 101 is only 660 ft away from a major fault line!
The structural engineers designed Taipei 101 to withstand winds of 216 km/hr (134mph), as well as the strongest earthquakes in a 2500 year cycle. They were able to build Taipei 101 to withstand all of this using:
- High-performance steel construction
- Columns
- 380 piles driven 80 m (262 ft) into the ground
- A 660 tonne steel pendulum mass damper suspended from the 92nd to the 87th floor
- This pendulum is designed to offset strong gusts that the building would receive
In fact, on Aug 2015, strong winds from Typhoon Soudelor swayed the damper by 100 cm!
Isn’t this amazing?
Taipei 101 is huge, yet it was built to be adaptable and flexible because the engineers knew that this is what was needed for it to survive the context and environment it was planted in.
Unlike other buildings that collapsed during typhoons, strong winds, and earthquakes, Taipei 101 was built to adapt with the changing context and winds in order to thrive.
How about your church or organization?
Are you structured as a network or a hierarchy? Do you have elements of both? And what rules the day for you? Is it adaptability or efficiency?
I love this quote by Andrew Zolli, “if we cannot control the volatile tides of change, we can learn to build better boats.”
What can you do to become more adaptable? What can your team do? What can your church or organization do?
Endnotes:
[1] Team of Teams: New Rules of Engagement for a Complex World by General Stanley McChrystal, 211.
[2] Accelerate: Building Strategic Agility for a Faster-Moving World by John P. Kotter, 5.
[3] Team of Teams, 19-20.
[…] This article originally appeared here. […]