<?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 Data Science Studies on Medium]]></title>
        <description><![CDATA[Stories by Data Science Studies on Medium]]></description>
        <link>https://medium.com/@dataethnography?source=rss-a53ab0797b70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RHtzfWBRl8Zqq2Ahh5Bo_A.jpeg</url>
            <title>Stories by Data Science Studies on Medium</title>
            <link>https://medium.com/@dataethnography?source=rss-a53ab0797b70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:34:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dataethnography/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[Data Walking for Social Good]]></title>
            <link>https://medium.com/@dataethnography/data-walking-for-social-good-46b9f7808ccc?source=rss-a53ab0797b70------2</link>
            <guid isPermaLink="false">https://medium.com/p/46b9f7808ccc</guid>
            <category><![CDATA[ethnography]]></category>
            <category><![CDATA[data-literacy]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-for-good]]></category>
            <dc:creator><![CDATA[Data Science Studies]]></dc:creator>
            <pubDate>Sat, 07 Oct 2017 03:49:18 GMT</pubDate>
            <atom:updated>2017-10-13T23:21:26.979Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By </em><a href="http://fioregartland.org/wp-admin/post.php?post=2&amp;action=edit&amp;message=1"><em>Brittany Fiore-Gartland</em></a><em>, Anissa Tanweer, &amp; Meg Drouhard</em></p><p>When you tell people you are doing a data walk, they are immediately intrigued. Two words that are simultaneously experienced as a contradiction of sorts and a surprisingly pleasing pairing, conjuring many different imaginations of what a data walk might be.</p><p>At the <a href="http://escience.washington.edu/">eScience Institute</a>, a hub for data science at UW, data is most often talked about as the stuff of bytes and bits and interacted with via an increasingly complex computing infrastructure and software ecosystem. Yet a host of scholars across many fields, including Critical Data Studies and Science and Technology Studies (STS), have demonstrated time and again the social, embodied, and contingent nature of data, not to mention the social and political consequences of data in use. This sociotechnical lens on data, so well articulated and researched in these fields, finds few productive ways to crossover and intervene in the practical everyday work of data science. To talk about data as human and sociotechnical, while centrally important to changing the discourse, often leaves a gap in engaging practitioners where they are and generating paths forward together. In light of this gap, we have advocated for creating more opportunities for critical data scholarship and data science practice to engage as a way to strengthen and improve them (Neff et al. 2017). What if data scientists could experience the ways data are human, embodied, and contingent, much like an ethnographer of data might? It is in this gap that the <em>data walk </em>becomes a compelling proposition for bridging discourse and practice and generating new collaborative forms of inquiry.</p><p>But what is a data walk? There are many possibilities.Thanks to <a href="http://www.lse.ac.uk/media@lse/whosWho/AcademicStaff/AlisonPowell.aspx">Alison Powell</a>, who has developed the concept and fleshed out what one version of a data walk could look like, we had a very healthy and robust place to start. Powell defines datawalking as:</p><p>“A research process for producing radical data through collaborative walks. Data walking creates a process for observing, reflecting on and seeking to intervene in how data influences civic space. By playing roles as photographers, note-takers and map-makers, participants develop ways to think about and reflect on what data might be, and what role it plays in key social issues.” (<a href="http://www.datawalking.org/">www.datawalking.org</a>)</p><p>Our data ethnography team wanted to experiment with data walking as a way to engage data science researchers in an embodied experience of data. We imagined a kind of nature walk — full of mindfulness and careful observation — but focused on data.</p><p><strong>A Data Walk Experiment</strong></p><p>We took up this idea in the context of the <a href="http://escience.washington.edu/get-involved/incubator-programs/data-science-for-social-good/">Data Science for Social Good program</a> (DSSG) at eScience. As ethnographers embedded in the <a href="http://msdse.org/">UW Data Science Environment </a>focused on studying the ethical and social dimensions of data science, we saw the data walk as both a research endeavor and a contribution to the DSSG program. This program hosts 16 DSSG fellows for the summer to work on four DSSG projects that are each led by one or two project leads, who are from academic, nonprofit and government sectors. The project leads bring a DSSG project to the program and work with data scientists and DSSG fellows at the eScience Institute to complete the project over the summer quarter. The fellows have a wide range of disciplinary backgrounds, but are all allied in their desire to expand their experience and develop their skills in the DSSG arena. We decided to run a pilot data walk as an initial orientation activity for the fellows because there was a need for an icebreaker at the beginning of the DSSG program. We could have easily orchestrated an alternate kind of data walk that was more deeply engaged with each team and focused around a particular relevant issue to that team. In fact, this is something we hope to do in the future, but given the constraints of the program timeline and our own bandwidth, we decided this initial walk would be more of an introduction to the program and participants, a low stakes way to try the activity out and learn something through the experience.</p><p>We started with a <a href="https://www.slideshare.net/secret/efgkwUyFnVB4UO">short presentation</a> motivating the data walk. Rob Kitchen (2014) talks about data as immersed in data assemblages — “amalgams of systems of thought, forms of knowledge, finance, political economies, governmentalities and legalities, materialities and infrastructures, practices, organisations and institutions, subjectivities and communities, places, and marketplaces — that frame how data are produced and to what ends they are employed” (xvi). This was a framing concept we used to introduce ways of seeing data embodied in the world on a data walk. We also presenting a structure and expectations for the walk, along with some suggested questions for reflection during the walk, including: What is missing? What is data-rich? Data-calm? Data resistant? We then facilitated discussion with the whole group of fellows along with some of the project leads soliciting their definitions of data science for social good. We used their responses to highlight the primary facets and dimensions of data science for social good and we organized the fellows’ responses into three themes: 1) Data for accountability, transparency, accessibility, openness, 2) Data as a site for community and stakeholder engagement, 3) Data as embedded in a network and infrastructure. We split the group into three teams around each of the themes based on people’s interests. In these sub-groups we began the process of designating roles and clarifying how the data walk could support the particular theme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LNInLlCRpkZ0AbSh." /></figure><p>These themes were marginally helpful in focusing the groups. Some participants found the themes to be ambiguous and vague, and as the walks began, each of the groups ended up discussing a particular issue around which they could notice and reflect on data. That all three groups took this step independently without being prompted to do so in the instructions indicates to us that a focusing issue helps make the exercise more concrete, and in this case, helped the data walk participants know what was data when they saw it. For group 1, the issue that emerged was urban development; for group 2, the issue was construction; for group 3, the issue was homelessness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lquAtyPsWuR17qS5." /><figcaption>Photo credit: Brett Bejcek</figcaption></figure><p>We had each team assign roles that were slightly adapted from the ones suggested on datawalking.org. The roles included: Interviewer, Photographer, Note-taker, Collector, Navigator, and Map maker. One ethnographer accompanied each group and we each played different participant-observer roles within our groups. The roles helped organize people and provide a bit of structure, especially for those who experienced the task as overly ambiguous. However, when we do the activity again we will experiment with different roles, either tied to people’s particular expertise and perspective or potentially associated with different layers of the data assemblage.</p><p><strong>Data Walk Reflections</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VUaQHihuFezGRK7U." /><figcaption>Photo credit: Brett Bejcek</figcaption></figure><p>We were surprised at how easily people’s notion of data become something quite broad and inclusive as we walked. For instance, when the first author’s group was asked about what they were considering to be data, they agreed that it could be anything that conveys some sort of information. The group described how this could be a crosswalk or a stop sign. This group even picked up a stick that had been spray painted bright blue. The stick was part of a blue mark sprayed on the ground that was unintelligible to us as data walkers, yet meaningful to those working on the construction site nearby. The group guessed at what it meant, but in this case although they could, quite literally, <em>collect </em>the data, they couldn’t interpret it without the expertise and context of the particular construction project.</p><p><em>Developing critical data literacies</em></p><p>Each group produced a blog post as a creative response to the walk reflecting on their particular experience, which can be accessed <a href="https://uwescience.github.io/DSSG2017/updates/2017/06/16/data-walk-team-2.html">here</a>, <a href="https://uwescience.github.io/DSSG2017/updates/2017/06/16/group3-datawalk.html">here</a>, and <a href="https://uwescience.github.io/DSSG2017/updates/2017/06/16/transparency-data-walk.html">here</a>. What was fascinating was that the insights gained through this exercise reflected many of the core distilled contributions of a wide swath of scholarship in STS and critical data studies. The data walk provided a rich context for developing these critical data literacies. As Group 1 reflected on what data calm and data rich meant, they found that a stroll through the rose garden was data calm for one participant, but for an ecologist in the group, the rose garden and pond were more akin to her research sites, and so she considered the garden space data rich. The group distilled this insight in their blog post to “One person’s data poor is another person’s data rich…”, articulating a key insight about the contextual, relational nature of data discussed by many scholars, including ourselves as ethnographers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eBHowPUSdIOcST3e." /><figcaption>Photo credit: Brett Bejcek</figcaption></figure><p>Group 2 reasoned that perhaps data rich and data calm weren’t necessarily on opposite ends of a spectrum. They considered air quality and noise pollution to be data rich because of the measures that could be collected, yet they also expressed that ideally air quality could be data calm, which they defined as “consistent, not fluctuating…or data that’s well known or understood.” Thus, the group concluded, even for data that could be readily measured and have numerous metrics that are valued for their potential impact on human health and well-being, it is possible that “data calmness” might exist in the sense of continuity or consistency of a particular state. Group 2’s reflections indicated that their approach to characterizing data would be contextual and interpretive with respect to both the manner in which data was constructed as well as the purposes for which its analysis might be most impactful. While Group 3 was discussing how data could be used to understand the issue of homelessness, they took time to observe from a distance an interaction between several bicycle-mounted police officers and a few individuals who appeared to be homeless. As the conversation ended on amicable terms and the cops went on their way, the fellows reflected on how biased an analysis of the homelessness problem would be if it relied on data about arrests for vagrancy. This is because it would inevitably miss many of the inconstant factors and subjective choices that determine whether an arrest happens at all…things like “the mood of the police officers, how polite the homeless people are, the time of day, whether or not people are watching.” Their reflections surfaced another critical data literacy as they recognized the subjective interpretations and biases that get baked into data from their very inception.</p><p>The data walk offered the DSSG fellows some of the tools and opportunities to experience data ethnographically. In other words, through using the techniques of observation, participation, documenting, and interviewing, the fellows became the instrument for collecting, processing, and interpreting data in the world. This produced valuable insights that operate at the capillary level (Foucault 2003, p.27), the level of micro-circuitry that makes us who we are and shapes how we produce knowledge and power in society. These are the building blocks of data literacies, that will ultimately shape what kind of society we live in. In thinking about the power of a data walk, we find a striking resonance with ethnographic <a href="http://dl.acm.org/citation.cfm?id=3025823">work</a> by Samantha Hautea, Sayamindu DasGupta, and Benjamin Mako Hill (2017). They study youth who are programmatically analyzing public data about their own learning and social interaction in the Scratch online community, and find that in the discussions among these youth, many of them readily grasp profound implications of data analytics relevant to them and their community, and a set of critical data literacies emerge that can be mapped easily to expert critiques. Their findings and our own experiences in the datawalk indicate that offering data practitioners a personally relevant and embodied experience with data, along with space for reflection, is an important way to develop critical data literacies. This is an approach that should continue to be explored and extended.</p><p><em>Data Assemblage as Palimpsest</em></p><p>A palimpsest is defined as “something having usually diverse layers or aspects apparent beneath the surface” (Merriam-Webster). It comes from the Greek word palimpsestos meaning “scraped again,” which refers to a writing material (such as parchment or tablet) that was re-used after earlier writing had been erased, such that two (or more) layers of writing are visible. In other words, you can see how the materials and meanings have changed over time through the layers of residue. This is the metaphor that emerged from the first author’s reflection on data walking, captured in this fieldwork memo:</p><p><em>Mindful data walking makes us aware of the limitations of what we can see at the surface. As an ethnographer and data walker I am drawn to examine more closely, to see what is underneath, to probe further in time and space, to inhabit the surrounds. The process calls attention to the layers that are now erased, almost invisible and overwritten with new layers. Sometimes the under-layers are barely visible and you have to physically unearth them. On our walk around a construction site, our attention immediately was directed to the beautiful images of the futuristic modern looking building imaged on the mesh fencing.This signaled future oriented data, a projection of what will be and an attempt to engage the community and elicit buy-in for the long term vision of the building.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*avnwriEnt47Lahj1." /><figcaption>Photo credit: Brett Bejcek</figcaption></figure><p><em>There was a website written on the fencing that was supposed to have highlights, but when we tried to go to the website there was nothing there. Evidently, it, too, was under construction. We looked a little closer and saw another sign. It was a bit hidden only because it had started to camouflage with the natural setting around it. It was quite dirty, growing moss, caked with grime, and pine needles covering it. The stand of the sign looked like it had been there quite a long time as it was rusted. The sign depicted a greenhouse roof, what looked like it had been a futuristic image at some point in time, and developed in part by the Green Futures Research and Design Lab. It was a “green roof demonstration”, ostensibly on the bleeding edge of a green future, yet it’s aged look told a different story. And then juxtaposed next to the most recent layer of modern building signs and projections, it was clearly a legacy of what had been there before. It was the residue from a “future” replaced by a new future.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-qwPd1BynYvFuZlc." /><figcaption>Photo credit: Brett Bejcek</figcaption></figure><p>These enmeshed, aging layers of infrastructure that exist when you scratch beneath the surface made us reflect on the legacies and residues of data assemblages upon which newer layers of infrastructure and the latest, greatest promises for the future are laid. How these layers can be felt today, and the environmental conditions that continue to shape them and change their meaning. This is painfully seen in how the traces and effects of redlining practices and maps that occurred in the first half of the 20th century live on in our current digital systems, as revealed explicitly in <a href="https://www.bloomberg.com/graphics/2016-amazon-same-day/">Bloomberg’s 2016 analysis</a> of the reach of Amazon’s same day service delivery in major U.S. cities. By combining data about the zip codes eligible for Amazon’s same-day delivery with U.S. Census Bureau data, they found that in six major same-day delivery cities, the service area excludes predominantly black ZIP codes to varying degrees. One example is Atlanta, in which the areas south of downtown do not receive same day service, whereas the places in the northern parts of the city do. This service map overlaid onto census data shows how the predominantly black areas of south Atlanta are not provided the same service as the predominantly white areas of the northern parts of the city. These maps that reveal in stark terms the inequality present in current day access to services have been called out as one form of digital redlining (see Talbot 2016; Weisse 2016; Gralla 2016). These Amazon same day service maps demonstrate how the early redlining maps and the associated discriminatory practices can live on in digital systems. The metaphor of palimpsest helps us think through the traces, the power dynamics, those layers scraped away, but that continue to act in the data-intensive world around us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WDPphmUoyIjtM8x9." /><figcaption>Photo credit: Brett Bejcek</figcaption></figure><p><strong>Data Walk Aspirations</strong></p><p>We have many aspirations for the data walks of the future. We would like to work with particular groups and collaborations to develop focused data walks on a particular issue or place. We want to use the walk to bring in the appropriate stakeholders and use it as a space for soliciting and sharing knowledge and wisdom across the collective group. We are also interested in using the activity to generate multiple perspectives on data — or a richer experience of the data assemblage people work with every day. This could be incredibly useful for thinking through various stakeholder relationships and social implications in product design and development. Developing a sociotechnical and humanistic lens on data is an essential building block of data literacy, which supports the generation of more socially valuable, relevant, and ethical data science. If you think you have a situation or team or project that might benefit from a data walk, reach out and let us know!</p><p><strong>References:</strong></p><p>Foucault, M., &amp; Ewald, F. (2003). <em>“Society Must Be Defended”: Lectures at the Collège de France, 1975–1976</em> (Vol. 1). Macmillan.</p><p>Gralla, P. (2016, May 11) “Amazon Prime and the racist algorithms” <em>Computer World </em><a href="https://www.computerworld.com/article/3068622/internet/amazon-prime-and-the-racist-algorithms.html">https://www.computerworld.com/article/3068622/internet/amazon-prime-and-the-racist-algorithms.html</a></p><p>Ingold, D. and Soper, S. (2016, April 21) Amazon doesn’t consider the race of its customers. Should it? <em>Bloomberg, </em><a href="https://www.bloomberg.com/graphics/2016-amazon-same-day/">https://www.bloomberg.com/graphics/2016-amazon-same-day/</a></p><p>Kitchin, Rob (2014) <em>The Data Revolution: Big Data, Open Data, Data Infrastructures &amp; their Consequences</em>. Sage Publications, London.</p><p>Hautea, S., Dasgupta, S. and Mako Hill, B. (2017) <em>Youth Perspectives on Critical Data Literacies</em>. In <em>Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems</em> (CHI ‘17). ACM, New York, NY, USA, 919–930. DOI: <a href="https://doi.org/10.1145/3025453.3025823">https://doi.org/10.1145/3025453.3025823</a></p><p>Neff, G., Tanweer, A., Fiore-Gartland, B., Osburn, L. (2017) 2017) Critique and Contribute: A Practice-based Framework for Improving Critical Data Studies and Data Science. <em>Big Data</em>, Special issue on social and technical trade offs 5(2): 85–97. <a href="https://doi.org/10.1089/big.2016.0050">https://doi.org/10.1089/big.2016.0050</a> (OA)</p><p>Talbot, D. (2016, April 25) “Amazon Prime or Amazon Redline?” <em>MIT Technology Review. </em><a href="https://www.technologyreview.com/s/601328/amazon-prime-or-amazon-redline/">https://www.technologyreview.com/s/601328/amazon-prime-or-amazon-redline/</a></p><p>Weise, E. (2016, April 22) “Amazon same-day delivery less likely in black areas, report says.” <em>USA Today </em><a href="https://www.usatoday.com/story/tech/news/2016/04/22/amazon-same-day-delivery-less-likely-black-areas-report-says/83345684/">https://www.usatoday.com/story/tech/news/2016/04/22/amazon-same-day-delivery-less-likely-black-areas-report-says/83345684/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46b9f7808ccc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Community Level Data Science: beyond novelty squared]]></title>
            <link>https://medium.com/@dataethnography/community-level-data-science-beyond-novelty-squared-4a70c51eae50?source=rss-a53ab0797b70------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a70c51eae50</guid>
            <category><![CDATA[community-of-practice]]></category>
            <category><![CDATA[ethnography]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Data Science Studies]]></dc:creator>
            <pubDate>Tue, 22 Aug 2017 23:00:50 GMT</pubDate>
            <atom:updated>2017-09-27T23:03:47.433Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/3e9bb303e2c0">Brittany Fiore-Gartland</a> &amp; Anissa Tanweer</p><p>April 4, 2016, cross-posted at <a href="http://escience.washington.edu/community-level-data-science-and-its-spheres-of-influence-beyond-novelty-squared/">eScience Institute</a></p><p>Data science has many characterizations, but in academia it is often talked about as pushing the limits of both methodological and domain science, what Josh Bloom, a Professor of Astronomy at U.C. Berkeley, has referred to as “<a href="https://medium.com/@profjsb/novelty-squared-dd88857f662#.2dvh32y4s"><strong>novelty squared</strong></a>”. Bloom sees this as the “great challenge of modern interdisciplinary scientific collaboration”. The idealized characterization of data science in academia is also represented in the idea of shifting from the traditional T-shaped scientists, who have deep expertise in a single domain, to Π (<em>Pi</em>)-shaped scientists with deep expertise in both a domain and methodological science (as coined by <a href="http://www.sdss.jhu.edu/~szalay/"><strong>Alex Szalay</strong></a> and discussed <a href="https://jakevdp.github.io/blog/2014/08/22/hacking-academia/"><strong>here</strong></a> and <a href="http://www.xconomy.com/seattle/2013/11/12/moore-sloan-foundations-grant-uw-berkeley-nyu-37-8m-data-science/"><strong>here)</strong></a>. As Π-shaped data scientists, they are primed to innovate in multiple disciplinary trajectories. Bloom and others have argued that these characterizations of novelty squared and Π-shaped scientists represent the “<a href="https://www.wise.io/tech/two-unicorns-data-science-software-engineering-full-stack"><strong>unicorn</strong></a>” of data science.</p><p>The mythological, elusive nature of the ideal data scientist was supported through our ethnographic fieldwork. In search of these so-called “data scientists” across the data science environment, we could find scarcely anyone who consistently identified as a “data scientist.” We found more often that “data scientist” was a partial and relational identity, one layer of many. We encountered lots of data science, emerging across a network of interactions across a multitude of differently shaped scientists, from T to Γ (<em>Gamma</em>) to Π to even Μ (<em>Mu</em>) -shaped! Individuals mostly did not see themselves as particularly Π-shaped, a category many reserved for only a very select few that had accomplished an exceptional level of expertise and contribution to multiple fields. As one of us has discussed <a href="http://astrohackweek.github.io/blog/ethnographic-notes.html"><strong>elsewhere</strong></a>, perhaps a more realistic characterization of data science includes a network of differently shaped scientists practicing data science on a community level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WvSIN2EixFz3DmZB.png" /></figure><p><em>T, Π, Γ, Μ network. A network view of community-level data science reveals a mix of T-shaped, Γ-shaped, Μ-shaped, and Π-shaped scientists practicing data science.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/80/0*drlWrz3OvlD9toam." /></figure><p>This image by Brittany Fiore-Gartland is licensed under a Creative Commons Attribution-Non Commercial 4.0 International License</p><p>In order to understand what practicing data science looks like more precisely we embedded ourselves in the Data Science Incubator (DSI) program at University of Washington’s <a href="http://escience.washington.edu/">eScience Institute</a> so that we could observe a cross-section of data science collaborations from across the campus. DSI is a program that aims to bring together data scientists and domain scientists to work on focused, intensive, collaborative projects over the course of an academic quarter. The program solicits proposals from scientists across campus for projects that require data science expertise. The accepted applicants are then paired with one or two data science liaisons at the eScience Institute.</p><p>As ethnographers we were participant observers in the DSI and found that it represents a promising model for cultivating what we term community-level data science. Instead of breeding unicorns that embodied the singular, ideal “data scientist”, we found that the DSI fosters data science practice on the community level such that work is distributed across domain and methods-based approaches and occurs at the intersections of these different forms of expertise. Beyond acknowledging the DSI’s role in advancing their particular research projects, participants articulated an awareness that they were engaged the process of learning what it means to be part of a data science community. In other words, participants recognized data science as a cultural practice.</p><p>As such, the novelty-squared model falls short of sufficiently characterizing the DSI interactions. Our respondents didn’t talk about the value of data science solely, or even first and foremost, in terms of simultaneously pushing the known limits of domain knowledge and computational methods. Rather, they imagined the “novel” in data science as its ability to influence a range of day-to-day work practices and to expand an array of scientific and professional possibilities.</p><p>This program provides a window into a range of data science collaborations that have significant value without all being characterized by a novelty squared approach. How do we make sense of this range of interactions and understand the different motivations and values that are imagined by participants? Based on our ethnographic observations of this program and interviews with all participants we categorized the different kinds of value we heard participants imagine and ascribe to data science into six spheres of influence.</p><h3>Spheres of Influence</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PL9yoDwLp_48ruF3.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/80/0*lw3FTOQMuXFM0rLq." /></figure><p>This image by Paul Roberts is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License</p><h3>Individual</h3><p>Some participants told us that data science helped distinguish them from other scholars in their fields by equipping them with uncommon skills or enabling them to generate novel data sets. For example, one participant told us:</p><blockquote>“[When] you are on the job market you present kind of one paper that you are going to be a solo author on and it’s becoming less and less common to use these kind of prepackaged data sets. <strong>It’s starting to be that you need to bring new data to the table, to answer any questions, to get a good job.</strong>”</blockquote><p>Data science in this case is imagined to be influencing the sphere of the individual by providing researchers with skills, tools, and data that can help them advance their career and professional goals.</p><h3>Laboratory</h3><p>Other participants have come to the data science incubator hoping to gain new skills and learn new tools or systems they can take back to their labs or collaborative research groups in order to optimize their workflow. For one participant, it was about using the tools and techniques learned in the incubator for automating an existing workflow that involved processing files manually. For another participant it was about bringing a more seamless and transparent workflow to their lab using Git. In the words of this participant:</p><blockquote><strong>What I’d like to do is build a better infrastructure.</strong> Programming is on Git, so I can look at [lab member’s] programs. I can download them. I can check them. [….] “Do I trust this code? Do I not trust this code? How much is this a bunch of hacks? How much is this tidy code?” [….] I knew I wanted to start using Git. I did not use Git, so then moving [the] lab over and doing it, [when you] don’t even know how to use it yourself, it’s just never ever going to work.”</blockquote><p>What was important about this person’s data science incubator experience was the acquisition of new skills and tools that would allow her to streamline and optimize work routines across a team of faculty and student researchers. For a number of participants, it is not necessarily about scientific advancement in the short term; rather it is about investing in scientific advancement and productivity in the long term. This perspective foregrounds the potential for community-level data science to influence the sphere of the laboratory.</p><h3>Disciplinary</h3><p>Sometimes, participants saw data science as providing novel ways of developing theory within their discipline. One participant told us:</p><blockquote>“[Traditional theorists in my field] say ‘This is my regression model. It’s these x’s that I guessed, basically, are important…Then I’m going to use that model to predict y.’ There’s never a process of kicking out any regressors that are potentially unimportant. We consider that to be a very old-timey way of doing it. <strong>That’s the way we’ve been doing it since before we had these machine learning techniques that could tell us that stuff.</strong>”</blockquote><p>This person sees data science as providing a new way of knowing, or introducing epistemological novelty to his particular domain. So in this case, we can consider data science to be influencing the disciplinary sphere.</p><h3>User/Developer Community</h3><p>Another area of novelty people sometimes identified was their contribution to the development of data science tools. One participant described her experience this way:</p><blockquote>“… I was one of the only people doing these calculations and doing a lot of numerical stuff through [the newly developed cloud-based data management system]. I think a lot of the other queries were looking at text. It was kind of a different focus. <strong>I was finding some really good bugs for them.</strong>“</blockquote><p>Because the contributions she made could potentially affect anyone who is using or developing the new tool, in this case we’ve characterized community-level data science as influencing the sphere of the user/developer community.</p><h3>Cross-disciplinary</h3><p>Sometimes researchers were developing novel approaches to examining an object of study that is common across a number of fields. This was the case with one participant who was developing tools and methods to analyze the entire corpus of text on the Internet Archive:</p><blockquote>“At this conference we went to, there was a group of people that were trying to do link analysis [on the Internet Archive] …. I’ve been looking at the text. I told them … I’d send them all of the stuff that I’ve done, and they were really excited about that because they want to start looking at the text, but <strong>they hadn’t considered doing that yet because it’s 90 terabytes of text. How do you look at that?!</strong>“</blockquote><p>In cases like this, the methods and tools being developed could be applied to similar data generated and analyzed across different academic domains. Therefore, we can think of community-level data science as potentially influencing the cross-disciplinary sphere.</p><h3>Cross-sector</h3><p>At times, participants in our study talked about how novel data science tools and methods they were developing could be applied to questions beyond academia. This idea was expressed by a participant who thought his algorithms for analyzing time series might have commercial applications with other types of data:</p><blockquote>“I would love to, for example, start a company up, that tries to model all these time domain streams coming from wearables or the internet of things. Where these things are producing these data streams and people aren’t necessarily listening. But if they were — <strong>if you had the right software listening to these streams — you could actually understand what’s happening.</strong>“</blockquote><p>Because this person envisions taking software that was developed for academic research and adapting it for use in a commercial setting, we can say that the imagined influence of data science is taking place in a cross-sector sphere that spans academic and commercial sectors, as well as public and private sectors.</p><h3>Toward a community-level data science</h3><p>As these examples show, we found that the wide ranging imaginations for the value of data science were often not at the level of “novelty squared.” To be sure, many of the DSI projects would have been intractable without the incubator; posing research questions the participants couldn’t or wouldn’t otherwise ask. In some cases this novel science required a specific input and contributions from the data science liaisons and in other cases the novel science was supported through the dedicated time for elbow-to-elbow learning of tools and techniques from the data science canon. But the incubator participants often characterized what were major breakthroughs for them as trivial tasks for their data science liaisons. In other words, we didn’t see much of the idealized imagination of a data science that simultaneously pushes the frontiers of domain knowledge and computational methods.</p><p>When the projects did seem to be pursuing novelty squared, some participants were ambivalent about that dual trajectory and identified a tension between the mandate to develop novel computational tools and techniques on the one hand, and the mandate of doing what was best for their science on the other hand. But that’s a topic for another installment.</p><p>Nonetheless, as we’ve shown, for these participants, the data science work accomplished in the DSI was imagined to be novel and transformational within a range of spheres. Many of the researchers we observed saw value in becoming acculturated to the data science community. They talked about how learning the languages, tools, processes, and norms of data science would advance their careers, allow them to keep pace with the trends in their fields, optimize their work routines, alter the repertoires of their disciplines and subdisciplines, and connect them to the array of expertise and resources their research required. In addition to incubating science projects, the DSI incubates researchers within a data science community in which they are immersed in the cultural language of data science, learning how to think like a data scientist and how to be part of a data science community. As such, if we want to understand the evolution of data science in academia, we need to recognize that it is not solely about developing the capacity of individual researchers to employ novel methods, but also about forging a community-level data science that can reshape the cultural contours of the academy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a70c51eae50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Undercurrents at the Data Science Environment Summit]]></title>
            <link>https://medium.com/@dataethnography/undercurrents-at-the-data-science-environment-summit-7cf6822acf02?source=rss-a53ab0797b70------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cf6822acf02</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[ethnography]]></category>
            <dc:creator><![CDATA[Data Science Studies]]></dc:creator>
            <pubDate>Tue, 22 Aug 2017 22:54:50 GMT</pubDate>
            <atom:updated>2017-09-27T23:07:22.307Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/3e9bb303e2c0">Brittany Fiore-Gartland</a></p><p>October 24, 2014, cross-posted at <a href="http://escience.washington.edu/undercurrents-at-the-dse-summit/">eScience Institute</a></p><p>The Data Science Environments (DSE) Summit took place in beautiful Monterey, CA at the Asilomar Conference Center. The Summit brought together over a hundred participants across three universities (UW, UC Berkeley and NYU) involved in the <a href="http://www.moore.org/"><strong>Moore</strong></a> and <a href="http://www.sloan.org/"><strong>Sloan</strong></a><strong> </strong>Foundations’ <a href="http://msdse.org/">Data Science Environments </a>grant.</p><p>As a <a href="http://astrohackweek.github.io/blog/ethnographic-notes.html"><strong>data science ethnographer</strong></a>, I typically take on the role of participant-observer of various data science events, but at the DSE Summit I ended up being more of a participant than an observer. The high degree of participation made it challenging at times to listen as closely as I would have wanted to for underlying rhythms and patterns across the group. However participating in the discussion sessions and interactions I identified some important undercurrents. I draw out these undercurrents into two main themes that I discuss in this post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*Mo-Nticj-riXnthI.png" /></figure><p><strong>Imagining a Data Science Environment</strong></p><p>I participated in particular sessions, including teaching and curriculum development, data science ethnography, and the ethnography and evaluation working group, which were all, to some degree, imagining a data science environment. Underlying these discussions were questions of where and what exactly is data science? Where is it located and when does it matter? What are the origins and the goals? These questions bubbled up in conversations imagining a curriculum for data science, career paths in data science, and the very structuring of a data science community within academia. As these various concepts were discussed and imagined, there was a fracturing and multiplication of perspectives around these questions that sparked a bit of confusion.</p><p>There was some clear discomfort with the uncertainty and messiness around these issues. Many people seemed to be craving concrete definitions and the move towards formalization of data science, while others seemed content to not know their specific position or where the ship was headed exactly, opening themselves up to being influenced by the experimentation yet to come. Allowing ourselves as a community to sit with the uncertainty and messiness while we try things out and wrap our heads around the implications is very much part of the goal of these five years. As an ethnographer, I am drawn to messiness, so I was feeling quite comfortable in these conversations.</p><p>I am going to attempt to disentangle a few strands of conversation in the unconference session on data science ethnography which focused on different approaches to data science. This discussion drew on a previous <a href="http://astrohackweek.github.io/blog/ethnographic-notes.html"><strong>conversation</strong></a> about how different ways of approaching data science can emphasize a more individual-oriented view versus a community-oriented view. This conversation helped shift the focus from data science as residing within an individual to data science enacted at the community level.</p><p>This included thinking through the implications of different metaphors, such as T to pi (Π) to gamma for characterizing the shape of data scientists of the future. The shape of a pi-shaped scientist implies there is an expectation of individuals having expert-level depth of knowledge in two domains. Whereas a gamma-shaped scientist would have expert-level depth in one domain and be versed and proficient in another domain. The addition of other metaphors, such as gamma-shaped individuals, expands our imagination for what this data science environment might look like. It also has implications for how people may or may not identify as data scientists or as playing various roles within the data science community. This gets at the heart of the question, “What are we building?”</p><p>This question of “What are we building?” opens up other fractures in perspectives around how applied or theoretical data science is and “should” be. As the term data science has accumulated many meanings across industry and academia, there are distinctions many people wanted to make around data science in a research sense, data science in an applied sense, and data science in a professional sense. Was data science going to be its own discipline, its own department, or was it simply a new dimension of the work of all other domains? Is data science always applied? What would its body of theory look like? What are the political implications of these different imaginations of data science for issues like status and careers?</p><p>A related strand of conversation emerges around the question, “Where are we building it?” A strong current across the discussions imagined data science coming out of statistics and/or computer science, which alienated some people within the group who did not see it that way. Others wanted to frame data science as an integral part of all domain sciences in this data-intensive age. These different imaginations require a language and infrastructure we don’t yet have and must build. What would it mean to be neither and both of these in the institutional context of the university?</p><p>Another strand emerges around the characterization of how and when is data science. This strand of conversation was first dominated by talk about “data producers” and “data consumers”. This characterization implied ways that the work of data science was being divided up. But by the end of the conversation, these oversimplified categories fell short of describing a more complex ecosystem of data science. First, this is because there are those individuals and practices that embody both consumption and production. Second, these categories don’t encompass the mediator roles and mediation practices that are integral to the data science environment. These roles and practices involve the work of translating, connecting, and often innovating in the interstices.</p><p>The conversation around the community level data science and the relation to T, pi, and gamma appropriately ended with a move to focus on the “horizontal line”, the connections and intersections among these various disciplines, the mediator roles and practices that support research translation. What emerged was that, perhaps as or more important than a conversation about the number of legs or their length (pi versus gamma), is the conversation about the character and future of the “horizontal line.” This focuses us on the translation work and the supporting infrastructures that function to forge and maintain connections across legs. Part of the important impact I think the ethnography group can have is in making visible the character of different horizontal lines, and to better understand how they function and their implications for developing a data science environment.</p><p><strong>Collaboration in Context</strong></p><p>Throughout the Summit, collaboration was often referred to and leveraged as an abstract principle that reigned over all of the activities of the grant. People talked at high levels about the goal of collaboration mostly ungrounded in what, when, where, how, and why. The overbroad terms in which collaboration was talked about potentially obfuscated the many levels, layers, and conditions at which differently configured collaborations may occur. Collaboration is multiple things, and importantly, it is negotiated within a multitude of circumstances and values.</p><p>The spaghetti and marshmallow hack (the community building activity we did on Tuesday morning) aimed to have the group experientially engage with the inextricable relationship of collaboration and the performance of tasks at hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/169/0*TwNGK2HnqVn4-PyG.png" /><figcaption>Photo credit: Gina Neff</figcaption></figure><p>For example, in many cases there is a fragile balance between attending to the work of collaboration and getting things done. Collaboration does not exist within a vacuum without constraints or consequences. We hope that the goals of the collaboration are aligned with measures of performance, but this is not always the case. Further, as anyone who has ever collaborated knows, collaboration requires time and energy beyond the task itself. Yes, we want to incentivize more collaboration across domains and groups, but most importantly we want to learn about how we configure effective collaborations, what different roles are important, and how different forms of value can be strategically distributed across participants.</p><p>Collaboration as a goal may make a lot of sense at the level of an individual’s specific research question when this question requires multiple types of expertise to answer, but at other levels such as collaborating across institutions to support a data science environment, the value and the incentives of collaboration may be harder to assess and determine for individuals. <strong>What our three universities together with Moore/Sloan are trying to learn about and develop on an institutional level shifts everyone’s focus beyond the particular research at hand to the hard work of building the infrastructures and cultivating the relationships, cultural norms, and values that are necessary for supporting a thriving data science environment.</strong></p><p>Interestingly, the concrete work of building collaboration the how, where, when, and why, one might say, didn’t get discussed until the Wednesday morning unconference when many had left, and many who were still there were “raptured” in important high-level meetings. The group that was left was made up of a mix of graduate students, postdocs and research scientists, but no faculty. It was about 12 of us discussing exactly how connection and communication would continue after the Summit. What infrastructure would support the exchange of ideas and the conversations we had begun to have here?</p><p>We discussed the role of a chat room and the needs of different working groups for sharing and connecting across the campuses. This is work that needs to happen to ground any kind of collaboration. This was what the 12 people left on the final morning thought was most important to discuss over any other data science topic. These people didn’t just discuss these questions, they generated ideas, innovated around these ideas, and executed these ideas. There is now a MS-DSE <a href="https://msdse.slack.com/"><strong>chat room</strong></a> set up and multiple ongoing conversations about how to connect and communicate within and across campuses. I felt inspired by this session as I got the sense that these interactions represented the movement taking root and beginning to grow!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cf6822acf02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacked Ethnographic Fieldnotes]]></title>
            <link>https://medium.com/@dataethnography/hacked-ethnographic-fieldnotes-4e59bc95f4e5?source=rss-a53ab0797b70------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e59bc95f4e5</guid>
            <category><![CDATA[astronomy]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[ethnography]]></category>
            <dc:creator><![CDATA[Data Science Studies]]></dc:creator>
            <pubDate>Tue, 22 Aug 2017 22:42:52 GMT</pubDate>
            <atom:updated>2017-08-22T23:42:27.579Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/3e9bb303e2c0">Brittany Fiore-Gartland</a></p><p>October 1, 2014, cross-posted from <a href="http://astrohackweek.org/blog/ethnographic-notes.html">Astrohackweek</a></p><h4>What is data science ethnography anyway?</h4><p>As an ethnographer of data science, I immerse myself in particular communities to understand how they make sense of the world, how they communicate, what motivates them, and how they work together. I spent a week at astro data hack week, which might as well have been a foreign culture to me. I participated as an active listener, trying to sensitize myself to the culture and discern patterns that may not be self-evident to people within the community. Ethnography can have the effect of making the ordinary strange, such that the norms, objects, and practices that the community takes for granted become fascinating, informative sites for learning and discovery. Many of the astro hackers were probably thinking, “Why is this woman hanging around watching me code on my laptop? There is nothing interesting here.” But I assured them it was interesting to me because I was seeing their everyday practice in the context of a complex social and technical world that is in flux.</p><p>Ethnography can be thought of as a form of big data. Typically hundreds of pages of fieldnotes, interview transcripts, and artifacts from the field would be recorded over a long period of time until the ethnographer determines they have reached a point of saturation. The analysis process co-occurs with the data collection, iteratively shaping the focus of the research and observation strategy. Across this massive dataset with an abundance of unwieldy dimensions, the ethnographer has to make sense. The ethnographer works with members of the community to help them interpret what they are observing. Ethnographic insights, what many may term “findings”, emerge as patterns and themes are detected. Theory and new questions are generated, rather than tested. In this process I also acknowledge my own biases and prior assumptions and use them as ways to probe deeper and understand through them rather than ignore them. For instance, I came to astro data hack week not understanding much of anything people were talking about. It made me prone to feeling intimidated and I recognized with this intimidation my own reticence to ask questions. My own experience with this feeling helped me identify in others that were also feeling variations of this and also be able to identify what helped transform that feeling throughout the week into a more comfortable and curious state.</p><p>I only spent 5 days among the community of astro hackers, but in the spirit of hacking, I have a few “hacked” fieldnotes to share. Sharing is a key component of the hack week and as a participant I feel it is important to follow suit. But bear in mind these thoughts are preliminary. So, what have I been working on this week?</p><h4>Initial descriptive observations from an outsider (a little tongue-in-cheek, forgive me):</h4><ul><li>Astro hackers live in a very dusty, dirty, and noisy environment! Very hard to keep clean and elaborate measures are taken to obtain a signal. But when the signal is too strong or the data too clean, there is a feeling of mistrust.</li><li>The common language is Python, although there are many other dialects, some entirely made of acronyms, others sound like common names, such as George and Julia.</li><li>When talking there is always some form of data, documentation or model that mediates the conversation, whether it is on the white board, on the screen, or through representational gestures.</li><li>Although most people are studying something that has to do with astronomy, they can literally be operating on “different wavelengths”!</li><li>Astro hackers play with “toys” and “fake data” as much as “real world data”!</li><li>Coffee and beer fuel interactivity!</li></ul><h4>Themes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*9ksCIIggY0PVdWKp.jpg" /></figure><p>Josh Bloom teaches Machine Learning</p><p><strong>Data science at the community level: From T to Pi to Gamma-shaped (Josh Bloom’s term) scientists:</strong> Across the group I heard over and over again in various ways reference and deference to those who are more expert, those who are smarter or those who know more than I do. Granted, this is a somewhat common occurrence in the culture of academia as we are continuously humbled by the expertise around us. However, I found this particularly acute and concentrated within this community. What I heard across students, postdocs, and research scientists was more than the typical imposter syndrome. It was the feeling that they are expected to be experts or at the very least fluent in a range of computing and statistical areas in addition to their own domain. While this motivates people to be at a hack week such as this, it can also have the unintended effect of making people intimidated and overwhelmed with having to know everything themselves. This can have a chilling effect across the community. This means the feeling that other people know more than they do is pervasive and this often leads to thinking their questions aren’t valuable for the rest of the group, and therefore, not worth sharing. This is a negative thing and we want to ensure this effect is minimized. Not only is it bad for morale; it is bad for science. We should consider who feels comfortable taking a risk in these settings? A risk might be asking a question that they fear isn’t scientifically interesting for others. Or sharing something that isn’t complete or isn’t perfect. If we take what Josh Bloom says, that we might be better off thinking about data science on the community level, happening in a more distributed way, rather than data science on the individual level, we can begin to paint a different picture and change some of the expectations that may trigger this negative effect.</p><p>Josh Bloom’s lecture on machine learning explained the popular idea of “Pi-shaped” individuals (a buzz word for the academic data science community) and his preference, for talking about “Gamma-shaped” individuals. Rather than promote the idea that there is an expectation of individuals having expert-level depth in two domains, which is unrealistic for the majority of people, what if we thought of people as Gamma-shaped? These people would have expert-level depth in one domain and also be versed and proficient in other domains. Someone with their PhD in biology may be conversant in the language and culture of computer science enough to have conversations and collaborate, but they don’t necessarily need to be an expert in computer science to the extent that they are able to advance the discipline. These Gamma-shaped individuals can work with each other to bridge multiple domains of expertise. This Gamma symbol better reflects the makeup of individuals in this astro hack week community and this view of data science allows for the expectations to shift to the community and to the collaborative interactions between people. This shift is important and has implications for thinking about how to better structure hack week. For instance, with these tweaked expectations a learning goal of the hack week might be working together across Gamma-shaped individuals.</p><p><strong>Categorizing hacking interactions</strong> I categorized the different kinds of hacking interactions I observed over the course of the week. This list is not meant to be exhaustive, but it might be helpful in understanding the diversity of interactions and how to facilitate the types of hacking interactions desired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*p3NcaI7Z9A-Db2fs.jpg" /></figure><ul><li><em>Resource Seeking:</em> An individual works on their hack idea and uses other people as sources of expertise when they need help Asymmetical Synergy: A pair or small group joins together to work on a hack idea in which one person is learning something, such as an algorithm, and the other has more advanced knowledge and is exploring what that algorithm can do. They are generating something together but getting different things out of the activity.</li><li><em>Symmetrical Synergy:</em> A pair or small group joins together to work on a hack idea and iteratively discovers how their expertise informs the other, or how interests synergize. Then, they generate something new together.</li><li><em>Comparing Notes:</em> An individual works on their hack idea and shares it with others based on their common interest. A form of comparing notes in which they are talking about the work more broadly and loosely.</li><li><em>Learning Collective:</em> A semi-structured activity that draws multiple people in to learn something collectively, thus creating a learning collective.</li></ul><h4>The Importance of “Connective Tissue”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*0nrrS2IoTEcDc2ds.jpg" /></figure><p>Across this community there is great diversity across institution, dataset, data source, methodology, computing tools and packages, statistical approach, status within academia, and level of knowledge in different arenas. This creates many opportunities for discovering connections, for sharing, and working together. Yet this also presents challenges for forging these connections especially within the broader academic environment which in many ways doesn’t incentivize collaboration and “failing fast”. Failing fast refers to the capacity to be highly experimental, to take risks, and invest a little bit often, such that when things don’t work, it is framed much more as part of the iterative process rather than as a significant loss. In a culture where people are failing fast, people are more likely to take risks and learning can happen more rapidly.</p><p>A key and essential role that emerged this week was the set of capacities for facilitating connection across people and ideas, what Fernando Perez has called the “connective tissue”. There is a need both the people and the organizational structure that supports social and technical resonances across a wide range of people and can facilitate connections among them. These people can play a role of translation across ideas that might appear otherwise unrelated. They also provide coaching (as opposed to teaching) to help both identify and achieve their goals. We should all be learning from these people so that we can all contribute to the connective tissue. This connective tissue developed further throughout the week. Specifically, the more semi-structured collective learning activities and the emphasis on working in pairs greatly increased the productivity across the group (there was more to show at the end of the day) and the interaction (fewer people with earphones in and more talking). I also observed many more small and big shared victories. I hadn’t yet seen a high five and I saw two instances on Thursday, which reflected the overall sense that the victory was about more than an individual completing the hack, rather it was shared and celebrated together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*u9KTeYoCM6Tal7_b.jpg" /></figure><p>This hack week performs as a kind of lab space where people can take risks and work together in new ways that they might not be incentivized to do otherwise. It is an opportunity to change the incentives for a short period of time. In fact, the frictions that we see emerge in this hack week (i.e. people needing to work towards publications) reflect some of the default incentives clashing with hack week incentives. For future hack weeks it might be important to advocate failing fast through normalizing it and facilitating a supportive environment for risk taking. In addition, part of the goal of a future hack week might be more explicitly to learn about how to work together and what it takes to develop connective tissue through incentivizing a range of different hacking interactions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e59bc95f4e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>