2 ms·
It seems this is a common problem with larger organizations, that everything turns (corrupts) into a process. I've even seen processes for following processes.
by ZaoLahma 2y ago
It seems this is a common problem with larger organizations, that everything turns (corrupts) into a process. I've even seen processes for following processes.
To make the problem worse, nobody dares to remove from a process as that would mean they would be accountable for the consequences of the "missing steps", and at the same time adding to a process is almost always safe - another step in a process to clarify or verify can't really fail and having contributed to the process work in a process driven organization looks fantastic on your yearly review. So we get more and more processes that are perpetually growing in scope.
The long term damage that heavy processes do, what I've seen first hand, is extreme stagnation. Even simple and straight forward improvements are avoided if it means that you need to produce ridiculous documentation that nobody will ever need, or seek approval from a (very busy) group of people who contribute nothing other than checking that you followed the processes.
- hinkley 2y agoWhen I remove steps I brag about it. I don’t know or recall if I ever consciously reasoned that as trying to normalize that activity, but that is certainly what I’m doing. Shorter processes in clock time matter more than step count, but it’s hard to do one without the other.