Personas » History » Version 1
Kyle Baker, 12/05/2014 03:34 PM
1 | 1 | Kyle Baker | h1. Katello/Foreman Systems Management Personas |
---|---|---|---|
2 | |||
3 | h2. Ecosystem |
||
4 | |||
5 | ACME Financial Services Company |
||
6 | A large consumer financial services company with a retail, web and office environment. |
||
7 | |||
8 | Personas: |
||
9 | • System Architect |
||
10 | • System Administrator |
||
11 | |||
12 | h2. What is a persona? |
||
13 | |||
14 | “The purpose of personas is to create reliable and realistic representations of your key audience segments for reference. These representations should be based on qualitative and some quantitative user research.” |
||
15 | [http://www.usability.gov/ |
||
16 | |||
17 | h2. How should they be used? |
||
18 | |||
19 | “Personas help to focus decisions surrounding site components by adding a layer of real-world consideration to the conversation. They also offer a quick and inexpensive way to test and prioritize those features throughout the development process.” |
||
20 | http://www.usability.gov/ |
||
21 | |||
22 | h2. How were these created? |
||
23 | |||
24 | * I built a cross-functional team including User Experience Designers, Product Managers, Developers. |
||
25 | * Gave an overview to the upstream community on what Personas are, how they are used, how we will construct them. |
||
26 | * Prepared a screener to run by potential interview candidates. |
||
27 | * Prepared a set of interview questions and reviewed with the team. |
||
28 | * Scheduled interviews and asked users the same interview questions to all while taking a lot of notes. |
||
29 | * Identified clusters of interviewees responses. |
||
30 | * Created persona write-ups based on these responses keeping the folks that we interviewed in mind. |
||
31 | * Finalized persona designs including a short write up on the persona and included a photo, Key Attributes, and Behavioral Drivers. |
||
32 | * Built this wiki page accessible as reference to everyone in the community. |