Feature #11162

Create personas to visualize our user base

Added by sajolida 2016-02-23 12:19:26 . Updated 2019-03-10 07:59:20 .

Status:
Resolved
Priority:
Normal
Assignee:
sajolida
Category:
Target version:
2019
Start date:
2017-08-30
Due date:
% Done:

100%

Feature Branch:
Type of work:
Research
Blueprint:

https://tails.boum.org/blueprint/personas/

Starter:
Affected tool:
Deliverable for:

Description

team: u, sajolida, (spriver) + review&advice from jaster

Subtasks

Feature #14525: Create tickets and update blueprint for the next steps in the personas process Resolved sajolida

0
Feature #15712: Create a first version of our personas in time for the summit Resolved

0
Feature #15713: Ask the project to prioritize the first personas Resolved

0
Feature #15714: Create artifacts to illustrate our personas Resolved

0
Feature #16483: Publish our personas on our website Resolved

0
Feature #16484: Integrate the comments from the summit in our personas Resolved

0

Related issues

Related to Tails - Feature #11778: Create user scenarios with regard to the scope of Tails Duplicate 2016-09-03
Blocks Tails - Feature #7627: Restructure the website Confirmed 2013-07-19
Blocks Tails - Feature #6170: Different visual identities for sections of the website Confirmed 2013-07-19
Blocks Tails - Feature #16080: Core work 2018Q4 → 2019Q2: User experience Resolved 2018-10-29

History

#1 Updated by SpencerOne 2016-03-01 20:36:55

  • Subject changed from Have personas to describe our typical users to Create personas to visualize our user base

01 [Profile Of A Tails User]

Personas, user personality types, are tools for assisting with thought experiments, most notably, those that aid in the creation of user scenarios and the resulting case-study flows.

User personas are available everywhere. However, it is in our best interest to build our own user personas that are more indicative of the Tails community and reflective of the system’s unique challenges.

This is where user profiles come in. By assembling user profiles first, we can more accurately assess the personality of our user base, plugging in different variables as we go and, presumably, gaining a more accurate understanding of the Tails community needs.

02 [Anatomy Of A User Profile]

There are many structures to a user profile. A common structure contains sections such as Demographic, Geographic, Psychographic, and Behavioristic information. Because there is often overlap between section contents, we will use Background and Lifestyle as section descriptors, mapping them to Macro and Micro levels of information where relevant, and using them as a checklist.

This list attempts to be exhaustive. Items will be crossed off if decided against for privacy or relevance concerns.

Background & Lifestyle Information:

- Name

- Age

- Gender

- Cultural Background

- Lifestyle Preference

- Family Status

- Social Status

- Personal Network

- Public Network

- Education

- Occupation

- Income

- Geographic Location

- Geographic Description

- Life Motivation

- Political Opinions

- Cultural Opinions

- Social Opinions

- Behavioral Values

- Activities

- Diet

- Attire

- Personal Accessories

- Home Products

- Furniture

- Transportation

- Services

- Devices

- Software

- Internet Use
- and more ..

An example of the mapping structure:

Background ( Macro ) { Education “College” }
Lifestyle ( Micro ) { Education “PhD, Transportation Design, Umeå Institute of Design” }

03 [Persona Formats]

The format of the personas is TBD.

It is recommended that we create as many personas as is needed to best visualize the Tails community as a whole.

#2 Updated by Dr_Whax 2016-08-20 12:45:16

  • Description updated
  • Target version set to 2017

#3 Updated by intrigeri 2016-08-23 00:29:54

  • Assignee deleted (None)

#4 Updated by sajolida 2016-11-04 12:08:52

  • related to Feature #11778: Create user scenarios with regard to the scope of Tails added

#5 Updated by intrigeri 2017-03-29 12:25:54

  • related to Feature #8422: Support running Tails from internal hard drives added

#6 Updated by Anonymous 2017-06-28 09:13:09

#7 Updated by Anonymous 2017-06-28 09:13:25

#8 Updated by Anonymous 2017-06-28 09:13:36

#9 Updated by Anonymous 2017-07-10 10:22:09

  • related to Feature #6170: Different visual identities for sections of the website added

#10 Updated by BitingBird 2017-08-26 17:24:23

  • Target version changed from 2017 to 2018

#11 Updated by BitingBird 2017-08-26 17:26:50

  • Description updated

#12 Updated by Anonymous 2017-10-02 16:06:41

  • Assignee set to sajolida

As you are the lead on this one, I’d rather assign the ticket to you and add myself as a watcher.

#13 Updated by sajolida 2017-10-03 12:34:44

I don’t think I’ve ever said I would be “the lead” on this project. You and me both volunteered to work on this on our free time during last summit. Since then I’ve been the “de facto” lead but I would be very happy if this changed and having you as assignee might help counterbalance the de facto state of things…

But yeah… whatever, any assignee is fine with me.

#14 Updated by Anonymous 2018-01-18 17:58:45

  • related to deleted (Feature #8422: Support running Tails from internal hard drives)

#15 Updated by Anonymous 2018-08-19 09:03:02

  • related to deleted (Feature #6170: Different visual identities for sections of the website)

#16 Updated by Anonymous 2018-08-19 09:03:11

  • blocks Feature #6170: Different visual identities for sections of the website added

#17 Updated by sajolida 2019-01-08 12:30:55

  • Target version changed from 2018 to 2019

#18 Updated by intrigeri 2019-03-10 07:59:20

  • Status changed from Confirmed to Resolved

All subtasks were closed so I’ll optimistically assume we’re done here :)

#19 Updated by sajolida 2019-03-11 11:20:41

  • blocks Feature #16080: Core work 2018Q4 → 2019Q2: User experience added