Process gaps can leave assumption-based or TBD (pre-event) data incomplete

In many processes, assumptions are made and information is stored in advance of hard facts or the actual event/instance. Afterwards, revision of the data may be flawed, overlooked or not deemed worthwhile.  In such circumstances, information can be inaccurate or may have been left out. 

An example is names of people attending a seminar.  An atendee preregisters himself and one additional colleague, to-be-determined.  At the seminar organizers may or may not capture the actual name into their system.  A registration sytem might be designed in many different ways to handle this use case.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s