This is a place for news, questions, discussion, and rants about Workflow Learning.

Click the blue "Subscribe" button and add your email address. I recommend the "Digest" option. You can click the same button to Unsubscribe at any time. By the way, your email address is secure here. I've used QuickTopic for years and have never received spam from the addresses I use here.

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

Thanks, Rich. I agree with most of what you write, but I'm a little less restrictive. The "Workflow Learning Resource Arrays," as Sam Adkins originally described them, include links to live experts as well as software. As a living system, every screen may not have examples and counter-examples: some of them will be work-in-process.

While I still stumble with the description, I find that examples help. Differentiating Workflow Learning from EPSS, I point out "Unlike EPSS, Workflow Learning is contextual, dynamic, and aware. Workflow Learning is most likely personalized to the individual worker and his role; EPSS treats everyone the same. The Workflow application is aware of what’s happening in the business, e.g. “That item is out of stock” or “We are no longer offering that policy to young adults in Southern Connecticut.” The Workflow Learning is probably embedded, the EPSS bolted on. The Workflow environment connects the worker to her colleagues. The Workflow environment automatically learns about the learner and adds to his experience portfolio. Workflow Learning is not a separate system; it is part and parcel of the work itself."

Some of these features are optimal but optional.

How do other people see this?

hello
its zia wth you hopefully you all will be fine and in best of your health. i need some nformation about the market of the workflow system can anyone help me in this regard. i will be very much obliged.