<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Caro Williams-Pierce on Medium]]></title>
        <description><![CDATA[Stories by Caro Williams-Pierce on Medium]]></description>
        <link>https://medium.com/@carowp?source=rss-3b4a210372ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*KMjYl7BUgVaopu5y2i8Rww.jpeg</url>
            <title>Stories by Caro Williams-Pierce on Medium</title>
            <link>https://medium.com/@carowp?source=rss-3b4a210372ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:47:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@carowp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Remixing & Reimagining: Research Papers Gone Rogue]]></title>
            <link>https://medium.com/hcil-at-umd/remixing-reimagining-research-papers-gone-rogue-7a885bbdd8f9?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a885bbdd8f9</guid>
            <category><![CDATA[hci-education]]></category>
            <category><![CDATA[remix]]></category>
            <category><![CDATA[chi]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 17:03:15 GMT</pubDate>
            <atom:updated>2025-12-16T17:03:15.607Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written, organized, and edited by Simran Bhatia, Jackson DeVico, Jasmine Voon, and Caro Williams-Pierce. Each remix by a different student, named below.</em></p><p>Every new Human-Computer Interaction Masters (HCIM) student in the College of Information starts their very first semester with the same course: INST631, Fundamentals of Human-Computer Interaction. And as soon as class starts up, students are faced with their first project, meant to introduce them to the thriving, complicated, beautiful world of <a href="https://dl.acm.org/doi/proceedings/10.1145/3706598">CHI</a>.</p><p>Students dig through the past two years of proceedings papers, read a few that they find interesting, and then ‘remix’ one paper to be more accessible to non-HCI audiences. Although inspired by the American Association for the Advancement of Science’s<a href="https://www.scienceintheclassroom.org/"> <em>Science in the Classroom</em></a> annotation project, HCIM students each develop their own approach, resulting in a wide variety of remixes. We share some of those remixes below with brief descriptions, a couple of images, and a link to each full remix. (And we hope the authors take these remixes as intended: an homage to their fascinating and incredible work! And perhaps a thought-provoking hook that makes you want to go read their whole paper — we’ve linked each paper for easy access to their brilliance.)</p><p>We’ve broken down the remixes into three categories: Point of View — where you are not just the reader, but maybe also the participant or the researcher; Product Recreation — where the students rebuilt and iterated the product originally described in the paper; and Paper Re-Presentation— where the paper is modified in some way to enhance the reading experience.</p><blockquote><strong>Some of the remixes are Figma prototypes — if you’re new to that format, here’s what to expect:</strong> Figma prototypes support designers in creating models of webpages that are not yet fully functional. There are two ways to navigate prototypes. The first is to click on buttons and links as you would in a regular app/webpage. The second is to use the forward/backward arrows that appear at the bottom of the screen to navigate through the flow in the way the designer intended. As the purpose of prototypes is to demonstrate general flow and design, it is possible that not all buttons or links are functional — so just keep clicking and tapping away, regardless!</blockquote><h3><strong>Point of View</strong></h3><p>These students reinterpreted the paper through alternate lenses, creating guided walkthroughs and interactive experiences that offer fresh perspectives on the original research.</p><p>Emilie Miranda incorporated the findings of <em>Digital Legacy Systems for Young Adults: Emphasizing Relationship-Oriented Perspectives and Physical Artifacts in Death Preparation</em> (<a href="https://dl.acm.org/doi/10.1145/3706598.3713764">Kwon et al. (2025) paper here</a>) into a Figma prototype modeled after the app used in the original study. Her recreation transforms the research into a practical, hands-on product where users can workshop a digital legacy while uncovering the study’s insights along the way. As you click through<a href="https://www.figma.com/proto/1iSkiGc0zz8eAmd9YWJYbi/Emilie-Miranda---Mission-1-Redesign?node-id=9-2&amp;p=f&amp;t=Ek5mg7hVzzpXJZ2q-1&amp;scaling=scale-down&amp;content-scaling=fixed&amp;page-id=0%3A1&amp;starting-point-node-id=9%3A2"> the prototype available here</a>, you take on the role of a research participant.</p><figure><img alt="Three screenshots from Emilie’s prototype: Story Mode, Participant Mode, and Final 5 Photographs." src="https://cdn-images-1.medium.com/max/1024/1*SvfJbVBv9nVxt_8pIwzyZg.jpeg" /><figcaption>A visual summary of Emilie’s prototype.</figcaption></figure><p>Anushka Chimote introduced the research <em>Augmented Reality Cues Facilitate Task Resumption after Interruptions in Computer-Based and Physical Tasks</em> (<a href="https://dl.acm.org/doi/10.1145/3613904.3642666">Bahnsen et al. (2024) paper here</a>) through a narrative lens. In an <a href="https://app.animaker.com/animo/ZrCqgzuwTcT3Y6pa/">animated video available here on Animaker</a>, viewers are guided through the research process and findings via engaging animated infographics. The video follows the perspective of Sarah, a busy nurse who encounters various interruptions throughout her workday. This study focuses on people who regularly multitask and could benefit from support in resuming disrupted workflows via virtual nudges.</p><figure><img alt="Experiment methodology information from the animation." src="https://cdn-images-1.medium.com/max/1024/1*xtAnz33oVN-vah8Yz9RYag.jpeg" /><figcaption>Captures from Anushka’s animation video.</figcaption></figure><p>Zayneb Omer presented the study <em>Designing Accessible Audio Nudges for Voice Interfaces</em> (<a href="https://dl.acm.org/doi/10.1145/3706598.3713563">Jamshed et al. (2025) paper here</a>) as an interactive paper walkthrough. Using <a href="https://www.figma.com/proto/6OnnaEWJKWkEiBxcR9xlOF/Designing-Accessible-Audio-Nudges-for-Voice-Interfaces?node-id=2002-3276&amp;t=XJmUdY60W8dbl4Sp-1&amp;scaling=scale-down&amp;content-scaling=fixed&amp;page-id=0%3A1">a Figma prototype available here</a>, she designed a self-paced digital interface where users can follow a virtual researcher through each stage of the study’s findings, making the experience both informative and immersive.</p><figure><img alt="Introduction to study and methods, with different nudge options to choose from." src="https://cdn-images-1.medium.com/max/1024/1*iO20zbWbf2JppLthj7iv8w.jpeg" /><figcaption>Zayneb’s interactive paper walkthrough.</figcaption></figure><blockquote>FYI: Some students chose to include logos and other materials of the Association for Computing Machinery Digital Library, as the publisher of the original works being remixed. <em>These remixes are NOT actually approved or reviewed in any way by ACM! </em>Instead, the use of these materials for educational purposes qualifies as fair use under the U.S., Section 107 of the Copyright Act.</blockquote><h3>Product Recreation</h3><p>Some students took it upon themselves to prototype design interventions presented in their chosen paper.</p><p><em>This Game SUX: Why &amp; How to Design Sh@*!y User Experiences</em> (<a href="https://dl.acm.org/doi/10.1145/3706598.3713246">Cormier et al. (2025) paper here</a>) presents themes for designing intentionally frustrating games to create meaningful experiences. Surya V Iyer incorporated these themes into a game prototype, using elements such as unintuitive controls to add challenge to an otherwise simple game. Video embedded below — or if you want to go through the complicated process to play/experience it yourself, you can <a href="https://drive.google.com/file/d/1psqJwMqZHy5W6-_RETGKA_bPAjvMvJhp/view?usp=sharing">download the winBuild.zip file</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FklVtp72gGXw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DklVtp72gGXw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FklVtp72gGXw%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/36180719e46553ccf311c899c37d196c/href">https://medium.com/media/36180719e46553ccf311c899c37d196c/href</a></iframe><blockquote>(Khondaker Mushfiqur Rahman also remixed this paper, and has a <a href="https://medium.com/hcil-at-umd/when-pedagogy-meets-ux-design-2432ef1bc82f">separate article</a> describing his process for doing so.)</blockquote><p>Oluwanifemi Eniola Orekoya created a Figma prototype of ReminiBuddy, an app designed to elicit memory recall for older generations, proposed in the paper <em>Chorus of the Past: Toward Designing a Multi-agent Conversational Reminiscence System with Digital Artifacts for Older Adults</em> (<a href="https://dl.acm.org/doi/10.1145/3706598.3713810">Sun et al. (2025) paper here</a>). In her <a href="https://www.figma.com/design/rUzTCYpfcXNhurYFruu8VN/ReminiBuddy?node-id=245-1180&amp;t=yw2xysTG2jigr6Ha-1">prototype available here</a>, Oluwanifemi features a home page, an artifact reminiscence page, and a saved memories page.</p><figure><img alt="Three different screens: choosing an artifact, reminiscing about that artifact in a memory, and looking back at saved memories." src="https://cdn-images-1.medium.com/max/1024/1*69uMKOxgGPcj6J0QrZoMdw.jpeg" /><figcaption>Olowanifemi’s prototype screens.</figcaption></figure><h3>Paper Re-Presentation</h3><p>Other students chose to redesign the research paper reading experience, in order to enhance the reader’s interaction with the original paper itself.</p><p>For example, Barath Vaithilingam chose the paper <em>“Don’t You Dare Go Hollow”: How Dark Souls Helps Players Cope with Depression, a Thematic Analysis of Reddit Discussions</em> (<a href="https://dl.acm.org/doi/10.1145/3706598.3714075">Väkevä et al. (2025) paper here</a>)<em>.</em> For his <a href="https://dontgohollow.netlify.app/">redesign available here</a>, he gamified the experience of reading his research paper, by creating a web app in which users click through sections of the paper, and earn an “award” for every section they complete. This incorporates a reward system into the reading experience, establishing a sense of accomplishment for progress users make, and incentivizing them to continue reading.</p><figure><img alt="The first two paragraphs of the paper, with shiny golden coins as rewards for reading." src="https://cdn-images-1.medium.com/max/1024/1*dkD8S5gtYgfkcYfBujUQvQ.jpeg" /><figcaption>Bharath’s reading and reward layout.</figcaption></figure><p>Niti Poddar decided to enhance the experience of reading her selected paper, <em>Proactive Conversational Agents with Inner Thoughts</em> (<a href="https://dl.acm.org/doi/10.1145/3706598.3713760">Liu et al. (2025) paper here</a>), by redesigning its ACM Digital library page. She created a <a href="https://www.figma.com/proto/lYQkHwciK13kgUMvX1MjO7/Untitled?page-id=0%3A1&amp;node-id=3-113&amp;viewport=-1006%2C703%2C0.42&amp;t=ZP617f4TUFfCgbkC-1&amp;scaling=min-zoom&amp;content-scaling=fixed">Figma prototype available here</a> that divides the paper into sections. Each section is presented in its original ACM written format, but with the addition of two optional features. Selecting “Explain like I am a kid” alters the content into a simplified child-friendly explanation, while selecting “Visualize” converts it into a mindmap.</p><figure><img alt="Original abstract, Explain Like I’m a Kid simplified abstract, and visualized abstract." src="https://cdn-images-1.medium.com/max/1024/1*6hPcp7DLbY-OdZj7TnmYew.jpeg" /><figcaption>Niti’s three different ways to ‘read’ the abstract.</figcaption></figure><p>Finally, Jackson DeVico chose the paper <em>Pathways of Desire: Enhancing Navigation and Sense of Community Through Player-Generated Desire Paths</em> (<a href="https://dl.acm.org/doi/full/10.1145/3706598.3713191">Lankes et al. (2025) paper here</a>), which explored physical navigation in video games. They reformatted the paper as <a href="https://drive.google.com/file/d/1Bg2CW05W0jJ8_BRJD-CuK3-L9G9AUKpt/view">an svg file available here</a>, presenting the content in a more visual, non-linear manner. This format emphasizes the reader’s navigation through the information presented in the paper, mirroring the paper’s focus on player navigation.</p><figure><img alt="A nonlinear way to experience the paper." src="https://cdn-images-1.medium.com/max/1024/1*mBIlvmNNU9FI__IGUmmHpA.jpeg" /><figcaption>Jackson’s non-linear representation of the paper.</figcaption></figure><h3>Conclusion</h3><p>The process of ‘remixing’ a paper presents students with the opportunity to engage with their papers in nontraditional ways. This can be challenging, or even frustrating for some students, but ultimately it individualizes their experience with the assignment. Remixing papers also provokes students to consider the reasoning behind the traditional research paper format, the accessibility issues that come with it, and the potential benefits of alternative formats. This principle can also be applied to many other designs we encounter everyday, encouraging students to consider how conventional systems they interact with in their everyday lives could be improved, or presented differently. In other words, remixing a paper is just another way of <em>doing HCI</em> by thinking about how to re-design our world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a885bbdd8f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hcil-at-umd/remixing-reimagining-research-papers-gone-rogue-7a885bbdd8f9">Remixing &amp; Reimagining: Research Papers Gone Rogue</a> was originally published in <a href="https://medium.com/hcil-at-umd">Sparks of Innovation: Stories from the HCIL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tracing the History of Designs: Music Edition]]></title>
            <link>https://medium.com/hcil-at-umd/tracing-the-history-of-designs-music-edition-7b5f99d7a583?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b5f99d7a583</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Tue, 26 Nov 2024 15:49:02 GMT</pubDate>
            <atom:updated>2024-11-26T15:49:02.057Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tracing the History of Designs: The Music Edition</h3><p><strong>Editors:</strong> Sohayainder Kaur, Udaya Shankar K R, &amp; Caro Williams-Pierce</p><p><strong>Contributing Authors</strong> (alphabetical by first name): Antonya da Silva,<em> </em>Ayesha Ajaz, Hansika Murugu, Marilyn Ortega, Nikita Khowala, &amp; Yujia Wang.</p><p>Design, like all human activity, happens within a personal, social, and historical context. Which means that we, as humans living out our numbered years, use designed objects that change radically over time, with each change influencing our own experiences in the world. In <em>INST631: Fundamentals of Human-Computer Interaction</em>, we were asked to <a href="https://medium.com/hcil-at-umd/loud-gleeful-learning-86f603f27497">play around</a> with this idea, and trace our own experiences with designed objects.</p><p>In other words, we thought back to our childhood days and the designed objects we used then, and traced those objects forward through time, to today. We reflected on how the representations, interactions, affordances, etc. of those designed objects have changed, and how those changes had a ripple effect and fundamentally changed our own experiences with those objects and in the world. We then drafted rough visual representations of our reflections, and those that focused on <em>listening to music</em> appear here, in the Music Edition.</p><h3><em>“I can’t imagine a single day of walking without my music”</em></h3><p><em>From portable cassette players to smartphones, by Nikita Khowala (left) and Hansika Murugu (right).</em></p><figure><img alt="Sketches of music gear from cassette tapes to streaming apps on a phone" src="https://cdn-images-1.medium.com/max/1024/1*DRrvIxX6QPaIVwtp8SaGCQ.png" /></figure><h3>Musings on the history of headphones</h3><p><em>Sketching through time, by Marilyn Ortega.</em></p><figure><img alt="Sketches of headphones from the 1910s to the 2020s" src="https://cdn-images-1.medium.com/max/1024/1*mF2fQcg1n0muVclR5N2Oog.png" /></figure><h3>From boombox public sound to private EVERYTHING</h3><p><em>From sharing music loudly with the world, to privately watching your favorite Netflix show on the bus, by Yujia Wang.</em></p><figure><img alt="Boombox (“All we hear is radio ga ga!!!) to Mp3 player to Mp4 player to iPhone/iPad with music, films, and AirPods" src="https://cdn-images-1.medium.com/max/1024/1*GzjW112-oOqC5SOwp-dMag.jpeg" /></figure><h3>From “weird wires” to no wires at all</h3><p><em>From big, loud, and complicated to small with no wires (but still loud), by Antonya da Silva.</em></p><figure><img alt="Timeline from speakers in the 1990s (heavy, easily tipped, and full of ‘weird wires’) to the 2020s (no more wires, easy music discovery through streaming)." src="https://cdn-images-1.medium.com/max/1024/1*HwxHFlbzc2TRpsB-LjJDzg.png" /></figure><h3>Sharing the feelings…</h3><p><em>It’s rock and roll, and sweet like cinnamon, and sharing the tunes you found, by Ayesha Ajaz.</em></p><figure><img alt="A digital collage of music-related ideas, including screenshots, social media posts, and pictures of the author." src="https://cdn-images-1.medium.com/max/1024/1*nHKBi-LaZtxvzDrJUP6_eQ.jpeg" /></figure><p>We hope you’ve enjoyed the Music Edition of tracing design through time — stay tuned* for more! (* pun absolutely intended)</p><p><em>Individual artwork copyright belongs to each individual author. Do not use without their written permission.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b5f99d7a583" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hcil-at-umd/tracing-the-history-of-designs-music-edition-7b5f99d7a583">Tracing the History of Designs: Music Edition</a> was originally published in <a href="https://medium.com/hcil-at-umd">Sparks of Innovation: Stories from the HCIL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The limit of perfection]]></title>
            <link>https://medium.com/hcil-at-umd/the-limit-of-perfection-ba69bc93e511?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba69bc93e511</guid>
            <category><![CDATA[perfectionism]]></category>
            <category><![CDATA[perfection]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Wed, 23 Oct 2024 16:58:11 GMT</pubDate>
            <atom:updated>2024-10-23T16:58:11.189Z</atom:updated>
            <content:encoded><![CDATA[<p>Caro Williams-Pierce, Tamara Clegg, Stacy Surla, &amp; Jason Aston</p><p><em>Being human is </em>hard. <em>So, sometimes we need a reminder to look back at all we’ve achieved, instead of looking forward at the vast mountain of things-yet-to-be-done that never seems to get any smaller!</em></p><p><em>So, from our little Design Club, some musings on the seductive and unreachable nature of perfection.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rzFcn4qn9Jlqe33ChwlQoA@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hv5kU1i3M0znY9ifRHOeGQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ThBSnkpzbEviJIkxBJzjYA@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UMA_mz8oCv-mHekgXhrZHA@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JHMi47aukk7MkHfsBsio5w@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0X-iLpM6UgYI-DiSjfd_lQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3k1UgCW6lDwvDBHg6snGpg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OCHU8A0K1KPQOBCSAPiqzQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nCVlyrxRb9x4NbHVmNhl0A@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_z6elt8WUSJe_JF7nLfVGA@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BsvIHETOoXwOt9sFg5a1CQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohvouxwfPLd0_EIHO_wr-A@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2wJjsaa7l3hZ3ILu7KfomQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XjD86OfpBgzvaZS2B0RVXQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f7nsT6HnrPwyLZs5dZm_BA@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cafDERQkRv6fWgpSg1qqQQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wYP5CZ51cejWrImnlDNSaw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zzci_2a2N0RAt4hc51y92Q@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oeNFbyb5ML6zE--Yej0RVQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*khsIvJhRLFS1Gv0rJ3TjTw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUWE23zzKDxeZUgbezzlIw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g4g0vf_EN37DL8E2hrWdQg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxe_8T1NdjrGmwiiNKG3CA@2x.jpeg" /></figure><p><em>This work is licensed under a </em><a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"><em>CC BY-NC-SA 4.0 license</em></a><em>. Attribution must include a link to this work.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba69bc93e511" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hcil-at-umd/the-limit-of-perfection-ba69bc93e511">The limit of perfection</a> was originally published in <a href="https://medium.com/hcil-at-umd">Sparks of Innovation: Stories from the HCIL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Changing AC:NH controls for one-handed play]]></title>
            <link>https://carowp.medium.com/changing-ac-nh-controls-for-one-handed-play-a62049294328?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/a62049294328</guid>
            <category><![CDATA[one-hand]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[animal-crossing-switch]]></category>
            <category><![CDATA[gaming]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Fri, 31 May 2024 00:14:12 GMT</pubDate>
            <atom:updated>2024-05-31T00:22:28.754Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve never remapped console controls before, so when I needed to figure how to play AC:NH with only one hand, all the otherwise useful comments online didn’t actually go step-by-step through the process. So here you go!</p><p><em>Mapped for right dominant hand, for casual meandering play, held like this:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*QTCBJL-NnUP3svoxJ2fGyQ.jpeg" /></figure><h3><strong>Step 1</strong></h3><p>Go to the System Settings button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2U_MGBTsT9eObneRgF1Dbg.jpeg" /></figure><h3><strong>Step 2</strong></h3><p>Scroll down to the <em>Controllers and Sensors</em> option:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jebZNglaZtiBMMinOJLiVw.jpeg" /></figure><h3>Step 3</h3><p>Select <em>Change Button Mapping</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5tysQCR4hSljmCTRTtQ8Qg.jpeg" /></figure><h3>Step 4</h3><p>Choose the <em>Joy-Con</em> you want to remap — in this case, the one on the right. The color will match yours — and yes, mine is a lovely orange color!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ebKFi6q99vpsxCVYrK5qEQ.jpeg" /></figure><h3>Step 5</h3><p>Then, select <em>Change</em> to begin your button mapping:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrB00RiOmxAI2AE6WL6MoA.jpeg" /></figure><h3>Step 6</h3><p>Now, select the first button to remap:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IcgxJOWfIz0A3uI9LHlmuA.jpeg" /></figure><p>We’re going to remap the SR button to the Down Button, so that when you click the top narrow button on the inside of the Joy-Con, you’ll store whatever tool you’re holding.</p><h3>Step 7</h3><p>After clicking the SR button, a menu will pop up. Scroll down to find and then select the <em>Down Button</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bhbGaCwYuHqROseUxftMLw.jpeg" /></figure><p>After you select the Down Button, the menu should automatically close — but if it doesn’t, click B to go back.</p><p>Now, you can see that the SR button symbol has turned green, to show that it’s been remapped:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6PY3gKsaptMpN5KzL5I9Bg.jpeg" /></figure><h3>Step 8</h3><p>Now, remap two more buttons the same way:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lvWfeRTTiuesiI0wrBQlJw.jpeg" /></figure><p>We’re remapping <em>SL</em> — the bottom narrow button on the inside of the Joy-Con — to ZL. That way, clicking that bottom narrow button will open your NookPhone and all the apps.</p><p>Then, we’re remapping <em>ZR</em> to the Up Button, so that when you hit ZR (which is the trigger-like button at the top and back of the Joy-Con), all your tool choices will open up. Gotta be able to switch from fishing to digging, after all!</p><h3>Step 9</h3><p>Now, let’s change the <em>Control Stick Settings</em> — we want the Right Control Stick to be Move (Walk/Run) instead of Pan Camera. (It’s a little annoying to not be able to pan the camera, yes, but not as annoying as being stuck in one place!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r1R2uFuNIlTGYBH7hIzjOA.jpeg" /></figure><h3>Step 10</h3><p>Now, see <em>Change to Left Stick</em>?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W8kmaGXExg7jucmj0CMf4A.jpeg" /></figure><p>Tap it so that it says On — and the image will change:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rJJWKSIApcR-qzKPoed2tw.jpeg" /></figure><p>Instead of clicking A for OK, you’ll want to click B for Back. (Don’t worry — it’ll save your change!)</p><h3>Step 11</h3><p>The final mapping looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBArkt8glNCMtUPk0FXD9g.jpeg" /></figure><p>Then, click the Done button in the bottom right.</p><h3>Step 12</h3><p>Lastly, save this mapping so that you can easily turn it off and on!</p><p>After hitting Done, you can scroll down slightly to see <em>Save as Preset Mapping:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3qHuAXCk_DByLHjTBc5Duw.jpeg" /></figure><p>Select that, then a Save Slot — with a name so you can find it easily again!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tHty7lIeyRlYpFzuTJNZgA.jpeg" /></figure><p>And now, you’re done! Enjoy your time relaxing on your island ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a62049294328" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Loud Gleeful Learning]]></title>
            <link>https://medium.com/hcil-at-umd/loud-gleeful-learning-86f603f27497?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/86f603f27497</guid>
            <category><![CDATA[play]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[adult-education]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Wed, 20 Oct 2021 12:46:57 GMT</pubDate>
            <atom:updated>2021-11-01T18:25:19.770Z</atom:updated>
            <content:encoded><![CDATA[<h4>Supporting and provoking adult play in formal contexts</h4><figure><img alt="Three people excitedly pointing at a laptop screen" src="https://cdn-images-1.medium.com/max/1024/1*9FHrjYvX1os0qVBI3MVkQg.jpeg" /></figure><p>The best learning — or maybe just my favorite type of learning — is often messy, full of happy cross-talk, and with lots of friendly disagreements. I’ve had the luxury of facilitating a number of these types of learning experiences in the past decade, both at academic conferences and in formal classrooms at the undergraduate and graduate levels, and I wanted to share my template for planning these chatter-filled, activity-centered, delightfully unpredictable sessions!</p><blockquote>tl;dr: Figure out your goal (<em>not</em> a learning objective!) and craft a ‘provocative argument’ that you can introduce to your participants. A good provocative argument pushes everyone to discuss and disagree, which can then be extended directly into a hands-on activity. Discussing that hands-on activity and how it relates to your provocative argument leads in turn to preparing the participants for the next learning session.</blockquote><figure><img alt="an hourglass with half the sand remaining" src="https://cdn-images-1.medium.com/max/1024/0*JRCj-NTh5BIMZlqe" /><figcaption>Photo by <a href="https://unsplash.com/@aronvisuals?utm_source=medium&amp;utm_medium=referral">Aron Visuals</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This post assumes about an hour of learning time — add more (and different types) of activities and discussions if you have more time! If you have a three-hour class block, for example, I recommend three hands-on activities, and at least one should get everyone out of their chairs and moving around.</p><h3>First, what is your goal?</h3><p>If you are or have been a teacher at any level, your first instinct will probably be to reach for a learning objective. If this happens, smack your hand and tell yourself NO! The messiness of loud gleeful learning means that you are opening up a possibility space, not defining a specific target to which you want the participants to travel directly towards and meet. Instead, pick a topic you want everyone to (loudly, gleefully) argue <em>around</em>. For example, in my Games as Emergent Experiences class, we have a week in which my goal is to have the students argue about how paired failure and feedback contribute to the experience of flow. As another example, in my Mathematical Play Working Group at <a href="http://www.pmena.org/">PME-NA</a>, we often find ourselves arguing around the tension between <em>the content objective</em> and the <em>play objective — </em>which should we forefront? Can we forefront both? Or is this a continuum, where we have to pick which end we want to be closest to (and which we want to be furthest from)?</p><p>Both of these arguments are unanswerable — or rather, there are multiple answers to each — because the experience of failure, of learning, of mathematical play, is inherently based upon the unique nature of the human being doing the experiencing. Which means these are perfect topics for people to argue around!</p><h3>Second, use your goal to build a provocative argument.</h3><figure><img alt="various colored pins pushed into a map" src="https://cdn-images-1.medium.com/max/1024/0*c_O6ukALMh5fDP-f" /><figcaption>Photo by <a href="https://unsplash.com/@delfidelarua7?utm_source=medium&amp;utm_medium=referral">delfi de la Rua</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A provocative argument isn’t about <em>telling</em>, but <em>describing</em> <em>the complex and often conflicting landscape</em> of the goal. Sharing three very different definitions of mathematical play is a good way to get folks at PME-NA arguing, because everyone that attends our working group already has opinions about mathematics content, classrooms, and play. And those opinions are often implicit and quite different, so sharing the three different definitions forces the attendees to figure out why and how they disagree with some definitions and not with others. (Plus, we are fortunate enough to have facilitators that range in expertise from early childhood mathematics play to undergraduate+ mathematical play — so the content differences always provoke delightful conversations!)</p><p>As a classroom example, one week in my course involves examining and experiencing failure, feedback, and flow. I build the provocative argument by assigning readings, a video, and a game that together create a partial and sometimes conflicting account of the relationship between these three. This semester, as they had already gained a strong grounding in feedback and failure in previous weeks, we focused on introducing flow into that familiar landscape. So, I had them read about <a href="https://dl.acm.org/doi/fullHtml/10.1145/1232743.1232769?casa_token=HM2hoqRlUYkAAAAA:cn4JrK9ON_O417SsgCbeeZvGPh9zncLXC6QpX87pY3SttjAx_dCJjeuEmL0wai-epgLSORB7TKEc3w">flow</a> and <a href="https://www.frontiersin.org/articles/10.3389/fpsyg.2018.01682/full">immersion</a>, watch a talk by <a href="https://www.youtube.com/watch?v=fXIeFJCqsPs">Csikszentmihalyi</a>, and play <a href="https://thatgamecompany.com/flower/"><em>Flower</em></a><em> </em>(with the back-up of <a href="https://www.playrix.com/en/games/fishdom"><em>Fishdom</em></a><em> </em>if tech issues prevents them from playing <em>Flower</em>; but see Footnote 1 about the drawbacks of using <em>Fishdom</em>). This Read-Watch-Play approach sets the provocative landscape for their loud gleeful classroom learning — they then bring conflicting understandings and experiences directly into our shared space. So a couple little questions about <em>Flower</em> usually turns on the loud gleefulness — did you experience flow? What failure and feedback did you see? Did you like or dislike the game, or were you just bored and didn’t care at all?</p><figure><img alt="A beautiful field with red and yellow flowers, and a small cluster of flower petals whirling in the wind" src="https://cdn-images-1.medium.com/max/1024/1*aCIn0VPfQV4nRbo0z1QfmA.jpeg" /><figcaption>An image from the player point-of-view in <em>Flower</em>.</figcaption></figure><p>There are many other ways to set the provocative argument beyond sharing three conflicting definitions of mathematical play or using a Read-Watch-Play system — check out Footnote 2 for some suggestions!</p><h3>Third, let ’er rip!</h3><p>A powerful provocative argument means that people will want to start discussing right away. So I usually start by giving folks some time to argue about the landscape, which has several additional bonuses:</p><ol><li>They can tentatively start using the language that you have introduced in a low-stakes environment, by asking each other questions;</li><li>They can, as a group, begin working towards a shared understanding of any new language;</li><li>They tend to be surprised (and excited) to find that others have wildly different ideas and opinions; and</li><li>They get the chance to blurt out any burning thoughts that would otherwise have to wait until the ‘right’ time in the discussion.</li></ol><p>In my course, students get the first 10 minutes of class to gabble about whatever they want — usually telling stories about that week’s game, and the horrible way their character died, or the time they just <em>barely</em> beat another player. Since the students come in with the shared experiences of Read-Watch-Play, they have an advantage that other formal environments often don’t offer.</p><p>For example, the first day of the PME-NA Working Group is more difficult to design for: anyone attending the conference can wander in, with more or less knowledge about mathematical play (although it’s safe to assume that everyone there knows and enjoys a variety of mathematics, so that’s a design leg up). Consequently, the attendees are often learning your provocative argument at the same time that they are learning what type of space your Working Group is. Is it all about lecturing and slides, like most academic contexts, or really discussion-based? Are their disagreements welcomed, or uncomfortably ignored? (Or worse, actively pooh-pooh’d!) Are they expected to ‘consume’ knowledge, or actively invited to co-create the learning community alongside the formal facilitators?</p><figure><img alt="three women animatedly chatting together" src="https://cdn-images-1.medium.com/max/1024/0*2Z0ubNNc4-WAypnc" /><figcaption>Photo by <a href="https://unsplash.com/@gradikaa_?utm_source=medium&amp;utm_medium=referral">Gradikaa Aggi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In these contexts, the provocative argument must be followed immediately by time for people to learn that the goal <em>is</em> to have everyone good-naturedly argue, no matter how much they know or don’t know about the topic at hand. You can either go the discussion route — although it’ll take longer than the 10 minutes I usually allot in class, so budget 20–30 minutes — or go straight into the next step so that folks can get an activity under their belt to keep their later discussions grounded in a shared experience.</p><h3>Fourth, extend the provocative argument with an activity.</h3><p>This can be a small group discussion that focuses on particular questions around the provocative argument — at PME-NA, the participants could be broken up into content area interests (early childhood math, linear functions, undergraduate calculus, what-have-you), and asked to think about how to implement one of the definitions of mathematical play into those learning contexts.</p><figure><img alt="a goose who looks in the midst of loudly squawking" src="https://cdn-images-1.medium.com/max/1024/0*sAl8C1X1V46zVPHH" /><figcaption>Photo by <a href="https://unsplash.com/@amit_8?utm_source=medium&amp;utm_medium=referral">Amit Talwar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This could also be a physical or digital game experience. In my course one year, I had the students read about The Untitled Goose Game, then play a <a href="https://medium.com/hcil-at-umd/the-goose-re-game-973fedcfe6e2">multiplayer analog version</a> together in class, followed by a discussion about the mechanics — the similarities and differences — between the two versions. I have also had students demo games in my course (such as <a href="https://en.wikipedia.org/wiki/Mario_Kart"><em>Mario Kart</em></a>) while other students looked on, and had a vibrant discussion afterwards about the indicators of learning, failing, and feedback in the game and between the competing players. I have also seen students play summary videos about games that have delightfully unusual design approaches that radically challenges what we had discussed previously (e.g., <a href="https://www.supergiantgames.com/games/hades/">Hades</a>, where the player’s death is only sorta-kinda punishment instead of solely an indicator of failure); or play a video of themselves learning a new game and doing a live commentary over the video about their learning.</p><p>Frankly, the sky is the limit here — new and old games, design activities, scavenger hunts, discussions about (figurative) giants in the field of focus, debates about big conflicts in the field, and so on. But remember that you are aiming for loud, gleeful learning — so bring in some silliness! Funny hats, self-deprecating humor, videos of your own huge failures in math, games, or whatever your topic is, and a very light guiding touch — aim only for questions that amplify and extend your participants’ ideas rather than restrict them. Remember, you don’t have a learning goal — just an a provocative argument space!</p><h3>Fifth, discussing and concluding.</h3><p>If there were small groups, then bring them back together and have them share with each other. If there were demos and videos, then discuss how everyone saw different things and made different connections between what they saw and the overall topic. Whatever you do, make sure you have sufficient time for folks to share all of their ideas, discuss different angles on the provocative argument, and figure out how today’s topic builds upon their previous knowledge from the class or the field. Two quick tips to help you guide — instead of dominate — the discussion:</p><figure><img alt="A small child with wide eyes covering their mouth!" src="https://cdn-images-1.medium.com/max/1024/0*wZ4h3tPl_eMdxEqW" /><figcaption>Photo by <a href="https://unsplash.com/@ilumire?utm_source=medium&amp;utm_medium=referral">Jelleke Vanooteghem</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>First,</strong> it is often easier to talk than to facilitate — fight against the urge to say something substantive after each comment from a participant, and let them respond directly to each other’s ideas. I use a lot of noises and physical gestures to facilitate and encourage, like “Ooooooh” when someone asks an interesting question, or an inviting gesture towards someone who looks like they want to respond but are waiting to see if you want to respond first. Sometimes, though, you’ll need to use tip #2, <em>wait time</em>, to foster a good discussion environment.</p><figure><img alt="A pedestrian “wait” light" src="https://cdn-images-1.medium.com/max/1024/0*0_H4_Afrm1L0BZjp" /><figcaption>Photo by <a href="https://unsplash.com/@kaip?utm_source=medium&amp;utm_medium=referral">Kai Pilger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Wait time</strong> is an important idea for facilitating, whether classes, working groups, or even committee meetings! At the front of the room, you’ll feel awkward when you ask a question and no-one answers right away — don’t let it make you keep talking! Instead, try to give a solid 30 seconds before you say anything else — people will desperately want that uncomfortable silence to end, and may break it for you, and/or the person who likes to think things through before speaking will actually have the space to contribute. So embrace the awkward!</p><p>Okay, back to the concluding discussion. Say that I’m wrapping up class by having my students discuss their experience of flow playing <em>Flower</em>. There is always someone who just can’t handle the fundamental different-ness of the game, and this invariably emerges at some point during class when that person shares their crankiness and explains how they tried their usual min/max approach but the sluggish controllers made it impossible, argh argh argh! And other students chime in, saying “Well, yeah, the controllers were a little difficult, but — ” and then they share with their more flow-like experiences, and what supported that feeling (the bell-like tones with every new blossoming flower, the susurration that pushes you back when you haven’t finished a level yet, the beautiful greening as you revitalize each landscape). And we discuss the personal uniqueness of the flow experience — how some people can find flow in <em>Flower</em>, while others just cannot. But the latter folks may find their flow in notoriously difficult games with precise controllers and useful min/maxing, like the <a href="https://en.wikipedia.org/wiki/Souls_(series)">Dark Souls series</a>.</p><p>So then a natural next step is wondering how those games are different — which leads students right back to the role of feedback and failure in flow (the provocative argument), as <em>Flower</em> and a <em>Dark Souls</em> game manifests failure and feedback in very different ways. And, as the students have been thinking about failure and feedback for a few weeks already, their discussion usually brings them right to this topic! Particularly as games from the <em>Dark Souls</em> series require failure to learn — how to fight, how to beat a particular boss, how to train your fingers to do certain really difficult combos — while a game like <em>Flower</em> has such <a href="https://medium.com/hcil-at-umd/designing-feedback-failure-in-videogames-55b99d5b1ad1">tiny failures</a> that they are barely experienced. And those tiny failures can be directly attributed to the sluggish controls — so the player doesn’t <em>feel</em> like they’ve failed — while at the same time, those sluggish controls are <em>fundamentally preventing</em> any player that comes in with a min/max attitude from actually engaging in the game that way! In other words, the controls being sluggish fit perfectly with the designed game experience of flow (and the narrative because the player is being a gust of wind picking up flower petals, and I’m pretty sure that gusts of wind, shouldn’t be able to corner very precisely!).</p><blockquote>An important note for doing this in a formal classroom setting: at some point, a student will ask a hard question, and everyone will swivel around to look at you for the answer. A good response to that is “Why are you all looking at me? Somebody has to have an opinion about this!”</blockquote><p>Build directly upon that conclusion by waiting until someone asks a question or makes a point that relates directly to next week’s theme — then say, “That is an awesome and difficult question, but we don’t have enough time! Let’s try to make sure we bring that back up in the next class!” In other words, you want a cliffhanger — so they walk out wanting the answer (and may try to puzzle it out themselves). The bonus is that they will be grateful when the next week’s Read-Watch-Play starts helping them answer the question!</p><p><em>This is dedicated to all my future students who will be worried about how to facilitate class, and to all my future colleagues who are planning to facilitate a working group. I hope this helps as you design, and lessens your worries!</em></p><p><em>Many thanks to the brilliant Dr. Susannah Paletz and my Fall 2021 </em>Games as Emergent Experiences<em> students for their support and insights.</em></p><p><em>This work is licensed under a </em><a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"><em>CC BY-NC-SA 4.0 license</em></a><em>. Attribution must include a link to this work.</em></p><h3>Footnote 1:</h3><p>Match-3 games like <em>Fishdom </em>require a content warning, as they share many design principles with casinos (e.g., casinos avoid windows and clocks, because they can both indicate the passage of time and remind the gambler that they have to go to work or bed; Match-3 games tend to obscure the digital clock on whatever screen you’re using, for the same reason). I always say: “If you or your family has a history of gambling addiction, DO NOT play this game — I can give you an alternative game toot-sweet!” My back-up is Threes, and I give them $6 so they aren’t penalized financially for being careful and smart.</p><h3>Footnote 2: some suggestions for setting the provocative environment.</h3><p>Remember that <a href="https://medium.com/hcil-at-umd/design-is-a-contract-2fd7dc07dcc5">design is a contract</a> between you and your participants. You promise to give them something interesting and achievable with your intervention, and they promise to do their darnedest to learn without asking you for the ‘right answer.’ A good rule of thumb here is to set a provocative argument that doesn’t <em>have</em> a ‘right answer’ — that makes the contract easier (and more fun) for both you and your participants! Some of the suggestions below also include the next step in this process (extending the provocative environment with an activity), while others don’t.</p><p>Share some in-process data that you’re analyzing and pointing out a big issue you’re having (e.g., why am I seeing mathematical play here, but can’t explain what the math content actually is?).</p><p>Share something you believe to be true but can’t figure out <em>why</em> you believe it to be true (e.g., I believe that mathematical play is the same as mathematical learning).</p><p>Give people three different representations of the same mathematical phenomenon, some pencils and graph paper, and some <a href="https://www.researchgate.net/publication/264002290_Using_Licorice_to_Reinvent_Trigonometric_Functions">licorice</a>, and ask them to figure out how to connect all the representations using only the given tools.</p><p>Emphasize the importance of the human side of things — our experiences, our thoughts, our hypotheses, the patterns we see in the world. Each human perceives and experiences the world in a different fashion, so focusing on our human-ness infuses even the most staid of topics with exciting different perspectives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86f603f27497" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hcil-at-umd/loud-gleeful-learning-86f603f27497">Loud Gleeful Learning</a> was originally published in <a href="https://medium.com/hcil-at-umd">Sparks of Innovation: Stories from the HCIL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Goose [Re]Game]]></title>
            <link>https://medium.com/hcil-at-umd/the-goose-re-game-973fedcfe6e2?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/973fedcfe6e2</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[untitled-goose-game]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Mon, 04 Oct 2021 19:44:49 GMT</pubDate>
            <atom:updated>2021-10-17T11:57:26.844Z</atom:updated>
            <content:encoded><![CDATA[<p>HCIL faculty Caro Williams-Pierce shares how she re-designed the delightfully absurd game in analog form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TZVEBwSmTgujVetk" /><figcaption>Photo by <a href="https://unsplash.com/@amit_8?utm_source=medium&amp;utm_medium=referral">Amit Talwar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I rebuilt the brilliant <a href="https://goose.game/">Untitled Goose Game</a> into an analog multiplayer game for the students in my Games as Emergent Experiences class. One glorious day, they ran around, stole things, and squawked at each other, and my two design goals were achieved: my students all got a sense of the delightful absurdity of the original game, <em>and</em> I laughed really hard. So yeah, if you have nine people, two hula hoops, and a need for giggling, give this version a shot!</p><p><strong>DESIGN GOAL: </strong>to adapt the Untitled Goose Game into a multiplayer analog game that kept some of the quirky eccentricities of the original game, and caused the same spontaneous belly-laughing.</p><p><strong>PEOPLE:</strong> you need nine people to play, divided randomly into three groups: Team Boom, Team Sling, and Non-Player Characters (NPCs).</p><p><strong>MATERIALS:</strong> Most materials can be modified based upon what you’ve got on hand — except the two hula hoops! Those are required.</p><p>You will also need two pairs of matching items and one unique item. For the pairs, we used two beach balls and two textbooks, I believe, and the unique item might have been a scarf. The items can really be anything, as long as a person can carry it somehow without using their hands (because their hands are holding hula hoops, naturally!).</p><p>Lastly, you’ll need the materials to place down some markers to make the ‘game board.’ You could use cardboard boxes, masking tape on the floor, chalk outlines on the grass, or anything else you have on hand.</p><p><strong>SPACE:</strong> you need an open space, inside or outside, that’s big enough to have nine people wandering around without constantly bumping into each other. Also make sure that it’s okay to be loud — don’t try this game in a quiet study space!</p><p>Use your materials to set up the game board, marking nests and putting down the five items in no particular order:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*4X5bhqSkIh-WojakXFkRKw.jpeg" /></figure><p>Actually tracing out the triangle is optional, as the NPCs will enact that shape according to their ‘programming’ — so yeah, up to you!</p><p><strong>WIN STATES:</strong></p><p>Team Boom or Team Sling can win by getting one of each type of item in their nest. NPCs have no win state — which makes sense, because they’re up against geese, and we all know there’s no winning against those sneaky, tricky, squawky little punks!</p><p><strong>GAMEPLAY:</strong></p><p>First, <strong><em>NPCs</em></strong>: each of the three NPCs gets a card with their actions and interactions listed in detail. I arbitrarily named my NPCs after colors, because why not? NPC Blue received this card:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hp1mBGwV_6jyUN0aoBAo_g.jpeg" /><figcaption>NPC Blue (full card)</figcaption></figure><p>Blue walks back and forth across the top of the triangle, and if they come across a place where an item should be, they execute a ‘searching path’ to the bottom right of the triangle, then to the nests. If the item is in the nest, they take it back to its place.</p><p>If they are meandering or searching, and they run into another NPC, they shake hands and mumble to each other. If they run into a Goose, they grumble and hrmph — if that Goose has an item, they start following them around, muttering <em>sotto voce</em>.</p><p>And if a Goose honks at them, the NPC jumps, yelps, and drops any item they happen to be carrying. Naturally.</p><p>Purple and Green have the same interactions, but their walking and searching paths are different:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-gxY2ERSbEXYAxQ6rAemg.jpeg" /><figcaption>NPC Purple and NPC Green</figcaption></figure><p>The goal with the NPC design was to have each just trying to go about their normal day, just as in the original game. (Poor NPCs — whether digital or analog, they are doomed to be constantly interrupted by the dratted geese!)</p><p>Now, <strong><em>Team Boom</em> </strong>and<strong> <em>Team Sling</em></strong>:</p><p>Each team gets a team card that explains their goal (win state) — as each team has the same win state, member roles, actions, and interactions, I’ll just use Team Sling cards to illustrate below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5bvtNshQueVZMPSk4MXHwQ.jpeg" /></figure><p>The <em>Welcome to Team Sling!</em> card describes the overall goal. Then each member gets one of three cards that determines their role as Sling Goose, Sling Squawk, or Sling Pick. As a multiplayer game, I wanted the team members to have to collaborate to <em>be</em> the Goose together. So I broke down the Goose into those three parts: Sling Goose walks around trying to steal items, but they are told when to steal an item by Sling Pick, and when to scare an NPC by Sling Squawk.</p><p>In other words, they are the executor of those commands, but the only part they actually control is where to walk — they have to wait for an order from their teammates to pick up an item or squawk.</p><p>(This is why the game is so amazingly fun — errr, loud — Sling Pick and Sling Squawk have to stay near the nest, so they’re hollering SLING PICK SLING SQUAWK SLING SQUAWK loudly across the game board to their Goose.)</p><p>The details of each role is listed on the card below — you’ll notice that this is where Sling Goose learns that they have to wear a hula hoop the whole time! I built the hula hoop in as a way to prevent players from using their hands to hold an item — that would be inappropriately un-goose-like behavior!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NYOjkQqfqGSbP4pWByAEuw.jpeg" /></figure><p>There are a variety of ways to modify this. For example, I had a unique item, which meant that the two teams were always squabbling over it! Using another pair would have changed those dynamics quite a bit. And some NPCs walk by item spaces more often than others, which means they tend up executing more search paths.</p><p>Sadly, I’ve only played this once in class before the pandemic shut us down, but the result was delightful! My students were loud and silly, yelling and honking and tucking beach balls under their chin. Neither Boom nor Sling managed to get the three different items in their nest at the same time, so I suppose that there <em>is </em>an NPC win state: don’t let the Goose win!</p><p>That’s my Goose [Re]Game story! At the time, I had to be careful about which games I assigned to students each week — my little Game Lab was just getting set up, so each student had to buy each individual game <em>and</em> have a way to play it. Needless to say, I aimed for free or cheap multi-platform games! And of course, the <em>very day</em> that I opened up the Game Lab was the same day that our campus was shut down for the following year and a half. (If anyone wants to donate a PS5 to the Game Lab, I’d be eternally grateful! The PS4 looks way less exciting and impressive now than it did when I bought it…)</p><p>Lastly, I want to share this image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouVPGbuNk__AXz982OoDkg.jpeg" /><figcaption>The <a href="https://yxlab.ischool.umd.edu/">Youth eXperience</a> dry erase board from before, during, and after the pandemic.</figcaption></figure><p>This board was what greeted myself and my <a href="https://yxlab.ischool.umd.edu/">Youth eXperience</a> lab colleagues on our rare visits back to campus throughout the pandemic. Every time, it reminded me how much I missed in-person classes — which was sad, yes, but also reminded me what we were aiming for in staying safe and alive. Now, we’re back (fully masked and vaxxed), and I’m deeply grateful. Yes, I have to learn how to identify students just from their forehead; but also yes, learning together is way better than learning apart.</p><p><em>This work is licensed under a </em><a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"><em>CC BY-NC-SA 4.0 license</em></a><em>. Attribution must include a link to this work.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=973fedcfe6e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hcil-at-umd/the-goose-re-game-973fedcfe6e2">The Goose [Re]Game</a> was originally published in <a href="https://medium.com/hcil-at-umd">Sparks of Innovation: Stories from the HCIL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HCIL 2020–2021 News Roundup]]></title>
            <link>https://medium.com/hcil-at-umd/hcil-2020-2021-news-roundup-be810ecfb21f?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/be810ecfb21f</guid>
            <category><![CDATA[hcil]]></category>
            <category><![CDATA[hcil-symposium-2021]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Mon, 24 May 2021 20:23:59 GMT</pubDate>
            <atom:updated>2021-05-24T20:23:59.930Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Our brilliant sparkling lights in a Stygian year.</em></h4><figure><img alt="A picture of a Zoom meeting with numerous smiling members of the HCIL." src="https://cdn-images-1.medium.com/max/1024/1*FnqxQBCX4B1H3lNO7XPD5g.png" /><figcaption>HCIL online!</figcaption></figure><p>I’m sitting outside on my porch, with the sun shining brightly and the cicadas timidly starting to buzz, and thinking back over a long and often sorrowful year. Writing this news roundup made me think about all the amazing (and often invisible) work so many people in the HCIL put in this year to change research methods and lab meetings, move classes fully online, and increase the amount of emotional support provided to their students, <a href="https://www.youtube.com/channel/UCXLn79EZgmsKIGPGVLrwXXg">move the weekly HCIL Brown Bags fully online</a>, and move the <a href="https://hcil.umd.edu/2021-symposium/">annual Symposium fully online</a> — all this while simultaneously taking care of their partners, children, elders, and newer colleagues (like myself). Somehow, amidst all this, my colleagues still managed to gather accolades at an astounding rate! And on the really hard days, it was always so heartening to hear the good news — whether that was a best paper nomination, a grant, or a new puppy — to remind us that we are all here together, as a community, holding the torch up high.</p><p>Here follows the HCIL 2020–2021 news roundup!</p><h3>Summer 2020</h3><p>Leilani Battle was recognized as a <a href="https://www.technologyreview.com/innovator/leilani-battle/">Visionary in MIT Technology Review’s 35 under 35</a> for her incredible (need I say, visionary?) work with enormous arrays of data. Congratulations, Leilani!</p><p>August was a big month for Michelle Mazurek and her students/colleagues:</p><ul><li>Michelle, her students Daniel Votipka and Kelsey Fulton, and other colleagues received the Distinguished Paper Award from USENIX Security for their paper “<a href="https://www.usenix.org/conference/usenixsecurity20/presentation/votipka-understanding">Understanding security mistakes developers make: Qualitative analysis from Build It, Break It, Fix It</a>”</li><li>Michelle, her student Noel Warford, iSchool alumna Elissa Redmiles, and other colleagues received the Distinguished Paper Award from USENIX Security for their paper “<a href="https://www.usenix.org/conference/usenixsecurity20/presentation/redmiles">A comprehensive quality evaluation of security and privacy advice on the web</a>”</li><li><a href="https://hcil.umd.edu/posts/daniel-votipka-mc2-and-hcil-is-a-recipient-of-the-2020-john-karat-usable-privacy-and-security-student-research-award/">Daniel Votipka received</a> the 2020 John Karat Usable Privacy and Security Student Research Award for his “excellence in research and dedication to mentorship and community service.”</li></ul><h3>Fall 2020</h3><p>Jonathan Lazar received the Award for Outstanding Contributions to Computing and Accessibility from ACM SIGACCESS, in “recognition of his life-long dedication to the goal of accessible technologies and digital content through his research, education, advocacy, policy and legal work.”</p><p>Catherine Plaisant received the Visualization Career Award from the IEEE Visualization and Graphics Technical Committee in recognition of her significant research contributions to this community. See Catherine accept this prestigious award <a href="https://hcil.umd.edu/posts/catherine-plaisant-honored-with-ieee-vgtc-visualization-career-award/">here</a>.</p><p>Emma Dixon and Amanda Lazar’s paper, “The Role of Sensory Changes in Everyday Technology Use by People with Mild to Moderate Dementia,” received a Best Paper nomination from ACM ASSETS.</p><p>Michelle Mazurek received the DARPA Young Faculty Award for her proposal “Generalizing to Understudied Populations Through the Lens of Key Privacy Challenges.” <a href="https://www.darpa.mil/work-with-us/for-universities/young-faculty-award">This award</a> targets “rising stars” — congratulations, Michelle!</p><p>Yuhan Luo was awarded the Dr. Joan Giesecke Health Informatics Fellowship from the iSchool — congratulations, Yuhan!</p><h3>Spring 2021</h3><p>Amanda Lazar received the National Science Foundation’s most prestigious early career award for her CAREER grant “<a href="https://www.nsf.gov/awardsearch/showAward?AWD_ID=2045679&amp;HistoricalAwards=false">Advancing Remote Collaboration: Inclusive Design for People with Dementia</a>.”</p><p>Jonathan Lazar was named to the <a href="https://sigchi.org/awards/sigchi-award-recipients/2021-sigchi-awards/">SIGCHI Academy</a>, in recognition of his influence on and leadership within the field of HCI.</p><p>Young-Ho Kim, Eun Kyoung Choe and colleagues received an Honorable Mention Award for their SIGCHI paper, “<a href="https://dl.acm.org/doi/fullHtml/10.1145/3411764.3445421">Data@Hand: Fostering Visual Exploration of Personal Data on Smartphones Leveraging Speech and Touch Interaction</a>” — congratulations!</p><p>Leilani Battle received the VMware Early Career Faculty Grant, which recognizes “the next generation of exceptional faculty members” — Leilani, we will miss you as your journey takes you away from UMD, but we’re incredibly happy that you are receiving this well deserved recognition!</p><h3>Research Sponsors</h3><p>Researchers in the HCIL were funded this year by a wide variety of sponsors, including:</p><ul><li>Adobe</li><li>Defense Advanced Research Projects Agency (DARPA)</li><li>Department of Defense</li><li>Department of Education</li><li>Federal Highway Administration (FHA)</li><li>Google</li><li>Institut National de Recherche en Informatique et en Automatique (INRIA)</li><li>Institute for Museum and Library Services (IMLS)</li><li>National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR)</li><li>National Institutes of Health — National Institute of Biomedical Imaging and Bioengineering (NIBIB)</li><li>National Science Foundation (NSF)</li><li>Office of Naval Research</li><li>Social Science Research Council (SSRC)</li><li>Spencer Foundation</li><li>Office of Naval Research</li></ul><p>We could not have accomplished all of this without your support — thank you thank you thank you!</p><p><em>HCIL’s 2020–2021 was rough, like everyone’s, but we are thrilled to be celebrating our amazing people who persevered through, kept racking up the accomplishments, and supported each other. We also want to take a moment to celebrate those who did not get external recognition for their work because they were too busy focusing on family, students, and other unsung heroics: we see you, and THANK YOU.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be810ecfb21f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hcil-at-umd/hcil-2020-2021-news-roundup-be810ecfb21f">HCIL 2020–2021 News Roundup</a> was originally published in <a href="https://medium.com/hcil-at-umd">Sparks of Innovation: Stories from the HCIL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trust and Failure in Technology]]></title>
            <link>https://medium.com/hcil-at-umd/trust-and-failure-in-technology-d6defb87fb88?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6defb87fb88</guid>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[trust]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Thu, 08 Apr 2021 19:52:21 GMT</pubDate>
            <atom:updated>2021-04-09T14:47:10.059Z</atom:updated>
            <content:encoded><![CDATA[<p><em>One way we’re failing to establish trust in technology.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrfBbU7aMzVT5dczCrcbOA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mmayyer?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">marcos mayer</a> on <a href="https://unsplash.com/s/photos/trust?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>.</figcaption></figure><p>In my day job, I design videogames that support mathematics learning. Despite my training in more traditional classroom-based mathematics teaching and learning, I chose videogames as a platform specifically because people playing a good game have <em>trust</em> in the game. When you experience failure during gameplay, you look automatically for <a href="https://medium.com/hcil-at-umd/designing-feedback-failure-in-videogames-55b99d5b1ad1">feedback paired with that failure </a>— because a good game won’t just arbitrarily fail you. There’s a <em>reason</em> for that failure, and the game will tell you what the reason is.</p><p>I believe that trust is a key component to all learning experiences, in classrooms, libraries, maker spaces, videogames, etc. We have to be able to trust our products, our colleagues, our professors, our friends, in order to learn from and with them. And trust requires a <em>lack of arbitrary punishment</em> — failure needs to come paired with useful feedback for understanding and correcting that failure. This trust — and the failure paired with feedback — is crucial for designing anything, whether learning environments, videogames, digital products, or any other part of the human experience.</p><p>As <a href="https://medium.com/hcil-at-umd/design-is-a-contract-2fd7dc07dcc5">I wrote about the Design Contract</a>, riffing off the brilliant Brousseau and extending from learning to more general design:</p><blockquote>With the Design Contract, the designer promises that the product is usable, reliable, and trustworthy…and that the product can be used with only whatever prior knowledge the user brings. That prior knowledge will be challenged with new problems and novel contexts, but the user has everything they need within themselves and within the product to accomplish their goals, whether playful or productive (or both).</blockquote><p>In other words, when a user begins using a product (or a student attends a class, or a gamer logs into Battle.net), that user knows that they can use/learn/play successfully. They know that if they do something wrong, they will be notified about their failure, and that failure will be paired directly with feedback, so they understand <em>why</em> and <em>how</em> the failure occurred (and how to avoid it in the future). This failure and feedback, in a well designed product or context, will never be arbitrary — it will always be trustworthy.</p><p>In fact, safety from arbitrary nonsense is just a key component of living a good, contented, reasonable life. When we click a button, we want the same thing to happen every time we click that button— the TV turns on, the email is deleted, your avatar jumps, the microwave adds 30 seconds to the timer. When we come to class every week, we want our professor to give us the same credit for attendance that the other students who come each week get; when we register to vote, we want the same access to the ballot box that a voter in a different neighborhood, a different county, a different state gets; when we live as our best selves, we want the same access to safe appropriate bathrooms and good healthcare that other genders get. We just want to trust that we, as people, learners, voters, and players, get a fair shot at this game called life — I could wax eternally philosophic about this, but I’m only tackling a reasonably sized topic today: trust in technology.</p><p>When the pandemic dropped, our lives became more reliant on technology than ever before. As a professor, in order to teach a reasonably good class in this new world, I have to be well versed in a long stack of layered tech — here’s just a couple off the top of my head:</p><blockquote>the suite of Google products (our institutional providers of email, cloud storage, etc.)</blockquote><blockquote>Canvas (our learning management system)</blockquote><blockquote>Zoom for our synchronous class time</blockquote><blockquote>Panopto for the storage of our Zoom recordings of our classes for students attending asynchronously</blockquote><blockquote>Slack or Discord for asynchronous communication with students</blockquote><blockquote>single sign-on through the university to get verified access to all those products above</blockquote><blockquote>Duo for multi-factor authentication to verify my single sign-on to get verified access to all those products above</blockquote><p>Now, these may not seem like too much — and frankly, I’m good with each of them individually — but the real problems emerge when we have to layer them upon each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nxfgfpZ6FuE_1Hct" /><figcaption>Photo by <a href="https://unsplash.com/@glencarrie?utm_source=medium&amp;utm_medium=referral">Glen Carrie</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Here’s a tiny little example: our single sign-on verification expires every day at different times — so I may think I’m logged into my official Zoom, and according to my desktop app I am, but when I arrive in a Zoom meeting I get shoved into a waiting room. This might be because my single sign-on expired — although it’s also possible that I was somehow logged out of my Zoom account, OR I’m accessing the meeting through a personal account by mistake, OR my single sign-on system just isn’t telling Zoom properly that I’m good to go.</p><p>(Or I just need to update my operating system. Or turn my computer off and then back on again. Or run outside screaming and go back to <a href="https://medium.com/hcil-at-umd/what-time-is-it-a441eaeff51a">my childhood life of peace, quiet, and no electricity</a>.)</p><p>In other words, there is distinct failure occurring here — I wanted to trust that if I clicked the right button to join the Zoom meeting, I would, but it arbitrarily failed. And there’s just enough feedback to <em>indicate</em> this arbitrary failure — getting trapped in the waiting room, while the host worries that if they let me in they’ll be subjected to pathetic zoombomb wankers who are just pretending to be me — but no feedback as to <em>why</em> the failure happened.</p><p>Was it Zoom? Or my university single sign-on? Or user error? Or lack of communication between Zoom and the single sign-on? Or maybe my Verizon internet hiccuped randomly?</p><p>(Or maybe it was sunspots?)</p><p>This is a single tiny example, but multiply that by all the products that sometimes are accurately verified and sometimes aren’t, and multiply that by the 120 students in one of my classes all struggling with this every week, and multiply that by weird updates that happen in strange places at strange times. My iPhone — which I use to authenticate via Duo — recently updated the iOS, and now Duo only sometimes recognizes my authentication. Is that the iOS update? A Duo issue? User error? Problems between the phone and Duo? The phone network and Duo? Should I turn my phone off and then on again?</p><p>(Should I turn the sun off and then back on again? Maybe that would fix the sunspots?)</p><p>As I’ve spent the year thinking about our layers of technology, I’ve realized that failure at one layer in our technology use may be accompanied by feedback, but that feedback just isn’t reaching us, because we’re hanging out at one layer (e.g., the Zoom waiting room), and the failure and feedback is happening at another layer (the single sign-on that expired in some random secret database or whatever), and since the two don’t talk to each other in a well designed fashion with the actual user in mind, I never get the feedback that goes with the failure I’m experiencing. So the failure is absolutely arbitrary to me — and I, like most humans, do not like or trust arbitrary experiences:</p><p>If I hit the +30 seconds button on my microwave, and sometimes it works but sometimes it adds 1 second or 30 minutes instead — I’m getting a new microwave.</p><p>If I go to class every week and yet my attendance is marked as only coming once a month, I’m going to be scared and angry.</p><p>If I hit a button to respond to an email and it deletes the email instead, I’m going to get worried about what emails I may have accidentally deleted, and will have to go dig through my trashed emails to make sure there isn’t something super important in there — and I’m really going to hope that my “respond to this email” button hasn’t accidentally been programmed to sometimes execute permanent deletion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vPao3QmN2F_S2DO-" /><figcaption>Photo by <a href="https://unsplash.com/@mikael_seegen?utm_source=medium&amp;utm_medium=referral">Mikael Seegen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In fact, I’m going to hope that one of the layers of my tech life didn’t get programmed by a cranky underpaid worker so that when I click “respond to this email” it’s actually auto-sending a nasty email response, muting the original sender, and then permanently deleting the whole conversation. Because that’d be pretty easy to do — the only reason I don’t <em>think</em> that’s happening, is because I have trust in my technology. And I trust that a button that says “respond to this email” actually <em>means</em> what it says. But the more layers that get involved, and the more failure I experience that comes with no feedback, the more I feel that clicking a button will have an arbitrary and undesirable response.</p><p>I think of our commitment to these multiple layers of technologies as being a factorial problem. If I use 10 different pieces of technology that connect to each other in some way, then it’s really like using 10! pieces of technology, because we have to account for all the updates, the edges between the technology, the platforms of the various technologies, the fact that my technology wants to talk to your technology, the help pages online that are outdated (or future-dated for a version that hasn’t been rolled out to me yet), the fact that reliable and affordable broadband isn’t considered a necessary service for modern life in my country yet, and that there is very little protection from companies who sell us hardware or software or services that aren’t actually working properly. So buying a new piece of software is not increasing your technology count by 1, but rather increasing from 10! to 11! which is HUGE.</p><p>So maybe hold off on that new piece of tech? At least until our technology layers start talking to each other (and us) better — because every new piece adds to our experience of arbitrary, frustrating, unhappy, no-feedback failure.</p><p><em>As I was writing this, the tone changed — it started all playful, because I have these lovely hilarious examples of arbitrary failure, with pretty pictures and everything! Then I ended up having time to write only because an expensive virtual conference I was attending combined three things I hate: 1) an idiosyncratic virtual conference platform that was locked down to make sure that only people who had paid could attend, which resulted in people who DID pay having issues with access; 2) a poor and slow-to-respond tech support system by the platform developers that starts with ‘Did you turn it off and turn it on again?’ and takes hours to escalate to someone who can actually help (I think — we haven’t actually made it to someone who can actually help); and 3) a complete inability to log in, even with official registration, multiple computers/browsers, and a tech support professional who calls me ‘wife’ and in return for that honor, is responsible for fixing my tech! So I wrote most of this in the six hours it took to figure out a secret backdoor to the conference, thinking crankily about the fact that I was missing my team’s first talk, and might have to notify the other 6 sessions I’m involved in that I can’t attend the premier conference in my field. So yeah, it definitely ended not playful — because arbitrary failure without support make life really forking frustrating!</em></p><p>The next piece about tech and trust I write <em>will</em> be goofier and funnier, with all those aforementioned pictures of arbitrary failure, I promise — unless the sunspots start acting up again.</p><p><em>This work is licensed under a CC BY-NC-SA 4.0 license. Attribution must include a link to this work.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6defb87fb88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hcil-at-umd/trust-and-failure-in-technology-d6defb87fb88">Trust and Failure in Technology</a> was originally published in <a href="https://medium.com/hcil-at-umd">Sparks of Innovation: Stories from the HCIL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design is a Contract]]></title>
            <link>https://medium.com/hcil-at-umd/design-is-a-contract-2fd7dc07dcc5?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fd7dc07dcc5</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Mon, 11 Jan 2021 19:11:01 GMT</pubDate>
            <atom:updated>2021-04-08T19:48:52.459Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Whether you design physical objects, digital experiences, or classroom curricula, your design is a contract with the users.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5TTjtdodtLWjlAwC" /><figcaption>Photo by <a href="https://unsplash.com/@adeolueletu?utm_source=medium&amp;utm_medium=referral">Adeolu Eletu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Well designed products of all stripes — videogames, classrooms, objects from the Internet of Things — all make a promise to the player/student/user: this product is <em>usable</em>, <em>reliable</em>, and <em>trustworthy</em>. However, there is not always a promise for ease of use — especially when, as with videogames and classrooms, <em>learning</em> is part of the designed experience. Instead, there’s a Design Contract between the designers and the users, that goes beyond usable, reliable, and trustworthy.</p><figure><img alt="A sign that says NO FIRES with a symbol of a fire struck through." src="https://cdn-images-1.medium.com/max/800/1*HYzQQTkwn59AzkINeM3WMg.jpeg" /><figcaption><a href="https://flic.kr/p/6F949r">Image courtesy of Chris Campbell</a></figcaption></figure><p>First, <strong><em>usable</em></strong> is a lesson learned by the U.S. videogame industry back in the 1980s — games were being shipped and sold that were fundamentally broken. So Nintendo developed the <a href="https://www.nintendolife.com/news/2019/02/talking_point_what_does_the_nintendo_seal_of_quality_mean_in_2019">Seal of Approval</a>, which promised that the game would actually start up and be playable — instead of the game version of a 404 message — and at least wouldn’t set your console on fire. (Which was, at the time, an unfortunately radical promise!) Because of this, Nintendo is still a major international player in the games business, unlike, you know, Atari.</p><p><strong><em>Reliable</em></strong> was also a part of the Seal of Approval: Nintendo devoted time, money, and expertise to advising game development companies. They wanted to accomplish more than just ‘playable’ — they wanted their games to reliably be enjoyable, as part of the promise they made to their players to be delivering a <em>game</em>. And since game design is as much art as science, they made their experts available to companies designing for the Nintendo platform. Part of the expert advising no doubt focused on a key but understated component of good games: the importance of designing for productive (and playful) learning.</p><p><em>Learning </em>is inextricably intertwined with<em> </em><strong><em>trustworthy</em></strong> in videogames. Although people often associate ‘learning’ with the extremely limited context of formal education, <a href="https://en.wikipedia.org/wiki/What_Video_Games_Have_to_Teach_Us_About_Learning_and_Literacy">learning is part-and-parcel</a> of how we become someone else within novel game contexts. How else can I — a portly middle-aged academic — become <a href="https://www.konami.com/games/eu/en/products/mgs4/">Old Snake</a>, <a href="https://www.playstation.com/en-us/games/littlebigplanet-2-ps3/">Sackgirl</a> (or <a href="https://press.etc.cmu.edu/index.php/product/well-played-vol-1-no-1/">both</a>), and a threadbare wizard gardening and fishing on a relaxed island?</p><figure><img alt="Image of an adorable game character with a wizard hat, standing on a dock by the water with coconut trees in the background." src="https://cdn-images-1.medium.com/max/1024/1*1J1fMeittpjCZ_N0EDCqzg.jpeg" /><figcaption><a href="https://www.animal-crossing.com/new-horizons/">Animal Crossing: New Horizons</a> image captured by author during gameplay.</figcaption></figure><p>These possibilities exist only because each of these games teach — and I learn — how to be those widely disparate characters. This teaching and learning primarily occurs through <a href="https://medium.com/hcil-at-umd/designing-feedback-failure-in-videogames-55b99d5b1ad1">failure paired with feedback</a>, and requires trust from the player that when they fail, the game will include feedback on <em>why</em> they failed. There is nothing quite like arbitrary failure to ruin a learning experience, whether that’s a teacher taking off points for something unexpected or a game just randomly killing you off. This is where the <strong><em>Design Contract</em></strong> comes into play (pun intended).</p><p>I adapted and extended the Design Contract from Brousseau’s <a href="https://www.springer.com/gp/book/9780792345268">didactical contract</a>. Brousseau is a French mathematics teacher and scholar who recognized the tendency of mathematics students to ask their teachers for an algorithm, and bemoaned the tendency of mathematics teachers to actually just give the algorithm. As a result, he developed the didactical contract, which essentially stated that teachers must design tasks in such a way that the student can learn using only their prior knowledge and the information included in the task. In turn, the student must use what they already know alongside the new information from the task, and the mathematical learning will emerge naturally from adapting what they already know to that new problem. In other words, as I wrote previously in my <a href="https://www.dropbox.com/s/gj7479e5m60180g/Williams-Pierce%20Dissertation%20FINAL.pdf?dl=0">dissertation</a> (pdf):</p><blockquote>The student knows that the task was designed to elicit some new form of knowledge, but “she must also know that this knowledge is entirely justified by the internal logic of the situation and that she can construct it without appealing to didactical reasoning [e.g., asking the teacher for the algorithm]” (Brousseau, 1997, p. 30).</blockquote><p>So the teacher and student here are promising to each play their own part in this contract: the teacher promises that the new problem is solvable, and the student promises to use the knowledge they already possess and dig deep into the problem in order to learn more.</p><p>With the broader Design Contract, the designer promises that the product is usable, reliable, and trustworthy— the very least of what we should expect from our products! — <em>and</em> that the product can be used with only whatever prior knowledge the user brings. That prior knowledge will be challenged with new problems and novel contexts, but the user has everything they need within themselves and within the product to accomplish their goals, whether playful or productive (or both). Slight modifications to the above quote gives us this:</p><blockquote>The player knows that the game was designed to elicit some new form of action or knowledge, but ‘she must also know that this action or knowledge is entirely justified by the internal logic of the game and that she can play it without appealing to resources outside of the game.’</blockquote><p>The designer, as one side of the Design Contract, doesn’t promise that playing the game, using the product, or learning in school will be <em>easy</em> — but only that playing, using, and learning will be <em>achievable. </em>The other side of the Design Contract — the player, user, or student — in turn must promise to honestly bring their prior knowledge and effort to that designed object. If the designer doesn’t follow through on their part of the Contract, there will be rage-quitting, frustration, and attempts to <em>just get the algorithm</em>. And if the user doesn’t follow through on <em>their </em>part of the Contract, they will make lesser known but prevalent versions of a user error: a lack of fun playing the game, blaming the product for their own inefficiencies, or trying to get a good grade while learning as little as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sDbL8BgFuqJHg9dFfECzrQ.png" /><figcaption>Learning how to play <a href="https://playhearthstone.com/en-us">Hearthstone</a> would have been much harder without my teenage experiences playing <a href="https://magic.wizards.com/en">Magic the Gathering</a>. Image captured by the author during gameplay, before she went on to kick Gutmook’s butt.</figcaption></figure><p><strong>In Conclusion</strong></p><p>As designers, we make a promise; as users, we also make a promise. The best games, products, or classes are the ones in which both sides of that promise adhere to the Design Contract: the designers develop an internally consistent experience that use failure and feedback to build upon the users’ prior knowledge; and the users bring a willingness to use and adapt that prior knowledge, alongside trust that the designers delivered on their part of the contract. Paying for a game, product, or class is but the first step — if we design it well, the players, users, or students may not have an <em>easy</em> time, but they will have a playful, productive, and learning-filled time.</p><p><em>This work is licensed under a </em><a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"><em>CC BY-NC-SA 4.0 license</em></a><em>. Attribution must include a link to this work.</em></p><p><strong>Further Resources:</strong></p><p>This article builds upon my previous piece about failure and feedback — so if you want more details about how failure paired with feedback is important, read it <a href="https://medium.com/hcil-at-umd/designing-feedback-failure-in-videogames-55b99d5b1ad1">here</a>.</p><p>My plenary at the 2020 <a href="https://hcil.umd.edu/hcil-overview/">Human-Computer Interaction Symposium</a> introduced the Design Contract — watch the video <a href="https://www.youtube.com/watch?v=YY3LpYCXtRw&amp;feature=youtu.be">here</a>. Particular thanks go to the folks who asked brilliant questions at the end, and made me think I should write more about this!</p><p>My primary research focus is on mathematical play in videogames. You can read some of my work on mathematical play in <a href="https://www.emerald.com/insight/content/doi/10.1108/ILS-03-2019-0027/full/html">digital media</a> or the <a href="https://www.frontiersin.org/articles/10.3389/feduc.2020.00147/full">importance of gesture</a> in mathematics games, and how mathematical play connects to <a href="https://www.aera.net/Publications/Online-Paper-Repository/AERA-Online-Paper-Repository">learning and design</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fd7dc07dcc5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hcil-at-umd/design-is-a-contract-2fd7dc07dcc5">Design is a Contract</a> was originally published in <a href="https://medium.com/hcil-at-umd">Sparks of Innovation: Stories from the HCIL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A flexible project-based assignment for your online Math Methods course]]></title>
            <link>https://carowp.medium.com/a-flexible-project-based-assignment-for-your-online-math-methods-course-2b0cbb70142e?source=rss-3b4a210372ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b0cbb70142e</guid>
            <category><![CDATA[mathematics-education]]></category>
            <category><![CDATA[undergraduate]]></category>
            <category><![CDATA[teacher-training]]></category>
            <category><![CDATA[online-teaching]]></category>
            <dc:creator><![CDATA[Caro Williams-Pierce]]></dc:creator>
            <pubDate>Tue, 15 Dec 2020 22:40:12 GMT</pubDate>
            <atom:updated>2020-12-16T15:30:42.187Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DyxhqJCr7Fc6aplf" /><figcaption>Photo by <a href="https://unsplash.com/@sctgrhm?utm_source=medium&amp;utm_medium=referral">Scott Graham</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Years before the pandemic hit, I found myself teaching fully online and asynchronously — that is, I was specifically mandated to <em>not</em> require students to be anywhere at a specific time, online or offline. While I was teaching at an institution that is renowned for its online education, I was new to it — so over the following four years, I built, revised, and revamped a Math Methods course. Little did I realize, I was preparing for modern times! But seriously, folks, here’s a flexible project-based assignment for your online Mathematics Methods course, whether you teach pre-service or in-service teachers, and regardless of the mathematical content you focus on.</p><p>This assignment is organized around a crucial big understanding that mathematics teachers need: there are many ways of learning and understanding mathematics, and different learners will solve those problems differently. This is a tricky big understanding — often, people are drawn to teaching mathematics because they loved the sense of reliability of mathematics they developed when <em>they</em> were students. So they can find it difficult to let that sense of reliability go when they encounter all the many different (powerful, legitimate) solution methods that emerge in the classroom. This assignment addresses that big understanding head on — even in a time when they can’t leave their homes!</p><p><strong><em>Introduction to give to your students:</em></strong></p><p>The goal of the Interview Project (the final project for this class) is for you to dig deeply into a math problem, trying to think like a wide variety of learners so that you can anticipate and understand their thinking. One of the wonderful things about math learning is that you can never capture every possible way a learner could solve a problem — but by digging deeply into the math problem, you can be more likely to understand and support different ways of learning the same content. The interview process is so that you can see how it feels to be super-prepared for facilitating math learning; and the write-up is so that you can share your detailed planning and interview results with others. If you run a blog, this paper is a wonderful piece to add to your online math teacher presence!</p><p>For the interview: find a single person of any grade or age. For example, if you don’t have a child of your own, interview a friend, partner, roommate, sibling, or parent. The sky’s the limit!</p><p>All organized around Harel’s (2008) article, which I short-hand as <em>conceptual paths</em> (<a href="https://math.ucsd.edu/~harel/pdf/DNRII.pdf">.pdf available here</a>).</p><p>For the following details, I’ve organized the Project by eight parts (well, technically, nine, but the first part is just reading Harel’s paper). I made this the final project in my class, and it is broken into eight parts, with each part taking a full week, and the final version due at the very end of the semester. Although, if you have your students just do this assignment, it could certainly fit in a couple weeks instead!</p><h3>Each Part gets this font</h3><blockquote>The details for the week follow in this font</blockquote><p>So you can skim and just look for specific fonts as needed. Okay, here we go!</p><h3>Part 0: read Harel’s paper, learn about conceptual paths</h3><blockquote>In the following image from the paper, Harel gives a math problem plus four actual categories of solutions given by students. Each solution has a different conceptual basis/path — that is, each solution illustrates a different type of thinking about the problem:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qfbVQxTDhf1A-yMJPtFgEw.jpeg" /><figcaption>Excerpt from Harel’s (2008) piece that I forefront for learning about conceptual paths.</figcaption></figure><blockquote><strong>The conceptual path for Solution 1</strong> goes something like this: find a common divisor for 20 and 30, that isn’t too big or too small, and divide the pool into that many pieces (5). Then imagine one pipe filling one part, and the other pipe filling another part — how long does each take to fill a part? Then, iterate each of those, keeping track of the hours and the full parts:</blockquote><blockquote><strong>Pipe 1:</strong></blockquote><blockquote>4 hours, 1 part</blockquote><blockquote>8 hours, 2 parts</blockquote><blockquote>12 hours, 3 parts</blockquote><blockquote>16 hours, 4 parts</blockquote><blockquote>20 hours, 5 parts</blockquote><blockquote><strong>Pipe 2:</strong></blockquote><blockquote>6 hours, 1 part</blockquote><blockquote>12 hours, 2 parts</blockquote><blockquote>18 hours, 3 parts</blockquote><blockquote>24 hours, 4 parts</blockquote><blockquote>30 hours, 5 parts</blockquote><blockquote>Is there the same hour amount where adding the parts of each pipe are equal to 5? Yes — at 12 hours, all 5 parts are full!</blockquote><blockquote><strong>The conceptual path for Solution 2 </strong>goes something like this: add the number of hours each pipe would take to fill the pool, and add them together.</blockquote><blockquote><strong>The conceptual path for Solution 3</strong> goes something like this: if it takes one pipe 30 hours to fill the pool, and another 20 hours to fill the pool, then with the two of them working together, it should only take 30 hours minus 20 hours, which equals 10 hours.</blockquote><blockquote><strong>The conceptual path for Solution 4</strong> goes something like this: the rate of one pipe is 1/20th of the pool in an hour, and the rate of the other is 1/30th of the pool in an hour. There must exist some number of hours (<em>x</em>) in which the rates of both pipes are equivalent to filling one pool — in other words: <em>x </em>* (1/20 + 1/30) = 1 (which is equivalent to the version given in Harel’s excerpt, with <em>x</em> multiplied across the fractions). Then solving for <em>x </em>will give me the number of hours needed to get to a single filled pool. <em>Note that this conceptual path is just a more sophisticated and abstracted version of the first solution’s conceptual path.</em></blockquote><blockquote>There are two important aspects to notice here: first, that some of these conceptual paths are incorrect; and second, that it is easy to imagine students engaging in all four of these possibilities. That is — all four conceptual paths are deeply authentic.</blockquote><h3>Part 1: Review Harel’s idea of conceptual paths, and pick a problem you will use in your interview</h3><blockquote><strong>Picking Problems.</strong> My classes run on a Read-Watch-Play format: reading an article or some chapters from Jo Boaler’s amazing books; watching a video of a mathematics educator or other brilliant speaker; and ‘playing’ a math problem. A lot of the problems are ones I’ve been collecting — as math nerds do — or found on various websites, or collected/provided by the students themselves. Having students choose their own math problem means they can choose one that’s appropriate for them — the content they teach, or plan to teach, or adapted to whomever in their household they will interview.</blockquote><h3>Part 2: Post at least four different conceptual paths (at least one incorrect) with an explanation of each. You will also be assigned a review partner</h3><blockquote>This is a write-up that will be shared (and included in your final paper), and I recommend you use Word, Google Drive, or another format that is easy to share and annotate — you will be assigned a review partner to give you feedback directly on your work, and having it in such a format will make giving feedback a simpler process.</blockquote><blockquote>The first part of this write-up should be the actual math problem that you have chosen. Then, follow that with at least four different conceptual paths for your chosen math problem/investigation (at least one incorrect) with an explanation of each.</blockquote><blockquote>Together with each conceptual path there should be an analysis/explanation of why one may take that approach.</blockquote><blockquote>General format:</blockquote><blockquote><em>Conceptual Path 1: ….</em></blockquote><blockquote><em>Analysis of CP1: ….</em></blockquote><blockquote><em>Conceptual Path 2: ….</em></blockquote><blockquote><em>Analysis of CP2: ….</em></blockquote><blockquote>These conceptual paths can include your solution approach, any that you have seen before in classrooms or etc., and/or any that you can imagine that a student might take. At least one of these approaches should be “unproductive” — not leading to the intended endpoint (correct answer) due to lack of certain understanding or reasoning, misunderstanding or misinterpretations, making and bringing in assumptions, inadequate analysis of the problematic situation, etc.</blockquote><blockquote>For this week and all following, each conceptual path must be authentic. This means that an incorrect solution cannot be merely because of an arithmetic error (e.g., 2+2 accidentally added to 5), but must be related to the student’s mathematical thinking, reasoning, understanding (or the lack of it) in a powerful way. In addition, the conceptual paths cannot be vague — just saying that a student doesn’t understand the problem is insufficient — rather, say what underlying misconceptions are setting the student off on the wrong path.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8Cu6ma7-xvvw-QAh" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Part 3: Review the conceptual paths of your assigned partner, and suggest at least one more that they haven’t thought of</h3><blockquote>In your review, you have two requirements:</blockquote><blockquote>Identify and mark any sentences/thoughts that are confusing or unclear — and ask questions about what your review partner is trying to say. This will help them further clarify their own thinking about the math problem and conceptual paths.</blockquote><blockquote>Suggest at least one more authentic conceptual path that they haven’t thought of. The best way to do this is to try to solve the problem yourself — <em>before</em> reading their conceptual paths.</blockquote><blockquote>Although these write-ups may be short, they are dense — in order to understand their conceptual paths, you have to dig into the mathematics they have done. I will try to assign partners who have the same or similar math problems, but it may not be possible — so set aside time (and pencil/paper) to really dig into these!</blockquote><h3>Part 4: Revise your conceptual paths according to the feedback from your partner</h3><blockquote>Revise your conceptual paths according to the feedback from your partner, and post the revised version here. Make sure to ask your partner questions about anything they wrote that is confusing to you — you can email them privately, or message them privately or publicly via whatever online management system you are using for this class.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1TvVHNZTDbXo8BSz" /><figcaption>Photo by <a href="https://unsplash.com/@gabriellefaithhenderson?utm_source=medium&amp;utm_medium=referral">Gabrielle Henderson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Part 5: Interview one (a child, sibling, or parent in your household, a friend via Zoom), and take field notes</h3><blockquote>It is time to interview, folks — this is my favorite part of this project!</blockquote><blockquote>Interview while taking field notes. IMPORTANT: these interviews are <em>not about</em> teaching, but about understanding student thinking.</blockquote><blockquote>Field notes should include the age of the interviewee, the context (home, via zoom, etc.), and what they did with the problem.</blockquote><blockquote>Post the field notes as fulfilling this assignment — they don’t have to be readable to us, but they have to be readable to you, because you’ll need to refer to them later!</blockquote><blockquote><strong>Tips for interviewing:</strong></blockquote><blockquote>If you’re using a multistage problem, consider placing each part of the problem on its own page, so that the interviewee has plenty of space to write and explore. Then, print the same document for yourself, so you can take field notes directly on the part of the problem they are currently investigating.</blockquote><blockquote>Make sure that they write and talk as they work (and, if this is happening virtually, ask them to hold up the document or send you a quick picture of their work in progress as they go, to keep you up-to-date!). Remember to collect the written work afterwards (physically or via phone camera), and focus your field notes on making sure you can understand their thinking in their written work. Focus on thinking about and tracing their conceptual paths — whether or not you are prepared for the one they demonstrate.</blockquote><blockquote>Don’t tell them anything — just ask them questions. It’s okay if they are doing the problem wrong — just ask them questions that brings them back to the math (e.g., can you draw a picture of that? what happens when you try a different number? does this always work? can you explain why you did that, or why you think that is the case?). They may discover their own misconceptions and correct them — but if they don’t, that’s fine — just try to understand what they are thinking!</blockquote><blockquote>Something that I find very useful in doing these interviews is to review and annotate my field notes <em>immediately</em> after the interview. There are thoughts that I didn’t have time to write down, or things that I didn’t know were important at the beginning of the interview but emerge as important later on. So going over the field notes and putting those thoughts down when they are fresh in your mind is very useful! I also recommend that you briefly summarize the interview — a paragraph of “here’s what I think just happened.” The annotations and the summary will help you refresh your memory when you start writing up your project.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IFLOT0yU5rFgf_EP" /><figcaption>Photo by <a href="https://unsplash.com/@helloimnik?utm_source=medium&amp;utm_medium=referral">Hello I&#39;m Nik 🎞</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Part 6: Write up the results of the interview, using your field notes for evidence. Share the results with your review partner</h3><blockquote>Time to write your first draft up! Include the math problem, the conceptual paths you identified in advance (remember to credit your review partner with any they contributed), and then details about your math interview.</blockquote><blockquote>Feel free to use previously written work — for example, no need to rewrite the conceptual paths assignment if you think no changes are needed — just plop it in!</blockquote><blockquote>For the interview part, include a detailed account of the conceptual path your participant took to solve the problem. Think of it this way: what approach did you think kids would take to solve this math problem? What approach <em>did </em>they take? Why? and how did you support/fail to support different approaches? What still confuses you about what they did? What questions do you wish you had asked them during the interview? What surprised you about their conceptual path?</blockquote><blockquote>This assignment will be at least 3 pages, single-spaced — I’m not giving a maximum limit, because different problems/contexts might influence the amount of space each of you need.</blockquote><blockquote>Again, this document will be shared with your review partner (same as last time), so use a format that is easily edited/commented on.</blockquote><h3>Part 7: Give feedback to your partner on their write-up</h3><blockquote>Give feedback to your review partner on their draft, and share that document directly with them. As with last time, let them know when you don’t understand something, and ask them questions about what they mean. In addition, give them suggestions for large edits (e.g., flow — does the paper flow nicely from paragraph to paragraph and section to section? or are there some transition/re-ordering ideas that might help?), and make small edits (e.g., grammar, spelling, formatting, etc.).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PiY83R5IB6lC5WdZ" /><figcaption>Photo by <a href="https://unsplash.com/@awcreativeut?utm_source=medium&amp;utm_medium=referral">Adam Winger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Part 8: Incorporate the feedback you received into your paper, and submit the final version</h3><blockquote>Incorporate the feedback from your review partner, and submit your final paper from the interview project!</blockquote><p>If you use this assignment in your Math Methods course, I’d love to hear about it! And I’d be happy to fold in any suggestions/comments you’re willing to share. MATH NERDS UNITE</p><p><em>This work is licensed under a </em><a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"><em>CC BY-NC-SA 4.0 license</em></a><em>. Online attribution must include a link to this work.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b0cbb70142e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>