<?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 Ken Skistimas on Medium]]></title>
        <description><![CDATA[Stories by Ken Skistimas on Medium]]></description>
        <link>https://medium.com/@kskistimas?source=rss-507f50a34832------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Mq7ZLicjA5EaMkB6p_Lrzg.png</url>
            <title>Stories by Ken Skistimas on Medium</title>
            <link>https://medium.com/@kskistimas?source=rss-507f50a34832------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:10:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kskistimas/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[Driving Quality and Consistency at Scale]]></title>
            <link>https://medium.com/facebook-design-business-tools/driving-quality-and-consistency-at-scale-644f9a744d5e?source=rss-507f50a34832------2</link>
            <guid isPermaLink="false">https://medium.com/p/644f9a744d5e</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-at-scale-series]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[business-tools]]></category>
            <dc:creator><![CDATA[Ken Skistimas]]></dc:creator>
            <pubDate>Tue, 17 Dec 2019 22:15:49 GMT</pubDate>
            <atom:updated>2020-07-30T16:58:02.333Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrRHSr2yWtuZnHZ6YENx6A.jpeg" /><figcaption>Illustration: Ximena Cuenca</figcaption></figure><p><em>This post is part of an ongoing series about design at scale. Read “</em><a href="https://medium.com/facebook-design-business-tools/doing-design-at-scale-57c972d6b183"><em>Doing Design at Scale</em></a><em>” by Lucinda Burtt, “</em><a href="https://medium.com/facebook-design-business-tools/design-at-scale-modern-design-tools-204f01a6cf06"><em>Modern Design Tools</em></a><em>” by Daniel Eden and “</em><a href="https://medium.com/facebook-design-business-tools/creating-stable-design-systems-at-scale-daa68a3c6b14"><em>Creating Stable Design Systems at Scale</em></a><em>” by Sean Blanton.</em></p><p>I’ve designed user experiences for business and enterprise software for most of my career, including at big brands like Salesforce and GE Digital. Yet when Facebook approached me in early 2018 about helping to design and build its ad and business tools, I was surprised.</p><p>Like most people, I associated Facebook design with products like the newsfeed and Instagram. But over the past year, I’ve discovered that the expansive suite of tools that support ads and business products presents a tremendously exciting opportunity to tackle some hearty and intriguing design problems at an immense scale.</p><p>I come from a family of entrepreneurs, designers and makers. We all enjoy finding creative and clever solutions to hard problems. It also happens that several of my family members own small businesses that rely on Facebook ads to drive awareness and promotions. In designing for Facebook’s ads and business tools, I’m in my element. I understand the value of a well-crafted mechanism that gets the job done efficiently — and I appreciate how important our tools are for growing businesses.</p><p>The challenge and responsibility of building software that millions of people depend on for their livelihoods really speaks to me.</p><h4><strong>Consistent answers to complex questions</strong></h4><p>My role as a product design manager is to help create and implement a coherent design language that’s built especially for Facebook’s ads and business customers. My team thinks about big questions like: How do you put rigor behind design? How do you predict impact at a global scale? How do you test and validate the critical real-world effects?</p><p>We focus on designing and building elements that are shared among at least a dozen Facebook ad and business tools. This includes designing the look and feel, as well as the functionality, of thousands of individual components, such as buttons, input elements and data visualizations. It means creating and sharing best practices among not just products and processes, but also subproducts and subprocesses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xKTW052Xk4wmfXY6NOv7oA.png" /><figcaption>Illustration: Facebook’s IPB4B Team</figcaption></figure><h4><strong>Systematic change at scale</strong></h4><p>Over the past 12 years, Facebook’s ad offerings have expanded as rapidly as Facebook itself. We now serve more than 7 million businesses. It’s terrific to have the responsibility of helping to grow and support that many mostly small- and medium-size businesses.</p><blockquote>Achieving our goals of improved consistency, upleveling the craft and boosting the overall quality of our products would be challenging at any big company, and it is certainly true at a global company like Facebook.</blockquote><p>But along the way, the experiences across the tools started to diverge and become inconsistent: This workflow changed; that feature merged with another. Just as often, pieces and parts were teased apart as industry standards evolved.</p><p>We realized that the people who advertise on Facebook faced potential confusion and decreased efficiency. Actions people were used to taking weren’t in the same place from tool to tool, or the same task had a different workflow.</p><p>Achieving our goals of improved consistency, upleveling the craft and boosting the overall quality of our products would be challenging at any big company, and it is certainly true at a global company like Facebook.</p><p>First, Facebook is a company that prides itself on always shipping. It can be quite difficult to get multiple teams to stop what they’re working on and align around a consistent treatment of a similar workflow or interaction pattern.</p><p>Second, we always keep at the top of our minds those 7 million advertisers I mentioned. As you might imagine, such a large number of people means we have to support a wide variety of use cases, from small businesses in rural areas to Madison Avenue advertising agencies that support hundreds of blue-chip clients.</p><p>Beyond that, most users come to the consumer-facing Facebook on their mobile devices. However, a majority of our business customers are on desktop or laptop computers. And they do dramatically different things in comparison: Instead of consuming videos or large, colorful status updates, they’re typically inputting data or studying charts.</p><blockquote>Only after each design is thoroughly validated do we implement changes to the full suite of business products.</blockquote><p>Finally, it would be impractical, not to mention incredibly disruptive, to do a sweeping update to all of our products at once. Instead, we prioritize updates that encompass the most common tasks and workflows. This gives us early feedback that tells us what’s working and what needs further refinement. Only after each design is thoroughly validated do we implement changes to the full suite of business products.</p><h4><strong>Improvement by design</strong></h4><p>We know that developing a rich set of reusable interface components and shared design patterns that can be used universally across business-focused products will allow us to up-level quality and consistency en masse. But rolling out a new design language at the scale of Facebook is no easy task. It sounds complicated because it is!</p><p>Ultimately, our goal is to provide a better, more predictable experience for advertisers while increasing their efficiency by making our products more consistent. The process is time-consuming, but we know that it pays to be careful and deliberate when you’re working with tools that people depend on for their living. As a coworker of mine often says, good design is good business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=644f9a744d5e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/facebook-design-business-tools/driving-quality-and-consistency-at-scale-644f9a744d5e">Driving Quality and Consistency at Scale</a> was originally published in <a href="https://medium.com/facebook-design-business-tools">Facebook Design: Business Tools</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Balancing Flexibility and Consistency in Design Systems]]></title>
            <link>https://medium.com/ge-design/balancing-flexibility-and-consistency-in-design-systems-c24cd0a9da16?source=rss-507f50a34832------2</link>
            <guid isPermaLink="false">https://medium.com/p/c24cd0a9da16</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ken Skistimas]]></dc:creator>
            <pubDate>Mon, 12 Mar 2018 16:01:01 GMT</pubDate>
            <atom:updated>2018-03-17T16:56:58.982Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to effectively use both to create a design system that scales</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B23nQq-J_K20YzZImBLQ7Q.png" /><figcaption>Avoiding the Wild West: The right level of flexibility can help drive consistency.</figcaption></figure><p>The catalyst for many design systems is the desire to drive consistency between products. As companies grow, products expand, acquisitions occur, and priorities change, then inconsistency becomes an issue. A design system is often seen as a good way to unify disparate products. This has been the approach of most systems I’ve worked on, and it’s worked well in many cases.</p><p>It’s natural that designers look for consistency and try to build visual systems. However, when focusing on building a consistent experience, it’s easy for the goals of an end user take a back seat which ultimately compromises the experience we set out to improve. Flexibility is often seen at odds with consistency, but for a design system to scale efficiently and effectively both need to be balanced. How they’re balanced depends on the personas and workflows for your products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*2rGP92qI3mhc-jtBIaaXXQ.gif" /><figcaption>The goal of many design systems is to align a suite of products to a strict set of design rules.</figcaption></figure><h3>Why you can’t always bet on consistency</h3><p>When I arrived at GE, my perspective on design systems was very much around limiting flexibility with the goal of making products consistent. As I got to know the businesses, use cases and end users the design system supports my viewpoint changed dramatically.</p><p>The businesses we service come with a diverse set of personas, use cases and environments. The customers looking to optimize their manufacturing plants have different goals than the ones looking to monitor their wind farms. Our design system has to offer enough flexibility to support those use cases but we also need to maintain a system that’s still identifiable as <a href="https://www.predix.io/">Predix</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b7BkaHQKZfY1uKBUdAX2ng.png" /><figcaption>From the top of a wind turbine to the shop floor, the Predix Design System supports a broad set of use cases, businesses and environments.</figcaption></figure><h4>Lessons from branding</h4><p>To determine where to drive consistency and when it’s ok to break with it, there are a few concepts we can apply from branding.</p><p>First, there’s the <strong>branded house</strong> where<strong> </strong>everything falls under a master brand. For example, anytime you interact with FedEx, it’s under a variation of that well known FedEx logo.</p><p>On the other side there’s the <strong>house of brands</strong>. There aren’t any Procter &amp; Gamble products, but the company houses a family of brands such as Crest toothpaste or Bounty paper towels which are independent brands on their own.</p><p>Finally, there a <strong>blend</strong> of the two like Coca-Cola. Some products, such as Diet Coke or Coke Zero adhere to tight brand guidelines and look similar to each other. Others, like Sprite, have their own brand and look completely different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0c5XMH1cROPHEVSU823Pcg.png" /><figcaption>Branding concepts can inform design systems on where to be consistent and how to be flexible.</figcaption></figure><h4>The case for consistency</h4><p>Under the lens of design systems, a branded house is analogous to a stand alone product or a series of products that work together. For smaller companies, this model encompasses all of their products. At large, diverse companies, like GE, this is equivalent to a business unit.</p><blockquote>The products in a branded house should look and work the same most of the time <strong>because the personas using them are related</strong> and it’s not uncommon that they might use multiple products in the suite.</blockquote><p>There’s a strong case to lean towards consistency in this model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RqL7wzgVE16ouDuLQzGu9A.png" /><figcaption>A family of products that share personas and workflows make it easy to enforce consistency.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KEjHZWz8WjkPvi3KAxyHRg.png" /><figcaption>Flexibility is required when a design system supports a blend of products where some stand alone and others will need to work together.</figcaption></figure><h3>Figuring out flexibility</h3><p>If your design system supports multiple products and businesses, some of which work alone, others that work together, a system needs to be more flexible. The products might address different personas, different workflows and maybe even different customers. This is the variety of businesses and products the Predix Design System supports.</p><p>Strictly enforcing consistency might not result in the best experience for the end users and would certainly hurt adoption of the system. To give teams the right tools to address their use cases, it’s important for the system to find a balance between being consistent and being flexible. To find the right points to enforce consistency and allow flexibility, it’s important to consider the way people are using our software. User paths and workflows are good signals for where to be rigid and where to bend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BaiqkEsSu_Ogx5SvTKugsA.png" /><figcaption>A family of cars addresses multiple use cases but carry common traits across to make them identifiable as belonging together.</figcaption></figure><p>An analogy that’s useful when identifying consistent elements is a family of cars. Typically, a manufacturer will build different cars to cover a variety of use cases. Among a line up, there might be an SUV for hauling the kids around, a sporty coupe for fun on the weekends and a sedan for weekday commuters. While they all serve a slightly different purpose, they have to hold together as a family.</p><p>The cars have different profiles and varied features to better accommodate for different use cases and each hold a slightly different identity. However, there are common traits between them such as the grill shape, body lines, door handles and instrumentation.</p><blockquote>When thinking about balancing consistency and flexibility in a design system, determining a set of common traits between products is important.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dELuxcUg4y_27pvj47E2hA.png" /><figcaption>Typography, spacing, color and form styling are core elements of the Predix Design System. Some elements are consistent, others have flexibility built into them.</figcaption></figure><p>The <a href="http://predix-ui.com/">Predix Design System</a> relies on typography, spacing, a core color palette, form interaction and iconography as foundational elements. While a few of those traits are fixed, such as typography and spacing, there is room to customize others. The <a href="https://www.predix-ui.com/#/design/color">core color palette</a> allows for teams create their own theme, the data visualization color palette is extensive, and the <a href="https://www.predix-ui.com/#/design/iconography">icon family</a> is easily extendable. Building flexibility into foundational elements gives teams the ability to adapt the broader design language to their use cases while still working within the bounds of the system.</p><h3>Creating a path of least resistance</h3><p>With more flexibility built into the system, it’s important to communicate best practices to encourage consistency. That can be done by enforcing compliance with strict rules and mandates, but that method can result in resistance to the system. A more productive approach for us has been to welcome people into the process while providing a set of tools that allow for easy on boarding.</p><blockquote>Trust in the design system and the decisions behind it are important to encourage consistency. When consumers of the system can explain the “why” behind decisions, they’re much more likely to be an advocate for consistency.</blockquote><p>We make an effort to invite stakeholders into the process by holding design office hours twice a week, embedding with product teams for workshops and scheduling regular touch points with stakeholders. This gives them an opportunity to influence work in progress and contribute to defining best practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zG-xCdtfGc8VrYSG8cQLlQ.png" /><figcaption>Guidelines, sample layouts, sample applications and workshops are all great ways to drive consistency and buy in.</figcaption></figure><p>When working with distributed teams, documentation is important to communicate best practices. Like most systems, we invest a lot in design and development guidelines, but we also visualize our best practices through tools like sample apps and Sketch stencils. Our <a href="https://www.predix-ui.com/#/about/start-designing">Design Starter Kit</a> ships with sample page layouts and relies on symbols to clearly indicate things like preferred configurations, spacing and component functionality. We also supply <a href="https://www.predix-ui.com/#/develop/frameworks-angular">sample code</a> for how to consume the system with various JavaScript frameworks. In addition to shortening the onramp for adoption, these tools frequently end up being a big time saver and productivity booster for teams.</p><p>The goal is to provide people a path of least resistance to adopt the system and get up and going quickly. Maintaining transparency in the design process, encouraging teams to contribute, and providing ways for team to easily consume best practices are a few ways to do that. The more barriers you can remove for adopting the system, the easier it will be to build consistency.</p><h3>Applying the lessons</h3><p>As a design system scales to address more products and use cases, leaning all the way in on consistency becomes challenging. Enforcing too much consistency hinders adoption, while adding too much flexibility can affect the coherence of the system. To find the balance between the two it’s important to look at the shape of your organization, products, and most importantly how people are using the products.</p><p>For more on how we balance consistency and flexibility in the <a href="https://www.predix-ui.com/">Predix Design System</a>, check out my presentation from the UX Pin Design Systems Virtual Summit.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTZnWIqJATU8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTZnWIqJATU8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FTZnWIqJATU8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d17e4819173742a23105e3b8ef8848cc/href">https://medium.com/media/d17e4819173742a23105e3b8ef8848cc/href</a></iframe><p><em>Special thanks to Andrea Perry for her input.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c24cd0a9da16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ge-design/balancing-flexibility-and-consistency-in-design-systems-c24cd0a9da16">Balancing Flexibility and Consistency in Design Systems</a> was originally published in <a href="https://medium.com/ge-design">GE Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Cirrus: The next generation Predix design language]]></title>
            <link>https://medium.com/ge-design/creating-cirrus-the-next-generation-predix-design-language-a6068d30a6f7?source=rss-507f50a34832------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6068d30a6f7</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Ken Skistimas]]></dc:creator>
            <pubDate>Fri, 15 Dec 2017 16:34:07 GMT</pubDate>
            <atom:updated>2018-09-10T19:46:53.208Z</atom:updated>
            <content:encoded><![CDATA[<h4>Evolving our design system with a community-driven approach</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3-NRGQgmGHkcSgJxj299KQ.png" /></figure><p>During the history of GE Digital, there have been <a href="https://www.slideshare.net/davcron/evolution-of-design-systems-at-ge">a few generations of design systems</a>. The current incarnation of the Predix Design System, based on <a href="https://medium.com/ge-design/predix-design-system-components-that-work-everywhere-97b774028b37">reusable web components</a>, was launched about two years ago. At the time, our product suite was smaller and the design system was focused primarily on one product line and some very specific use cases. As GE acquired products, the number of teams building apps increased and so did the requirements and expectations of their customers.</p><p>Common feedback told us that the design system wasn’t flexible and lacked visual impact and appeal. The original design language was created with a very minimal style to suit our main objective at the time: speed of delivery. While it was appropriate at the time, expectations grew for a more refined and diverse design system for our products. The time was right to invest in an overall refresh of the design language for the entire system.</p><p>To measure our success, we outlined a set of goals for the effort:</p><ul><li><strong>Establish</strong> a more visually sophisticated design language</li><li><strong>Increase</strong> <strong>the</strong> <strong>diversity</strong> of design patterns</li><li><strong>Involve</strong> the design community to improve quality and adoption</li><li><strong>Provide better guidance </strong>about how to use the design system.</li></ul><h3>Determining our viewpoint</h3><p>Prior to gathering the broader design community at GE, our core team needed to explain the elements of a good Predix application. Considering our digital-industrial use cases, the businesses goals of our apps, and end user workflows we devised a set of design principles to guide the refresh effort.</p><p><strong>Purposeful<br></strong>Design with a purpose citing context and clear calls to action that allow for fast orientation.</p><p><strong>Efficient<br></strong>Respect a user’s time and workflow.</p><p><strong>Consistent<br></strong>Rely on familiar visual styles and similar interactions for common patterns across the suite of Predix apps.</p><p><strong>Elegant<br></strong>Utilize modern visual and interaction conventions. Find opportunities to create and own innovative ideas.</p><p>These principles gave us a common language to speak about the work we were seeing and a framework to measure the success of existing applications and patterns for the refresh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5tXSf_MTUZa0BLUKCdDklA.png" /><figcaption>Design principles gave us a common language to speak about the work and framework to measure against with the immediate team and the product teams.</figcaption></figure><h3>Connecting with the community</h3><p>Before fully embarking on the refresh, we spoke with numerous designers and product teams about their experiences with the Predix Design System. Over the course of a few weeks, we scheduled informal conversations with stakeholders. We wanted to hear their thoughts about what was working and where we should focus our fixes. The feedback was fairly consistent. In general, they thought the components weren’t flexible for their needs, they wanted apps with visual impact, and they also wanted to know best practices for using the design system.</p><blockquote>For the effort to be successful, we needed to invite teams into the process and give them a voice.</blockquote><p>The previous version of the Predix Design System was built on the use cases and requirements of a single product. As other product teams appeared and applications evolved, a gap emerged. For the refresh to be successful, it was clear that we needed to invite teams into the process and give them a voice. We determined the best way to connect with the community and have them contribute was to conduct a series of workshops. Giving our stakeholders an opportunity to share their use cases, highlight challenges and brainstorm solutions would help us understand the needs of our users, build their investment in the System, and inspire design ideas for a System that would better address the everyone’s needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J2F9O0BiI0dLtc94yGQjVQ.jpeg" /><figcaption>Auditing existing products gave us a baseline for where to focus the workshops.</figcaption></figure><h3>Structuring and running the workshops</h3><p>To determine the focus of the workshops, we needed to better understand the work happening in the GE design community. We asked each team to post their work with annotations on our internal design-sharing site. We then printed out the work and posted it on boards and performed an audit. We catalogued existing patterns and components in framework of our design principles, noted where designers chose to create new components based on use cases, and identified emerging patterns we weren’t addressing.</p><p>We scheduled six workshops, allowing sufficient time for remote teams to travel and attend. In the first session, designers shared their work and spoke about requirements and design decisions. This helped us validate our findings from the audit and update the remaining workshops, while participants could communicate their priorities and compare with design work across the company. The other five workshops were focused on foundational elements of our applications. This included focused sessions on navigation, page layout, color, and materiality as well as data input and data presentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*iJ36FHlWeLP7e7IW14Q10g.png" /><figcaption>Clearly outlining the goals for the workshops was critical for getting the most out of them.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fg3CIEOkwDk4a5VfP9Fkog.jpeg" /><figcaption>Grouping people from different teams together during the workshops was a good catalyst for creativity.</figcaption></figure><p>We structured the design workshops in three-hour blocks to keep attendees focused and respect their time. An agenda was shared beforehand and we prepared a brief introduction and handouts for each session. We arranged the room with tables seating 5–6 people each, and asked people to sit with others than their usual co-workers.</p><p>We wanted to facilitate cross-talk between business units and inform participants of the broad range of requirements the design system needs to support. The time was divided between sharing work, enjoying an activity based on themes that emerged from the sharing session, and discussing output from the activity. Following each workshop, we provided detailed notes and pictures to the entire design community (those present and absent).</p><h3>Defining the language</h3><p>During the course of the workshops, we started to see some trends and common pain points. By the time we wrapped them up, we had a fairly clear idea of the direction we needed to take the design system.</p><p><strong>Color<br></strong>Our products are used in critical environments, where colors have distinct and important meanings, so we were very purposeful with our use of color. In addition, <a href="https://medium.com/ge-design/introducing-ges-data-visualization-framework-for-iot-27c350b02c04">data visualizations</a> are an important aspect of many Predix applications, where some of the most in-depth tasks are performed. It was logical to extend our <a href="https://www.predix-ui.com/#/css/visual/px-colors-design">data visualization color set</a> for more meaningful and expressive charts and graphs; however, we also needed to consider how much color to lend to the foundational interface elements, such as menus, headers, and navigation. Ultimately, based on research from our Healthcare design team, we chose to add more colors to our neutral core palette and shift the tone from warm to cool. This gives a Predix application a personality that augments meaningful color usage within data visualizations and alerts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*_ejewmIj-5Wm3qmN6Ut7sg.png" /><figcaption>The neutral core greys combined with the extended data vis palette allows for expressive charts that scale.</figcaption></figure><p><strong>Materiality<br></strong>The next step was to interpret the objective of a visually sophisticated design language. Because readability of data on our product interfaces is so important, we wanted to keep our data input and presentation patterns clean. We saw the background materials as a good opportunity to add style to the design system. The existing system had a light theme and a dark theme, but we learned during the workshops that the choice didn’t allow much flexibility. For a richer sense of materials, we <a href="https://www.predix-ui.com/#/design/color">combined the themes</a> while extending our foundational cool greys — now a signature element of the System. Unifying the themes doubled our core color palette and gave designers more ability to highlight important information and add visual interest. The palette also allows teams to define a unique style for their app within the Predix color family.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ZDAF8wn5H78vEApWIgh4g.png" /><figcaption>Combining our dark and light themes allows product teams a lot of flexibility in their layouts.</figcaption></figure><p><strong>Animation and layering<br></strong>Predix applications often relate to real-world devices and environments, and we wanted to bring some of that tactile approach to the design language. We created a <a href="https://www.predix-ui.com/#/design/elevation-layering">system for layering</a> user interface elements that adds physicality and reinforces visual hierarchy. Components sit at the bottom of a page, temporary elements, such as drop downs, sit in the middle, and modals and navigation sit atop all. The clear layering helps reinforce hierarchy and priorities during workflows.</p><p>Further building on our principle of elegance, we added motion to transitions. We choose places to add subtle transitions, where they would add to the experience and not hinder the efficiency. This resulted in lightweight animation treatments for navigation menus, panels, and loading spinners that augment the experience and make it more fluid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*hhvr1J-oyL-TgY-_ocvI3A.gif" /><figcaption>Subtle layering of components and transitions bolster hierarchy and add to the overall elegance of the language.</figcaption></figure><p><strong>Iconography<br></strong>The design system had relied on a practical, but not unique, open source icon font for its iconography. As we started applying the existing icons to our new, open, and modern language, we realized the bulky icons did little to help. Additionally, many teams didn’t have optimal metaphors because they were limited by the selection of the icon font. To fulfill the direction of our design language, we created a <a href="https://www.predix-ui.com/#/elements/px-icon-set">custom icon set</a> that would let us address our industrial use cases and easily extend them when necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1xn4DnagmgU9pGDGaIc4Fw.png" /><figcaption>A set of custom SVG icons was important to fulfill our design language. Design guidelines allow teams to extend the set as needed.</figcaption></figure><h3>Implementation</h3><p>Before we committed to writing a line of code, we needed to stress-test our designs in real-world applications. Once we had worked through our initial design ideas, we provided a Sketch file with core components and layouts to allow designers to explore how to translate their apps to the new design language. We invited designers to attend office hours and discuss how the System was scaling for them. This process let us refine the design language easier than if we had jumped right into development, and our steps also let the community create the design language that helps create a shared ownership.</p><blockquote>Before we committed to writing a line of code, it was important to stress-test our designs in real world applications.</blockquote><p>We held monthly stakeholder readouts to recap the progress for designers, product managers, and engineers, to gather feedback on the design direction, and to field questions. In addition to demonstrating the core concepts and visual direction, we were able to show explorations by other teams to illustrate how the system would scale and apply to various applications. This proved a powerful way to visualize the community involvement and communicate the vision for our applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hNZWj_PROJNVrIBLptK25g.png" /><figcaption>A Kanban board was the most productive way to manage progress within our team.</figcaption></figure><p>Once we were confident in our direction, the team went heads-down on implementation. We had to decide whether to release components in-progress or when all were ready. Typically, our team prefers continuous integration, but since this would be a breaking change, we chose to keep components in-progress behind a prerelease tag in GitHub. Having started the design process in January, we competed the huge effort and succeeded to ship the General Availability code in July.</p><p><strong>Stats:</strong></p><ul><li><strong>117</strong><a href="https://github.com/search?q=topic%3Apredix-ui+org%3APredixDev&amp;type=Repositories"> <strong>GitHub repos</strong> </a>included in the release</li><li><strong>3,578</strong> <strong>commits</strong> to those repos</li><li><strong>116 days </strong>of<strong> </strong>development time, for an average of 31 commits per day</li><li><strong>3484 automated unit tests</strong> for our Web Components, which we run against 6 browsers</li></ul><h3>Introducing Cirrus</h3><p>The result of this community-driven approach is our new visual language named Cirrus. The name suggests the thin, wispy clouds of the upper atmosphere, and reflects the “lightness” of the visual and interaction language improvements. The system is flexible to support the variety of our product use cases while still recognizable as Predix.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F247015395&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F247015395&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F672143295_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/35b41430e4b8be3416becc624894420d/href">https://medium.com/media/35b41430e4b8be3416becc624894420d/href</a></iframe><h3>Guidance and adoption</h3><p>Shipping the updated components was only the start. Prior to the update, the components and design guidelines had separate locations for designers and developers to adhere to best practices. If you knew about the component library, it was likely you had never seen the design guidance. Based on the output from the workshops and input from the community, we created a fresh set of guidelines for our new design language. With teams spread all over the world, we need to keep our all our documentation and guidance in one place. So, we built out a new section on <a href="https://www.predix-ui.com/">predix-ui.com</a> to serve <a href="https://www.predix-ui.com/#/design/navigation">design</a> and <a href="http://develop/">development</a> guidelines.</p><p>Published guidelines are helpful, but to be fully effective, our work needed to become part of a designer’s workflow. The previous iteration of our design stencil was built in Adobe Illustrator, and allowed some freedom, but didn’t provide much guidance on the functionality of components. The design stencil also allowed designers unfamiliar with the design system to easily veer away from available functionality in the components and inadvertently cause more development work for their teams. This created much friction for the product teams and confusion concerning what our components actually provided.</p><p>To avoid this, we built a completely <a href="https://www.predix-ui.com/#/about/start-designing">new Sketch stencil</a> relying on symbols to maintain parity with the functionality of the components. The symbols allow us to put rails on the customization and show designers how components work without entirely relying on the component catalog. The new stencil has been highly effective in boosting the productivity of designers as well as making their designs accurate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*iFyvHVczWL4ZK4LMaDLdpw.gif" /><figcaption>Utilizing symbols in Sketch allows us to bring component functionality and guidance to the designer’s workspace.</figcaption></figure><p>Additionally, we doubled down on our <a href="https://www.predix-ui.com/#/about/introduction">on-boarding material</a> on the site to clarify how to get started with the design system. As for the design guidelines, much of the material existed but was scattered. Sometimes showing is better than telling, so we created a <a href="https://www.predix-ui.com/px-sample-app/">sample app </a>to illustrate how basic constructs like navigation, data visualization, and forms should work within an application.</p><h3>Takeaways</h3><p>Our design language is modern and elegant, the components and design patterns are more flexible, we’ve cultivated a great community through workshops, design office hours and other channels, and guidance for designers and developers is more robust. We’re able to ship a better product and have advocates when we involve the community in the design process. See how it all comes together at <a href="https://www.predix-ui.com/">Predix-UI.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6068d30a6f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ge-design/creating-cirrus-the-next-generation-predix-design-language-a6068d30a6f7">Creating Cirrus: The next generation Predix design language</a> was originally published in <a href="https://medium.com/ge-design">GE Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Holding Off on High Fidelity]]></title>
            <link>https://medium.com/salesforce-ux/holding-off-on-high-fidelity-273d2232a99c?source=rss-507f50a34832------2</link>
            <guid isPermaLink="false">https://medium.com/p/273d2232a99c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Ken Skistimas]]></dc:creator>
            <pubDate>Wed, 02 Dec 2015 20:00:48 GMT</pubDate>
            <atom:updated>2015-12-04T23:05:35.387Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lJh0yLwuRY1cLvp3B4GLUg.jpeg" /></figure><h4>How sketching can improve your design process</h4><p>Growing up, my father was an illustrator. Sketching and drawing was part of our household. The recognizable squeak of a Xylene Design marker on a Graphics 360 pad is a fond childhood memory of mine. As I grew up, the times in which I broke out an actual pen and paper became less frequent. Now with UI kits, symbol libraries, and a plethora of other electronic tools it’s easy to jump right to high-fidelity mockups.</p><p>Over the last few years, I’ve frequently used variations on the <a href="http://www.gv.com/sprint/">Design Sprint</a> to get projects rolling.<em> </em>It’s been a fantastic reminder of the value of working in low fidelity — ideating quickly, provoking the right questions, and collaborating early and often with stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pqTTHZ2EOr2Fhx_N-eBAwg.png" /><figcaption>The bigger the mess, the greater the progress!</figcaption></figure><h4>Putting Pen to Paper</h4><p>It’s great to start a project off with sketches because it’s easy to include anyone from the team. Everyone knows how to put pen to paper, and while the initial sketches can be done independently, there can be a ton of value in teaming up a designer with a product owner or a developer in this process. I’ve recently used this technique when designing a user flow for an upcoming product release.</p><h4>Sketching a User Flow</h4><p>Start with a narrative or a user journey to map out the user’s key objectives. As you sketch the screens a user would interact with, post them on a board or a wall and create a storyboard. Too often the focus is on the details and it can be easy to forget the bigger picture. The board gives you a substantial visual artifact that your team can rally around and react to.</p><p>Gather the team to talk through the flow. It’s especially important to have representatives from product and engineering included in the sketching stages for a few reasons. It gets people thinking in flows rather than screens and it gives team members an early point to provide feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*duKRs4WQn6J_w61Q_kJ11g.png" /><figcaption>Post your sketches in a public place so it’s easy for stakeholders and team members to annotate.</figcaption></figure><h4>Focusing on the Right Questions</h4><p>A low fidelity sketch invokes a particular level of feedback that focuses on fundamental UX choices that set the direction for the rest of the project. In a recent review, our conversation addressed our target user’s needs, the complexity of the flow, and the overall interaction model, which is critical to get right before investing in higher fidelity.</p><blockquote>A pixel-perfect mockup has an implied finality that doesn’t exist with a marker sketch.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ut7V2hkqPgdqfoqf3SSSrA.png" /><figcaption>Sketches don’t have to be pretty to communicate.</figcaption></figure><p>There’s very little cost to trying out a new idea on the fly in response to feedback. Anyone can quickly add a new sketch, patch over an existing one, flip the order around or entirely remove a step. The feedback cycle can be shortened to a matter of minutes as opposed to hours or days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PnX1Fx407xX1ENCT67xx7Q.jpeg" /><figcaption>Call out your persona or target user and annotate each sketch for context.</figcaption></figure><h4>Moving to Higher Fidelity</h4><p>While it would be easy to declare a recommended length to stay in sketches, it’s different for every project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dgqkjg0Rmn-15oSvef8rFg.jpeg" /><figcaption>The evolution of a storyboard from analog to digital.</figcaption></figure><p>The conversion to high fidelity often happens a few screens at a time rather than all at once. To help with the transition, scan the sketches and create a Google Slides document replicating the flow. Be sure to give access to editing and commenting as it continues the collaborative and live nature of the physical storyboard. As screens are completed, swap in the mockups for the sketches. Print the mockups and update the physical storyboard until all collaboration has transferred to Google Slides.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HGL-GtZpZIJUFZIkSS5viQ.png" /><figcaption>Whether it’s a physical storyboard or a Google Slides doc, retaining a revision history by stacking screens on top of each other is helpful.</figcaption></figure><h4>Make It Your Own</h4><p>While designing, it’s important to remember that not everything needs to be perfect. The next time you eagerly launch Sketch or Illustrator ready to work up a new flow, consider stepping back and picking up a marker instead.</p><p><em>Follow us at </em><a href="http://twitter.com/salesforceux"><em>@SalesforceUX</em></a><em>.<br>Want to work with us? Contact </em><a href="/service/mailto:uxcareers@salesforce.com"><em>uxcareers@salesforce.com</em></a><em><br>Check out the </em><a href="http://salesforce.com/designsystem"><em>Salesforce Lightning Design System</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=273d2232a99c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-ux/holding-off-on-high-fidelity-273d2232a99c">Holding Off on High Fidelity</a> was originally published in <a href="https://medium.com/salesforce-ux">Salesforce Designer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[People-Powered Design]]></title>
            <link>https://medium.com/salesforce-ux/people-powered-design-371a6d180d2e?source=rss-507f50a34832------2</link>
            <guid isPermaLink="false">https://medium.com/p/371a6d180d2e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ken Skistimas]]></dc:creator>
            <pubDate>Tue, 06 Oct 2015 19:12:46 GMT</pubDate>
            <atom:updated>2015-12-18T18:21:44.485Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Dreamforce brought design face-to-face with our customers</h4><p>The dust has settled on my third <a href="http://www.salesforce.com/dreamforce/DF15/">Dreamforce</a> as a UX designer at Salesforce, and there’s no doubt that it was one of those moments in my career that I’ll never forget. For those unfamiliar, Dreamforce is Salesforce’s annual event where we showcase products from our five clouds, people get together to learn and network and Salesforce shares a vision for the future of technology as it relates to business. This year there were over 170,000 registered attendees.</p><p>What made this year unique is that design has been recognized as a differentiating factor and elevated to the forefront as a critical element of making customers more successful. Commitment to creating great experiences for our users resulted in the launch of two very significant design-centric projects — the <a href="https://medium.com/salesforce-ux/how-we-designed-the-new-salesforce-at-scale-6d3607fd92e5">Lightning Experience</a> and the <a href="https://www.lightningdesignsystem.com/">Lightning Design System</a>. Dreamforce was our first opportunity to show our work to the world and gather first reactions from individuals who depend on our products every day.</p><h3>Step Right Up</h3><p>This year at Dreamforce we created the Design HQ — a place to feature our work and share the importance of design. Located in the heart of Moscone Center, it became an integral part of an attendee’s experience. Tens of thousands of customers came through the HQ interested in what we had to offer and explore the future of Salesforce.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8W7DOnd5BNk%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8W7DOnd5BNk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8W7DOnd5BNk%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bdbdc86ea26ced457f935d6a5ea9297d/href">https://medium.com/media/bdbdc86ea26ced457f935d6a5ea9297d/href</a></iframe><p>A lot of my time was spent here demoing. We focused on the new Lightning Experience and the Lightning Design System. The <a href="https://www.salesforce.com/blog/2015/08/future-of-crm-salesforce-lightning.html">Lightning Experience</a> is a newly reimagined user experience for our core sales product. The <a href="https://www.lightningdesignsystem.com/">Design System</a> is a living style guide for developers and designers.</p><p>As a designer, demoing required me to focus on what’s important to our customers. This is something that I expected would be really easy. After all, this was a product I’ve been intimately involved with for the last 9 months. After my first few attempts, I found myself tongue-tied and struggling to tell a coherent story. I realized that I was too focused on the details and started reframing the demo around our customer’s workflows and use cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*iH79GPks8f8VJLE57tC1MQ.jpeg" /><figcaption>Yours truly demoing to customers. You will talk — a lot. Bring water.</figcaption></figure><p>When I began to speak directly to customers needs, the interaction became much more engaging. I fielded all kinds of questions I never expected and the demo became a discussion. I was humbled by the deep knowledge our customers had about Salesforce and was able to better empathize with what they expect from new Lightning Experience. As a designer, it really drove home how valuable it is to have direct contact with the people that use your product. I fostered a deeper connection with our users and I was reminded of what’s really important to them.</p><h3>Getting Personal</h3><p>While being in the spotlight was fun and rewarding, I was curious how our work was being received in the wild. There were many places in the conference where attendees could directly interact with Lightning Experience, one of which was the Sales Cloud Expo. This area focused squarely on the customer workflows I demoed, so it was a great opportunity to do some lightweight usability testing.</p><p>The Expo had individual stations for particular tasks such as logging a call, taking notes and moving a deal forward — all common tasks for a sales rep that happen to map well to individual features. I spent some time quietly and intently observing at each station as people got their introduction to the new UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GrcsYDFb54pg3omVOfEbtg.png" /><figcaption>Looking over the shoulder of an attendee getting an introduction to Lightning.</figcaption></figure><p>It was exciting and nerve-wracking to watch people jump in with little more context than the task they were assigned to complete. I was anxious to jump in at times, but I had to remind myself that it was analogous to most people’s real world experience. The anticipation of watching an attendee peruse the screen practically had my stomach in knots, but that was followed by a great sense of elation when they completed the task.</p><p>At the end of the session, I took the opportunity to introduce myself as a designer and asked for their feedback. I asked participants to tell me about their job and what a successful day was like. Those conversations gave me some deep personal insights into what drives and motivates our customers.</p><h3>Recognizing the impact</h3><p>As I walked around the conference surrounded by thousands of people who use our products, I recognized the scale at which we work as Salesforce designers and the effect of our technology. Dreamforce gives our customers a vision for the future and focuses on the tech, yet at the end of the day I found that it’s all about the people. Meeting a variety of customers allowed me to build greater empathy for their use cases and understand how our products are used in the real world.</p><p>I realize that Dreamforce is unique as a venue to share designs and interact with users, but what I learned here can be applicable to any designer. When meeting with customers or users, step back from the details and focus on your their needs and workflows, find time to make a personal connection, and seek opportunities to observe your designs in the wild. It was exciting to see how design has taken a front seat this year at Dreamforce and I’m looking forward to seeing how this momentum brings us into the next year.</p><p><em>Special thanks to </em><a href="https://medium.com/@icschoen"><em>Ian Schoen</em></a><em> for his help on this post.</em></p><p><em>Follow us at </em><a href="http://twitter.com/salesforceux"><em>@SalesforceUX</em></a><em>.<br>Want to work with us? Contact </em><a href="/service/mailto:uxcareers@salesforce.com"><em>uxcareers@salesforce.com</em></a><em><br>Check out the </em><a href="http://salesforce.com/designsystem"><em>Salesforce Lightning Design System</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=371a6d180d2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-ux/people-powered-design-371a6d180d2e">People-Powered Design</a> was originally published in <a href="https://medium.com/salesforce-ux">Salesforce Designer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>