<?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 Rebekah Cheng on Medium]]></title>
        <description><![CDATA[Stories by Rebekah Cheng on Medium]]></description>
        <link>https://medium.com/@rebekah.cheng?source=rss-d1f50556eb8a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*7kJLnEQMJQ1vzoxuzJzACQ.png</url>
            <title>Stories by Rebekah Cheng on Medium</title>
            <link>https://medium.com/@rebekah.cheng?source=rss-d1f50556eb8a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:09:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rebekah.cheng/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[Being a designer in a sea of engineers (& other stories).]]></title>
            <link>https://medium.com/supahands-techblog/being-a-designer-in-a-sea-of-engineers-other-stories-505960fb4da0?source=rss-d1f50556eb8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/505960fb4da0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Rebekah Cheng]]></dc:creator>
            <pubDate>Tue, 18 Jun 2019 04:37:32 GMT</pubDate>
            <atom:updated>2019-09-24T09:22:26.626Z</atom:updated>
            <content:encoded><![CDATA[<p>__</p><p><strong><em>Part 1: Why frank feedback is fortuitous.</em></strong></p><p>A few weeks into my role as Product Designer at <a href="https://www.supahands.com/">Supahands</a>, someone in Tech¹ boldly declared to me:</p><h3>“I used to think that a designer’s main job was to annoy and make life difficult for engineers.”</h3><p>Marvellous.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-LyUzsqte7t_WGtNXUT8pA.png" /></figure><p>But there’s always a golden nugget to be found when one receives feedback as forthright as this. By “golden nugget”, I do mean <strong>actionable user insights</strong>.</p><p>My initial thoughts went a little like:</p><blockquote>If someone within my own team doesn’t quite get what I do, how much more the rest of the company?</blockquote><p>Nevertheless, as a new hire finding her place in a thriving tech startup, I wasn’t about to launch a full-on design research project (or should I say <em>intervention</em>!?) on <strong>why design matters</strong> (can I get an Amen).</p><p>Fast forward a few weeks and somebody from BizDev² marches up to my desk (in delightful candour …and a lot of muscle) with this declaration:</p><h3>“So, WTF do you do around here?”</h3><p>Time for that intervention.</p><p>Putting the latter into play started with this question:</p><h4>How might we (the Design team) shape the Design DNA and culture at Supahands?</h4><p>While Baim³ and I had discussed design principles, protocols and people (I do really love alliteration), we wanted to make sure our team’s vision aligned with that of our <a href="https://www.supahands.com/">Mothership</a>.</p><p>But, why does this matter? Who cares about what other people in the company think of designers? Let alone what <em>type</em> of designers we bring in?</p><p>Well.</p><h4>If we nail our Supahands Design DNA, we’re not just bringing in designers that will fit our team. We’ll be hiring champions of our culture too.</h4><p>And <a href="https://blog.prototypr.io/design-begins-with-culture-not-process-c2148b863da4">design begins with culture, not process</a>.</p><p>So how did we do this?</p><p>We spent a few weeks speaking to people from each department to get a flavour of what design means to them, what they love (and hate) about design(ers), you get the drift.</p><p>Sample question? “Tell us about a time when you had a bad experience working with a designer.”</p><p>I know, rather delicious.</p><p>I’ll save the details of our Design DNA report for another post⁴.</p><h4>But for now, Baim and I have a solid foundation. We’ve got good bones for growing our design team of two⁵. This includes a checklist for hiring, a values system and a streamlined design process.</h4><p><strong>Key takeaway/TLDR</strong>: There’s no such thing as bad feedback. We wouldn’t have our Design DNA without frank, honest feedback (from an engineer, no less).</p><p>So, designers, the next time you hear something you don’t want to hear, make the most of it. Ask yourself (as I always do): how might I use this ?!@&amp;%$ feedback for the public good?</p><p>Because at the end of the day, we design for people — not for ourselves and certainly not for our egos.</p><p><strong>Footnotes i.e. the juicy bits.</strong></p><p><em>¹ This Front-End Dev shall remain anonymous as he named a button (in CSS) after me. I may or may not have bribed (he might say threatened) him with raw vegetables.</em></p><p><em>² Greetings Greg. Find him on LinkedIn for all things Sales/BizDev </em><a href="https://www.linkedin.com/in/greg-meehan-01257110/"><em>here</em></a><em> but if that’s too much effort, he’s also on </em><a href="https://www.instagram.com/thegregmeehan/"><em>Instagram</em></a><em>.</em></p><p>³ <a href="https://www.linkedin.com/in/baimhanifkamil/"><em>Senior Product Designer</em></a><em> at Supahands and alarmingly single. Ladies, he rides a pretty sweet motorbike. I’ll make sure he picks you up with a spare helmet — safety first, kids.</em></p><p>⁴ <em>Because I promised </em><a href="https://www.linkedin.com/in/juinn/"><em>Marketing</em></a><em> I’d start writing on “Design”. And I am also a (content) tease.</em></p><p>⁵ <em>Never despise the day of small beginnings my friends!</em></p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYxBP_WV7LI6zc-zdUkNqQ.png" /></a></figure><p>📝 Read this story later in <a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_read_later_text">Journal</a>.</p><p>👩‍💻 Wake up every Sunday morning to the week’s most noteworthy stories in Tech waiting in your inbox. <a href="https://usejournal.com/newsletter/noteworthy-in-tech/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_text">Read the Noteworthy in Tech newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=505960fb4da0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/supahands-techblog/being-a-designer-in-a-sea-of-engineers-other-stories-505960fb4da0">Being a designer in a sea of engineers (&amp; other stories).</a> was originally published in <a href="https://medium.com/supahands-techblog">Supa Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>