3 ms·
The author's musings about this are good fun but they struggle to make a coherent point that delivers deep insight. In this post, he considers the points that c
by temp-dude-87844 8y ago
The author's musings about this are good fun but they struggle to make a coherent point that delivers deep insight. In this post, he considers the points that commenters raised and tiptoes around the possibility that maybe some bureaucratic rituals are a filter to screen the petitioners by desperation, but he doesn't talk about the possibility that such structures may have evolved incrementally to optimize for maximum ass-covering and the implications thereof. To him, efficiency (of filtering customers) is a sufficient explanation, which is odd considering his complaints about bureaucracy's inefficiencies before and after.
So then he raises the archetypal story of the DMV. For being the primary identity providers of the US populace, the DMVs of US states are actually rather remarkable. I guess the seemingly arbitrary progression of ticket numbers in cavernous waiting rooms is valid annoyance, but watermarked cards being mailed out to thousands of people just a few business days after collecting their info is pretty good, and then there's more vehicles than that.
Bureaucracy gets a bad rap, but it's worth applying the "I could've built that" test for them the same way it's trendy to critique valuable companies that are "just a chat app". If you had to credential 35 million people and 39 million vehicles a year, how would you do it? Would you codify a few things, and hire rockstars who can think on their feet? How soon would you start making rules about the blatantness of invalid forms, or unpaid fees, or how many people would you have to catch selling favors before you re-examine the process?
Deep bureaucracies are often the emergent result when your process has been burned by costly customers (in time, money, effort) or rogue employees (corruption, graft, espionage) too many times. They are systems where each and every decision maker can always defer to the Process as an explanation for why someone can't have something and the Process is sacred because "it's always been that way", even if it changes, and where each and every fulfiller is powerless to truly make a meaningful exception, except when that feature was already built in.
- repsilat 8y ago> The author's musings ... struggle to make a coherent point... > So then he raises the archetypal story of the DMV Maybe read it again? The author raises a coherent hypothesis, then questions it as a widely explanatory principle, using the DMV explicitly and intentionally as an example of bureaucratic inefficiency that it describes poorly.
- vinceguidry 8y agoIt's worth noting that Scott Alexander is himself a psychiatrist, not a software engineer. We should remember sometimes that not everyone thinks in terms of bandwidth and scale.
- natmaka 8y agoAn explanation may be true and useful (better than no explanation) even if it is only applicable to some cases. A given case of bureaucracy may have one or even many among multiple potential causes, inducing (for the requester) latency or cost in order to "separate out the needy from the greedy" being one, the various benefits a manager gains by over-staffing being another (DMV?)... Time and exasperation people are willing to put up with in order to get what they want is a form of co-payment. Part of it is paid for by the insured (as a "proof of real need"), another part being the bureaucracy which is paid by all insured people. Any insured may prefer to wait (than to occupy the bureaucracy by filling useless forms...) because it is far cheaper (no work for him nor for the bureaucracy), but this is rarely possible because there are urgent cases, and also because it seems more frustrating.