3 ms·
I see this quite a bit in my current job. Question for you, how did IT sell this to the business folks (or the buyer)? Was this under the auspices of enterpri
by lhuang 17y ago
I see this quite a bit in my current job.
Question for you, how did IT sell this to the business folks (or the buyer)? Was this under the auspices of enterprise agility?
- edw519 17y agoWas this under the auspices of enterprise agility? Exactly. If a customer called in an order at 6:30 a.m., it didn't even get to the data base for 18 hours. So there was no same day shipping and if it had to be scheduled, the schedulers weren't even aware of it until the next day. Real competitive disadvantage. Worth spending millions to solve. Real time Accounts Receivables paid for itself by reducing Days Sales Outstanding by one day. But real time Accounts Payable? Made no sense. The IT solution was a blanket decision made multiple levels (and cities) away from the people who actually did the work. Go figure.
- lhuang 17y agoMan I see this so much at my job. Its amazing that architects don't catch things like this. Was there any requirements written up or charters that justified moving accounts payable to real-time? Its pretty inane, as you point out, how companies blindly apply strategies. Alot of times this is caused by simply cutting corners. If they would have had a body write up requirements (even high-level) for each department the would have caught this. Were there any problems with the actual implementation? If there are these kind of problems at the architecture level, I can only imagine the issues that came up actually initiating and executing the program.