<?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 Greg Podunovich on Medium]]></title>
        <description><![CDATA[Stories by Greg Podunovich on Medium]]></description>
        <link>https://medium.com/@greg.podunovich?source=rss-ef59363408f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*J_rF5KC7Hz9oAcXDG14_zw.png</url>
            <title>Stories by Greg Podunovich on Medium</title>
            <link>https://medium.com/@greg.podunovich?source=rss-ef59363408f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:35:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@greg.podunovich/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[The Eight Principles Of Purpose-Driven Design]]></title>
            <link>https://medium.com/expand-the-room/the-eight-principles-of-purpose-driven-design-e7d05111701b?source=rss-ef59363408f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7d05111701b</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Greg Podunovich]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 15:05:35 GMT</pubDate>
            <atom:updated>2018-03-25T19:42:22.946Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong><em>Why Every Designer Needs a Code</em></strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jOrgwGySWeg7MxSFxEICOA.png" /></figure><p>In many ways, Process is the currency on which designers trade. The ability to tell the story of how you arrived at a particular design solution is every bit as important as any one design deliverable itself. The ability to articulate how we’re going to turn a potential client’s great idea into a functional, valuable product or service is every bit as critical as wowing them with a Keynote deck full of hot-looking designs.</p><p>The helpful thing about the user-centered, iterative design process is that it’s a known quantity. If you look at the <strong>Our Process</strong> section of enough design agency websites what you’ll likely see is some variant of the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*h7ftEiIK82zTA-feMJmwWw.png" /></figure><p><strong>Start by gathering insights about the problem at hand.</strong></p><p><strong>Define the goal and scope of the project.</strong></p><p><strong>Ideate like hell. Prototype the best ideas quickly.</strong></p><p><strong>Test those prototypes.</strong></p><p><strong>Gather learnings from those tests.</strong></p><p><strong>Rinse and repeat.</strong></p><p>That it’s such a known quantity is also what makes the user-centered, iterative design process so tricky. That is, it can be tough to differentiate yourself as a designer through your process, but not for lack of trying. I see design articles all the time with titles like <em>Personas Are Garbage</em> or <em>Don’t Waste Your Time With Empathy Maps</em> or <em>Stakeholder Interviews Are For Suckers</em>. The headlines are provocative to be sure, but, they all point to the same general idea: don’t fixate on design deliverables that might not be right for a given project just because your process mandates it. Instead, focus on the desired outcome of a given design phase and use the best tools in your arsenal to get there.</p><p>I lead an awesome team of UX designers at a small digital design agency in NYC called <a href="https://expandtheroom.com/">ExpandTheRoom</a>. At ETR, we’ve spent a lot of time thinking about how we might add some kind of secret sauce to our own process. We discovered that we could, but it had very little to do with what design deliverables we chose to embrace or throw overboard. At the end of the day, we believe that designers differentiate themselves through their principles more than their process. A process describes <em>how</em> you do something while a set of principles describes <em>why</em> you do something. Our process is rooted in a set of <a href="https://expandtheroom.com/purpose-driven-design/">eight design principles</a>, and the whole thing is rolled up into a framework we call <strong>Purpose Driven Design</strong>.</p><p>We certainly don’t claim these principles as original thought any more than we would claim to have invented <a href="https://en.wikipedia.org/wiki/Card_sorting">card-sorting</a>. Like all designers, we’re influenced and inspired by a lot of great thinkers past and present, across many disciplines. We’ve done our best to attribute their ideas below. Some of our principles are not attributable to any one person. They’re merely part of the design-thinking commons.</p><p>What we do claim is that these principles are 100% authentic to us. They reflect what we collectively hold dear about the work we do at ETR.</p><h3>The Eight Principles</h3><h4>1. Real Value Is Discovered</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/137/1*elUIg7gzJ0wSn14g0SyDJA.png" /></figure><p>Getting beyond what a client has stated as their problem and unearthing a hidden root-cause is one of the high points for any designer. That’s a moment when we can have an unexpectedly valuable impact on their organization.</p><p>That moment only comes after gaining a deep understanding of their business, customers, competitors, goals and aspirations.</p><p>This principle drives our discovery process and serves as the yardstick to let us know when a design problem has been properly framed and contextualized.</p><p>Our friend <a href="http://twitter.com/danielmall">@danielmall</a> introduced us to the idea of creating a <a href="https://aycl.uie.com/virtual_seminars/so_what_do_i_make">Project Manifesto</a>. It’s one or two sentences that articulates who the client is, who they serve, where they’ve been and where they’re going. It’s an incredibly difficult thought exercise. But when you can generate a Project Manifesto that a client agrees accurately captures them and their business, you will surely have what you need to deliver real value to a project.</p><h4>2. Usefulness Depends On Empathy</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/160/1*lusc3RHY6BwvQ5uAax20Lw.png" /></figure><p>People care more about their problems than our solutions. Design decisions must be rooted in solving real problems suffered by actual users, or they’re not useful.</p><p><a href="http://twitter.com/ashmaurya">@ashmaurya</a> from <a href="https://leanstack.com/welcome">LEANSTACK</a> wrote an excellent article on this idea: <a href="https://blog.leanstack.com/love-the-problem-not-your-solution-65cfbfb1916b">Love the Problem, Not Your Solution</a>. While Ash frames this through the lens of entrepreneurship, I think there’s a lot that designers can learn from his main point about the pitfalls of “Innovator’s Bias”, a crippling pre-disposition for some great idea that you just can’t let go.</p><p>It’s easy for designers to get seduced by a fantastic design solution while overlooking the fact that it might be a solution in search of a problem. This principle serves as a gut check and forces us to ask whether or not our design solutions are genuinely in the service of what we know about end users and stakeholders.</p><h4>3. Collaboration Requires Learning</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*jfFq7v13XJ7eVs_vk6QGyA.png" /></figure><p>It’s impossible to collaborate meaningfully without an eagerness to learn from other people. One of the hardest things to do in any professional setting is to acknowledge when you don’t know the answer to something. We permit ourselves to collaborate from the perspective of receiving knowledge and insight from our team in equal measure to the knowledge and insight we give back. This extends beyond our internal team to include our partners from the client side of a project. In this way, we’re able to navigate new and increasingly complex design challenges collectively and honestly.</p><h4>4. The Road To Obvious Is Rigor</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/117/1*-TjZP0sEi47h9GaEtLHrBQ.png" /></figure><p><a href="https://maedastudio.com/">John Maeda</a>, who literally wrote <a href="https://www.amazon.com/gp/product/0262134721?ie=UTF8&amp;camp=1789&amp;creativeASIN=0262134721&amp;linkCode=xm2&amp;tag=redesiglead03-20">the book on simplicity</a>, once asked: How simple can you make it? How complex must it be? We’re continually looking for the place where the answers to these two questions meet.</p><p>This is the principle that we repeat most often at ETR. It usually happens just after that slap-to-the-forehead moment when one of us pulls focus on a laughably simple, elegant design after days of wrestling with a problem. We always wonder aloud, “Wasn’t there an easier way to get here?” Achieving true simplicity is a lot like solving a riddle — the answer is obvious only after you’ve worked it out. This principle reminds us that there’s no shortcut to simplicity in design.</p><h4>5. You Can’t Guess Your Way To Credibility</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/134/1*DR2znuL-KgM6AlOomkVe6w.png" /></figure><p>We believe an unverified fact is just an opinion. Facts, not opinions, are the foundation of credible designs. We strive to leverage data where ever we can in our process to verify or refute our assumptions . This helps ensure that the things we design and build behave precisely how users expect them to.</p><p>Validating our work can come through rigorous user testing, or just by documenting an established best practice. The important thing for us is to eliminate assumptions whenever we can.</p><h4>6. Design For Context, Not Device</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*H2EJl3jXURfi0YpPek86pA.png" /></figure><p>This principle speaks to our position on the evolving topic of mobile design. We believe the physical conditions beyond the edges of a screen have every bit as much to do with how we design as the size and dimensions of that screen. What are users wearing? How’s the light? Are they sitting, standing or running? Maybe their hands are covered in paint or cookie dough.</p><p>By unhitching ourselves to the device du jour, and considering the full context around an experience, we believe we can remain flexible for whatever the future brings.</p><h4>7. Innovation = Aspiration ÷ Feasibility</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/136/1*EqCtZI7hpCFO-aieIZvArA.png" /></figure><p>This principle reminds us that you can’t innovate on what you can’t realistically build. Good designers are always searching for creative ways to break new ground. Looking to the blue sky is a big part of why many of us chose this profession. However, we have to temper our aspirations with reality. That might be budget or time constraints, a client’s resistance to change, or technological limitations.</p><p>For us, feasibility has to do with collaborating early with developers to gain alignment and find efficiencies, allowing us to focus on the most potent opportunities for innovation.</p><h4>8. Keep It Human, Stupid</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/124/1*PLlNLxp-aX23xHtGrOkOqQ.png" /></figure><p><a href="https://uxmag.com/contributors/amanda-o-grady">Amanda O’Grady’s</a> brilliant article, <a href="http://uxmag.com/articles/stop-sprinkling-emotion-start-creating-magic-and-meaning">Stop Sprinkling Emotion, Start Creating Magic and Meaning</a> was a big source of inspiration when we wrote this principle.</p><p>We’ve all likely seen some version of the <strong>UX Pyramid of Needs</strong> which describes an evolving hierarchy of design attributes. At the base there is <strong>functional</strong>. Next, is <strong>reliable</strong>. Then it’s <strong>useful</strong>, followed by <strong>convenient</strong>. From there it elevates to <strong>pleasurable</strong>. Finally, at the top where we all strive to be, is <strong>meaningful</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*7xpF2mdQC8005jYF2WQ-5A.png" /></figure><p>It’s a handy visual aid, but there’s something quite misleading about that pyramid metaphor. It implies that each attribute is somehow layered onto the preceding to create an instance of human delight — like when Bob Ross dabs on those final highlights, and you’re suddenly looking at a photo-realistic painting of trees.</p><p>We believe that if we want to have a chance at creating a meaningful connection with users, human emotion must be woven into what we design from the very start. For us, this means making users feel known and understood at every touchpoint along an interaction that matters to them.</p><h3><strong>There’s So Much More To Say…</strong></h3><p>Defining your own set of guiding design principles is an arduous task. It’s difficulty is amplified ten-fold for an organization. The most important thing we learned while creating ours is that it absolutely has to be true to who you are, or it won’t work.</p><p>We love to talk about process and principles, and we have a lot to say about it. We’ll be following up with more about how these principles guide our work through all phases of our design process and how we came up with them in the first place. In the meantime, we’d love to hear from you: what does your process look like, and what are the principles that guide it?</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7d05111701b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expand-the-room/the-eight-principles-of-purpose-driven-design-e7d05111701b">The Eight Principles Of Purpose-Driven Design</a> was originally published in <a href="https://medium.com/expand-the-room">ExpandTheRoom</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Tool To Rule Them All]]></title>
            <link>https://medium.com/expand-the-room/one-tool-to-rule-them-all-11e45696b647?source=rss-ef59363408f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/11e45696b647</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Greg Podunovich]]></dc:creator>
            <pubDate>Tue, 21 Jun 2016 14:30:23 GMT</pubDate>
            <atom:updated>2016-06-21T14:30:23.508Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Look Back On Our Year-Long Quest To Deliver A Massive Design Project Solely On UXPin</h4><p>In July of last year, ExpandTheRoom kicked off a massive design project for a large, multinational travel IT company which provides a variety of products and services to airlines around the world. We collaborated with them to redesign their consumer-facing flight reservation system (what you would find at an airline’s homepage) and a similar booking system used by reservation agents working at an airline call center.</p><p>As a team, we made the decision early on to experiment with using a web-based design platform as the primary pipeline through which we would deliver design assets to the various project stakeholders. One of the main drivers for this decision was the fact that this project had many stakeholders across so many internal silos. Adding complexity was the fact that they’re also spread out geographically from across North America, the UK and India. To us, it seemed like the only way to keep so many people in so many locations in sync was to have one central location where everyone could find the most current work. Basically, we wanted to see how easy we could make it for our client partners to access the most up to date versions of everything — one url that anyone could follow and find exactly what they needed…</p><p>There are so many web based wireframe/mockup/prototyping tools that to list them all would take the remainder of this article. Plus, that list would literally be out of date the second I hit the publish button. Essentially, we’re talking about things like <a href="https://balsamiq.com/">Balsamiq</a>, <a href="https://atomic.io/">Atomic</a>, <a href="http://uxpin.com/">UXPin</a>, <a href="https://www.invisionapp.com/">InVision</a> &amp; <a href="https://marvelapp.com/">Marvel</a>.</p><p>We had previously used UXPin internally for wireframing, as well as some basic prototyping with fairly good results. As we looked closer at UXPin, we saw a number of features that we thought we could leverage throughout the life of this project to make it a really effective central hub for all of our design work. This is not to say that we ever thought UXPin would be the only tool we would use to create our design assets. <a href="https://medium.com/u/e46a1bba73bb">Keaton Herzer</a>, so hilariously addressed in his recent send-up article <a href="https://blog.prototypr.io/the-ideal-design-workflow-2c200b8e337d#.gl5i6bl0x">The Ideal Design Workflow</a>, there is no one tool that can meet all of our design needs. There likely never will be. However, we recognized in UXPin not just the ability to get a lot of our design work done, but also the ability to play nicely with some of the other tools we’d be using.</p><h4>QUICK IDEATION, SHARING &amp; ITERATION</h4><p>On the creating front, the layer-based drawing and text editing tools in the UXPin editor made pretty quick work of rapid ideation. We were able to try out and build upon all sorts of ideas without having to invest a lot of time. I could send a link to my team members in the office. They could give me live feedback. Updates that I made at my desk showed up almost instantly at theirs. We covered a lot of ground in a relatively short amount of time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*s_BXwB_alMqtv5gqRZiwXA.png" /><figcaption>Basic drawing tools in UXPin make it very easy to quickly wireframe ideas.</figcaption></figure><h4>CLICK-THROUGH PROTOTYPING IN NO TIME</h4><p>UXPin also made it really easy to connect a series of screens for click-through prototypes that we could use to test interactive flows and overall architecture. Additionally, beyond just linking pages, UXPin allows for more advanced animations so we were also able to start looking at more complex interactions and micro animations, again with relative ease.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*ZH3foNPj6eAPDSiAOSOTwA.gif" /><figcaption>It was nice not to have to export pngs of these wireframes to InVision to mock up this little animation.</figcaption></figure><h4>BRINGING IN VISUAL DESIGN COMPS FROM SKETCH</h4><p>The tool of choice for our visual designers at ETR is (currently) Sketch. UXPin has a really nice Sketch plugin that allowed us to export from Sketch and import into UXPin while maintaining (for the most part) our Sketch layers. That was pretty nice and allowed the team to continue playing with animations and transitions at a higher level of fidelity and polish inside UXPin.</p><h4>BRINGING IT ALL TOGETHER</h4><p>For us, the big challenge of using UXPin was packaging it all up in a cohesive deliverable that was useful for a broad range of stakeholders including people in all levels of front and back end development, product definition, product QA and testing, business architects, systems architects, project managers and much of the corporate leadership of our client. We found a few features inside UXPin that helped us address this.</p><h4>A BIT OF TAB HACKERY</h4><p>For one, we used the UXPin’s Adaptive Version feature, which essentially allows you to have multiple work canvases inside a tabbed navigation on any given page view. The most obvious use for this feature is if you want to show a desktop and mobile version of the same design without having to send a users to two separate pages to see them. We leveraged the Adaptive Version tabs to bundle all of the different assets for a given screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4wCf2eUYAud3Y9DDesGDnQ.png" /><figcaption>Above you can see that for any given screen view we have the desktop wireframe, tablet wireframe, mobile wireframe, design comps and prototypes all in different tabs on the same page. This way, whichever asset is the most useful for a particular stakeholder is within immediate reach. Plus, the other assets are readily available for cross reference.</figcaption></figure><h4>STUFF WE COULDN’T PROTOTYPE IN UXPIN</h4><p>In some cases we needed to demonstrate animated interactions or transitions that were either outside the limitations of UXPin or were just easier for us to mock up in Framer.js. No problem. UXPin makes it really easy to embed a video player linked to a video hosted on YouTube or Vimeo. We simply screen captured those animations and embedded the video in the Prototype tab in UXPin. This created an extra step, but it was nice to have the video of the animation there with the rest of the work.</p><h4>CREATING A META NAVIGATION</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*45gpOhvDQrm2Qm0rvlouuw.png" /></figure><p>One nice thing we discovered was the ability to add a little interactivity and navigation into our deliverable structure. By adding Forward, Back and Home buttons we gave our client users a way to navigate what was often a pretty large set of screens. UXPin does provide a navigable Site Map in the presentation view, but it lives in a left-hand collapsible drawer that many of our users found hard to use. We wanted to provide a more surfaced and obvious way for people to quickly move around. We also reserved the Homepage of our projects for a linked table of contents. We found that our clients much preferred this to the UXPin navigation.</p><h4>LAYERING ON INFORMATION</h4><p>Another nice touch we added was the ability to show and hide annotations and the corresponding markers which tend to litter up a screen comp. Sometimes, it’s nice to just get a clean view of the screen and not have to look at dozens of little numbered markers calling out annotations. In the past, this often meant including several versions of the same work — one clean, one with anatomical annotations, another with state and interaction annotations, another with specs and so on. However, in UXPin we could have one comp with several showable/hide-able annotation layers. Users could toggle on or off any of the annotations they wanted to see, or just see the work clean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SfgijUS2h_xMAHMuNLicsw.gif" /></figure><h4>CAPTURING AND TRACKING FEEDBACK</h4><p>UXPin comes with a decent commenting system for people who are looking at work in the presentation view. Much like InVision, users can toggle into a “commenting” mode and drop comment markers on the page. This is nice, of course because people can put a marker right on the thing they’re referring to. It removes a lot of ambiguity. Comments can easily become discussion threads as other people respond to an initial comment. Comments can be marked as resolved, and UXPin makes it easy to sift our resolved comments so that you can easily see what the open issues are. These features all worked really well for us. There were limitations to be sure. For one, you can’t export comments. Exporting would have been nice as we could have translated comments into tickets in something like <a href="https://www.codebasehq.com/">Codebase</a> or <a href="https://basecamp.com/">Basecamp</a>. Then we could have more easily tracked open issues. As it was, we had to do a good bit of legwork to keep on top of who on our team was addressing which comments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*raz2lc8NkvnIJpzv4LOZFA.jpeg" /><figcaption>As you can see, we leveraged UXPin’s commenting system quite heavily. We had to do a little leg work to make sure we were properly tracking comments.</figcaption></figure><h4>FINAL THOUGHTS</h4><p>The short and sweet answer is that this worked out pretty well for us. There were some bumps along the way, but we got them solved, often with the help of the great support staff at UXPin. They are very responsive to support questions and quite receptive to feature and enhancement ideas.</p><p>As an organization, working this way made us think differently about our own workflow and, I think, has changed how we think about the role of wireframes, design comps and prototypes to communicate the intent behind our designs… But that is for another story.</p><p>Thanks for reading. I hope this was helpful to anyone thinking about how a web-based design platform might figure int your own workflow. If it is, please hit the recommend button. Also, if you have any questions about how we used UXPin (or any of our other go-to tools) please hit us up in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11e45696b647" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expand-the-room/one-tool-to-rule-them-all-11e45696b647">One Tool To Rule Them All</a> was originally published in <a href="https://medium.com/expand-the-room">ExpandTheRoom</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>