I miss good technical manuals. Nowadays, there is a barebones manual which will direct you to a tech support area (github or stack overflow are big offenders for software, discord for games, and twitter or reddit for everything else it seems). The most obvious effect is everyone has piecemeal knowledge about systems. However, I strongly believe that system design is reflected in the communication structure of the organization who made the system, and manuals serve as a way to keep an order to this structure for users of these systems. So I see two additional issues popping up in this shitty manual world: a muddled core purpose of the system, and increased time spent maintaining and developing the system by the organization.
I think everyone can understand what I mean by a muddled core by taking a look at so-called "Internet of Things". Other examples are "feature creep" and Zawinsky's law: "All software expands until it can read e-mail."
The extra maintenance and development time, however, does not have a concise term that I know of. For this, I mean that since the idea of a canonical manual has been thrown out by seemingly everyone, the burden of explaining what a piece of technology's purpose, and, more importantly, method of operation is foisted upon every public-facing individual in an organization. If this isn't clear, think of the all of the times you've tried to figure out how to use software and think about how quickly you bypassed the official documentation, willingly or not, to instead visit the support forums. You no doubt found exactly what you needed, from someone else looking to do the same thing. But often the person explaining how to do that thing is a member of that organization, and they've given the answer to this to countless others before them. And this happens both unwillingly: some middle manager telling their underlings that budget cuts lead to letting go of the technical writers, so now the underlings get to manage the documentation and are part of the support team, also there's no opportunity to reduce their current workload to accommodate; as well as willingly: some developer creates a program, frobnar, and encourages every person to post their question to github because he simply loves to interact with the frobnar community, but over time frobnar seems to be less stable and doesn't seem to solve the problems it was originally created to solve, despite the github activity being off the charts.
And both of these issues can go away if everyone got their collective heads out of their asses and once again embraced the up front time and resource cost of designing a good manual.