<?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 Nick Hahn on Medium]]></title>
        <description><![CDATA[Stories by Nick Hahn on Medium]]></description>
        <link>https://medium.com/@makeitso_nick?source=rss-64d404381504------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*G8v06xiQb6eU5vzOBby9jw.jpeg</url>
            <title>Stories by Nick Hahn on Medium</title>
            <link>https://medium.com/@makeitso_nick?source=rss-64d404381504------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:46:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@makeitso_nick/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[Art of the Possible]]></title>
            <link>https://medium.com/@makeitso_nick/art-of-the-possible-3eca41df0bcc?source=rss-64d404381504------2</link>
            <guid isPermaLink="false">https://medium.com/p/3eca41df0bcc</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[designops]]></category>
            <dc:creator><![CDATA[Nick Hahn]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 14:56:15 GMT</pubDate>
            <atom:updated>2019-09-26T13:51:29.914Z</atom:updated>
            <content:encoded><![CDATA[<p>Why we as designers fall short of envisioning the future. <br>And how to not let it happen again.</p><blockquote><strong>“The developers said it’s not possible”</strong></blockquote><blockquote><strong>“We tried that like 3 times before, it didn’t work.”</strong></blockquote><blockquote><strong>“There’s no API for that”</strong></blockquote><p>well…</p><h3>Fuck that.</h3><p>These aren’t <em>our</em> rules. As designers we didn’t sign up to be given a list of requirements and features and make some canned little wireframes.</p><p><strong>We signed up to solve problems. </strong>Our user’s problems… not our business’ problems. We’ve got hordes of product managers and technical sales managers and VPs that tell us what the business wants and thinks it needs. Everyday we walk in and hear these voices. Rarely do we get the chance to hear the voices of the people we’re actually building for. Instead we get fed lines like:</p><blockquote>We made a HUGE deal with this new customer, but our product needs x, y, and z feature to be built or they won’t close. BY NEXT WEEK!</blockquote><blockquote>We need this security feature or else new markets can’t use our product!</blockquote><p>These kinds of statements are the perfect way to craft perfectly meh products solving ambiguous problems.</p><p>I know I know, sometimes you just gotta…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*DuJjTQusquEXJR1hJ6amLw.gif" /></figure><p>I’ve been there and made that argument before. It’s the easy argument and people feel good that when they close another git hub issue on time and bug free.</p><p>We all make sacrifices in the name of getting it done. But for the love of all things sacred to the design gods, please don’t forget why we exist.</p><h3>To envision what’s possible.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*UNPMFUaOFnWTXLV-G5a-yQ.jpeg" /></figure><blockquote>“When we’re able to visualize the opportunity and people are able to understand the potential, <strong>they become very optimistic. They become evangelists </strong>and they actually really can make the world work better”</blockquote><p><strong>Lee Green:<br></strong>Retired, VP, Brand Experience and Strategic Design — IBM</p><p>This guy designs.</p><p>Lee Green, the former head of design at IBM, knew that we can simply visualize a future for people to see for themselves. When see what’s in your head and become excited about that vision, they move from detractors to promoters, or in non-NPS speak: evangelists.</p><p>Don’t just talk about what the future is, <em>visualize it</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4T-Eh1Wbw4pF7jadLRW5Tw.jpeg" /><figcaption>Designers should set the bar for what’s possible.</figcaption></figure><h3>Set the bar high.</h3><p>Every time we sit down to design something, this should be the goal. Block out the noise, focus on what the the solution <em>should</em> be, not what it can be right now.</p><p>There’s a time at the start of a project where you can put on your blinders. Forget what the world has told you is possible. Leverage your imagination and allow yourself to craft something that may or may not be possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sV1k0m6wU47OQ8tp2eAJfg.jpeg" /><figcaption>But we listen to the doubters of what’s possible.</figcaption></figure><h3>Don’t focus on today’s limitations</h3><p>When the HiPPO (highest paid person’s option) enters the room, designers often suffer imposter syndrome. The HiPPO will gladly define the box in which the product should fit.</p><p>Don’t self censor when designing the vision. Plenty of other people will censor you down the path.</p><p>Then start designing. See where your ideas and inner customer voices take you. There are plenty of ways to validate these ideas, with real user’s feedback, but for now, breath and focus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R78SUlnQe05kgaaMqUmlAg.jpeg" /><figcaption>and we can end up shipping low quality shit.</figcaption></figure><h3>Don’t ship shit.</h3><p>Your squad might focus on shipping an MVP first to meet some deadline and/or client request, then think they’ll fix it later.</p><p><strong>99% chance they don’t fix it.</strong></p><p>When starting the vision from an MVP perspective, what really gets shipped is just the “MP”. <strong>Don’t allow the team to forget about the adding the <em>value </em>from day one.</strong></p><p>When you <em>start </em>by designing for the ideal experience, you’ll be surprised how much of the initial vision can get shipped.</p><p>Speaking of what ships —</p><h3>The business drives most of what goes out the door:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1-6MAvvqQyVW9tHW1G1soQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5HT9wDrNYUgcZg24NUUbUw.jpeg" /></figure><h3>But our job as designers is to be an equal counterweight to the business’ desires.</h3><h4>We should be:</h4><ul><li>advocating for the user</li><li>understanding where the market is going</li><li>and most importantly…</li></ul><h3>Bring the future!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*uFmtgaUuCnfof1MsdA_Uwg.gif" /><figcaption>when do we get flying cars?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AybtM-zu9cmTGUhzxBfwKQ.jpeg" /></figure><p>As designers we have a chance to shape where we’re going, as opposed to acclimating to where we’re already at.</p><p>We’ve fought the good fight to get a seat at the table. But now as designers, we need to step up, skill-up, and be equal peers to our PMs and developers. Make decisions with them and push back when something doesn’t feel right. You’re just as responsible for the quality of what goes out the door.</p><p><strong>I want to build the future — it’s why I became a designer.</strong></p><p>I want to do something no one has ever done and that brings value to people who need it. And I’m happy if my company makes money from this (…keep the paychecks rolling in please!).</p><p>I’m not satisfied building safe solutions that are just bug free. I don’t care about getting it off my plate if it’s not solving a real problem. I’d rather ship something with bugs that people line up around the street for. Shit, Apple has been doing that for years.</p><p>Build alliances and trust with your dev and PM peers (at work and hopefully over some beers), so that when you do push back on something, they’re open to listening to you.</p><p><strong>Skate to where the puck is going.</strong></p><p>There is no one better suited to know where the puck/market is going than you, the designer. Be the voice of the user, trust yourself, and embrace the little voice in your head that says</p><blockquote>“this could be so much more”</blockquote><p>and fight like hell to turn that voice into a vision.</p><p>— — — — —</p><p>FYI: These thoughts are from my brain and very helpful peers of mine who’ve provided invaluable feedback (<a href="https://medium.com/u/d9b1c8cef779">Gabriella Campagna</a> and <a href="https://medium.com/u/5114d8705184">Patrick Lowden</a>). It isn’t a reflection of the work I’m a part of at IBM or other institutions I’ve collaborated with. It’s just what I’ve seen across years of trying to build products that actually meet user’s needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3eca41df0bcc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NEW COLLAR, NEW EDUCATION:]]></title>
            <link>https://medium.com/design-ibm/new-collar-new-education-5b78afda1451?source=rss-64d404381504------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b78afda1451</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[high-school]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Nick Hahn]]></dc:creator>
            <pubDate>Tue, 29 Jan 2019 22:24:08 GMT</pubDate>
            <atom:updated>2019-01-29T22:24:08.013Z</atom:updated>
            <content:encoded><![CDATA[<h3>HOW STEAM AND DESIGN THINKING PREPARE US FOR NEXT-GENERATION JOBS</h3><p><a href="https://www.cooperhewitt.org/publications/design-journal-winter-2017-copy/">originally published by <em>Cooper-Hewitt Design Journal</em> Summer 2019</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*joYumngRtvWBOMU2QYbVwA.png" /><figcaption>Final “Playback” presentations at the annual Design-a-thon where forty teens learn design thinking over a whole weekend.</figcaption></figure><p>Ace the AP high school classes, graduate from a prestigious university, and land that dream job — most of us grew up with this prescribed path for success. Creative jobs today, however, demand novel skills and new mindsets that aren’t necessarily being taught within the current education paradigm.</p><h4>Careers can no longer be defined by the binary of the blue-collar versus white-collar job. There are alternative paths, especially in technology, design, and entrepreneurship — we call those jobs “new collar.”</h4><p>The path to landing one of these jobs can look vastly different than what we’re used to. New-collar jobs look beyond the four-year degree and instead focus on whether a potential employee has relevant skills, often obtained through vocational training. As more students are exposed to new ways of thinking, my hope is some of these students go on to become the next generation of educators aiming to train the next-next generation of creative thinkers, or new-collar workers.</p><p>We are already seeing this change in action with STEAM — the educational approach initiated by the Rhode Island School of Design (RISD) that adds the arts to the STEM (Science, Technology, Engineering, Mathematics) model. According to RISD, their goal is “to foster the true innovation that comes with combining the mind of a scientist or technologist with that of an artist or designer.”</p><p>In an effort to scale STEAM education, IBM created P-TECH (Pathways in Technology Early College High School). It blends high school, college, and career to foster students who can enter the workforce not just with knowledge, but with practical experience that combines academics, mentorship, and paid internships in its six-year program.</p><p>The skill set critical for success, yet still missing from a traditional or STEAM education, includes soft-skills such as <strong>problem identification, creativity, adaptability, and collaboration.</strong></p><p>The best ideas won’t come to fruition until we get the design, engineering, marketing, sales, and product management teams aligned to see the solutions to market.</p><h3>This is where design thinking comes in.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A9P7AriBJfqVqTQFm-ZZ5g.png" /><figcaption>IBM Product teams align around insights found during an Enterprise Design Thinking Workshop.</figcaption></figure><p>Design thinking enables new-collar workers to create solutions that truly connect to their user’s needs and builds strong team alignment so that those solutions actually ship out the door. In my nearly twenty-year experience creating digital products, I’ve been surprised by how many product development teams lack this combination of skills to see projects through to implementation.</p><p>Currently, there is a burgeoning ecosystem of corporate and private programs aiming to bring STEAM + design thinking training to the masses for this next generation of workers. Cooper Hewitt’s mission is to inspire, educate, and empower through design. With education as a key pillar, programs are developed to offer insight and practice in design and design thinking across all levels of competency in design. Programs expose intergenerational audiences to design concepts and help connect award-winning designers with their communities to facilitate change. While not everyone who participates in these programs is a designer or will become one, an understanding of the design thinking framework could assist in prototyping solutions for problems we encounter in our daily lives. Design thinking is taught as the necessary lifeskill to solve the complex problems of tomorrow.</p><p>Over two years ago, I joined IBM’s fledgling corporate-wide design program and I took on the mission of evangelizing our very own flavor of design thinking. My background in design and selling ideas came into high demand when trying to bring Enterprise Design Thinking and a new sustainable culture of design to over 340,000 employees worldwide. We’ve leveraged this new way of working to ship design-led innovative products, including the IBM Cloud Platform, which emerged out of our design incubator program five years ago and is now our fastest area of growth. We’ve also begun programs to introduce Enterprise Design Thinking to students of all ages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TkbxzXGUWv12-4Q_yMkrIQ.png" /><figcaption>Designers pull a print of a custom poster for a Design Thinking event celebration.</figcaption></figure><p>In Austin, Texas, home of IBM Design’s headquarters, we’ve hosted over three hundred students to learn about design thinking and innovation. I’ve done this in conjunction with my own STEAM education initiative called Austin Spark League, which is focused on teaching kids the full product development life cycle, including entrepreneurship, design, and engineering. In partnership with IBM, we’ve hosted annual design-a-thons where high school students learn the art of IBM’s Enterprise Design Thinking. Through these weekend-long events, students are prompted to solve a real-world problem that is relevant to them, do user research, envision a solution, and hone their storytelling skills through a large group presentation.</p><p>Immense focus is placed on these presentations because they teach storytelling skills so rarely exercised in classrooms. The biggest challenge students say they encountered at our events was not how to program or design, but how to communicate effectively with their teams. Failing to establish a fluid way of working across disciplines within a group leads to silos. Designing with empathy and considering the user and the audience are essential design-thinking skills our students require to prevent these silos from forming in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*PvZbxH6H9N5faFuj8S1kTA.png" /><figcaption>AIGA Austin + IBM Design setting up for a collaborative Design Thinking workshop</figcaption></figure><p>When asked for career advice in the creative space, I reassure students that they shouldn’t stress about their GPA, or awards, or even years of experience. What really matters are three simple things. Learn to learn quickly — new tools come out all the time and being able to adapt as they emerge is key. How well can you tell a story? The narrative they weave will help convince others of their great ideas. Check your ego at the door. Humility and collaboration will always win.</p><p>Educational collaborations like these supported by IBM and other companies can be a powerful tool that helps students see real-world applications of design thinking. The deeper mission of these initiatives is to help youngsters find their spark: that magical intersection in life when you find out what you’re good at, what you love, and what pays well. If they even get part of the way down this path, they’ll have a lot higher likelihood of finding success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b78afda1451" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/new-collar-new-education-5b78afda1451">NEW COLLAR, NEW EDUCATION:</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>