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

The DATA Act Driving Grant Management Automation

The Digital Accountability and Transparency Act enacted in May 2014 calls for making spending data available in open, standardized formats to be published online.  It is a continuation of transparency initiatives and lessons learned with experiences such as grants.gov, the 2009 economic stimulus under the Recovery Act and the spending site USASpending.gov.

Government grantees will have significant new administrative responsibilities.  Many organizations that were tracking grants in spreadsheets or documents will have to adopt more sophisticated automated grant management systems such as Microsoft Grants Manager to keep up with reporting rules.

For profit companies will lose some privacy as a result of this law.  Grant recipients will be required to disclose information including officer salaries.

Continued improvements to publishing grant opportunities such as grants.gov may make it easier to find grants. These reforms together are designed to improve the effectiveness of grant prog…

Dynamics 365 for Government Contractors (GovCon) Frequently Asked Questions (FAQ)

One of InfoStrat's most popular solutions is Dynamics 365 for Government Contractors (GovCon).



Here are some answers to frequently asked question on this solution:
Can I add new fields to the solution?  -- Yes, the solution is fully customizable and you can add your own new fields to any form, view or report.Does Dynamics 365 for GovCon work on mobile devices?  -- Yes, Microsoft offers mobile apps for all the most popular platforms including iPhone, iPad, and Android phone and tablets.Does Dynamics 365 connect with bid data systems such as Deltek and Onvia?  -- Some information services, such as Onvia, offer integration with Dynamics 365.  Others require third party solutions such as the InfoStrat integration with Deltek GovWin IQ.What do customers typically customize for their unique requirements? -- Not all contractors follow the same steps in the capture process.  Most clients will tailor the business process to add or remove steps in order to match their sales methodology.  Of…

Getting the Most from Dynamics CRM Online -- Synchronous v Asynchronous Workflows

This video shows highlights from the InfoStrat March 2015 seminar "Getting the Most Out of Dynamics CRM Online" presented by Dmitri Riz, the leader of the InfoStrat Dynamics CRM practice.  This is the second part of a series of blog posts.  The first is Benefits and Cloud Thinking.



In order to make your CRM workflows perform best, you need to understand the difference between synchronous and asynchronous workflows so you can choose which is appropriate for your applications.



Synchronous workflows are a new feature that was introduced in Dynamics CRM 2013.  Unlike asynchronous workflows which are sent to a queue, synchronous workflows execute in a single transaction. 

This means you can eliminate the need for many plug-ins which were created for previous versions of Dynamics CRM.

You may want to disable synchronous workflows during import operations, because they will could be triggered by each new record and significantly slow down the import process.