Re: Problems and solutions not welcome
I do, and it's a problem, but I also see the opposite which is also a problem. For example, having a computer take a paper form and transfer it between different mailboxes, just like the original paper forms did. You could probably do things a lot more efficiently by having the computer read the form and use the contained information to decide how to direct it, but the original process says that Dave does that, so we just send everything to Dave and wait for him to send them. If we automated that part of the job, Dave could probably do a lot more of the tasks that actually require some thinking, but by not touching the process, we're not saving the time we could. The best approach is to frequently consider changing the process, and keep in mind all available tools when you do, but only actually change it when the change will or is believed to make a real improvement, then check whether it has. That's a lot more work than assuming that someone, whether it's the software writers or the people running the original process, will be much better if only the other group conforms exactly to what they want to do, so people don't always want to do it.