The headline chosen by the publication can give the impression that the selection of Excel as the data management tool over alternatives caused the problem, but the core issue appears to be poor record-keeping in general.
From the article: “The way Vowles and technical director Pat Fry reportedly recounted it, Williams has been using a spreadsheet that grew to include some 20,000 parts used to make its cars. […] Not only was this system amateurish and unnavigable (making it unsuitable for the hectomillion-dollar sport that is F1), it was also desperately lacking in important logistical info. […] The team reportedly didn't have a central resource that tracked what parts cost, how long they took to make, or even how many they had or where they were stored. This forced production staff to search for parts whose location hadn't been documented, wasting valuable time.”
Though PostgreSQL or another database tool would be a better fit for complex datasets, I’m curious if Excel could still effectively be used for a database like this one.
I’ve known a couple people who use Excel a lot for their work, and they’d probably tell me that having over 20,000 rows of data isn’t necessarily unmanageable, if the implementation is well-designed.
