<?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 Adam Polansky on Medium]]></title>
        <description><![CDATA[Stories by Adam Polansky on Medium]]></description>
        <link>https://medium.com/@AdamtheIA?source=rss-604d74a30f88------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VG3GX8npgIM2R7hQLd6xvQ@2x.jpeg</url>
            <title>Stories by Adam Polansky on Medium</title>
            <link>https://medium.com/@AdamtheIA?source=rss-604d74a30f88------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:38:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@AdamtheIA/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[Tossed Into the Deep End]]></title>
            <link>https://medium.com/atlas/tossed-into-the-deep-end-f5e4b0cef1b7?source=rss-604d74a30f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5e4b0cef1b7</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[discovery]]></category>
            <dc:creator><![CDATA[Adam Polansky]]></dc:creator>
            <pubDate>Tue, 12 May 2020 17:25:54 GMT</pubDate>
            <atom:updated>2020-05-12T18:48:09.090Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lessons from my first “all remote” Discovery session</h3><p><em>Adam Polansky: Principle Experience Architect, Bottle Rocket</em></p><p>On the day my company, Bottle Rocket, decided to have everyone work remotely, I found out I would be taking-on a new client and Discovery would need to take place within about a week.</p><p>Crap!</p><p>Not only had we just found out we’d be working from home until further notice, I was faced with planning a completely remote Discovery session <em>without</em> all the comfortable elements that helped us earn our reputation. At first, I couldn’t even imagine what that would look like. Discovery is a process I love because of the opportunity to build trust with a new client, and we help the team gain new perspectives about their customers and what they care about. As a company we’ve developed a method that relies heavily on people being physically in the same room. It involves lively discussions, whiteboarding, impromptu sketching, serious listening, and eating together (never underestimate the value of breaking bread with your clients). Now I needed to pull all of this off, essentially over the phone.</p><p>Fortunately, I wasn’t alone. Several people from different disciplines joined in to create a “Remote Discovery Team” to help define a new “digital” process. First, I created an agenda for each activity which I sent to the team for perspective. Then, I made a recommendation to use <a href="https://miro.com/">Miro</a> — a digital whiteboard with tools to create different deliverables like mind maps using interactive sticky notes. In an attempt to keep an organic feel to some of the exercises, I also proposed using my document camera and a small whiteboard so that I could sketch live when we made lists or drew-out pictures for journey maps. For communication, we chose Zoom; our existing teleworking platform. As a team, we spent as many days as we could preparing and refining not only the exercises we had planned but rehearsing our roles within them; who would lead which exercise, how would hand-offs work, how would we interlace the different technologies smoothly and get past our own learning-curves with things like Miro.</p><p>Let me describe how we orchestrated the two-day session.</p><p><strong>DAY 1 — FOCUS &amp; PERSONAE</strong></p><p>Our first exercise would introduce everyone to each other beginning with name, title, project role, and a single phrase to tell us what success will look like for this project. In the physical space, I would normally just list the phrases on the whiteboard as they come, but we realized this was a chance to train the participants to use Miro. They would need to select a sticky note, fill it out, and place it on a board. It was important to break-down that simple act into components, so sequence became important. We decided we’d get everyone to introduce themselves as the first step, then place the stickies all at once as the second step. The third step would be reading the stickies aloud, to understand the different perspectives in the room. By doing it this way, we were preparing the team for a more complex exercise to come. Just like a platform game, the first level or two is designed to show you how to play the game. This turns out to be more effective than just explaining with a tutorial or static instruction. The preparation to this point taught me two things:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*ruw6dmV6m37Y-nxv5L6aiA.png" /><figcaption>Fig 1. Sticky-Note tool in Miro</figcaption></figure><p><strong>Learning #1:</strong> <strong>The more you try to match the real world, the more complicated you make things.</strong> In deconstructing the first sticky exercise, I saw that I was making too many assumptions about what people would understand. I learned we needed to design the activity around learning the software, and not try to mirror a room full of people sitting together.</p><p><strong>Learning #2:</strong> <strong>This is still asynchronous communication.</strong> It moves quickly, but the technology dictates that the activity must unfold one person at a time. I learned that even though the breaks between communications are short, the system wouldn’t support the kind of rapid-fire activity that comes with physical proximity.</p><p>The next exercise was the creation of quick personae to give us a more tangible picture of “the User” within the context of the app we’re designing. Ideally, personae are data-driven from information gathered through usability testing with some kind of contextual inquiry or interviews. In the past, we would use large flipcharts to capture the details for each person we’re trying to describe. Again, to convert a lo-fi, hands-on exercise to a digital format, we used Miro to create a template for each persona and pre-populated each with the basic information and a quick portrait sketch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*MdsRpJtocjX7a1vd9NMkzw.png" /><figcaption>Fig 2. Quick Proto-persona Summarized</figcaption></figure><p>The purpose of this exercise is to characterize the people (end users) who would be using the application. We noted a few demographic details: a real name (not “Sally Shopper”); their age; family status; and what technology they use. We then listed any other unique insights that would give us a glimpse into the world they live in. Next we made three lists. The first list considered the persona’s basic expectations. We asked, “what are the table stakes for an app like this?” The second list asked “what could potentially really disappoint the persona in this sort of app?” The third list asked “what could make the persona really happy about this app?” We focused as an entire group on each persona and used sticky notes to fill-in the lists. I read them to the group as they were posted until we’d broadly filled out information for three personae with input from the group. This part is not a long exercise because of what follows. That evening, I clustered the sticky-notes based on their similarities and used a short phrase to characterize each cluster. This made each persona more referenceable for the next day’s exercise.</p><p><strong>DAY 2 — EMPATHY/JOURNEY MAPS &amp; APP MISSION STATEMENT</strong></p><p>The following day, we created a combination of a journey map and an Empathy map. It is a diagram with steps in a process across the top and down the left-hand side, a list of senses and actions the user might experience during those tasks. The exercise took us through the things a person using the app will encounter before, during, and after their experience. While capturing touchpoints and their likely emotional state, it also captures what they perceive through their different senses and what they might be thinking. It’s a deeper way to inhabit the world of a person and ultimately helps the participants separate the persona in their mind from themselves (everyone’s default “user”). To do this we had a grid set-up in Miro and as we took each persona though the journey, we used sticky notes to say what they might be thinking, feeling, or doing at that moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*pkrEA3r78hoH-jcBsEO3VA.png" /><figcaption>Fig 3. Zoomed-out view of the Empathy/Journey Map</figcaption></figure><p>It turned out that taking our time with the first exercise paid dividends. By this point everyone was thinking about the user rather than how to open and place a sticky note.</p><p>To move the session along, we created Zoom rooms so we could divide into teams and work separately. Each team took ownership of one of the personas answering questions from that customer’s point of view. For example: “During checkout, what is Susan thinking about?” or “Between placing an order and receiving his food, what was Omar feeling in that moment?” While they completed the grid for an individual persona, they were posting stickies on the same board which was a little chaotic, but it worked. I was able to drop-into each Zoom room to see how the teams were doing and answer any questions about the exercise or their persona.</p><p>The final exercise was to collect the terms that we would use to craft an app mission statement. Rather than dust-off an existing corporate mission statement, we created one just for the project. This is a standard Bottle Rocket practice that we adhere to for each new app build we work towards. It gives everyone involved a north star to revisit and keep top of mind throughout all decisions. To do this, we made two lists using the document camera. The first list contained the different adjectives one might use to describe the finished project. The second list asked for emotions that might be felt when the application is used. I would later use some of these terms along with the success statements from the first exercise to craft the mission statement. Doing it this way is much more efficient than trying to word-craft in a room full of 12+ people. By writing it myself I can work with key stakeholders to refine it later.</p><p>To wind up the sessions, we explained how this Discovery work will inform the ongoing project, and then discussed the next steps to begin designing the interface. Obviously, there would be further meetings about user stories and how the capabilities of the app will support the business, but these exercises often reveal reasons to downplay or eliminate certain features while creating or emphasizing others. Without Discovery we can’t really know if we are solving a problem for the people who will use the app.</p><p>More learnings I picked up along the way:</p><p><strong>Learning #3: You can only expect so much participation in a day.</strong> Fortunately, we determined that a full day in front of the computer would be too much of a beat-down for everyone, so we divided the session into two segments, four hours each, over two days.</p><p><strong>Learning #4: There is still a lot of homework for the moderator; just a different kind. </strong>I had to spend a fair amount of time before we could continue and after sessions for review. I had to make sense out of the clusters of sticky-notes and characterize the groups before we could continue.</p><p><strong>POST DISCOVERY</strong></p><p>That evening I extended the data in the Empathy/Journey Maps to capture the emotional state of the users at each point in the task flow and connected the points to show the ebb and flow across the tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*CgyMA5z-EIUBVpLQe80GMA.png" /><figcaption>Fig 4. Derived emotional states along user journey</figcaption></figure><p>It was critical to distill the data we compiled into artifacts to help us remember the key attributes of the experience through the eyes of our personae. I created Journey Maps by first downloading all the sticky-notes to a spreadsheet. The spreadsheet let me see how similar observations rolled-up into key phases of the experience. I translated them into a set of illustrated pathways with different characteristics. This deliverable was also posted to the Miro board which now stands as a record of our activities. Later that week, we came back together to review our work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*LHpwnG9_xwH6Q7lXRIjHqw.png" /><figcaption>Fig 5. Illustrated pathways to display different experiences from the user’s point of view</figcaption></figure><p><strong>SO, HOW DID IT GO?</strong></p><p>The team regrouped a couple of days later to review our efforts and review the deliverables that emerged. The “Success Is..” exercise, the development of separate personae, the deep-dive using the Empathy/Journey map, the app mission statement, the emotional graph, and the illustrated user journeys together gave us a picture of the users and their different experiences from various perspectives. We also canvassed the team for feedback about what they thought was successful about our sessions and gather feedback on what needed work.</p><p>Comparing this effort to our usual method, there were some things we missed that come with being face-to-face in a room together like general spontaneity — everything had to be planned more prescriptively. Being remote eliminates cues from facial expression and body-language that help you pace the meetings or shift focus. You lose the ability to step into a hallway for a quick sidebar that leads to a course correction even though there were ways to communicate in the background. Pivoting in this environment would be much harder.</p><p>On the other hand, the nature of the environment created in Zoom made it easier to hear and understand people speaking and I think there was a leveling effect that encouraged people to speak-up. We can now consider alternatives to requiring everyone to be in the same physical space when sometimes, that just isn’t possible. When we emerge to a time when social distancing can be safely relaxed, some of these techniques will become fixtures in our future approach.</p><p>Ultimately, the effort was successful in that the client was highly engaged, understood the purpose of each exercise, and valued the time we spent together on this process. The ultimate testament is the client is pleased and we’ve learned so much about our client and their end users to inform the design and development process going forward.</p><p>In summary, I would say this process was successful at replicating some of the human-to-human interaction that makes Bottle RocketBottle Rocket. This process is definitely not a script for all future Discovery sessions, but rather an attempt at trying something new given our new circumstances in an effort to maintain as much of our Bottle Rocket norms as possible. We were able to create an atmosphere focused on great outcomes rather than simply executing on a pre-determined list of features and functions, even while all working remotely. This is just one of the many tools we have at our disposal to better understand our clients, their customers, and ourselves a little better. We’re definitely not the first company to face this challenge, but hopefully this process and our learnings can help you if and when you are presented with a similar challenge. On to the next!</p><p>P.S. If you were curious about all of the technology used to make this possible, see below.</p><p>My rig:</p><p>· Laptop — 2017 13” MacBook</p><p>· Monitor — Dell 27”</p><p>· Camera — Unzano HF2 Streaming Webcam (USB)</p><p>· Microphone — Samson Meteor Mic (USB)</p><p>· Document Camera — IPEVO V4K Ultra High Definition (USB)</p><p>· Whiteboard — 9 x 12 laptop whiteboard</p><p>· Markers — Steadtler Lumocolor Correctable</p><p>Software:</p><p>· Zoom for communication</p><p>· Miro for a digital whiteboard</p><p>· Slack for back-channel communication</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5e4b0cef1b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/atlas/tossed-into-the-deep-end-f5e4b0cef1b7">Tossed Into the Deep End</a> was originally published in <a href="https://medium.com/atlas">Atlas</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BLURRED LINES: Using Design to Solve for the Right Outcomes — Part 4 of 4]]></title>
            <link>https://medium.com/@AdamtheIA/blurred-lines-using-design-to-solve-for-the-right-outcomes-part-4-of-4-298927081378?source=rss-604d74a30f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/298927081378</guid>
            <category><![CDATA[quality]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ethics]]></category>
            <dc:creator><![CDATA[Adam Polansky]]></dc:creator>
            <pubDate>Fri, 12 Apr 2019 14:24:10 GMT</pubDate>
            <atom:updated>2019-04-12T14:24:10.115Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>BLURRED LINES: Using Design to Solve for the Right Outcomes — Part 4 of 4</strong></h3><p>Adam Polansky</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*QmCGy9in6TQ0qNxT3i5zLA.png" /></figure><p><em>In Part three we examined the relationship between quality and other project constraints. Part four looks at intent and being responsible for your work.</em></p><p><strong><em>Bad intent erases quality</em></strong><em>.</em></p><p>You can do the most elegant work but bad intent erases that.</p><p>I grew up with marketing and advertising. I got really good at convincing myself of the reasons for doing work for people with bad intent. Strictly speaking, what they’re doing was legal. For instance: a pawn shop is a legal business. The truth is they engage in predatory business practices. They take advantage of people in a bind. I could tell myself that they provide a service to the unbanked or unbankable. I could rationalize with the best of them. But I would put the truth in a little box and close the lid. I wouldn’t open it because I knew if I examined it closely enough, I wouldn’t like what I saw.</p><p>Everyone has their reasons</p><p>” I’m not paid to make the decisions about our clients.”</p><p>“I have a mortgage.”</p><p>“I have kids that I want to send to college.”</p><p>“I like and want to keep my job.”</p><p>“Somebody is going to get this job. It might as well be us.”</p><p>Those are good arguments. Everyone has their own scale for what’s acceptable to them. That’s your moral compass. Ethics are not morals. They are empirical. One day you may find yourself at a fork in the road where you know your moral compass and the ethical approach are diverging. What if you learn that your company just landed an account for a big utility firm. That’s big news and probably big money. But what if that company is nationalized in a country where the leadership uses it to locate and imprison “enemies” who eventually disappear; a capability made easier by the design work you’re being asked to do? Morally, you might be able to distance yourself from the outcome; you put it in that little box and shut the lid and later you feel bad when you hear about the events on the news. You might even connect those events to your work but it’s just business, right? You have all those good arguments remember? Morality might be debatable but ethically, you’re accountable.</p><p>In his Designer’s Code of Ethics, Mike Monteiro says Designers are human beings first and that we are responsible for the work we put out into the world. That means we own the outcomes even when they are unpredictable but especially when they are. You may be able to live with that. You may not.</p><p>If you keep asking “Why” you might uncover the fact that people have bad intentions for the work you do. You can rationalize away your accountability or accept it. Refuse the work if you can. Try to convince decision-makers to refuse the work. If you’re unsuccessful…quit. I know that’s easy to say but I faced a situation where I had to decide for myself if I was willing to walk-out over our pursuit of a prospect. I talked with my wife long into the night before I raised the subject at work. I made my case. I connected some dots that leadership had not. Fortunately, we stopped pursuing the company. I know I was willing to walk. Fortunately, I didn’t have to test that resolve. Something else I can tell you with absolute certainty, if you have an ounce of empathy, you’ll regret some of the compromises you made in life. It’s going to happen. Which will you regret more, quitting or enabling bad intent that caused people harm which could include murder? That’s an outcome.</p><p>With great power comes great responsibility. I would add If you want the responsibility, you have to accept accountability. If you can’t or won’t, don’t accept the work. <em>Having a seat at the table means knowing when to refuse it.</em></p><p>Deliberately decide what your principles are and stick to them. That‘s what makes them principles and not just guidelines. Have the vision to see the longer horizon and the outcomes that can’t be achieved any other way. There are no short-cuts.</p><p>Commit to your design principles and quality. If you don’t people will have SOME kind of experience by default. Why wouldn’t you want to move that in the right direction deliberately, ethically, and magically?</p><p>***</p><p>This ends the series. In case you haven’t read the previous installments, they covered…</p><p><a href="https://t.co/B6GtPaofIM"><strong>Part One </strong></a><strong>— </strong>The best solutions fill needs. Ask “Why?“ to uncover the real needs. They need the best minds to tackle them not just MBAs but designers of all definitions.</p><p><a href="https://medium.com/@AdamtheIA/blurred-lines-using-design-to-solve-for-the-right-outcomes-part-2-of-4-1acf3e8a4913?source=friends_link&amp;sk=e2e91ae732255738ab1ef7efdf190e55"><strong>Part Two</strong></a><strong> — </strong>People have expectations. Meeting them is great. Exceeding them is better.</p><p><a href="https://medium.com/@AdamtheIA/mmblurred-lines-using-design-to-solve-for-the-right-outcomes-part-3-of-4-12d1bf8ff171?source=friends_link&amp;sk=ead9c047900061aeb580f1f3a793e106"><strong>Part Three</strong></a><strong> — </strong>Commit to the value of quality. Artificial Intelligence is burning-up the headlines but I’ll say it. There is no piece of software in the world that can replace creativity in the moment. That’s where the kind of quality we see as magic emerges. Everybody wants it, but it needs protection in the form of championship and enterprise commitment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=298927081378" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BLURRED LINES: Using Design to Solve for the Right Outcomes — Part 3 of 4]]></title>
            <link>https://medium.com/@AdamtheIA/mmblurred-lines-using-design-to-solve-for-the-right-outcomes-part-3-of-4-12d1bf8ff171?source=rss-604d74a30f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/12d1bf8ff171</guid>
            <dc:creator><![CDATA[Adam Polansky]]></dc:creator>
            <pubDate>Fri, 05 Apr 2019 02:55:40 GMT</pubDate>
            <atom:updated>2019-04-12T14:26:22.257Z</atom:updated>
            <content:encoded><![CDATA[<p>Adam Polansky</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*QmCGy9in6TQ0qNxT3i5zLA.png" /></figure><p><em>Part two explored solving problems from a design perspective. Part three takes a closer look at the dynamics of quality and a business’ perspective of its importance.</em></p><p><strong>Quality</strong></p><p>I remember our first microwave oven in the 70s. We’d put a piece of cheese on a Dorito and watch it sit there. Suddenly the cheese would bubble-up and melt across the chip. It was like time-lapse photography in real-life. That’s all we had to compare it to. We watched it like TV for weeks; It was an event whenever someone made a hot dog. My dad also was with Amana when they developed the first radar range, so he understood the principles involved and he explained basic microwave science. Our response? “Yeah, that’s cool dad. Gimme another piece of cheese”.</p><p>Just about any application has room for improvement. Can you make it simpler by removing friction points to streamline a process? Maybe you need to add friction points to make a complex process manageable.</p><p>Can you find a way to improve convenience? Face it. We’re lazy and love anything that can save us a tap or a click.</p><p>Look at your favorite apps, look between the screens at what really happens when you tap or click on something. Does the screen just become a new screen or are there cinematic transitions? Does one image evolve into another? Do they set a tone? A box or image that glides-in says something different than one that bounces. They aren’t quite subliminal, but the aggregate effect of these transitions can create an experience that is calm, energetic, practical, frantic or…magical.</p><p>Magic is what we call something that can’t be explained. An experience can be so good the device disappears and you forget you’re holding a little computer or sitting in your living room or at your desk. Yes logically, we know there are real explanations like microwaves but we like to suspend that knowledge because frankly, it’s more fun to believe in magic…even if it’s just for a little while. We get to make magical things. All these elements speak to Quality. Quality is the province of UX; not exclusively, but quality is where our influence can be seen</p><p>Quality is in the UX details that speak to finesse, completion, fit and finish and usability. All these things roll-up to Quality. Quality needs protection because it can’t speak for itself on a spreadsheet tomorrow. What do I mean by protection?</p><p>Every project is acted-upon by three factors. We know this. Time, Cost and Quality or Good, Fast &amp; Cheap. There is a general belief that a product owner gets to control two of these dynamics at the expense of the other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*YMpuE-slSK3mTE6_qpFgWg.png" /></figure><p>That’s a lie. You get one. I say this because if you decide that time and cost are going to be controlled, you WILL have to break that tie at some point downstream and it will cost you time or money. You can help yourself by determining which of the three has the least flexibility when compared to the other two. Which has the most and what’s in the middle.</p><p>Here’s the problem: People in charge like predictions. They want to know when they’ll go to market because they are coordinating other efforts. They want to know what the expense will be so they can predict what the ROI will be. People can and do make those numbers up arbitrarily. How do you estimate the ROI of Quality? How much time does quality take? Quality isn’t a direct cause/effect dynamic. There are phases in-between before it’s realized. Some people don’t have the patience for that.</p><p>Here’s another fact. People will do the most nonsensical things to avoid pain. When a project gets going, it doesn’t take long before time or money is causing pain. When we’re in pain we get tunnel vision. We lose trust in others especially if we think the pain is their fault so we’re less likely to take advice. We also want pain to stop RIGHT NOW so we lose sight of longer-term benefits of quality. Since we want the pain from time or money to go away, we cut scope, that scope usually includes the refinement that gives a product quality. Quality ends-up on the curb because the pain from bad quality can be deferred — remember we want the pain to stop NOW. Quality needs protection because it can’t be dissected into pieces on a spreadsheet and put back together again in any way that works. If you begin by understanding the real needs of real people and using that as your context, you make quality less flexible, it will be worth the time and money. How much? I don’t know but I do know it will cost more if you don’t keep it in the picture.</p><p><strong><em>Quality is easy to defer and impossible to recover</em></strong></p><p>It’s impossible to recover because recovery means more of the time and cost you thought you were saving. By the time you realize it, it may be too late. You put a piece of crap out there and now you have to win-back lost credibility with stakeholders and the people using the product who got shorted on the first go-round. People won’t care what it cost. People won’t care how long it took unless they’ve been led to expect it by a certain date which only raises the anticipation and magnifies the disappointment if the quality is poor. That…after all, is what they do care about.</p><p>In the long-run. Quality abandoned will <em>always </em>cost you more than quality implemented.</p><p><a href="https://medium.com/@AdamtheIA/blurred-lines-using-design-to-solve-for-the-right-outcomes-part-4-of-4-298927081378?source=friends_link&amp;sk=c81098fc2e35caeac3444ca2689a33dc"><em>In Part 4 I’ll offer some thoughts on intent and being deliberate about the problems you solve and why.</em></a></p><p><a href="https://t.co/B6GtPaofIM">In case you missed Part 1</a></p><p><a href="https://link.medium.com/Or6eTTr1CV">In case you missed Part 2</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12d1bf8ff171" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BLURRED LINES: Using Design to Solve for the Right Outcomes — Part 2 of 4]]></title>
            <link>https://medium.com/@AdamtheIA/blurred-lines-using-design-to-solve-for-the-right-outcomes-part-2-of-4-1acf3e8a4913?source=rss-604d74a30f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/1acf3e8a4913</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[problem-framing]]></category>
            <dc:creator><![CDATA[Adam Polansky]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 14:37:32 GMT</pubDate>
            <atom:updated>2019-04-12T14:28:56.143Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>BLURRED LINES: Using Design to Solve for the Right Outcomes — Part 2 of 4</strong></h3><p>Adam Polansky</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*QmCGy9in6TQ0qNxT3i5zLA.png" /></figure><p><em>In Part One I talked about ways to frame problems, in Part Two, we’ll look at how to approach solving them.</em></p><p><strong>Solving problems by design</strong></p><p>Herbert Simon gave the best definition of design: “To design is to devise courses of action aimed at changing existing situations into preferred ones.“ Recently in an interview, the designer Milton Glaser, one of the greatest designers of our time, gave an interview where he said. “Design is the process of going from an existing condition to a preferred one.” Whether he knew it at the time or not, he was paraphrasing Simon. Did you notice that neither of them made any reference to art in their statements? Glaser went on to talk about how things can be rendered many ways; not just by an artist. He used to say that “Design is to communicate clearly by whatever means you can control or master.” Still not a direct reference to art. Yes, in terms of accountability, art directors are responsible for design but the responsibility also falls on engineers, information architects, strategists, product owners even quality assurance because they all inform the end product toward a purpose — a desired state. Great design doesn’t just look good. It works well and it’s a vehicle for great experiences for the people who use it. We can equate quality with good design.</p><p>For the longest time, we designed for roughly the same environment. (I’m talking specifically about digital now.) A person sitting at a desk, 18–20 inches from a screen with a keyboard and a mouse. Then, technologies raised the bar for what people expected from it because devices like personal digital assistants (PDAs) and Blackberries moved tasks from the desk to our hands. About 10 years ago, we got an app store and a limited environment opened-up even more to the point that a mobile phone serves as the only computer many people need or own. New considerations come with that. Luke Wroblewski described the need for an application to be manageable with one eye and one thumb. Back In the mid-nineties, people were talking about WANs, Wide Area Networks, LANs Local Area networks but they were just whispering about PANs -personal area networks. That term may have died but look at what we have! We’re personally connected to our homes, our cars, our music, our families and our caregivers. We maintain relationships of a sort with people around the world. I know what beer my friend in New Zealand drank with dinner before the appetizers were finished.</p><p>We’re designing for more than one generation that grew-up on games with rich interaction and responsive controls. These folks don’t just hope the tech they use professionally and personally will be similar, they expect it. They expect it to surpass…routinely. <em>The best experiences align with what you desire in your world.</em></p><p>When it comes to designing solutions, you don’t have to look far for the problems; usually no further than the people who use your products or services. There is almost always something that can stand to be improved. It may not be your product but it may be the support. A solution might be operational but it may also be solved on line, or with a mobile device or wearable. Somewhere you can find a way to ease a process by removing or even adding a few steps. Maybe a solution is too far from where the problem occurs and maybe you can find a way to close that gap.</p><p>Observe what people are doing and where they are doing it; home, office, the park, the train, the bathroom? Don’t laugh! How many of you have started to walk towards the restroom only to do an about-face, grab your cell phone and <em>then </em>go?</p><p>How and why are they doing things? Is it a direct result of what and where? What are the connections? What results are they experiencing? How do they feel about it? Are they happy, pissed-off, indifferent?These are the elements of a journey map — one of several tools used to characterize the context around an activity. This is where you find your opportunities.</p><p>What else will fuel your insight? You may have participated in one or all of these data gathering methods.</p><ul><li>Interviews to hear what people are thinking.</li><li>Field Observation while you’re in Discovery to see what people are actually doing.</li><li>Usability testing of early prototypes and completed apps to hedge your bet that people can actually use them.</li><li>Analytics after launch to extract what’s really happening with your products.</li><li>Rinse and repeat.</li></ul><p>No single method will give you all the insight you need. It’s the combination and repetition of methods that gives you a more complete, more faceted picture in 3 dimensions. We talk about them all the time. The thing is…you have to DO THEM! Find a way. You can sneak this stuff in.</p><p>Another place you can look is off-screen. Most of you know what a 2D graph looks like; two planes — X &amp; Y axes. But…add a Z plane and you are working in 3D now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/216/1*n2a_5WVlroTJUJpFDNmj0Q.png" /></figure><p>Why is this important? Because all the things that happen in the world you’re observing happen in the Z space. Whatever we’re doing on a screen is often connected to something we’re doing off the screen. What do you think is so attractive about virtual reality or augmented reality? It offers an environment like the one we live in with physics we can readily understand. That said, if you think a VR project is necessary, you have to observe the world you want to create. What is the physicality of that world? Will it mimic the physics we know, or will it go beyond giving people extraordinary powers? Also, be deliberate when you determine its value not just to your enterprise but to the people who’ll use it. Innovation is measured by comparing the effort to produce something to the value it brings. Do you want to teach with it? Inspire? Entertain? Be productive? Challenge? Has anyone not seen a sci-fi movie that shows someone interacting with a virtual environment? Does it ever occur to you that if you did that all the time, your arms would get tired? American Sign Language interpreters work in teams of two for that exact reason. Something “cool” might have a short life-span if it isn’t sustainable.</p><p>Why is the Z Space so important?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/1*i1UszxNzOhp9-BEdwhVA7Q.png" /></figure><p><em>Hype Cycle for Emerging Technologies, 2015: © Gartner, Inc. 2015</em></p><p>This is called the Hype Cycle — it’s a story that shows the journey of ideas. This one charts the path of emerging technologies and I just want to point-out that well over 50% of these techs exist beyond the app. They operate in the Z space. They face different challenges; the supporting tech may be too immature, infrastructures may not be in place, economies of scale still hard to realize or predict or maybe…people’s arms just get tired. These are problems and expectations are building around people like us solving them because, more specifically, <strong><em>they are design problems.</em></strong></p><p><a href="https://medium.com/@AdamtheIA/mmblurred-lines-using-design-to-solve-for-the-right-outcomes-part-3-of-4-12d1bf8ff171?source=friends_link&amp;sk=ead9c047900061aeb580f1f3a793e106"><em>Part 3 will take a closer look at the dynamics of quality and a business’ perspective of its importance.</em></a></p><p><a href="https://t.co/B6GtPaofIM">In case you missed Part 1</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1acf3e8a4913" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BLURRED LINES: Using Design to Solve for the Right Outcomes — Part 1 of 4]]></title>
            <link>https://medium.com/@AdamtheIA/blurred-lines-using-design-to-solve-for-the-right-outcomes-part-1-of-4-8df9c767ce5b?source=rss-604d74a30f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/8df9c767ce5b</guid>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Adam Polansky]]></dc:creator>
            <pubDate>Fri, 22 Mar 2019 17:04:05 GMT</pubDate>
            <atom:updated>2019-03-29T14:42:24.374Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>BLURRED LINES: Using Design to Solve for the Right Outcomes — Part 1 of 4</strong></h3><p>Adam Polansky</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*QmCGy9in6TQ0qNxT3i5zLA.png" /></figure><p><em>World Information Architecture Day is an event with gatherings happening simultaneously in over 50 countries around the globe. The theme in 2018 was “IA for Good”. I was invited to Austin to speak to students at the University of Texas Information School. I chose to talk about Design’s place in the world and the good (and harm) we, as User Experience professionals can do. It’s broken into four parts.</em></p><p>About forty years ago, a guy named Ray Ruby figured out that if you put a drop of liquid in one end of a tube of a specific diameter, you could predict exactly how much force or surface tension it would take to move that liquid to the other side of the tube. Surface tension is what holds a drop of water on the end of your finger before it falls. What could Ray and his friends do with this knowledge? Well, they embedded four of these tubes in a round plate that would show the tubes turning red if they were shaken or dropped. The plates were used in Disk-Packs; the industrial grand-daddy to the floppy disc. A disk-packs was about the size of a Tupperware cake carrier and sat inside a disk drive about the size of a dishwasher. Problem was…if you dropped or mishandled a disk-pack you wouldn’t know if it was damaged until you put it in the drive and it crashed. But…If you looked at the four little tubes in the top of the pack and any of them were red, that could tell you the pack had been dropped or mishandled. Everyone thought this was great! Honeywell, the manufacturer of the disk-packs and drives became their first customer. Now they just needed more customers like that. So, they hired a guy to find them. His name was Dick.</p><p>Over the next two years, Dick learned that there weren’t any other clients like Honeywell but he did make an observation: All over the world, people were putting things in boxes and shipping them without any idea what was happening to them in transit. What if there was a way to monitor your shipment?</p><p>Dick recommended putting the tubes in stickers on boxes. If you received a box with a red indicator on it, you didn’t accept it. That’s what they did. But you might not guess what happened. “Instead of people buying “clips” and slapping them (gently) on their packages, the shipping companies bought them. They created awareness programs for their employees and promoted the fact that they were proactively looking out for the condition of your stuff. Companies saved money by not accepting potentially damaged packages, they saved money in replacement parts, shippers were more careful when handling goods. The Shockwatch changed the way people behaved because observing their behavior in the first place led to a solution with an outcome different from the one they set out to solve.</p><p>Dick’s last name was Polansky and he was my father. His idea would grow into ways of preventing damage to forklifts, warehouses, rail cars, autos and paper rolls. I grew up around smart people who solved problems by understanding the nature of the environments their products occupied….and by asking “Why?”</p><p><strong>Problems</strong></p><p>How often does a conversation like this occur? The C-somebody EO, MO, TO … says “We need a program, a mobile app, a website, an Internet of things because…reasons; It’s going to be big, we need some of that, we need to be in that channel. When that happens, does anyone ask “Why?”; because those reasons aren’t reasons. Someone needs to ask “Why?” and keep asking until the problem can be clearly stated and the weight of need (if there truly is any) can be understood. How do you recognize that need?</p><p>In the book Gamestorming, by Gray, Brown &amp; Macanufo., there’s an exercise created by Sakichi Toyoda called the “5 Whys” We use it where I work to get to the root of a problem. If we take the example of the Shockwatch, the conversation might have gone something like this:</p><p>“Our equipment costs are so high!” — “Why is that? “</p><p>“Equipment is often damaged when we receive it. You can’t see that when it’s delivered so we accept the equipment.” — “Why so much damage?”</p><p>“The shippers are mishandling our equipment in transit.”- “Why do they do that?”</p><p>“There’s no accountability.” — “Why is that?”</p><p>“No one can prove exactly when the damage took place. There’s no monitoring.”</p><p>This conclusion would have shown the team where the real problem was and where to focus their solution.</p><ul><li>What’s broken that needs fixing? …WHY</li><li>What works but could work better? …WHY</li><li>Who benefits? …WHY</li><li>Who loses? …WHY</li></ul><p>When it’s all said and done what will be the result…and WHY?</p><ul><li>WHY uncovers reality.</li><li>WHY can force honesty.</li><li>WHY can get you to root of a problem that really DOES need to be solved</li><li>WHY can generate an outcome that really DOES need to be realized</li></ul><p>That outcome is the context you’ll be working within to solve your problem. <em>A Solution without context is an abstraction.</em></p><ul><li>You can’t build an abstraction</li><li>You can’t estimate the value of an abstraction</li><li>You can’t predict what an abstraction will do</li></ul><p>You’ve heard about solutions in search of a problem. For context, begin with the problem.</p><p><a href="https://medium.com/@AdamtheIA/blurred-lines-using-design-to-solve-for-the-right-outcomes-part-2-of-4-1acf3e8a4913?source=friends_link&amp;sk=e2e91ae732255738ab1ef7efdf190e55"><em>In Part Two, I’ll explore ways to solve problems by using what you know as a designer.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8df9c767ce5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proving Your Way Out of the Dog-House]]></title>
            <link>https://medium.com/@AdamtheIA/proving-your-way-out-of-the-dog-house-1a0a4ccc29c2?source=rss-604d74a30f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a0a4ccc29c2</guid>
            <category><![CDATA[enterprise-ux-2017]]></category>
            <category><![CDATA[eux17]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[this-happened-to-me]]></category>
            <dc:creator><![CDATA[Adam Polansky]]></dc:creator>
            <pubDate>Sun, 11 Jun 2017 16:19:54 GMT</pubDate>
            <atom:updated>2017-06-11T16:19:54.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E3B7kD9IM38mybDLEfh1PA.png" /></figure><p>Enterprise UX 2017 Storytelling Session — UX Horror Story</p><p><em>The Enterprise UX Conference sets aside a segment for 5 minute talks. They can be inspirational, rants or as in this case, cautionary tales. This is the transcript from my 5 minute talk.</em></p><p>I was sitting at my desk in the dark wondering if I could get all my shit to the car in one trip.</p><p>Back-up a couple of days to me working with a client’s advance team on a laundry list of items they wanted to cover when their execs were in town the next day for meetings. I had to distill all that information and create the presentation materials to discuss it. As the lead strategist, I would also be leading some of those discussions. The client’s unapologetic expectation was that I simply work through the night to be prepared; which I did.</p><p>The next morning, I met with the executives from our largest, most profitable, most visible client; an internationally known brand, along with our executives including the founder of our company for a day of planning and review.</p><p>Things went mostly as expected then…late in the day during a break, someone added a new topic to the agenda on the whiteboard. I’ll call it project “X”. It had to do with an iPad app and It was a sore subject because the client kept going back &amp; forth about when they wanted it. I’d been requesting information to scope it for some time. I had nothing. As a discussion topic, I had nothing. I asked the client Program Manager how this should go and I was told “Don’t worry, we got this one. You won’t have to speak to it.”</p><p>A few minutes later, the client SVP asked: “What about project ‘X’?”</p><p>Silence.</p><p>As that silence started to gain weight, someone said “That’s a question for Strategy.” You know the shot in the movies when the background flattens-out as the camera zooms-in on a panic-stricken face. That was me. This might be a good time to mention that I have…distractibility issues and difficulty filtering and measuring my responses at times. For this I take medication which had worn-off way back the day before.</p><p>Everyone was waiting. The client Program Manager wouldn’t look at me. I realized in that moment, I was under the bus.</p><p>“Well…” I said,</p><p>“In the absence of the information I’ve been requesting for nearly 3 months, your iPad app will look like an oversized, fucking phone.” My sleep-deprived, filterless brain shouted <strong><em>Nooo</em></strong> as my words landed in the middle of the table with a big…wet…thump.</p><p>I didn’t just crawl-out from under the bus, I flung the Program Manager under it and tossed a hand grenade over my shoulder as I did so.</p><p>Pause — Cue the explosion. People were up out of their chairs huddling into small fast-talking groups. There were no questions. The meeting was over and I slunk back to my desk which brings us back to me sitting in the dark, when my CEO hurried-by. He didn’t see me until I called to him and said “Look, I know that was a mess in there and I will do whatever I need to and apologize to whomever I need to.”</p><p>I wasn’t expecting his response: “Hey. I heard you’ve been awake for nearly two days. Are you okay?” I was completely off-balance. Then he said, “Yeah, I‘m still not sure what just happened in there.” Through the glass walls, I could see everyone still huddling in earnest. Some were already picking-up their coats to leave for the airport. It was still chaos and my boss probably should have been present. In spite of that, he took a seat, invited me to do the same and we talked for about 10 min. Now, at no time did he tell me everything would be okay but we talked about how things <em>might</em> have gone a little better. He was both calm and helpful.</p><p>About a week later I was told the client “wasn’t comfortable” with me in front of their execs anymore. I was fired from an account for the first time in my life but the business was still ours.</p><p>So…You may not do it as spectacularly as I did, but you’re going to screw-up and when you do, remember, what you did and why you did it doesn’t matter. How you handle it means everything.</p><p>First, Own it. You can’t move forward until someone takes responsibility. Even in the debrief, when they threw me a bone and suggested I was ambushed, I said that didn’t matter. It was more productive just to own it than to dissect which parts to own.</p><p>Next, serve your penance. Until we could hire a replacement, I had to spend three more awkward months working for a client that didn’t want me around. It was rugged but I never complained. Staying professional, helped me get square with the house again. They didn’t dump me out the airlock but make no mistake, I was on notice.</p><p>Last, move on. Take what you can from it but move on. Ultimately, this proved to be one of the best learning experiences I ever had because it uncovered some fundamental things I needed to do differently. Absolutely take the time to understand what happened so you can avoid it in the future. I had developed an attitude about this client. I felt like the project was broken and dysfunctional and, meds or no meds, I let it show in a bad way. I spent so many years being the guy who fixes broken projects, I just dove-in without asking the client if they thought anything needed fixing. Turns-out, they didn’t. There were other observations but that was the main one. Identify your role in the mess but don’t let that be the ongoing conversation. Also, moving-on means everybody. If you have someone who won’t let you live it down, you need to address it with them. I was lucky, I got the chance to prove myself out of the dog-house without having it thrown in my face later.</p><p>Does it work-out like this way every time? No. When it’s your turn, you may still wind-up on the curb but this is a way to keep from having one moment define you even if it’s just for yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a0a4ccc29c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[12 Things UX Champions Do]]></title>
            <link>https://medium.com/@AdamtheIA/12-things-ux-champions-do-201346549ff5?source=rss-604d74a30f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/201346549ff5</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[championship]]></category>
            <category><![CDATA[enterprise]]></category>
            <dc:creator><![CDATA[Adam Polansky]]></dc:creator>
            <pubDate>Mon, 24 Oct 2016 15:58:19 GMT</pubDate>
            <atom:updated>2016-10-24T20:12:45.245Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>It is literally true that you can succeed best and quickest by helping others to succeed. — NAPOLEON HILL</blockquote><p>More than any other discipline, User Experience needs protection. It needs championship.</p><p>UX is in a paradoxical situation. Businesses are clamoring for UX professionals and claiming loudly that UX is the key to success for creating loyal customers and for extending and maturing their brands. On the other hand, UX has a hard time establishing a foothold in an enterprise. I believe the reason is that UX is tied closely to Quality. Along with Time and Cost, Quality is one of the three project pillars. Time is mostly the domain of development and Cost is owned by the stakeholders. The fact is, Time and Cost begin to cause pain at the outset of any project. Pain from bad Quality won’t be felt until much later so it can be deferred. Since stakeholders and project leaders want to manage pain, they start looking for ways to reduce scope which, in turn reduces Quality. When Quality ends-up on the curb, so does UX. Great experiences are the result of balance between UX and Development. A project driven out of that balance won’t have a solid result.</p><p>Here’s a list of things champions do to help create great experiences that are the result of a good balance between Development and Design.</p><p>You have to play in two arenas; the <strong>Team</strong> which might be a single project group or the UX leadership over several projects and the <strong>Enterprise</strong> which includes your supervisors and peers across the organization. It’s a combination of strategy, tactics, direct involvement and Public Relations.</p><h3><strong>The Team</strong></h3><p><strong>Servant leadership</strong>. Promote the people on the team to give them the best opportunities for advancement and recognition. That means moving obstacles and running interference so they can do their best work and then shining the spotlight on them for a job well-done. Don’t be in it to take bows but to make heroes of others.</p><p><strong>Demonstrate your trust in team members</strong>. Your peers and leadership may not know or trust the members on your team but they may trust you. Broker that trust to win opportunities for your team to work effectively.</p><p><strong>Advocate unconditionally</strong>. Make sure your team knows you have their back without question by default. Let them know that you will go to the mats for them without hesitation as long as they are honest and keep you informed.</p><p><strong>Share pain</strong>. Is your team pulling an all-nighter? This is when they feel most unappreciated. Be there with them or at least stay in contact. Feed them. Find ways to reward them as they do the work. Own the screw-ups. That’s part of the job. If teams know you’ll throw one of them under the bus to save your hide, they won’t trust you.</p><p><strong>Be translucent with your team</strong>. If you have any gripes, point them upstream in your organization. Your team doesn’t need to know your hardships but they do need to know about anything that will affect them.</p><p><strong>There’s magnifying glass on you.</strong> If you are in a mood; good or bad, it’s magnified to your team. Remember that. If you need to have hard conversations the gravity will seem greater. If you are positive, it will have a halo effect. Either way always be honest.</p><h3><strong>The Enterprise</strong></h3><p><strong>Put UX in an existing context. </strong>Inside the Product Development process, establish clear UX steps and milestones. Shift the conversation away from UX explicitly and talk about Quality.</p><p><strong>Campaign Publicly. </strong>Establish executive buy-in and air cover. Make publicized commitments. Build your relationships with Sales, Marketing, HR, Legal and Line of Business Managers. Make sure the whole company knows you value UX and the need for its impact.</p><p><strong>Find new metrics.</strong> The ROI from Quality can’t be predicted in the same way costs are factored. Stakeholders’ unwillingness to take a risk pre-empts research, innovation and imagination. Speak to outcomes. OKRs (Objectives &amp; Key Results) should drive KPIs (Key Performance Indicators). A great experience is a desirable outcome and teams should be given room to determine how to realize that outcome not just build features. Help stakeholders understand and <em>want</em> those outcomes.</p><p><strong>Be the arbitrator. </strong>Are there tribal differences between Design and Development? — UX and Marketing? Find ways to make sure they’re communicating. Make sure Design concepts are demonstrated to developers before leadership.</p><p><strong>Look for deferred wins</strong>. Not everything has a direct cause/effect. Especially qualitative efforts. Find a way to explain benefits that are the result of a chain reaction.</p><p><strong>Play the long-game</strong>. So many operations can’t look past the next quarterly earnings call. If the ROI isn’t captured within three months of investing, it won’t get funding. Not everything yields an immediate turn-around and often the quick win is a small win. Look at longer horizons to give efforts the chance to grow bigger by having the time to establish a strong foundation. You’ll see a bigger and more sustainable pay-off.</p><p>Not every project will be a smashing example of great User Experience. You’ll have to make compromises. If you can carve-out some room for Quality, you’ll build momentum that makes it easier for others to have the patience for the rewards it will bring. Being deliberate about UX is good business. Can you bridge the gap between old business practices and the protection of Quality?</p><p>Can you find a champion? Can you be a champion?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=201346549ff5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Heroes Turn-Out To Be Heroes]]></title>
            <link>https://medium.com/@AdamtheIA/when-heroes-turn-out-to-be-heroes-399ece768970?source=rss-604d74a30f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/399ece768970</guid>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[adam-polansky]]></category>
            <category><![CDATA[bigd16]]></category>
            <category><![CDATA[heroes]]></category>
            <dc:creator><![CDATA[Adam Polansky]]></dc:creator>
            <pubDate>Tue, 13 Sep 2016 17:40:38 GMT</pubDate>
            <atom:updated>2016-09-14T15:41:03.093Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many kinds of heroes. There are the ones almost everyone can agree upon like first responders to disasters who willingly step into harm’s way for others. There are heroes by example who do thankless work to try and make the world a better place. Sports, entertainment, even business provides us with people we truly admire for many reasons.</p><p>Sometimes we get to meet them. That experience can be cursory; a handshake, a quick word and away they go. Other times we might get to witness them going about their lives when we see them acting like anyone else, riding a subway, ordering coffee or waiting to catch a plane. Sometimes we get to interact with them more directly and we see a glimpse of the person. They could be having a good day and the experience is great and memorable. They could also act like a douchebag leaving you wishing the truth hadn’t revealed itself. Encountering our heroes is an opportunity for awesomness or disappointment.</p><p>Last week I got to meet one of my heroes. Scott is the author of a book I found helpful some years ago and it’s popular enough that many of my peers will agree with me when I say the work is important. While helping coordinate a conference, I invited him to be our closing keynote speaker and he accepted. I thought I was winning at life! I spoke to him a few times before the event mostly to sort-out logistics. He was always very nice — not demanding at all.</p><p>When he arrived at the conference, Scott texted to let me know he was there so I went to greet him. It was early evening and he was about to order dinner and invited me to join him. For the next few minutes he had several questions about the event; its history, its objectives, what he might expect when it was time for him to speak. during the meal a few friends stopped-by and I introduced him to them. Each time he was gracious and spent a little time visiting before they left. We also learned we had some mutual friends and talked about our experiences with them. When the meal was over, we checked our arrangements for the following day and said our goodnights.</p><p>The next day was a track-meet for me, This is a big conference and we had several tracks running simultaneously. The other coordinators were either absent for family reasons or not feeling well and needed me to help cover some additional duties so I was in pretty much in constant response mode. During the day, I ran into Scott a couple of times as he was enjoying the conference like any other attendee but there wasn’t any time to visit. During that time, one of the sponsoring groups asked if he would sit for a 20 minute recorded interview which he did willingly. We also had a book table and the ladies who ran it asked me if he would be signing books at some point. I asked Scott acknowledging that we didn’t arrange for this when he agreed to speak but he was totally amenable and worked-out a time with the book ladies.</p><p>That afternoon we got together to set-up his speaking space. They had to trun three big room into one humongous room and we were testing microphones, laptops and clickers as people were filing in. I had the priveledge of introducing him and I managed to do it without gushing before he gave what turned-out to be one of the best presentations we ever had at a conference that boasts Oscar winners as past keynotes. His talk held something relevant for an audience that included designers of every kind from digital to analog and animators to engineers. Afterward, he went outside the ballroom to sign books which he did for nearly an hour talking to everyone who stepped-up — and not just in that cursory way. He really met them; asking questions and sharing ideas. Near the end of the line was a tall young girl clutching a folio and when Scott was signing her book, she asked “I know you had a long day but would you mind critiquing my comic art?” He said “Sure. Let the line finish and I’ll take a look.” After the last five or six folks got their chance to meet him, Scott cleared the chair next to him and invited the young artist to sit down. I walked away to give them time to visit and I talked to one of the other coordinators who wanted to know if Scott would come to the after-party at a local bar. I turned around to see Scott and the artist really engaged. I took a picture. They spent another 20 minutes or so discussing her work. When they were done, I asked the girl for her e-mail and sent her the picture I took.</p><p>I told Scott about the after-party and asked if he wanted to go. He said “Sure! Can I get a ride?” I typically don’t go the after-party because the rooms are kind of small and crowded and I’m usually exhausted which means as an introvert, I’m not at my best so of course I said “yes” and off we went. When we arrived, the place was crowded. There was free food and drink and I made a point <em>not</em> to hover but I did watch as people invited him to sit-down and he had long conversations with anyone who asked. I went downstairs to visit with some other folks congratulating us for putting-on a great conference when he came up beside me and said. “I’m a little parched.” He caught site of the pool table and said “You know what, you don’t have to talk much to shoot pool. Let’s shoot pool!” So we did. I won a game that showcased both of our sad skills and stayed to play the next-up while Scott went out to the front patio to visit some more.</p><p>After I predictably lost the game, I joined him. The people at that table were closer friends of mine so I pulled-up a chair to talk with a long-time colleague. This went-on for another hour or so with the chair configuration evolving until about five of us including Scott were talking about drawing faces. He was eating dessert after which he got what has to be the most aggressive and vocal case of hiccups I ever heard. That was time to go back to the hotel. The drive was short so we were there quickly and as we walked-in. I thanked him not only for coming to the conference but for the graciousness and ease with which he dealt with everyone he met. He said “Well, I suppose you could call it enlightened self-interest but it’s just easier to be nice. Nice things happen back.” We shook hands and he said “Maybe I’ll see you at breakfast.”</p><p>When I went down for breakfast the next morning, he was there and soon, we were joined by the other coordinators for the conference. We had a great conversation over our coffee, bacon and eggs. He thanked us for creating such a welcoming atmosphere and told us how much fun he had. Finally, he said he had to go so the group broke-up with hugs all around. That’s never happened at this event.</p><p>When the conference ends, I’m usually on my hands and knees exhausted. This time, I was energized not only because the conference went so well but because this week, I got to witness a clinic on how to be a guest and and host at the same time. I’m lucky enough to get to attend events around the world and even speak at some of them. I get introduced to a lot of people who, it turns-out, look up to me. I can only hope I leave the same impression as Scott.</p><p>Sometimes, we get to meet our heroes and they turn out to be every bit as cool as you hope they’ll be. Sometimes, even cooler.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=399ece768970" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>