Fedora's Audience and Why Fedora
Fedora's Target Audience
The target Fedora user audience is people who:
- are familiar with and comfortable interacting with computers.
- are not afraid to try something different when it comes to technology.
- want to change how they work with their computer.
- are not necessarily computer hackers or developers.
- participate in online forums such as online shopping product reviews, blogs, or movie fan sites.
- someone who does not mind submitting a bug report as long as it's not too time-consuming.
- are active users of the web, having accounts on a wide range of web-based applications.
- use their computer to produce content, whether it's an expense report for work or a photo slideshow of the kids for Grandpa.
Fedora enables people worldwide to enjoy and contribute to free and open source technology without requiring them to be computer hackers or developers. It allows them to accomplish every day personal and work-related tasks in a safe and secure manner, presenting them with a selection of the best-of-the-best free and open source software to get the job done, either pre-installed or easily installed when needed. Fedora also makes it easy for people to put their own mark on the free and open source software community, whether its participating in a user forum or filing a bug to make free and open source software better for everyone. Fedora makes free and open source software fun and easy to integrate into their lives.
Guesstimation of Top 10 User Tasks
Based on our target audience definition alone, here is a guesstimation at the Top 10 User Tasks we'll want to support. Keep in mind that these may change based on findings in user research. Some of theseare also ob-board specific tasks.
- Decide whether or not to download Fedora.
- Download and install Fedora, and personalize it, configuring email, bookmarks, wallpaper, etc.etc.
- File a bug with Fedora. Follow up on the bug and take a look at its progress.
- Take a photo of the kids and send it to Grandpa.
- While on a business trip, make a video call to your boyfriend/girlfriend.
- Print out invitations to your holiday party, including directions and mailing labels for the envelopes.
- Create a mix of tunes, save it for later use, and burn it to CD for an upcoming roadtrip.
- Get live help with Fedora.
- Find a good meeting time and book an appointment on your calendar for a business meeting.
- Write and send in your weekly status report for work, and figure out what you should work on today.
Success for Users
- Fedora has the functionality they need to get the job done.
- Fedora is not painful to use in getting the job done.
- Fedora is enjoyable to use, and 'cool.' They *want* to use it and are happy with it.
Success for the Fedora Project
- More bug reports!
- More posts on Fedora-related user forums, and more activity and blog posts and general discussion of Fedora online and off.
- More downloads of Fedora. Increased traffic to the website.
- Increased awareness and mindshare of Fedora and free & open source sofware in general.
|Stakeholder||Goals and Questions|
|Fedora Desktop Team||?|
|Fedora Design Team||?|
|Fedora Release Engineering||?|
|Fedora Marketing Team||?|
|Fedora Spins Maintainers||?|
|Fedora Infrastructure Team||?|
|Fedora Documentation Team||?|
|Fedora Websites Team||?|
|Fedora Help forums (#fedora, fedoraforum.org, Fedora Unity)||?|
|Current Fedora contributors||?|
- For each of these stakeholders, we'll need to ask:
- How well do you think Fedora accomplishes its stated goals in light of your role in the project?
- How is Fedora not meeting those goals?
- What questions do you have about Fedora's target audience that you'd like to see answers so that your team can help get Fedora closer to its goals?
- We'll then need to prioritize the goals based on importance, severity, and priority.
- Per goal, we should formulate research questions, and come up with specifics to research for each question.
- Then we'll need to decide research methods for each questions.
- Then we'll need to come up with a research schedule.
Note: The methodology followed here is outlined in Observing the User Experience by Mike Kuniavsky.