Editing DUB Seminar (Summer 2022)
From CommunityData
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 1: | Line 1: | ||
<div style="float:right;" class="toclimit-3">__TOC__</div> | <div style="float:right;" class="toclimit-3">__TOC__</div> | ||
=DRAFT! Not yet finished= | |||
:'''Design, Use, Build Seminar''' ('''HCID 590 A''') | :'''Design, Use, Build Seminar''' ('''HCID 590 A''') | ||
:'''Instructor:''' [https://kayleachampion.com Kaylea Champion] / [mailto:kaylea@uw.edu kaylea@uw.edu] | :'''Instructor:''' [https://kayleachampion.com Kaylea Champion] / [mailto:kaylea@uw.edu kaylea@uw.edu] | ||
:'''Office Hours:''' By appointment (I'm usually available via chat during "business hours.") Use | :'''Office Hours:''' By appointment (I'm usually available via chat during "business hours.") Use [https://harmonizely.com/kaylea to schedule time with me]. If you schedule a meeting, we'll meet in the Jitsi room (<code>kayleaoffice</code>) -- you'll get a link to it through the scheduling app. | ||
:'''Meeting Times:''' Wednesday 12-1pm and several other 90-minute sessions (see [[#Class Schedule|the class schedule below]]) | :'''Meeting Times:''' Wednesday 12-1pm and several other 90-minute sessions (see [[#Class Schedule|the class schedule below]]) | ||
:'''Important Links''': | :'''Important Links''': | ||
Line 39: | Line 41: | ||
# Wednesday June 22: Small Group Mixers (optional) | # Wednesday June 22: Small Group Mixers (optional) | ||
# Wednesday June 29: | # Wednesday June 29: | ||
# Wednesday July 6: | # Wednesday July 6: | ||
# Wednesday July 13: | # Wednesday July 13: | ||
# Wednesday July 20: Saleema Amershi (Microsoft Research | # Wednesday July 20: Saleema Amershi (Microsoft Research) | ||
# Wednesday July 27: | # Wednesday July 27: | ||
# Wednesday August 3: | # Wednesday August 3: | ||
# Wednesday August 10: | # Wednesday August 10: | ||
# Wednesday August 17: MHCI+D Capstone Presentations (yay!) | # Wednesday August 17: MHCI+D Capstone Presentations (yay!) | ||
Line 54: | Line 56: | ||
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. These will be at: | ||
# | # Tuesday from 3:30–5pm (in person, in Alumni House classroom) | ||
# | # Tuesday from 3:30–5pm (in person, in Alumni House classroom) | ||
# | # Tuesday from 3:30–5pm (in person, in Alumni House classroom) | ||
== Assignments == | == Assignments == | ||
For each week that we have a DUB seminar, I'm asking folks to do two things each week. | |||
I am expecting that everybody will spend a minimum of 30 minutes each week outside of the seminar time discussing each seminar on Slack. This should roughly be split between reading others' messages and posting your own thoughtful responses | === Discussion on Slack [Due Friday following seminar @ 6pm] === | ||
I am expecting that everybody will spend a minimum of 30 minutes each week outside of the seminar time discussing each seminar on Slack. This should roughly be split between reading others' messages and posting your own thoughtful responses. | |||
A simple starting point will be to simply pose a 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 questions posted, you can spend time responding to others. | A simple starting point will be to simply pose a 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 questions posted, you can spend time responding to others. | ||
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. | |||
=== | === Capstone group discussions [Due each Monday before facilitated discussions @ 6pm ] === | ||
We'll be having our three discussion groups after talks 1&2, talks 3&4, and talks 5&6. I want everyone to set aside 45-60 minutes to discuss each pair of talks with their capstone project groups. I'm hoping this makes things easier logistics-wise because you'll be meeting with these folks regularly as part of your projects. | |||
==== | ==== Example Ways of Responding ==== | ||
Your | Your discussion might take several forms: | ||
* Analysis: Why or how is the research being presented considered to be important? What conversation does it contribute to? What's puzzling or confusing about what was described? | * Analysis: Why or how is the research being presented considered to be important? What conversation does it contribute to? What's puzzling or confusing about what was described? [Analysis Response Example] | ||
* Same Approach, New Context: Given the same approach, methods, or point of view that you saw described in the talk, what would it look like to explore a different context or problem space using this approach? | * Same Approach, New Context: Given the same approach, methods, or point of view that you saw described in the talk, what would it look like to explore a different context or problem space using this approach? [ | ||
* New Approach, Same Context: Given the same overall problem space, organization, cultural phenomenon, etc. that you saw described in the talk, what would it look like to explore it using a different approach or method? | * New Approach, Same Context: Given the same overall problem space, organization, cultural phenomenon, etc. that you saw described in the talk, what would it look like to explore it using a different approach or method? | ||
* Short-term Application: How might ideas in the talks influence your capstone projects? Are there things you might approach differently? Don't let resources or time be a barrier. I'm not asking you to actually apply the ideas from the talks or to rework your projects as you go. My main goal here is prompt you to think about how you could. | * Short-term Application: How might ideas in the talks influence your capstone projects? Are there things you might approach differently? Don't let resources or time be a barrier. I'm not asking you to actually apply the ideas from the talks or to rework your projects as you go. My main goal here is prompt you to think about how you could. | ||
* Long-term Application: If you think beyond your time in the MHCI+D program, how you might apply these ideas in your career or your other work and projects? | * Long-term Application: If you think beyond your time in the MHCI+D program, how you might apply these ideas in your career or your other work and projects? | ||
* Skill Practice -- '''The Pitch''': How would you summarize one/several of these talks to others outside MHCI+D -- in the context of a meeting, coffee conversation, e-mail, etc.? Who needs to know about this research and why? Give each other a pitch and refine your delivery. | * Skill Practice -- maybe we would call it '''The Pitch''': How would you summarize one/several of these talks to others outside MHCI+D -- in the context of a meeting, coffee conversation, e-mail, etc.? Who needs to know about this research and why? Give each other a pitch and refine your delivery. | ||
* Skill Practice -- '''The Interview''': Imagine you are talking to one of the leaders of the research project being described and you're seeking a job on the team. How does your MHCI+D background and skills position you to contribute to their work? Offer each other feedback and consider potential follow-up questions or responses from a hiring manager. | * Skill Practice -- maybe we would call it '''The Interview''': Imagine you are talking to one of the leaders of the research project being described and you're seeking a job on the team. How does your MHCI+D background and skills position you to contribute to their work? Offer each other feedback and consider potential follow-up questions or responses from a hiring manager. | ||
* | * Synthesis: Thinking back over these talks and all the many other talks you've attended as part of the DUB seminar (see [https://dub.washington.edu/seminar.html#tab_previous_seminars past talks list]), what themes do you identify? Are there tensions or conflicts that emerge within these themes? | ||
Your | Your deliverables are to post the following things to pinned Slack discussion threads that I'll create for the purpose: | ||
# A short summary of your conversation, using one of the above ways of responding or your own approach (shoot for 200 words). | |||
# At least two questions or topics your group would be interested in discussing with the full group. | |||
My understand is that all the project groups have three people. As a result, I'll expect each of you to take the lead in posting your group's contributions to the pinned thread during the quarter. Also, please remember to mention your teammates when you post so that I know whose conversation you are reporting back about! | My understand is that all the project groups have three people. As a result, I'll expect each of you to take the lead in posting your group's contributions to the pinned thread during the quarter. Also, please remember to mention your teammates when you post so that I know whose conversation you are reporting back about! | ||
Line 98: | Line 101: | ||
== 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: | 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: | ||
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 slack conversation: 40% | * Weekly slack conversation: 40% | ||
* | * Bi-weekly group discussions: 30% | ||
* | * Facilitated group discussion: 30% | ||
== Administrative Notes and Resources == | == Administrative Notes and Resources == |