Planning season meant fifty workbooks, color-coded tabs, and a hero analyst who could merge them without sleeping. Everyone knew it was fragile. No one had time to fix it.
Platform thinking started small: one source for store clusters, one API for allocations, and a change log every merchandiser could read.
The political work mattered as much as the tech. Teams agreed on what could be edited locally versus centrally, and who could approve overrides.
Excel did not disappear. It became an interface to governed data instead of the database of record. That distinction saved the season.
The spreadsheet did not become chaos because people were careless. It became chaos because it worked for too long.
Planning season had its rituals. One person owned the master workbook. Another knew which tabs came from stores. Someone else copied regional overrides from an email because the official system was already closed. A color meant “final” in one workbook and “check again” in another. Everyone knew the process was fragile, but it had saved the business more than once.
The first platform step was deliberately small. The team did not ban Excel. They chose one shared object: store clusters. Those clusters had been copied, renamed, and adjusted across teams. A store could belong to one group in allocation and another in reporting. That created arguments later, when nobody remembered who made the change.
The new approach gave the clusters an owner, a change log, and a place where people could see the current version. Excel remained, but it stopped being the memory of the business. It became a working surface connected to a governed source.
The political work was harder than the technical work. Some teams feared losing flexibility. Others feared being blamed for old inconsistencies. The platform team had to say: local knowledge still matters, but local edits need visibility.
The lesson is not that spreadsheets are bad. In fashion, spreadsheets often carry speed, intuition, and survival. The problem begins when they become invisible infrastructure. Platform thinking starts when the business keeps the flexibility but moves the memory somewhere safer.
