UserPersonas » History » Version 3
Sarah Zaranek, 09/20/2022 03:07 PM
1 | 1 | Sarah Zaranek | h1. UserPersonas |
---|---|---|---|
2 | |||
3 | 3 | Sarah Zaranek | h3. Ingrid the Informatician |
4 | 1 | Sarah Zaranek | |
5 | 2 | Sarah Zaranek | h3. Titles |
6 | 1 | Sarah Zaranek | Computational Biologist, Statistician, Informatician |
7 | |||
8 | 2 | Sarah Zaranek | h3. Background |
9 | 1 | Sarah Zaranek | Ingrid has PhD in genomics, computational biology, systems biology. She also has training in statistics and mathematics. Some understanding of software programming. Ingrid has strong training in biology and a deep understanding for how biology works. |
10 | |||
11 | She works in a bioinformatics, biology or genetics laboratory. She works alone, but usually has other informaticians, biologists and geneticists in the same lab. She may recommend or evaluate tools but does not normally have budget authority. |
||
12 | |||
13 | She knows Python and R, and is most comfortable in one of these languages for most of her analytical work. Likely some exposure to other general purpose languages (Perl, shell scripting) and stats/math languages like Matlab. |
||
14 | |||
15 | 2 | Sarah Zaranek | h3. Personality |
16 | 1 | Sarah Zaranek | Core motivation is to make discoveries which can be published or delivered as new products. She is highly independent and wants to have the freedom to do what she wants to do. Ingrid is a tinkerer and is constantly iterating and trying new things. |
17 | |||
18 | Ingrid is an analytical problem solver. She is focused on solving biological or genetic problems. For Ingrid, tools are there to get to results and to answers of hard questions about biological and biomedical problems. |
||
19 | |||
20 | She is not interested in hardcore technical development, scalability or creating production software systems. |
||
21 | |||
22 | |||
23 | |||
24 | 2 | Sarah Zaranek | h3, Needs Matrix |
25 | 1 | Sarah Zaranek | |
26 | 2 | Sarah Zaranek | |
27 | 1 | Sarah Zaranek | Pain |
28 | Aspiration |
||
29 | |||
30 | |||
31 | Expressed |
||
32 | Storage space |
||
33 | Big data complexity |
||
34 | Slow computations |
||
35 | Limited time |
||
36 | Wasting time on computing |
||
37 | Make a discovery |
||
38 | Spend time on biology |
||
39 | Independence |
||
40 | |||
41 | |||
42 | Latent |
||
43 | Provenance |
||
44 | Don’t understand big data |
||
45 | Don’t get fault tolerance |
||
46 | Learning new languages |
||
47 | Respect |
||
48 | Credit for work |
||
49 | Translating discovery to med |
||
50 | |||
51 | |||
52 | |||
53 | 2 | Sarah Zaranek | h2. Deepak the Developer |
54 | 1 | Sarah Zaranek | |
55 | |||
56 | 2 | Sarah Zaranek | h3. Titles |
57 | 1 | Sarah Zaranek | Developer, Application Developer, Software Engineer |
58 | |||
59 | 2 | Sarah Zaranek | h3. Background |
60 | 1 | Sarah Zaranek | Deepak has a degree and training in computer science. Regardless of training, in this role Deepak is doing applied work creating applications and systems. Deepak works in an IT team. He is responsible for building and maintaining systems for internal users within their organization. |
61 | |||
62 | Likely program in Java but may also be a Dot NET developer. (Not sure if he knows PHP or Ruby.) |
||
63 | |||
64 | 2 | Sarah Zaranek | h3. Personality |
65 | 1 | Sarah Zaranek | Deepak is smart. He’s an orderly and systematic problem solver. He works with a team and takes direction easily from his manager. As developers go, he is relatively conservative and likes to work with established technologies that he already knows. |
66 | |||
67 | In general, his manager or an architect on the team makes the technology choices. Deepak isn’t the first to jump on the latest and greatest technologies, but wants to be well informed and do good work. He doesn’t want his skills to fall behind in the job market. He likes to work 9-5. |
||
68 | |||
69 | Deepak likes to learn in a structured way through training and certification programs. |
||
70 | |||
71 | |||
72 | 2 | Sarah Zaranek | h3, Needs Matrix |
73 | 1 | Sarah Zaranek | |
74 | |||
75 | Pain |
||
76 | Aspiration |
||
77 | |||
78 | |||
79 | Expressed |
||
80 | Working with big data |
||
81 | Understanding biology |
||
82 | Having to abandon known tools |
||
83 | Failing to deliver projects |
||
84 | Wasting time on infrastructure issues |
||
85 | |||
86 | |||
87 | Rapid development |
||
88 | Get a promotion |
||
89 | Happy “customers” |
||
90 | Work life balance |
||
91 | |||
92 | |||
93 | Latent |
||
94 | Maintaining too much technology stack |
||
95 | |||
96 | Using the wrong technology and getting stuck |
||
97 | |||
98 | Working too hard |
||
99 | |||
100 | |||
101 | Not looking bad |
||
102 | Feel like making a difference |
||
103 | Job security |
||
104 | |||
105 | |||
106 | 2 | Sarah Zaranek | h2. Alex the Administrator |
107 | 1 | Sarah Zaranek | |
108 | 2 | Sarah Zaranek | h3. Titles |
109 | 1 | Sarah Zaranek | System Administrator, IT Manager, Orvos Administrator, Developer, Lab Manager |
110 | |||
111 | 2 | Sarah Zaranek | h3. Background |
112 | 1 | Sarah Zaranek | Alex is technical. His training may not be formal technical CS training. He is not a software programmer but he can do some scripting work. He has some networking certificate and a Linux administrator certificate. |
113 | Alex is respected in the organization for being good at managing projects and keep operations running smoothly. The other people in the lab depend on him for the distribution of resources, but when there conflicts he turns to his manager (usually an Executive) to reconcile differences. |
||
114 | |||
115 | He may work in the lab, departmental IT, or in central IT that supports labs in the institution. |
||
116 | |||
117 | 2 | Sarah Zaranek | h3, Personality |
118 | 1 | Sarah Zaranek | Alex is a very task oriented person. He likes clear processes and organization. He tries to keep people happy. He is generally not a risk taker. Alex likes to learn as he goes by solving specific problems as they come up. He is the person who calls support or goes to the support forums. |
119 | |||
120 | |||
121 | 2 | Sarah Zaranek | h3. Needs Matrix |
122 | 1 | Sarah Zaranek | |
123 | |||
124 | Pain |
||
125 | Aspiration |
||
126 | |||
127 | Expressed |
||
128 | Systems going down |
||
129 | Unhappy users |
||
130 | Surprises |
||
131 | Hard to use admin |
||
132 | Security breaches |
||
133 | Wasting |
||
134 | |||
135 | |||
136 | Happy users |
||
137 | |||
138 | Latent |
||
139 | Doesn’t understand system |
||
140 | Job security |
||
141 | Respect |
||
142 | |||
143 | |||
144 | |||
145 | 2 | Sarah Zaranek | h2. Don Datacenter |
146 | 1 | Sarah Zaranek | |
147 | |||
148 | 2 | Sarah Zaranek | h3. Titles |
149 | 1 | Sarah Zaranek | Network Administrator, System Administrator, IT Tech, System Consultant |
150 | |||
151 | 2 | Sarah Zaranek | h3. Background |
152 | 1 | Sarah Zaranek | Don is self taught in doing network work and system administration. He’s always liked to hack with hardware. He was the person that you’d call if your computer wasn’t working or you couldn’t get your wireless set up. |
153 | |||
154 | Out of school he started out working in an IT department and learned on the job how to manage systems. |
||
155 | |||
156 | 2 | Sarah Zaranek | h3. Personality |
157 | 1 | Sarah Zaranek | Don is thoughtful and feels a high degree of responsibility for ensuring that the equipment he is responsible for is working. He is a highly reliable and careful person. He doesn’t like bullshit, because in his job things work or don’t work and it’s usually pretty clear. If something doesn’t work, he’d expect that the vendor will provide good support. |
158 | |||
159 | Don is protective of the systems that he runs and enforces rules and requirements. |
||
160 | |||
161 | 2 | Sarah Zaranek | h3. Needs Matrix |
162 | 1 | Sarah Zaranek | |
163 | Pain |
||
164 | Aspiration |
||
165 | |||
166 | Expressed |
||
167 | |||
168 | People not unhappy |
||
169 | Unreliable |
||
170 | Unpredictable systems |
||
171 | Hard to trouble shooting |
||
172 | Black boxes they can’t fix |
||
173 | Equipment that breaks |
||
174 | Equipment that’s hard to repair |
||
175 | Things that don’t integrate with SMS |
||
176 | |||
177 | Not being hassled |
||
178 | |||
179 | Latent |
||
180 | Have someone else sys admin cloud |
||
181 | |||
182 | Job security |
||
183 | |||
184 | |||
185 | |||
186 | 2 | Sarah Zaranek | h2. Carl the Clinician |
187 | 1 | Sarah Zaranek | |
188 | 2 | Sarah Zaranek | h2. Titles |
189 | 1 | Sarah Zaranek | Medical Geneticist, Oncologist, Pathologist |
190 | |||
191 | 2 | Sarah Zaranek | h2. Background |
192 | 1 | Sarah Zaranek | Carl has a MD and/or a PhD, and probably works at a major academic medical center where he conducts clinical research. Carl’s research is funded by a mixture of the profit from clinical care and grant money. Even though it may not be the focus of Carl’s life, Carl takes his research seriously: being cited and being published are important to him. |
193 | |||
194 | 2 | Sarah Zaranek | h2. Personality |
195 | 1 | Sarah Zaranek | Carl is a workaholic, but motivated more by prestige than by money. On the clinical care side, Carl is very risk-averse and won’t try untested methods. On the research side, Carl is a risk seeker and wants to be published in the most visible and prominent journals. |
196 | |||
197 | 2 | Sarah Zaranek | h2. Needs Matrix |
198 | 1 | Sarah Zaranek | |
199 | Pain |
||
200 | Aspiration |
||
201 | |||
202 | Expressed |
||
203 | |||
204 | Research possibilities constrained by fear of violating consent promises |
||
205 | |||
206 | Lack of access to larger data sets due to non-sharing of data |
||
207 | Discover medical breakthrough/insight |
||
208 | |||
209 | Be published in top journals, invited to speak at top conferences |
||
210 | |||
211 | Latent |
||
212 | Staff unhappy with lack of resources, or stupid processes, or unnecessary menial labor (having to copy disk drives, having to re-validate pipelines) |
||
213 | |||
214 | Be the lab of choice for fellows, postdocs, etc. |
||
215 | |||
216 | |||
217 | |||
218 | 2 | Sarah Zaranek | h2. Heather the Human Biology Researcher |
219 | 1 | Sarah Zaranek | |
220 | |||
221 | 2 | Sarah Zaranek | h2. Titles |
222 | 1 | Sarah Zaranek | Professor of human genetics; Head of major research group |
223 | |||
224 | 2 | Sarah Zaranek | h3. Background |
225 | 1 | Sarah Zaranek | PhD, probably NOT MD. Postdoc. Almost certainly a professor or at a large research institution. |
226 | |||
227 | 2 | Sarah Zaranek | h3. Personality |
228 | 1 | Sarah Zaranek | Visionary, dislikes mundane details, strong preference for open source and transparency, because they never spend money. They are good at convincing their institution to buy things for them. They only make money from grants, so grant-writing is a core skill. |
229 | |||
230 | Examples |
||
231 | Jon Seidman, Ting Wu, Steve Elledge, Jim Gusella, David Reich, Peter Park, Mark Gerstein |
||
232 | |||
233 | Needs Matrix |
||
234 | Pain |
||
235 | Aspiration |
||
236 | |||
237 | Expressed |
||
238 | |||
239 | Lack of access to larger data sets due to non-sharing of data |
||
240 | |||
241 | Inability to get enough grant money |
||
242 | |||
243 | Getting budget built into grants to cover infrastructure needs |
||
244 | Be published in top journals, invited to speak at top conferences |
||
245 | |||
246 | Latent |
||
247 | Can’t do the advanced computational stuff because they don’t have the resources to get it done. |
||
248 | Be the lab of choice for fellows, postdocs, etc. |
||
249 | |||
250 | |||
251 | 2 | Sarah Zaranek | h2. Clyde the Remote Admin |
252 | 1 | Sarah Zaranek | |
253 | |||
254 | 2 | Sarah Zaranek | h3. Titles |
255 | 1 | Sarah Zaranek | System Administrator |
256 | |||
257 | 2 | Sarah Zaranek | h3. Background |
258 | 1 | Sarah Zaranek | |
259 | 2 | Sarah Zaranek | h3. Personality |
260 | 1 | Sarah Zaranek | |
261 | Examples |
||
262 | |||
263 | Needs Matrix |
||
264 | |||
265 | |||
266 | Pain |
||
267 | Aspiration |
||
268 | Expressed |
||
269 | |||
270 | |||
271 | Latent |