<?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 Connie Liu on Medium]]></title>
        <description><![CDATA[Stories by Connie Liu on Medium]]></description>
        <link>https://medium.com/@connie-liu?source=rss-e05059a546f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zDmecCcF5XyKk7hu6wZAMA@2x.jpeg</url>
            <title>Stories by Connie Liu on Medium</title>
            <link>https://medium.com/@connie-liu?source=rss-e05059a546f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:01:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@connie-liu/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[LIFE Camp — Building a Requests System]]></title>
            <link>https://medium.com/cornellh4i/life-camp-building-a-requests-system-a7fa441becc9?source=rss-e05059a546f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7fa441becc9</guid>
            <dc:creator><![CDATA[Connie Liu]]></dc:creator>
            <pubDate>Tue, 09 Nov 2021 06:29:49 GMT</pubDate>
            <atom:updated>2021-11-09T06:29:49.910Z</atom:updated>
            <content:encoded><![CDATA[<h3>LIFE Camp — Building a Requests System</h3><p><strong>Team: 2 Designers (co-designer Alyssa Zhang), 1 PM, 1 TPM, 5 developers<br>Timeline: </strong>Spring 2021</p><h3>Context</h3><p>LIFE Camp is a NY-based nonprofit that aims to use community intervention to make sure youth stay out of the criminal justice system. They have significantly reduced violence rates over the last couple of years.</p><p>Our goal was to create an internal tool for LIFE Camp to sort through and prioritize requests as well as quickly view any trends.</p><h3>User Research</h3><p>LIFE Camp wanted to better understand the needs of the community, especially due to the challenges that have been brought on by COVID-19.</p><p>During our initial calls, they emphasized that they wanted to:</p><ol><li>Conduct surveys about people in the community who request their services</li><li>Analyze the results to understand which resources are necessary for the community</li><li>Allocate the resources and help as needed</li></ol><p>We asked staff to walk us through several user flows where we learned users would be typically requesting:</p><ul><li>To receive help and therapeutic wellness services to overcome trauma</li><li>To encourage their children to stay in school</li><li>To receive financial support for their children</li><li>For support to deal with personal impacts of Covid-19</li></ul><p>Due to the vast amount of requests, they wanted a more sophisticated way to go through the project.</p><h3>The Problem</h3><p>Due to constraints of time, LIFE Camp has difficulty fulfilling the large amount of requests and needs a prioritization system to understand which ones to go to first.</p><h3>Challenges</h3><p>We initially ran into some issues with our user research questions because they were often filled with needless technological jargon- instead we aimed to re-ask them in an intuitive way.</p><p>For example, instead of asking “Do you want the survey to be a one-time form or are multiple submissions allowed?” we asked “Do people request help multiple times?”</p><h3>Design Decisions</h3><h4>User Form</h4><p>With the user form we were unsure whether to go with a single page or a more type-form esque. Because questions did not require as much individual thought and explanation we went with option 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VdgN79k7Vo5z7ByuDuhKsA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*axtW_3EBcyDDL7pNGsi0cQ.png" /></figure><p>We iterated on the form to allow for more LIFE Camp branding and to ensure that the content copy was accurate.</p><h4>Request Cards</h4><p>Because of the vast amount of text we decided to go with option two to allow for concision and easier scanning with the icons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*hzL7qe7WvE-omPdi3Wdjxg.png" /></figure><p>We then added tags to highlight urgency of requests as well as the kind of request for easier scanning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*37YnLNhk8lXWeM_m8jn06Q.png" /></figure><h4>Filters</h4><p>For the filters we decided to go with option two because of the large amounts of data so a sidebar would allow for easier multitasking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*enZ7XVkdFXBMdnAYAgnilg.png" /></figure><p>We simplified constraints further on the sidebar because we realized that the user wouldn’t typically stack filters and it would make more sense to have all the filters present at once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*hwZPneeDTc7jPyRoI4zy9A.png" /></figure><h3>Final Product</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*t6dGw4thTD6cT5xZv7pA9Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QxKf-sPVvnpj4NOj54fJxQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dN4nM8Tb_U5CUP-KUxkGFQ.png" /><figcaption>From left to right — form page, requests page, and a trends page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-ClgPRU_DjySHSaq475Ig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*EB3Xb7lEj39bgY0cFBB9eg.png" /><figcaption>The design system</figcaption></figure><h3>Reflection</h3><p>Overall this project was extremely difficult because we realized as students we live in a tech bubble where we assume clients will understand our technological jargon. Learning to iterate on this took engineering time away and ultimately made it difficult to launch the product in one semester. The engineering team is currently iterating on this project in their off-time and we hope to launch it sometime in 2022.</p><p>As a result Hack4Impact has reassessed our commitment to project sustainability and currently is only pursuing projects on a two semester timescale. Working for nonprofits is highly rewarding, but as students we must be cognizant of our ability to overcommit and make mistakes.</p><p>As always I’m greatly in-debted to my co-designer who contributed to the bulk of this case study. You can read her take <a href="https://www.alyssazhang.com/work/lifecamp">here</a> and view her wonderful portfolio as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7fa441becc9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cornellh4i/life-camp-building-a-requests-system-a7fa441becc9">LIFE Camp — Building a Requests System</a> was originally published in <a href="https://medium.com/cornellh4i">cornellh4i</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflecting on Hack4Impact Design as a National Director]]></title>
            <link>https://medium.com/hack4impact/reflecting-on-hack4impact-design-as-a-national-director-a5ce7d5dbf63?source=rss-e05059a546f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5ce7d5dbf63</guid>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[social-impact]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Connie Liu]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 00:11:59 GMT</pubDate>
            <atom:updated>2021-07-06T00:11:59.834Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NgsmEu0nbdt5RU-LtlazCA.png" /></figure><p>It’s been about a year since I was the National Director of Design! It’s been a journey to collaborate with so many motivated individuals across the country — and I’ve even been able to meet my co-director Tiffany, in real life! Below is a recap of what Design at Hack4Impact nationals has been up to, and where we’re going.</p><h3>First Chapter — Open-source guides + Chapter Mentoring + Website Revamp</h3><p>In the early stages, we first wanted to define what design is — especially in an organization that provides non-profit consultation and not necessarily one where we work on our own time. Drawing experiences from my own first semester as a designer at the Cornell chapter, we collaborated with products to create an integrated timeline for chapters to follow. After interviewing several established chapters and taking our own learnings — we compiled our insights into a comprehensive <a href="https://www.notion.so/Design-Guide-cccacdc8600a4fdbaf42fa6e829690c7">Design Guide</a>! Eventually, this expanded to include tips on recruiting and resources for growing designers!</p><p>We also established direct chapter mentoring — where we created individual channels for new chapters to ask us about proper design practices. Finally, with the amazing help of engineering, was finally able to revamp the Hack4Impact website!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dn-zi1Jn9LiSLfd59kO1_g.png" /><figcaption>Preview of our Design Guide!</figcaption></figure><h3>Second Chapter — Interactive Workshops, Seminars, and Community Building!</h3><p>We did an audit and learned that many designers and chapters at H4I did not know about the resources that Nationals was providing! To provide a more direct impact, we created three sets of workshops focusing on <strong><em>Product design cycle + Figma basics, User Research and Testing,</em></strong> and <strong><em>Accessibility</em></strong><em>!</em> You can view them <a href="https://www.notion.so/Workshop-1-Design-Basics-Figma-8a504b6982b244019056866d616dbc09">here</a>! We got great reviews from the workshop series, and hope to continue them in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Kplq2CSOHkZ4GGni" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v0ME0R8zZshYh6Pk" /><figcaption>Workshop pic and results from the workshop!</figcaption></figure><p>In addition to workshops, we wanted to make Hack4Impact design feel like a community. We held our first-ever design mixer over zoom, and invited Kat Zhou (a designer at IBM and now Spotify) to teach a seminar on frameworks to design ethically!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ConfLgznIytaeCIG" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*zcl_Ec7t6PjEPHlQ" /><figcaption>Our meeting with Kat Zhou to learn about a design ethics framework + marketing for the event!</figcaption></figure><p>However, as we’ve progressed into a more in-person era, it’s been hard to keep up operations and engagement virtually. Nationals will have to do more brainstorming on how we can support design culture at H4I perhaps asynchronously. I’m excited for what’s to come and can’t wait to see how the design community in H4I will grow closer and advance through the years!</p><h3>Where next?</h3><p>It’s been a wild journey since then, and I’m happy to announce that the next Director of Design for Nationals will be <a href="https://www.chaeeunpark.com/">Chaeeun Park</a>! Chaeeun is a dear friend of mine who helped me with creating Cornell Hack4Impact’s design team and we’ve gone on to do the Civic Digital Fellowship together in the fall! They’ll be auditing current design practices at various design chapters and designing more customized resources to help burgeoning chapters that don’t have a pre-existing design culture at their school — I can’t wait to see what’s next!</p><h3>Bonus!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cTZQLPubg5pFoawM" /></figure><p>I also happened to pass by Tiffany’s school and got to meet her IRL! Super grateful for the opportunity to shape H4I design in the past year to be able to meet so many interesting people across the country!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5ce7d5dbf63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hack4impact/reflecting-on-hack4impact-design-as-a-national-director-a5ce7d5dbf63">Reflecting on Hack4Impact Design as a National Director</a> was originally published in <a href="https://medium.com/hack4impact">Hack4Impact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Visualization Platform for Prison Complaints — a Design Case Study]]></title>
            <link>https://medium.com/cornellh4i/creating-a-visualization-platform-for-prison-complaints-a-design-case-study-55e25e2d3277?source=rss-e05059a546f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/55e25e2d3277</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-for-social-change]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[hack4impact]]></category>
            <dc:creator><![CDATA[Connie Liu]]></dc:creator>
            <pubDate>Tue, 12 Jan 2021 23:48:26 GMT</pubDate>
            <atom:updated>2021-10-15T20:16:09.683Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VaPQ0ZDBraTKUd5w.png" /></figure><h3>Creating a Visualization Platform for Prison Complaints — a Design Case Study</h3><p><strong>Team: </strong><a href="http://cornellh4i.org/"><strong><em>Cornell Hack4Impact</em></strong></a><strong><em> (Designers: </em></strong><em>Connie &amp; Ishika</em><strong><em>, Developers: </em></strong><em>Shefali, Steve, Anika, Jiwoo, Amy</em><strong><em>, Tech Lead: </em></strong><em>Anusha</em><strong><em>, Project Manager: </em></strong><em>Priya</em><strong><em>)</em><br>Timeline: </strong>Fall 2020 (6 weeks Design, 10 weeks overall)</p><h3>The Problem</h3><p>There is a huge lack of transparency about conditions inside prisons and three supreme court cases (Branzburg v. Hayes, Pell v. Procunier, and Saxby v. Washington Post Co.) make it difficult for journalists to access these prisons.</p><p>Currently, the <a href="https://www.correctionalassociation.org/">Correctional Association of New York</a> (CANY) is the only organization with access to that data. CANY wants to surface the data and use it to form an argument as to why it&#39;s important to increase transparency about conditions inside prisons.</p><h3>The Solution</h3><p>We created a dynamic data visualization platform for CANY to easily create graphs that use real-time prison complaint data.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FVwp6bs0hroM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DVwp6bs0hroM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FVwp6bs0hroM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a6a0659c94498184b4a1bfa5ccd05b51/href">https://medium.com/media/a6a0659c94498184b4a1bfa5ccd05b51/href</a></iframe><h3>Competitive Analysis</h3><p>First, we did market research on similar platforms that involved editing custom visuals. What we noticed from each of these is:</p><ul><li>Not all options are immediately available, and options are broken off by <strong>distinct aspects</strong> of the graph, artboard, or use-case</li><li>Shifting from action to action should require a <strong>one-click</strong> transition</li><li>Most of the detailed options are concentrated on the <strong>sidebar</strong> and rarely on the top bar</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EmB85w_ky8GHZn8Q.png" /></figure><h3>Information Architecture</h3><p>Based on the initial prompt, we went through several rounds of the information architecture. We chose to iterate on information architecture first paired with low-fidelity sketches because we didn’t want to create the mid-fidelity until all the details were concretely defined.</p><h3>Iteration 1</h3><p>My initial mental model was that all kinds of graphs with different x and y axis’s were possible.</p><p>However, after talking with the client, we learned that <strong>they were mainly interested in complaints as the dependent variable.</strong></p><p>From our meeting with the client, we also learned they wanted features such as a way to save the graph, undo and redo, and reset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*iPiBP9HHgL4i8lgN.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*hX4VQFCGOuYLnACS.png" /></figure><h3>Iteration 2</h3><p>In the second iteration, complaints were pre-assigned as the y axis. We had it so the user could limit the data set from both the x and y.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/0*rwbJ4xPAwC5HnEjn.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LPhENykqIvHg_RH4.png" /></figure><p>In the next user testing review with the client, we focused on asking questions to define what the client envisioned the y and x axis being, and what actions they wanted to take in customizing the data.</p><h3>User Testing</h3><p>During our meeting, we tested our prototypes with the client, two CANY employees, and two non-CANY affiliated students for both <strong>functionality</strong> and <strong>visual design.</strong> As a side note, the flows below have been abridged.</p><h4>Visual Feedback</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H7pxod50INekveaj.png" /></figure><p>We had an array of options visually but settled on two final options to test because they either echoed previous design patterns (eg google sheets) or seemed the clearest based on internal team feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Pe9nrR3_wMN8fDwG.png" /></figure><p>✓ Nice visually and usable after users played around with controls<br>✗ Unclear at first the correlation between tabs and sidebar content, the active color placement in visualization settings was unnoticed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ToyJSVDsZonWLjQO.png" /></figure><p>✓ Able to quickly toggle between different actions, similar to Google Sheets UI<br>✓ Clear relation between the settings summary, edit summary, and the task-action<br>✗ Unclear the settings co-related to the filters above, needs to be fixed visually</p><p>Ultimately, user testing revealed users preferred Option B. We decided to freshen up the UI and optimized the spacing. We also added more visual hierarchy to the sidebar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TwYzhVr-oC-_ek6S.png" /></figure><h4>Function Feedback</h4><p>We tested for the usefulness of our product by asking people at CANY to walk us through how they would use our tool to construct visualizations they would use from day-to-day.</p><p>We discovered that it was hard to distinguish the difference in action between defining complaints (third option) and limiting the data-set (second option). Both were limiting the data set <em>and</em> defining the x-axis at the same time, but they were separated as if they were performing two separate actions.</p><h4>Figuring out the 3 Core Actions</h4><p>After talking with the client some more to figure out the three core actions, we learned that the y axis would always be the number of complaints and that would never change. That meant the only axis to be altered would be the <strong>x axis.</strong> The client agreed they still wanted to limit the data set and change the graph type — which meant an easy fix would be to replace changing <strong>Complaint Type</strong> to <strong>Setting X Axis.</strong></p><h3>Final Iteration</h3><p>The new information architecture and design reflected the changes in the three actions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lLu4p3k2zRJtYjP7.png" /></figure><p>We also realized that the user would need a way to keep track of the multiple limits placed under the ‘limit data set’ option which we added visually via a sidebar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*buYUkKj-17g7wSco.png" /></figure><p>We also learned that the dataset was <strong>incomplete</strong> and there would be entries without demographic data. We added the explanation via a popup and placed it under the ‘limit data set’ sidebar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1S0XxtUFRyT9a_3b.png" /></figure><h3>Design System</h3><p>The final visual design system was heavily based off of CANY’s existing brand to maintain consistency, even though it was an internal tool. That meant using brand fonts, Oswald and Helvetica, as well as brand colors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1QUq2jQfPRiPQu4C.png" /></figure><h3>Results</h3><p>View a walkthrough the final iteration below!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FVwp6bs0hroM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DVwp6bs0hroM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FVwp6bs0hroM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a6a0659c94498184b4a1bfa5ccd05b51/href">https://medium.com/media/a6a0659c94498184b4a1bfa5ccd05b51/href</a></iframe><p>At our end-of-semester showcase, we demo’d the project to our client and we were met with positive reviews. A CANY employee expressed his gratitude and said that our tool would make the data visualization process much faster and efficient for them, and they were so excited to use it.</p><p>Because the pandemic has been stressful for everyone, our team is still working on developing the tool but it will be deployed in the spring.</p><h3>Reflections</h3><p>This semester was Hack4Impact’s first time designing before the beginning of development, and also with pairs of designers. Here are some key lessons learned —</p><ul><li><strong>The user knows best</strong> — there were times where our team couldn’t make a design decision, after we got feedback from users we were able to make clear, informed decisions on which avenue to pursue.</li><li><strong>Walkthrough the user journey</strong> — if we had constructed a user journey earlier we would’ve realized our mental model didn’t line up with our client’s. We did do it verbally, but a more concrete model would’ve been more effective.</li></ul><p>In the end, designing wouldn’t have been possible without our wonderful developers and project managers and we can’t wait to see what will happen in the upcoming semester!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h_Zve_1O5Teh3QZej3Evpw.png" /><figcaption>Handoff with CANY!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55e25e2d3277" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cornellh4i/creating-a-visualization-platform-for-prison-complaints-a-design-case-study-55e25e2d3277">Creating a Visualization Platform for Prison Complaints — a Design Case Study</a> was originally published in <a href="https://medium.com/cornellh4i">cornellh4i</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Increasing the Organization and Scope of the p5.js Showcase]]></title>
            <link>https://medium.com/processing-foundation/increasing-the-organization-and-scope-of-the-p5-js-showcase-7193ef558c5a?source=rss-e05059a546f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/7193ef558c5a</guid>
            <category><![CDATA[processing-foundation]]></category>
            <category><![CDATA[creative-coding]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[p5js]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <dc:creator><![CDATA[Connie Liu]]></dc:creator>
            <pubDate>Mon, 14 Sep 2020 13:16:01 GMT</pubDate>
            <atom:updated>2020-10-22T10:47:41.412Z</atom:updated>
            <content:encoded><![CDATA[<h4>by Connie Liu, Google Summer of Code 2020</h4><p>mentored by by <a href="https://jk-lee.com/">Joey Lee</a> and <a href="http://1023.io/">Yining Shi</a></p><p><em>2020 marks the Processing Foundation’s ninth year participating in Google Summer of Code, where we work with students on open-source projects that range from software development to community outreach. We’ve been posting articles written by some of the GSoC students, explaining their projects in detail, which you can read </em><a href="https://medium.com/processing-foundation/pfgsoc/home"><em>here</em></a><em>. The series will conclude with a wrap-up post of all the work done by this year’s cohort.</em></p><figure><img alt="A gif of the 2020 showcase page that transitions through the data visualizations to the actual gallery page." src="https://cdn-images-1.medium.com/max/800/1*uxgj3Fg7BaG-ZMO_OF9awQ.gif" /><figcaption>Connie Liu worked on the p5.js Showcase, adding tags and implementing translations for Spanish and Chinese, among other things. “I’m an upcoming sophomore at Cornell University, pursuing a major in Information Science (with a concentration in User Experience and Interactive Technologies) and a minor in Computer Science. I hope to one day be a creative technologist. p5.js was what first opened my eyes to the world of creative coding. It’s my first time contributing to open source with Google Summer of Code and I’m beyond excited to contribute to the p5.js Showcase. <a href="https://connieliu0.github.io/#/">Portfolio Website </a>and <a href="https://www.linkedin.com/in/connieliu23/">Linkedin</a>.”</figcaption></figure><p>When I learned I was selected to be a GSoC student for p5.js I was absolutely ecstatic. p5.js has always held a special part of my heart. Ever since discovering it in junior year of high school, it’s always reminded me that art and code can intersect, that there is a space in the world for interdisciplinary creativity.</p><figure><img alt="A screenshot of the Showcase with different filters applied, showing three different works" src="https://cdn-images-1.medium.com/max/1024/1*yc0gfcfPLSQdxsORNQZMKA.png" /><figcaption>The p5.js Showcase can now be sorted by tags.</figcaption></figure><h3>The Development Process</h3><p>Initially, I was going to integrate the Showcase into the original codebase of the p5.js website. However, after a month of auditing and trying different solutions (and contacting many people in the community to make sense of it), I came to the conclusion that for what I wanted to do—which was autogenerating 50 projects and having a filter for each—it would be very difficult within the current Handlebars framework. As a result, I planned a new proposal to use a React Framework in which I would be able to autogenerate different UI using content from the JSON files.</p><h4>i18next</h4><p>Figuring out how to integrate i18next into the React framework was one of the biggest challenges I faced. It took three days of rereading the same docs over and over again, and I still could not figure out how translations worked with nested JSON arrays. After stumbling onto a GitHub thread from a couple of years ago, I was finally able to figure out the syntax.</p><p>Because of the problems I had with figuring out the previous tech stack of the website and with creating the new one, as part of my project I wrote up <a href="https://github.com/connieliu0/p5.js-showcase/blob/master/showcase2020_documentation.md">brief documentation</a><a href="https://github.com/connieliu0/p5.js-showcase/blob/master/showcase2020_documentation.md"> here</a> about how i18next worked with the JSON files.</p><h4>Designing the Showcase and Data Visualizations</h4><p>Another challenge was figuring out what data visualizations I wanted in the beginning. In my original iteration, I focused on splitting it up into three different categories. However, that ruined the linear narrative flow and all the different visualizations felt very separate from one another. At one point, I just had a series of graphs that were auto-generated by the Google Form. I also had planned to use d3.js, but my mentors encouraged me to change my approach to different JS libraries that were more tailored towards the graph types I was planning for.</p><figure><img alt="Three slides of different pages in the Showcase, one each for Community, Experience, and Projects" src="https://cdn-images-1.medium.com/max/1024/1*rlI8tMVz85oEf4UXajJblQ.png" /><figcaption>First Iteration of the visualizations, there are three different sections with tabs.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rIEIY4HJeHUbrokg2yiAxg.png" /><figcaption>Final iterations of the visualizations, the top is a map, the middle are charts, and the last is a word visualizer.</figcaption></figure><p>The one advice my mentor told me that really stuck with me was to design the visualizations for a story. In my final iteration, I made sure that the visualizations acted as part of a narrative, and incorporated it with a sentence that explained the significance of the visuals.</p><p>As a result, I was able to steer away from creating a generic graph with a title and description.</p><h4>Organizing the Submissions</h4><p>Another thing that changed this year was that I reached out to many different institutions and people to try to increase the number of submissions. As a result, the Showcase grew to 60 submissions! In order to make it easier for people to find what they were interested in among all the submissions, I split them up into 11 different categories. I also put tags on the bottom of each entry to give more context to the technologies used.</p><p>In order to get more people to submit and also check out the Showcase, I created some marketing graphics. It was a challenge for me, as someone who hadn’t created graphic design in a while, but it was worth it and I learned a lot.</p><figure><img alt="3 different flyers asking for submissions. The font is bright pink on white background, with images and illustrative patterns" src="https://cdn-images-1.medium.com/max/1024/1*8B5_4EWp_GVY6xSMGw5YVw.png" /><figcaption>Flyers I made for the Showcase. The Showcase received 60 submissions!</figcaption></figure><h3>The Final Product</h3><figure><img alt="The homepage is white with two shades of pink font. It says “Welcome to the p5.js 2020 Showcase!”" src="https://cdn-images-1.medium.com/max/1024/1*-c9MsT2JVfWpYU1jwN9tPw.png" /><figcaption>The final p5.js Showcase Welcome Page</figcaption></figure><p>In the final p5.js Showcase I was able to improve it in the following ways:</p><ul><li>Added translation support and implemented translations for Spanish and Chinese</li><li>Implemented data visualizations with Leaflet.js, p5.js, and Chart.js</li><li>Added filters for various project categories</li><li>Added tool tags for various niche libraries and functions used in p5.js</li><li>Created documentation for translation contributions</li></ul><h3>Conclusions and the Future</h3><p>Currently, I am the maintainer of the p5.js 2020 Showcase repo and it exists within <a href="https://github.com/connieliu0">my GitHub account</a>. The hope is that next summer’s GSoC student can take over as the maintainer, or work to expand the Showcase into an official system that can be maintained by a team of people. Another goal is to make sure that the Showcase is accessible to everyone as there wasn’t enough time to make sure it complied with <a href="https://www.a11yproject.com/checklist/">a11y guidelines</a>.</p><p>I hope that the Showcase can be expanded every year or two as a celebration of people’s work. I truly believe it’s a unique opportunity to bring the p5.js community together to recognize everyone’s work.</p><h4>Support</h4><p>Please tag me @connieliu0 on the p5.js Showcase <a href="https://github.com/connieliu0/p5.js-showcase">GitHub repo</a> if you would like to add translations or propose a new issue on the current repository. Feel free to email me at <a href="/service/mailto:cliu55567@gmail.com">cliu55567@gmail.com</a> for any other matters concerning the Showcase!</p><h4>Acknowledgments</h4><p>I am so grateful to the Processing Foundation for providing me with this opportunity to expand and curate a new p5.js Showcase. This summer’s project was the perfect blend of everything I loved: community engagement, design, and the creative implementation of technology.</p><p>Furthermore, I’d like to extend my deepest thanks to my mentors, Joey Lee and Yining Shi for helping me throughout the whole process and providing advice for everything from curation to career. There are many others I’d also like to thank, click <a href="https://github.com/processing/p5.js/blob/main/contributor_docs/project_wrapups/connieliu_gsoc_2020.md#acknowledgements">here</a> for the full list!</p><p>All in all, it was a wonderful summer, and I’m so excited to see how p5.js grows in the future!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7193ef558c5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/processing-foundation/increasing-the-organization-and-scope-of-the-p5-js-showcase-7193ef558c5a">Increasing the Organization and Scope of the p5.js Showcase</a> was originally published in <a href="https://medium.com/processing-foundation">Processing Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding your own flocks — a Twitter case study]]></title>
            <link>https://uxdesign.cc/finding-your-own-nests-a-twitter-case-study-970d2aa4efd8?source=rss-e05059a546f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/970d2aa4efd8</guid>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Connie Liu]]></dc:creator>
            <pubDate>Mon, 15 Jun 2020 21:32:08 GMT</pubDate>
            <atom:updated>2021-02-27T04:46:53.906Z</atom:updated>
            <content:encoded><![CDATA[<h3>Finding your own flocks — a Twitter case study</h3><figure><img alt="Three iphone screens, left is the home page for groups, center is the details for groups, and right is how to search groups" src="https://cdn-images-1.medium.com/max/1024/1*ErSHEovFH3QDuzN4RGxDGg.png" /></figure><p>Unlike Instagram and Facebook, Twitter is a social media platform where interacting mostly means <em>connecting </em>and in many cases with strangers. There are so many different forms of connection on Twitter from designers networking to fandoms raving about the latest song.</p><p>But a huge problem with the platform happens when your audience is a mix of these people with different interests. Who do you post to? Is it a good idea to post about the newest Harry Styles album if your audience is mostly professionals?</p><blockquote><em>Instead of being afraid to tweet because of conflicting audiences, is there a better solution?</em></blockquote><p>To figure out how to solve this problem, I knew I had to do some research.</p><h3>The Daily Life of a Tweeter</h3><p>For my user interviews, I asked about how people browsed, found content, and interacted on Twitter. Here’s a summary of the insights I found:</p><figure><img alt="Sorts insights from interviews into four categories- community, time, content, and posting" src="https://cdn-images-1.medium.com/max/1024/1*r8zgc0CUj_iWkWc5EyeGkw.png" /><figcaption>Insights from User Interviews</figcaption></figure><p>The research revealed that users post on Twitter for multiple people — friends, network contacts, and fandoms. They’re constrained by factors like <strong>time</strong> and <strong>image</strong> in their usage.</p><p>Because Twitter has a sprawling user base, I made user personas to better understand the audience and different use cases.</p><figure><img alt="User personas of two types of people who would use Twitter" src="https://cdn-images-1.medium.com/max/1024/1*nyUOh4WF4BcaDhMD4hJpHA.png" /></figure><h3>The Problem Statement</h3><p>When people use Twitter, they find it difficult to be able to tweet/reply what they want because:</p><ol><li>All their tweets/replies are public and they don’t want their entire audience to see them</li><li>They don’t want to sound too unprofessional/uninformed</li><li>They have niche interests where their tweets would only apply to a certain group of people</li></ol><p>Also, users already seem to want a space of their own. In many fandoms, there are “group chats” where users can interact with others interested in the same things in a private space.</p><figure><img alt="A screenshot of a tweet showing how fandoms make groupchats" src="https://cdn-images-1.medium.com/max/1024/1*E-J4Br4lIvD8FnCyqTUEfg.png" /></figure><p>Although it’s a great way to get content and to meet people with similar interests, my user research found that these group chats could get awkward and often dissolve quickly.</p><h3>Introducing Twitter Groups (or perhaps… Flocks)</h3><p>Users wanted a private space, one that they could define in terms of content and visibility. Introducing… Twitter Groups!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-hz8bhJ32pM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-hz8bhJ32pM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-hz8bhJ32pM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e4e82f2135e5a4fb14126c15afd07200/href">https://medium.com/media/e4e82f2135e5a4fb14126c15afd07200/href</a></iframe><h3>How Did I Get There?</h3><h4>A Brainstorming Session</h4><figure><img alt="Three people stand in front of a wall full of brainstormed sticky notes" src="https://cdn-images-1.medium.com/max/666/0*3id74fAFct_gFTCr" /></figure><p>Brainstorming with a couple of pals revealed some problem spaces to tackle- specifically how do we increase <strong>privacy</strong> and <strong>engagement</strong> at the same time?</p><p>Out of many solutions, I narrowed it down to three…</p><figure><img alt="Sketch of what a feature called Twitter private conversations would look like" src="https://cdn-images-1.medium.com/max/1024/0*WPoa-J9ohgzInSOT" /></figure><p><strong>Twitter private conversations</strong> would allow replies to be only seen to the poster, but it lacked any feasibility for community engagement. After all, we tweet because we want to be <strong>heard.</strong></p><figure><img alt="Sketch of what the feature Twitter shower thoughts would look like" src="https://cdn-images-1.medium.com/max/1024/0*tMHqepGVvfX6R3-o" /></figure><p><strong>Twitter shower thoughts</strong> would allow users to post whatever they wanted to a select number of people, almost like a private Twitter integrated into a public one. However, that would limit posts to be mostly about the user&#39;s life. What about a space for other topics?</p><figure><img alt="Sketch of what Twitter Groups feature would look like" src="https://cdn-images-1.medium.com/max/1024/1*pULiIutO0U2HycFsyDk-Eg.png" /></figure><p><strong>Twitter groups</strong> would allow users to post whatever they wanted, but also provided the perfect degree of customizability as to who would see the post. The user could use groups to rant to their close friends but also post the latest fandom news with fellow internet users at the same time.</p><h3>Figuring Out Where the Pieces Fit</h3><h4>Entry-points</h4><figure><img alt="Different options for the entry point" src="https://cdn-images-1.medium.com/max/1024/1*uvPQ6gznTnDy6ObRfP9T_A.png" /></figure><p>Ultimately I decided on option D because user research indicated that users were less inclined to use features that were hidden in the sidebar (such as Lists). Also, options B and C were ruled out because that was how Twitter currently integrated Lists and Special News Features into the feed.</p><h4>How do we view groups?</h4><figure><img alt="Different options for viewing groups" src="https://cdn-images-1.medium.com/max/1024/1*KppuEWga5NdtsVmZXkta8Q.png" /></figure><p>I ultimately settled on option D. User feedback indicated that it was important to <strong>quickly </strong>and <strong>easily </strong>navigate between each group’s content. They didn’t want another cluttered feed like the home page.</p><p>This posed another problem, how do we still ensure the user can view all the content in a single stream? Users indicated they still wanted an option to see an <strong>unfiltered view.</strong></p><h4>Integrating an Unfiltered View</h4><figure><img alt="Different options for navigating an unfiltered view" src="https://cdn-images-1.medium.com/max/1024/1*Yubf8UBJmgyGlb6otuMeQw.png" /></figure><p>Although option A was similar to how Twitter integrated Lists onto the homepage, I went with option B in the end because the interaction was more seamless while swiping would provide a break in the interaction.</p><p>Also, since the default Twitter feed is organized by highlights, the user would implicitly understand that the Twitter groups feed is organized the same way.</p><h4>How do we find these groups?</h4><h4>Iteration 1: Integrating Your Groups, Explore, and Create</h4><figure><img alt="First iteration of integrating your groups, explore, and create" src="https://cdn-images-1.medium.com/max/1024/1*xXE30X0f93BJ3evoXKfwhQ.png" /><figcaption>My Initial Iterations</figcaption></figure><p>Initially I had the idea of having <em>Your Groups</em>, <em>Explore </em>and <em>Create</em> all be accessed through the same tab system, indicating they had equal importance. However, through user research I learned that:</p><ul><li>Users will only use <em>Explore</em> on Twitter once or twice in the beginning when setting up the groups they wanted to follow.</li><li>Users would use <em>Create </em>once, twice, or even never, meaning it didn’t need to be as accessible as viewing the feed.</li></ul><h4>Iteration 2: Integrating Explore and Search</h4><figure><img alt="Second iteration of putting together explore and search" src="https://cdn-images-1.medium.com/max/1024/1*h0bIIq3tPYnsp_vCHUFLdw.png" /><figcaption>My Second Iteration</figcaption></figure><p>For a while, I was stuck on trying to integrate both searching <strong>for all groups on Twitter </strong>(Explore) and searching <strong>within your own groups </strong>(Search)<strong>. </strong>After user research, I learned that my explorations in my second iteration weren’t enough because:</p><ul><li>The difference in function between <em>Your Groups</em>, <em>Search</em>, and <em>Explore</em> was <strong>confusing</strong> from first glance</li><li>If users really wanted to look for groups <strong>ALL </strong>over Twitter, they always went to the bottom bar when prompted</li><li>Users wanted a way to access <strong>a list of groups they were currently in </strong>instead of solely relying on the carousel</li></ul><h4>Iteration 3: The Final Solution</h4><figure><img alt="The final solution for searching in groups" src="https://cdn-images-1.medium.com/max/1024/1*nNBASZ9LSux4rS0L8UDf2Q.png" /><figcaption>Final Iteration</figcaption></figure><p>For my final solution I simplified <em>exploring</em> and <em>searching</em> into one action.</p><ul><li>Because users would only have one or two groups under a keyword, it allowed space for an option to explore groups from the search button on the bottom</li><li>The empty state would make room for a list of all groups a user was in, which made sense because that was when a user would want to access a specific group anyways</li></ul><h4>What makes these groups so different anyways?</h4><figure><img alt="How to differentiate groups and profiles visually" src="https://cdn-images-1.medium.com/max/1024/1*bTp6jDqMJazHMZC1XHcUzQ.png" /></figure><p>User testing showed that leaving the presentation of groups to be the same as a user profile proved to be very confusing, ruling out option A. Option C would make viewing the follower count difficult if the cover photo was a detailed photo.</p><p>In the end, I chose option B, however there was still a major problem- <strong>users didn’t know the difference between following and joining at first glance.</strong></p><h4>What’s the difference between joining and following?</h4><p>The point of joining and following was to allow people the option of passively following a group and to also allow for more control over posting privileges. Only people who joined a group would be allowed to post and follow at the same time. This would allow more customization in the usage of groups.</p><figure><img alt="Using the bottom up modal to show the difference between joining and following" src="https://cdn-images-1.medium.com/max/1024/1*3ZNR0HUnbO1wG5P9J2NgFw.png" /></figure><p>To explain the difference I took inspiration from how Twitter currently explains its features, through a bottom pop-up modal.</p><h3>Bringing Back the Twitter Aesthetic</h3><p>Understanding how Twitter currently designed various functions in their system was important in terms of <strong>consistency</strong> and helped me decide which design decision to pursue for creating groups.</p><h4>Forming the Flocks… I Mean Groups</h4><p>Although the content requirements for this feature were straight-forward, I went through several iterations to make it match Twitter’s design system and increase usability.</p><figure><img alt="Final iteration of how to create a group" src="https://cdn-images-1.medium.com/max/1024/1*V4Mojyw3dhOs8EMc16f5PA.png" /></figure><p>In my original version, it was difficult for the user to know where to click to input their information. Also, the invite was a scroll within a scroll which would add poor usability.</p><p>I then split it into three steps and provided context to each so the user felt more guided in the group creation process.</p><h4>Representing Groups in Unfiltered Feed View</h4><figure><img alt="The different options to show which group the user is posting from" src="https://cdn-images-1.medium.com/max/1024/1*K1FlVvFd4E-uugCYLYLK_A.png" /></figure><p>Although it was minor, I went with option A because option B made it seem like the @ referred to the <strong>username </strong>of the tweeter rather than the <strong>group.</strong> As for option C, the solid triangle wasn’t visually seen anywhere in Twitter, and I wanted to keep consistency.</p><h4><strong>Create Iconography</strong></h4><figure><img alt="How to visually show adding a group" src="https://cdn-images-1.medium.com/max/1024/1*UUlgEyhBRS_TG2zwTeID3A.png" /></figure><p>Option A is the most clear that it’s a create group button, but option B keeps more in line with Twitter’s current aesthetic (symbol and shapes). Option C is a simplified version but sacrifices any context. I ultimately went with option B.</p><h3>Final Flow</h3><h4>Browsing Groups</h4><figure><img alt="Final gif for browsing groups" src="https://cdn-images-1.medium.com/max/265/1*8kBAZhhYDukEeJty_HHnRA.gif" /></figure><h4>Searching for Groups</h4><figure><img alt="Final gif of searching for a group" src="https://cdn-images-1.medium.com/max/266/1*Yc0_H0K_ze9X4ubwmPmL7Q.gif" /></figure><h4>Creating Groups</h4><figure><img alt="Final gif of creating a group" src="https://cdn-images-1.medium.com/max/266/1*q5FlbXFPSNRZIlbW9duvnQ.gif" /></figure><h3>Conclusion</h3><p>I didn’t realize it at first, but users don’t need a lot of followers to experience this problem. Recently, I started tweeting more and I realized that I had professionals following me and underclassmen from high school and close friends. I didn’t know what to post and so I didn’t post at all.</p><p>Ultimately, if there were more time I would look into how users interact with others within groups. Besides retweets and posts, what else would make Twitter Groups different from any old group chat or shared account? Would it be possible to integrate discussion boards, polls, or collaborations?</p><p>In the end, Twitter Groups is a solution that at the very least makes <strong>Twitter a comfortable space for everyone.</strong></p><p><em>This was my first full-length case-study and boy it was wild. Shoutout to Cornell AppDev’s Introduction to Digital Product Design Class and my wonderful TA Femi for pushing me to test out all my ideas. I’m a rising sophomore at Cornell and I’d love to connect! If you’re interested in learning more about me find me at </em><a href="https://connieliu0.github.io/#/"><em>connieliu0.github.io</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/76/0*3FncAlJj-a8D0q8o" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://medium.com/uxmpretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=970d2aa4efd8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/finding-your-own-nests-a-twitter-case-study-970d2aa4efd8">Finding your own flocks — a Twitter case study</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Heart-Tube-Heart: Designing a “Connector” for Storytelling]]></title>
            <link>https://connie-liu.medium.com/heart-tube-heart-designing-a-connector-for-storytelling-d49b1767a0b3?source=rss-e05059a546f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d49b1767a0b3</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[explorative-design]]></category>
            <category><![CDATA[environmental-design]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Connie Liu]]></dc:creator>
            <pubDate>Fri, 29 May 2020 02:58:27 GMT</pubDate>
            <atom:updated>2020-05-29T02:58:27.681Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSJxtUP-6CJlrzKN58pZLQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mb_qrZFfsuCn4pv-I7jzCg.jpeg" /><figcaption>Our Final Solution: Heart-Tube-Heart</figcaption></figure><p>How often do we find ourselves talking to complete strangers? Not to ask for directions, but just to get a glimpse into someone else’s world?</p><p>The short answer is: not often. It isn’t done because it isn’t the cultural norm, and is outside of people’s usual comfort zones.</p><p>Our team consisting of Xin Wen (DEA ‘20), Mikail Masqood (Arch ‘21), Sheri Guo (InfoSci ‘22), Joseph Yoon (ChemE ‘23), Connie Liu (InfoSci ‘23), and Benji Magin (Arch ’21)<em> </em>decided to tackle this problem- how would we make spontaneous interaction more comfortable and allow people to connect with one another?</p><h3>The Problem: Invisible Social Barriers</h3><p>Within the broad topic of “diversity and inclusion”, our team chose to focus on the topic of connection building. University students often want to broaden their perspectives through meeting and interacting with others who might not be the same as them.</p><p>However, connections often cannot be formed due to unspoken, invisible social barriers. These barriers can come in all forms, such as social anxiety, uncertainty about intentions, assumptions based on appearance, worries about perception, etc. We wanted to provide an experience to dissolve the invisible barriers and allow people to be able to connect with each other without being held back by preconceptions or social anxiety.</p><h3>Initial Research</h3><p>Our team conducted both in-person interviews and literature reviews to dive deeper into how people build connections with one another. We also examined case studies of personal experiences that allow people to connect and bond.</p><p>We found that:</p><ul><li>People tend to bond over commonalities, such as shared interests and experiences.</li><li>People can bond over catalysts, or “forced” or obligated experience, such as being assigned to do the same task in a group.</li><li>A sense of urgency could be detrimental to forming new relationships. If people are in a rush, they may not feel as inclined to connect.</li><li>Pre-formed social networks, such as pre-existing cliques or friend groups, can be detrimental to forming new relationships.</li></ul><p>Based on these findings, we wanted to create a catalyst, or an experiential installation, in this case, to facilitate interaction between people without rushing them.</p><h3>Iteration 1: Thin Screens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uPL0T8uQG7kwMSHjhohk4Q.png" /></figure><p>In our first iteration, Thin Screens, we wanted to use projectors on two screens on respective sides of a semi-enclosed booth to create a focused experience between two people. The projector would project questions for a user to answer as well as the other user’s answers in real-time. After the users are done with answering the series of questions, they have the option to choose to lift the screens in the middle and see each other.</p><p>We received feedback from a panel of professors who commented on potential problems with this design. The design highly emphasized the importance of the identity (face and physical appearance) as the final objective. Instead of encouraging a conversational flow, the booth setting resembles more of a “confessional” style of communication, which may induce stress and deter participants from being honest and comfortable with the experience. It can also be hard to leave the situation without making the other participant confused or bothered.</p><h3>Iteration 2: Resonance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iZFaJxCHcJjWpzxrlWmUgg.png" /></figure><p>We wanted to keep the physical interactivity aspect and the initial anonymity of our last prototype, but without the potential trapped feeling of a booth setting. Inspired by playground pipes, Resonance is designed to be a tubular installation for Medium’s RAW Expo event in Milstein, through which people can talk to other people directly through the pipes, with partitions that provide some anonymity. For this design, we received feedback from Professor Denise Ramzy during our mid-semester review. One thing that she pointed out was that there’s no activation point or prompt when two people arrive at the tube, which can lead to awkward moments of uncertainty. It is also hard to know when someone else is on the other end of the tube without some type of indicator. Finally, it is also unclear when an interaction is considered over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xWsrKyWRYOVtNM7paQAoCA.png" /><figcaption>Graphic Summarizing Iteration 1 and Iteration 2</figcaption></figure><h3>Final Design: Heart-Tube-Heart</h3><p>For our final design, we took all previous feedback into consideration and created<strong> Heart-Tube-Heart</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mb_qrZFfsuCn4pv-I7jzCg.jpeg" /></figure><p>Similar to Resonance, Heart-Tube-Heart is an installation intended to be located on the Milstein Hall walkway at Cornell University for Medium RAW Expo. The installation consists of multiple sets of height-adjustable PVC pipes that loops over the walkway, which eliminates the closed-off setting of a booth. Each end of the pipes consists of a mouthpiece and earpiece that allows users to listen and talk without having to move their head back and forth from one pipe opening.</p><p>On each end of the pipe, there is an additional panel with 5 buttons, with each button corresponding to a prompt displayed on a sign attached. The sign also notes that the conversation is finished after answering one prompt unless the user wishes to answer more. This addresses how the interaction should start and end, eliminating awkward moments of uncertainty. People can interact with each other through the pipe without being able to directly see each other, removing any social or visual preconceptions.</p><p>The pipes are also intended for one-on-one interactions, to remove the sense of pre-formed social networks. People are able to press buttons that correspond to various questions that serve as conversation starters, facilitating storytelling and helping people to quickly build deeper connections with others.</p><h4>Steps for Using Heart-Tube-Heart:</h4><ol><li>Choose a specific topic from the sign that is most interesting to you and press the corresponding button.</li><li>Button begins to blink on the other end. A curious person on the other end presses it.</li><li>Share your experiences as prompted and listen to their response.</li><li>Bid the other person farewell when the conversation is finished and leave with a better understanding of another person you might not have talked to otherwise.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KzyXr5vJKiYb4J7C81_Xwg.png" /></figure><h4>Storytelling Prompts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ngquSGUUIr2rbJeyr6j7A.png" /></figure><p>Prompting storytelling with specific prompts helps people to share their perspective and bond over this Heart-Tube-Heart experience. These prompts include:</p><ul><li>What is the hardest thing you have experienced at Cornell?</li><li>For what in life do you feel most grateful for?</li><li>What is your take on modern love?</li><li>What similarities do you share with your parental figure(s)?</li><li>What quirks did you have as a child?</li></ul><p>We chose these five questions because they immediately go beyond the typical “what’s your major” or “what dorm do you live in” questions that college students typically ask when they first meet. These questions are intended to show deeper insights about a person, providing a basis for more interesting and memorable conversations.</p><h4>Branding</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSJxtUP-6CJlrzKN58pZLQ.jpeg" /></figure><p>Our design is inspired by playground sound pipes, which is a common feature found on children playgrounds. To echo this inspiration, we wanted our brand to have a personable and relatable name. “Heart-to-heart” was something that came to our minds during our brainstorm session. Through our design, we want to help people to skip over the ordinary, surface-level questions and immediately have candid and genuine conversations. Heart-to-heart perfectly describes our intent. To make it a bit more unique, we decided to make the “to” into “tube”, to echo the main component of our design.</p><h3>Future Direction</h3><p>Heart-Tube-Heart could be an experience that can go beyond the university setting, such as in a museum as a travel destination. The mechanism of Heart-Tube-Heart is simple, but the prompts can be easily changed for the appropriate audience, providing an interesting way not just for university students to connect, but people all over the world. With Heart-Tube-Heart, we dream of a world where it’s no longer intimidating to approach others, or fear judgment and stereotyping based on appearances. We hope that the Heart-Tube-Heart will inspire people to reach out to each other and hear each other’s stories beyond the installation experience.</p><p><em>This project was created by Xin Wen (DEA ‘20), Mikail Masqood (Arch ‘21), Sheri Guo (InfoSci ‘22), Joseph Yoon (ChemE ‘23), Connie Liu (InfoSci ‘23), and Benji Magin (Arch ‘21) as part of Cornell’s Medium Design Collective’s Incubates Team!</em></p><p><em>For more information and other projects see formsofbelonging.com and cornellmedium.design</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d49b1767a0b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>