At some point, an app gets complicated enough that starting over sounds pretty good.
Years of added fields, old reports, and “temporary” fixes will do that. But a rebuild is a project of its own, and it’s worth understanding what you’re taking on before making the decision.
A focused review can help you work out which parts need attention, which still serve the business, and where a larger redesign makes sense.
1. What does the business need today?
Start with the current process. List the core jobs the app supports and the places where it falls short. Be specific: “We can’t see which orders are waiting on approval” gives you something to investigate. “The app is outdated” leaves a lot open to interpretation.
Include the people doing the daily work. Their workarounds can reveal requirements that never made it into the original design.
2. How does the data fit together?
Review the main tables and their relationships. Where does customer information live? How do projects connect to orders? Are people entering the same information in multiple places?
If the structure no longer matches the process, changing forms alone may have limited value. If the structure is sound, you may have a useful foundation to build on.
Also consider historical records. A redesign needs a plan for how people will find older information and how that information relates to new work.
3. What depends on the existing app?
Map the automations, integrations, documents, and reports that rely on it. Include any exports or outside processes your team uses regularly.
For each important dependency, identify what starts it, what it changes, and who notices when it fails. This helps you estimate the scope of a rebuild and avoid overlooking a quiet process that runs in the background.
4. Who needs access to what?
Review roles and permissions alongside the workflows they support. People may have changed responsibilities since the app was first built, or new departments may now rely on the same information.
Document the access each role needs and how it should be checked during testing. Include the accounts and connections used by integrations.
5. Who will maintain the result?
A new app needs an owner, just like the existing one. Decide who will handle changes, investigate issues, and keep documentation useful.
If your internal builder will take over after launch, involve them in the design. If outside help will be ongoing, define how requests and priorities will be managed.
Turn the findings into a decision
Group the work into immediate fixes, improvements that can happen in stages, and structural changes that need a larger plan. Compare the effort and disruption of improving the current app with replacing it.
You may find a rebuild is justified. You may also find that a few targeted changes address the biggest problems. Either way, you’ll have a clearer basis for deciding.
Start with a Quickbase app review
Douglas Media Group can help assess your existing application and work through the options. Tell us what the app handles and why you’re considering a rebuild. We’ll discuss a practical scope for the review.
Based in Wendell, North Carolina, we serve Raleigh and the greater Triangle and work remotely with businesses across the U.S.
