batteriesincluded.com · Questions & Answers

We built an internal tool with AI, but our team still uses the old spreadsheet. How do we get people to switch?

Treat this as a workflow and training problem before requesting more features. Watch employees complete a real task in the new tool. Find out whether the spreadsheet still offers something essential, such as faster entry, easier corrections, or visibility the application lacks.

The useful EOS principle here is simplification: make the process easier to follow, not merely more digital. An easy-to-use interface and practical training matter as much as the software itself.

Give one process owner responsibility for the transition. That person should distinguish genuine workflow gaps from preferences that do not justify maintaining two systems.

- Fix obstacles that prevent people from completing the agreed process.
- Train users on actual tasks, including mistakes and exceptions, rather than giving a feature tour.
- Set a clear cutover date and explain where new records belong afterward.
- Make the old spreadsheet read-only when operational and recordkeeping requirements allow.
- Provide a visible route for questions and unresolved issues.

Measure whether the work happens in the tool, not just whether employees log in. Track completed transactions, work still happening outside the application, and recurring support requests. Bring persistent barriers to the Level 10 Meeting Issues List for resolution.

For a Batteries Included engagement built with Lovable or Replit, adoption work should be part of the build scope. The recommendation is not to force a switch immediately. Remove legitimate obstacles, establish one working system, and stop making duplicate entry the permanent compromise.

Category: Internal Tools

← All questions