Excel is amazing for rapid data analysis and modeling, the flexibility it provides is exceptional when you're working alone and are trying to do one thing, fast

Excel is amazing for rapid data analysis and modeling, the flexibility it provides is exceptional when you're working alone and are trying to do one thing, fast. It becomes a pain when you're trying to use it to enforce workflows, across multiple people. The problem is that it works "well enough" that building a proper data model/system to replace the spreadsheet workflow is not going to get prioritized because it already sort of works and there are likely bigger problem areas in the org. It's a pretty classic problem where something enables you to solve a problem fast and well enough as to often preclude an excellent solution. On the flip side, if something is new/evolving and is handled in excel, it's a mistake to try to tighten it up in an application right away because you are going to end up evolving the app at a cost whereas evolving the spreadsheet would have been nearly free.