<?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 Bethany Sonefeld on Medium]]></title>
        <description><![CDATA[Stories by Bethany Sonefeld on Medium]]></description>
        <link>https://medium.com/@bsonefeld?source=rss-8e8536800f66------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RI9b6Kk9wEOnk9-wBUYsfg.jpeg</url>
            <title>Stories by Bethany Sonefeld on Medium</title>
            <link>https://medium.com/@bsonefeld?source=rss-8e8536800f66------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:03:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bsonefeld/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[Remaining productive when your world is on fire]]></title>
            <link>https://medium.com/@bsonefeld/remaining-productive-when-your-world-is-on-fire-a6bf08a461c4?source=rss-8e8536800f66------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6bf08a461c4</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Bethany Sonefeld]]></dc:creator>
            <pubDate>Tue, 05 Dec 2017 15:31:01 GMT</pubDate>
            <atom:updated>2017-12-05T15:31:01.321Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s face it, in today’s world full of distractions, it can be difficult to be productive. There are books, blogs, podcasts, and tools telling us how to be productive in different facets of our lives. Turn off distractions, go for a walk, plan out your day, they say. We rely on experts to tell us what to do in our day to day instead of trusting ourselves. Why is it that we find it so hard to tap into the inner workings of our brain and just <em>focus?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0E0zzp2BNUaT0q7lnUQdw.png" /><figcaption>Let’s trust the woman with 4 arms to tell us how to be productive.</figcaption></figure><p>I put the blame on the advancement of technology and the rise of multitasking. Technology has programmed us to multitask, always wanting to accomplish the most amount of things in the shortest amount of time. We wear productivity as a badge of honor. Think about the different contexts of your life where you can be productive. At work, we feel great when we accomplish a lot within an 8 hour day. At home, we run errands on a Saturday to feel productive instead of like lazy bums.</p><p>Productivity looks different on everyone. It can mean being efficient. It can mean feeling good about something you’ve accomplished.</p><p>I used to think productivity meant working long hours and hustling to get done what you needed to. Since I was young, I’ve always been a self-motivated and productive individual. Working two jobs throughout high school and college pretty much programmed me to be as efficient as possible. Could I squeeze in a three-hour lifeguarding shift after my seven-hour workday at the bakery? Sure, I’ll just bring a change of clothes and eat dinner in my car. Keeping busy was what made me happy, where I was hustling to make something of myself. This mentality continued on to my professional life. I loved getting to the office early, slipping on my headphones, and getting time to focus. I took on freelance and side projects that occupied most of my nights.</p><p>This lifestyle came to a screeching halt when earlier this year, I experienced some pretty drastic health issues. I had no choice but to rest (literally, doctor’s orders). People who know me understand that this order didn’t sit well with me. I don’t enjoy binge watching shows, I can’t seem to sit for over an hour, and I have to do something active at least once a day. During the time when I was sick, I couldn’t do anything but rest and take it easy. Despite my efforts to try and get back into my routine, mentally and physically I was exhausted. I classify this as the least productive phase in my life.</p><p>The thing is, you don’t realize how fast life moves until you’re forced to slow down. Once I was actually able to go back to work, things felt different. I wasn’t my normal “busy-bee” self — I had little to no motivation and some days it was tough just getting out of bed. My productivity levels tanked and I had no clue how to fix it. I tried listening to podcasts, reading motivational books, and even taking a solo vacation to clear my head.</p><p>One day, I stumbled across the notebook that I had written my personal, career, and financial goals for 2017 in. Rereading them forced me to reflect on the person I envisioned I would become. My health issues put a kink in these goals, and I couldn’t help but be disappointed and frustrated with myself. I finally realized that the only person we can really count on to motivate us is our own self. This whole time, I should have been listening to myself, my body, and do what felt right for me.</p><p>Slowly, I’m beginning to feel like myself again. I view productivity in a different light, for fear of burning myself out again. Now, I’ve been making a strong effort to slow down, focus on one task, and listen to my own needs. Multitasking can actually hurt our levels of productivity. You’ll get things accomplished faster if you just take the time to sit down and focus on one thing. Working smarter, not harder is my new mantra. Let’s hope this one leads to a more sustainable lifestyle.</p><p><a href="http://bethanysonefeld.com/"><em>Bethany Sonefeld</em></a><em> is a Design Lead and UX Designer at IBM Design, based in Austin. The above article is personal and does not necessarily represent IBM’s positions, strategies or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6bf08a461c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing: Carbon Themes]]></title>
            <link>https://medium.com/design-ibm/introducing-carbon-themes-83d3985a8627?source=rss-8e8536800f66------2</link>
            <guid isPermaLink="false">https://medium.com/p/83d3985a8627</guid>
            <category><![CDATA[scss]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[ibm-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[themes]]></category>
            <dc:creator><![CDATA[Bethany Sonefeld]]></dc:creator>
            <pubDate>Fri, 11 Aug 2017 14:55:44 GMT</pubDate>
            <atom:updated>2017-08-11T20:22:39.808Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The Carbon Design System is a series of individual styles and components that can be used to design and build experiences for IBM Cloud products.</em></p><p>Carbon Themes gives developers and designers the ability to customize components within the Carbon Design System. Each teams’ “theme sheet” includes SCSS variables that modify Carbon Components to fit their specific style. These variables range from color, to border-radius, to margin or padding.</p><p>While Carbon was initially built for IBM Bluemix, teams have been asking for an elegant way to customize Carbon for their respective products. The challenge for the Carbon team was updating a few key elements of the system to make theming adoptable — beginning with our color palette.</p><h3>Color naming system</h3><p>We rebuilt Carbon’s color palette as a set variables. This means that each team can change their palette at a global level to customize the components to their liking. We wanted a naming system that was flexible enough to scale across themes but also hint at the colors’ purpose. Pulling in inspiration from Bootstrap and Base16, we decided on abstracting our naming system for colors.</p><p>Each color variable consists of a role (brand, text, UI) and a unique number (01, 02, 03). The role is based on the color’s purpose within the UI, while the unique number is used for that color’s specific role within that area. For example, text-01 is used for the primary text color on the page, while text-02 is used for secondary text.</p><p>With this new naming system, we began to be more thoughtful about how color was used within Carbon Components. We identified specific things as core brand elements, such as links and other interactive elements, and mapped the components to our brand-01 color variable. Refactoring the components to include these updated color variables made theming readily available to product teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vfG7Udjy6-Ulyuei0dtTRw.png" /><figcaption>The brand-01 color variable can affect various components.</figcaption></figure><h3>Carbon Theming sandbox</h3><p>We wanted to give designers and developers a quick way to experiment with color variables and understand how they effect a component. The <a href="http://themes.carbondesignsystem.com/">sandbox</a> allows you to build a custom theme by changing a color variable’s value and then exporting the theme sheet SCSS file. Users can also filter per component, to see as many or as few within the page view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FYPbMj_OzNmojAKAhx4Jvw.png" /></figure><h3>Building out additional themes</h3><p>Our goal is to expand and scale Carbon Components to fit the needs of other teams within IBM. The idea that other products are interested in using Carbon as their component library is exciting for our team, and we’re here to support them in any way we can. Moving forward, we plan to add more variables such as text styling and stroke weight to further customize and build out additional themes.</p><p>To explore themes and experiment with colors, check out our Carbon Themes<strong> </strong><a href="http://themes.carbondesignsystem.com/">sandbox</a>.<strong> </strong>We would love to see some themes you’ve built using Carbon Components, so send us a tweet of something you’ve made!</p><p><em>Bethany Sonefeld is a Design Lead and UX Designer at IBM Design based in Austin. The above article is personal and does not necessarily represent IBM’s positions, strategies or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83d3985a8627" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/introducing-carbon-themes-83d3985a8627">Introducing: Carbon Themes</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Carbon: Designing inside Big Blue]]></title>
            <link>https://medium.com/design-ibm/carbon-designing-inside-big-blue-8577883cfe42?source=rss-8e8536800f66------2</link>
            <guid isPermaLink="false">https://medium.com/p/8577883cfe42</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Bethany Sonefeld]]></dc:creator>
            <pubDate>Thu, 30 Mar 2017 15:02:00 GMT</pubDate>
            <atom:updated>2017-03-31T00:33:59.847Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hxal4RqFNlNzN-3joW_DSg.png" /></figure><p>Carbon is the design system for my product team at IBM Bluemix. A design system contains components that can be combined and reused to build user interfaces. It enables teams to focus on how a user interacts and converses with a piece of software, rather than arguing over what color a button should be.</p><p>At IBM, we’re in a unique situation of size. IBM as a company has over 2,000 products, and different experiences should look and feel like IBM across the board — scale is our primary challenge. At the corporate level, the <a href="http://www.ibm.com/design/language">IBM Design Language</a> provides guidance on how to communicate IBM’s brand promise and creates a basic framework for how all IBM products should look and feel (with assets like a sweeping color palette and iconography), but doesn’t dive deep into how that translates into product interface itself. The challenge for my team was taking that framework, and crafting a system for Bluemix itself that fit with the parent IBM brand, but could also scale across many Bluemix sub-products as well.</p><h3><strong>Growing pains</strong></h3><p>When IBM Bluemix debuted in June 2014, it launched with only basic functionality — essentially, it was an easy way to host an application on the web. Two and a half years later, Bluemix is now comprised of over a 130 different services that users can use and integrate to power their applications. Bluemix now also lets users spin up different infrastructure elements, such as Containers and Virtual Machines.</p><p>While the feature set grew in leaps and bounds, the UI didn’t age as well. Until February 2016, the original interface only went through minor iterations and consequently looked old, tired, and inconsistent. To exacerbate the consistency issue, large swathes of the UI are owned and designed by the individual services themselves. These service teams range from a fully functional cross-discipline team, to just a few developers and a project manager. Over 50 designers were working on the product, and yet only a two page style guide existed as a single source of truth.</p><p>In short, we needed a design system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fA2KSw-6WDedXifO5xR52Q.png" /><figcaption><em>IBM Bluemix (June 2014, February 2016, March 2017)</em></figcaption></figure><h3><strong>Building out the system</strong></h3><p>Our first step was formalizing a Design System team. From the very beginning, we set out with two main goals — one, the system should work for both designers and engineers, and two, the system must be easily adoptable by teams.</p><h4><strong>Creating trust</strong></h4><p>A key facet to accomplish these core goals was establishing trust with our different service teams. Engineers and designers can rely on the fact that any component within the Design System is backed by research, visual consideration, accessibility, and UX guidance. For engineers, there were two main things we did to build trust: first, we semantically versioned the Design System. Engineers knew that we treated the system like a product, and would not haphazardly push breaking changes. And second, we distributed the codebase through industry standard channels (npm and bower) — we wanted to create an environment where developers already felt comfortable working in. There was a large emphasis on blanketing our codebase with tests — as if it were a product itself — to ensure that anything we shipped was production-ready. For designers, we finally had a single source of truth for UI patterns, so there were fewer questions about correct color usage or sizing.</p><h4><strong>Accessibility</strong></h4><p>Accessibility was and is a top priority within the Design System. Each component and element was built following the <a href="https://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines</a> (WCAG) and met the AA standard. Our patterns are perceivable, operable, and understandable to users, even when using a screen reader or other assistive technology. An example of this is running color contrast tests on our UI patterns to ensure they are accessible to low-vision users, or testing keyboard navigation to verify the tab index is presented in a logical order. These are just a few measures we take to design with accessibility in mind.</p><h4><strong>Documentation</strong></h4><p>We couldn’t make assumptions about our users level of knowledge, so our documentation covers everything from getting started to detailed usage guidelines. Our hope is to enable individuals with no design background to understand when and how to use the patterns in our system. A developer or project manager, for example, should be able to learn when to use a checkbox versus a radio button. Good documentation allows us to properly communicate with our service teams, which has been crucial for adoption.</p><h3><strong>Introducing, Carbon</strong></h3><p>We gave the design system the name Carbon, because in nature it builds complex structures from simpler compounds. This motif mimics how our individual styles and components can combine to make beautifully complex, natural, and intuitive designs.</p><p>Initially, it was challenging to deploy Carbon across Bluemix, due to the amount of legacy code in the product coupled with development teams’ unfamiliarity with sharing a UI library versus just creating a component themselves.</p><p>Much of the success of the system lies in the hands of those who adopt and use it. Although Bluemix has a team dedicated to building and maintaining Carbon, we have many others that contribute code, design patterns, and provide general feedback.</p><h3><strong>A new era</strong></h3><p>It’s very common for the Carbon team to hear the need for additional patterns or components. And that’s where the beauty lies within a system — in its ability to scale and grow to accommodate the needs of those using it. Running on a continuous delivery model, the system will never be “done” or “finished.” The Carbon Design System surely isn’t perfect, but we didn’t build it to be. I have confidence in knowing what we’re building will be an essential piece to our design and development process, and the growth of the platform. It’s an exciting time for IBM and for Bluemix, and I’m lucky enough to be a part of it.</p><p>Check out the <a href="http://carbondesignsystem.com/">Carbon Design System</a> and let us know your thoughts!</p><p><em>Bethany Sonefeld is a Design Lead and UX Designer at IBM Design based in Austin. The above article is personal and does not necessarily represent IBM’s positions, strategies or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8577883cfe42" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/carbon-designing-inside-big-blue-8577883cfe42">Carbon: Designing inside Big Blue</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>