Editing DUB Seminar (Winter 2022)

From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 4: Line 4:
:'''Instructor:''' [https://mako.cc/academic/ Benjamin Mako Hill] / [mailto:makohill@uw.edu makohill@uw.edu]
:'''Instructor:''' [https://mako.cc/academic/ Benjamin Mako Hill] / [mailto:makohill@uw.edu makohill@uw.edu]
:'''Office Hours:''' By appointment (I'm usually available via chat during "business hours.") You can view out [https://mako.cc/calendar/ my calendar] and/or [https://harmonizely.com/mako put yourself on it].  If you schedule a meeting, we'll meet in the Jitsi room (<code>makooffice</code>) you'll get a link to through the scheduling app.
:'''Office Hours:''' By appointment (I'm usually available via chat during "business hours.") You can view out [https://mako.cc/calendar/ my calendar] and/or [https://harmonizely.com/mako put yourself on it].  If you schedule a meeting, we'll meet in the Jitsi room (<code>makooffice</code>) you'll get a link to through the scheduling app.
:'''Meeting Times:''' Wednesday 12-1pm and three other 90-minute sessions (see [[#Class Schedule|the class schedule below]])
:'''Meeting Times:''' Wednesday 12-1pm and three other 90-minute sessions {{tbd}} (see [[#Class Schedule|the class schedule below]])
:'''Important Links''':
:'''Important Links''':
:* We will use [https://canvas.uw.edu/courses/1516345 Canvas] for [https://canvas.uw.edu/courses/1516345/announcements announcements] and [https://canvas.uw.edu/courses/1516345/assignments assignments] and for giving you grades and feedback
:* We will use Canvas for [https://canvas.uw.edu/courses/1479641/announcements announcements]
:* We will use [https://app.slack.com/client/T054LSQ4F/C02FVPE4SSY our own Slack Channel] (<code>mhcid590-dub-seminar</code> on the [https://uwdub.slack.com DUB slack] for asynchronous group chat to discuss assignments and talks, ask questions, and share information throughout the week.
:* We will use [https://app.slack.com/client/T054LSQ4F/C02FVPE4SSY our own Slack Channel] (<code>mhcid590-dub-seminar</code> on the [https://uwdub.slack.com DUB slack] for asynchronous group chat to discuss assignments and talks, ask questions, and share information throughout the week.
:* [https://dub.washington.edu/seminar.html DUB Seminar website] with the calendar, links to information about speakers, etc
:* [https://dub.washington.edu/seminar.html DUB Seminar website] with the calendar, links to information about speakers, etc
Line 20: Line 20:
I am going to approach HCID 590 as one class stretched out across the year. This means that although the core of the class—the seminar itself—will remain the same, the learning goals will shift a little  each quarter. It also means that the assignments and activities may change so that they we can all build upon what we have learned.
I am going to approach HCID 590 as one class stretched out across the year. This means that although the core of the class—the seminar itself—will remain the same, the learning goals will shift a little  each quarter. It also means that the assignments and activities may change so that they we can all build upon what we have learned.


== Winter 2022 Edition ==
I'm approach ''this quarter'' (#2) as an opportunity for you to develop your own points of view based on what you have heard in the seminars.  
 
   
In addition to the core learning goal related to '''building up an ability to understand and draw lessons from academic material about HCI''',  the fall quarter was focused on developing your skill in '''developing questions about academic material'''. This quarter will be focused on '''developing a point of view''' in regards to the same types of content. This is really more a shift in emphasis than the introduction of something entirely new. You all did a bit of the latter last quarter. We will continue to do a bit of the former this quarter as well.   
 
I will consider this quarter a total success if the following happens:
I will consider this quarter a total success if the following happens:


* Everyone attends the weekly DUB seminars, listens actively, and takes excellent notes.
* Everyone attends the weekly DUB seminars, listens actively, and takes excellent notes.
* Everyone participates thoughtfully and consistently in discussions about the work presented at seminars over the quarter, both synchronously and asynchronously.
* Everyone participates thoughtfully and consistently in discussions about the work presented at seminars over the quarter, both synchronously and asynchronously.
* Everyone is able to develop and communicate an informed POV about the material covered in the seminar.
* Everyone is able to develop opinions and attitudes about the material we cover.


== Class Schedule ==
== Class Schedule ==
Line 40: Line 38:
# Wednesday January 12: Kathryn E. Ringland (University of California Santa Cruz)
# Wednesday January 12: Kathryn E. Ringland (University of California Santa Cruz)
# Wednesday January 19: Ben Shapiro (University of Colorado)
# Wednesday January 19: Ben Shapiro (University of Colorado)
# Wednesday January 26: Sheena Erete (DePaul University) ('''''NOTE:'' Because the talk is not recorded, there will be no assignments this week.''')
# Wednesday January 26: Sheena Erete (DePaul University)
# Wednesday February 2: Aylin Caliskan (UW Information School)
# Wednesday February 2: Aylin Caliskan (UW Information School)
# Wednesday February 9: Marisol Wong-Villacres (Escuela Superior Politécnica del Litoral (ESPOL))
# Wednesday February 9: Marisol Wong-Villacres (Escuela Superior Politécnica del Litoral (ESPOL))
# Wednesday February 16: Kashyap Todi (Facebook Reality Labs)
# Wednesday February 16: Kashyap Todi (Facebook Reality Labs)
# <strike>Wednesday February 23: Sayamindu Dasgupta (UW Human Centered Design & Engineering)</strike> (Dr. Dasgupta's talk is not being recording so we're switching to an alternate talk, described below)
# Wednesday February 23: Sayamindu Dasgupta (UW Human Centered Design & Engineering)
# Wednesday February 23 (ALTERNATE): [https://dub.washington.edu/seminars/2021-02-10.html Ailie Fraser (Adobe Research)]
# Wednesday March 2: {{tbd}}
<!-- You'll notice that we're skipping October 13 because we'll all be attending the DUB retreat that week and November 26 because it is the day before Thanksgiving. There will be no seminar either week.
We're skipping March 2nd because (a) nothing has been scheduled during that period and (b) this will coincide with IxDA during which MHCI+D is not going to be having classes.
-->


You'll also notice that there will be small group mixers on both [https://dub.washington.edu/seminars/2022-01-05.html January 5] and [https://dub.washington.edu/seminars/2022-03-09.html March 9]. Although you're not required to attend these, I encourage you to attend these because they are low key, lots of fun, and provide great opportunities to connect with folks working on related stuff at UW. You can follow the links above for more information.
You'll also notice that there will be small group mixers on both [https://dub.washington.edu/seminars/2022-01-05.html January 5] and [https://dub.washington.edu/seminars/2022-03-09.html March 9]. Although you're not required to attend these, I encourage you to attend these because they are low key, lots of fun, and provide great opportunities to connect with folks working on related stuff at UW. You can follow the links above for more information.


=== Facilitated Group Discussions ===
=== Class Group Discussions ===


You are expected to attend the three facilitated group discussion events. These will be at:
You are expected to attend the three facilitated group discussion events. Once they are scheduled, I'll update the syllabus. Expecting something week following January 26, February 16, and March 2.
<!--
# Tuesday, February 1th from 3:30–5pm (in person in Alumni House classroom)
# Monday, October 25th from 3:30–5pm (in person in Alumni House classroom)
# Tuesday, February 15th from 3:30–5pm (in person in Alumni House classroom)
# Monday, November 15th from 3:30–5pm (in person in Alumni House classroom)
# Tuesday, March 1th from 3:30–5pm (in person in Alumni House classroom)
# Monday, December 6th from 3:30–5pm (''Optional'' and virtual only via Zoom)
-->


== Assignments ==
== Assignments ==


For each week that we have a DUB seminar, all of the assignments are build around a set of one-on-one pair discussions with another member of your cohort. To help these conversations happen, I'll be randomly pairing folks up with one of their classmates. I'll be posting a list of the pairings for the week on Slack on Wednesday afternoon ''after'' each seminar.
For each week that we have a DUB seminar, I'm asking folks to do at do two things each week.


Your assignment involves the following three things:
=== Post visual notes and questions [Due each Thursday following seminar @ 9pm ] ===


# Formulate three questions ''for other members of your cohort'' based on the talk. [Individual Deliverable]
By 9pm on Friday following a talk, please post to the relevant place in the [https://canvas.uw.edu/courses/1479641/discussion_topics Canvas discussion forum] with the following two things:
# Share your questions, and talk through one or more of them, with your conversation partner for the week.
# Report back to the group on Slack. [Pair Deliverable]


You are welcome to structure your pair conversation in whatever way makes sense. It can be an in-person discussion, a chat over coffee or lunch, or a short video call in Slack or Zoom. It can also be an asynchronous text chat in a set of private messages on Slack. Do whatever works for you!
;(1) A visual note capturing a single idea from the presentation: You are welcome to reflect on how the talk fits into the design challenges that you are currently addressing, highlight a research methods that you can use in the context of your projects or capture your key takeaway. Please do not try to visualize the whole presentation within your one visual note! The best notes will focus on one key point.  


I'm imagining that you will spend about half an hour talking through things in a synchronous discussion or some equivalent amount of idea development in a text chat over hours or even days.
I'm actually pretty new to visual note-taking myself but I'm not a particularly great at drawing. I know that both experience and skills will vary quite a lot across the group so don't feel bad if you're new to this too. I found these videos pretty useful:


=== Questions DUE Thursday at 9pm [Individual Deliverable] ===
* [https://www.verbaltovisual.com/what-is-sketchnoting/ Verbal to Visual / What is Sketchnoting]
* [https://www.youtube.com/watch?v=DNFk1HvlCho The 50/50 Rule of Visual Note-Taking] (YouTube)


Your individual deliverables are the three questions that you will pose to your partner. They will be due in [https://canvas.uw.edu/courses/1516345/discussion_topics the appropriate Canvas discussion] where others can see them the day after each talk. This will be similar to what we did in the Autumn quarter, but without the sketch noting and without the need to frame questions for three different audiences.
;(2) Three questions including:
:* A follow-up question for the speaker
:* A question for the cohort to discuss
:* A question for the instructor, industry, or someone else


=== Reports from Pair Discussion DUE Sunday at 5pm [Group Deliverable] ===
Every question that you ask should help you gather facts or opinions. The questions should be probing and with a purpose. It is not required of you to ask the speaker any questions during the seminar but it is highly encouraged! If you decide to ask your questions in class be sure to respect the speaker and ask questions that you are really interested in learning about.


Each group will have two deliverables which will be due at time that due at 5pm on the Sunday after each seminar:
I am asking you all to turn these in using a Canvas discussion because I want you all to be able to see each others notes and questions. I am ''not'' expecting that you will be responding to each other on Canvas. In fact, I strongly recommend that if you've got a good question for the cohort, you copy-and-paste that question into Slack in ways that are described below.


# A short summary of your conversation (shoot for about 200 words).
[[File:Canvas insert image menu.png|thumb]]
# Nominate one question (either you brought to the session or one developed up in your conversation) for the facilitated conversation in the full group discussion. Ideally this will be a question that you and your partner believe will provide an illuminating discussion and/or elicit productive disagreement from your classmates.


Each week, '''one member of each pair should do one of these things and the other member should do the other.''' You're welcome to divide this up however you like but do make sure that everybody does some of each over the quarter.
When you turn these in on Canvas, please attach your image with the ''Insert → Image → Upload Image'' menu as shown in this image. This will make is to that it's easier for your classmates to browse all the sketchnotes that folks are uploading.


Please complete both of these assignments in Slack in the following way:
=== Discussion on Slack [Due Monday following seminar @ 3:30pm] ===


# When posting summaries, please just post this as a normal message into Slack (i.e., start a new thread). Of course, be sure to both indicate that this is a reportback and mention the name of your conversation partner!
I am expecting that everybody will spend 30 minutes each week discussing each seminar on Slack, roughly split between reading others messages and posting your own thoughtful responses.
# For questions, let's try to keep these together under a single thread in Slack. I'll try to pin a message for these questions each week but go ahead and start the thread if I haven't gotten to it first and I'll pin it when I see it.


=== Vote on others' questions DUE Monday at 5pm ===
A simple starting point will be to simply pose your question for the cohort in the slack itself! If you don't feel the desire to share your question or if there are already an interesting set of question posted, you can spend time answering others.
There is one final assignment:


<ol start=3>
For the purposes of tracking participation, I am logging our Slack channel and will generate statistics each week of who has participated and when/how much they posted. I don't have a target word count that I'm looking for and I definitely understand that sometimes a thoughtful short message may reflect a bunch of research. That said, I do expect that (a) everybody will post every week, and (b) the posts will be substantial enough to suggest something in the range of 15-20 minutes of thoughtful effort.
<li>In the period between #2 above is done/due and ''before 5pm on the Monday before we have our facilitated group discussion'', look through the group discussion questions threads in the weeks since our last full group dicussion and nominate any question you are interested in for further discussion. Thumbs-up (:+1:) reactions are a totally fine way to do this!</li>
</ol>


== Grading and Assessment ==
== Grading and Assessment ==


This course is offered credit/no credit. Although you will not receive a numeric grade, passing this class is not automatic and I will assess your work and evidence of learning throughout the quarter. You can find details about my approach to assessment and my very detailed grading rubric on [[User:Benjamin Mako Hill/Assessment|my assessment page]]. Although I don't expect this to be a problem, you'll need to have credit for at least 2/3 of the assignments in the class in order to get credit for the class:
This course is offered credit/no credit. Although you will not receive a numeric grade, passing this class is not automatic and I will assess your work and evidence of learning throughout the quarter. You can find details about my approach to assessment and my very detailed grading rubric on [[User:Benjamin Mako Hill/Assessment|my assessment page]].


I will assign points for each of following items according to the weights below:
I will assign points for each of following items according to the weights below:


* Weekly Questions: 20%
* Asynchronous discussion on Slack: 40%
* Weekly Pair Discussions: 50%
* Visual notes and questions: 35%
* Facilitated group discussion: 30%
* Synchronous group discussion: 25%


== Administrative Notes ==
== Administrative Notes ==
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see CommunityData:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)