Most software should nowadays be easy to apprehend for an IT-literate community. We can hope that this becomes true for new software, but a lot of software is vintage.

Training should be reduced to how the software handles specific procedural approaches if it varies from the norm.

Training can be included into the documentation proposal itself in the form of an editorial strategy: e-learning is the high-end or this segment; sets of show-me-how-to documents are the low end.

The new paradigm is helping software editors to include educational procedures into their software. These are a combination of procedural wrapping of GUI and documentation.