Products/Pasteboard/UserResearch - Revision history

Dan Mills at 18:27, 5 September 2013

2013-09-05T18:27:23Z

Dan Mills at 18:19, 5 September 2013

2013-09-05T18:19:20Z

Dan Mills: Created page with "= User Profile = = Methodology = = Insights, Themes, Workflows = = JTBD & Constraints = = fixme - previous text = In our user research, we gathered valuable information a..."

2013-09-05T17:24:37Z

Created page with "= User Profile = = Methodology = = Insights, Themes, Workflows = = JTBD & Constraints = = fixme - previous text = In our user research, we gathered valuable information a..."

New page

= User Profile =

= Methodology =

= Insights, Themes, Workflows =

= JTBD & Constraints =

= fixme - previous text =

In our user research, we gathered valuable information about how teachers in the San Francisco Bay Area ("Silicon Valley") prepare and use resources, particularly digital ones. We held qualitative, 1x1 interviews, some in context (at a school). We gathered data:

[[file:Teacher_Research.jpg|400px|thumb|left|Teacher Research]]
 

While we realize that these teachers do not represent the needs of all teachers everywhere, we are starting with their needs and building from there. Here are some high-level insights. These are all paraphrased and summarized, but allow us to get into the shoes of a teacher, to some extent:

* No matter where it comes from, I always have to adapt content, but it is hard, so I don't always do it.
* A 'successful day' is based on the feedback that I get regarding the expectations I have for my students and for myself.
* Prepping is an intense planning and customization activity subject to many external pressures like moving schedules, changing standards, and team changes.
* Differentiation allows me to engage students at varied levels or interests, but it requires extra effort, immediate feedback, and deep subject expertise.
* I consider the textbook to be just an outline, so I'm always looking for new, relevant content, even though it takes a lot of time.
* I recognize creation and curation as both forms of ownership, but neither stops me from sharing with my colleagues.
* I complement my teaching with additional materials, but it's hard to control the exact experience and learning path.
* Tool lock-in is a worry, but if it's clear how it will fit my workflow from the start I might use it.
* Not all kids learn in the same way, so I like to mix things up to keep myself and the kids engaged.
* Staying on top of plans and dealing with multiple classrooms and limited class time is challenging.
* I have a strong sense of right and wrong, but the legal framework doesn't match that.
 

Here's a snapshot of what a day/week/year looks like, at a very high level:

[[file:Teacher_Research_Day.jpg|400px|thumb|left|Teacher's Journey]]

@@ Line 5: / Line 5: @@
 Roughly speaking:
 # Develop user interview criteria and interview guide.
-# Interviews and field research. Gather qualitative data.
+# Qualitative interviews and field research. Gather data.
 # Develop themes and insights, followed by needs, constraints, and behaviors/tasks
 # Develop ideas and opportunities, followed by prototypes
@@ Line 54: / Line 54: @@
 * I have a strong sense of right and wrong, but the legal framework doesn't match that.
-= Behaviors & Tasks =
+= Behaviors & Tasks, JTBD & Constraints =
-Here's a snapshot of what a day/week/year looks like, at a very high level:
+Here's a snapshot of what a day/week/year looks like, at a very high level. Each block has a "Jobs to be done" and "Constraints" section associated with it, which later on were instrumental in developing ideas and opportunities.
 [[file:Teacher_Research_Day.jpg|400px|thumb|left|Teacher Journey]]
 <br clear="all"><br>
-= JTBD & Constraints =
+= Opportunity =

@@ Line 1: / Line 1: @@
-= User Profile =
+= Methodology =
-= Methodology =
+Of course, this process blends into the product creation cycle, it is not a static set of work. That is, the prototypes are initial product ideas, and form the basis of iterations which yield additional data, which we use to validate our data and learn more, which in turn leads to the next prototype, and so on.
-= Insights, Themes, Workflows =
+These were a starting point, and once we developed an initial interview guide, we scheduled user interviews. Some were in context (at a school), though not all. All of the teachers were in the San Francisco South Bay Area ("Silicon Valley").
-= JTBD & Constraints =
+(todo: more info on interviews here)
-= fixme - previous text =
+= Themes & Insights =
-In our user research, we gathered valuable information about how teachers in the San Francisco Bay Area ("Silicon Valley") prepare and use resources, particularly digital ones. We held qualitative, 1x1 interviews, some in context (at a school). We gathered data:
+We gathered a lot of data:
 [[file:Teacher_Research.jpg|400px|thumb|left|Teacher Research]]
 <br clear="all"><br>
-While we realize that these teachers do not represent the needs of all teachers everywhere, we are starting with their needs and building from there. Here are some high-level insights. These are all paraphrased and summarized, but allow us to get into the shoes of a teacher, to some extent:
+While we realize that these teachers do not represent the needs of all teachers everywhere (given our Silicon Valley focus), we did gather some very interesting insights which allow us to begin with these teacher communities before expanding to others. Here are top-level insights we learned (from the POV of the teacher):
 * No matter where it comes from, I always have to adapt content, but it is hard, so I don't always do it.
@@ Line 27: / Line 53: @@
 * Staying on top of plans and dealing with multiple classrooms and limited class time is challenging.
 * I have a strong sense of right and wrong, but the legal framework doesn't match that.
-<br>
 Here's a snapshot of what a day/week/year looks like, at a very high level:
-[[file:Teacher_Research_Day.jpg|400px|thumb|left|Teacher's Journey]]
+[[file:Teacher_Research_Day.jpg|400px|thumb|left|Teacher Journey]]
 <br clear="all"><br>