<?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 Zachary Aman on Medium]]></title>
        <description><![CDATA[Stories by Zachary Aman on Medium]]></description>
        <link>https://medium.com/@zackaman?source=rss-6bafd9ce7ecc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6UGU0Y8W4bZm-9qz.jpeg</url>
            <title>Stories by Zachary Aman on Medium</title>
            <link>https://medium.com/@zackaman?source=rss-6bafd9ce7ecc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:19:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zackaman/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[Zachary Aman — Portfolio]]></title>
            <link>https://medium.com/@zackaman/zachary-aman-portfolio-107b9266471f?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/107b9266471f</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Wed, 26 Aug 2015 04:29:23 GMT</pubDate>
            <atom:updated>2015-08-27T16:37:49.019Z</atom:updated>
            <content:encoded><![CDATA[<p>I am a product designer focused on information architecture, interaction design, and front-end development. I have a broad skillset, including user research, UI/UX design, and development.</p><p>I’m currently looking for roles where I can put my broad skillset to use, and am especially interested in hybrid designer/developer roles.</p><p><a href="https://s3.amazonaws.com/zacharyaman.com/zack_aman_resume+8-27.pdf">My resume is available here.</a></p><p>You can <a href="https://github.com/zya6yu">view my code on GitHub</a>, <a href="https://www.linkedin.com/profile/view?id=AAIAAAWxw60BqIpPX79K6EyyT37KBhhi28Wpyik">connect with me on LinkedIn</a>, <a href="https://medium.com/@zackaman">read my writing on Medium</a>, or email me at zackyuaman@gmail.com.</p><p>A couple of things I’m particularly interested in:</p><ul><li>Interactive information visualization and information architecture, especially the use of visualizations as navigational elements and allowing conversations between users and data.</li><li>The border between interaction design and development, and narrowing the gap between design and code workflows.</li><li>Empowering creativity by giving people the tools to build their visions and supporting collaboration.</li></ul><h3>Projects:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*YQC_4u79CWaJ1DBwXmnFIw.png" /></figure><h3><a href="https://medium.com/@zackaman/teamsense-bf48e5f5a2fa">TeamSense</a></h3><p>TeamSense is a virtual-reality scenario and prototype that supports shared perception of team location and status.</p><p>TeamSense was a nine-month long project spanning domain research with first responders, concept ideation and validation, and prototyping. As Project Lead, I participated in all parts of the process with an extra emphasis on technical implementation and project strategy.</p><p><a href="https://medium.com/@zackaman/teamsense-bf48e5f5a2fa">Read more about TeamSense here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JqRtVjZCtAT098HoS9c8DA.png" /></figure><h3><a href="https://medium.com/@zackaman/metonymy-9d6ca1e014a2">Metonymy</a></h3><p>Metonymy uses degree-of-interest calculation to suggest locally and globally relevant Wikipedia articles.</p><p>My focus with Metonymy was on information architecture and sensemaking, specifically looking at how users interact with algorithms while searching and browsing.</p><p><a href="https://medium.com/@zackaman/metonymy-9d6ca1e014a2">Read more about Metonymy here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*XuK39fwmFGbG2Qf7xOHuOQ.png" /></figure><h3><a href="https://medium.com/@zackaman/mastery-orientation-motivational-design-in-lynnette-9deaff48bfc6">Lynnette</a></h3><p>Lynnette is an intelligent tutoring system for math at Carnegie Mellon University. I worked on redesigning the problem selection process to encourage a mastery-orientation in students.</p><p>I worked on the project from end-to-end, including research with students, interface and interaction design, and prototype development using HTML and Angular.js.</p><p><a href="https://medium.com/@zackaman/mastery-orientation-motivational-design-in-lynnette-9deaff48bfc6">Read more about Lynnette here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8bdUASQmgFsqiKbJVKxmA.png" /></figure><h3><a href="https://medium.com/@zackaman/loopback-68235fe05ec2">Loopback</a></h3><p>Loopback is designed to support feedback and training for EMTs.</p><p>The focus of Loopback was on visual design and information architecture.</p><p><a href="https://medium.com/@zackaman/loopback-68235fe05ec2">Read more about Loopback here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_dP1uxR3hZF5mgxcFkYp-g.png" /></figure><h3><a href="https://medium.com/@zackaman/color-pyramid-acc30583d90">Color Pyramid</a></h3><p>Color Pyramid is an application designed to teach practical color usage fundamentals to novice designers.</p><p>My work on Color Pyramid included cognitive task analysis with novices and experts, educational design, and basic Android prototyping.</p><p><a href="https://medium.com/@zackaman/color-pyramid-acc30583d90">Read more about Color Pyramid here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=107b9266471f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TeamSense]]></title>
            <link>https://medium.com/@zackaman/teamsense-bf48e5f5a2fa?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf48e5f5a2fa</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[information-architecture]]></category>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Wed, 26 Aug 2015 03:22:35 GMT</pubDate>
            <atom:updated>2015-08-29T21:20:19.163Z</atom:updated>
            <content:encoded><![CDATA[<h4>Mission:</h4><p><strong>Team Dado partnered with Draper Laboratory to enhance situational awareness for first responders in emergencies.</strong> Communication is essential to emergency response — responders need to know what each other responder is doing in order to share information, coordinate safely, and minimize duplicate work. However, existing communication structures do not scale, causing breakdowns as scenes become more complex. Limited radio bandwidth forces responders to proactively evaluate the relevance of their information, placing a heavy cognitive load on individual responders.</p><h4>Solution:</h4><p><strong>TeamSense is a virtual-reality scenario and prototype that supports shared perception of team location and status.</strong> The scenario, built in Unity, acts as a platform for us to rapidly prototype and test different heads-up display and 3d audio presentation methods in a realistic context.</p><p>We focused on three use cases:</p><ul><li>Helping responders integrate with ongoing searches through a historical view of where other teammates have been.</li><li>Alerting responders when a responder is injured and they need to shift their priorities.</li><li>Targeted search for a downed responder.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F134799413&amp;url=https%3A%2F%2Fvimeo.com%2F134799413&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F528448970_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/20dbcc5cb42c984bb7f49a4c114a9ef9/href">https://medium.com/media/20dbcc5cb42c984bb7f49a4c114a9ef9/href</a></iframe><h4>Role:</h4><p>The entire project was highly collaborative, with each of us contributing heavily in research, design, and prototyping. As project lead, I was responsible for managing our discussions with Draper and making sure that we approached the design process in a strategic manner. I was also heavily involved in coding the prototype, especially in prototyping the audio interactions.</p><h3>Breakdowns in Communication</h3><p>We worked with first responders in Pittsburgh, Pennsylvania to understand how they deal with emergency situations. Through a combination of structured interviews, directed storytelling, contextual inquiry, and guerrilla research we got as close to emergency response as possible without actually stepping foot in a burning building. After gathering data, we modeled the information flows throughout the scene and identified two primary problems that we wanted to address with our prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cOJYHFqPDYF-h8LWPKbK1A.png" /><figcaption>Radios communication forces responders to figure out if their information is worth communicating to everyone.</figcaption></figure><h4>Existing Communication Models Don’t Scale</h4><p>Currently, first responders communicate primarily through the radio. The radio is great at broadcasting information to a large group of people, but only allows one person to communicate at a time.</p><p>As scenes become increasingly complex, responders are forced to restrict their communication to conserve radio bandwidth. Responders have to make assumptions about what others need to know, rather than communicating all information and letting receivers pick out the important information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YAnkRIRUjnTkhuGnLzFJhw.png" /><figcaption>If responders aren’t getting the full picture from their teammates, they may act in ways that endanger themselves and others.</figcaption></figure><h4>Misunderstandings Compound</h4><p>Emergency responses are collaborative efforts, and the actions that each responder takes depend heavily on a shared understanding of the scene. When responders are unable to communicate their understanding with the rest of the team, collaboration starts to break down.</p><p>A lack of communication causes misunderstandings to compound. When one responder doesn’t know what another is doing, he does not know what needs to be communicated or what safety precautions need to be taken. This is especially problematic in large-scale scenes, where scene chaos can quickly overtake the ability to communicate.</p><h3>Building Shared Perception</h3><p>Explicit, verbal communication places a heavy cognitive load on responders by requiring them to consciously evaluate the importance of their information. Our goal was to place information out into the world where it can be easily perceived by every responder.</p><h4>Picking the Right Problem</h4><p>Before actually building out the prototype, we wanted to validate which problems are worth solving for first responders. We made 17 storyboards and ran speed-dating with 12 responders. The most popular storyboards all centered around location information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D1YCDASwSy9AUeYq9OfR3g.png" /><figcaption>A historical view of where teammates have been.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jENsIB2pUnri16Ks4sGYGg.png" /><figcaption>Automatic triggering of mayday alerts (with location included.)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*inYeAMP93b8JoF3yxNQb7w.png" /><figcaption>Ensuring teammates are out of harms way before taking action.</figcaption></figure><p>We found that location is a key piece of information in a variety of use cases, but it is not easily communicated through the radio. By building a system that allowed responders to see where there teammates are, have been, and might be we could have an impact throughout an entire emergency response scene.</p><h4>Rapid Prototyping</h4><p>One of the main obstacles in designing for first responders is that you cannot actually test within a burning building or in an active shooter situation. To get around this, we started with quick concept validation exercises, such as bodystorming, JavaScript web applications, and using Counter-Strike as a prebuilt environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CvLpxPaHBTffUmyUqgEAng.png" /><figcaption>We traced participants’ search paths on paper to test the usefulness of trails.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cfvnuLjQA_YMjMYs7_dTrg.png" /><figcaption>We built a JavaScript webapp to see how different audio factors (pitch, reverb, etc.) are intuitively understood.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pUNQ8lYzCfoz3nj1fiu55A.png" /><figcaption>We used Counter-Strike as a prebuilt environment to quickly test haptic concepts.</figcaption></figure><h4>Making the Jump to Code:</h4><p>The system we imagined is not the traditional web or mobile experience, and so we hit the limits of existing prototyping tools pretty quickly. We decided to build our own prototyping and testing platform in Unity, giving us the flexibility to build our ideas while simulating the pressures of an actual response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*43D-TDeGm9qM7XWv-AIgkg.png" /><figcaption>We designed a range of layouts, including simple 3-apartment floors, labyrnthine 20-apartment buildings. Eventually we settled on a four-story apartment building.</figcaption></figure><p>TeamSense’s goal is to deliver location information to responders in a way that is immediately understandable and robust in emergency environments. We wanted to explore which modalities work best for which kinds of data and how our system could fail gracefully between sensory channels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*YQC_4u79CWaJ1DBwXmnFIw.png" /><figcaption>Visual trails displaying where other responders have been.</figcaption></figure><p>We ended up building visual and audio representations of historical trails and targeted search. Trails were a big hit, allowing responders to quickly understand which rooms had been searched, find other responders, and find the exit. Targeted search was also much quicker with visual and/or audio cues. Our prototypes required minimal training, allowing location information to be directly perceived and understood by participants.</p><h4>Testing and Metrics</h4><p>In testing TeamSense, we looked for both overall task completion and the cognitive effects of our prototypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Br9CemZp8UF0e4pjsGtXsQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBuIIcsKfjp4qUPUhMAk5Q.jpeg" /><figcaption>Testing participants ability to navigate an unknown building with and without a view of where other responders had been previously.</figcaption></figure><p>For task completion we looked at the time to completion for each of our three stages (collaborative search, targeted search, and exiting the building) and the number of errors made in each stage.</p><p>For cognition we wanted to measure how intuitively understandable the feedback was and if there was any cognitive tunneling going on. We measured understandability by periodically pausing the simulation and asking participants to state their interpretation of the scene at as granular a level as possible. To measure cognitive tunneling we used two secondary tasks, requiring participants to call out whenever they heard “Ladder Six” on the radio or when their air dropped to a multiple of ten.</p><h3>Further Work</h3><p>We laid the groundwork for developing situational awareness prototypes, but delivering location information is only the tip of the iceberg. We built our platform so that data and presentation can be mixed and matched, allowing rapid prototyping of new concepts.</p><p>Beyond the delivery of new information and the development of intuitive presentation methods, there are two other areas that we think are worth exploring:</p><h4>Implicit Communication</h4><p>We focused on the receiving end of communication — how an individual receives information and makes sense of it. The sender’s side, however, also has a lot of potential. Our goal was to make communication passive, creating digital residue that can be observed by other responders; doing this, though, opens up more bandwidth for intentional, explicit communication.</p><h4>Sensory Augmentation / Customization</h4><p>The modular architecture of our platform was, for us, a means to quickly test multiple variations of prototypes. However, this could also be delivered as a customizable solution for individuals and teams. Looking at what information should be standard across whole teams versus what information can be varied and split between individuals could optimize information flows and cognitive load during emergency responses.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf48e5f5a2fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Metonymy]]></title>
            <link>https://medium.com/@zackaman/metonymy-9d6ca1e014a2?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d6ca1e014a2</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[wikipedia]]></category>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Tue, 14 Jul 2015 02:45:37 GMT</pubDate>
            <atom:updated>2015-07-14T02:45:37.032Z</atom:updated>
            <content:encoded><![CDATA[<h4>Problem:</h4><p>To me, Wikipedia is a modern world wonder. However, <strong>directed exploration within Wikipedia is problematic</strong>. From the user’s perspective, falling down a rabbit hole of links in a depth-first search is easy — surfacing and understanding the clusters of information that an article sits within is not.</p><h4>Solution:</h4><p><strong>Metonymy is an information periscope for readers.</strong> Keeping track of the user’s trail through Wikipedia, Metonymy uses degree-of-interest calculation to suggest locally and globally relevant Wikipedia articles.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F127565695&amp;url=https%3A%2F%2Fvimeo.com%2F127565695&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F518382354_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/084c51f72e79bbc65d729e37caf77fd1/href">https://medium.com/media/084c51f72e79bbc65d729e37caf77fd1/href</a></iframe><h3>Making sense of Wikipedia:</h3><h4>Saving Pages</h4><p>Before knowing where you want to go, it’s important to know where you’ve been. Metonymy tracks all pages visited within Wikipedia, and allows users to star pages for later. (Honestly, it blows my mind that this isn’t already part of Wikipedia, though it is available with other Chrome extensions.)</p><h4>Cluster Based Recommendation</h4><p>Metonymy generates recommendations by calculating the <a href="https://en.wikipedia.org/wiki/Tf%E2%80%93idf">term frequency — inverse document frequency</a> of articles within two steps from the in-group and out-group, respectively. The user is able to build an in-group by toggling on saved articles, and the remaining saved articles serve as the outgroup. This filters out the articles that are highly connected within all of Wikipedia, leaving only the articles that are highly-referenced near the in-group and specific to the selected articles.</p><p>The goal is to empower users to triangulate their way to new Wikipedia articles, allowing a sort of “information alchemy” based on what articles the user puts in the in-group.</p><h3>Designing with Algorithms</h3><p>Designing an extension for Wikipedia is entirely about information architecture. The approach I took was to use <strong>algorithms as a method of interaction design</strong>: prototyping new methods of information access and retrieval, and evaluating the output and usability of the recommendation algorithm.</p><p>Ultimately, the dream is to build a system for myself that takes my knowledge as input and gives me optimal information as output. This leaves me with two real questions:</p><ul><li>Has Metonymy changed the way I use Wikipedia?</li><li>Do I trust the results Metonymy gives me?</li></ul><p>To the first question, Metonymy has made structured browsing easier. I no longer browse my way into dead-ends, because each recommendation is algorithmically intersting, in relation to either my current article or the boundary of my knowledge. However, I still have control over the recommendations so I have a greater trust in their output.</p><h4>Further Work</h4><p>There is still a lot of work to be done on Metonymy. The algorithm is loosely based on the degree-of-interest function found in <a href="http://ieeexplore.ieee.org/xpl/login.jsp?tp=&amp;arnumber=5290699&amp;url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5290699"><em>“Search, Show Context, Expand on Demand”: Supporting Large Graph Exploration with Degree-of-Interest</em></a><em>. </em>As I built it, however, the algorithm runs in O(n^2), and starts to slow down noticeably with more saved links.</p><p>I’d like to do more work on the UI, providing a graphical, node-based view similar to the one in <a href="http://www.cc.gatech.edu/~dchau/papers/11-chi-apolo.pdf">Apolo</a>.</p><p>Finally, building the graph out of explicit links between articles is just the tip of the connection iceberg. There are many other types of connections that could be examined, such as authorship and crowdsourced trails throughout articles.</p><p>This project was originally produced for <a href="http://www.flong.com/">Golan Levin’s</a> <a href="http://golancourses.net/2015/"><em>Interactive Art and Computational Design</em></a> class at Carnegie Mellon, Spring 2015.</p><p><a href="https://github.com/zya6yu/Metonymy">Metonymy source code available on GitHub.</a></p><p><a href="https://github.com/mirkonasato/graphipedia">Thanks to mirkonosato and his Graphipedia project, which was used to create the Neo4j graph database.</a></p><p><a href="https://github.com/cgallello/UXCheck">Thanks to cgallello and UXCheck. Studying the code of UXCheck helped me understand how the architecture of a Chrome extension works.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d6ca1e014a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Color Pyramid]]></title>
            <link>https://medium.com/@zackaman/color-pyramid-acc30583d90?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/acc30583d90</guid>
            <category><![CDATA[colors]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Wed, 25 Feb 2015 23:07:07 GMT</pubDate>
            <atom:updated>2015-02-25T23:07:07.798Z</atom:updated>
            <content:encoded><![CDATA[<p>We are immersed in color; so much so that it is often taken for granted. This is a challenge for tudents learning design, who often have an instinctive knowledge of color but lack theoretical rules to guide exploration.</p><p>The goal of our educational design is to teach practical fundamentals of color usage to college-age, novice students.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KGwc3BZZpHMpuop9dWMq3g.png" /></figure><h3>Process</h3><p>Domain research, design, iteration, and prototyping.</p><h4>Domain and Cognitive Research</h4><p>In order to scope the project initally, we did background research into how color is taught currently and created benchmark tasks, giving us a clear endpoint.</p><p><a href="http://www.usabilitybok.org/cognitive-task-analysis">Cognitive Task Analysis</a> is a research technique designed to elucidate the discrete knowledge components a person needs to complete a task. We created our own solutions to the task using a rational, prescriptive task analysis and generating a subset of specific concepts, skills, and schema we thought would be sufficient to solve the problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZxVxyRkV79ujU8_0IUkCDQ.png" /></figure><p>Afterwards, we interviewed three expert designers and conducted think-alouds with five novices. Using the empirical data, we adjusted the set of concepts we wanted to teach, breaking up some into smaller parts and adding others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AP1OMFy3H8IU5eXYtmh5pQ.png" /></figure><h4><strong>Cognitive Task Analysis Insights</strong></h4><p>The main changes we made to our cognitive model were providing a structured method for applying and proportioning color, and breaking color feeling and association into cultural and personal components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LnhTVxHegz1qa5cnuRD8gg.png" /></figure><p><strong>The Pyramid Method</strong></p><p>One often counter-intuitive principle of color usage is that the power of a color is inversely related to how much it is used; accent colors must be used sparingly lest they lose their ability to draw the eye. To teach this concept, we teach a pyramid method that starts with a base color, supported by a small amount of contrasting accent color and a neutral base. This gets at both the contrast and proportion needed to effectively draw the eye.</p><p>This is only one of many ways to apply color, but it is one that is easy to convey and practical for novices.</p><p><strong>Personal and Cultural Color Associations</strong></p><p>The other thing we were surprised by was the distinction between widespread cultural associations and weaker, personal associations. Cultural associations are strong enough to go from word to color (from “Love” to “Red”). Personal associations, by contrast, are more delicate and can only go from color to word, often through free association. Being able to delineate how widely an association is held is crucial to critiquing color usage.</p><h4>Design and Iteration</h4><p>Once we knew what cognitive building blocks we wanted to teach, we worked on mocking up a design to paper prototype with. Our design used pretraining, multimedia, explanatory feedback, and compared examples as the grounding for our instruction.</p><p><strong>Pretraining:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fa32jAq5ZJs0OGu_2nqLqw.png" /><figcaption>Pretraining is used to teach baseline concepts such as hue and saturation.</figcaption></figure><p><strong>Multimedia:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UkuF3wmlqXI16kicjoQiEg.png" /><figcaption>Multimedia are used to visually demonstrate the concepts we want to teach.</figcaption></figure><p><strong>Explanatory Feedback:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*anhLSEQ3GJtSn6m9HqbRBQ.png" /><figcaption>Explanatory feedback makes sure that every test condition is also a learning opportunity.</figcaption></figure><p><strong>Compared Examples:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqS-H_45KnpX2gxhMY5M7w.png" /><figcaption>Compared examples support student induction.</figcaption></figure><p>With the full flows built, we used printed versions to user test with. This exposed several usability issues as well as educational issues where concepts were not clearly explained or demonstrated. We then iterated on our designs using the test feedback. After testing the mock-ups on paper, I prototyped our application as an Android application to test the interactions.</p><p><em>With Qian Hu for E-Learning Design Principles, Fall 2014 at Carnegie Mellon University.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acc30583d90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Loopback]]></title>
            <link>https://medium.com/@zackaman/loopback-68235fe05ec2?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/68235fe05ec2</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[application]]></category>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Wed, 25 Feb 2015 20:41:16 GMT</pubDate>
            <atom:updated>2015-02-26T03:36:19.727Z</atom:updated>
            <content:encoded><![CDATA[<p>Encouraging training and feedback in the Carnegie Mellon EMS system.</p><h4>Scope</h4><p>Loopback is an application designed with two goals in mind:</p><ol><li>Support EMT career growth by aggregating and making sense of feedback</li><li>Help EMT supervisors provide effective training</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iuVAavI4d88y37bkquFhug.png" /><figcaption>The History, Team, and New Evaluation screens.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gSnUrZWv8BWwxaPi0rInw.png" /><figcaption>Flows for the key screens in the application.</figcaption></figure><h3>From Research to Design</h3><p><em>Loopback fosters feedback within an EMT station, ensuring each member receives the training they need.</em></p><p><strong>Training is critical for EMTs.</strong> Proper training prevents errors that could lead to EMT endangerment, patient mistreatment, or improper administrative handling. Loopback promotes training and fosters a positive work environment by providing a central place for evaluations to happen. After the completion of each run, EMTs are evaluated by their direct superiors and given comments and suggestions on how to improve. These evaluations are saved and aggregated, allowing each EMT to track their progress as well as helping team supervisors structure training to meet the needs of their team.</p><h4><strong>Preliminary Online Research</strong></h4><p>The first place we went to research was the internet. This provided a wide cross section of life as an EMT. In addition to basic information about pay, responsibilities, and quality of life, we were able to find more varied and personal details within the EMT subreddit. Talking with EMTs on Reddit showed that there is no singular EMT experience; rather, <strong>it is a job that varies largely between stations and geographic region, but is always both stressful and proud</strong>.</p><h4><strong>Preliminary Interview</strong></h4><p>Prior to starting design, we interviewed a supervisor at the Carnegie Mellon University EMS, who I will refer to as Alan. As there is not a large amount of standardization between different EMS services, Alan was especially useful in drawing a complete, concrete picture of how runs are handled at CMU as well as of how <strong>training occurs constantly during their large periods of downtime.</strong></p><h4><strong>Follow-Up Interview</strong></h4><p>After our preliminary research we identified promising problem areas to work on, eventually settling on feedback, evaluation, and training. With a goal in mind, we sketched out some ideas and met with Alan a second time. Alan validated the overall idea and further elucidated the evaluation process and how it could be improved. <strong>One of the key takeaways was that evaluations need to be general in order to adjust for unique, edge-case runs.</strong></p><h4>Ideation</h4><p>We did ideation by brainstorming as many issues and technological tools as possible and combining those into as many ideas as possible. We then ordered them based on feasibility and impact and clustered related ideas together. <strong>We chose feedback and training because it was feasible and high impact.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*tfQ0ySzxaqm7TyW07p82jQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*bVUENhC_sY6JFYZwOGKS3Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*W1lx6rnFoSrHZ122xVzyyQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tKqd9LDGu4qjCq6vYq1aAQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*auZXRfCpJmQ6HYb5ElGWKg.jpeg" /></figure><h4>Mapping and Flows</h4><p>The structure of our application is straightforward: we have three top level categories (Evaluations, History, Team) controlled through a bottom nav bar. Under each of these are some subpages, such as the screen for filling out the evaluation or a drill down into a single report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*0Qc0AtR3cO4VuVMZgSDRXA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oKSlcBoSar8YxX4T5T15xg.jpeg" /></figure><h3>Design Insights</h3><h4>Personal History Screen</h4><p>One of the most problematic screens was the personal history screen, where we wanted to quickly show trends but also provide navigation to both single-criterium drill downs as well as individual reports.</p><p><strong>This is a problem of information hierarchy and reconciling data visualization with intuitive navigation without overloading.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8qzU_B9q-iOQuf_pZEe1MA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vGon_Omx1UZVjCFjfDIbyA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EUz3kgZ1aXDeRNRd4lmAvQ.jpeg" /><figcaption>Personal History started off abstract but unusable.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewlZ0RVzRh5l-u-OLNrfcw.png" /><figcaption>In the end, we used explicit labeling and a clear major axis to make the screen usable.</figcaption></figure><p><strong>Major and Minor Axes</strong></p><p>One of the main problems was that rows and columns were initially given even weight, making it confusing what the difference between a row and column was. To solve this, we made rows our major axis to keep single runs together and made criteria columns secondary.</p><p><strong>Explicit Labeling</strong></p><p>Our initial concept for the history was as an abstract, beautiful grid with minimal labeling information. It turns out this isn’t usable at all. Instead, we ended up focusing on explicit labeling and repeated iconography to minimize abstraction.</p><h4>Team Overview Screen</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ox8yt-mXhg6KETvCHLGRTQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aGolRe0B7gHPUa8BQbKlfw.jpeg" /><figcaption>Our initial team view was just a color-coded grid without any pre-interpretation.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ALlW_xD_vxAvo98nPo_4BA.png" /><figcaption>We redesigned the team view screen to include suggestions and highlighted runs to reduce cognitive load for the supervisors.</figcaption></figure><p><strong>Don’t just show the data—interpret it.</strong></p><p>It’s not uncommon in writing to hear “show, don’t tell.” This gets flipped in a way when it comes to design work: it’s not always enough to simply show the data. Instead, <strong>make understanding as easy as possible for the user by providing suggestions and interpretation up front. </strong>This was the key lesson we learned in designing our team view screen. We weren’t able to properly design the screen until we grounded ourselves in what the team supervisor’s intentions are. Our final design provides training suggestions and highlights specific runs, reducing the amount of mental processing required by the supervisor.</p><p><em>With Sharon Lin, Israel Gonzales, David Ralley for Interaction Design Fundamentals, Fall 2014 at Carnegie Mellon University</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68235fe05ec2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastery Orientation: Motivational Design in Lynnette]]></title>
            <link>https://medium.com/@zackaman/mastery-orientation-motivational-design-in-lynnette-9deaff48bfc6?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/9deaff48bfc6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[motivational-design]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Wed, 17 Dec 2014 06:14:11 GMT</pubDate>
            <atom:updated>2015-02-26T03:44:00.058Z</atom:updated>
            <content:encoded><![CDATA[<p>Teaching students to focus not simply on doing problems, but on how they choose which problems to do.</p><p>Lynnette is an adaptive math tutor built at Carnegie Mellon University. However, it <em>feels</em> like a tutor—there’s little present beyond more and more math problems to solve. This semester I worked with Professor Vincent Aleven and Yanjin Long (PhD candidate) to focus on the non-mathematical part of the experience. Specifically, <strong>the goal of our project was to focus on problem selection and encourage a mastery orientation rather than a performance mindset</strong>, with the end goal of conducting a research study on the efficacy of different design interventions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*UI2Ak94v-0xmJw67xkpD1w.png" /><figcaption>The first welcome screen of the interactive prototype</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*amIPzDhFGSqs3DbJQWOqkA.png" /><figcaption>One of the tutorial screens that calls out a specific interface element.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*-9sGGZgQHxacv_WioYSoLA.png" /><figcaption>The home screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*HILwaLBWrMJtEo1jaMlknA.png" /><figcaption>Problem selection becomes an interactive item with explanatory feedback.</figcaption></figure><h4>Problem Scope</h4><p>In the words of <a href="http://link.springer.com/article/10.1007/s11031-012-9293-6">O’Keefe et al</a>., “A <em>mastery goal orientation </em>refers to a focus on <em>developing </em>competence. With a <em>performance goal orientation, </em>the focus is on <em>demonstrating </em>competence” (51). That is to say: <strong>challenge is healthy</strong> and effective learning comes from growth, not from what you already know.</p><p>What we want to design are structures that get students out of the continuous rhythm of doing math problems over and over again and instead get students to question, “Which problems should I be doing?” However, we don’t just want to heavily support students in making decisions; we want to affirmatively teach students how to make their own decisions and create transferable selection strategies that are applicable in different domains.</p><h4><strong>Storyboarding</strong></h4><p>To kick off our design process, Yanjin and I brainstormed potential features and solutions that could help students make good problem selections, which I turned into 18 storyboards, ranging from different types of feedback to social mechanisms to avatar customization. We used these storyboards to run speed dating with 12 middle school students, quickly walking them through each idea to see how the students reacted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hBtpaU-FPnbsxEK3ERujPw.png" /><figcaption>This storyboard focused on negative feedback when students select an already mastered level.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lrJ2aVYU153gsdD7ZeVhMQ.png" /><figcaption>Several of our storyboards focused on goal setting and helping students plan their way forward.</figcaption></figure><p>Middle school students are fascinating to interview. Some were timid, some were so sharp they made me feel stupid. What struck me the most, however, was how enthusiastic they were—generally they were in favor of our ideas, though some ideas more than others. The key insights we took away from storyboarding were:</p><p><strong>Collectibility: </strong>Students<strong> </strong>like collecting things and being able to see a visual representation of their progress. Achievements, badges, and collectible avatar items were all well received.</p><p><strong>Mastery is hard: </strong>As a concept, mastery is not well defined in the minds of middle school students. Some students had very high capabilities for planning their education, but most students simply tried to do what was asked of them without taking a proactive look at what is best for their learning. Student feedback solidified that this metacognitive domain is worth exploring.</p><p><strong>Social works for some, but not all: </strong>We spent a lot of time trying to think of what motivations we could latch on to and use to foster a mastery orientation, one of which is the idea of social competition. Some students loved this idea, but the more timid students were decidedly unenthused by the competition-centric storyboards. In retrospect, competition is largely focused on <em>demonstration of competence</em> rather than <em>development of competence, </em>making it hard to fit into the mastery scheme.</p><h4><strong>Interactive Prototype + Paper Mockups</strong></h4><p>After storyboarding, we moved to paper prototyping and a HTML/Javascript prototype and tested with another group of 10 middle school students. This allowed us to test both the usability as well as the interactivity of our ideas and get a good look at whether or not our features were teaching students the right concepts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i7Gu7ZHwYv7D9I65Lg9Shw.png" /><figcaption>The “HCI” approach that breaks students out of a sequential level model. However, this would be too much scaffolding and not help students transfer their knowledge afterwards.</figcaption></figure><p><strong>Human-Centered Design vs. Research Design: </strong>One of the key issues I kept bumping up against was that the design had to be practical from a research standpoint: every detail had to be considered with a specific hypothesis in mind, and every feature had to be linked to a cognitive theory and motivation. Most importantly, the desired outcome was that students would make good problem selections outside of the tutor; it was not sufficient to simply steer them toward good selections within the tutor. Instead, we needed to focus on instruction and goals that would have a lasting impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VcWWGE40S7MKNz8IgBBPbg.png" /><figcaption>Each interaction is designed to reinforce a mental model of mastery.</figcaption></figure><p><strong>Mental Models: </strong>The success of our design lives and dies on teaching students a correct conception of “mastery” and how mastery relates to making good problem selections. In our testing, however, this proved a tricky concept to impart. We try to take every opportunity available to surface this concept and make it an inescapable part of the instruction. What became immediately clear is the need for an explicit tutorial that defines the concepts, explains how mastery is calculated by the tutoring system, and how each interface component is tied to mastery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xVCGy7MPFwECDAMMuy1oTA.png" /><figcaption>Rewards are given not for problem completion, but for making good selections.</figcaption></figure><p><strong>Explicit Reflection: </strong>Yanjin had previously observed that students had a tendency to quickly and automatically go through problem selection without any pause for reflection and metacognition. Our design focuses on making moments of reflection an integral part of instruction, allowing students to receive explicit feedback on their strategy and forcing them to pay attention to an often overlooked aspect of learning how to solve new types of problems.</p><h4>Reflections</h4><p>This project was very much an exercise in my own mastery orientation. I had never done extensive user testing before and I had only basic design skills. My main strength, web development, was pushed beyond my comfort zone by my desire to learn the entire <a href="http://meanjs.org/">MEAN.js</a> stack when I only had a rudimentary understanding of Angular. Working beyond my current masteries, though, has been immensely rewarding: I now feel comfortable with running user tests with students at different stages during the design process, my ability to pump out mockups has grown significantly (though my visual design ability is still far from perfect), and I feel competent and comfortable tackling future projects using MEAN.js. I am always surprised by how useful it is to learn about learning—learning how students learn best is also learning how I learn best, and the idea of a mastery orientation is one I plan on keeping in my head.</p><p><strong>Metacognition is difficult to design for: it’s not immediately visible and useful to students, and is often taught implicitly rather than explicitly. </strong>However, getting students to take a step back and think about how they are learning is enormously fruitful, and pays educational dividends over time. The fact that these middle school students do not have well developed metacognitive abilities is perhaps not surprising; what is slightly more startling is that I sometimes see the same thinking in my peers in graduate school. When you see students in their mid-twenties still in the mode of “perform, perform, perform” without the ability to take stock and look at their own learning strategies, you have to wonder, and you have to hope that metacognitive skills become an integral part of future educational design.</p><p><em>This piece is based on my independent study with Associate Professor Vincent Aleven and PhD Candidate Yanjin Long for the Fall 2015 semester.</em></p><p><em>Source code for the prototype can be viewed on GitHub here: </em><a href="https://github.com/zya6yu/lynnette_prototype"><em>https://github.com/zya6yu/lynnette_prototype</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9deaff48bfc6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where do we go from here?]]></title>
            <link>https://medium.com/@zackaman/where-do-we-go-from-here-f3e10681c5b7?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3e10681c5b7</guid>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Sat, 22 Nov 2014 03:02:07 GMT</pubDate>
            <atom:updated>2014-11-22T03:08:13.164Z</atom:updated>
            <content:encoded><![CDATA[<p>Robin Hunicke (<a href="https://twitter.com/hunicke">@hunicke</a>) is by turns a games researcher, game evangelist, and game maker. A member of the team behind the acclaimed <a href="http://thatgamecompany.com/games/journey/">Journey</a> and author of the influential <a href="http://www.cs.northwestern.edu/~hunicke/MDA.pdf">Mechanics, Dynamics, Aesthetics framework</a>, Hunicke knows where she wants to go in game design. Core to her practice is the idea of designing for experience first, starting with the question, “What do I want my user to feel?” Rather than focus first on the mechanics or even the action of the game, she looks at the top level of the pyramid, starting from the end result and finding the mechanics and dynamics that can foster this feeling.</p><p>Currently she is working on a new game called <a href="http://www.funomena.com/luna/">Luna</a>, where the feeling is transformation. While doing this, Hunicke is aiming to create what she calls the “Triple-E” game — a game that is simultaneously elegant, expressive, and emotional.</p><h3>Elegant, Expressive, Emotional</h3><p>Games come in many varieties. To help figure out what kind of game a game is, Hunicke presents three orthagonal spectra for evaluation. A game can be heavily scripted, like Final Fantasy, or it can be open ended and encourage player expression, like the Sims. In terms of production cost, games can be baroque (heavily produced) or elegant (small but impactful.) The third dimension is emotional versus rational; a heavily strategic game like Starcraft is more rational, whereas the power of an emotionally gripping game like The Last of Us comes from the way it moves our feelings.</p><p>The end of any one of these scales is not inherently bad; what is important is being able to evaluate and classify games. Hunicke takes this a step beyond classification, however, by using it not only as an after-the-fact tool but also as a map forward. She takes this theory of classification and asks, “How can I make a game that is at the extreme of not just one of these scales, but at all of them? What does it mean for a game to be elegant, expressive, and emotional at the same time?”</p><h3>Building an Environment for Building</h3><p>As the founder of the game studio <a href="http://www.funomena.com/">Funomena</a>, Hunicke is responsible not just for building the game, but also for building the environment that the game is built in. Tackling a radical design problem requires a studio specifically tailored to that problem. Funomena is aligned with Hunicke’s philosophy of feeling-first game design—the company as a whole is feeling-first. Hunicke describes the studio as having “one big idea and a few little ideas” and being a company that treats people not as “eyeballs, installs, or wallets,” but as people.</p><p>Key to making a studio like this work is being able to find and articulate that feeling at the core of the “feeling-first” game. This touches every facet of production, from the feeling of animation, the color palette, and the sense of fable present in Luna. The aesthetics of the game are what define the emotional interface with the user, and it is fascinating to see the sources of inspiration that Hunicke and the rest of the Funomena team draw on. The illustration of Mary Blair exemplifies the fantastical imagery that is beautiful, and haunting. The work of Anish Kapoor is held up as work that is not simply only visual but deeply tactile and (almost) edible. The works of Umetaro Azeki and Lee Bontecou give definition to the feeling of transformation itself. At each step, inspiration and aesthetic are tied back to immersing the player in the desired feeling.</p><p>No matter what the undertaking, it is always helpful to have a sense of where you are, where you are going, and how to get there. In game design, orientation can an abstract notion but it’s important that this does not stop these questions from being asked. No matter the discipline, it is critical to define the feeling you want your product to evoke—how you get there is up to you.</p><p><a href="https://www.cs.cmu.edu/calendar/wed-2014-11-05-1600/human-computer-interaction-institute-z-axis-seminar"><em>This piece is based on Robin Hunicke’s talk for the Carnegie Mellon Human Computer-Interaction Z-Axis series</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3e10681c5b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who’s Walking Whom?]]></title>
            <link>https://medium.com/@zackaman/whos-walking-whom-b0bbb05844e4?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0bbb05844e4</guid>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Fri, 21 Nov 2014 03:47:41 GMT</pubDate>
            <atom:updated>2014-11-21T03:47:41.273Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Dr. Hannes Vilhjálmsson wants our digital social interactions to have all of the richness of face-to-face communications. We’ve attempted to replicate this before; in MMOs like World of Warcraft we click a button and our character laughs, another button and the character cries. What’s missing, however, is the naturalness of the interaction. Avatars can reside in the same digital space as each other but they do little more than that; for the most part they simply reside, statically.</strong></p><p>Vilhjálmsson’s work focuses on uncovering the intuitive natural rules of interpersonal interaction and translating these into what he calls a “social engine,” a framework that automates inter-avatar interaction the same way a graphics engine controls how light reflects off of digital surfaces. It’s an ambitious undertaking, focused on replicating interpersonal patterns from conversational eye contact to smoothly navigating past a group in a crowded hallway. In keeping with its audacity, a social engine could also have massive ramifications for how we interface with one another in digital spaces. The more automated our digital representation becomes, the more we have to grapple with how much control we are willing to cede and how much freedom we grant our electronic doubles.</p><p>He posits a world in which we might tell our avatar, “I really want to impress the person across the room,” and our avatar takes it from there. Taking the idea a step further, he says our personal avatar might go out and make friends for us on its own while we go about the rest of our lives. You can’t deny the convenience of it—press button, receive friends—but how tightly coupled is this to our physical existence, and what are the consequences when digital and physical get out of sync? If the end goal is to create an autonomous, digital representation of ourselves it behooves us to examine what controls the inter-avatar grammar our doubles employ. We will start by guiding our avatars’ actions, but the more autonomous they become the more their actions will shape the way we interact in the physical realm.</p><p>The important point here is that <strong>the more autonomy our avatars have, the more control they will have over us</strong>. The avatar-human relationship can be broken down into four, non-exclusive types of control:</p><h4>Human Prescriptive: We Control Avatar Behavior</h4><p>This is the simplest, most straightforward type of relationship: the avatar does as it is told. All social benefits rely directly on a human with the digital-social finesse to humanize his or her own communications. This is also exactly the kind of relationship Dr. Vilhjálmsson wants to escape from. For the most part, we don’t consciously think about our body language, our gait, or how we stand together in groups — but, in a human prescriptive scheme, these all need to be controlled by the user, manually. There’s little question of who’s in charge, but how much can you accomplish when you have your hands full choosing how much weight to put on your right foot versus your left?</p><h4>Human Descriptive: Avatar Behavior Reflects Us</h4><p>Undoubtedly a step in the right direction would be to have our avatar learn and reflect our personal mannerisms. As we continue to quantify more and more of our personal information, this doesn’t seem so far-fetched. While it might be unnerving to look at a digital mirror, at least here the digital and physical would remain tightly coupled. As we act in reality, so does our digital double. However, any negative personal traits we possess would be reflected in our avatar, keeping all of the joy of our awkward handshakes, our uncertainty when we’re the last person stuck with the person no one wants to talk to, the inability to keep our composure when we’re on the verge of a breakdown. This is real, but is it what we want?</p><h4>Avatar Prescriptive: Avatar Behavior Pushes Us</h4><p>A key component of Dr. Vilhjálmsson’s research is unearthing and modeling the social cues and rules that govern our day to day interaction, and it is these rules that cause the relationship between human and avatar to get murky. What happens when our avatar discovers rules beyond our capability to actualize? Once we have an optimized quantified model of interaction, we will feel compelled to optimize ourselves. Rules are a tricky business, because once we know how to optimize our eye contact, know just how to walk, or know the exact angle to stand at in relation to another person we will try and hold ourselves to those rules. We will come full circle, from having to dictate our avatar’s actions to having our avatar’s actions dictate our own.</p><h4>Avatar Descriptive: We Grow to Match Our Avatar</h4><p>Perhaps, though, we won’t go so far as having to live up to the social rules our avatars uncover. Maybe we’ll see how they act and try and emulate them, letting our avatars act as behavior scaffolding. This relationship has the best of both worlds: a hands-off approach to our avatars that allows them to refine their interactions while keeping our personal interactions intuitive instead of rule driven. The key difference here from the avatar prescriptive relationship is the lack of rules, or at least the lack of consistent rules between the digital and physical realms. If we are to describe our avatars with our actions, then it has to be intuitive. We can’t rely on interpersonal rules derived from the digital world because rules will only be effective to the extent that we can live up to them; however, we can take cues from our doubles, hold up their successes as something to live up to, and let our own, intuitive, behaviors grow and evolve.</p><p>It’s always hard to separate out our influence on technology from technology’s influence on us, and our digital representations are no exception. As we bump up against the limit of human ability and are forced to rely on automation to handle our affairs the bounds of human identity and human agency become increasingly blurred. How comfortable are we giving up control over the elements of our personality? Do we embrace it as a step forward or do we stand on the precipice, trembling?</p><p><a href="https://www.hcii.cmu.edu/news/seminar/event/2014/09/hcii-seminar-series-hannes-hogni-vilhjalmsson"><em>This piece is based on Dr. Hannes Vilhjálmsson’s talk for the Carnegie Mellon Human-Computer Interaction Institute Z-Axis series</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0bbb05844e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Art After Snowden]]></title>
            <link>https://medium.com/@zackaman/art-after-snowden-a29bdf9439e5?source=rss-6bafd9ce7ecc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a29bdf9439e5</guid>
            <dc:creator><![CDATA[Zachary Aman]]></dc:creator>
            <pubDate>Sat, 04 Oct 2014 00:46:22 GMT</pubDate>
            <atom:updated>2014-10-04T00:46:22.510Z</atom:updated>
            <content:encoded><![CDATA[<p>You can’t deny that technology is changing the world. We live in a world of mass surveillance, big data, new media — personal crises our forefathers never could have dreamt. Within the external pressure, though, we also have increased flexibility to define ourselves, both individually and communally. Our personal boundaries have become vague and ill-defined — caught between the desire for freedom and the allure of the hive. It’s tempting to fall to one side or the other, to see technology as fundamentally optimistic or rapidly spiraling beyond our control. In reality, however, technology use has always been a two way street: it empowers us to create new realities but, without critical reflection, often tempts us toward convenience and short-term thinking.</p><p>We have reached a critical juncture in our relationship with technology. On one hand, we are capable of <a href="https://en.wikipedia.org/wiki/Stuxnet">digitally attacking the physical infrastructure of other countries</a> from the comfort of our desks. On the other hand, “There’s an app for that,” has become the catchphrase of our times (<a href="http://motherboard.vice.com/read/the-goat-sacrificing-app-that-tweets-out-your-sins">we can now even digitally sacrifice goats</a>). Awash in pop-tech, we often take our interaction with technology at face value, perhaps unwilling or unable to actively take part in deciding how technology molds our lives.</p><h3>Self &amp; Others, Self &amp; Self</h3><p>Lauren McCarthy (<a href="https://twitter.com/laurmccarthy">@laurmccarthy</a>) and Kyle McDonald (<a href="https://twitter.com/kcimc">@kcimc</a>) create artwork that plays with and examines our personal identities’ increasingly fluid boundaries. They approach the role of technology in our lives from three main perspectives: the ability to integrate technology into ourselves to alter our behavior, its potential to connect us, and examining the relationship between private and public control over ourselves. Our relationship with ourselves is changing — we are constantly asked to define ourself in relation to the world around us. Are we our Facebook profile, our Tinder matches, our LinkedIn network? These don’t paint the whole picture of who we are, but in many ways these are the things that the world knows us by.</p><p>One piece by Kyle and Lauren, “<a href="http://vimeo.com/90547410">Social Soul</a>,” represents and distills us down from our social media, then matches us with our “social soulmate.” There’s something overwhelming about being immersed in personal media, typically doled out in bits and pieces. More salient, though, is the simultaneous excitement and trepidation of seeing our digital selves run through the code machine; we are dissected, broken down, analyzed, and finally regurgitated back out as our algorithmic other-half.</p><p>This experience is what drives our conflicting attitudes toward technology. We feel invaded and we don’t know whether or not to embrace it. The allure of technology is so strong because it promises to connect us, to create something bigger out of our constituent parts. At the same time, however, we feel reduced, taken in bits and pieces and never truly known as an entire person.</p><p>Interestingly, these contrasting views of technology, optimistic and cynical, are reflected strongly in how Kyle and Lauren make and document their art. Their videos alternate between a sense of naive wonder and a surreal, tongue-in-cheek tone that says, “imagine if this were actually the reality we lived in.” Their work plays both sides of the coin, pushing forward the realm of possibility while providing a critique of our breakneck route into the future.</p><h3>Accelerated Abstraction</h3><p>We live in a strange state of affairs:</p><p>Imagine that two people are in a race. The first person is what is conceptually possible to the human mind. A bit behind, the second person is what is practically within our grasp. The distance between them fluctuates, but one thing is for certain: every time the laggard speeds up the frontrunner does too.</p><p>Artists are the pioneers in closing this gap. Enabled by technology, they are increasingly able to make abstract notions tangible. Serendipity? There’s an app for that. In the other direction, however, our tools themselves are becoming amorphous. Mechanical Turk, central to several of their pieces, is literally human intelligence turned into a machine. It uses humans to carry out what we have not yet been able to automate by providing a machine-like interface, making subjective computation experientially the same as a calculator. Does this dehumanize us? The only way to find out is to go forward.</p><p>It says something, though, when an unintended side-effect of our art is giving a human face back to a machine that is, ultimately, already human.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a29bdf9439e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>