Embracing the EPSS

According to the site EPSS Central, there are two “flavors” of EPSS:

• stand alone
• embedded

A stand alone EPSS refers to a data base that is independent of larger databases within an organization. In an embedded EPSS, the software becomes the EPSS and provides just in time learning. Workers are guided through steps in a process to solve problems.

While not really stating anything “new” (information was credited to Raybould and Gery, same as our text), I found the bulleted approach to key points more illuminating than our book.

I believe there are two reasons for the lack of acceptance/use of EPSS. I’d like to believe the main reason is because many are not aware of the potential of an EPSS. A secondary, and hopefully lesser reason would be contentment with the status quo.

EPSS will almost certainly become more prevalent in the future because of the exponential increase of knowledge. A static program is a dead program, as far as I’m concerned. Almost as soon as a piece of software is created and marketed, it’s obsolete. I think this is why many software designers are making the change to web-based products. Content can be updated easily, on-demand learning can be embedded within the product and, since all users are working from the same “version” (web-based), it’s probably a lot easier to field questions.

Another reason I feel EPSS are about to catch fire is because of the independent nature of most learners today. “On demand” is a phrase heard often in education...and with good reason. Learning in isolation doesn’t “stick”. Meaningful learning experiences, such as solving a real life problem through the use of guidance provided with EPSS, are the ones we tend to remember.