<?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 Roland Lösslein on Medium]]></title>
        <description><![CDATA[Stories by Roland Lösslein on Medium]]></description>
        <link>https://medium.com/@weaintplastic?source=rss-c0ca7c85c9ff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*BFCBWbNFuOEvwq-kahUokQ.jpeg</url>
            <title>Stories by Roland Lösslein on Medium</title>
            <link>https://medium.com/@weaintplastic?source=rss-c0ca7c85c9ff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:47:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@weaintplastic/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[Diamonds and Rice — A framework for Product Managers to build a successful product.]]></title>
            <link>https://medium.com/@weaintplastic/diamonds-and-rice-a-framework-for-product-managers-to-build-a-successful-product-52063ac257bb?source=rss-c0ca7c85c9ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/52063ac257bb</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Roland Lösslein]]></dc:creator>
            <pubDate>Mon, 18 Nov 2019 08:53:55 GMT</pubDate>
            <atom:updated>2019-11-18T08:53:55.846Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>Diamonds and Rice — A framework for Product Managers to build a successful product.</em></h3><p>Managing a successful product is hard. We are constantly challenged to make the right decisions on what to work on next. More often than not, there are more options than choices. It’s then our job to identify which ones maximize the added value to cost ratio.</p><p>My team and I are working on design systems and design tooling at ResearchGate and are regularly swamped by exciting new opportunities. As a consequence of serving a broad variety of people working in different disciplines with individual needs, we receive more feedback, requests, and proposals than we can possibly handle. And on top, we have tons of ideas ourselves. For a long time, we have been desperately looking for a way to organize, manage and filter that input to be able to distill the most impactful work and intentionally forget about the rest.</p><p>Being able to make the right call requires more than just intuition or gut feeling. Over the past nine months, we’ve been experimenting with different approaches that enable us to make conscious and informed decisions and allow us to move on with clarity and focus. The result of this journey is a combination of different frameworks and mental models that can be applied to any situation where tough prioritization is required, even outside the scope of our team. We are merging the fairly popular <em>Double Diamond</em> process invented <a href="https://www.designcouncil.org.uk/news-opinion/what-framework-innovation-design-councils-evolved-double-diamond">by the British Design Council</a>, the mental model of <em>Opportunities &amp; Solutions</em><a href="https://www.producttalk.org/2016/08/opportunity-solution-tree/"><em> </em>pioneered by Teressa Torres</a> and RICE,<a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/"> an extension of the ICE score by<em> Intercom</em></a><em>.</em></p><p><em>Double Diamond</em> separates the process into four phases: Discover, Define, Develop and Deliver. In the first half of the process, we focus on the exploration, analysis, understanding, and prioritization of problems to ultimately help us to identify <em>the right things to do</em>. In order <em>to do things right</em>, we iteratively develop and ship solutions while keeping track of their success as part of the last two phases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VCl38I3uVUZa2zJ-" /><figcaption>Our interpretation of Double Diamond clearly separates the concerns of Opportunities and Solutions.</figcaption></figure><h3>Do the right things</h3><h4>Discover Opportunities</h4><p>In the first phase of <em>Double Diamond</em>, we build up a catalog of potential opportunities for us to work on. An <em>Opportunity</em> is defined by the specific problem it will solve and for whom. We document possible success metrics along with the insights that led to the creation of the <em>Opportunity</em>. New <em>Opportunities</em> can be discovered by observing users, running surveys, analyzing metrics, doing research or conducting ideation sessions. Interestingly, we’ve found that many times our discovery starts with the idea about a specific solution. However, when that happens, we strive to understand and identify the underlying problem in order to keep our mind open to alternative solutions later.</p><h4>Define Opportunities</h4><p>Throughout the <em>Define</em> phase, we aim to separate the most promising Opportunities from those that don’t provide enough value for their costs. A common practice is to use an accumulated score that factors in different aspects that define the value and costs of an <em>Opportunity</em>.</p><p>A scoring model that works well for us is<a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/"> RICE by Intercom</a>. The first three aspects <em>Reach</em>, <em>Impact</em> and <em>Confidence</em> are projections of the value an <em>Opportunity</em> provides, whereas <em>Effort </em>(or <em>Ease of implementation</em>) describes the costs of it.</p><blockquote><em>Reach</em> * <em>Impact</em> * <em>Confidence</em> = <em>Value</em></blockquote><blockquote><em>Effort = Costs</em></blockquote><p>The <strong><em>Reach</em></strong> forecasts the absolute number of people that may benefit from a solution within a specific timeframe (e.g. three months). Considering the <em>Reach</em> in order to prioritize Opportunities avoids that we are working on a feature we’d only use ourselves or that are just adopted by a few.</p><p>The <strong><em>Impact</em></strong> describes the relevancy of a problem for our customers. If no data-driven insights on the impact are available, we fall back to doing simple customer surveys to determine the relevancy of a problem. Customers can choose between a low (0), medium (0.5) or high (1) relevancy of a problem. The final Impact is derived by averaging all data points, resulting in a value between 0 and 1.</p><p><strong><em>Confidence</em></strong> is a factor that represents the level of evidence supporting our hypothesis. Again we are using a simple scale ranging from low (0), medium (0.5) to high confidence (1). The more we can back up that the problem actually exists via insights (qualitative or quantitative) the higher the confidence will be:</p><ul><li><strong>Low</strong>: The problem is only backed up by personal opinion or few external requests</li><li><strong>Medium</strong>: The problem is backed up by data through customer evidence (surveys, interviews, requests)</li><li><strong>High</strong>: The problem is backed up by data collected through experiments or tests or data-insights at scale (e.g. production environment)</li></ul><p>Take a look at<a href="https://itamargilad.com/the-tool-that-will-help-you-choose-better-product-ideas/"> Itamar Gilad’s definition</a> if you’re aiming for a more granular confidence scale.</p><p>The combination of Reach, Impact, and Confidence is what we describe as the value an Opportunity can provide. At this stage in the process, we can filter all Opportunities that provide not enough value and only continue with the ones that actually do. To get a better overview and automate the calculation, sorting, and filtering we‘ve created a <a href="https://docs.google.com/spreadsheets/u/1/d/1pHfgL-1MMp2IRGTWAIqV-7RCi0Sy5g5c_JxTaMh2yMo/copy">spreadsheet</a>.</p><figure><img alt="A spreadsheet that ranks all Opportunities based on the value they provide." src="https://cdn-images-1.medium.com/max/1024/1*IYIjz2l23kHBBXhiaXM_tw.png" /><figcaption>A threshold of 0.5 marks Opportunities red if they provide value below a threshold of 0.5</figcaption></figure><p>Estimating the <strong>Effort</strong> required to solve a problem is especially hard when you don’t know the details of a possible solution yet. To compensate for the lack of specificity we estimate the effort, usually measured in time, by considering the following factors instead:</p><ul><li><strong>Risk</strong>: The likelihood that we break things and therefore need to invest in risk management.</li><li><strong>Complexity</strong>: The complexity we are facing to create or rollout a solution due to dependency or stakeholder management.</li><li><strong>Uncertainty</strong>: How much of the landscape of a problem is unknown territory.</li></ul><p>The idea is that the more risk, complexity, and uncertainty you are facing, the longer it will take to deliver a solution to a problem. To be able to rank Opportunities according to their efforts, we practice relative estimations.</p><p>First, we print all Opportunities on cards and put them on a table in no particular order of format. Then, we pick the Opportunity we conclude it will take the lowest effort to deliver a solution and put it to the lowest end of the scale we’ve drawn on a whiteboard. Next, we randomly pick one of the remaining Opportunities and compare it with the one previously added. Depending on if we believe that it takes less, equal or more effort, we put the card below, next to or above it. We continue picking the remaining Opportunities one after another and compare them with the ones that are already on the board starting with the lowest until we’ve found the right spot along the scale. Once finished, we end up with Opportunities distributed on a scale where the easiest to execute can be found at the lower end and the most difficult at the top.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4rSRkBYxEltrr83o-SYG9g.gif" /><figcaption>We use relative estimations to determine the Efforts required to work on an Opportunity</figcaption></figure><p>To assign an Effort score to the Opportunities we use the exponential Fibonacci scale (1, 2, 3, 5, 8, 13, 21, 34, 55, …), rather than linear, to take into account that estimates are less precise and predictable the bigger they are.</p><p>Because we are never interested in working on Opportunities that deliver a low value, we don’t even consider estimating their efforts and only do this with a set of Opportunities that scored above a certain Reach, Impact, and Confidence threshold. We usually start with a threshold of 0.5 of the calculated value and adjust it later if necessary.</p><p>Finally, we put the estimated Effort into our spreadsheet. The resulting RICE score helps to determine the Opportunities that provide the greatest value compared to their costs.</p><figure><img alt="A spreadsheet that highlights all Opportunities that provide high value for low effort" src="https://cdn-images-1.medium.com/max/1024/1*rFmA_lBYcXi5mq5DZf-G4Q.png" /><figcaption>The conditional formatting in the <a href="https://docs.google.com/spreadsheets/u/1/d/1pHfgL-1MMp2IRGTWAIqV-7RCi0Sy5g5c_JxTaMh2yMo/copy">RICE Spreadsheet</a> supports to identify Opportunities that provide the greatest value compared to their costs.</figcaption></figure><p>Plotting the results on a chart that compares effort and value even better illustrates the idea of <em>low hanging fruits </em>— Opportunities that require low effort in return for high value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rtVmB8z5Vj3Gn8igOVaPuw.png" /><figcaption>The RICE Chart compares Value and Effort. The lower right corner contains the low hanging fruits.</figcaption></figure><p>The result leaves you with the challenge to now balance your work around short, medium and long term work on Opportunities and the feasible throughput of your team.</p><h3>Do the things right</h3><h4>Develop Solutions</h4><p>Until now we deliberately avoided the consideration of solutions to avoid bias in the Discover &amp; Definition phases. The <em>Develop</em> phase aims to generate as many solutions to deliver on Opportunities that graduated from the <em>Define</em> phase. They can be sourced in ideation workshops, by talking to your customers or researching industries’ best practices. More often than not the initial idea on how to solve a problem turns out to be just one of many and most likely not the best.</p><h4>Deliver Solutions</h4><p>During the creation of Opportunities at the beginning of our process, we also identify possible success metrics. Before implementing and shipping any solution, we ensure that we can track and analyze them. We can then use these success metrics to define and commit to quarterly goals in the form of Objectives and Key Results.</p><p>In fact, we rarely hit our goals first try. We continuously ship, analyze and improve solutions in an iterative process where we regularly go back into the <em>Develop</em> phase trying to find new ways of solving the problem.</p><h3>Conclusion</h3><p>The process as outlined above is the result of many iterations. It will continue to be improved as we discover new concepts or approaches that are even more appropriate. That said, we know it is not perfect. Many data points are far away from a scientific approach and sometimes are still derived from gut feeling rather than from insights provided by a data-driven landscape. But we strongly believe an imperfect system is still better than having no system at all, if merely for the sake of being able to pinpoint flaws and potential improvements.</p><blockquote>👉 Grab a free copy of our <a href="https://docs.google.com/spreadsheets/u/1/d/1pHfgL-1MMp2IRGTWAIqV-7RCi0Sy5g5c_JxTaMh2yMo/copy">RICE Google Spreadsheet</a></blockquote><h4><strong>References</strong></h4><p><a href="https://www.producttalk.org/2016/08/opportunity-solution-tree/">https://www.producttalk.org/2016/08/opportunity-solution-tree/</a><br><a href="https://www.designcouncil.org.uk/news-opinion/design-process-what-double-diamond">https://www.designcouncil.org.uk/news-opinion/design-process-what-double-diamond</a><br><a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/">https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/</a><br><a href="https://itamargilad.com/home/the-tool-that-will-help-you-choose-better-product-ideas/">https://itamargilad.com/home/the-tool-that-will-help-you-choose-better-product-ideas/</a><br><a href="https://www.agilealliance.org/glossary/relative-estimation/">https://www.agilealliance.org/glossary/relative-estimation/</a><br><a href="https://openclassrooms.com/en/courses/4544631-learn-the-fundamentals-of-agile-estimation/5157731-learn-the-benefits-of-relative-estimation">https://openclassrooms.com/en/courses/4544631-learn-the-fundamentals-of-agile-estimation/5157731-learn-the-benefits-of-relative-estimation</a><br><a href="https://www.youtube.com/watch?v=XfZpkxhpUzQ">https://www.youtube.com/watch?v=XfZpkxhpUzQ</a><br><a href="https://elearningindustry.com/using-the-fibonacci-sequence-makes-better-agile-development-5-reasons">https://elearningindustry.com/using-the-fibonacci-sequence-makes-better-agile-development-5-reasons</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52063ac257bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Senior Front-End Engineer (m/f/d) — Design Systems and Tooling @ ResearchGate]]></title>
            <link>https://medium.com/@weaintplastic/senior-front-end-engineer-m-f-d-design-systems-and-tooling-researchgate-38b807c3042d?source=rss-c0ca7c85c9ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/38b807c3042d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[jobs]]></category>
            <dc:creator><![CDATA[Roland Lösslein]]></dc:creator>
            <pubDate>Mon, 27 May 2019 15:55:22 GMT</pubDate>
            <atom:updated>2019-05-27T15:56:52.102Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Senior Front-End Engineer </strong>(m/f/d)<strong> — Design Systems and Tooling @ ResearchGate</strong></h3><p>This is a full-time position based in Berlin</p><h3><strong>The Mission</strong></h3><p>The web was created by scientists, to foster scientific collaboration and drive progress for a better world. Here at ResearchGate, we’re looking for a committed front-end engineer to join our Design Systems and Tooling team. We are a bunch of passionate optimists from all around the world and many different backgrounds. Together, we focus on taking the web back to its original mission and changing the way scientists communicate for the better.</p><p><em>We love what we do. We connect the world of science and make research open to all.</em></p><h3><strong>The Opportunity</strong></h3><p><strong>Work with impact</strong> At ResearchGate your input can help over 15 million scientists and researchers to solve global challenges. Whether studying the first moments of our universe or tracking global warming, our users are making a real difference.</p><p><strong>Building at scale</strong> Building at scale means to create solutions that facilitate an end-to-end design workflow that enables designers and engineers in over a dozen product teams to continuously ship reliable features and great user experiences.</p><p><strong>Grow at work</strong> At ResearchGate we put people first. You’ll join an environment where your personal development is our number one priority. In regular one on ones, quarterly feedback talks and annual check-ins you and your manager will identify possible paths for you to grow and the right amount of guidance needed to reach your goals. We provide education budget and free days to attend conferences to make sure you can gain knowledge in the fields you are most interested in.</p><p><strong>Have ownership</strong> As a member of the Design Systems and Tooling team, you’re given the opportunity to own medium to long-term initiatives and potentially entire solutions. Your thinking, your processes, and execution will be key to the success of new ideas.</p><h3>The Requirements</h3><p>To be successful in the role of a Senior Front-end Engineer Design Systems and Tooling at ResearchGate folks will need to have:</p><ul><li>Deep understanding of JavaScript and CSS principles and architecture</li><li>Expert knowledge on React ecosystems needed to build rich front-end applications and scalable design systems</li><li>Common understanding of accessibility best practices</li><li>Experience working with tools to orchestrate, test, build, release and publish your work (e.g. webpack, yarn, lerna, npm, node, babel, jest, eslint, jenkins, etc.)</li><li>Passion for the nitty gritty details that create great user experience</li></ul><p>You’ll join an environment where people come first. Your increasing scope of ownership and autonomy will be one metric to your successful personal development. You can expect that…</p><ul><li><strong>in 3 months</strong> you’ll be able to work completely independent, creating small to medium features while continuing to gain insights into our ecosystem via pair programming.</li><li><strong>in 6 months</strong> you’ll actively drive mid-term goals, give meaningful feedback to your colleagues in code reviews, and actively contribute to the core processes and best practices of your team.</li><li><strong>in 1 year</strong> you’ll become an expert and own an entire product in the range of our solutions. You’ll create and manage roadmaps, coordinate contributors and stakeholders, and constantly identify new opportunities.</li></ul><h3>The Team</h3><p>You will join a dedicated Design Systems &amp; Tooling team that works at the intersection of design and technology and is shaping the future of ResearchGate’s UX. We’re experts in creating scalable cross-platform design systems and tools that bridge the gap between design and engineering. Our mission is to create solutions that facilitate an end-to-end design story lifecycle so that designers, engineers and copywriters are enabled to collaborate closely and ship features that make a real difference.</p><p>Meet the crew:</p><h3>👩🏻‍🚀</h3><p>Nika is our CSS specialist. She knows how to make things flex across platforms, devices, and other distant galaxies.</p><h3>👨🏼‍🚀</h3><p>Ryen’s focus is on design tooling. His solutions are like superglue that connects designers and engineers.</p><h3>👨🏻‍🚀</h3><p>Tim is our architect. He decodes our most complex problems and makes rocket science easy to understand for everyone.</p><h3>👨‍🚀</h3><p>Roland is the captain. If this was a Hollywood movie, he’s the one willing to sacrifice himself for the crew.</p><h4><strong>Achievements</strong></h4><p>In the past four years we’ve bootstrapped and championed a design system for the web and emails. With custom tools like plugins for Sketch or a tailored design-to-engineering handoff solution, we’re facilitating an end-to-end design workflow that is relying on the design system’s codebase without becoming overwhelming for designers. This makes us one of the few UX organisations worldwide to have successfully established code as the single source of truth on standards for both designers and engineers. You can read more about it over here on Medium:</p><p><a href="https://uxdesign.cc/design-handoffs-that-specify-design-system-standards-410531d9c05a">Design handoffs that specify design system standards</a></p><h4><strong>Challenges</strong></h4><p>There are countless opportunities for you to make an impact. Next on our road-map is to further improve the design-to-engineering handoff by turning it into a one-stop-shop for engineers with all the resources needed to translate designs into functional features. That includes copywriting deliverables, accessibility instructions, static assets and code snippets of individual elements.</p><p>Designing and prototyping with real data is in high demand. Instead of using just any kind of data, we want to be able to use our own data to create high fidelity prototypes for user tests and more realistic designs that can stand the test once they are implemented. Our goal is to seamlessly integrate the possibility to access and spread this kind of data into the designer’s toolbox.</p><h3>Our Story</h3><p>ResearchGate was founded in 2008 by three friends who believed it was possible to connect all of the world’s scientists.</p><p>We started out with just a handful of members. By 2011, one million ResearchGate members discussed their research questions and shared advice on the then newly launched forums.</p><p>By 2015, four complete rounds of financing had fueled ResearchGate’s growth and investors included Benchmark Capital, Founders Fund, Bill Gates, Tenaya Capital, Goldman Sachs, Wellcome Trust, and Four Rivers Group.</p><p>Today, 15 million scientists connect on the network, collaborate, and share their research. They report on their research as it happens and get feedback to make progress faster. They post 500 questions and give 2000 answers daily. They find jobs that fit their interests and research profiles. They connect to universities and companies through advertising solutions.</p><p>We’re now closer than ever to fulfilling our mission to connect the world of science and make research open to all.</p><h3>Hiring Process</h3><p>Our hiring process is transparent and uncomplicated. You’ll have a chat with one of our recruiters as the first step. Instead of expecting you to work on a take-home assignment for hours by yourself, we’re going to pair-program together with you on-site where you’ll also meet the people you’ll be working with. With respect to your time we might ask you to complete a concise online questionnaire upfront.</p><p>We’re located in the heart of Berlin, one of the most exciting cities in the world and a place where people from all walks of life feel welcome.</p><blockquote>If you are interested please DM me or apply over here: <a href="https://www.researchgate.net/careers/senior-front-end-engineer-design-systems-and-tooling-m-f-d-5c2bfe6d-8950-4d2b-b55d-8b3a10ff3a2a">https://www.researchgate.net/careers/senior-front-end-engineer-design-systems-and-tooling-m-f-d-5c2bfe6d-8950-4d2b-b55d-8b3a10ff3a2a</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38b807c3042d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design handoffs that specify design system standards]]></title>
            <link>https://uxdesign.cc/design-handoffs-that-specify-design-system-standards-410531d9c05a?source=rss-c0ca7c85c9ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/410531d9c05a</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Roland Lösslein]]></dc:creator>
            <pubDate>Tue, 07 May 2019 09:52:40 GMT</pubDate>
            <atom:updated>2019-11-02T14:02:31.670Z</atom:updated>
            <content:encoded><![CDATA[<p>About three years ago we started to build a unified and shared design language at ResearchGate. What started with standardizing basic design tokens like colors, fonts and drop shadows quickly evolved into an ecosystem of libraries, workflows and tools managed and maintained by a dedicated Design System and Operations team.</p><p>ResearchGate caters to a monthly audience of over 60 million readers and 15 million registered scientists through numerous different product offerings and countless use cases. Aiming to serve a delightful user experience for this breadth of scenarios in an efficient manner we created Nova, our design system. Among the many benefits that unfolded since Nova’s first release, most importantly, Nova’s unified design language streamlined the way stakeholders communicate about design. Everyone involved in the lifecycle of design tasks and projects adopted our shared design vocabulary, which in turn simplified the collaboration of people across different functions.</p><p>A critical moment in our collaboration is how designers share design deliverables and briefings with engineers. Unfortunately, in terms of referring to design system components, this step became a breaking point. Using conventional handoff tools would result in the loss of meaningful information about the specific design standards used in a design. In the absence of any explicit descriptions, engineers often needed to guess components and detailed specifications — which complicated collaboration significantly.</p><h3>Problem — The loss of information</h3><p>Nova is what’s commonly known as an open design system. It hides away technical complexity and high configurability behind multiple layers of abstraction. While the flexibility of an open design system allows us to successfully provide and maintain a maximum number of component configurations, it lacks the simplicity of closed systems that focus on addressing a smaller range of specific use cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g05XY9UTmqktjp-MDPx8ug.gif" /><figcaption>Inspecting the Button configurations inside Nova’s living styleguide</figcaption></figure><p>For example, when configuring a Nova button, any combination of the four main properties (such as color, size, radius and theme) will result in more than 200 valid button specifications. Meanwhile, conventional design handoff tools are not able to understand and convey the specifics of such complex design system components — and at this point, Nova hosts over 40 them. Regular design deliverables would be constructed with dozens of these components in varying configurations. This complexity makes it virtually impossible for engineers to “manually” read a design deliverable and translate it into code. Without detailed design system-aware specs, all information about the use of standards would be lost at the point of exporting handoff files from Sketch.</p><p>The consequence of underspecified design handoffs is a very poor developer experience.</p><h3>Solution — Smart handoffs that do speak design language</h3><p>Nova’s principles and architecture are tailored to the specific needs of ResearchGate. In fact, we didn’t expect any conventional design handoff solution to match our unique requirements. Instead, we’ve created our own solution that seamlessly integrates with existing workflows.</p><p>Available as a plugin for Sketch, our solution allows exporting of design specs with a single click. The result is a shareable HTML file that allows the design work to be inspected when opened in a browser. Engineers and other stakeholders are able to discover any aspect of the design work and find all relevant design system information at a glance. Colors, fonts, radiuses and other design tokens are translated to their corresponding aliases. This, in turn, simplifies their usage with provided APIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*__prayEW2iYqdRyhJgon8g.gif" /><figcaption>Inspecting standards in our custom design handoff</figcaption></figure><p>Every design system component included in the design is marked as such, making it easy to distinguish between what’s already covered by standards and what’s meant to become a custom implementation. Next to a list of component properties JSX code snippets allow engineers to seamlessly translate designs into code conforming with Nova standards.</p><h3>Conclusion</h3><p>Today, after investing about two years of continuous development into our tooling, Nova’s code library is the single source of truth for both engineers and designers. Designers render components into Sketch directly from the codebase, allowing them to access the most up-to-date resources of the Design System at any given point in time. Specific details about what components were placed by the designer and what component configuration was chosen are replayed for engineers in the design handoff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J6qOAPJbBjqvng5oSLqPeQ.gif" /><figcaption>From styleguide to Sketch to design handoff — The end-to-end design to engineering workflow</figcaption></figure><p>We bridged a massive missing link in our workflow by being able to preserve and forward information about design system usage throughout the entire design and engineering lifecycle. Engineers are now able to find all necessary information to identify and use design standards right at their fingertips — which is making translating designs into code a one click effort (literally).</p><p>Our investments in custom handoff tooling have allowed us to vastly increase the efficiency of teams and improve the overall developer experience when working with our design system.</p><p>Next up, we are working on the integration of copy briefings and accessibility specifications to finally turn design handoffs into a one-stop-shop experience for engineers.</p><p>Stay tuned.</p><p><em>By Roland Lösslein, Design Systems Lead, ResearchGate<br></em><a href="https://twitter.com/weaintplastic"><em>https://twitter.com/weaintplastic</em></a></p><p><em>and Christian Gaillard, Head of Design, ResearchGate<br></em><a href="https://twitter.com/uxchg"><em>https://twitter.com/uxchg</em></a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=410531d9c05a" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-handoffs-that-specify-design-system-standards-410531d9c05a">Design handoffs that specify design system standards</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>
        <item>
            <title><![CDATA[Pull-to-Return — A new interaction pattern?]]></title>
            <link>https://medium.com/@weaintplastic/pull-to-return-a-new-ux-pattern-d409404f7313?source=rss-c0ca7c85c9ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/d409404f7313</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[material-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Roland Lösslein]]></dc:creator>
            <pubDate>Fri, 12 Jun 2015 15:38:42 GMT</pubDate>
            <atom:updated>2015-06-17T13:19:20.711Z</atom:updated>
            <content:encoded><![CDATA[<h2>Pull-to-Return<br>A new interaction pattern?</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*ykYgVSZej6dru0JM-xUTCA.gif" /><figcaption>A screen capture of my prototype crafted with Framer</figcaption></figure><p>Recently I stumbled upon feedly’s post here on medium where they share some interesting insights about the process of redesigning their mobile platform following the principles Google’s material Design.</p><p>While many of the things shown there are already quite common, on certain thing caught my attention. <em>Arthur Bodolec</em>, Design co-founder at feedly, showed an interaction pattern, I’ve rarely seen before. Like the widely adapted Pull-to-Refresh interaction, Pull-to-Return instantly throws you back to the overview once you overdrag the content to a certain point. Unfortunately Arthur noted that this particular feature will be definitely shipped one day even it is not included in upcoming releases.</p><p>I really wanted to know how this might work out in the wild. So I sat down and crafted a prototype using Framer and I really love the result. Feedly did an awesome job and the whole idea of switching from article back to the overview that way feels so natural.</p><p>I’ve uploaded the prototype to my website. I’d love to hear what you think.</p><h4><a href="http://prototypes.weaintplastic.com/pull-to-return/"><strong>Tryout the prototype</strong></a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d409404f7313" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A two level mobile menu approach]]></title>
            <link>https://medium.com/@weaintplastic/a-tow-level-mobile-menu-approach-ca9db005745b?source=rss-c0ca7c85c9ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca9db005745b</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Roland Lösslein]]></dc:creator>
            <pubDate>Fri, 12 Jun 2015 14:47:23 GMT</pubDate>
            <atom:updated>2015-06-17T09:14:53.861Z</atom:updated>
            <content:encoded><![CDATA[<h2>Two Level</h2><h2>Mobile Menu</h2><h2>Approach</h2><p>Recently I’ve worked on a Project with a pretty complex information architecture on two levels.</p><p>While the Desktop version had its challenges, the first drafts of the mobile version became pretty messy and hard to use. So I went a step backward and defined some key requirements that should help me to find a better solution</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/233/1*991xmrafiAytn770L6BX6A.gif" /></figure><ul><li>Access via burger icon and support for drag gestures</li><li>Separate second level but preserve quick access to the first level at any time</li><li>Preserve level status after selecting a second level menu item</li><li>Integrate quick access to the search functionality on both levels</li></ul><p>After some wireframes and prototypes I came up with a solution that combined common mobile menu interactions with the list of requirements and some nice transitions and interactions.</p><p>You can find a working prototype on my Website</p><h4><a href="http://prototypes.weaintplastic.com/two-level-mobile-menu/"><strong>Tryout the Prototype</strong></a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca9db005745b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let me be your rubber duck]]></title>
            <link>https://medium.com/@weaintplastic/let-me-be-your-rubber-duck-f6c605a059e4?source=rss-c0ca7c85c9ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6c605a059e4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Roland Lösslein]]></dc:creator>
            <pubDate>Fri, 12 Jun 2015 14:13:09 GMT</pubDate>
            <atom:updated>2019-02-13T10:30:02.009Z</atom:updated>
            <content:encoded><![CDATA[<h3>Three simple ideas on how designers and<br>developers may collaborate</h3><p>Nowadays it seems everybody is aware that bringing together Designers and Developers is the key for building successful products. You can read about this on numerous platforms and even I’ve written about the <a href="https://medium.com/@weaintplastic/your-developers-aint-slow-56f47d6ef629">importance of involve Developer’s early in the process</a>. But while everybody agrees on the importance of this topic and the indispensability to implement such a collaborative environment, there seems to be a leak of ideas on how to exactly raise the treasure of this hidden potential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*EUJqtmL3alr53hPTD8R4Sg.png" /></figure><p>Simply putting a designer and a developer together into a room probably ain’t gonna work. Here are some ideas on methods and strategies to make collaboration the key in creating beautiful and meaningful products.</p><h4>Pair programming and designing</h4><p>Working in pairs is a common technique in agile software development. While the <em>driver</em> is constantly writing code, the <em>observer,</em> who is sitting right next to him, is reviewing each line of code and giving strategic directions of the work. I noticed, that teaming up designers and developers in pairs, while a developer’s taking the role of the designers observer and vise versa, can become the magical bullet in your workflow. Sharing deep insights on work strategies, knowledge about feasibility, patterns and general thinking plus having the chance of influencing the outcome will not just lead to a great fellowship between designers and developers but can be seen as a continuous process of learning and education.</p><h4><strong>Let the other be your rubber duck</strong></h4><p>Another great strategy that was evolved in software development and can be applied to the collaborative work between designers and developers is the principle of <em>Rubber duck debugging</em>. In short, developers are asked to explain their problem to a rubber duck (yes you heard right) in order to force them thinking out loud. It is quite common that the solution for a problem some times just pops out of nothing, by just explaining yourself to someone else. Taking this technique into our context, will ask designers to explain the challenges they meet to a developer and will ask a developer to invite a designer the next time he is fixing a bug or facing a challenging task. This way both will share insights into the strategy of thinking and problem solving in their specific fields and gather meaningful information that can influence their own way of working.</p><h4><strong>Stay with what you know but share it</strong></h4><p>Today I see a lot of designers striving into the fields of development and becoming overwhelmed by the complexity and diversity of techniques, tools and languages. Especially in the fields of <em>User Experience Design,</em> tools like Framer Studio became pretty popular in the design scene. Its flexibility of creating prototypes with Coffeescript (Javascript) earned a lot of compliments but caused lot of frustration for designers who had to write code for the first time in their life. On the other hand, there are developers who struggle hard with creating meaningful transitions in user interfaces or with their responsibility on creating excellent user experience and meet the expectations of designers. The idea is simple but effective: Team up designers and developers whenever they face their own weakness which probably is the strength of the other.</p><p>That said, give developers the possibility to demonstrate their strength in coding prototypes and taking care about the code architecture while designers still take the direction of look and feel. Both sooner or later evolve to something that is located between development and design and will unveil the hidden potential.</p><p>But no matter which strategy or method you choose, there is one fundamental key to make this a story of success rather then a mess:</p><p>It’s treating each other with <strong>Respect</strong>.</p><p>Both, designers and developers put so much more into their work then just time and skills. A good portion of passion, blood, sweat and tears emotionally binds each individual to their work. What is usually a good thing, can turn out to become the deal breaker when it comes to criticism or decision making.</p><p>Although both share a lot of commonalities and commitments, there seems to be a thin line between a potentially productive collaboration and a mess of emotions, vanities and bullishness. To make all this work, it is a must that you treat the ideas of each other right. Talk about alternatives instead of labeling other’s work as a fail. Try to see the good things of somebody’s work, I’m pretty sure there is always something hidden, that can be transformed to a new vision. And try to learn as much as possible about the way others are working and let their thinking influence the way you are used to work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6c605a059e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unveiled Sticky Navigation — A neat UI pattern examined and enhanced]]></title>
            <link>https://medium.com/@weaintplastic/mediums-unveil-navigation-ux-pattern-2108f9a53631?source=rss-c0ca7c85c9ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/2108f9a53631</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Roland Lösslein]]></dc:creator>
            <pubDate>Sat, 17 Jan 2015 17:49:56 GMT</pubDate>
            <atom:updated>2015-05-29T08:21:22.686Z</atom:updated>
            <content:encoded><![CDATA[<h2>Unveiled-Sticky-Navigation</h2><h2>UI Pattern</h2><p>Ever since I discovered medium.com the first time, I’m fascinated by the way how they deal with the main navigation while scrolling. I don’t know, if they were the first ones who used this kind of UI pattern, but they were the first ones that brought my attention to this.</p><p>This is how it basically works. Scrolling down will move the navigation out of the viewport quite naturally. But here’s the thing: Once you scroll up a little bit, the navigation will be unveiled right ahead without the need to scroll to the very top of the page where you left it before.</p><p>I did some research lately, but I couldn’t find any term that is in use for that kind of UI pattern. Since it feels like unveiling a sticky navigation, I just call it <em>Unveil Navigation Pattern</em> for now, but please feel free to educate me.</p><p>The big advantage of handling things this way is that you can focus on what’s important while scrolling down, but bring back in what the user is probably looking for when scrolling up. Furthermore on mobile devices this technique will leave space that’ll be available for the content.</p><p>I got some time to tinker a little bit and create a jQuery plugin to make this UI pattern available for others. I’ve also found some useful features that’ll enhance this pattern:</p><ul><li>Scrolling up to the very top, the navigation can be transformed to a <em>special state</em> (like an extended version)</li><li>Once scrolled to the very bottom, the navigation will be <em>automatically unveiled</em>, which gives users new opportunities on where to go next when finished reading the content.</li><li>An <em>offset</em> will define how much pixels a user needs to scroll up until the navigation becomes unveiled. This will prevent distraction from reading the content when users scroll up just a bit.</li><li>Even if hiding and unveiling the navigation naturally with the speed you are scrolling, an <em>acceleration</em> property will help you to get some kind of lazy navigation unveiling/hiding.</li></ul><h3>The plugin on GitHub</h3><p><a href="https://github.com/weaintplastic/jquery-unveiled-navigation">https://github.com/weaintplastic/jquery-unveiled-navigation</a></p><h3>An example over at Codpen</h3><p><a href="http://codepen.io/weaintplastic/full/RNpXOO/">http://codepen.io/weaintplastic/full/RNpXOO/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2108f9a53631" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developers ain’t slow]]></title>
            <link>https://medium.com/@weaintplastic/your-developers-aint-slow-56f47d6ef629?source=rss-c0ca7c85c9ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/56f47d6ef629</guid>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Roland Lösslein]]></dc:creator>
            <pubDate>Fri, 16 Jan 2015 16:50:14 GMT</pubDate>
            <atom:updated>2017-08-17T10:52:06.207Z</atom:updated>
            <content:encoded><![CDATA[<p>Developers often find themselves at the end of the production chain that already seems to be messed up even before their work has begun. Facing unrealistic deadlines, small budgets or missing specifications can cause frustration and helplessness. Here are a few thoughts that can help to improve your production workflow and meet the expectations of developers</p><h4>1. Involve Developers early in the process</h4><ul><li>Excluding Developers from decisions that are made during the design thinking and making, can lead to concepts that are impossible to build or more likely not thought through. Developers can serve another perspective on things and may come up with ideas and solutions that make building stuff easier and more efficient.</li><li>Having somebody there, that can tell you what’s technologically possible and what’s not, can sharpen others sense of nowadays possibilities in digital products. Restricted through guidelines or technological capabilities you can find thousand of perfectly good looking dribbbles out there which most like won’t ever find their way into production.</li><li>Clients, Designers, Developers, Product Owners and Project Managers, they all have a different interpretation of the complexity and prioritisation of tasks in an project. That’s not a mischief, it’s the nature of the beast. Face it, involve everybody of the team early and on a regular basis and you’ll get a more realistic evaluation of time and budgets.</li><li>Developers are making design decision all the time. Designers rarely have the time think through every part of a website. This is why developers have to make decisions that affect the design anyways. Involving a developer in the early stages will allow them to fill in the blanks.</li><li>Involving developers early will lead to a greater sense of project ownership. Let developers speak, hear there voice and you’ll end up with a true creative workflow you’ve ever dreamt of.</li></ul><h4>2. Clear requirements</h4><p>Writing a good briefing is important. How can a developer start on a project without understanding how it should work? Handing over undercooked project project specs will cause frustration and slows down the development process. If you follow my suggestions of point 1 it should be a pretty easy task to sit down together and define the final project specification before heading into production.</p><h4>3. Missing Project Leads</h4><p>Developers often find themselves in the role of the master mind of a project. Probably because they tend to dive deeper into things than anybody else before. Define somebody in the team who owns the product, who will keep the overview and is willing to answer and think of any questions raising.</p><h4>4. Changing requirements</h4><p>Constantly changing specs during production is probably one of the biggest game breakers for developers. Even an agile workflow needs a stable scope of work for every sprint. So don’t throw tasks into the production cycle that are not thought through or feel imperfect.</p><h4>5. Context switching</h4><p>Context switching can cause huge problems regarding efficiency.<br>Asking a developer to switch from Task A to Task B is pretty tough since the time that it takes to get into a new scope is pretty high.</p><h4>7. Take responsive design serious</h4><p>The majority of website designs are delivered desktop only. Responsive states are discussed in passing which is totaly fine for most of the cases. But as soon as components become more complex, have a lot of interactions and different states, just talking about the responsive version won’t work anymore. Try to find a way to communicate your visions and help you to think through responsive states. Team up with developers and think about it together and you probably don’t have to deliver final designs, sometimes wireframes do the job perfectly fine.</p><h4>9. Missing breakdowns and style guides</h4><p>Browsing through a huge PSD or Sketch file in order to collect used fonts and font sizes, colors and icons is simply a pain in the ass. Provide breakdown sheets that provide basic information about your design work. Furthermore it can serve as the template for a frontend styleguide to onboard upcoming team members quickly.</p><h4>10. Regular meetings with the whole project team</h4><p>Just do it. Meet up with all project memebers on a regular basis. It will keep the process transparent for everyone involved. Talk about the projects scope of work, the current timeline and about outstanding tasks for the next day or two. Discuss incoming requirements and different opinions anytime. But try to keep this as efficient as possible. 10–15 min standup meetings every day should be enough.</p><p><em>I was inspired to write about this after reading that </em><a href="https://sprint.ly/blog/your-developers-arent-slow/"><em>excellent article</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56f47d6ef629" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>