8 ms·
> Since these policies so rarely help improve or ship features, it’s just an ever-increasing source of productivity loss from the perspective of someone who wan
by jiggawatts 5y ago
> Since these policies so rarely help improve or ship features, it’s just an ever-increasing source of productivity loss from the perspective of someone who wants to get stuff done. When internal politics are complained about, this is typically the root cause.
"Why do I have to fill in this mountain of paperwork, in triplicate, just to get permission to do this basic activity that is an essential part of my job, and hence the permission being granted is a foregone conclusion anyway?"
"Eleven years ago a guy named Bob tried something similar and screwed up terribly."
"But not the same?"
"No, but similar. So anyway now we have a 'process' to make sure nothing like that will ever happen again."
"Is Bob liable to make the same mistake?"
"Oh no, he's learned his lesson. Also, he was fired a year later, so he's not around anyway."
"So, has anyone made the same mistake since?"
"No."
"Do you think I'll make the same mistake?"
"I don't believe so, no."
"So why do I have to fill out the paperwork to avoid making a mistake we all know I won't make, especially now that I've been made aware of it."
"Just in case."
"Just in case, what?"
"Well, how do we know that you won't make mistakes? We have to have proof, some sort of written evidence."
"But you can't prove ahead of time that people won't make mistakes! People don't make mistakes on purpose, so no amount of paperwork will ever stop mistakes happening."
"You're just being argumentative now. You're not special, everyone has to do the paperwork."
"Why everyone? You just said only Bob ever made the mistake!"
"HR told us that we can't make rules just for Bob, so everyone has to follow the same rules. That's fair."
"But you don't need the paperwork any more, you got rid of Bob!"
"Yes, but the process has been established, it would take a lot of time and effort -- and paperwork -- to change it now."
"It's less than making everyone jump through unnecessary hoops just to do their jobs!"
"Maybe, but I'm very busy. Back-to-back meetings to discuss important matters, like how several staff are behind on their paperwork and may need to be disciplined."
etc, etc, etc...
I've had conversations like that -- nearly verbatim -- at several organisations in contexts such as:
"Why does it take four weeks to add a firewall rule?"
and:
"Why is the minimum permitted change turnaround time two months?"
and:
"Why can't person responsible for system X have access to said system X?"
- Jensson 5y agoThe real answer is typically "These rules is why I have my job, I can't remove them since I want to stay". It is like when you automate 90% of someone's job they usually don't get happy. This is the same thing but the opposite, bureaucrats de-automate tasks to create new jobs.
- NikolaNovak 5y agoThe terrifying part for me,is that by now I've been on both sides of that conversation multiple times - and the third,less seen side, where the paying client explicitly and specifically asks and expects you to implement such a Process as part of "lessons learned". It's noble to say "ouch! well let's make sure we don't do THAT again!", but yeah ; over time the processes and procedures do expand ad infinitum :-/
- ekimekim 5y ago> expects you to implement such a Process as part of "lessons learned". I sometimes refer to this as "scar tissue" - an over-response to a trauma that causes ongoing issues more so than the initial injury.
- PeterisP 5y agoLooking back at a megacorp experience, I could read most of your exact text but replacing the Bob's mistake with Bob's intentional fraud - and then the process does start making sense. People do make mistakes on purpose; sure, a small minority of people, but in a large organization that will be multiple cases every year.
- Aeolun 5y agoDoes that justify wasting hours upon hours of every employees time per year? Somehow businesses do not look at this kind of thing as ‘a cost of doing business’.
- netjiro 5y agoIt really does not. Conservative sketch: assume 10k ppl, avg cost $50k/y, process/procedure/policy overhead 30%, is 150M/y. For that to make sense you'd need 15x $10M fraudulent or single point stupidity errors per year. And that is assuming that the bullshit actually catches most errors. In my experience the 30% is conservative, from my measurements of large orgs. High overhead does not reduce errors, instead it increases both frequency and severity. It also kills innovation, thinking, adaptability, etc.
- jiggawatts 5y agoThis pales in comparison to the tender process required of government. The logic goes something like this: Before: In the past, companies would bribe bureaucrats in order to land sweetheart deals. There was not enough competition and hence the government was paying too much. After: There is now a 10% chance of landing a contract after a month of paperwork. Only Accenture, Deloitte, and a handful of their direct competitors can afford to risk the time and effort required to win a contract. They don't actually do anything, they just subcontract everything while skimming their cut off the top. This isn't corruption however, it's just a nice legal business transaction. I regularly see projects that might take 1 guy 6 months balloon out to 20+ people for multiple years across three orgs and costing tens of millions of dollars, all in the name of "avoiding corruption". The best part is that because the projects end up costing so much, they have to be "taken more seriously", which means that the tender process must be "thorough", which means more papework and more managers and paper pushers on both sides of the fence. There's an exponential cost to this a bit like the rocket equation...
- andi999 5y agoOne shd also consider that the process is often the only thing which really holds large megacorps together, there is nothing else. You could have a turnover of all staff, as long as you keep the process it is still the same megacorp. That's probably the reason management often says 'process over results' because it is the heart of the company.
- Aeolun 5y agoThe stupid thing is that the reverse also happens. I happen to have a random conversation with a business member that is complaining about something ridiculously simple in our system, and that it’s been in the pipeline to fix for months. My mind boggles, since it’s literally a 5 minute fix, and somewhere over our head some managers have been protecting their little fiefdoms at the expense of this poor guy that does something stupid by hand for an hour every day. 5 minutes later the fix is deployed, and we just saved 200 hours per year of pointless labor.
- refurb 5y agoOne problem I’ve seen is someone implements a process, a really nice process, but has zero clue how it fits into the big picture. It’s clearly designed as if it’s the only process someone needs to complete. What you end up with is a half dozen “really nice processes” all stacked up and suddenly what took 1 week now takes 4-6 weeks to complete. Each process is justifiable on its own but put together make no sense at all.
- AnimalMuppet 5y agoEveryone sees that the check could have saved them that one time. Nobody sees the cost of the check, applied over and over and over...
- impjohn 5y agoReminds me of that anectode where the father would ask the son to take the clay pots and go fetch water from the fountain. He would yell at the son to not break the pots and slap him. When people asked why he punished the son before even going, he said: "What's the point of punishment after he breaks the pots?"