If I understand workflow learning properly then I think that it will be a paradigm shift and will morph with "process change", instructional design, and user interface design to create an environment where training on new computer software systems is no longer necessary.

Here is my understanding of the characteristics of Workflow Learning. (It does not seem that complicated when you break it down.)

…is characterized by:

*Task support and work support fused into the aggregated business processes that make up the real-time workflow.
 
*Short, granular bursts of learning and workflow task support embedded at specific “nodes” of a business task.

*Continuous performance improvement and performance measurement.

*Workflow Learning Resource Arrays aggregated “around” (hubs) workers based on job roles.

*Learning incorporated into the workflow.

For instance, software will be developed with all of the following to make it more intuitive.

-all terms or phrases that a novice user may not know have a link to a definition that is contained in a list of terms that is also accessible separately from the links.
-a help 'assistant' <-- software not live
-contextual help
-decision assistance, if a user needs to make a decision in the program they can click on a button that says "help me decide" and they will be given explanations of the options and as well as consequences of making various selections.
-Included in the above example and wherever else it is applicable every help screen should show not only an example of the correct way to do something but also an example of how it would be done incorrectly