re: not a mistake
We're a small company that has brought in some new people at the mid-manager level and these newbies are trying to make a lot of changes to our workflow without understanding how we work in the first place. It has simply created more paperwork for us and a lot of resentment towards the new managers. While we like their ideas, and there are some good ones, us IT folks need to see where these tools fit in with our process. Trying to fix a critical problem at a client (hospital software) does NOT mean that we need to "storyboard" the process, get managerial approval of our process, then contact the client for "buy-in", then finally implement the fix. Often our immediate fix is, "Hello IT, have you tried turning it off and back on again?"
