Choosing an idea
When should I replace a spreadsheet with an app?
Lumos · Updated
Consider an app when a spreadsheet makes a recurring task difficult enough to justify changing how people work. Start by naming that difficulty. If the sheet does the job and people are comfortable using it, keeping it may be the better choice.
Common reasons to investigate a change include people needing different access to records, awkward data entry on phones, or a process that requires several people to pass work back and forth. Glide's spreadsheet-to-app guide describes these uses and how spreadsheet data can become an app's starting point.
Find the problem around the sheet
In our hypothetical designer example, a spreadsheet tracks projects waiting for client feedback. The designer checks it and sends follow-up messages. Before replacing the sheet, find out what causes the delay. A different place to keep the same list may leave that difficulty untouched.
Ask the person to walk through a recent task. Where did they have to copy information, chase a response, or correct something? What worked well? Write down what you actually saw and leave questions beside anything you're guessing.
Then choose one part to try as an app. For example, the designer could test whether putting a draft beside a specific question makes it easier for a client to respond. Use made-up records for the first experiment, and keep the existing workflow available while you learn.
Before moving real work, decide who can see and change each record, how existing data will move, and how you'll retrieve it later. Compare that effort with the benefit of changing.
In the Builders Handbook
Use finding problems to investigate the current workflow, then read make it work with real data before bringing people's records into the app.