Automate Training Activities
In this webinar recording, I explain (at a high level) how you could make self-contained employee training courses that automate the employee training experience.
How to Create Killer Documentation
Topics
-
2. A recipe for great documentation 7
-
3. How to write your documentation 1
-
4. Managing your documentation 1
-
5. Other articles 5
- 5.1 How to figure out why people don't use your documentation
- 5.2 Creating engaging documentation: Motivation matters more than Learning Styles
- 5.3 Evaluating the cost of a documentation system
- 5.4 Why your documentation needs to be online - not locked in a PDF or Word file
- 5.5 Transferring your client's processes to ScreenSteps: The first 30 days for Business Process Outsourcers
-
6. Creating a Customer Support Site with ScreenSteps 2
-
7. List of videos 12
- 7.1 How to get employees to read your docs
- 7.2 Choose an Outcome
- 7.3 Automate Training Activities
- 7.4 Organizing Your SOPs and Policy docs
- 7.5 How to Customize the 2015 (Old) Site Template [Webinar]
- 7.6 Decrease Support Tickets
- 7.7 Create and Organize Documentation
- 7.8 The 2 Most Important Kind of Help Articles In Your Knowledge Base [Webinar]
- 7.9 ScreenSteps Employee Training Features
- 7.10 Using ScreenSteps Employee Features
- 7.11 ScreenSteps and Zendesk
- 7.12 ScreenSteps Basic Knowledge Base
h2. Creating Killer Documentation
* Are you drowning in support requests?
* Does you business lack established procedures that you can rely on to get the job done right every time?
* Do you feel like your employees are wasting time constantly re-learning the same tasks?
If you answer yes to any of these questions then you probably have a documentation problem. This site is designed to give you a simple methodology for:
* Creating great documentation quickly
* Publishing it in a way that your customers and employees can use it.
* Keeping your documentation up-to-date.
Following this methodology will transform your documentation from a huge headache into a major asset.
Comments
Liquid error: internal for this article
0 Comments
Add your comment