<?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 Alex Penman on Medium]]></title>
        <description><![CDATA[Stories by Alex Penman on Medium]]></description>
        <link>https://medium.com/@penxman?source=rss-8e3881a2c75e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MXgpW1pSfLkSJcj04Al_ww.jpeg</url>
            <title>Stories by Alex Penman on Medium</title>
            <link>https://medium.com/@penxman?source=rss-8e3881a2c75e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:59:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@penxman/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[CIID 6 Month Reflection]]></title>
            <link>https://medium.com/@penxman/ciid-6-month-reflection-36653f32c172?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/36653f32c172</guid>
            <category><![CDATA[ciid]]></category>
            <category><![CDATA[ciid-idp]]></category>
            <category><![CDATA[ciid-idp-2018]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Tue, 16 Oct 2018 16:29:17 GMT</pubDate>
            <atom:updated>2018-10-16T16:29:17.266Z</atom:updated>
            <content:encoded><![CDATA[<p>“Foraging is a good business model…free stuff…” — Aram</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PuCVqduenhyCBjS9vs9e1A.jpeg" /><figcaption>CIID Go Boats to celebrate the end of reflection week.</figcaption></figure><p>We’ve made it halfway through the year already… it’s almost time for industry/final projects but luckily I feel ready for them. The past two weeks were spent reflecting on what I’ve learned about myself and the design process, where I want to go in the future, and possible directions to explore going forward. <a href="https://www.askthesherwins.com/meet-the-sherwins/">The Sherwins</a> returned once again to guide us through our reflection week and help evaluate our peers. Getting somewhat of a sense of direction post-CIID was very calming for me and has given me a clearer head going into our last stretch of school.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1U_3VcHf9qfJehKBWGcGog.png" /><figcaption>Intro slide for my mid-way presentation, a description of me before attending CIID.</figcaption></figure><p>For my <a href="https://drive.google.com/file/d/1YvTD7SYID8rJtqMwdl_Fz2zV_KJqiBDJ/view?usp=sharing">mid-way presentation</a>, I actually prepared and designed some slides rather than using boring templates! I originally intended to just fill the slides with minimal text and spend most of the time talking, but while working through what I was going to say, I came upon a quote from our teacher Priscilla during Video Interactions that I really liked: “Inject your references into your work.” It was here that I realized it would be a missed opportunity for me to not try something new with my presentation and design it in a way I thought was reflective of my own personal taste.</p><p>I started off using xerox’ed pictures to give it an old zine feel but it quickly was apparent the content wasn’t lining up with the images in a way I liked. I then decided to use patent diagrams and drawings from old software publications, two things I have been spending a lot of time browsing lately, to drive the aesthetics. So I set out scouring <a href="https://www.are.na/">Are.na</a> for hours to find the perfect images. This ended up working really well. I paired minimal, bold text with diagrams that were humorous, informative, and puzzling all at the same time. Throughout the entire presentation, I didn’t acknowledge the diagrams at all and left it up to interpretation of the audience, which from feedback, apparently was a great touch.</p><p>Ultimately, I’m very happy with the way it turned out and the experience I gained with giving a 30 minute presentation. Talking through long speeches has never been a problem, but knowing that I can confidently pull in other inspirations to build a more engaging presentation is a nice feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3RTtXjV9-sRbpR-BG9aHA.png" /><figcaption>Feedback slide from my presentation. I talked about how regular feedback has been helpful.</figcaption></figure><p>Up until this point, my posts on here and things I’ve been thinking about in my head have mainly been about how to improve my own interpersonal skills. Things like working in teams, speaking up, vocalizing my opinions, and everything generally related to my natural shyness. The time I’ve spent on that has definitely helped me improve fairly easily this year. Reflection week came on as surprisingly relaxing for me since a lot of these thoughts I’ve been thinking about since before the first week of school even started. The feedback from my peers has given me some confirmation that I’m making progress in the right direction and clearly outlines things I can improve further. So while this path is not complete, what needs to be done in regards to keeping up with the interpersonal side of things is solid in my head. I’m hoping to spend the next half of the year really focusing in on my design skills and process.</p><p>The main theme from my feedback on how to be a better designer was about developing my own taste. I got a few good starting points on how to improve this thanks to <a href="http://ciid.dk/education/management/aram-armstrong/">Aram</a>, the Sherwins, my peers, and other faculty.</p><ol><li>Use your influences: This seemed to be a big one for me and was briefly touched upon earlier with how I went about creating my presentation. I got a lot of encouragement to use outside resources in how I approach projects, even if it isn’t immediately clear how the two will link up. Whether it is something I had been thinking about for the past few days or a few years, being able to use resources that I gravitate to in what I do will help build up my own style. Using mid-way presentation as an example again, many people told me that the visual style felt like it fit me. This wasn’t something I had explicitly thought of during the process of making the slides but just from the nature of using ideas that I had an interest in, things fell in place.</li><li>Design is not “only” based in graphics: Aram recommended that I start using things such as mixtapes to help me think about approaching new projects. Creating a series of songs can work as a type of auditory mood board. Even if it’s just for me, being able to define clearly what I work towards in a project is helpful. Similarly, he also suggested maybe making a mini zine at the beginning of each project to even further define the directions to take.</li><li>Doing things with intention: Probably the hardest one on the list to get right and I’m sure a lot of people struggle with it as well. I think a lot of things I do are usually by chance and on the spot. While I do think this has suited me well with approaching things I work on, I do lose out on the intentionality and it’s apparent when I start to try to explain why I did things a certain way. Being intentional from the beginning will help guide my process from an early stage in a way that feels natural to me. It also opens up for a deeper level of critical thinking and understanding of what works (or doesn’t work).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8cHRdTXHMl4t6WYpp_JbXg.jpeg" /><figcaption>CIID Go Boat with Rina, Jing, and Josh.</figcaption></figure><p>I think I have a clear path set out for me through the end of the year to work on my design skills. It feels very empowering to be able to pull in things you like to influence your work and help you. This is something that I don’t think I could have done in software engineering — at least not as obviously. It’s exciting. I’m sure I’ve mentioned this in previous posts but software engineering existed solely as a career option that was viable for me, not fully enjoyable. I found ways to find it fun but it never really held my attention. Being able to mix actual interests with something I can do as a career is one of those things that feels more and more obtainable as this year carries on…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O67T0YbJRyAwCCuMreFPEA.jpeg" /><figcaption>Went to the Louisiana with my parents (these are not my parents).</figcaption></figure><p>On the side, I’m really hoping to start posting more <a href="http://antiradioonline.tumblr.com/">ANTI playlists</a> again. Our web domain recently expired and I decided not to renew it considering nothing had been posted in over a year. Staying motivated to post constantly is tough but I think cutting back on the pressure to post every week and trying to go once a month or so will help out. Inspired by <a href="https://rui.cool/">Rui Paz</a>, I’m also wanting to start doing seasonal playlists and designing imagery for them. This is a step towards putting Aram’s advice to work, using the music that is influencing me in my design. Not to mention, it will also help practice with my visual design skills. I have one in the works currently and if all goes as planned, will include a small zine release from the summertime months.</p><p>For summer break I went to Prague and Budapest with Jing and Henry. Then traveled back to California for a week to see Bryan and Linda get married. Here are a few pictures:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M58v1HLZhbn-itAJ2WEZ5A.jpeg" /><figcaption>Prague.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Rkx-sD94uBwFYSwcX3O2w.jpeg" /><figcaption>Inukaze (JP) playing at Klinika in Prague.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IurUvWv5KZDqmniU-JoV9Q.jpeg" /><figcaption>Henry ruining (or making) a nice abstract picture.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QqgiIxdjGJF1QAU645uT0g.jpeg" /><figcaption>P’s stuff.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6cUHTrDUJ14vl348ggm03g.jpeg" /><figcaption>Eating KBBQ with P and Matt.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JuwfqpYcO7fuhp1KS_QWMg.jpeg" /><figcaption>The church where Bryan and Linda got married.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*20JlNDGeEUnN5M7N8wWIQg.jpeg" /><figcaption>Set times for Culture Abuse Bay Dream LA record release show. About 100 bands played short, two song sets.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36653f32c172" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID Weeks 12 & 13: GUI]]></title>
            <link>https://medium.com/@penxman/ciid-weeks-12-13-gui-31f2c35d7bfb?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/31f2c35d7bfb</guid>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Wed, 25 Jul 2018 19:33:56 GMT</pubDate>
            <atom:updated>2018-07-25T19:33:56.988Z</atom:updated>
            <content:encoded><![CDATA[<p>“If you use RGB, you might as well use Hex so you can copy/paste faster.”</p><p>We got to focus on “Graphical User Interfaces” for a solid two weeks with Frank Rausch and Timm Kekeritz of <a href="http://www.raureif.net/en/">Raureif</a> based in Berlin. While we all joked about the class being labeled as GUI when most everything in the world has dropped the G and gone with UI, I learned a lot about designing and what makes apps look nice. Frank and Timm were professional teachers and the epitome of German efficiency. They packed in a good amount of content while allowing us the time to design on our own at a leisurely pace. Frank even ended class on Friday at 3:30 after project presentations to let us enjoy the first sunny weekend of the year out on the harbor with some beers!</p><p>In the short span of two weeks, we all came up with app ideas related to water usage in the world and developed nice looking prototypes of them. The constant use of Sketch allowed me to develop my design skills and trust in my instincts a bit more. I came into this class warning my team that I may have an eye for decent design but can’t actually design anything myself. And this was immediately apparent at our first round of prototyping in Sketch. The three of us split up and all designed our main use case and came back together to compare. My designs looked like they were an unpolished version of a 10 year old app. I was pretty sure that there was nothing in my first prototype that we could use for the next phase. Luckily, someone on our team had a lot of visual design experience and was willing to point out what could be good to keep around, despite it looking pretty ugly. It was here that I realized in this first round of designing, what was import was the flow of the user not the overall look of the app.</p><p>Over the next week, I watched the other teammate as he refined our designs. Tweaking things ever so slightly, moving around small details, switching up the colors, making everything look uniform. As soon as he made changes, I would immediately realize that the design was much better and I could make the connection in my head with what he did and what the outcome was. It was a good process to observe. Our team dynamic allowed us to all experiment and each time we went back to Sketch, I could attempt to take what I saw last round and try it out myself. By the end of the week, I felt a lot more confident in my ability to not only articulate what needed to happen in regards to design, but also apply it and make the changes myself. I’m nowhere near an expert in design after this one week, however, I feel much more at ease going in and contributing to design, which is important for the rest of the year. I’m no longer trapped in the world of code.</p><p>Inspiration from lecture:</p><ol><li><a href="http://dougengelbart.org/images/firsts/1967testreport-knee-device.jpg">Doug Engelbart’s knee-controlled mouse</a></li><li><a href="http://www.gianlucagimini.it/prototypes/velocipedia.html">Velocipedia</a> by Gianluca Gimini</li><li>“The only way to experience an experience is to experience it.” — Bill Moggridge</li></ol><p>Things outside of school:</p><ol><li>Carla Dal Forno @ ALICE</li><li>Tarantula</li><li>GY!BE</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31f2c35d7bfb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID 3 Month Reflection]]></title>
            <link>https://medium.com/@penxman/ciid-3-month-reflection-8b5612418b24?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b5612418b24</guid>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Mon, 21 May 2018 14:08:58 GMT</pubDate>
            <atom:updated>2018-09-04T14:32:35.433Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FkK9hOsoZuac0rHkLZYDtA.jpeg" /></figure><p>It’s been three months already and yet everything before CIID seems like a lifetime ago. I think that’s a common feeling with everyone in the class. For me, I think it’s for the better. I’ve felt myself get excited for what I’m working on and have put long hours into projects, something I haven’t done since joining UClass four years ago. At the same time, I’ve focused on paying attention to my emotional needs and recognizing my mental limits.</p><p>Outside of school, I’ve still been exploring the music scene here in Copenhagen. While it’s not as eventful as back in San Francisco, there are a lot of great things going on here. Enough to keep me happy and enough to keep me doing my weekly concert updates for my classmates to keep them informed of good music. I’ve been playing board games more, biking more, and now that the sun has finally returned, have been really appreciating the outdoors.</p><p>It hasn’t been a complete shift into a new person though. I still see myself falling into bad habits every now and then. I’ll get burnt out and waste the night away scrolling mindlessly through social media. Or play hours of Dota just because I don’t feel like leaving the house. I’ll still shy away into a corner in social situations when I’m not feeling like talking much. And I’ll catch myself overthinking my thoughts and not contributing to group feedback. Most importantly, I still haven’t gotten myself to carry my camera around daily. But it’s all a process and the fact that I’m aware of all this keeps me optimistic about the year and my future.</p><p>A lot has been going on, but here are some of the most important things that I have improved on within the last few months:</p><h4>Stepping back and appreciating</h4><p>One thing CIID has taught me is to not go into anything with a set idea of how things will turn out. This doesn’t mean putting your opinions or ways to solve problems aside, it’s more about leaving your mind open to change.</p><p>I’ve caught myself a few times going into a course with a negative outlook on the technologies or topics we were covering and it really doesn’t help at all. All it ever did was slow me down in the creative exploration process. The first time this happened, I was amazed at how excited my classmates got at something I already thought was boring. By stepping back and appreciating the technology, I was able to use it to aid me in my design process rather than constantly fighting with it.</p><h4>Recognizing my strengths and putting them forward</h4><p>One of the things I was struggling with last year was finally figuring out how to speak up for myself and demonstrate the skills I was good at. Throughout the past it’s been so easy for me to hide away from my opinions and go with the decisions of others, even when I was more knowledgeable in something. To me, there was a fine line between constructive suggestions and looking arrogant, and I didn’t know how to navigate it. Being the one person in the class with a formal coding background has helped me with this. I’ve not only been given the opportunity but also forced to make executive decisions around how the code in some of our projects works. It’s helped me take a stronger stance and has transferred into other parts of my decision making and group work process while designing in teams.</p><h4>Working hard but not overdoing it</h4><p>This one is pretty self explanatory. My mom is a first grade teacher and I remember up until 5th grade she kept a tight watch on all the assignments I turned in to school. I always had to go above and beyond what was asked of us and always got A’s on everything. I actually looked through a bucket of old projects my parents saved and could remember working through a lot of them even though most of them were over a decade old. I think I actually enjoyed this work but when I went into middle school in 6th grade, something switched. I had discovered that I picked things up fast. I could pay attention in class, skip homework, and still pass classes with pretty good grades. I focused my time on skateboarding and hanging out with friends every day after school. This started me on a long process of just doing what I needed to get by. It got me real close to failing out of college my freshman year but I made it out and it wasn’t until joining UClass that I would find a spark to work hard and do the best I could. I felt myself fall back into my old minimum effort habits after a year into Renaissance and it didn’t feel good.</p><p>CIID has brought me back into pushing myself when it comes to my work. It feels good but I’ve intentionally tried to keep my mental health at the top of my priority list. It’s helped me keep a nice balance between things. Not just in school but in my social life as well. I’ve tried much harder to be more social and not spend too much downtime at home. But at the same time, I allow myself the space to relax and sit with myself when I know I really need it. It’s felt like my whole life I’ve pushed into one side or the other. Switching between extremes of doing too much and doing too little. It’s nice to know I’m finding a way to balance it all out and it feels much healthier and more productive.</p><p>It’s been crazy so far. In more ways than I want to spend writing in a blog post. Before leaving for Copenhagen, my therapist said at our final meeting that I should keep track of how I’m feeling on a weekly, if not daily, basis. I haven’t stuck to that in a strict way but I’ve kept it in mind as I navigate this year. It’s been nice and I feel like these reflections and posts have been beneficial to me improving during CIID.</p><p>Like I said in the beginning, life before CIID feels like a lifetime ago. And we are only one fourth of the way through the year. It’s been fun and I’m looking forward to the rest. For now, I’ll drop some inspiration and pictures from spring break (I went to Portugal and Switzerland!).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yFQDva57uJ5_izqrHk4n2A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c0v0S7TS1VbLmizMYYJobg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YvIRMpYejSJeTAvd73mohA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CY-TrongdWnGQ4ODOr-noA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lo902fQZaw2QH_GxCCGdqg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PIpdnezvRNQovh4SJ7J7eA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b5612418b24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID Weeks 8 & 9: Physical Computing]]></title>
            <link>https://medium.com/@penxman/physical-computing-8f69946be658?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f69946be658</guid>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Sun, 15 Apr 2018 14:31:51 GMT</pubDate>
            <atom:updated>2018-04-22T12:05:57.537Z</atom:updated>
            <content:encoded><![CDATA[<p>“You do know, you do can.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aZLRyJ7_GmCUzFwgUEO1Fw.jpeg" /></figure><p>Next we began two weeks on Physical Computing split up into two different classes. It was two weeks full of circuits, Arduinos, long nights, pirates, and Italian instructors. The first week, Basics of Physical Computing, was taught by <a href="http://www.ubidefeo.com/">Ubi de Feo</a> and <a href="http://www.pierdr.com/">Pierluigi Dalla Rossa</a>. We used this time to apply some of the skills we learned during Material of Electronics to computing in order to create small projects. The second week, simply titled Physical Computing, focused on a week-long project where we could spend more time developing ideas and aesthetics. Ubi joined us again for the week, this time alongside Dario Buzzini. Here are some highlights from the two weeks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GVP8JQ3MogcXAQykiKKnow.jpeg" /></figure><h3>Week 1</h3><p>I wasn’t too excited for this physical computing course but I think it was from my experience in the past. I’ve only done very simple things with physical components and did not enjoy it too much. Looking back, this was a bad mindset to go into the course with. During the first day of lecture we got to experiment with <a href="https://pierdr.github.io/Tramontana-for-Processing/">Tramontana</a>, a platform to interact with Arduino created by Pierluigi. At first, I only saw the negatives of Tramontana like network issues and some inconsistencies in the javadocs (sorry Pier!). After talking with some classmates who had no experience with physical computing, I found that they were amazed by the technology. The fact that you could upload code to a board then control it with your phone blew them away. And that’s when I stopped to reflect on things. It all is pretty magical when you think about what you can do with fairly simple tools. This complete surprise and excitement from my classmates got me to look at the technology with fresh eyes and actually got me excited to experiment with it. And in the end, I really liked Tramontana. Being able to interface easily with an Arduino board was really helpful and let us make fun little projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vr2xMtLuDZkpQKPpDuYZtw.jpeg" /></figure><p>Our team dove into a very ambitious project during this week. We had the brief to create anything we wanted but only had around 24 hours to do so. After sessions of brainstorming, we came up with the concept of a turntable synthesizer. It would have a platter that spun like a turntable and different “grooves” that corresponded to one of six notes in a scale. Each groove had a laser pointing down from the top to a photo-resistor. You could then place blocks onto the platter and as it spun around and broke the laser connection to the photo-resistor, a note would play. We had a cardboard prototype that we could play with our hands working in the afternoon, but we were not content with just that. And with only 16 hours remaining until our project deadline (including sleep time), we went to work on building the next version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4nP4QsIikFo4ntrGn7PhDw.jpeg" /></figure><p>We drew out a diagram, modeled it in a CAD program, and laser cut the whole thing. This went surprisingly well. We were able to hide the Arduino in the base and ran the wires through the inside up to the lasers on the top bridge. Since our concept relied on lasers shining from the top, we needed to cut the platter out of clear acrylic so that the material wouldn’t interfere. We worked through the night getting things done. Tensions got a little high around 3am but we all bonded together and had a common drive to get the thing done so we pushed through until 5:30am until we had our final product, the Lazy SuSynth. It was probably just a bit excessive to do for a 24 hour project, we probably made some questionable decisions cutting acrylic with a table saw at early hours in the morning, and we may or may not have filled the whole lab with the wonderful smell of burning acrylic from the laser cuter. Would we recommend doing this much for an overnight project to the students next year? Probably not, but it was a great learning experience and it was fun to have everyone on board with a cool idea that we were proud of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RkxIbPtfVq21D_EmRuv2Cw.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F264950992%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F264950992&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F694846887_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/ba374c77150a88127f7ced23d993d47e/href">https://medium.com/media/ba374c77150a88127f7ced23d993d47e/href</a></iframe><h3>Week 2</h3><p>This week we got to spend most of the time building out a device related to radio. There were minimal lectures and the focus was hands-on building. Our group was inspired by the pirate radio culture and built a device that created a community around taking over local airwaves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gesauCvP072MfdwJijpwLw.jpeg" /></figure><p>Up until this week, it seemed like we were usually getting positive feedback during reviews. Some instructors would come by and gently guide us in other directions while we were ideating, but when we had something to present, it felt like things were always going well. This week, we got to experience Dario give us the honest truth while critiquing our project. He told us what wasn’t working and since he was tracking our progress, was able to question decisions we made. This whole process was actually very pleasant and constructive.</p><p>I felt like this was the first time that I had someone with an experienced eye truly critiquing the work we were doing. It was blunt and honest but we since we knew it was meant to be constructive, it was very much welcomed. I initially thought that it was a great introduction to “real life” design reviews, but as the week went on I found it more valuable than that. By listening someone break down everyone’s design decisions, I felt like I learned new tools to think critically about my own work which I can apply during the process, not after. The learn by doing attitude of CIID really felt like it was coming to life during this week. We we’re building and learning from it. We weren’t making mistakes, we were experimenting and applying what we knew, then getting deeper feedback to improve our own ways of creating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZbAMndVQV0b7SMqIy8T5_Q.jpeg" /></figure><p>A fun exercise my team created in order to check that everyone had a common vision of what we wanted to build (and see that there weren’t any clear holes in our thinking) was what we called Random Metaphors. Each of us wrote down a random word — ie. Dracula, spoon, Titanic — and passed the words to the person on the left. That person then had to quickly, off the top of their head, communicate how that metaphor could be used to describe our concept. It was a silly exercise that was a nice break for us but also got us thinking about the device in new ways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3UXHePJdqTPzLSZqk9z2QQ.jpeg" /></figure><p>Since we spent a whole week on this project, we were expected to have a more polished demo than the classes before. This meant we have to put a good amount of thought into how we would convey the idea despite having a not fully functioning prototype. We learned about smoke and mirrors and tips on how to fake functionality. Since our project was meant to take over local radio waves but we had not implemented an FM transmitter, we needed to trick the audience into thinking we actually could do it. In order to get around this, we hid a bluetooth speaker in an old radio shell and used an iPhone to act like the radio waves were being controlled by our device. When someone on our team pressed the transmit button on the device, another person on our team in the background would press next on the iPhone which would switch it to a new song. It actually worked fairly well and for the sake of demonstrating functionality, was a success.</p><p>Since we knew we would need a demo on Friday, we spent a lot of time thinking how we could do this prior to actually starting to implement the code and hardware. This gave us a little advantage by the end of the week. We didn’t have to scramble to find ways to make things work or explain why certain things didn’t work. Having realistic expectations of what we could accomplish through the week and how we could fake the rest made for a surprisingly stress-free time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0KQ1M_oiSiIbxMVaybuJ5w.jpeg" /></figure><p>Inspiration from lectures:</p><ol><li><a href="https://en.wikipedia.org/wiki/Computer_Lib/Dream_Machines"><em>Computer Lib</em></a> by Ted Nelson</li><li><a href="http://www.yingjiebei.com/moon-phases">Moon Phases</a> by Yingjie Bei</li><li>Harvey Moon’s <a href="https://www.youtube.com/watch?v=VufMgHvaoG0">Drawing Machines</a></li><li><a href="https://vimeo.com/163436492">Hortum Machina</a></li></ol><p>Notable things outside of school:</p><ol><li>Celebrated Milliner’s Day</li><li>Walked on the frozen lakes</li><li>Survived the dropping temperatures</li><li>Finally made it to Mayhem from my apartment without looking up directions</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*REwswghw-z9aYcs9o1a-ew.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QIYZXZkb_R4bpDdzXKcsDg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f69946be658" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID Week 7: Introduction to Programming]]></title>
            <link>https://medium.com/@penxman/introduction-to-programming-cf40b2c9897b?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf40b2c9897b</guid>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Sun, 15 Apr 2018 11:48:37 GMT</pubDate>
            <atom:updated>2018-04-22T12:05:39.097Z</atom:updated>
            <content:encoded><![CDATA[<p>“Data is virtual, we are not.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mmVYINB1opgwgb_CpaLa1Q.jpeg" /></figure><p>This week was Intro to Programming, and since I’ve spent the last 8 years of my life focused on that, I was ready to be a little bit bored. But the first day of class, we got a syllabus that mentioned John Cage and approaching projects with a “punk attitude” which, naturally, got me interested. We had four instructors overall but our more advance class was taught by <a href="http://www.jacobremin.com/">Jacob Remin</a> and <a href="https://dennisppaul.de/">Dennis Paul</a> and ended up being a fun learning experience. Everything revolved around sound and led up to a final performance of our “sound machines” that we would be building through the entire week. While I did not learn much in direct programming skills, I did learn a lot about approaching code with a designer’s perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*_piJBR8S8f9PQorQnEGmgA.jpeg" /></figure><h3>Keeping an open mind</h3><p>My one regret this course was not working in a group. While the week was fun overall, I found that my project was something I could have attempted to try on my own prior to arriving at CIID. It wasn’t very inspiring when I saw the final product. Other people created sound visualizations based on topological maps, turned poems into music, and physical objects that made noises. I ended up with a synth/sequencer controlled by facial movements. Using FaceOSC and Processing, this was a pretty simple task for me to hook up but took a while getting the interactions and the sounds right.</p><p>It’s not that I wasn’t happy with how everything turned out, in fact it’s the opposite, I quite like it. But it seemed too inline with small experiments I have already done. I didn’t put myself through a brainstorming session like I had in previous classes. Since it was just me, I thought up an idea and went to work. This siloed me into working in a direction that was not fully thought out and creative. It wasn’t until I talked with one of our instructors in depth towards the end of the week that I was able to pull out of my original idea and add some interesting tweaks to it.</p><p>Looking back, this week felt like I was back at work. Getting an end product and rushing through to complete it by the deadline set by the boss. Once I had made up my mind, I focused in on the project and went to coding. I did not allow myself to stop, reflect, and think about what could be added to the project to make it better or refine it.</p><p>During our Friday retrospective, Dennis gave me some good advice. He reminded us to keep an open mind while coding. While working in a space like Interaction Design, I have to remember I am in a design world, not an engineering world. There is more room to adjust, add things, and try new ideas. Especially while I’m here at school learning. I think having this closed mind while I work through the week was the main factor of my disappointment in my project. It was the usual thing from me and I know I could have pushed myself more. But I didn’t realize it and fell into my old habits. Which is okay and is something I have fresh in my mind as I continue into more programming related skills courses in the next month.</p><h3>Code as a tool</h3><p>Another teacher for the course was <a href="http://thefactoryfactory.com/">Josh Noble</a>, a fellow coder turned designer. Aside from spending some time bouldering together, he gave me some great advice on seeing code as a tool. If I am to transition into design, code is no longer my only medium to work through. It becomes a tool to help make decisions easier. You can use it to rapidly prototype new ideas, assist in normal design pitches, and much more. This concept felt like a relief to me. Looking down the design path and not being married completely to code is very enticing. I may have mentioned it before but I’ve realized code isn’t my passion. I enjoy it but it’s not something I’m in love with. Being able to mix it in with other skills I like and not being tied to it all the time seems like a nice balance.</p><h3>Listening to sounds</h3><p>Jacob took another student and me on what he called a “sound micro-excursion” where we explored the outdoors while listening to headphones hooked up to <a href="https://www.zoom-na.com/products/field-video-recording/field-recording/h6-handy-recorder">Zoom H6’s</a>. It was an exercise for us to pay attention to details around us and to immerse ourselves in our environments. I think this was my biggest learning experience of the week. Being able to slow down and notice all the details around you is something powerful. I have tended to do this a lot on my own but he taught us what to do with the information we gather from these details. How to process it and pull out new ideas from the small bits of sound all around us…or not if you just want to enjoy your environment. This was a nice break from the fast paced nature of CIID. It was a reminder not only to slow down for a mental break but also as an exercise for ideation.</p><p>Inspiration from lectures:</p><ol><li><a href="https://dennisppaul.de/institut-fur-mikroelektronische-schaltungen-und-systeme/">Institut für Mikroelektronische Schaltungen und Systeme Identity Design</a> and <a href="https://dennisppaul.de/an-instrument-for-the-sonification-of-everyday-things/">An Instrument For The Sonification Of Everyday Things</a> by Dennis Paul</li><li><a href="https://vimeo.com/200738315">Shattered By Nature</a> by Vincent Brinkmann</li><li><a href="http://www.peterbuczkowski.com/projects/crowd-weather-indicator">Crowd Weather Indicator</a> by Peter Buczkowski</li><li><a href="https://criticalengineering.org/">Critical Engineering</a></li><li><a href="http://fonik.dk/works/isfald.html">Isfald</a> by Jacob Kirkegaard</li></ol><p>Notable things outside of school:</p><ol><li>Saw Yen Towers perform at Mayhem</li><li>Planned my Spring break trip</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*udUTvJskpRH4R3O1ntDThw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf40b2c9897b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID First Month Reflection]]></title>
            <link>https://medium.com/@penxman/ciid-first-month-reflection-962954294dca?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/962954294dca</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Sun, 11 Mar 2018 13:35:48 GMT</pubDate>
            <atom:updated>2018-03-11T13:36:38.994Z</atom:updated>
            <content:encoded><![CDATA[<p>One month down, eleven more to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6wpLbNL7kfEYAHD4kzzFBQ.jpeg" /></figure><p>It’s already been a month. Feels like everything has gone by so quickly but at the same time, so much learning has been packed in that it feels like time has gone slower. But it’s all a good thing. I haven’t had my mind actively and regularly engaged in a very long time. For the last two years I had been drifting in and out of interest in work. Spending some days excited on a project, but spending others just trying to pass the time and get code done at a reasonable rate. At CIID, every day has been a challenging learning experience and being on this journey with such a diverse group of students definitely helps. I’ve gone through team building, storytelling, and intro to interaction design in only a few weeks and it’s been a lot to pack in.</p><p>I wrote a short list of goals I had for the year which was meant to be an outline for myself so I can actively work on areas throughout the year. After a month of seeing where this year is taking me, I’ve made a few adjustments to them:</p><ol><li>B̵e̵c̵o̵m̵e̵ ̵a̵n̵ ̵I̵n̵t̵e̵r̵a̵c̵t̵i̵o̵n̵ ̵D̵e̵s̵i̵g̵n̵e̵r̵ Learn new tools: I originally wrote that at the end of this year I wanted to be able to consider myself an Interaction Designer and find a job in that area. When I set out into this program, my goal was to keep the ending open in terms of where I was going and what I was doing after. I’ve quickly realized that the biggest potential of this year would be to expand my set of skills within the Interaction Design world but not necessarily set myself to that one path. I’ll be able to explore freely this year and try new things without restricting myself to a single option. From there, I’ll see where it takes me. Maybe I’ll be back to Software Engineering with a new outlook on things, maybe I’ll find myself in Graphic Design, maybe I’ll end up in Interaction Design anyways, maybe I’ll land somewhere completely different. But either way, the strength in this year will be pulling in new knowledge and blending it all together in a way that fits me best.</li><li>Be able to communicate what I like: This has popped up over and over again so far this year and was a big point one of my close friends made to me last year. People say I have a solid taste in things but when it comes to describing what makes those things interesting, I fall short. I want to work on actively digesting new information and pulling out the key points that catch my attention. The communication aspect is the biggest part for me. Sometimes, in my mind, things make sense but I can’t put them into words. This goes for both what I like and I dislike. In the realm of engineering this was never a problem, things are usually functionally better or worse and it’s easy to define. As I’m exploring the design world more, this line becomes blurrier and things aren’t always as explicitly clear. Working on this will help me out both in my personal life and in my career.</li></ol><p>But not everything this year is about school. I’ve gone to a diverse range of shows, began biking more, gained a deeper appreciation for the sun, developed a new love for coffee shops and writing, worked on stabilizing my mental health, made better progress at reading regularly, and pushed myself to be more social with strangers. I’ve been sending my classmates a weekly list of upcoming concerts, made an attempt at starting a school radio station, put more effort into publicly showing my art, and wasting less time on social media. I’ve been able to really focus on myself and figure out a schedule that works for me. It’s been quite nice. Now if I would only carve out more time to take more pictures…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z7jYx3xeO2A87Jcvw8hvWA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=962954294dca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID Weeks 4 & 5: People Centered Research]]></title>
            <link>https://medium.com/@penxman/ciid-weeks-4-5-people-centered-research-99dd0ba2c547?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/99dd0ba2c547</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Sun, 11 Mar 2018 13:34:09 GMT</pubDate>
            <atom:updated>2018-03-11T13:34:09.889Z</atom:updated>
            <content:encoded><![CDATA[<p>“Hygge? Hyyyyygge!”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*23QtiTBXaVpk0xMJUs2Z9w.jpeg" /></figure><p>People Centered Research was filled with new experiences. Our first two-week course. Our first weekend spent working in the studio. Our first super late nights spent at school. My first visible display of frustration at school. But despite all that, it was a great learning experience getting to interview people, analyze our findings, and develop ideas from them. <a href="http://www.francescadesmarais.com/">Francesca Desmarais</a> and <a href="http://ciid.dk/education/management/aram-armstrong/">Aram Armstrong</a> guided us through the first steps of people-centered design for these two weeks. We started with a brief from an outside company and the vague directions of coming up with a concept to help people suffering from a very prevalent disease. We then split up into groups of three and began on our journeys…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QzjyGMbLpf9TMrgMKfFQcg.jpeg" /></figure><h4>Statement of Intent</h4><p>The first step for our team was to come up with a statement of intent — a general compass for our field research. We all wrote down what interested us in this problem space and the areas we felt could be productive to explore. Our team came together, compared interests and blended them to get an idea of where we were headed. This actually took quite a bit of time for us. We were stuck in the studio still working on our statement of intent long after other teams began leaving for the night. But once again, this time spent in getting everyone on the same page proved to be helpful in the long run. We all had a clear idea of what kinds of things we wanted to get from our field research and ultimately carved out a clear pathway to the end of the project.</p><h4>Intercept Interviews</h4><p>At the conclusion of last week’s course, I told Francesca and Aram that I was nervous about stopping strangers in the street for interviews. They assured me that it would be happening during People Centered Research. When that time came around, I found out it wasn’t too bad.</p><p>My first attempt at asking a stranger for a quick interview was rejected by a nice, old lady at the train station. It was possibly the kindest rejection I could have received. She said she didn’t want to be interviewed but was so excited to hear that we had moved to Copenhagen for the year to study. This helped clear my head of any worries right from the beginning.</p><p>I found that, for me, the hardest part about intercept interviews is getting going. I’ll stop, scan the streets for the perfect person, and hesitate when I find someone. But once I make that push into the first interview, it’s easy to jump around from person to person in rapid succession. I was able to build up this flow of interviews to knock out a lot pretty quickly which I think helped get rid of any pre-existing inhibitions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Et-sN9WWQ1z8BshYsMlFmw.jpeg" /></figure><h4>Synthesis</h4><p>With all of our data collected in notebooks, computers, phones and brains, we had to consolidate it all somewhere. Coming from an engineering background it was only natural to want to digitize everything in one document, which we did, but the real power of our data when we wrote <em>everything </em>out on Post-Its. This was the cliche of designers I had in my head, waste a ton of paper and go through an absurd amount of Post-Its. But after running through the exercise once, those little sticky squares really do help. Our team was able to reorganize the data endlessly, clustering the quotes we got into various themes and groupings. When we got stuck with our thinking, just moving two new notes side-by-side would often times prompt us into a whole new direction.</p><p>Once we had groups we liked, we generated a sentence for each which was the overall insight we could extract from that group. These were then used to generate design opportunities (AKA the return of the How Might We’s). The power of Post-Its came into play once again. Our team created an activity we called Fridge Magnets. We broke down our insights into individual key words and stuck them on separate Post-It notes. We then rearranged them on our board collaboratively to generate sentences describing out design opportunities, much like the <a href="https://www.amazon.com/Magnetic-Poetry-Original-Essential-Refrigerator/dp/1890560014">Magnetic Poetry</a> sets on your refrigerator.</p><h4>Cross pollination, bias, and the importance of relaxing</h4><p>Through our reflections on the two weeks, our team had three major points we wanted to keep in mind going forward.</p><ol><li>Cross pollination: While our brief was focused around a particular disease and those affected by it, we found that getting data from totally unrelated (but actually related) sources was extremely helpful. Our group interviewed only people with the condition and thus only got information around how it affects them personally. Other groups interviewed experts on breathing (something that is greatly affected by the disease) which ranged from scuba divers to yoga instructors. At first we thought this was a little silly but by the end, merging the information these groups got with our own helped us get an overall picture of new treatments and products that could address the problem.</li><li>Personal bias can’t affect your data: While casually talking to someone we interviewed, it was brought up that their beliefs contradicted the beliefs of a few of our team members very strongly. Though tough to digest at first, it was a great learning experience in personal bias. Just because we had conflicting thoughts on a totally different subject, we couldn’t let this change the way we presented our findings to the class and our client. Our main focus was living with this disease and although we disagreed on some very big core beliefs, their experiences were still valid and important to consider while synthesizing ideas.</li><li>Don’t overwork yourself: Our team made the mistake of setting loose work schedules over the weekend. We ended up dragging things out, showing up late, and putting things off which ultimately led us to working both Saturday and Sunday. Not having a full day off before the second week of the course was unexpected at the end of the day on Friday. It was generally agreed upon that we were all in worse moods throughout the second weeks. If we had planned and set standards before the weekend, we all agreed it would have been a little easier to manage if we had been expecting a full weekend of work.</li></ol><p>Inspiration from lecture:</p><ol><li><a href="https://www.lensculture.com/articles/daesung-lee-futuristic-archaeology">Futuristic Archaeology</a> by Daesung Lee</li><li><a href="https://www.mindtools.com/pages/article/seven-dimensions.htm">The Seven Dimensions Of Culture</a></li></ol><p>Notable things outside of school:</p><ol><li>The sun came out for a bit longer than usual!</li><li>Snow!</li><li>Visited a castle with my team!</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99dd0ba2c547" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID Week 3: Intro to Interaction Design]]></title>
            <link>https://medium.com/@penxman/ciid-week-3-intro-to-interaction-design-b1e84296d5c1?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1e84296d5c1</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Sun, 11 Mar 2018 13:23:11 GMT</pubDate>
            <atom:updated>2018-03-11T13:23:11.751Z</atom:updated>
            <content:encoded><![CDATA[<p>“It begins…”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJAPI5qZZGVM-K2Afbv0RQ.jpeg" /></figure><p>Week 3 was our first dive into Interaction Design led by <a href="http://emenel.ca/">Matt Nish-Lapidus</a> &amp; Blair Johnsrude. I learned new design ideation techniques, got to work in a group designing a product for the first time, and found out the mass collection of inspiration in my brain is ultimately useless if I can’t pull it up and show it to others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lXgtp0W9uFe-WnbfCpEhnw.jpeg" /></figure><h4>Bill</h4><p>We followed basic guidelines from our teachers in order to find a solution to a problem in a space that was randomly assigned to us. The process was long and a little draining on the team. We hit walls and tension built up. But in the end, spending so much time figuring out our problem space really helped with.</p><p>We were given the problem space of “food” in regards to our troubles with living in a new country. This was the first time I had really dug into something like this. Going through engineering courses, you’re almost always given the problem and what the solution should look like. Your job is just to implement it in the best way possible. To go through the whole process was a fun experience, you really feel connected to your solution in the end.</p><p>Our team began brainstorming pain points we had related to food. These were all over the place — from eating out in large groups, ordering in a foreign language, to trouble finding ingredients from home. We used a variety of methods to get us to our final proposal but it wasn’t easy. So many ideas and directions were shot down by instructors but each time I feel like we learned something.</p><p>We ultimately ended up with Bill, a friendly NFC reader which prints out receipts of all your purchases throughout the day. Giving you a small summary of your spending habits in your home currency to help with digesting the info.</p><p>Through the process we found that all of us had trouble changing our spending habits, especially now that we all aren’t working during school, and wanted to address that. But we also realized how hard it is to create something that changes peoples’ habits. Aside from just the habitual changes one has to make, with spending, you need to baseline what is “normal” spending for a user and respond to that. It adds extra complexity to a device we wanted to keep simple. Further along from that, the issue of customer retention after they actually do change their habits becomes a problem. If someone successfully changes their spending habits are they done with your product? Do they just move on to something else? So we decided to focus on a friendly product that just helped make people more aware of what they were doing so that they could make more informed spending decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8AXGa1zDfNTQmkPkTNygaA.jpeg" /></figure><h4>Ideas</h4><p>Something that really stuck out for me was how to approach problems. We were given an example in class of how to build better stairs. One of the first ideas to come to mind would be to use escalators. They’re stairs but people don’t have to use so much energy. But thinking more about the core issue, you might find that this whole problem isn’t really about the stairs, it’s about moving from floor to floor easier. Thus, a proposed solution could be an elevator. By understanding the problem space and the issues around it, you’re able to intervene in better ways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZocTyppLsLPcIqNIjF5FIA.jpeg" /></figure><h4>How Might We</h4><p>I was introduced to How Might We’s for the first time this week. Not a lot to write on this subject, but I found it very helpful in learning that these should always be framed in the positive for the people it is addressing.</p><p>For example:</p><p>“How might we help prep meals for students who don’t have time” is framed in the negative, only highlighting the problem that students have.</p><p>While, “How might we help prep meals for students so that they have more time” frames it in the positive.</p><p>At a high level, both succeed in getting across what the problem is and prompting us to begin thinking of how to address it. But by framing in the positive, we are able to communicate what the problem is and what we are trying to achieve. According to our teachers, keeping this in mind is both helpful for ideation and getting users on board with your line of thinking.</p><h4>Reference Material and Mood board</h4><p>It finally happened, I got to make a mood board for a project! I had seen all the designers show these while I was working at <a href="http://butchershop.co/">Butchershop Creative</a> in SF but had never made one myself. What I thought would be a quick and fun process was actually a little painful to me. I realized I had no concrete catalogue of inspiration to pull from. Other students who had worked in design had various ways in which they recalled inspiration they had seen in the past that could influence our idea, but I had none. Searching through my own brain to bring up projects I had seen was of little value to the team. And that’s when I realized just taking quick mental notes of things I was inspired by wasn’t enough. It’s important to have a catalogue of ideas you can pull up quickly to show others.</p><p>Yes, through this course I started a Pinterest. But it also got me to realize the potential of <a href="https://www.are.na/alex-penman/channels">Are.na</a> (which my old roommates would always speak highly of) and got me to use it a little more seriously.</p><p>Inspiration from lecture:</p><p><a href="http://worrydream.com/refs/Bush%20-%20As%20We%20May%20Think%20(Life%20Magazine%209-10-1945).pdf"><em>As We May Think</em></a><em> </em>by Vannevar Bush</p><p><a href="https://www.are.na/block/1637942">10 Rules For Students And Teachers</a> by John Cage</p><p><a href="http://xoxxcomposer.axelbluhme.se/">XOXX Composer</a> from Axel Bluhme</p><p><a href="http://www.fionaoleary.ie/Spector">Spector</a> by Fiona O’Leary</p><p>Notable things outside of school:</p><ol><li>Learned to enjoy the sun when it does decide to pop out</li><li>Played many board games</li><li>Picked up a bike that fits me</li><li>Got a little ripped off by the guy who sold me the bike</li><li>Fell in love with biking in the city now that I have a comfortable bike</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1e84296d5c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID Weeks 1 & 2:]]></title>
            <link>https://medium.com/@penxman/ciid-weeks-1-2-2edef169d7f3?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2edef169d7f3</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Thu, 01 Feb 2018 00:00:41 GMT</pubDate>
            <atom:updated>2018-05-13T15:20:24.484Z</atom:updated>
            <content:encoded><![CDATA[<h4>“This is the year to try new things and experiment”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-G28opkvcCNHzaIJR7uFHA.jpeg" /></figure><p>It’s been two weeks but it feels like I’ve been here for months. I haven’t been this mentally engaged in quite a long time. Since the last update, our cohort has gone through team building and storytelling classes with a little bit of woodshop and laser cutters thrown in between.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yguMSP9XhGJ-IqXe0AXj9g.jpeg" /></figure><h3>Week 1: Team Building</h3><p>The first week of class began with a team building course taught by <a href="https://www.askthesherwins.com/">David and Mary Sherwin</a>. It was a trial by fire, super fast, crash course on how to work in teams effectively. As crazy and hectic as the week was, it was refreshing to stop and turn what I knew about team collaboration upside down. In the end, I now have a lot of great tools to help me through the year and beyond. Below are some of my key takeaways from the class.</p><h4>1. Getting an entire team on board with an idea is important to working effectively</h4><p>During the first week, I noticed a lot of students were saying they found it hard to let go of their ideas or let other team members change them, which was something I had not really been experiencing at CIID. After some discussion it seemed like since I had been on teams where everyone had a very solid idea on the direction we were taking, decisions were smoother. I could trust my teammates that their input would help pull us in the right direction so I didn’t worry about making changes to my ideas. As the week went on, and I worked in some groups that weren’t as united around a vision, I found that what I had been hearing earlier was happening to me. I held on tighter to my ideas when I didn’t trust that the other people in the group would advance our project in the right direction. Getting everybody on board with the project early helped all around in getting quality work done fast.</p><h4>2. Timeboxing <em>actually </em>works</h4><p>I had done a good amount of timeboxing at my previous job, but it all seemed like a waste of time. If we reached a standstill while trying to assign points to stories, we would resolve it by going and “timeboxing” a task. In this case, it was merely giving someone an hour or two to go try out a few things and report back to the team if there was any update. This never worked and we usually landed back in the same spot as before or the person doing the timeboxing would end up extending the time they needed. With the Sherwin’s, we learned some techniques for effective timeboxing and I was actually surprised at how well it went. Definitely reinforced in my mind that just because you are doing <em>something </em>doesn’t mean it will work to your advantage if you aren’t doing that thing right.</p><h4>3. Share all ideas during brainstorming no matter how weird they are</h4><p>This came up multiple times throughout the week. Brainstorming is all about getting ideas out in front of the group. Holding back during this stage will only do you harm. In two cases, what I thought were my craziest ideas ended up being the inspiration for the final products. Sure, they sounded a little absurd at first but there were things at the core of the ideas we were able to work out and refine as we went along with our process.</p><p>Upon reflecting on this, I realized this has been a big thing for me throughout the last few years. I can think of multiple times where at work some silly idea has led to the way we solve a problem. The biggest one that sticks out was during my Media Arts class in college. We were setting off on a three quarter class where we would script and eventually shoot a short film over the course of the full year. I didn’t take the first assignment of coming up with movie ideas very seriously and came up with crazy ideas. My professor found a theme at the core of what I thought was the most outlandish one and urged me to go along with it. I took that, and with another person in the class, went to work on the script. By the end of the year we had a finished short which the professor still shows to incoming students all these years later.</p><h4>4. Resetting is sometimes very necessary and can help the team</h4><p>I was lucky to work pretty well with most of my groups this week. There was only one point when things weren’t going so well and ideas weren’t coming to us. Things got a little tense and it really was apparent in the atmosphere. After finishing a portion of the project, we all walked out frustrated, agreeing we needed a five minute break. We came back in and all admitted that there was something off in the group. Rather than pushing through the pains without communicating, we all talked about the tension, took a few steps back, then proceeded to move on. We had no problems after that.</p><p>It’s inevitable that tensions will rise and people will disagree on opinions. What we learned from the Sherwin’s is that it’s important to address these issues head on and directly. In our case, we were able to all recognize what was bothering us, reset, and continue forward much more efficiently than before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBzq4W4fkDHKXOt74oLCuw.jpeg" /></figure><h3>Week 2: Storytelling with Tom Manning and David Yun</h3><p>Week 2 began with introductions to the school facilities which meant we all got to learn how to use the laser cutter, where the studio lighting set up was, and how to use giant saws without cutting off any limbs. But the main focus was our storytelling course taught by Tom Manning and David Yun. It was an interesting learning experience with lectures by Tom, who focused on the core concepts of storytelling by using his love for comic books, complemented with Dave showing how these concepts have helped him through his design process over at Wax Studios.</p><p>The lectures were supplemented with two activities where we had to create product videos for fictional products made up by Tom and Dave. This was the first time we really put the Sherwins’ advice to action for more long-term projects. Over the course of two days we shot two videos in our groups. One was a simple brief giving us clear instructions and the opportunity to work through brainstorming a product idea, storyboarding, filming, and editing. After that, we had to go back to the drawing board with a similar brief, but this time working with two restrictions pulled out of a hat. Our group had to create a video for children that contained 10 seconds of two people laughing on screen at the same time. Not too bad considering another combination pulled was an infomercial that contained no talking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RLYSgl0WxHHEfIhKqkLQZQ.jpeg" /></figure><p>The projects were a fun exercise in building storytelling skills and thinking critically about what makes good stories succeed but my biggest takeaway from this week occurred during critique. About halfway through I realized I had not been saying much about other groups’ work. I’m so used to sitting silently through class which has worked out in the majority of Engineering courses I’ve taken but the whole point of crit is to get honest feedback. As I started formulating thoughts in my head, I realized not only was this helpful for the other teams but also myself. I was forced to put words to why I liked or disliked something. I couldn’t get away with just simple “it was good” responses because that’s not helpful feedback.</p><p>Going home and thinking more on this, I realized I had done the same thing through all of my photography classes in college. I would sit silently in the back while others presented, waiting until it was my turn to go up and show my work. Being an active participant during these sessions might have helped me progress with my photography skills faster but since I did not take it seriously, I don’t think I really gained anything from them. At first, this seemed like a small topic that I would need to keep in mind. But the more I think about all the ways critique helps with the design process, the more I’m realizing this should be something I prioritize in my list of things to improve on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-9eu7jc2wirYHQlrjwe8wg.jpeg" /></figure><p>That’s all from the first two weeks. Half a month down of school and eleven and a half more to go. Things are going great and I’m excited what the rest of the year brings.</p><p>Inspiration from lectures:</p><p><a href="https://thecharnelhouse.org/2015/06/11/about-two-squares-el-lissitzkys-1922-suprematist-picture-book-for-kids/"><em>About Two Squares</em></a><em> </em>by El Lissitsky</p><p><a href="http://www.rtqe.net/ObliqueStrategies/OSintro.html">Oblique Strategies card deck</a> by Brian Eno and Peter Schmidt</p><p><a href="http://www.notclosed.com/pages/wemake/work_wk_ms.html#">National MS Society Branding</a> by Open</p><p>Notable things outside of school:</p><ol><li>Went on two architecture walks with friends from class</li><li>Went to a show at a punk squat near my house (<a href="https://urbanoia.bandcamp.com/">Urbanoia</a> was great)</li><li>Saw Internazionale at Mayhem</li><li>Spent a lot of time in coffee shops reading and writing</li><li>Had a final wrap up call with my therapist and ended it with a good feeling about the year</li><li>Explored Bakken and Klampenborg</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DsOXZ14o6C7bA8yJtNLcqw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2edef169d7f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CIID Week 0: Goals]]></title>
            <link>https://medium.com/@penxman/ciid-week-0-goals-ad3aacff09d1?source=rss-8e3881a2c75e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad3aacff09d1</guid>
            <dc:creator><![CDATA[Alex Penman]]></dc:creator>
            <pubDate>Sun, 07 Jan 2018 22:53:59 GMT</pubDate>
            <atom:updated>2018-02-04T12:56:34.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n6xa31eLspBAttiSoIN63A.jpeg" /></figure><p>I’m starting school tomorrow at the Copenhagen Institute of Interaction Design (CIID) along with a diverse group of around 20 other international students. This marks the beginning of my transition from engineering into a design discipline, which I feel is much needed. I’ve spent the past 10 days sleeping off sickness, exploring Copenhagen, catching the New Year’s fireworks on Queen Louise’s Bridge, meeting new people, acclimating my body to the cold, preparing for the year ahead, and quickly falling in love with the concept of “hygge.”</p><p>Below are a few goals I’ve set for myself to focus on this year.</p><h4>1. Become an Interaction Designer</h4><p>This one is pretty self explanatory. I’m going to an Interaction Design school with an end-goal of working as an Interaction Designer. After studying Computer Science in college and working as a Software Engineering, I realized pure engineering is something that isn’t for me. I’m incredibly fortunate to have enjoyed the work I’ve done so far and all the opportunities it’s opened for me, but it’s time to move on to something new. I’m looking forward to focusing on the human side of software and hardware.</p><h4>2. Throw self doubt in the trash</h4><p>For as long as I can remember, I’ve always doubted my abilities and have worried about the way I look in front of people. It has affected me in all aspects of my life. Asking questions in class was never something I did, I would only enjoy going to skateparks when they were completely empty, sharing my opinions on music and movies was uncomfortable, and having people watch me take pictures is something I hate. Being open and free-flowing with ideas is crucial to the success of design thinking and the group project based curriculum at CIID. Working for a year in a highly collaborative environment will help me improve on this.</p><h4>3. Become comfortable in decision making</h4><p>Like a lot of people, decision making is a tough thing for me. Individual choices are totally fine for me though. It’s just when another person has a stake in my choice, I tend to second guess myself and, often times, force them to decide. This can even beover something as small as getting lunch. It probably relates a bit back to the above point. Once I’m in control of someone else’s satisfaction, I freeze up and worry about making the wrong decision. Building up myself to make confident and final decisions in group settings is something I’d like to get much better at.</p><h4>4. Have fun</h4><p>It’s going to be a busy year. Attempting to learn everything about Interaction Design in one year is a big task and super long days are CIID are probably more common than they are not. But despite all that, I’m in a completely new place far away from home, and I want to make sure I enjoy the time here. Whether it be exploring Copenhagen’s diverse music scene, enjoying a book at a cafe, traveling around other parts of Europe, or just walking around taking pictures, I want to be present during this journey and enjoy it while it lasts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad3aacff09d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>