<?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 Robbin Cenijn on Medium]]></title>
        <description><![CDATA[Stories by Robbin Cenijn on Medium]]></description>
        <link>https://medium.com/@robbin_70405?source=rss-a3fd1445f485------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mClNaDFJjud6ENE-</url>
            <title>Stories by Robbin Cenijn on Medium</title>
            <link>https://medium.com/@robbin_70405?source=rss-a3fd1445f485------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:59:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@robbin_70405/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[Dear Ueno: How should designers deliver projects to developers?]]></title>
            <link>https://medium.com/ueno/dear-ueno-how-should-designers-deliver-projects-to-developers-31ae471a5c99?source=rss-a3fd1445f485------2</link>
            <guid isPermaLink="false">https://medium.com/p/31ae471a5c99</guid>
            <category><![CDATA[keynote]]></category>
            <category><![CDATA[designers-and-developers]]></category>
            <category><![CDATA[dearueno]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Robbin Cenijn]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 11:58:16 GMT</pubDate>
            <atom:updated>2018-11-27T11:59:25.403Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Dear Ueno is an advice column for people who for some weird reason think we know what we’re doing. Read </em><a href="https://medium.com/ueno/dear-ueno-b6946471b26a"><em>more about all this</em></a><em>, or check out our </em><a href="https://loremipsum.ueno.co/dear-ueno/"><em>old advice</em></a><em>.</em></p><p><a href="https://medium.com/@ortimd"><strong>Dmitro Petrenko</strong></a><strong>, a product designer based in Warsaw, sent us an email:</strong></p><blockquote>“Hi, guys. I want to ask you about a problem I usually have when design is finished and ready for the development stage. My question is: How do you prepare design specifications for developers, like animations, transitions, hover effects? Do you provide examples with prepared animation like After Effects, or you describe it in text? If you have an example of a design document or guideline for this, I’ll be very grateful.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V2pFg-M4LkZgc__5o0v4oA.gif" /></figure><p><strong><em>Robbin Cenijn, Executive Creative Director at Ueno SF, replies with a big smile on his face:</em></strong></p><p>Hey Dmitro, it’s a great question. I don’t have the perfect answer, but I’ll give you my two cents. Since you refer to hover effects my guess is you are talking about websites, so I’ll focus on that.</p><h3>Back in the days</h3><p>I used to work at an advertising agency and like most traditional ad agencies we didn’t have development in-house, but instead hired production companies. To give them a good idea of the scale and scope of a project, we created a brief — the more detailed, the better. So once design was in a good spot I either animated pieces or recreated the whole flow of the site in After Effects. Then I would make a deck with references, questions and ideas to share. If you can involve your developers from the very beginning of the process is obviously better. But everyone knows that for various reasons this is not always the case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dRxHkHLSg8XQcha6.png" /><figcaption>Example slide from <a href="https://ueno.co/work/clearmotion">ClearMotion</a> project</figcaption></figure><h3>Fast-forward to the present</h3><p>With or without in-house development, it is still helpful to document or get your thoughts together for the team, client or others you collaborate with. Not everyone is always available and it helps to visualize your ideas to get a better starting point to discuss ideas.</p><p>As for tools: After Effects is still my go-to for making animation references for websites, but I know some people here use Framer or other prototyping apps. It doesn’t matter what you use, what matters is that you quickly make something that will get the point across.</p><p>A lot of different stuff goes into a document like this. To put it all in one place what works best for me is Keynote. Keynote accepts everything! Gifs, links, images, pretty much any video format and you can slap it together with text anywhere! It’s also slide-based so you can take some slides out of the deck to send over to others. It saves a lot of time and it’s great.</p><h3>It’s not a hand-off</h3><p>Remember, it’s not a <em>developer hand-off. </em>I’m not handing anything off and the document is not only for the developers. And it’s is never really completed — the document changes constantly during the whole process. This is not about the designer telling the developers or anybody else, “this is how things should be.” Rather, it’s open-ended and collaborative.</p><p><em>Example: How many frames of an animation sequence should be rendered to make it look great? This isn’t something a designer just decides. I need input from the developer and animator for this.</em></p><p>I should mention is that I usually abandon the document at some point. It’s not something that I finish or perfect. At the end of the project when the project has launched, there are decisions made with the team during the process that might deviate from the document. Things change over the time of a project and many ideas will evolve. That’s part of the collaboration.</p><h3>Some tips</h3><p><strong>1. It’s not supposed to be pretty.<br></strong>Your document should feel dirty, not pretty. It’s more of a digital sketchbook. Don’t waste more time on it than needed.</p><p><em>Example: That little voice in your mind tells you it has to be pretty. You start using the project fonts and so on. Some people might not be fully on to the project (but are in the loop) so they probably don’t have the right fonts installed. When they open the deck your fancy text reverts to the default typeface and now your whole deck is unreadable. Nice.</em></p><p><strong>2. It should be self explanatory.<br></strong>The document should make sense to anyone reading it. At Ueno we work with teams across time-zones. Which means I might be sleeping while someone else is going over it. I always try to focus on one or two things per slide, which helps to keep focus on what you are trying to get across.</p><p><strong>3. Write like a normal person.<br></strong>Say what you are thinking. Don’t beat around the bush. Don’t write cool sentences like: “<em>Conceptually it made sense to visualize the functionality of the component by …” </em>Just say: “<em>Here we will have two videos that you can control by doing …”</em></p><p><strong>4. When something is not final: Say so.<br></strong>Sometimes things are not final, but in order to give a complete picture I add WIP designs or animations in the doc. I clearly state it’s not final, so people don’t freak out over inconsistencies or comment on things that are “not pretty.”</p><p><strong>5. If you don’t know something: Say so.<br></strong>Everyone needs help. No one knows everything. I don’t know everything. So sometimes I make suggestions about how I think we can solve certain things, but I always clearly state that I may not have any idea what I’m talking about. The right person will spot this and it always leads to a conversation. It’s also useful for me, because it keeps it on my radar.</p><p><strong>6. If you want specific input: Say so.<br></strong>I work on projects holistically. Sometimes I need input or recommendations on development solutions in order to create the right visual solution. Then I put notes in the doc stating that I need input and what, why and the consequences of the decision.</p><p><em>Example: Let’s say there is a commerce part of the project. Then the question becomes; What are we using? Is it Shopify? How much can we customize, how much can we integrate the functionality within the page, do we need to integrate code in other pages in order to make the experience better?</em></p><p><strong>7. Sometimes more is better<br></strong>Add as many references, links, and examples as you can to explain what you want to say. But always clearly state what and why the reference is in there. If it’s too much and too varied it could lead to confusion.</p><p><strong>8. Add links to the source files<br></strong>It’s very convenient to be able to jump to files straight from the slide. Just add a link to Dropbox or your server, and voilà. Easy for everyone.</p><h3>Why would you create a document like this?</h3><ul><li>When people jump on the project later on it’s easy for them to find everything.</li><li>It’s a go-to file for references, documentation, Dropbox locations and so on.</li><li>This can grow over time and it doesn’t take a lot of time to add or change stuff.</li><li>It could also be used to explain things to clients.</li><li>Small things don’t fall through the cracks.</li><li>It helps to go through each piece of the design puzzle and knowing you pushed it as far as you could. (It doesn’t mean it is going to happen, but an ambitious starting point never killed anyone.)</li><li>The team can prioritize based on understanding the entire scope.</li><li>Documentation like this can be shared, read and explored independent of timezone.</li></ul><h3>Some examples</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Po2LDcRz6ew1hrfBSr9sg.gif" /><figcaption>The PrescribeWellness site flow with WIP assets</figcaption></figure><p><strong><em>How it turned out:</em></strong></p><ul><li><a href="https://dribbble.com/shots/3052658-PrescribeWellness-Homepage-Animation-02">PrescribeWellness Homepage Transition</a></li><li><a href="https://dribbble.com/shots/3043251-PrescribeWellness">PrescribeWellness Homepage Sequence</a></li><li><a href="https://ueno.co/work/prescribewellness">Case study</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CdRs0yVQKu0QJvdoPy8O9w.gif" /><figcaption>Interaction mockups for ClearMotion</figcaption></figure><p><strong><em>How it turned out:</em></strong></p><ul><li><a href="https://dribbble.com/shots/4139404-Launch-ClearMotion-com">Homepage ClearMotion Dragger</a></li><li><a href="https://dribbble.com/shots/4294426-Adapting-to-mobile-ClearMotion">Homepage ClearMotion Mobile adaptation</a></li><li><a href="https://ueno.co/work/clearmotion">Case study</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zccDfzyQFb7N812hYCjKsg.gif" /><figcaption>ClearMotion transition references</figcaption></figure><p><strong><em>How it turned out:</em></strong></p><ul><li><a href="https://dribbble.com/shots/4183684-Stripping-the-layers">Stripping the layers</a></li><li><a href="https://dribbble.com/shots/4139414-ClearMotion-An-inside-job">Technology page</a></li></ul><h3>Famous last words</h3><p>This is my way — it has worked for me the past 12 years or so, but everyone does it differently and every project is different.</p><p>The most important thing is to involve your team as soon as possible. Collaborate, jam, and inspire each other. That’s where the magic happens.</p><p>And when development is ongoing, your job isn’t done. You need to be there to make decisions, push, collaborate, test and see it through together with the team that’s working on the project.</p><p>Hope this answers some of your questions, Dmitro.<br> — Robbin</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h4FcWt3XyYR1bNkg_WofSg.jpeg" /></figure><p><em>Robbin Cenijn is Executive Creative Director at Ueno in San Francisco, even if he does say so himself. Originally from the Netherlands, he’s still from the Netherlands. Some things never change. Want to work with Robbin? Because </em><a href="https://www.ueno.co/careers"><em>Ueno is hiring</em></a><em>.</em></p><p><strong><em>Need more answers? </em></strong><em>Yes, you do.</em><strong><em> </em></strong><em>Just email </em><a href="/service/mailto:hi@ueno.co"><em>hi@ueno.co</em></a><em> with the subject line “Dear Ueno,” or </em><a href="https://twitter.com/uenodotco"><em>tweet at us</em></a><em> with the hashtag #DearUeno. Include your name, location, and profession, and let us know if you want to remain anonymous.</em></p><p><strong><em>Need more email? </em></strong><em>Yes, you do. </em><a href="https://ueno.co/newsletter"><em>Sign up for the Ueno newsletter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31ae471a5c99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ueno/dear-ueno-how-should-designers-deliver-projects-to-developers-31ae471a5c99">Dear Ueno: How should designers deliver projects to developers?</a> was originally published in <a href="https://medium.com/ueno">Ueno.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>