<?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 Paul Nylund on Medium]]></title>
        <description><![CDATA[Stories by Paul Nylund on Medium]]></description>
        <link>https://medium.com/@paulnylund?source=rss-caaef21a11df------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dvZSXpDeLM4BP1ubmDiVBg.jpeg</url>
            <title>Stories by Paul Nylund on Medium</title>
            <link>https://medium.com/@paulnylund?source=rss-caaef21a11df------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:31:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paulnylund/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[What I Learned During my Internship at ustwo™]]></title>
            <link>https://uxplanet.org/what-i-learned-during-my-internship-at-ustwo-2817af659e5d?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/2817af659e5d</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[agency]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Tue, 14 Aug 2018 10:47:05 GMT</pubDate>
            <atom:updated>2018-08-22T21:10:16.560Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NWlhYNKgLMlC4pQYR4q4Ng.jpeg" /><figcaption>Playing ping pong in the street outside of the office</figcaption></figure><p>In the spring of 2018, I worked as a UX Design Intern at<em> </em><a href="http://www.ustwo.com/"><em>ustwo Nordics</em></a> in <a href="https://goo.gl/maps/qdhgVydLVBQ2">Malmö, Sweden</a>. As a UX Designer, I would employ a range of learnings from my education at the University of Southern Denmark, including –yet not limited to– processes such as user experience mapping, paper prototyping, and design ideation.</p><h4>What is ustwo?</h4><p>Ustwo Nordics is a digital product design studio; It is the Scandinavian branch and second studio of a larger studio group with other offices in London, New York, and Sydney. It was originally founded in London by best friends Mills and Sinx about 10 years ago.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WbNXM3MVC5xhQVdE8zpqZA.jpeg" /><figcaption>The main social area in the Malmö studio</figcaption></figure><p>Since its inception, ustwo has grown to become one of the world’s most highly regarded digital design studios, consistently winning well-known clients such as Google, Ford, Samsung, and Adidas. The studio group is perhaps most well-known for creating the Apple Design Award-winning game, <a href="https://www.monumentvalleygame.com/mv2">Monument Valley</a> –although their <a href="https://www.ustwo.com/work/ustwo-games/">Games division</a> has since become a separate entity.</p><p>Ustwo remains as one of the only independent digital design agencies left. Their primary competitors, such as IDEO, Frog, DesignIt, or Method, have all been acquired by larger parent companies.</p><h4>Internship Goals</h4><p>Ustwo’s impressive reputation within –as well as their relationship with– the consumer technology industry was the primary reason why the agency was one of my top choices for which to complete my internship.</p><p>My primary goal during the internship was not necessarily to improve upon my specific skills as an interaction designer. Rather, it was to act as a sponge, absorbing organizational processes and/or work ethic that I could employ in my upcoming graduation project and beyond.</p><p><strong>Organization and Process</strong></p><p>Prior to ustwo, I had worked with several other companies –either as an intern or freelancer– during my summers. While each of these companies offered a unique learning experience, they left something to be desired. I had, in fact, never worked for a company with over ten employees.</p><p>I wanted to see what it was like to work at a more sizeable company. Ustwo as a whole employs approximately 300 people. And their studio in Malmö employs 70 of them (making them the second-largest after London).</p><p>My goal to learn more about organizational tactics and processes was therefore driven by ustwo’s relatively large body of employees. How might the way they treat employees or organize projects differ from a company of 10 employees? I had no idea, and so I was excited to find out.</p><p><strong>Client Communications</strong></p><p>While I had worked with clients previously as part of university projects, doing the same on behalf of a design agency could introduce a new set of client-communication standards or protocols that I had not considered before.</p><p>I wanted to practice communicating with clients with whatever new considerations might arise in an agency such as ustwo. My hope was that I would become a more efficient communicator and collaborator, which could help me push the conversation in a positive direction as I embark on future projects.</p><p><strong>Interaction Design</strong></p><p>I mentioned previously that improving on my specific skills as interaction designer would not be my primary goal, but I had to expect that new learnings would inevitably come to fruition as I worked on projects at ustwo. Might ustwo have a different definition of interaction design than the one I have found during my education?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*92rZdJkbbfIVITs8YFQ3tg.png" /></figure><h3>Contributions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I0q6O9b76_RY3qtjuD3W8g.jpeg" /><figcaption>Ringing the bell for winning the project pitch</figcaption></figure><p>I was assigned to a <a href="https://www.ustwo.com/work/alk">client project</a> with a subsidiary of <a href="https://www.alk.net/">Allergy Lab København</a> (ALK) called <a href="https://klarifyme.de/">klarify.me</a>. The goal was to explore how ALK could provide a user-friendly and personalized service product that delivers pollen counts, allergy information, and air quality data. The resulting app is called <a href="https://app.klarifyme.de/uk">Klara</a>, now live on <a href="https://play.google.com/store/apps/details?id=me.klarify.klara&amp;pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBadge-Mar2515-1">Google Play</a> and the <a href="https://itunes.apple.com/gb/app/id1380057946">App Store</a> in Germany and the UK.</p><h4>Agile Process</h4><p>This would be my first time working with an Agile process on a project. While I have worked with design processes and ‘Lean Startups’ in the past, Agile introduced a new set of structures. Specifically, my team would work in two-week sprints, each concluding with a sprint demo (client presentation). We would start every day with a team ‘stand-up’ (meeting), when we would discuss what we were doing that day.</p><h4>Brainstorming and Collaboration</h4><p>When I first joined the project, it was in its infancy, having only been active for about a week until I arrived. Following a briefing by the ustwo team on their progress up to that point, we all bounced several ideas back and forth. I sketched out some concepts for the onboarding process, as well as some hunches that were swirling around my head. I took it as good start, but it was admittedly hard to tell without the problem being clearly defined at that point. Regardless, the others on my team seemed to be appreciating my input.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*6UpVA8SVT7JID8WGgfNrKg.gif" /><figcaption>Publishing the app</figcaption></figure><p>While the developers would generally participate in such discussion during the first couple weeks, the team’s assigned roles such as as UX Designer, Project Owner, or Developer would eventually become more pronounced.<br>I would continue collaborating in this fashion throughout the course of my internship, offering input and debating ideas related to anything from the app’s search functionality, to whether or not we should place titles in the tab bar in order to increase usage rates (they should), to enforcing brand alignment throughout the product.</p><h4>Client Collaboration</h4><p>Our clients at ALK were exceptionally open to collaborating on the project. Their representatives would regularly commute between Copenhagen and Malmö and work with us at the ustwo office. Our clients really felt like a part of the team. I really enjoyed that level of collaboration, as it allowed me to get a lot of practice communicating with them. Expectation management suddenly became a very critical part of my process.</p><h4>Notifications</h4><p>Amidst the team’s push to make Klara more personal to users, implementing push notifications was seen as a relatively low-hanging fruit –meaning it wouldn’t require loads of resources to implement. This eventually led to a series of discussions about when to push notifications to the app’s particular user base. We also had to consider the particular goals of ALK in determining what these notifications should say or recommend –or what information they should ask for.</p><h4>Widgets</h4><p>Prior to working on notifications, we explored the potential of widgets. While this little project was mostly by client request, I designed some mockups for the client demonstration meeting. In order to do so, I had to adapt the existing design language to use system fonts, stronger colors, as well as making certain spacing-adjustments.</p><h4>Side Projects</h4><p>During the course of my internship, I worked on two side-projects in parallel to the continuing design and development of the app. The primary function of first project was to ████████ ██████ ███████ ███████ ████ ██ █████ ████ ██████ █████████ █████████ ███████ ███████. The second project focused on ██████ ███ ███████ ████████ █████ █████████ ████████.</p><p>Unfortunately, that’s about all I can disclose for the time being.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FXSvEiht5eLeSI%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FXSvEiht5eLeSI%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FXSvEiht5eLeSI%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="271" frameborder="0" scrolling="no"><a href="https://medium.com/media/e6a6c0f61d79730f0e3b98d41477fae2/href">https://medium.com/media/e6a6c0f61d79730f0e3b98d41477fae2/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*92rZdJkbbfIVITs8YFQ3tg.png" /></figure><h3>Learnings</h3><h4>Cutting Corners</h4><p>When working on projects prior to my internship at ustwo, I usually took a more reckless approach of just designing and building everything I could in the shortest time possible. Now, after having worked at a more organized company, I have become much more familiar with the allocation of resources required to ensure that a project stays on track. While I still dream big, I understand now that focusing on getting perhaps only a couple features right for a minimum viable product is an extremely viable strategy. Going forward, I would like to be much more purposeful in determining which features carry the most value –for users and stakeholders alike.</p><h4>Communicating Effectively</h4><p>Very much related to cutting corners, learning communicate effectively was certainly a major takeaway for me. The most obvious example of this would be to be more conscientious about what a discussion needs in order to move forward. Contrary to a small startup, in a large company such as ustwo, adhering to the subject of a meeting becomes vital for upholding order. This applies especially to client meetings, when discussions can be extra sensitive.<br>I actually think we could have benefitted from organizing more client socials earlier in the process, as it contributed significantly to a more casual team morale. It’s certainly something that I see myself paying more attention to when collaborating with clients in future projects.</p><h4>Pros and Cons of Agile</h4><p>Compared to a traditional waterfall structure, Agile is useful in circumstances where the end-goal of a project is uncertain and ever-changing. While I’m not going to dive into the details about what Agile is (<a href="https://medium.com/search?q=what%20is%20agile">there are plenty of Medium articles for that</a>), I felt that, by the end of my internship, I had some idea of its benefits and drawbacks. As someone who likes to think in terms of the big-picture, my biggest concern would be maintaining long-term goals in spite of the amount of ambiguity that Agile provides.</p><h4>Weighting Velocity</h4><p>At the end of every sprint, the team coach would estimate the team’s capacity to do work by comparing the amount of tasks completed with their individual difficulty. After several sprints, we would start to have an idea of the rate of completion –in this case, dubbed velocity– and thus the likelihood of meeting deadlines set between us and the client. While at first I was sceptical, now I find that using velocity to estimate a team’s ability to complete a project is actually very useful. It is something I hope to leverage for my graduation project.</p><h4>Talent</h4><p>The level of experience and talent at ustwo Nordics was above and beyond most other companies I have worked for; the team working on Klara was, in fact, the most senior in the office. So, while my own responsibility was consequently reduced, I spent a lot of time listening to and learning from others. The connections I have made have been incredibly strong, and I’m really looking forward to building on them when seeking future opportunities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tpeiEyp-ddc2UBOkR35r5A.png" /><figcaption>Playing a game of kubb with the clients</figcaption></figure><h3>Conclusion</h3><p>All in all, in spite of its ups and downs, I think interning at ustwo has been a vastly rewarding experience. Ustwo’s more traditional, segregated roles, urged me to face myself and consider who I am and where I see my own role going forward. While working in a more typical UX Designer role is a very good fit for me, I cannot help but to miss working with emerging technologies and cutting–edge interactivity. My internship at ustwo seemed to affirm what I was perhaps avoiding all this time –that perhaps UX Design in itself does not work towards satisfying my career ambitions. In the corporate world, it touches on but a sliver (not necessarily in a bad way) of the breadth of subjects which I have studied at University.</p><p>This only makes me more excited to work on my graduation project. I look forward to discovering how my internship has truly changed my approach in my own projects. A big reason for my excitement is being able to forget about tallying work–hours, at least for a few months. That means a lot of late nights.</p><p>Onwards!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*92rZdJkbbfIVITs8YFQ3tg.png" /></figure><p><a href="http://www.paulnylund.com/">Paul Nylund</a> is an Interaction Design Engineer / Creative Technologist with more than 7 years industry experience from Los Angeles to New York City, to Denmark, Norway, and Sweden. Working on bringing the future into present tense through functional design and hardware / software engineering.</p><p>See more of his work at <a href="http://www.paulnylund.com/">www.paulnylund.com</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2817af659e5d" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/what-i-learned-during-my-internship-at-ustwo-2817af659e5d">What I Learned During my Internship at ustwo™</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design is Not Aesthetic.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.prototypr.io/design-is-not-aesthetic-a1cdc9c004d3?source=rss-caaef21a11df------2"><img src="https://cdn-images-1.medium.com/max/2600/1*o9A5uTcfWZ2nc3epHe_LRg.jpeg" width="4497"></a></p><p class="medium-feed-snippet">I want to talk about something that&#x2019;s been bugging me lately. While design is discussed in great magnitude across the internets, I&#x2019;ve&#x2026;</p><p class="medium-feed-link"><a href="https://blog.prototypr.io/design-is-not-aesthetic-a1cdc9c004d3?source=rss-caaef21a11df------2">Continue reading on Prototypr »</a></p></div>]]></description>
            <link>https://blog.prototypr.io/design-is-not-aesthetic-a1cdc9c004d3?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1cdc9c004d3</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Wed, 27 Sep 2017 21:30:39 GMT</pubDate>
            <atom:updated>2018-08-14T11:27:16.283Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Making, Post-2016]]></title>
            <link>https://medium.com/@paulnylund/making-post-2016-dc2b3194edaf?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc2b3194edaf</guid>
            <category><![CDATA[making]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[2016-election]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Wed, 30 Nov 2016 01:35:41 GMT</pubDate>
            <atom:updated>2018-08-14T11:28:19.586Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XmULFspq7zoJk2d-A6DH8Q@2x.jpeg" /></figure><p>I watch the late November sun set over a peaceful Danish landscape. The scene is still. My mind is racing.</p><p>It has without a doubt been a tumultuous year -precarious political situations and increasing uncertainty surrounding the environment are trends that will continue to provoke effect on the near and far future. 2016 has left a mark on me in ways I couldn’t have predicted, in that I feel as though my perspective (of society) on which I have relied has been promptly shaken. And this has had an effect on how I approach my work. A year ago, I dreamt of landing a dream job in tech in Northern California, floating on a bulletproof safety net. Today, however, I am learning that I can no longer rely on such a safety net and instead must pursue greater self-governance. No institution can be taken for granted any longer.</p><p>As I have steadily unrooted myself from any one culture over the last three years, it has become increasingly clear to me that globalization is catalyzing profound and sweeping changes in the ways information flows freely amongst humans. I have realized that I cannot rely on governments or corporations to decide upon emerging trends. Institutions are rapidly losing their power due to a large increase in information flow, and control over information is instead being transferred to the masses.</p><p>Now, more than ever before, it is vital to create products that speak to people -or that let people speak to them- on a level that is truer to their own humanity. Technology has the potential to supplement, rather than to provide, means of communication. While it seems as though people are becoming more divided, there is quite an opportunity to find ways of bringing people closer together. This can be achieved by looking past established trends or conventions: past gamification, past social affirmation, past temporary information, et cetera. There is more potential in technological products than what is popularly embraced today. Technology can be an extension of ourselves -our thoughts, and I want to make it my mission as a designer and engineer to realize that very idea.</p><p>In an uncertain world, the opportunities you create yourself are the most important of all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*92rZdJkbbfIVITs8YFQ3tg.png" /></figure><p><a href="http://www.paulnylund.com/">Paul Nylund</a> is an Interaction Design Engineer / Creative Technologist with more than 7 years industry experience from Los Angeles to New York City, to Denmark, Norway, and Sweden. Working on bringing the future into present tense through functional design and hardware / software engineering.</p><p>See more of his work at <a href="http://www.paulnylund.com/">www.paulnylund.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc2b3194edaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jumping the Fence]]></title>
            <link>https://medium.com/tokeninc/jumping-the-fence-cb6d8b823651?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb6d8b823651</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[kyn]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ideo]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Thu, 24 Nov 2016 21:39:40 GMT</pubDate>
            <atom:updated>2017-02-07T09:44:52.472Z</atom:updated>
            <content:encoded><![CDATA[<p>After defining the problem, this portion of the project was geared towards converging on a singular idea. In order to do so, we needed to consider all of our initial hunches, while adding more ideas to the mix.</p><h4>Starbursting (WWWWWH)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7_v5OHBn6z0Uq33x4DIACg.jpeg" /><figcaption>It’s called starbursting, because StarBurst are delicious.</figcaption></figure><p>While the problem statement certainly gave us a more pointed direction, we needed to transform it into a specific set of questions, in the form of who, what, when , where, why, and how. We chose this method in order to make sure that we were exploring every potential fault in the project’s scope and to lead us to be inspired prior to our initial brainstorming session.</p><p>In many of the questions, we referred a lot to “it” — this is a pseudonym for the scope-as-product. A few of these, sometimes intentionally provocative, questions were: “Who could it piss off?”, “What is the incentive?”, “When can we interrupt other people?”, “Where could it be purchased?”, “Why is this important in people’s lives?”, “How would it be percieved by others?”</p><h4>Initial Brainstorm</h4><p>Following the starbursting (?), we took inspiration from the many questions and sketched down as many ideas as we could muster, interspersed by rounds of listening to each others’ thoughts and further open questioning.</p><p>The ideas from the brainstorm, in addition to our hunches (ideas generated throughout the process, especially following user research and interviews), were then sorted into categories defined by similarity.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4yx3JD-Iwhg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4yx3JD-Iwhg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4yx3JD-Iwhg%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/64c7bbfe9f74ecdd03c8e11d23e6af50/href">https://medium.com/media/64c7bbfe9f74ecdd03c8e11d23e6af50/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MgOvCm2oXgwyX03tfstASg.jpeg" /><figcaption>Hunches and initial brainstorm ideas sorted into categories</figcaption></figure><h4>Comparing new Ideas to Hunches</h4><p>The categories were then given titles, consequentially unifying groups of ideas into catchy soundbytes. We drew a table on the whiteboard and attempted to draw comparisons between our hunches and our initial brainstorm. The purpose of this was to pull inspiration from throughout our process, leaving no stray thought behind. Identifying core themes that underlie the process is integral to maintaining a solid footing. The main topics that emerged after this comparison were “Reactive Architecture” and “Grouping People Together in Public Spaces”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tOVI7wnUWzpr71BI3jWOdA.jpeg" /></figure><h4>Connection Whale 🐋</h4><p>Okay, so this didn’t help us. We were hoping to draw more connections between the topics, but we ended up drawing a useless whale instead. It’s kind of cute though, so we might have to write a paper on this newfangled design tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*63Za3y751EurmdwNiZW9fQ.jpeg" /></figure><h4>2X2 Framework</h4><p>Enter the 2X2 framework: Keeping in mind the topics, “Reactive Architecture” and “Grouping People Together in Public Spaces”, as a result of categorizing our ideas, we defined multiple metrics by which to evaluate the latter.</p><p>First, we defined the horizontal axis as directness of communication (eg. How much friction between information and the user) and the vertical axis as the proximity to body (eg. Whether it is something users interact with on their body or within the environment).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*illvoFIsK2v7kE4HYua4ew.jpeg" /></figure><p>After plotting each idea on these two axes, it was clear that the majority of them communicated information within the environment — not on the body. Additionally the ideas were evenly dispersed on the communication directness axis. While plotting our ideas by these metrics told us a lot about what we had to work with, we weren&#39;t any closer to understanding why one idea might be more relevant than any other.</p><p>We then chose to define two new axes: The horizontal axis, inspired by <a href="http://www.myersbriggs.org/my-mbti-personality-type/mbti-basics/">Myers-Briggs’ psychological traits</a>, represented the spectrum of perceiving and judging said ideas, and the vertical axis represented the spectrum of passive to active communication with each idea. This gave us a much broader distribution of ideas, which aided our discussion in that it gave each idea a greater argument for the purpose it serves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ke74rjwZuLm6yywT-FBaw.jpeg" /></figure><p>To move on, we evaluated the axes against “Reactive Architecture” and “Grouping People Together in Public Spaces”. The concept of reactiveness felt important to us, due to our goal of increasing engagement between seemingly unwilling strangers in Denmark, which led us to narrow in on those ideas within “passive” and “perceiving”.</p><p>We repeated the same 2X2 framework only to the ideas in the lower-left quadrant. This was effectively the ultimate moment of convergence in the arc of our design process. By plotting these more focused ideas by the same perceiving-judging / passive-active metrics, it became much easier to see similarities between them. We, again, gave a name to each group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FiarkyYxUv5QeTd_qddc1w.jpeg" /></figure><p>Tags and/or Directions.</p><p>Adaptive Architecture.</p><p>Pushing and/or Pulling People.</p><p>Wearable Feedback.</p><p>Broadcasting Emotions and/or Information.</p><p>…But what could this all mean?? Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb6d8b823651" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokeninc/jumping-the-fence-cb6d8b823651">Jumping the Fence</a> was originally published in <a href="https://medium.com/tokeninc">tokeninc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We have a problem.]]></title>
            <link>https://medium.com/tokeninc/we-have-a-problem-95f23acb4795?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/95f23acb4795</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[kyn]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 13:15:12 GMT</pubDate>
            <atom:updated>2017-02-07T09:45:17.472Z</atom:updated>
            <content:encoded><![CDATA[<p>In order to narrow down the scope of our project, we decided to offer a survey to our collective network and the interaction design community on Reddit. In addition to probing respondents for basic identity categories such as age, gender, race, and socioeconomic class, we asked them the following questions:</p><p><em>‘Where were you primarily raised?’</em></p><p><em>‘Do you currently live in Denmark?’</em></p><p><em>‘What was the population of the area in which you were primarily raised?’</em></p><p><em>‘How often do you talk to people you don’t know?’</em></p><p><em>‘How comfortable are you talking to people you don’t know?’</em></p><p><em>‘How long does it typically take before you are able to feel comfortable around new people? What is your reasoning?’</em></p><p><em>‘Would you mind if a stranger started a conversation with you? Why or why not?’</em></p><p><em>‘How do strangers typically react if or when you start a conversation with them? Is it generally a positive reaction?’</em></p><p><em>‘Is there a cultural norm in your country of origin advising for or against socializing with strangers. Do you agree?’</em></p><p><em>‘Why would you start a conversation with a stranger (eg. on the metro, at the market)?’</em></p><p>The purpose of asking these types of questions was to gain insight into how people might feel when they are met with the opportunity to speak with a stranger. In the end, we collected 50 responses, which made us ecstatic (that’s, like, a lot, isn’t it?)! We then dove into the answers and began to fish for meaningful correlations.</p><p>As the vast majority of our survey’s respondents were caucasian, the factor of race had to be ruled out (it’s still a very important issue, obviously). 1/3 of respondents were raised in an area with a population of over 100k people, although population did not appear to have any influence on their answers — neither did socioeconomic class. The vast majority of respondents were under 35-years-old.</p><p>What did matter was whether or not the respondents are currently living in Denmark and whether or not they identified as male or female. Thereby, we decided to generate 4 main user profiles; We calculated the average comfortability (1–5) with conversing with strangers and the average frequency at which people claim to do so.</p><p><strong>Male living in Denmark</strong></p><p>Comfortability: 2.0</p><p>Frequency: 2.81</p><p><strong>Male living outside of Denmark</strong></p><p>Comfortability: 3.69</p><p>Frequency: 3.23</p><p><strong>Female living in Denmark</strong></p><p>Comfortability: 3.0</p><p>Frequency: 3.4</p><p><strong>Female living outside of Denmark</strong></p><p>Comfortability: 3.76</p><p>Frequency: 3.55</p><p>What was especially striking was how people outside of Denmark do not seem to engage with strangers as much as they are comfortable with, while the people living in Denmark engage more with strangers than they are comfortable with. What this tells us is that it may be more important to increase comfortability with engagement in Denmark, and more important to increase frequency of engagement outside of Denmark. Because we had previously converged on tackling the Danish market, it is clear that we must pursue increased comfortability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DlFmiiSY_v8UewZa0sLKTw.jpeg" /><figcaption>The Dimensions of Self are helping us visualize the user profiles we are working with.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3YmP8JT9tUQPxdg5KjjBDg.jpeg" /><figcaption>Meta.</figcaption></figure><p>Regarding the more qualitative answers, we took notes on the responses and identified common threads. One of the most notable features was that people generally wanted to start conversations with strangers for the purpose of acquiring knowledge or new experiences. While people are weary of engaging strangers for fear of disturbing the strangers’ peace, most of our respondents said they wouldn’t mind if a stranger engaged them. This tells us that there is likely a strong cultural stigma against casual engagement — especially in Denmark. Respondents are fearful of being rejected and read tentatively into others’ body language to determine whether or not they should engage.</p><p>This is a plethora of information that is certainly worth exploring during our brainstorming sessions in the coming weeks. The big question is now…</p><blockquote>How can we increase frequency of engagement between strangers in Denmark, as a consequence of increased comfort levels?</blockquote><p>A higher level of communication will result in increased sharing of information, spurring healthier economies and happier people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95f23acb4795" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokeninc/we-have-a-problem-95f23acb4795">We have a problem.</a> was originally published in <a href="https://medium.com/tokeninc">tokeninc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where the heck is Apple going?]]></title>
            <link>https://medium.com/@paulnylund/where-the-heck-is-apple-going-87750cba3c33?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/87750cba3c33</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[macbook-pro]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[microsoft-surface]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Sat, 29 Oct 2016 16:00:53 GMT</pubDate>
            <atom:updated>2018-08-14T11:28:01.069Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Rd0obY1LKtZlaZCNwrx4A.jpeg" /></figure><p>How does the Touch Bar fit into any grand narrative? What does this newfangled feature tell us about future hardware? Are we destined to dig in our heels and hold onto the archaic form factors of past gadgets?</p><p>Apple appears to be confronted with the paradox of its self-fulfilled prophecy that good design should be pervasive. Now that Apple products are indeed pervasive, the quest to fulfill this prophecy seems to be coming to a confusing halt. Good design is now pervasive in tech—just see what Microsoft and Google are up to these days.</p><p>Take Microsoft, for instance. Their lineup of Surface devices promises true-to-life, paper-like productivity devices, while Hololens is making strides in augmented reality. Microsoft’s new products promise a more human-friendly future, one where technology blends in all while becoming more tangible. Tired of sitting at your desk? Fold up your Surface Pro and head outside. My point is that the Surface suite is highly adaptable. The devices are all <em>surfaces</em> with optional accessories.</p><p>Apple’s new MacBook Pro is a largely unfocused device with many built-in accessories. The company has managed to pack three different input devices into a single gadget: a trackpad, keyboard, and now, the Touch Bar. It’s like they haven’t been able to unify their vision. What is their long-term game-plan? Will we have to come to expect the trackpad, keyboard, and Touch Bar as default accessories in every future iteration of the MacBook until 20xx?</p><p>The fact that Apple is unable to commit to the abolishment of the 3mm headphone jack on the Mac speaks volumes about their ability to unify their plethora of ideas. I’m starting to have doubts that there’s any real risk-taking at Apple anymore. They’ve become too comfortable — too static. Microsoft is rising from the grave, because their only option right now is to take risks or risk becoming obsolete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*92rZdJkbbfIVITs8YFQ3tg.png" /></figure><p><a href="http://www.paulnylund.com/">Paul Nylund</a> is an Interaction Design Engineer / Creative Technologist with more than 7 years industry experience from Los Angeles to New York City, to Denmark, Norway, and Sweden. Working on bringing the future into present tense through functional design and hardware / software engineering.</p><p>See more of his work at <a href="http://www.paulnylund.com/">www.paulnylund.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87750cba3c33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eureka]]></title>
            <link>https://medium.com/tokeninc/eureka-2d1ce523f8e4?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d1ce523f8e4</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ideation]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[kyn]]></category>
            <category><![CDATA[ideo]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Fri, 14 Oct 2016 09:39:08 GMT</pubDate>
            <atom:updated>2017-02-07T09:45:32.975Z</atom:updated>
            <content:encoded><![CDATA[<p>So, we’ve finally settled on a topic we want to tackle.</p><p>It all began with sorting our findings into different categories. This gave us a more abstracted overview of the different topics that were brought up so far. Perhaps ironically, sorting the post-its only made us more uncertain. The scope of the project appeared to be extremely broad and unfocused. But we had to move forward. Scroll on down…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5qlySV1I4m1SxCKFMrMLg.jpeg" /></figure><p>Each of the team members chose 5 of the most compelling and encompassing post-its, which we then separated from the rest. Now we had a more concise and manageable collection of topics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mdFQKdKpgXh-zkljdZRFVw.jpeg" /></figure><p>We began to discover the similarities: community, collaborating with neighbors, collective intelligence, integration, biodiversity, responsibility and accomplishment, culture, tangibility, pervasiveness, immunity. These words all pointed towards a grander idea:</p><blockquote>Increasing social interaction in urban areas, using pervasive technologies.</blockquote><p>The next step will be to identify themes and to formulate insight statements. This should allow for a more careful exploration of the problems involved before we dive into the initial ideation phase.</p><p>Stay tuned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d1ce523f8e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokeninc/eureka-2d1ce523f8e4">Eureka</a> was originally published in <a href="https://medium.com/tokeninc">tokeninc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interviews]]></title>
            <link>https://medium.com/tokeninc/interviews-ecaeae3427e?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecaeae3427e</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[urban-agriculture]]></category>
            <category><![CDATA[air-pollution]]></category>
            <category><![CDATA[kyn]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Wed, 12 Oct 2016 08:31:40 GMT</pubDate>
            <atom:updated>2017-02-07T09:46:02.448Z</atom:updated>
            <content:encoded><![CDATA[<p>We are wrapping up the week with an aura of satisfaction. After conducting some very insightful expert interviews, we feel like we are getting ever closer to defining a problem.</p><p>The subjects interviewed are Anders Lauerson of the Øhaven community garden in Aarhus, Ethan McMahon of EPA’s Smart City Challenge in Washington, D.C., and ‘urban ecology’ expert Ariel Levi Simons in Los Angeles, CA. We also sent out questionnaires to Øhaven users, urban agriculture interest groups, and to subjects of air pollution. Next week, we plan to speak with participants of SØF (a community-driven distribution channel of locally grown organic produce in Sønderborg, Denmark). We would like to thank each and every one of the participants, in addition to Ace Kremmer for his wonderful support.</p><p>The goal is now to process and code the data we retrieved from the interviews and questionnaires. This involves writing bits of information on stickies and grouping these stickies by similarity. It should give us a more definitive understanding of the problems at hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Um1Vpb71EVfAUqwF2ssvw.jpeg" /><figcaption>Pallet boxes at the Øhaven community garden</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IztPW0XrcH3anqwMkUf5Pw.jpeg" /><figcaption>Rooftop greenhouses in the background</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0eT08tslO6MWv5aYjDUiqA.png" /><figcaption>Michael taking notes on the interview with McMahon</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QWH7kh7HQi5PzJ2C4a1N1Q.jpeg" /><figcaption>Post-processing the interviews</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecaeae3427e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokeninc/interviews-ecaeae3427e">Interviews</a> was originally published in <a href="https://medium.com/tokeninc">tokeninc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello World]]></title>
            <link>https://medium.com/tokeninc/hello-world-450feccec64e?source=rss-caaef21a11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/450feccec64e</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[ideo]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[hello-world]]></category>
            <dc:creator><![CDATA[Paul Nylund]]></dc:creator>
            <pubDate>Fri, 16 Sep 2016 19:24:31 GMT</pubDate>
            <atom:updated>2016-09-16T19:37:17.220Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ozYsr3EF_0D63ywrxZYIpg.jpeg" /><figcaption>Spazzing out in our sweet new office. Photocredz: Michael Nissen</figcaption></figure><p>‘Token Inc.’ is Interaction Design students Mads Henriksen, Michael Nissen, and Paul Nylund. The theme, courtesy of the <a href="http://www.sdu.dk/">University of Southern Denmark</a>, is welfare technology. Here, we will be posting updates on our design process.</p><p>The focus today has been on organization: setting up <a href="http://www.trello.com/">Trello</a> boards, <a href="http://drive.google.com/">Google Drive</a>, <a href="http://www.any.do/">Any.Do</a>, and this very fancy publication. In the real world, our progress will be largely driven by IDEO’s <a href="http://www.designkit.org/">Design Kit</a> — under the <a href="http://t.umblr.com/redirect?z=http%3A%2F%2Fwww.methodsandtools.com%2Farchive%2Farchive.php%3Fid%3D32&amp;t=Yjc4ZjM2M2MwODJmYjA2NDBjMTBjYjhmZTVkY2Q1MTA3ZWQwMDY5MSxvUFZ2emlubA%3D%3D">Unified Process</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=450feccec64e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokeninc/hello-world-450feccec64e">Hello World</a> was originally published in <a href="https://medium.com/tokeninc">tokeninc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>