Rajeev Khandelwal's industrial and financial background provides a useful context for the spreadsheet that quietly runs a corner of an enterprise. An unofficial file may create risk, yet it may also perform work the formal system does poorly. Removing it without understanding its purpose can make the process less reliable rather than more controlled.
Ask what the file makes possible
The sheet may reconcile mismatched records, track a customer promise or translate technical units into a management view. Its owner often understands a gap that has never reached the system team clearly. Starting with the task, rather than the tool's unofficial status, helps reveal why colleagues continue relying on it.
Identify the fragile features
A manual file becomes vulnerable when formulas are unclear, versions multiply or one person controls the only copy. Those weaknesses deserve attention even if the underlying task is legitimate. The immediate response can preserve useful work while improving access, documentation and checks, instead of forcing a hurried migration that introduces new errors.
Design the replacement around use
A formal solution should reproduce the valuable function and remove the fragile parts. Involving the people who use the workaround helps avoid a technically neat replacement that misses the practical requirement. A short period of comparison can show whether the new process produces the same information with less effort and fewer unexplained differences.
Recognise the knowledge contribution
The employee who created the workaround has supplied evidence about how the business actually operates. Treating that contribution respectfully encourages future disclosure of process gaps. A stronger institution does not depend on hidden tools, but it learns from them before deciding which capabilities belong in its official systems and operating records.
