Differences

This shows you the differences between two versions of the page.

--- training [2018/11/14 21:14] – external edit 127.0.0.1
+++ training [2018/11/28 15:12] (current) – Struct data changed splitbrain
@@ Line 1: / Line 1: @@
-===== Training =====
+====== Training ======
 Spending time and resources to produce training materials for an unresponsive prospective user community will actually impede the adoption and long-term success of your knowledge base.
-==== Usage ====
+===== Usage =====
-Wiki contributions are down or stagnant. You recognize an abundance of [[Do+it+all|Do It All]] , [[Leech|Leech]] , [[Wikiphobia|Wikiphobia]] , and possibly [[ContributorForHire|ContributorForHire]] people anti-patterns. People complain that it's too difficult to get their ideas into the shared knowledge base. You (or your established IT infrastructure) responds by addressing their apparent demands for more **training** , simpler examples, and more technical documentation.
+Wiki contributions are down or stagnant. You recognize an abundance of [[Do It All]], [[Leech]], [[Wikiphobia]], and possibly [[ContributorForHire]] people anti-patterns. People complain that it's too difficult to get their ideas into the shared knowledge base. You (or your established IT infrastructure) responds by addressing their apparent demands for more **training**, simpler examples, and more technical documentation.
 ==== Example ====
-  * wiki [[Champion|Champion]] resources are spent making training pages, duplicating or simplifying application documentation, and making walkthrough videos or presentations (especially in 3rd party tools rather than the wiki itself)
+  * wiki [[Champion]] resources are spent making training pages, duplicating or simplifying application documentation, and making walkthrough videos or presentations (especially in 3rd party tools rather than the wiki itself)
   * users attend training sessions, but this does not translate to contributions
   * users don't even attend training sessions but complain that the application is 'non-intuitive' or 'complicated'
@@ Line 22: / Line 22: @@
   * some IT solutions are about technical training rather than 'teaching'. 'learning' happens when the student has the triad of //motivation// , //information// , //practice// . You are lacking //motivation// and perhaps //practice// . These can't be mandated easily, but rather encouraged.
-==== Alternatives ====
+===== Alternatives =====
-  * Use peer tutoring, encourage (wiki [[Champion|Champion]] s)
+  * Use peer tutoring, encourage (wiki [[Champions]])
-  * Use wiki [[Magnet|Magnet]] , wiki [[Scaffold|Scaffold]] or other  [adoption patterns]  to demonstrate utility and encourage use.
+  * Use [[Magnet]], [[Scaffold]] or other adoption patterns to demonstrate utility and encourage use.
   * Be patient.
   * Encourage resource spending on training in **response** to user demand only, not as a means to promote usage.
   * Consider targetting 'philosophy' campaigns directed at problematic trend-setters rather than technical training
-==== Related Patterns ====
+===== Related Patterns =====
-==== Suggestions? ====
-  * This pattern could be part of a new  [PuttingTheCartBeforeTheHorse]  super-anti-pattern (which combines a number of similar timing-related patters)
-  * Could also be a  [HowBeforeWhy]  super-anti-pattern, or a  [WhatThenWhyThenHow]  super-pro-pattern, which promotes a progression from [[Scaffold|Scaffold]] / [[Magnet|Magnet]] patterns encouraging participation, -> continued participation demonstrates philosophy/cultural change -> training and documentation support and enable the first two).
 ---- struct data ----
+classification.type  : Anti-Pattern
+classification.focus : Adoption
 ----