<?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 Melvin Hogan on Medium]]></title>
        <description><![CDATA[Stories by Melvin Hogan on Medium]]></description>
        <link>https://medium.com/@sadisticuserexperience?source=rss-b6df43c7c8da------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Ax1ztB5t7fmArH1P5ggfYQ.png</url>
            <title>Stories by Melvin Hogan on Medium</title>
            <link>https://medium.com/@sadisticuserexperience?source=rss-b6df43c7c8da------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:50:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sadisticuserexperience/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[Handing off designs to developers SUX]]></title>
            <link>https://medium.com/@sadisticuserexperience/handing-off-designs-to-developers-sux-740aa322ee59?source=rss-b6df43c7c8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/740aa322ee59</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[handoff]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Melvin Hogan]]></dc:creator>
            <pubDate>Mon, 26 Feb 2024 02:02:06 GMT</pubDate>
            <atom:updated>2024-02-26T02:02:06.384Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dd26-yE0U83DHZPE.jpeg" /></figure><p>For the uninitiated ( or lucky, depending on your point of view ) handing off designs to development teams has always been a tedious and labor-intensive process. It seems we as designers had to come up with our own methodologies, often each time we worked with a new developer, organization, client, CTO, or development lead. Well, no more. Thanks to the brilliant folks at Figma, this process can be cut to almost nothing. Let me show you how to remove the S.U.X. from design handoffs.</p><p>We’re going to start by assuming you understand Figma basics. If not, head <a href="https://adplist.org/mentors/melvin-hogan">here</a> and sign up for my free ( for now ) six week mentoring session to learn what you need to know.</p><p>The first thing you’re going to want to do is your initial design in Figma. This could be a layout, a form input, a complex component, or a button with many properties. Basically any element where some explanation and documentation will be required when handing to your development team.</p><p>For our purposes, we’re going to create a button that has the following properties.</p><p><strong>States</strong></p><ul><li>Default</li><li>Hover</li><li>Focus</li></ul><p><strong>Size</strong></p><ul><li>Small</li><li>Medium</li><li>Large</li></ul><p>Previously, you’d have to create some type of design specs in Figma to show a developer your intention for the components properties. <a href="https://www.figma.com/community/plugin/1205622541257680763">Eight Shapes Specs</a> plugin came along and made this simpler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YUcS_UDE9Lo4qQtF.png" /></figure><p>But even this wasn’t ideal, and it was still somewhat time consuming if you wanted to edit the specs, or change properties based on developer feedback. Enter Figma’s Dev Mode:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-129NLjLC614Tffw.png" /></figure><p>Now, while you can learn all of the ins and outs of Dev Mode <a href="https://www.youtube.com/watch?v=__ABPkb0aF8">here</a>, the most compelling feature I’ve found for my workflow is this little button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2OJzYLf2qjgiiwUH.png" /></figure><p>Provided you’ve set up your properties correctly, developers can simply click on a given component, and literally play with all of the properties to view the various variations variably ( okay, I got carried away, but you get the point). Check out the gif below to see what I mean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*A7SVPsBB-VX9Fl-ohJWXSg.gif" /></figure><p>That’s it. Developers can test all aspects of your component easily, and you don’t have to create specs for them. There’s a lot more to Dev Mode, but this is the most useful designer tip I’ve stumbled upon thus far.</p><p>Thanks for reading, and let me know in the comments if you have questions!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=740aa322ee59" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is everyone a designer? Maybe.]]></title>
            <link>https://medium.com/nyc-design/is-everyone-a-designer-maybe-4754072faa97?source=rss-b6df43c7c8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/4754072faa97</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[new-york]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Melvin Hogan]]></dc:creator>
            <pubDate>Wed, 14 Feb 2018 20:53:31 GMT</pubDate>
            <atom:updated>2018-02-21T14:34:23.608Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e5flIoQf_jfcYYoSD0MkyA.jpeg" /><figcaption>Photo by freestocks.org from Pexels</figcaption></figure><p>Google defines a designer as “a person who plans the form, look, or workings of something before its being made or built, typically by drawing it in detail.” Seems like an accurate definition.</p><p>In the broad sense, yes, everyone is a designer. Everyone designs what they will wear each day, from a collection of options. Everyone designs meals from time to time, rooms in their home, the elements on their desk, etc. Everyone is a designer in some form, but not everyone is a UX Designer, Industrial Designer, Fashion Designer, etc. These are specific fields requiring years of experience and a honed design sensibility.</p><p>When we apply the EIAD idea to these disciplines, we devalue them. It gives the impression that all points of view hold the same amount of weight when making decisions about design. Design is the only field I’m familiar with where this is the case. We would not state “everyone is an engineer” or, “everyone is a neurosurgeon” because we see these as requiring a specific skill set and knowledge based. I can watch a surgeon perform surgery. This doesn’t make me a surgeon. I can watch Law and Order SVU. Clearly this doesn’t make me a police officer or a lawyer. But, if I can look at a web app, I can design one. At least according to the EIAD idea.</p><p>I challenge the design community to push back whenever this is brought up. Question it. Let others contribute to the design discussion, but don’t acquiesce. Defend your expertise. You’ve earned them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4754072faa97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/is-everyone-a-designer-maybe-4754072faa97">Is everyone a designer? Maybe.</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Write, Right?]]></title>
            <link>https://medium.com/@sadisticuserexperience/write-right-30f6681c5f18?source=rss-b6df43c7c8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/30f6681c5f18</guid>
            <dc:creator><![CDATA[Melvin Hogan]]></dc:creator>
            <pubDate>Wed, 28 Jan 2015 22:43:18 GMT</pubDate>
            <atom:updated>2015-01-28T22:43:18.775Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve spent a good deal of my life benefiting from those brave souls who choose to put their thoughts and ideas out there in the digital space for all to read, criticize, comment on, and read. Due to this, I’ve decided to set a writing goal for myself. Partially as an effort to improve, partially as a weird return on investment for those who have influenced me. I’ll probably provide a list at some point, but, suffice it to say, there are many.</p><p>My goal is relatively simple and straightforward. Write 500 words per day. It’s not an overly ambitious goal, but it something I’ve committed to doing in 2015.</p><p>Originally I was going to do it on my little-known blog resolutionink.com, but I decided instead to put my writings and opinions out here in the big, bad world of Medium.com. It was a scary thought initally, but I think it will pay dividends in the long run. We’ll see.</p><p>The reasons I chose to start my writing practice on Medium are as follows. One, I know they’ll be seen and scrutinized by more people than my blog. Two, I’ll get valuable feedback on what I’m writing in some form. Three, let’s face it, saying my blog is little-known is like saying Lebron James is famous, a bit of an understatement at best.</p><p>So, what do I hope to achieve with these written ramblings? Well, I’m hoping that I’ll get to know myself better as a writer, designer, artist, husband, etc. Basically putting myself out into the world and seeing what reflects back at me. It seems strange to me that I haven’t done this earlier in life ( I’m 45 years young ), but as they say, better late than never.</p><p>What my hopefully growing group of readers can expect is thoughts on UX design, design, art, comics, life, love, etc. Basically human stuff. What I hope to receive is critical feedback on my efforts, pointers, and maybe a bit of learning. Feel free to be unabashedly critical in your commentary. My skin is thick and my head is hard, so you won’t hurt me in any noticeable fashion.</p><p>I’ve read for some time that writing is the way to feed your creativity regardless of your chosen creative endeavor. I know on the occasions I’ve chosen to write in the past, I’ve had breakthrough moments conceptually. I’ve just never adopted a formal practice until now.</p><p>Now, if you’re reading this and you’re saying “wow, this guy is all over the place” I’d respond, YEP. I am, my plan initially isn’t to critically judge every word I write ( that’s where you people come in ). Rather, it’s simply to hit that 500 word goal each and every day.</p><p>With that, here’s hoping some folks join me on this journey of self-discovery and exploration. I think it will be an interesting exercise, and I hope I can make it an interesting exercise for those who choose to read it ( thanks in advance for that ). Until tomorrow, I bid you farewell. Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30f6681c5f18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where low-res prototypes fail]]></title>
            <link>https://medium.com/nyc-design/where-low-res-prototypes-fail-b16b59cfbe81?source=rss-b6df43c7c8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/b16b59cfbe81</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[fail]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[new-york]]></category>
            <dc:creator><![CDATA[Melvin Hogan]]></dc:creator>
            <pubDate>Wed, 28 Jan 2015 22:20:04 GMT</pubDate>
            <atom:updated>2018-02-15T20:50:33.880Z</atom:updated>
            <content:encoded><![CDATA[<p>Prototyping in UX seems to be all the rage these days. The cure for all of our ills. But it’s not with out its flaws. I’ve read many articles touting the benefits of prototyping and iterating and I don’t disagree. That said, one type of prototype that consistently falls down IMO is the low-res prototype.</p><p>Low res prototypes are lauded for their ease of creation and execution. While both of these are true, they tend to ignore the U in UX. Low res prototypes leave can leave numerous user considerations on the table, not the least of which is the user’s emotional response to the interface.</p><p>While I can imagine the arguments against worrying about this in the early stages of prototyping, they all fall flat. If we are designing User Experiences, isn’t the emotion a part of that experience? If so, what type of emotion do we hope to elicit with paper and pencil sketches. I doubt a pencil sketch would have sold the iPhone to millions of users.</p><p>Another core issue with low-res prototypes is they can be hastily and lazily executed, often absent the thought a more refined solution requires. While sketches are nice for communicating a concept internally, my experience with actual users has been the amount of investment involved in explaining a low res prototype is equal to or greater than the amount it take to simply polish the idea more.</p><p>With all of this said, I’m not advocating that every concept be completely refined. To the contrary, I’m simply saying any concept you actually intend on garnering meaningful feedback from real users should have an appropriate level of refinement to test your hypotheses. If you’re able to do that with low-res prototypes, bravo. It’s an experience I have yet to have.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b16b59cfbe81" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/where-low-res-prototypes-fail-b16b59cfbe81">Where low-res prototypes fail</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>