Our final heuristic refers to help and documentation. Even though it's better if the system can be used without any documentation, it sometimes may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large. Why is this important? Well, in some cases, your user interface may not be as self-explanatory as you hoped it might be. The guidelines in this heuristic about the structure of help and documentation, are there to help support the gulf of execution. So, that's why helped needs to be easy to search so that people can find the help that they need, needs to contain the list of actions so they know how to apply the help to solve their problem, and it needs to be focused on users tasks because we're trying to help bridge that gap between user's goals and how they can accomplish those goals using this particular interface. To look at an example for how help and documentation can be focused on a user's tasks, I'm going to go back into edit mode and look at how PowerPoint organizes their help files. When I open PowerPoint Help, I can see that the first two options that are presented to me describe tasks, that I as a user and likely to want to perform, like creating a presentation and adding and organizing slides. The next few items are more generic, but if I drill into them, I can see that they too are organized in terms of tasks that I'm likely to want to accomplish, like changing or removing a theme, creating and applying my own theme and so forth. To look at how help can be organized into step-by-step instructions, we'll look again at PowerPoint Help. So, if I look at a particular help item, let's say I look at adding and organizing slides, I want to add text to a slide, I want to add text to a text box, the actual help content is organized into these step-by-step instructions that will allow me to accomplish my task. One other technique that can be used to help users find the help that they need as quickly as possible, is contextual help or help that is specific to the particular tasks that people are trying to perform. For this, let's look at an example from Eclipse, which is a programming editor in development environment that I use sometimes. So, here we see the eclipse environment and there are several different areas on the screen. On the left we see the area that organizes the different code files that I'm working on, the center shows the specific file that I'm working on and it provides editing capabilities, and then there's other screens as well. If I click any editor to set the focus on that part of the screen and then select eclipse's dynamic help, this streamlines my search for help by focusing on the things that I'm most likely to be interested in, based on the tasks that I'm performing right now at this moment. To summarize this heuristic, it's best if help and documentation is not needed. Ideally, your interface's intuitive and clear enough that people know what to do without help. But sometimes, especially in more complicated software, help and documentation is required. If it is, make sure that the help is searchable, focused on the users tasks, and provides concrete steps to help them accomplish the things that they need to get done.