FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 11-20-2009, 07:50 PM
"Paul W. Frields"
 
Default User Profiles

On Thu, Nov 19, 2009 at 05:14:50PM -0500, Máirín Duffy wrote:
> On Thu, 2009-11-19 at 21:16 +0000, Colin Walters wrote:
> > The client parts of this are not too hard; the Fedora Infrastructure
> > part is harder, last I talked with them about something like this they
> > had a lot of concerns about storage space, etc. In the big picture
> > all of infrastructure at the moment is contributor-scale and not
> > user-scale, and that's a big leap even if we're saying the user is
> > likely to be a contributor.
>
> If scale is a problem, could we, rather than tying this into first boot,
> have some kind of email-based invitation system where only maybe 250
> users get emails and are allowed to send data into the program?

Am I right in thinking we'd want to randomize these in some way to
ensure that we're not getting a selection of people that's too
insular, beyond the obvious selector of saying "sure, I'll
participate"?

--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
 
Old 11-20-2009, 07:58 PM
Máirín Duffy
 
Default User Profiles

On Fri, 2009-11-20 at 15:37 -0500, Paul W. Frields wrote:
> I'm going to bounce back some ideas below. As you read them, can you
> tell me what would be the best way to capture them in discreet bits
> that help with this profiling task? I don't know whether that means
> just bulletizing in notes on the wiki and figuring it out later, or
> stating them in some separate, well-understood way that's specific to
> user profiling.
>
> > Paul announced the Board's current working definition of Fedora's target
> > audience in his 26 Oct 'Target audience' mail to this list [2]. I think
> > this definition does a fine job of linking back to the goal of the
> > project. That target audience definition with my inline comments on its
> > relevancy to our goal is as follows:
> >
> > (1) Someone who is voluntarily switching to Linux
> >
> > Our strategy is not to force anyone to use Fedora. It's not going to
> > come pre-installed on your computer. Maybe a better way of stating this
> > point though is, "Someone who voluntarily wants to try another way of
> > running their computer." It doesn't necessarily have to be Linux. The
> > main point here should be, the target audience needs to be open to a
> > change in how they use their computer. We are trying to lead the
> > advancement of free software, and the folks most likely to switch to
> > free software (advancing it through greater ubiquity) are those who are
> > not afraid to undergo some change. (Let's make the change as painless as
> > possible though!)
>
> So you're saying this person (we should come up with a name!) is
> interested in "another way" generally, and not FOSS or Linux in
> particular. That sounds sensible to me, because it is possible for
> people to contribute who don't *yet* understand how FOSS works. We do
> want someone who is open-minded about it, because if she's not, she
> likely wouldn't spontaneously change. (And maybe wouldn't be
> interested in this other way in any case.)

Well, it's not a specific person per se; it's going to be a
characteristic shared by potentially multiple personas in the same
target group. To be clear, we may well end up with 3-8 different
personas to represent this target audience. And that's perfectly
fine.
>
> But yet, we're not looking to exclusively target tinkerers, "looking"
> to change their computers for arbitrary reasons. Would it make sense
> to describe *why* she wants to change?

Hmm... I think that is a good idea, to understand why they want to
change. I'm not sure though if it's something that is dictated by the
target audience definition, or something that we determine via user
research.

To be honest, I was thinking about the type of person who might read
about Linux or some piece of free software on a site like lifehacker.com
- and the implicit reasoning for change there is to make your life
better / easier / simpler. So if we want to take a stab at a reason in
the target audience definition, that's one potential one we could throw
out htere.

We may not need to decide on their reason for changing now, however.
Remember our goal is to get our target audience to change to *us* - is
it important to our goal why they want to change yet? Do we know enough
about the reasons someone would want to change to determine which of the
'changers' we want to target to in order to meet our goals? Certainly,
"Why would you consider changing your OS" might be a good high-level
research question to pursue with a sampling of target audience members.

> > I interpret point #2 to mean that if you're familiar enough with
> > computers to comfortably place an order with Amazon.com, you should be
> > in our sights.
>
> Here's what I was thinking about this point, and this may not be at
> odds at all. (I like your interpretation too.) This person by
> definition has to be someone who's comfortable with sticking a DVD
> into their system, and potentially writing over part or all of their
> hard disk. They'd need to understand the potential impact of an
> installation. I'm not saying that it's then OK to go nuts and
> surprise them, just that the person needs to be comfortable with the
> idea that they are going to perform an action on their computer, as
> part of installation, that many people don't do. (Well, more of them
> do it these days than should have to, but that's another story.)

For hard disk installation, it needs to be someone who has permission to
write over the hard drive potentially, which means Sharon's 5th grade
son George who uses her computer to do his homework on is probably not
in the target audience. But when George gets his own computer upon
entering high school, it's his to explore. So maybe we need to add to
the definition that our target audience needs to exclusively own and
control a desktop or laptop computer (since if they share their computer
'roommates' may not appreciate change ). If it's a shared computer,
it really needs to be the primary computer owner / head of family making
the changes.

This is definitely an important refinement on the 'Amazon.com purchaser'
interpretation.

> For example, Trent Reznor doesn't want to hack on his computer, he
> wants to make music. But he's certainly interested in spreading
> free/libre code and content, even if it's in service of just shaking
> up the norm. OK, maybe you don't buy that example because Trent's
> looking for music-making capabilities we can't yet provide. My point
> being someone like this is certainly not a developer but the ideas we
> put into practice in Fedora should sound appealing enough for Trent to
> say, "My music tracks are all backed up on that other disk over there,
> so they're safe, and if I hate this new thing, I'll just restore this
> system anyway."

Absolutely. It seems like we're already fleshing out some inflection
points to dictate specific within the target audience. A free/libre
content creator who wants to make sure his content is not lost when he
tries this new OS and also that he can work his content in the new OS.
>
> And yes, I understand that Live USB might invalidate part of this
> characteristic I'm describing. Is it possible to capture the
> characteristics for a persona using Live USB at the same time as we
> capture those for this other persona? Can they be the same? Do they
> need to be the same?

Absolutely. This is an inflection point that could determine the
boundary between two different personas in this target audience:

- George who is a 5th grader who wants to play Tux Racer on a Fedora USB
stick with his friends without getting in trouble with his Mom for
erasing her hard drive.

- Sharon who can't afford the $$$ Adobe Creative Suite but would like to
install Fedora on the family computer for her artistically-inclined son
to be able to try the many FOSS graphic design tools available. She
obviously doesn't have to worry about 'getting in trouble' for
installing Fedora.

>
> > (3) Someone who is likely to collaborate in some fashion when
> > something's wrong with Fedora.
> >
> > This collaboration can be as simple as filing a bug report using abrt or
> > posting a comment on a Fedora-related blog or news article. We want to
> > advance free software as a collaborative community, so focusing on folks
> > who are willing to collaborate, even just a little bit, to give back, is
> > important to advance that goal. This is not to say we shouldn't work on
> > tools such as abrt to make it easier for them to collaborate with us.
> > Just that they need to be receptive to engaging with us. I think this
> > statement could be further refined - you can collaborate when there
> > isn't anything wrong with Fedora as well, by blogging about Fedora or
> > talking about Fedora at a local LUG meeting or technology fair.
>
> Good point indeed. In all the cases of Fedora you list above, I see
> that communication is the common point. What about something like
> this, that's less charged?
>
> (3) Someone who is willing and able to communicate about their
> experiences with Fedora.
>
> ...which captures the same idea, but is broad enough to capture a
> broad spectrum of activity, from bug reporting to Ambassadorial work.

I like this much better! Is it okay if I update it on the wiki?


~m

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
 
Old 11-20-2009, 08:01 PM
Máirín Duffy
 
Default User Profiles

On Fri, 2009-11-20 at 15:50 -0500, Paul W. Frields wrote:
> On Thu, Nov 19, 2009 at 05:14:50PM -0500, Máirín Duffy wrote:
> > On Thu, 2009-11-19 at 21:16 +0000, Colin Walters wrote:
> > > The client parts of this are not too hard; the Fedora Infrastructure
> > > part is harder, last I talked with them about something like this they
> > > had a lot of concerns about storage space, etc. In the big picture
> > > all of infrastructure at the moment is contributor-scale and not
> > > user-scale, and that's a big leap even if we're saying the user is
> > > likely to be a contributor.
> >
> > If scale is a problem, could we, rather than tying this into first boot,
> > have some kind of email-based invitation system where only maybe 250
> > users get emails and are allowed to send data into the program?
>
> Am I right in thinking we'd want to randomize these in some way to
> ensure that we're not getting a selection of people that's too
> insular, beyond the obvious selector of saying "sure, I'll
> participate"?

Absolutely. The other thing is, though, if we're studying people using
Fedora, we're going to be insular. We're not capturing the side of
people in our target audience who aren't using Fedora. That's okay
though, as long as we contextualize the data collected via this
mechanism appropriately.

In a perfect world, we'd be able to write clients that Windows and OS X
users could install that would capture data too. But I don't know if we
have the development (and legal?) resources to do that.

~m

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
 
Old 11-20-2009, 09:23 PM
"Paul W. Frields"
 
Default User Profiles

On Thu, Nov 19, 2009 at 04:03:52PM -0500, Máirín Duffy wrote:
> On Thu, 2009-11-19 at 15:06 -0500, Máirín Duffy wrote:
> > Since this message is already really long, I'm going to cut this here.
> > Next I am going to make a post about our options on moving forward with
> > a user research plan.
>
> So first, to figure out which user research methods to use and the
> research deliverables we'll want to produce, I think we need to think
> about to what ends we would like to employ these personas. Here's my
> stab at it:
>
> - Personas will help us make informed design and policy decisions about
> the default configuration of software in Fedora itself. We need to
> consider these persona's needs and situations when making decisions
> about default application behavior in Fedora, and even the look & feel /
> appeal and style of the default artwork.
>
> - Personas will help us determine what tasks our target audience wants
> to accomplish with Fedora. This will help us figure out good default
> package selections for Fedora, and also to figure out, for a given task,
> which application is best suited to get the job done.
>
> - Personas will help us determine the timbre of our messaging in both
> marketing materials and our website in order to attract the very target
> audience we are hoping to gain.
>
> - Personas will help us streamline the main flows of the Fedora project
> - making it easier to download and install Fedora itself, making it
> easier to join Fedora as a contributor, and making it easy to get help
> with Fedora.
>
> - Release-engineering-wise, they can help us determine which updates are
> appropriate to be released when and the appropriate severity for them.
> E.g., it may be determined some sets of packages need to be under
> stricter guidelines than others based on the usage patterns we discover
> in our target audience.
>
> - Can you think of any other uses?

There might be implications for the test cases on which we concentrate
for Fedora, and the content and prioritization of test days, given
what I see below. Besides those ideas, this is a great summary of the
goals I'd had in mind.

> I think the kinds of deliverables we are going to want to focus the
> research towards producing then could be along these lines:
>
> A) A task list. This is a simple list of the things people are using
> Fedora to do. To help in prioritization, indications of frequency and
> how widely practiced the tasks are across the user set should be given.
> Tasks should be goal-centric, not application-centric. E.g., 'Use
> firefox' is not a task. 'Create a logo design for my business card to
> send to the printers' is a task. The task should have a clear goal.
>
> B) Most frequently-used applications list (should include rich client /
> desktop apps AND web applications.) Mugshot used to have a tool that
> collected this data, and I think it's in gnome-shell now. Is there any
> way we could allow users to opt-in to this sort of application usage
> data collection?
>
> C) A list of peripherals used with Fedora and what task workflows they
> are a part of. (Downloading photos off of a digital camera to post on
> your recipe blog and email the link to grandpa, Plugging in a scanner to
> digitize old family photos and store them on a consumer NAS, filming a
> music video for a school project grabbing the video off the camera
> editing and uploading to youtube then emailing the teacher with the
> link, connecting the computer to a TV and watching the movie with the
> whole family, etc etc etc.) Some notion of how frequently the tasks are
> performed / how many users perform them will be important to prioritize
> efforts to streamline these workflows and produce guides / other content
> for the website and marketing materials to show users how to accomplish
> them with Fedora.
>
> D) Applications commonly installed post-Fedora install. Looking at the
> applications a user installs on top of Fedora, and the type of
> configuration they do on a machine beyond the defaults I think would
> help inform us where the default configuration / package set falls
> short, and/or how packages and configurations might be chunked together
> to make it easier to find them and get them installed.
>
> E) And of course, most importantly, a set of user personas extrapolated
> from all the data collected during research.
>
> Here are some user research methods I think we could employ to gather
> this kind of data. Some of them come from my set of IDEO method cards
> [1]:
>
> 1) An opt-in application usage collection mechanism as described in B
> above.
>
> 2) Maybe towards C and B, a listing of the Fedora-related bugzilla
> components in terms of frequency folks are filing bugs against them. The
> more bugs, perhaps the more visible problems are in those applications
> thus they might need to be prioritized more.

That makes sense and would probably be pretty easy to gather.

> 3) Surveys & Questionnaires - these are easy to do, although it would be
> nice if we had a survey system in our infrastructure to conduct these.

There is a polling mechanism packaged (I believe) for Zikula, the CMS
that the Fedora Marketing team is working on at FUDCon Toronto 2009.
Also, I believe Ian Weller or someone involved in the Marketing team
had looked into packaging LimeSurvey, which is also 100% FOSS and thus
eligible for Infrastructure.

> 4) Personal Inventory - interview a handful of target audience members
> and ask them what objects related to their computer and computing
> lifestyle are most important to them and why. Produce a catalog of the
> items per interviewee. This will help us come up with a task list (A)
> and understand how Fedora might fit into our target audience's lives.

How do we go about selecting these people?

> 5) Be Your Customer - with the task list (A) we come up with, members of
> the Fedora project should walk through / enact performing those tasks on
> their own to understand all the issues that arise. Out of this a
> document listing out issues that need to be addressed in order to make
> the tasks easier to perform could be written and bugs filed as
> appropriate.

This is brilliant -- occasionally in rare moments of downtime I work
through a procedure to see what it takes, and use that to file bugs
myself, but hadn't made the contextual connection with the user
profiling. In large part, this is also how the Desktop SIG worked on
their "Fit and Finish" days to provide additional shine for Fedora 12.

> 6) Scenarios - write up a character-rich story involving a made up user,
> who is clearly a member of the target audience, interacting with Fedora
> to provide context for how Fedora is used.
>
> 7) Behavioral Archeology - look for evidence of activity based on
> organization / placement of things. We could ask for people in our
> target audience to send in screenshots of their desktop and take note of
> what changes they made to their desktop.
>
> 8) Cultural probes - make 'camera journal kits' including a camera,
> notebook, and instructions and send it out to members of the target
> audience asking them to keep a photo journal of their experience with
> their computer over the course of some set time period. One way of doing
> this to help the participants remember to do it is to send them some
> signal at frequent intervals (phone, text message, email) and ask them
> to write down what they're doing on their computer as soon as they get
> it.
>
> 9) Fly on the wall - sit with members of the target audience for a few
> hours and simply observe how they interact with their computers without
> interfering with their activities.

This is akin to a "sit bird-dog with a notepad" method?

> 10) Think-Aloud Protocol study - Similar to fly on the wall but more
> interactive - observe a member of the target audience interacting with
> the computer and take on a mentor/apprentice role with them - with you
> as the apprentice - and ask them to explain what they are doing as they
> do it.

Seems like this would be tough to do without role-reversing! But it
would be fascinating to watch someone with the proper discipline do
it. I could imagine a third person acting as coach to help people
learn how to do this right.

> 11) Extreme User Interviews - pick a set of target audience members who
> are completely unfamiliar with Fedora and ask them to give it a try,
> writing up their experiences.

The SO test?

--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
 
Old 11-20-2009, 09:28 PM
"Paul W. Frields"
 
Default User Profiles

On Fri, Nov 20, 2009 at 03:24:22PM -0500, Máirín Duffy wrote:
> On Thu, 2009-11-19 at 17:12 -0500, Máirín Duffy wrote:
> > Does anybody want to help conduct the stakeholder views, as the first
> > next step?
>
> So I am gonna run a hackfest on Tuesday to start hashing these out.
> Please come!
>
> http://mairin.wordpress.com/2009/11/20/want-to-learn-design-skills-want-to-help-fedora-fedora-interaction-design-hackfest-tuesday-24-nov/

Brilliant! If I can break free for part or all of this time, I would
love to participate in this -- at the very least I'll lurk and log.

--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
 
Old 11-21-2009, 09:36 AM
Mel Chua
 
Default User Profiles

On 11/20/2009 12:39 PM, Mel Chua wrote:

Mo Duffy is working on user research for Fedora, which has a lot of
potential overlap (and therefore synergy - yay synergy!) with our
marketing research efforts.


Update: the Design Team is having a sprint this coming Tuesday to work
on user research - see
http://mairin.wordpress.com/2009/11/20/want-to-learn-design-skills-want-to-help-fedora-fedora-interaction-design-hackfest-tuesday-24-nov/
for details.


By sheer coincidence, our current plan for next week's meeting time is
that Sakis is leading us on sprinting on user stories - Sakis, how can
we use this to our benefit (and what are we doing / what should we do to
prep for Tuesday)? Mo, do you have any thoughts/requests on whether (and
if so, how) we can join forces?


--Mel

--
Fedora-marketing-list mailing list
Fedora-marketing-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-marketing-list
 
Old 11-23-2009, 10:58 PM
John Poelstra
 
Default User Profiles

On 11/20/2009 12:24 PM, Máirín Duffy wrote:

On Thu, 2009-11-19 at 17:12 -0500, Máirín Duffy wrote:

Does anybody want to help conduct the stakeholder views, as the first
next step?


So I am gonna run a hackfest on Tuesday to start hashing these out.
Please come!

http://mairin.wordpress.com/2009/11/20/want-to-learn-design-skills-want-to-help-fedora-fedora-interaction-design-hackfest-tuesday-24-nov/

~m


Yes, I want to help. I will be there tomorrow, but will be 30 minutes
late. Thanks for all you are doing to help us move forward on this issue!


John

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
 
Old 11-23-2009, 11:56 PM
John Poelstra
 
Default User Profiles

On 11/19/2009 01:03 PM, Máirín Duffy wrote:

On Thu, 2009-11-19 at 15:06 -0500, Máirín Duffy wrote:

Since this message is already really long, I'm going to cut this here.
Next I am going to make a post about our options on moving forward with
a user research plan.


So first, to figure out which user research methods to use and the
research deliverables we'll want to produce, I think we need to think
about to what ends we would like to employ these personas. Here's my
stab at it:

- Personas will help us make informed design and policy decisions about
the default configuration of software in Fedora itself. We need to
consider these persona's needs and situations when making decisions
about default application behavior in Fedora, and even the look& feel /
appeal and style of the default artwork.

- Personas will help us determine what tasks our target audience wants
to accomplish with Fedora. This will help us figure out good default
package selections for Fedora, and also to figure out, for a given task,
which application is best suited to get the job done.

- Personas will help us determine the timbre of our messaging in both
marketing materials and our website in order to attract the very target
audience we are hoping to gain.

- Personas will help us streamline the main flows of the Fedora project
- making it easier to download and install Fedora itself, making it
easier to join Fedora as a contributor, and making it easy to get help
with Fedora.

- Release-engineering-wise, they can help us determine which updates are
appropriate to be released when and the appropriate severity for them.
E.g., it may be determined some sets of packages need to be under
stricter guidelines than others based on the usage patterns we discover
in our target audience.

- Can you think of any other uses?



- Personas will help us focus our Test Days and QA time on applications
and Fedora experience used by our Target Audience.


John

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
 
Old 11-24-2009, 06:54 PM
Máirín Duffy
 
Default User Profiles

On Sat, 2009-11-21 at 04:36 -0600, Mel Chua wrote:
> By sheer coincidence, our current plan for next week's meeting time is
> that Sakis is leading us on sprinting on user stories - Sakis, how can
> we use this to our benefit (and what are we doing / what should we do to
> prep for Tuesday)? Mo, do you have any thoughts/requests on whether (and
> if so, how) we can join forces?

I think maybe the user stories you're sprinting on might give us good
ideas of which users we could interview as part of the 'users'
stakeholder category. I'll be in both channels.

~m

--
Fedora-marketing-list mailing list
Fedora-marketing-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-marketing-list
 
Old 11-24-2009, 10:15 PM
Máirín Duffy
 
Default User Profiles

On Fri, 2009-11-20 at 15:24 -0500, Máirín Duffy wrote:
> On Thu, 2009-11-19 at 17:12 -0500, Máirín Duffy wrote:
> > Does anybody want to help conduct the stakeholder views, as the first
> > next step?
>
> So I am gonna run a hackfest on Tuesday to start hashing these out.
> Please come!
>
> http://mairin.wordpress.com/2009/11/20/want-to-learn-design-skills-want-to-help-fedora-fedora-interaction-design-hackfest-tuesday-24-nov/

Here's my summary:

http://mairin.wordpress.com/2009/11/24/fedora-interaction-design-hackfest-summary/

~m

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
 

Thread Tools




All times are GMT. The time now is 09:50 PM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org