3 ms·
Our PIM team disagrees with that take. They enjoy the PIM interface and Excel doesn't come close to the data hierarchy and relationships our systems provide. An
by oneplane 2y ago
Our PIM team disagrees with that take. They enjoy the PIM interface and Excel doesn't come close to the data hierarchy and relationships our systems provide. And that includes reporting, vendor exchange and internal integrations.
But perhaps you're missing the point here (like plenty of others): it is not about handling a few offline rows, it's about re-inventing established systems that have proven their value and risk mitigations. We don't want someone to setup a collection files to build a homebrew PIM or ERP or CRM because they feel like it, disconnecting themselves from the organisation and teams they work with. In most cases, single player data silos are bad.
- eviks 2y agoSure, agreeing would be a fireable offence "And anyone who wants to build a system where it is, is not working for us." But the non-PIM teams agree, and they are a few orders of magnitude bigger and more important.
- oneplane 2y agoNo, they don't. Our finance teams, accounting, B&S, purchasing etc. also all disagree with your take. There also is no "fireable offence" structure here, we aren't a US-company and we have strong labour protections here. They themselves chose how they want their processes to work, and none of them ended up with Excel in the main process loop, anywhere. Perhaps this is something you cannot imagine, but over here, this has been the standard for years. And it pays dividends. This does not mean excel doesn't exist or isn't used outside of the main processes/loops/flows. But that is what I wrote in my first comment here, which people seem to skip over.