I do think legibility is actually very helpful, especially as organizations grow in size. I'm wondering why you are saying that legibility isn't healthy in and of itself.
Say, for example, I am working on a task and I need something done which is not normal. For example, I may need to make a change to some service that is running, or get permissions or ownership of some object assigned to my account. Because of the legibility that bureaucracy brings, I can find the relevant team with ability/authority to solve my problem, or I can discover that no such team exists.
If the team exists, then that's great. I can talk directly to people with experience with whatever problem I'm solving, who know the relevant policies / risks / recommendations. If the team doesn't exist, I can still just make the change myself. If the team exists but won't help me, I can hand the problem off to my manager. If the relevant people are on vacation, I can find out who has power in their stead. (There are some cases where this doesn't work--my experience is that this usually involves some inflexible legal requirement, or some essential technical expertise, and the relevant person is on vacation.)
This legibility brings a sort of "mindlessness" to the bureaucracy. I have high confidence that soon, I will either solve the problem, or the problem will belong to somebody else. I don't have to think too hard about what the right thing to do is when it's outside my domain, except in the exceptional cases.
Say, for example, I am working on a task and I need something done which is not normal. For example, I may need to make a change to some service that is running, or get permissions or ownership of some object assigned to my account. Because of the legibility that bureaucracy brings, I can find the relevant team with ability/authority to solve my problem, or I can discover that no such team exists.
If the team exists, then that's great. I can talk directly to people with experience with whatever problem I'm solving, who know the relevant policies / risks / recommendations. If the team doesn't exist, I can still just make the change myself. If the team exists but won't help me, I can hand the problem off to my manager. If the relevant people are on vacation, I can find out who has power in their stead. (There are some cases where this doesn't work--my experience is that this usually involves some inflexible legal requirement, or some essential technical expertise, and the relevant person is on vacation.)
This legibility brings a sort of "mindlessness" to the bureaucracy. I have high confidence that soon, I will either solve the problem, or the problem will belong to somebody else. I don't have to think too hard about what the right thing to do is when it's outside my domain, except in the exceptional cases.