Information Quality - A shift in focus is imminent for all web workers

The Internet facilitates human conversation, and is manifested as mostly text and visual ques. The hierarchy and order of which users experience the text/visuals is coordinated by organizational executives, designers, and information contributors. Experience is mapped as paths through elements intended to inform or persuade the user. The user, however has their own conceptual model of information they are interacting with, referencing, and updating as revised information experiences.

The quality of information experienced can be segmented and analyzed into about dozen categories (metric or KPI):

* Authority
* Scope of Coverage
* Composition and Organization
* Objectivity
* Integrity
* Comprehensiveness
* Validity
* Uniqueness
* Timeliness
* +Relevance
* +Context

Web designers and managers usually contend with only "Composition and Organization", reorganizing, presenting, and contextualizing information assets across a wide variety of formats: Applications, HTTP sites, Marketing Collateral, Business Intelligence, etc.

The expected scope of web professionals is much too limiting, by only classifying individuals as technicians, we eliminate the recursive learning loop. The valuable information a developer discovers during the hours/days/weeks/months ruminating over the business processes you employ are generally wasted when not directly applicable to the current project task, but merely insightful as a concept. By improving the concepts for which we build organizations, processes, and products we can increase the quality, efficiency, and return on work already being accomplished. The quality of information directly correlates to a quality user experience - and vice versa during production/operation a quality: planning phase, execution phase, monitoring phase, and closing phase.

By evaluating and prioritizing why the information is important, we can optimize the message (hierarchy, order, content) for the most appropriate delivery.

Web professionals should facilitate the incremental improvement of information, with technology and creating conceptual models with abstraction and decomposition, before creating a software framework.

Ideas are much more flexible than code, and empty packages don't need decoration.

Keep up the great work,
-Ryan Gensel

twitter.com/readysetproject
www.readysetproject.com

(originally posted as a comment @ http://hobbsontech.com/content/recap-two-years-blogging-cms-migration-large-site-issues-and-more)