When a team builds a spreadsheet beside your product, do not call it misuse. Call it research.
The spreadsheet exists because your product has a gap: a missing field, a missing status, a missing export, a missing way to compare two things at once. Users do not build shadow systems for fun. They build them because the official system is too rigid or too slow.
Read the spreadsheet
Look for three columns:
- The column your product does not have. That is usually the feature.
- The manually edited status. That is usually the workflow state you failed to model.
- The notes field. That is where edge cases go before they become requirements.
The spreadsheet is often ugly, duplicated, and full of stale rows. That does not make it wrong. It makes it honest.
Product teams love clean systems of record. Operators love systems that let them finish the day. The shadow spreadsheet is the negotiation between those two needs.
Before you replace it, understand why it survived.