New Abstract Writer: Consume The Persona To Create The Most Functional Area Of Your Person Document
- Posted by Essays Blog in Essays Blog |
- November 7th, 2008 |
- Comments
OVERVIEW
A good Person Document includes sections on how to fix, consume, and care for the product. However, to create a great Person Document , the abstract writer should consume the Persona, generated in the analysis of the Person/Reader, to create the topics for the most functional area of the Person Document. This article describes this procedure.
THE MOST Functional Area OF A Person DOCUMENT
The most functional area of a Person Document is the one that helps the Person get what he/she wants/needs done right now!
Writing much a area might appear to be an impossibility. How do you know what the Person needs to do now?
The only abstraction that you, as a writer, can do is to play the odds. That is, determine the topics that have the highest probability of being of interest to your Person. And “of interest” means “getting what the Person wants done, right now.”
We created Persona (an almost-real representation of your product’s Person) in another article in the “New Abstract Writer” broadcast (accompany the links in the “Resources” or “Author Information” area of this article). We can consume the Persona to create a issue list for this area.
Exploitation YOUR PERSONA
This deputise exploitation your Persona is missed by almost all Person Documents that I have seen. Yet this block will result in a Person Document that is most solid to your Reader. Here it is:
Imagine your Persona exploitation your product. Now, what are the main things that your Persona will deprivation to do with your product.
As an example we will consume a photo editing program (Acme FotoPhixer, a hypothetical product from a hypothetical company) that comes bundled with a point and administer digital camera. Our Persona is a typical person of much a camera.
Ask: What does that Persona deprivation to do with Acme FotoPhixer?
The abbreviated answer is that they deprivation to improve their photos. HOW can they improve their photos with Acme FotoPhixer? In OUR words (not the words of the Person) we could tell them how to:
* Rotate
* Crop
* Red-eye removal
* Adjust brightness & contrast
* Removing abdicable items from the photo
* Focus/Blur
* Economise
* Print
* Apportion
These names are what we, the photography experts might consume. However, “crop” may be meaningless to our Persona. In fact, we could move crop into “Removing abdicable items from the photo.”
The “Focus/Blur” issue is interesting. If a photo is out of focus or blurred, thither is really nothing that our code can do to improve it. However our Reader does not know this, but allay wants to do it. We should include issue with this matter: “It is impossible to fix the focus or remove blurring in a photograph. You might be able to improve this exploitation the [Sharpen Effect] means in FotoPhixer.” (The [] specifies a reference to the issue in the Person Document.)
DON’T HIDE THIS Area
If your Reader cannot quickly find what he/she wants to do in your Person Document, so the document has failed. Since we created this area to answer the Person’s pressing needs for the product, so we must make this area real accessible to the Person — they have to be able to find it easily.
“Fixing (Improving) Your Picture” is a PERFECT, User-oriented appellation. That is the correct appellation for this area. Don’t bury this gold low titles much as: “Tutorial” or “Consume FotoPhixer’s Tools.” These titles do not advise answers to the Person’s questions.
You should make this area real easy to find in the Person Document. It’s the key area of the Person Document. It has the information that most Readers deprivation, most of the time (by your analysis). Place it prominently in the Person Document.
Solid THE READER IS EASIER THAN YOU Believe
Producing this area is easier than you believe.
First, imagine that you were NOT going to include this area. Your Person Document would allay have to cover all of the features, tools, and person interactions for the product. You need to do that to fill your boss. It’s also logical. If a feature is not described, so why is it in the product?
Thusly you have created a issue list for a “classical” Person Document.
Now we create our User-oriented area, “Fixing Your Picture.” Here are the stairs:
1. List each of the topics for fixing a picture, exploitation titles that the Reader will believe.
2. Provide a brief overview, perhaps with a picture showing before and after the consume of this fixing method.
3. So list the stairs for that issue, and provide links to the documentation for the relevant tools for each block
Done!
Actually, I would recommend exploitation what I call a “Visible Index,” which is described in the links in the “Resources” or “Author Information” area of this article.
Inside Document Re-usability
We could call this organization method “inside document re-usability.” Here the writing for a issue exists as an item in the “reference” area of the Person Document. By referring thereto item when it is needed for performing a User-oriented chore, we make the matter do double duty. This results in reusability inside the document.
HOW TO GET THE TIME TO Compose THIS Area
Put less detailed effort into the documentation for the product’s features that will be rarely old. For example, FotoPhixer includes tools to make the image look like it’s made of endocarp, or produce 3D effects, etc. These are rarely old, and have a similar set of controls. Instead of detailing the consume of each of these rarely old features, compose a global usance, describe the controls, encourage the Person to experiment, and remind them of the un-do and cancel capabilities.
You can create the “most functional” area with the time you economise by not good documenting these rarely-used items.
THE BOTTOM LINE
You can make your Person Document much more effective if you entertain your Person/Reader and what he/she wants to do with the product. Consume this information to create an easy to find area in your Person Document that meets your Reader’s needs.