PS,Pointedstick wrote:It sounds like you're describing a system that is heavily automated and could be further automated, perhaps taking care of transporting the samples itself. I don't think this counts as "bureaucracy." If would be a "bureaucracy" if instead of submitting jobs to a software tool, you sent emails to your manager, who forwarded them to his or her manager, who had to get approval from billing, who had to ask what it was for, which percolated down to you again, and when you got approval, you had to go to the shipping department, and get approval to create a shipping label, and on and on and on...TennPaGa wrote: Let me give a simple example that I encountered today at work. I'm currently investigating different polymers to gauge their suitability for 3D printing. I've subjected these to various treatments, and I want to see if, and how much, some physical properties have changed as a result of the treatments.
There are 5 different measurements I need, all performed at different physical locations manned by different people.
So I divide up the sample myself into 5 smaller bags. I connect to our laboratory information management system (LIMS), and create "jobs" where I specify the tests I want done. LIMS will then print out barcoded labels, which I retrieve, place on the bags, and then deliver them to the appropriate labs, making sure I scan them in.
From a completely selfish viewpoint, this is bureaucracy.
The most efficient thing, from my standpoint, would be to completely eliminate the LIMS system: I simply take one bag of the stuff to one of the labs, verbally tell the analyst what I want done, and when he is done, he takes it to the next lab, where that test is done, etc.
Of course, if everyone took this same "micro-efficient" route, there would be chaos.
The system you describe in your example works because you are presumably efficient and make good decisions regarding which samples are worth testing and which offsite locations are appropriate to send the samples to; you don't need someone constantly checking up on you to make sure you followed the rules or made good decisions. If you were a poor employee, then probably your manager would institute a policy that all of these jobs had to be approved before being requested, and the approval would be subject to a review process, and so on and suddenly, you're in a bureaucratic hell.
In the end, bureaucracy only really exists as a verification system. Inputs that are naturally correct require no verification and can be hindered by it, when applied to excess or in a manner that slows things down. So if we are plagued by bureaucracy, that's really a sign that we are not doing our jobs correctly.
I think you're just describing the difference between "good, modest bureaucracy," and "bad, heavy-handed bureaucracy." Having to follow certain processes to produce products or ideas in a way that works within an organization is "bureaucracy." If you see a work-flow chart, that is "bureaucracy." Whether it's done in a balanced way or not is up for debate.
Producing financial statements doesn't cease to be "financial accounting" just because you have a bunch of well-designed information systems that folks use consistently to produce said statements. It's just being done right within the context of what the business desires.
I think we're getting into semantics here, a bit. We all know there's a difference between "effective information systems/controls and processes" and "mind-numbing, inefficient, soul-sucking bureaucracy." If my government (or a company) is going to lean towards the latter, I truly hope it is for truly important control/security/risk priorities rather than allocating another pen to Bob in Accounting. The point-being, the profit motive doesn't eliminate the latter in the private sector. The government, being something larger and in need of more oversight than a private company, should probably be expected to have more of that kind of stuff.
But to tech's point that "women don't do much of the more productive work." Well bureaucracy IS, by definition, and extremely important function to corporations and profit-seeking entities, and they have no reason to pay more for it than it is worth. Women would probably be naturally better-wired for that kind of work than something more unruly, but there's no reason to think they're job is worth anything less than they're paid in relation to what men are made for making the widget.
If tech held consistently to his capitalist philosophy, he'd probably quickly realize that just because something doesn't directly produce some desired end-output, that doesn't mean that it is not "of value." Especially since one company's "end output" is another company's "input, requiring bureaucratic management of some sort."
I think tech is forgetting the difference between "politically incorrect" and just simply "incorrect."