Elenco Personas

Primary Persona - Ellen Scott - Business analyst

{ I want to find an innovative way to produce quality documentation that helps customers perform their jobs when using our products." -- Ellen Sco tt \ \ Ellen Scott is 35 years old; she is married and has 2 children. She is the financial responsible of the documentation group in a big organization. Ellen needs to find new tools that allow her group to produce documentation that makes the difference when buying a product. She has to prepare a business plan to provide details and information on the potential benefits of buying a specific tool (or licenses) for the Information Development group. Periodically she needs to provide a report on the customer satisfaction on the product documentation quality to the CEO and to convince him on the judiciousness of her decisions. This persona is a stakeholder.

{style:type=span|font-family=Arial}Primary Persona - Christine Bredford - Information Architect

{ "I coordinate the planning, modeling and designing of the information model and the development of the information design. I also communicate with the technical writers to ensure successful implementation of the design. I would like to start designing the documentation earlier, at the product design stage." -- Christine Bredford

Christine Bredford is 42 years old; she is married and has 2 children. Her job consists of helping her ID colleagues do their job better and to find innovative solutions for the documentation design information that is easy to use and meets the user's needs. She has a good understanding of customer requirements, goals and business needs for information products. She reviews the requirements from an information development perspective and outlines the design of the information system. Christine performs the following tasks:

• gathers early information for analysis and preliminary sizing
• performs information analysis
• constructs the high-level information model
• validates the high-level information model
• constructs the detailed information model
• validates the detailed information model
• defines the metadata and taxonomy to be used throughout the project and ensures that templates are used to support the goals of the architecture (for example, ensuring that task templates are used for Information Center topics as opposed to chapter templates)
• determines how and in what user contexts different kinds of information is to be retrieved
• defines the information delivery system, including navigation and organization
• describes where and how information is to be stored in the final product for delivery to the user, as well as where source code will be stored, so as to ensure that the project infrastructure supports the architecture and design and facilitates an efficient authoring environment\

  \ \

  Primary Persona - William Smith - Technical writer

  { "I would like to interact more with my audience to continuously improve the documentation with customer feedback and validation." -- William Smith\ \ William Smith is 42 years old; he is married and has 2 children. He is a technical writer who authors manuals and information center for the companies for which he works as a contractor. William plans, writes, builds, publishes, and maintains information products using a variety of leading edge technology, as well as, traditional technologies. His purpose is to communicate complex technical information clearly and concisely, whether it's for the Web, a usable user interface, product messages, online infocenter information or traditional books. He works closely with the Information Architect, as well as with Development and Test groups. He usually works in writing teams, although, on very small projects, he can work alone.

  {style:type=span|font-family=Arial}Secondary Persona - Ann Taylor - ID Tool specialist

  {style:type=span}{ "I like tools that help technical writers do their job without causing too many troubleshooting issues." -- Ann Taylor \ \ Ann Taylor is 30 years old; she is not married. Her job consists of supporting the tools used by the Information Development team and in searching new tools for the documentation production. She accomplishes this by studying the new tools. She also suggests the best tools to use in the Information Development group to the Business analyst and influences the decisions about which product should be purchased. Ann is also responsible for configuring and setting up the tools, resolving problem tickets or requirements related to the tools and verifying that they work as designed or specified. She is also involved in the decision about the documentation process changes: for example when there is an acquisition or there are some new requirements from customers. This persona is a stakeholder.