Your app has the fields. It has the reports. You even showed everyone how to use it.
So why is someone still keeping a separate spreadsheet?
Before you schedule another training session, ask them to show you how they actually do the work. There may be a good reason they’ve found another way.
Watch a real task from start to finish
Pick something ordinary: entering a customer request, updating a job, or finding work that needs attention. Have a person who does that task walk you through it using a typical example.
Notice where they pause, switch screens, ask a coworker, or copy information somewhere else. Ask what they expected to happen at those points. You’re looking for the friction that has become so familiar nobody mentions it anymore.
A useful question is, “Which part of this do you wish you could skip?”
Give each person a clear starting point
A manager reviewing open projects and a field employee updating one job have different needs. If both land on a screen full of every possible report, finding the right place to work becomes another task.
Review what each role needs to see first. For someone handling assignments, that might be today’s work and items waiting on a response. For a manager, it might be overdue jobs and exceptions.
Start with the decisions each person needs to make, then organize the screen around those decisions.
Look at the questions your forms ask
A form can be technically complete and still be hard to use. Field names may make sense to the builder while leaving everyone else guessing. Required information may not be available until later in the process.
Work through the form in the order the user receives the information. Check which fields they need at that stage, which labels need clarification, and where a short instruction would help.
Before hiding or removing anything, review how it supports other workflows. A cleaner screen still needs to preserve the information the business depends on.
Make reports lead to action
A report named “Open Items v3 Final” probably means something to someone. Finding that someone shouldn’t be part of the workflow.
Use names that explain the purpose, such as “Jobs Waiting for Approval.” Review whether the columns and filters help the person decide what to do next. Include enough context to distinguish an urgent exception from an item that’s moving normally.
Fix one recurring frustration
Choose a task people perform often and agree on what a better version would look like. Fewer screens? Less retyping? A clear way to find the next assignment?
Let the people doing that work try the change before rolling it out more broadly. Their feedback will help you distinguish a useful improvement from a screen that simply looks nicer.
Need another set of eyes on your app?
Douglas Media Group helps review and improve existing Quickbase applications, including forms, reports, dashboards, and workflows. Tell us where your team keeps getting stuck, and we can discuss a focused starting point.
Based in Wendell, North Carolina, we serve Raleigh and the greater Triangle and work remotely with businesses across the U.S.
