3 ms·
Honestly, I don't know anything about running a business. But if there's one thing I learned in engineering, it's the great if it ain't broke, don't fix it. (I
by aneutron 7y ago
Honestly, I don't know anything about running a business. But if there's one thing I learned in engineering, it's the great if it ain't broke, don't fix it.
(I know you're joking)But even if they're costly, if they keep the service running and bring in funds, why would anyone risk damaging their business and start cutting costs ?
- three_seagrass 7y agoIn grad school, my MBA-level technology course had a case on Zara and their POS software. The case problem was that the software was running on MS-DOS, had a janky text-based interface, but managed to work well for Zara's fast-fashion inventory. The 'right' solution for the case was to not change anything at all.
- meesles 7y agoJust curious how one would know if it was the 'right' solution without having tried other solutions? I find it hard to believe that any business would not benefit from moving from an ancient computer system to one with error validations and better tooling so that their boots on the ground can make less mistakes. Forget the cost of transitioning since at scale that's a whole executive job function, but purely from a day-to-day I don't understand how what you said can be true.
- three_seagrass 7y agoThat's why it was taught as a business case, because it forces you to look at the requirements for switching and evaluate the cost/benefit of the action. Even passenger jets still use floppy disks. AFAIK Zara did update their POS system later though, to be more compatible with payment device hardware.