It usually does once it has been completed. But, during development, it takes interaction among developers to bring a large project together. Projects are mismanaged and so are meetings. Software efforts are often made more difficult through the use of untalented systems designers and software engineers. Meetings do need to take place when changes must be made across numerous subsystems.
I can't speak to non-software related hiccups related to computer technology; however, I suspect that is mostly due to users not understanding the software they use and sometimes their own processes.
In my experience, a typical software product is sold, then it’s used, and users have to put up with regular inefficiencies of various kinds until the company scraps it and then gets another flawed system.
I know what I’m about to say might touch on sensitivities, but let’s be men. We can handle it:
The idea that digital technology is flawless is a lot like a religious belief.