<?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 Alexandra DM on Medium]]></title>
        <description><![CDATA[Stories by Alexandra DM on Medium]]></description>
        <link>https://medium.com/@fromADMwithlove?source=rss-e7d2ff5d60c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uMxNC_2aOx0JoEs05QASzQ.jpeg</url>
            <title>Stories by Alexandra DM on Medium</title>
            <link>https://medium.com/@fromADMwithlove?source=rss-e7d2ff5d60c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:10:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fromADMwithlove/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[Opportunities for making appraisal transparent when documenting the now]]></title>
            <link>https://medium.com/documenting-docnow/opportunities-for-making-appraisal-transparent-when-documenting-the-now-10b807606d39?source=rss-e7d2ff5d60c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/10b807606d39</guid>
            <category><![CDATA[archive]]></category>
            <category><![CDATA[web-archiving]]></category>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[Alexandra DM]]></dc:creator>
            <pubDate>Wed, 14 Jun 2017 12:35:44 GMT</pubDate>
            <atom:updated>2017-06-14T12:35:44.321Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tz_jtd9i_p38dsvt4EDRLA.jpeg" /><figcaption><a href="https://www.trudilynnsmith.com/finding-aid/">Finding Aid</a> by <a href="https://www.trudilynnsmith.com/">Trudi Lynn Smith</a></figcaption></figure><p>While archives and archivists have long liked to believe that we are neutral in the process of building collections, <a href="http://saa.archivists.org/store/archives-power-memory-accountability-and-social-justice/1354/">we know</a> this is not true. Traces of the archivists hand can be seen in the arrangement and description of collections, but often not in the appraisal, though this may have the largest impact on what information is available within a research collection. In <em>Colophons and Annotations: New Directions for the Finding Aid, </em><a href="http://americanarchivist.org/doi/pdf/10.17723/aarc.65.2.l3h27j5x8716586q?">Michele Light and Tom Hyry make an important argument</a> for why documenting appraisal decisions and publicizing them through annotation in finding aids can be useful. They state, “Indeed, our personal, professional, political, and cultural biases are most obvious, and controversial, in the practice of selection and appraisal, and the profession has been struggling with these issues for more than a generation.”</p><p>Appraisal decisions are not often transparent in finding aids, as <a href="http://americanarchivist.org/doi/pdf/10.17723/aarc.76.2.x4h78gx76780q072">Kathrine M. Wisser and Jackie Dean found</a> in analysis of Encoded Archival Description tag usage. Only 4.8% of the encoded finding aids in their study of over one thousand used the &lt;appraisal&gt; element. This presents as a significant gap in sharing knowledge about collection decisions considering how much our own biases, the political climate, or institutional policies may influence those choices. There are many potential reasons for the omission of an appraisal note, including a dearth of documentation from accession, lack of an appraisal process at all, internal institutional decision making, or perceived insignificance of the metadata field. There is also great opportunity to correct this gap, particularly when archivists are actively engaged in documenting the now. As <a href="https://issuesandadvocacy.wordpress.com/2017/03/27/archivists-on-the-issues-the-neutrality-lie-and-archiving-in-the-now/">Sam Cross explains</a> in <em>Archivists on the Issues: The Neutrality Lie and Archiving in the Now</em> archivists have a mandate to actively collect, which means we are making appraisal decisions and can document them and their impact along the way.</p><p>The DocNow team is dedicated to helping archivists and researchers ethically create collections of social media data, particularly Twitter data. When archivists decide what to collect from Twitter they begin the appraisal process of identifying relevant hashtags, users, timelines, and locations for creating collections. As they do this work it’s important that they can easily build a log of searches and decisions, and have a space to annotate their decision making process. This form of documentation can then be used to help write the appraisal section of the finding aid. We are excited to be able to provide this feature for added transparency, but know the community must also come together to help build standards for how to describe appraisal of social media content in finding aids.</p><p>We are still in the early days of archives creating finding aids for collections with social media data, and there are no set guidelines for how to describe a <a href="http://www.docnow.io/catalog/">tweet ID dataset</a>. A pioneering early example is the finding aid for the <a href="http://proust.library.miami.edu/findingaids/?p=collections/findingaid&amp;id=1550">US-Cuba Policy Change Twitter Archive, 2014–2015 from the University of Miami Cuban Heritage Collection</a>, which clearly lists in the both the Abstract and Scope and Contents which hashtags were captured, the date range, and the restrictions placed by Twitter’s API and terms of service. The collection, built in 2014, was created using the command-line <a href="https://github.com/docnow/twarc">Twarc</a> tool and is served up to an internal community as a full dataset, rather than just the tweet IDs. Without more recent tools like DocNow’s <a href="https://github.com/docnow/hydrator">Hydrator</a> this was the only easy way to share the data. This information, along with the decision making process to capture the six hashtags specified, and what Twitter’s Streaming API rate was at time of capture, could be added to an appraisal note to enhance understanding of what is in the collection and why.</p><p>Another encouraging example is the work of the Progressive Librarians Guild Toronto Area Chapter. Their <a href="http://archives.plggta.org/index.php/free-dale-askey-campaign;isad">#freedaleaskey collection</a> includes a general appraisal note explaining their interests in building the collection. The Twitter feed in Series 03 explains method of capture and each tweet ID set describes what hashtag was captured, the date range, and the number of tweets. Furthermore, the tweets are displayed online as well as available for download.</p><p>These early finding aids describing and sharing Twitter content also bring up the important question of sustainability for access within finding aids — as technologies and the Twitter API and terms of service change, archivists will have to review and maintain finding aids to ensure the collections are still accessible. This is a new challenge for archivists that could add considerably to workloads over time.</p><p>With this new and important work going on in the archivist community, we look forward to discussing the value of appraisal transparency, tackling the appraisal issues inherent in social media data, and developing best practices for highlighting the non-neutrality of the archivist to best contextualize collections. We hope to host conversations on these topics soon, so look out for details!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10b807606d39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/documenting-docnow/opportunities-for-making-appraisal-transparent-when-documenting-the-now-10b807606d39">Opportunities for making appraisal transparent when documenting the now</a> was originally published in <a href="https://medium.com/documenting-docnow">Documenting DocNow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anti-social web design]]></title>
            <link>https://medium.com/@fromADMwithlove/anti-social-web-design-6c34c2b67f7?source=rss-e7d2ff5d60c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c34c2b67f7</guid>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[Alexandra DM]]></dc:creator>
            <pubDate>Mon, 22 May 2017 03:15:05 GMT</pubDate>
            <atom:updated>2017-05-22T03:15:05.907Z</atom:updated>
            <content:encoded><![CDATA[<p>I am of that generation that first grew up in the hyper-connected world of the social internet. Friendster at 14, Myspace at 16, Facebook at 18, and so on. Intensely interested in how social media effects our identities, relationships, and information consumption, I test and critically think about each platform I delve into. In part, my experience with these social platforms is what led me to get a master’s degree in information studies, and to work as a user experience designer for platforms embedded with social interactions.</p><p>For half of my life I have actively considered and curated my online life — which largely means my social media presence. I have gone cold turkey for months on end, disgusted with the advertising, the conversations, or my addiction to it all. Through much trial and error I have come to a comfortable social internet experience that incorporates my work interests, art interests, sense of humor, awareness of events, and knowledge of friends’ lives. For the most part I have been happy and comfortable sharing what I do.</p><p>Recently, though, I decided to break open my weary suitcase of half-written thoughts in half empty notebooks. I knew I wanted to work on these bits and pieces, turn them into something I could feel worth sharing with someone. As I started to work I realized I wanted to share these writings online but not through any of the mediums available to me. The writings are personal, a part of me, and often written to other people, about parts of them. Thinking of “likes”, the ability to share at the click of a button, advertising in the periphery, even to have a link to send around made me feel queasy.</p><p>So what is a user experience designer to do? Build an anti-social website! Not something hidden — I want the writings out there for anyone who might be interested — just something that isn’t so easy. Read it if you want to, but you have to want to first. You have to find it. To find a piece again you’ll have to remember the title.</p><p>I recognize few people want to interact with an RSS-less, anchor-less, date-less and generally ugly website. But if you’re interested in love, in the effort it takes to pursue it, to think about, and to write it for the world to see, well, spend some time with me here: <a href="http://fromadmwithlove.me/">http://fromadmwithlove.me/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c34c2b67f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pioneer Cafe, December 21, 2016]]></title>
            <link>https://medium.com/@fromADMwithlove/pioneer-cafe-december-21-2016-aaa227f317de?source=rss-e7d2ff5d60c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaa227f317de</guid>
            <category><![CDATA[short-story]]></category>
            <category><![CDATA[scenes]]></category>
            <category><![CDATA[short-fiction]]></category>
            <dc:creator><![CDATA[Alexandra DM]]></dc:creator>
            <pubDate>Thu, 22 Dec 2016 01:53:24 GMT</pubDate>
            <atom:updated>2016-12-22T02:00:47.458Z</atom:updated>
            <content:encoded><![CDATA[<p>Brown granite stacked stones ornament the facade both inside and out. Large windows make the upper two-thirds of the north and east walls. A white wooden border and off-white speckled wallpaper finish the bottom third. The chairs are pink and off-white speckle to match. The table covers are uniform light maroon clothes with a mix of plastic covers and glass plate tops.</p><p>A small TV along the top of the south wall plays Dr. Oz and Christmas decorations somehow make the place sad instead of festive. When I first walk in I am the only customer and have my choice of tables. I choose a plastic top. Sitting one row from the northern windows facing the northwest glass encasement, I can see people walk in from the street — if anyone actually chooses this path. The Pioneer Cafe is connected to an Extended Stay and the three diners I observe while sitting all come from the hallway around the corner from the register.</p><p>The hostess/server works alone in the front room, which does not seem too stressful given the diner’s emptiness. Maybe she gets lonely. Today she is wearing a red flannel and a sad face to match the Christmas decor. She looks All-American but has an Armenian accent, which just makes her more American to me.</p><p>The first diner other than me to come in is an intrigue I did not know I wanted. He is around 75 years old, with a hunched back and cranial displacement that requires to turn his entire body to face you. He sports a large gray blazer on his short frame and walks with a push-wheel laundry cart to steady his gait. He asks after the hostess’ child, says hello to me, and clearly is in need of deeper human connection, but I, as usual, am currently emotionally unavailable.</p><p>Two other diners enter but I stop taking notes. Instead I ponder the relative qualities of communicating versus observing, and lose track of my surroundings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g-JJMTJiCUwwoKYeEscyXQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaa227f317de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mapping the Journey: A walk in the shoes of our users]]></title>
            <link>https://medium.com/documenting-docnow/mapping-the-journey-a-walk-in-the-shoes-of-our-users-de2dac3cb34f?source=rss-e7d2ff5d60c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/de2dac3cb34f</guid>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[archive]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Alexandra DM]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 18:09:21 GMT</pubDate>
            <atom:updated>2016-11-18T18:09:21.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V8dk5baLBK5uDwngn0GwmA.jpeg" /><figcaption>Photo from user story mapping exercise at DCPL, September 30th, 2016 (photo by author)</figcaption></figure><p>We are excited to present the first drafts of our <strong>user story maps,</strong> which take users on a journey from first to last steps of using the DocNow app to build ethical social media collections. As discussed regularly in our <a href="https://docs.google.com/forms/d/e/1FAIpQLSf3E7PAXPoT-XoedpEy9UCTpDPS8kPj5JkMwpaWbuqVP0bTrQ/viewform">Slack channel</a>, we believe there is much work to be done <em>outside</em> the application to build truly considerate and safe collections, and we want the application to reflect that mindset. We developed the following story maps over two days in-person at the <a href="http://www.dclibrary.org/">DC Public Library</a> (many thanks to <a href="https://twitter.com/missjames">Maryann James-Daley</a> for the space), with helpful feedback from <a href="https://twitter.com/justin_littman">Justin Littman</a> of <a href="https://social-feed-manager.readthedocs.io/">Social Feed Manager</a> fame at George Washington University and <a href="https://twitter.com/trevormunoz">Trevor Muñoz</a>, Associate Director of the <a href="http://mith.umd.edu/">Maryland Institute for Technology in the Humanities</a>.</p><p>Having developed <a href="https://news.docnow.io/design-for-social-good-aa5503dcbef2#.gwr29ld5q">personas</a> through interviews and board meeting discussions,we now stepped into their shoes to try to use DocNow. Walking through the desired steps from left to right helped us think about when users will need to accomplish a task to move forward, where they might have ethical questions, and what pain points might exist in accomplishing tasks. As we added post-its to the wall we realized there are three different maps to consider: the <strong>Documenter Map</strong> (primary user of DocNow), the <strong>Public User Map</strong> (viewers of the Documenter’s end product), and the <strong>Initial Setup/Admin Map</strong> (setting up and administering the app for individuals or institutions). We are using these story maps to help guide our development plans, keeping a holistic view of the app in mind so that we do not have major gaps in the final product.</p><h4>Map Key</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*44FvClLYG7AoUbA30EHvRQ.jpeg" /></figure><p>Typical of most user story maps, the top row of <strong>white post-it notes</strong> is the stage in which a set of actions (the second row) takes place. In our maps, we are thinking of these as the screen or page a user will be looking at. The <strong>yellow post-its</strong> are individual actions a user walks through to complete their work. The third row of yellow post-its are items we want to build in but may not make it in the initial development round due to time constraints. The notations on these cards are generally broad, vague phrases that will be defined better as we begin development. A <strong>red star</strong> tags ethical considerations, as a commitment to ethics has been at the foreground of our work. The <strong>green post-its </strong>are options that are determined instance-wide by the administrator or researcher during application set up.</p><p><strong><em>We invite you to please read through them and leave comments in Medium with questions or concerns. </em></strong>While we feel we did a good job of capturing the wishes and ideas of our potential users, more feedback will help us refine terminology and ensure a comprehensively thought-out product. The stories aren’t meant to be etched in stone, they are living documents that reflect our current thinking of the thing we are building.</p><h4>The Documenter’s Journey</h4><p>This map describes the journey of the four personas of our DocNow users. These are the steps we worked on with our advisory board at our meeting in St. Louis this summer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e6bPFwQN19hQclqfqr-B8g.jpeg" /></figure><p>Briefly, we expect documenters to log in, be able to view collections (twitter datasets) they have already started, or start a new search. Documenters will then explore some search parameters, being able to modify as they go, and see what kind of data is coming in before actually starting a search and writing data to memory. Once they decide to start collecting, they will name and describe the collection and set the collecting parameters. At this point they will set up the message to auto-tweet about what is being collected (the Twitter account being set up in the Admin panel), an ethical notification that will bring the public to a page describing <em>why</em> the data is being collected, <em>by who</em> and allow for opt in/opt out, or to contact.</p><p>Documenters can also review in-progress and completed collections, where they can grab URLs of web pages to archive, grab images, and annotate collections. Finally, when a documenter feels the collection is completed and fully described, they can publish the collection to the public interface.</p><h4>The Public User’s Journey</h4><p>This map describes what the public sees of any DocNow instance. This could be anyone from researchers coming in to an archive to a Twitter user who finds out a hashtag they use is being collected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TWndqqsr-wHiMuPVXG46qw.jpeg" /></figure><p>Public engagement is at the core of our vision for DocNow. While we believe social media data should be collected and researched, we also believe that the people creating this data should have a say in how (or if) they are represented in archives and publications. To that end, each instance of DocNow will have views where the public can learn about why the person or team is using DocNow, what is being collected, and how to opt in, opt out, or learn more about the work. Crucially, a Twitter user will be able to check if they are present in any dataset.</p><p>Furthermore, the public will be able to do their own research in the collections made public. Each DocNow instance will be able to choose in the Admin panel if they want to make the public register to do research, to keep a trail of who is using these collections. The public will be able to view visualizations of collections and download Tweet IDs — that they would then have to hydrate on their own (as per Twitter’s Terms of Service). The public interface will be a major point of engagement, but the application will also encourage all DocNow documenters to reach out to Twitter users in other ways, particularly if a specific voice will be highlighted in a finding aid or publication.</p><h4>The Initial Setup/Admin Journey</h4><p>This map walks through all the steps a person or institution will take when they decide they want to use DocNow to start developing social media collections. <em>We are committed to making the application easy to launch by someone with limited technical abilities.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qXtFsosRIaLbz_wKQkdE1w.jpeg" /></figure><p>When someone decides they want to start collecting social media, they have a lot of options for how to do it. We hope that DocNow will come forward as an easy-to-use, inexpensive, open (both source and community) option with embedded social values to help guide collecting. To that end, the initial set up map is important in that it walks through how to launch an instance with AWS, how to personalize your instance, and how to set global parameters that have impact on the documenter and public user journeys.</p><p>The “Admin” who sets up DocNow may be the head of an archive, or the technical administrator of a library, or just the researchers themselves. We envision the set up having a “wizard” of sorts that walks through the implications (ethical and otherwise) of decisions. After initial set up there will be an admin panel where settings can be changed.</p><h4>Next Steps</h4><p>With these three maps in hand, we will now take the post-it notes and expand on them, defining features and setting them into agile sprints for development. We will incorporate any feedback on the maps as well as solicit feedback through various rounds of development. Thank you to all of our expanding community for being a part of DocNow, we couldn’t do it without you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de2dac3cb34f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/documenting-docnow/mapping-the-journey-a-walk-in-the-shoes-of-our-users-de2dac3cb34f">Mapping the Journey: A walk in the shoes of our users</a> was originally published in <a href="https://medium.com/documenting-docnow">Documenting DocNow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design for Social Good]]></title>
            <link>https://medium.com/documenting-docnow/design-for-social-good-aa5503dcbef2?source=rss-e7d2ff5d60c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa5503dcbef2</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[twitter-data]]></category>
            <category><![CDATA[archive]]></category>
            <category><![CDATA[twitter]]></category>
            <dc:creator><![CDATA[Alexandra DM]]></dc:creator>
            <pubDate>Wed, 12 Oct 2016 21:56:50 GMT</pubDate>
            <atom:updated>2016-10-12T21:56:50.394Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HNUN7ZNwKd6jxvwFhpjaXA.jpeg" /><figcaption>An early map of ethical pinpoints in application development</figcaption></figure><p>When <a href="http://www.docnow.io/">Documenting the Now</a> was building its team, the user experience designer position was created to ensure that the DocNow app would have three principles embedded in the design. The tool must:</p><ul><li>be intuitive and easy to use</li><li>be built <em>with </em>our users, not just <em>for</em> them</li><li>embody our project’s values and ethics</li></ul><p>While most development teams concentrate on the first two UX imperatives, I was particularly excited to join the team to explore how we could design ethically.</p><p><strong>Designing for social good</strong></p><p>Documenting the Now was conceived as an endeavor in building both an ethically-minded community of practice and an application. Taking the methods, tools, and approaches from user experience design, we have developed what I will call <em>ethical experience design</em>, looking critically at potential abuses of the application and determining how we can add design and programming elements that discourage such abuses. If it helps you can think of our approach as loosely informed by <a href="https://en.wikipedia.org/wiki/Value_sensitive_design">value sensitive design</a> in combination with <a href="http://agilemanifesto.org/">agile software development</a>.</p><p>Our first step, using our <a href="http://www.docnow.io/#advisory-board">advisory board</a> as our testing group, was to conduct user interviews by phone. These interviews consisted of ten questions asking what they wanted to do with social media data, ethical concerns they had around using such data, and how they expected the application to work. The interview results were analyzed and synthesized into four general personas for the DocNow team to reference while creating user story maps, which in turn help plan our application development. The personas, which were presented and refined at our <a href="http://www.docnow.io/meetings/stl-2016/">advisory board meeting in St. Louis</a>, include:</p><ul><li>“Pat” the Institutional Archivist</li><li>“Jaylen” the Community Archivist/ Activist Archivist</li><li>“Mamta” the Publishing Researcher</li><li>“Nalo” the Reporter/Blogger</li></ul><p>Each of these personas is a simplified example of a potential user. Each character has their own use cases (the creation of a long term archive, a reproducible data set to reference, quick analyses of daily behaviors, etc.) and concerns with how to properly use and store social media data. Additionally, the concept of a <em>persona non grata</em> was formed at the St. Louis meeting. An example of this would be a law enforcement or surveillance agency wanting to use DocNow. Though we cannot ban anyone from taking this open source code and using it, we can, by representing our values, show that this tool is not meant for such work.</p><p><strong>So how do we represent our values in DocNow?</strong></p><p>We are trying out a variety of methods: through licensing agreements, building in auto-tweet notifications, giving an option to find if you are present in a collection and the ability to opt-out, retention and deletion scheduling, embargoing certain content, and creating labels for how collections should be used. As we develop the application we will test these features with our users to see if they are helping to embed ethical consideration while still allowing the tool to be used quickly and easily. At this phase we are exploring all options, taking big ideas and turning them into actionable programming. We hope that this tool will provide a framework for considering access and use of all social media.</p><p>We will be sharing our user story maps and development plans soon. Please contact us <a href="https://docs.google.com/forms/d/e/1FAIpQLSf3E7PAXPoT-XoedpEy9UCTpDPS8kPj5JkMwpaWbuqVP0bTrQ/viewform">on Slack</a> or <a href="https://twitter.com/documentnow">Twitter</a> to share any thoughts on how we can better design for social good.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa5503dcbef2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/documenting-docnow/design-for-social-good-aa5503dcbef2">Design for Social Good</a> was originally published in <a href="https://medium.com/documenting-docnow">Documenting DocNow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>