Page MenuHomeSoftware Heritage

Identify user personas to clarify who are the users reading the documentation
Closed, ResolvedPublic


A summary from the following article to create SWH user personas to help with writing clear documentation.

  1. User Group—This typically designates the role of a particular type of user—for instance, Laboratory Manager.
  2. User Name—This should be a fictional name.
  3. Job Details—Indicate the persona’s primary role and responsibilities.
  4. Demographic Data—You might include the persona’s age, academic and professional qualifications, ethnicity, and family status.
  5. Goal—What is the customer trying to achieve by using your product?
  6. Tasks/Actions—What tasks would this persona perform using your product, how, and in what order? How long would it take to complete these tasks?
  7. Aspirations & Values—What is of primary importance to this persona? What values drive this persona’s purchasing decisions? Would emotions, logic, or impulse shopping influence these purchasing decisions? Would this persona perceive the product as utilitarian or aspirational? Does product quality or cost influence this persona more?
  8. Needs & Requirements—What answers does this persona seek? What information is necessary to accomplish the persona’s tasks and when is it needed? What are the persona’s must-haves, desirables, and value-adds?
  9. Painpoints—What would cause this persona to opt out of using the product, switch to a rival product, or abandon a process midway? Why?
  10. Expectations—How does this persona expect the product to work? What are the expectations this persona has in regard to product pricing? To what degree would this persona be tolerant of time consumption or delays? What is the persona’s mental model for this experience?
  11. Customer Journey Stage & Customer Type—Might this persona represent potential customers who are just starting their product research? Customers who are ready to make a purchase? Satisfied repeat purchasers or returning customers? Prospective switchers or loyal customers who are planning to upgrade?
  12. Emotions—What is the persona’s current emotional state? Happy, angry, anxious, disappointed, excited, or indifferent?
  13. Back Story & Quotation—Provide a short narrative and a real user quotation that sums up the key characteristics of a user need or problem.
  14. Image—Include an image that represents the particular target user group.

Event Timeline

moranegg triaged this task as Normal priority.EditedDec 16 2020, 3:19 PM
moranegg created this task.

Here is the stakeholder landscape that was created for the SCID WG output (RDA & FORCE11)

We can identify three general types of personas:

  • visitors: people who want to know what is the SWH initiative and archive
  • users: people who want to use the SWH features
    • as a service
    • as a module by running a local instance
  • contributors: people who want to contribute to the SWH project, specifically on a feature or in general
    • source code contributors
    • sys-admins contributors
    • documentation contributors

There are also other types of contributions, that don't need a specific section in the documentation. This is why they are not identified here, but keep in mind these contributors are very important to the project.

To help each general persona on her journey in the SWH documentation, we have decided to create a main page on:
On this page there will be several links to access the documentation from a different point of view:

  • devel for developers and other technical contributors
  • sys-adm for sysadmins
  • user for the service users

see T3155
Visitors should have all the needed information on the main website.

This task is now resolved, since we will not explore specifying individual personas at the moment.

moranegg renamed this task from Create user personas to clarify who are the users reading the documentation to Identify user personas to clarify who are the users reading the documentation.Jun 29 2021, 9:49 AM