<?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 Jenna Mortemore on Medium]]></title>
        <description><![CDATA[Stories by Jenna Mortemore on Medium]]></description>
        <link>https://medium.com/@jennamortemore?source=rss-3b5ddd72a315------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9w9skFe9YPEWu1Vvie_baA.jpeg</url>
            <title>Stories by Jenna Mortemore on Medium</title>
            <link>https://medium.com/@jennamortemore?source=rss-3b5ddd72a315------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 17:47:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jennamortemore/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[Improving design to development communication for remote teams]]></title>
            <link>https://uxdesign.cc/improving-design-to-development-communication-for-remote-teams-ac3e2bf9cb1c?source=rss-3b5ddd72a315------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac3e2bf9cb1c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Jenna Mortemore]]></dc:creator>
            <pubDate>Wed, 13 Nov 2019 23:16:08 GMT</pubDate>
            <atom:updated>2019-11-15T00:38:13.996Z</atom:updated>
            <content:encoded><![CDATA[<h4>3 common challenges, with solutions for Product Designers and Product Managers</h4><p>Not getting too suspiciously specific or anything, but speaking as a Product Designer, have you ever gotten an app build back from a remote development team, only to poke around and find margins on each screen ranging from 10 — 20px, and about 9 shades of almost-the-same-but-not-quite-the-same green exist? Nope, me neither (obviously).</p><p>The reality of working with teams that are physically in different spaces, whether that’s in another part of the same building, or in a different time zone in another country is that the lack proximity and face time can lead to a culture of apathy — developers who don’t have the information to get it right and then don’t care, and designers who are frustrated by not seeing pixel perfection giving up on their designs. And don’t get me wrong, this is not a problem specific to remote teams, just that the time and distance can exacerbate things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lkJLYRKW8JJxEmG-CZOWwQ.jpeg" /><figcaption>Graphically represented, there is probably a maximum level of design/implementation parity that exists, as shown on the y-axis. As the number of time zones between teams increase (x-axis), the overlapping hours decrease, and with the disappearance of direct collaboration, implementation quality drops to a point of plateau somewhere along the way. Graphs make articles like this look smarter, even if they’re hand drawn!</figcaption></figure><p>My personal experience with this comes from spending 5 years as a Product Designer, and then a Product Manager working with an awesome development team in Bangladesh. I’ve taken the liberty of speaking to this from the perspective that I know — that of a designer and a manager, not as a developer. I’m conscious that my experience doesn’t qualify me as an expert, or that I’ve even solved these problems. I’m sharing my thoughts here because that’s the liberty that the internet grants us. So without further ado…</p><h3>Problem #1: The only constant is change</h3><p>As a Product Designer, you’re overflowing with ideas. You’re studying your customers, you’re looking at other products, but more than that, you’re constantly thinking of how things can be improved. And there’s never a shortage of options. You’ve got 10 different versions of the same screen and you want to try them all.</p><p>As a Developer, you’ve built out and launched a perfect little filter screen. It’s awesome, slick, sexy. Then lo and behold, next sprint rolls around, and that filter screen is going to get totally reworked. Fine. Then the sprint after that, it’s changed again. When will design just make up their damn minds?</p><p>Agile development practices require teams to adopt an empirical mindset, which means being committed to changing and iterating. However, a piece that can often end up missing from this equation is the <strong><em>“why?”,</em></strong> the critical information that brings everything together.</p><p><strong>Solutions:</strong></p><ul><li>For Product Designers — Look at how you are handing off your designs. Are you throwing them in Invision or some other tool for sending design documents? These communicate visuals extremely well, but even with a user story to back it up, don’t really say a lot about the intention behind the change or your design decisions. Coordinate times to do an in person walk through with development, and really get into the details of why you’re updating elements. Then leave it for a few days before meeting again to get feedback. This is a GREAT opportunity to get new ideas and perspectives, and this will challenge and strengthen your designs.</li><li>For Product Managers — Besides ever evangelizing the need to keep iterating on a product, the most important thing you can do here is provide total transparency on the potential impact, followed up with actual impact once implemented. What metrics is this change impacting? Is there a space (digital or physical) where this information can be shared at all times for everyone, regardless of where they are? <strong>Get the whole team involved in the successes and failures, and make sure everyone can get a direct view of the impact their own work is having. </strong>The ability to see your own personal impact in the chaos of everything going on is a powerful motivator.</li><li>Bonus round:<strong> find a way to share impacts organization wide, and not just in a boring a dashboard that someone walks past</strong>. Things that work in person: obnoxious gong ringing with impromptu announcing, town hall/demo days, potluck lunch and learns, weekly stand-ups. Things that work remotely: video demo walkthroughs (with a coordinated time), a Slack channel #projectXupdates dedicated to sharing cool things. The important thing is showing consistency in a frequency and activity — acknowledgement is not a one time thing, and I don’t care how “busy” you think you are. This IS important. Think of this concept like a product in itself — what are moments that you can delight or surprise your company? Think beyond spreadsheets. Unless you’re a spreadsheet wizard, then you do that, it’s the magic that’s important.</li></ul><h3>Problem #2: Turnovers, and not the fun apple kind</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P6uNzHQENDHCft4w" /><figcaption>Token food photo by <a href="https://unsplash.com/@saracervera?utm_source=medium&amp;utm_medium=referral">Sara Cervera</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>People come and go. Teams change. Turnovers get eaten. Thus is life. However, products often aren’t prepared for this eventuality — iterating on the product and getting out a new feature usually takes precedence in the roadmap to taking time to ensure longevity and consistency in backend design files and systems.</p><p>From a design standpoint, this can mean getting a bunch of files, usually named<em> Productx.sketch, “Productx-final.sketch”, </em>or<em> “Productx-final-finalreallyImeanitthistime.sketch” </em>(yeah, guilty as charged here). And when you open them to see <em>Rectangle685 </em>in the Layers panel you know you’re in for a super fun time (still guilty).</p><p>From a product standpoint, turnover of developers and designers on a team can lead to a lot of legacy elements and inconsistency throughout screens or user flows. When a lot of different people work on one thing without checks and balances in place to ensure consistency, you suddenly have one green that’s multiplied into 9.</p><p>This problem isn’t just an equation of time — a product that has been around for 2 years, or even 10 may or may not have this problem. It’s a direct result of what kind of work you prioritize as a team.</p><p><strong>Solutions:</strong></p><ul><li>First, consider the bus principle. That is, if you were to walk out of the building, and cross the road on your way to grab a coffee and tragically get hit by a bus, could someone easily come in and take over your job? Morbidity of the situation aside, if you just answered no, then it might be time to <strong>think about what things are better out of your head and in the world for other people to use.</strong> You’re awesome! Share that awesome!</li><li>For Product Designers — make sure you make time for organization. I’ve put it off forever, only to come to handoff time and have to try to rope everything together last minute. Goes about as well as you’d expect. That’s why style guides and design systems are your friend from the start. Make one. Use a plugin to export one, or a service to store one. Build up a template or resource file of instances to pull from. There are LOTS of options. The harder part becomes just sticking with it over time, and making sure everyone understand it’s importance. <strong>A design system is a only tool, and it’s only as powerful as you let it be through a commitment to its use. </strong>Use it against people. Fight for it, and fight for the time to make it because if it becomes that central repository for everyone, then regardless of the time zone, there is a place to turn to.</li><li>For Product Managers — any product can take on debt. It’s just how it works. There’s just too many competing priorities for this to never happen. But <strong>don’t ignore the impact of forgetting about design debt</strong>. I think we talk about tech debt a lot, but it’s equally important to know where your design debt stands, if design is being implemented sustainably, and where design needs to fit in the future of the product. Because if you aren’t preparing for it now, there’s gonna come a time when debt collectors come askin’ for their dues.</li></ul><h3>Problem #3: The question of ownership</h3><p>When a designer passes off a design to a developer to implement, whose design is it? Is there a transfer of responsibility? How much control should a designer retain? What happens if development just doesn’t pay attention to those little details designer and polish both crave? What about when you’re remote, and there is even less direct collaboration?</p><p>When I first started out as a UX designer, I was told strictly by my boss that he had no interest in me learning to program. “Design and development are separate skills. I don’t want your designs to be limited by your programming ability,” he declared.</p><p>There is a clarity to that statement that makes it sound easy to just draw a line, and never cross it. But in reality, those lines are blurry. No one can purely sit on one side without <em>some </em>knowledge of the other, nor <em>should </em>they try to be that distinct. It’s the overlap and collaboration between these spaces that really drives innovation, not them being quarantined from each other.</p><ul><li><strong>For Product Managers — this one’s mainly on you.</strong> You want a collaborative team that values input from each side, then you have to work to make that happen. A big part of this is recognizing who has strength in what area. But more importantly, if ownership is ambiguous, then assign it. The RACI framework works well for this, but if you are implementing it, like everything else, you have to make sure that everyone knows what they are signing up for before you just give them a role. Define clearly what the difference between Accountable and Responsible and everything else. And then follow through on ensuring people stick to it.</li><li>For Product Designers — there comes a time when you just need to own it. You can’t sit around and look at executed designs that have passed out of your hands complain they aren’t like you intended. You need to act. Besides ensuring you have a clear understanding of where your role lies, as a design expert, your strength is the ability to see details. Not everyone has that, so don’t be afraid help other people see your perspective. <strong>Don’t take it for granted that everyone understands and interprets all of your design work in the same way you do. </strong>They won’t. And yes, that may mean learning development, but it really comes down to being able</li></ul><h3>TL;DR</h3><ol><li>Yeah, remote teams have challenges when it comes to design/development handoff, but these same challenges can exist in house and are not often unique to remote work. You just don’t have the luxury of face time to fix things.</li><li>Stuff is always changing, so overshare your information. Find a transparent and deliberate way to share and maintain designs that is available to all team members regardless of their location. Use tools, and bring a little delight to be memorable.</li><li>Account for errant buses, rogue waves, acts of god that could wipe out your existence. Use this morbid principle to future proof your designs and your products. Can someone else take it over and understand it easily in your absence?</li><li>Make time for design debt like you would tech debt, or any other kind. Just because you ignore it, doesn’t mean it’s going anywhere either.</li><li>Ownership is important, and critical when it comes to doing the little things right. As long as it is coupled with strong follow through and accountability, it’s a powerful driver of change.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac3e2bf9cb1c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/improving-design-to-development-communication-for-remote-teams-ac3e2bf9cb1c">Improving design to development communication for remote teams</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>