"To do A, did B, applying technique B', resulting in C, which you can use ongoing like C' "īriefing and internal doco - essentially the Literate Programming approach - remained in the system run book as "JIT Training" until the plant was retired, about another 20 years later. Handoff briefing was essentially training in the techniques behind the structural changes, anchored to the work done. Non-obvious introduction of encapsulation.Non-obvious reuse of large material models: like a large finite element model.Non-obvious alternative formulation of the core numerical modeling.I restructured a legacy mfg productiton program that wasn't tolerating further hack upgrades after near two decades in use. Personally, I don't understand work items absent the quality standards and success conditions, identified by name (with revs) with links even better and if the resources include tutorials & examples, say videos, better still. If only some kind of tool supported this.Associated the videos with tags, keywords, the work item they spawned from, links to related items, and maybe even a discussion thread on the guidance and the video.In particular, an unusual solution (like using one of those whacky KMS things), includes briefing on using that whacky new thing, and how that helped.Back in the day, this was one payoff from "reviews." Create brief-outs for work done, capturing how."To do A, did B, resulting in C." That's the best kind of contributed content. People are attracted to people they trust describing how they solved similar problems.Hook content creation in the KMS to doing the other work supporte from the KMS: "Here's how to pitch in guidance, examples, solutions and similar that you figured out in doing your thing.".helps do the work: "Here's how to wrangle our KMS to find support in it for what you are doing." If guidance, standards, examples, etc.If memorializing your work is required: "Here's how to wrangle our KMS to memorialize your work" is great if the KMS actually helps with that.Think of what you're creating as "JIT Training" while doing the work. People will grab tools n learn how to use them that they believe will help them do their work. How have you helped your user base learn the application?
0 kommentar(er)
