In my first mobility role, I joined the team soon after they took over International Relocations and everything was tracked on a whiteboard.
It was simple, and at the time, the population was small enough that it worked.
As the program grew, the whiteboard was running out of space. Updates got erased if someone walked by too closely. Reporting was almost impossible.
Eventually, we moved everything to a spreadsheet. Honestly? At the time, it felt like an upgrade. It felt sophisticated.
The spreadsheet solved the whiteboard problem. We could sort data, add formulas, track dates and create tabs for reporting. It finally felt manageable.
Over time, something really subtle happened. The spreadsheet stopped being a tracker and started being the system.
At first, the spreadsheet made life easier. We could easily check an employee status, add any notes to a specific employee and pull the reporting we needed.
Then it became more layered.
We added new tabs, more calculations, new reporting requirements from leadership and special tracking columns. And as it grew, so did the workarounds.
Some formulas linked across multiple tabs. Some cells had to be updated manually. Some calculations only worked if you copied the row above exactly right. We all eventually learned the same rule: Oh please don’t break the formula.
You opened the spreadsheet carefully, scrolled slowly, and didn’t touch anything shaded gray. When I needed to make a major update, I made a backup copy first – saved it to my desktop. I definitely wasn’t going to be the one who broke the spreadsheet.
I wasn’t careless, but the spreadsheet had quietly become responsible for running huge parts of the mobility program.
Over time, more and more operational knowledge started living in this one file.
Employee data > move timelines > policy details > cost projection totals > allowances > population tracking....
And once that happens, the spreadsheet stops being tool. It becomes the infrastructure.
That’s the part I don’t think we realize while it’s happening.
First, the tracker is the database.
Then, the database becomes a reporting tool.
And the reporting tool becomes the operational process.
Eventually, institutional knowledge gets buried inside formulas only two people (one of whom can retire at any time) fully understand.
This isn’t because Excel is bad. It’s incredibly useful.
But mobility programs grow and at some point, the complexity outpaces the structure supporting it.
This is when things start to feel different.
Instead of relying on one spreadsheet to manage everything, Navi centralizes those pieces into one structured platform.
Employee records live in the system.
Policies and exceptions live in the system.
Cost estimates, dashboards, reporting, and documents live in the system.
Not across fifteen tabs maintained by institutional memory.
And that changes more than efficiency.
It changes confidence.
Nobody should feel nervous about opening the file that runs the program. Mobility work is complex enough. The structure supporting it shouldn’t feel fragile too.
At some point, every growing mobility program reaches the same realization: The spreadsheet was never supposed to be the system.