There are so many ways to write down a user guide. One should write the product user guide in such a manner while explaining every one of the features that are easily understandable. Otherwise, you can write and clarify a few important tasks dealing regarding what the user wants and requires when he or she trapped at a serious point in the task procedure. The majority of the users do not concern in reading the complete Guide. They are more concerned in knowing regarding what they are doing, why they are caught in the procedure and what should be done to get the job finished.
Writing a user guide to a layman is dissimilar from writing for a professional. In other words, how you write mainly depends upon the prospective audience and upon the use or the item/product, you are going to buy. Overall, if the prospective audience reads as well as understands your content without any complexity, confusion and trouble, then it means you have done a good job in Technical Writing task.
The learning graph of each user differs in extremes levels. It is not feasible to guess what the user can or cannot comprehend. Unless until the end-user communication is there, the whole circumstances look bizarre. Since it is not likely to interact with end users basically, the only other substitute way is to get diverse kinds of reviews such as peer, technological, editorial, etc. To ensure that both the Product Guide as well as the end-users is on the same line strictly, it is recommend getting your user guide as well reviewed by departments such as Marketing and Sales etc, who interacts with end-users often and knowing what they are searching for. Interacting with the departments will make it easier to draft your user guide more appropriately.