<?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 Rachel Radford on Medium]]></title>
        <description><![CDATA[Stories by Rachel Radford on Medium]]></description>
        <link>https://medium.com/@rachel.radford?source=rss-638a818728fe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UaPHcP7RbFPGjhuGp6ZPqg.jpeg</url>
            <title>Stories by Rachel Radford on Medium</title>
            <link>https://medium.com/@rachel.radford?source=rss-638a818728fe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:14:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rachel.radford/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[Balancing creativity with Design Systems]]></title>
            <link>https://medium.com/trade-me/balancing-creativity-with-design-systems-c31b083258ac?source=rss-638a818728fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/c31b083258ac</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Rachel Radford]]></dc:creator>
            <pubDate>Mon, 25 Jun 2018 04:21:29 GMT</pubDate>
            <atom:updated>2018-06-25T04:21:29.271Z</atom:updated>
            <content:encoded><![CDATA[<p>As Design Systems mature and start to provide tooling such as <a href="https://airbnb.design/sketching-interfaces/">translating sketches directly to code</a>, they are sometimes eliminating the need for designed layouts altogether. While Design Systems make designing interfaces more efficient, they also impact the way designers work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1KSUyZh3wq36o0d1BZWIxQ.png" /><figcaption><em>Airbnb Sketch to Code tool. Image credit: Airbnb</em></figcaption></figure><p>Personally, I get so excited when I think about how Design Systems can allow us to channel our energy into creative problem solving, design thinking, and focussing more on the user. The often repetitive task of layout design is removed, and handover to developers is aided as we pair on building the layout, or have automated tooling to label components.</p><p>But not everyone sees this as a positive move.</p><p>Over the past couple of years I’ve had discussions with a few designers who love the craft of layout. They pore over creating pixel-perfect layouts, and enjoy ensuring it’s <em>just right</em>.</p><p>With a design system, these designers feel like they are losing the ‘creative’ bit of their job.</p><blockquote>Our Design System, as good and efficient as it is, does box the designer in. Especially the more visually creative designers can, to some level, feel restricted, or that there are too many constraints in designing the best possible experience.</blockquote><blockquote>Ant, Design Lead</blockquote><h3>So what can you do to support a designer who feels like the best bit of their job is going away?</h3><p><strong>Ensure your Design System looks beautiful</strong>: so beautiful that designers in your organisation can’t resist it. This will make it fun for them to work with, as they will appreciate the visual craft that’s gone into each component, and how the components work together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kOfqvXIEoTrzlUT-vRBysQ.png" /><figcaption><em>Gorgeous! Who wouldn’t want to shop here?</em></figcaption></figure><p><strong>Involve a variety of designers in the process of creating the Design System</strong>. Here at Trade Me we did this by running sprints where we tested out the Design System in the early stages of a redesign. Designers from all teams were invited to test it out, give feedback and design any missing pieces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kbqQ43nit5QNH9KRC6YXFA.jpeg" /><figcaption>Designers from our Property, Jobs and Central teams testing the Design System together.</figcaption></figure><p><strong>Make kick-ass tooling</strong>. Toolkits should be available for the tools they’re already using. Don’t necessarily just support Sketch — if your designers are using Adobe software then look at leveraging Adobe Libraries. <br>Handovers to developers are often a pain point, so ensure you’re providing or recommending tooling for handovers, alongside the Design System.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XW9ZoWGz8qyKdC39U8j8OQ.png" /><figcaption>A snapshot of our Toolkit for Sketch</figcaption></figure><p><strong>Build space for creative freedom into your system</strong>. There can be opportunities for crafted creative touches, such as illustration, branded sections, image selections and colour combinations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QA2pqG-A9UVE8w42LOSS8g.png" /><figcaption><em>Brand spots are an example of how we intentionally added visual delight amongst user-generated content.</em></figcaption></figure><p><strong>Appreciate a designer’s craft</strong> by recognising them for any contributions to the Design System.</p><blockquote>I feel like I have ownership over part of the Design System because I help to create it. The system is living, and when we find something that needs to be added to it I can get involved even though I’m not part of the Design System squad.</blockquote><blockquote>Dan, Digital Product Designer</blockquote><p>You may encounter a squeaky wheel — the odd person who will complain about moving to working with a Design System, even if it’s a positive change.</p><p>When I discussed this issue with people from other companies, it is clear that your company culture has a huge part to play in how you respond to these people. For some that means a top-down decision applied to teams. At Trade Me, a company with a fairly egalitarian culture, it was important for us to listen to everyone who was having issues with the change, ensure they felt they had been heard, and ‘sell’ the idea to them.</p><p>Regardless of company culture, it’s important for them to <em>start</em> working with the Design System. When we checked in again in a few months time, these people had discovered for themselves the benefits of a Design System and would not go back to their old way of working.</p><p>These are some of the lessons learnt from rolling out our Design System, Tangram, to around 35 designers at Trade Me.</p><p>Today, the designers have extended Tangram to email, visual communications design, and are soon to incorporate it in native mobile design alongside Material and Apple’s Human Interface Guidelines. I’d take this is a good sign that they are excited by the benefits and options for creativity in a Design Systems world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c31b083258ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trade-me/balancing-creativity-with-design-systems-c31b083258ac">Balancing creativity with Design Systems</a> was originally published in <a href="https://medium.com/trade-me">Trade Me Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating collaborative pattern libraries]]></title>
            <link>https://medium.com/trade-me/creating-collaborative-pattern-libraries-8b556ae7efdd?source=rss-638a818728fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b556ae7efdd</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[pattern-library]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Rachel Radford]]></dc:creator>
            <pubDate>Sun, 23 Apr 2017 23:19:03 GMT</pubDate>
            <atom:updated>2017-04-30T22:51:02.847Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our pattern library has a scalable structure and facilitates collaboration across our company of 500 employees, but it hasn’t always been this way.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I2Wmr3su5Wf6qXRC7odHew.jpeg" /></figure><p>One of the most influential podcasts I have ever listened to is the story of <a href="https://www.thisamericanlife.org/radio-archives/episode/403/nummi">General Motors &amp; Toyota’s NUMMI initiative</a>. I have learned a lot from this podcast. It talks about communication, about teams and change management, and it highlights the importance of going on journeys <strong>together</strong>.</p><p>When I first heard that podcast we were chipping away at Tangram, our brand-new pattern library. As part of a centralised team, we were doing the work that we knew should be done to make design and development smarter and more efficient for <a href="http://www.trademe.co.nz/">Trade Me</a>. Just like <a href="http://styleguides.io/">many before us</a>, we had created an <a href="https://www.google.com/url?q=http://bradfrost.com/blog/post/interface-inventory/&amp;sa=D&amp;ust=1492670007038000&amp;usg=AFQjCNGFN8QVoPt5hZGH4a5u1AbWotxDjQ">audit of elements</a> and were working our way through them.</p><p>Then the time came to roll out across the company. Developers would now start working on our new website, using our new pattern library. And despite being fairly comprehensive, the pattern library was — of course — missing lesser-used patterns that were important to some squads.</p><p>We initially carried on with the same <a href="https://www.google.com/url?q=https://medium.com/eightshapes-llc/team-models-for-scaling-a-design-system-2cf9d03be6a0%238b29&amp;sa=D&amp;ust=1492728201317000&amp;usg=AFQjCNH6g3JniVWhehR0k4i7wbffzCkVbA">centralised process model</a> we’d followed to date, taking these new requirements into our central team. The level of quality-control with this process was great, but the team was being dragged down by pressure from external teams. And critically, there were items still outstanding from the initial audit which we weren’t able to get to.</p><p>We weren’t happy. The squads waiting on their elements from the pattern library weren’t happy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TQrZztrbB6L2l8BGjVHK7g.jpeg" /><figcaption>The centralised model was not a fit for us long-term</figcaption></figure><p>The podcast came to mind. General Motors’ story could be very different if the others had been on the NUMMI journey too.</p><p>It was obvious that the centralised model was not a fit for us moving forward. It was also clear that some teams were not entirely on-board with the switch to style guide driven development.</p><p>But most of all I really wanted to answer this question: <strong>How do we bring everyone on the journey?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jz-rzNejQLJsLyNWoBfoGQ.jpeg" /><figcaption>Encourage, celebrate and support involvement</figcaption></figure><h4>1. Encourage involvement</h4><p>We moved away from a centralised locked-down library to an internal-open-source project — with strings.</p><p>Squads are encouraged to design and develop their own pattern library elements, giving autonomy back to the squads. The newly developed element is then submitted to our central team for quality review, and may be revisited until it meets design, accessibility and code-quality requirements. We approach this in a conversational, collaborative way. It is then released to the pattern library.<br>Our model is fairly similar to the <a href="https://www.google.com/url?q=https://medium.com/salesforce-ux/the-salesforce-team-model-for-scaling-a-design-system-d89c2a2d404b&amp;sa=D&amp;ust=1492728201321000&amp;usg=AFQjCNFgJigwyKXIpUvpB8mYgJOH5KEoCg">Cyclical model used by Salesforce</a>.</p><h4>2. Celebrate involvement</h4><p>We celebrate contributions, acknowledging teams in a positive way. When we started to celebrate the behaviour we needed to see, we saw more squads embrace style guide driven development and share the benefits with other team members. They started to see that the benefit of reusing elements from the pattern library outweigh the review process.</p><h4>3. Provide excellent tools and support</h4><p>Our centralised team continues to act as gatekeepers of quality, but that is a small part of what we focus on today.</p><p>With new developments in Sketch we have been able to create a kick-ass design resource (which is a future post of its own!). Our app and code documentation is also heading in the right direction.</p><p>Support via strong collaboration is given to squads requiring more complex elements, or who may be lesser experienced in systematic design and development. Over time this builds stronger relationships and develops people to be skilled advocates around the business.</p><p>There are a lot of models for how pattern libraries can work for companies, and I’m always curious to hear from others how those work in practice. <br>For us at Trade Me, I’m super happy we found a way to go on the journey of style guide driven development <strong>together</strong>. (Awww, warm fuzzies!)</p><p>(By pattern library, I’m referring to a repository of reusable interface elements and code snippets.)</p><p>Thanks to the talented <a href="https://www.instagram.com/mazhermon/">Maz Hermon / The Dude Foundry</a> for the drawings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b556ae7efdd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trade-me/creating-collaborative-pattern-libraries-8b556ae7efdd">Creating collaborative pattern libraries</a> was originally published in <a href="https://medium.com/trade-me">Trade Me Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>