First, one of the endless stream of intrusive updates from Microsoft borked Outlook, as a new and overzealous server-monitoring program shut down server after server. This caused a cascading collapse of business communications that are reliant on MS services. This also gave a brief and unanticipated vacation to countless workers, and there was much rejoicing.
Second, an update to FAA systems unexpectedly compromised the entire flight control system in the United States, grounding every single plane in America. To be fair, "unexpected" isn't quite right, as our Frankenstein's monster of an air traffic control system is mostly held together with duct tape, thoughts, and prayers. Best I can tell, a modern routing system was connected via fiber optic to much older systems, and it proceeded to overwhelm them with high speed inputs. The whole SNAFU parses like a self-inflicted denial-of-service attack. It was fixed in four hours, which was reassuring. On the other hand, there's no reason to believe something like that won't happen again. This isn't reassuring.
The more complex a system, the more energy it requires to maintain, and the more potential points of failure surface within it. As a nation, we're increasingly aware of this, as our shambolic health care system, crumbling transportation infrastructure, and inscrutably complex IT economy start to show point after point of failure.
Being Presbyterian, I marvel at how the overcomplicating of America mirrors our own hypercomplicated polity. Like the bloated administrative structures of academe, we seem to think that the answer to the problem of complexity is more complexity.
We keep adding requirements, loading policy upon procedure upon protocol, to the point where we've created a ruleset for life together that's a vampiric drain on our collective energies. At three point five million members, we could fill the committees and task forces and mid-council professional roles without difficulty. Now? Now those energies are waning, as our collapsing membership and participation leaves us saddled with a system so bureaucratically and legalistically overweight that we can barely stand.
I notice it everywhere.
Like, say, at a recent "Healthy Boundaries" training put on by my Presbytery. It's something I'm Book-of-Obligation obliged to do every three years, with the idea that it reduces the likelihood of pastoral and congregational malfeasance. Requiring pastors to participate in that training reduces organizational liability, but it also provides a bulwark against sexual and financial misconduct. This is all well and good, and I see the value of it.
But...as I learned at the training...the General Assembly recently expanded the requirement not just to pastors, but to all leaders in the church. Meaning, your congregational elders, all of whom are volunteers. Is there a plan to make this happen? No, there is not. Was that requirement communicated to the church effectively? Nope. I didn't know about it until that moment. Not a single pastor in the two small groups I participated in during that training knew about it. They were too busy keeping up with all of the already-extant requirements and the demands of the pastorate to have noticed.
Is that requirement well-meaning? Sure.
But so are the paving stones in the road to hell.
Or, say, the recent requirement that pastors receive Antiracism training every three years. Why every three years? I honestly don't know. It's not like it's a certification thing. Like baptism, just doing it once would seem sufficient. At the Healthy Boundaries training, a longstanding and active pastor in Presbytery expressed surprise that it wasn't just one and done. "Don't we only have to do that once?" she said. "Nope," I replied.
When I went to that mandatory eight hour Antiracism training a few weeks later (it was a surprisingly useful day), I was one of five pastors in attendance. It's offered semiannually, and there are hundreds of pastors in my large urban Presbytery, and there were five pastors in attendance. Even my clergyfolk-level mathematical skill tells me folks are just bailing on it.
When requirements aren't required, what do they even mean?
Take our remarkably convoluted ordination process, one that requires an undergraduate education, a graduate degree, internship in congregations and hospital settings, and a sequence of exams modeled on modern era civil service tests. It always felt to me like trial-by-process, more a test of patience and endurance than anything else. Not a single Presbytery meeting goes by without the body being required to approve an exception to that process, as it's a consistent stumbling block to our dwindling trickle of candidates for ministry. If we're constantly having to circumvent a process, it no longer serves its purpose.
Again, if requirements aren't required, what do they even mean?
There's an increasing disconnect between the demands of an overcomplicated polity and the real-life congregations that it's meant to serve. It's as if we suffer from ecclesiastical neuropathy, as the signals from our putatively higher functions don't get down to the body, and the body's pain isn't felt by the systems that nominally guide our actions.
