Skip to main content

Consider the Overhead Costs of Tracking Data


When I was meeting with one of InfoStrat's clients recently, we were discussing what fields to include in an online application form for a new system.  Over the years, the form had grown to 29 pages, including several pages of legal terms and conditions which required no user input but required review and acceptance.

We went through the form page by page to determine which fields were needed, and identified many fields which had become obsolete due to changes in business rules and requirements.

This reminded me that there are hidden costs to adding more information to forms, even though storage may be cheap and it's easy to add new fields. This cost is recognized in industry and government. The Paperwork Reduction Act (PRA) of 1995 requires that U.S. federal government agencies obtain Office of Management and Budget (OMB) approval before requesting or collecting most types of information from the public.

Here are some questions that can help you identify and eliminate unneeded fields:
  1. How often is data entered in this field?  If it is seldom used, it could be an indication that the field is not needed.
  2. Do you perform calculations on the field?  
  3. Does the field cause the use to repeat information which is sought elsewhere on the form?
  4. Do users understand what is needed in the field?  If the field leads to inaccurate entries, try to find ways to clarify your intentions or delete the field. 
Brevity is desirable. Longer forms can discourage users and result in abandoned transactions as well as extra help desk calls. Adding new fields to a form may also trigger changes to your reports, views and dashboards.

When you refresh an online system you have the opportunity to improve your business processes and create a better experience for users. By analyzing your data inputs you can identify problem areas and correct them. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

Updated 8/15/2022 To understand Microsoft Dynamics 365 (formerly Dynamics CRM) and Power Apps, you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises.  These concepts also apply to Power Apps.  The main difference is that with Power Apps you are not starting with a Microsoft app but more of a blank canvas for your custom apps.  This post introduces some key terms and how these concepts are important for planning your implementation. While Dynamics 365 is still available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds in several countries. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uni

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Switching from Microsoft Dynamics GP to Dynamics 365 Business Central

Updated 4/6/2022 Register for our webinar  "Great Plains to Microsoft Dynamics 365 Business Central for Nonprofits." Source: https://docs.microsoft.com/en-us/dynamics-gp/terms/lifecycle This year Microsoft announced a date for the end of mainstream support for Dynamics 365 GP 2018 accounting software.  This spurred some blogs and customers to think that they must switch from Dynamics GP to another product by January 10, 2023 when mainstream support ends. It turns out that this announcement does not cover the latest version which is named simply Dynamics 365 GP (without a year in the product name).  Dynamics 365 GP will continue to be developed and supported indefinitely. Without support, customers cannot continue to use accounting software because it must be maintained in order to comply with changing tax and regulatory requirements.  Microsoft ships these updates in the June and December releases, and adds hotfixes and other new features in an October update.  This stay of