Creating content in SelfGuide is intuitive and efficient, using a recurring approach helps reaching goals and to keep going towards success. Based on customer experience and feedback, a best practice is set up to help all editors to structure the process of content creation. It helps to be sure the created content fits the need, the content is 'correct' and used by the organization.
The first step in the process is to determine the scope, it details what content is needed, the purpose is serves and the people who will benefit.
Two approaches are seen in practice:
Creating content with a good quality requires certain aspects:
To fulfill the first aspect, the owner should be known and aligned. The owner can point out who will be a good editor, optional review created content, make choices when there are questions about details, etc. Not having a owner can lead to discussions and eventually the wrong instruction. Often seen owners are managers (team or process) and functional application engineers.
The second aspect has all to do with aligning the content to the audience. Content made with too much detail feel unnecessary and scare off, while content with too few details leaves questions open and is not helping at all. By knowing the audience, their educational level, their role within the organization and their prior knowledge, helps to determine the right tone of voice, the level of detail, etc.
During this phase, editors will deliver the required content by creating recordings, finishing Instructions and structuring Instructions in User Guides and / or Courses. These steps are straight forward, especially when working often with SelfGuide, but still requires attention.
Using content to guide and learn is easier when it's consistent. The way SelfGuide is build and behaves helps to keep consistency in content as all content looks the same and works the same. As editor, or even team of editors, consistency increases with a shared tone of voice like:
When recording and post-processing to finish the Instruction, be aware of the best practices like working on the primary screen, keep titles short, add applications and tags to Instructions, censor sensitive information, etc. These are just a few best practices, read the Getting Started and Best Practices articles for more information. Another option might be to enroll for a SelfGuide training to get familiar with all functionality.
Is content finished, reach out to a few pilot users to gather feedback. It's a common mistake to think instructions are obvious for the user and are in line with their need. SelfGuide makes it easy for a user to deliver feedback on Instructions. As and editor, just share a few links with a group of users and ask them to use the feedback function to keep things simple.
The option to be guided and having the ability to gain knowledge does not imply that it will be used directly and on a frequent base. It starts with awareness and requires repetition to change behavior towards more self-sustainability. Especially the repetition helps to change the behavior and culture, as long as people are not directed to an instruction when somebody asks as question, the person asking will not learn another way to get the answer.
A few takeaways: