Two lists always drift apart

Nobody sets out to keep double records. The second list appears because the first system does not quite do what someone needs. The CRM does not show the column sales wants, so there is an export. The accounts only catch up at the end of the month, so someone tracks revenue on the side. Each time a reasonable answer to a real problem.

A year later there are five of those answers, and the real work begins: every meeting opens with ten minutes of working out which number is the right one. A customer who cancelled in one system still gets a reminder from the other. A team member works from last week's version. It costs nothing on any invoice. It costs trust in your own numbers.

The answer is not one big system for everything. It does not exist, and whoever promises it is selling you a year-long migration. The answer is deciding, for each kind of data, where it lives. Customer details live in the CRM. Amounts live in the accounts. Appointments live in the calendar. You can show them anywhere, but you only change them where they live.

Write it down in a simple table: data, source system, who updates it. It takes fifteen minutes and settles more arguments than you would expect. Once everyone knows where the real number sits, the shadow lists lose their purpose on their own.

Banning spreadsheets does not work, because the need behind them stays. Treat every second list as a signal instead: what is someone missing in the source system? Usually the answer is small. One extra field, a filter, an overview that updates itself instead of by hand.

Fix that and the list disappears without anyone having to unlearn anything. And where two systems genuinely need the same data, let one feed the other through an integration, never through someone retyping it. Retyping is exactly where two truths are born.