<?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 Jessica Schilling on Medium]]></title>
        <description><![CDATA[Stories by Jessica Schilling on Medium]]></description>
        <link>https://medium.com/@jessicaschilling?source=rss-dbf8b945911c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UV1KbmNZAzLt7T1krY8RNQ.jpeg</url>
            <title>Stories by Jessica Schilling on Medium</title>
            <link>https://medium.com/@jessicaschilling?source=rss-dbf8b945911c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:04:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jessicaschilling/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[Design Systems at Startup Scale: Yes, Please!]]></title>
            <link>https://medium.com/solaria-labs-blog/design-systems-at-startup-scale-yes-please-dc9c35529f99?source=rss-dbf8b945911c------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc9c35529f99</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[invision]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[atomic-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jessica Schilling]]></dc:creator>
            <pubDate>Mon, 24 Sep 2018 19:53:40 GMT</pubDate>
            <atom:updated>2018-09-24T19:53:40.532Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by </em><a href="https://medium.com/u/dbf8b945911c"><em>Jessica Schilling</em></a><em> and </em><a href="https://medium.com/u/239635a94454"><em>Katherine Brandy</em></a><em> — August 20, 2018</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wntvFxvokt01R-Rv17mv6g.jpeg" /><figcaption>Jessica (left) and Kate (right) showing off an enormous Solaria Labs design pattern</figcaption></figure><p>As <strong>designers</strong>, we know the importance of well-crafted visual patterns. As <strong>UX practitioners</strong>, we know consistency is critical. As <strong>front-end developers</strong>, we know how much easier atomic design makes our lives. But as team members in a small business or startup … it’s often too easy to let these fall to the wayside in our rush to get stuff deployed. That’s where <strong>design systems</strong> come in. At first glance, particularly in an Agile shop, this might seem counterintuitive: Why would you devote time to documenting design for something that’s in constant flux? <strong>As the user experience team at </strong><a href="http://www.solarialabs.com/"><strong>Solaria Labs</strong></a>, the innovation incubator at Liberty Mutual Insurance, we understand this well: We’re a small team in a lab that’s essentially a group of small, timeboxed startups. But since our incubator is part of our much larger parent company, we’re also well versed in the speed and efficiency that comes with a well-built design system. As the lab’s UX team, we really wanted the best of both worlds: on-the-fly generation of design patterns to serve us in the long run, but not cramp our Agile style.</p><p>In true test-and-learn fashion, we decided to try this out on the Solaria brand itself, creating <a href="https://solarialabs.invisionapp.com/dsm/solaria-labs-liberty-mutual/solaria-brand-guide"><strong>a public-facing Solaria Labs stylebook</strong></a> using InVision’s new <a href="https://www.invisionapp.com/design-system-manager/">Design System Manager</a>. The Solaria visual identity is pretty straightforward, but as a UX team, we’re always re-explaining and enforcing it with an ever-changing roster of interns, staff from Liberty Mutual’s home office joining us for temporary innovation placements, and new lab employees. Creating a lab brand book gave us an opportunity not only to prove that small-scale design systems are valuable for other lab projects, but also to make sure our people always have access to correct, consistent Solaria assets. Plus, we had a lab-wide, two-day hackathon on our schedules — a perfect opportunity to give the project a go. <strong>Here’s a run-down on how it went from product designer Kate Brandy and myself (senior product designer Jessica Schilling).</strong></p><h3><strong>What we did</strong></h3><p><strong><em>Jessica:</em></strong> We built an entire design system in less than 24 hours — impressive, right? Joking aside, we <em>did</em> spin up the lab’s design system in two working days, but in the spirit of Agile, it definitely wasn’t intended to be perfect the first time around. This project was about creating a lab style guide, but it was just as much about proof-testing how we might build and maintain design systems for our other projects and products as they — and our lab as a whole — grow.</p><p><strong><em>Kate:</em></strong><em> </em>This was also a great opportunity to create a public-facing resource— an externally visible brand book — that could act as a window into how we work as a lab. The challenges that came with balancing what should be publicly accessible and what needed to be protected also brought a lot of interesting considerations into play that we’ll be able to utilize for future projects.</p><h3><strong>Why we did it</strong></h3><p><strong><em>Kate:</em></strong> One reason we decided to use the Solaria brand for our prototype design system was scalability, both for our UX team and the lab at large. We’ve been a staff of two for the last year, but we’ve just added a third team member and are expanding further in the next few months. It’s fine to keep track of logos, colors and other assets in an ad-hoc way when there are only two of you, but add even one more person and things get confusing.</p><p><strong><em>Jessica:</em></strong> Plus, there’s always a steady stream of interns or innovation-placement staff from home office needing lab-branded artifacts like logos, official icons/colors, and document templates … followed by a new batch of people a few months later. We needed a way for these folks to easily get hold of what they needed in a way that didn’t involve a ton of intervention on the UX team’s part.</p><p><strong><em>Kate:</em></strong> And also, as as the lab grew in size, we realized we really needed to set aside some time to devote our attention to the Solaria style and brand as a whole — to get together as a UX team, talk through what we liked and what didn’t work so well, and get everything down in words and artifacts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*XF1XEIcxiqCbDqZXeFaVig.gif" /></figure><h3><strong>What tools we chose</strong></h3><p><strong><em>Kate:</em></strong> After a lot of exploration, we landed on a combination of InVision’s Design System Manager for public-facing materials and our internal Confluence instance for protected assets. Why? While it was important to us to keep the bulk of our design system publicly visible — the lab is really committed to transparency — we realized that some items really did need to be kept behind a login.</p><p><strong><em>Jessica:</em></strong><em> </em>We realize that this project only scratches the surface of what DSM can do — particularly in terms of automatically-generated code and SCSS samples — but that said, we know from this exercise how simple it is to use DSM’s code generation capabilities for other, more web-style-intensive projects, and we’re looking forward to making the most of that as requirements dictate. As a lab, we’ve really been focusing on how our UX team can expand our own coding skill sets and just work more collaboratively with developers in general, which naturally leads to everyone focusing more on working under <a href="http://atomicdesign.bradfrost.com/">atomic design principles</a>. It’s a great way for each of us to learn bite-sized pieces of each other’s specialties, and to have a common mental model when starting from scratch on new projects. And since our team all uses Sketch in generating assets for new projects, DSM’s integration with <a href="https://labs.invisionapp.com/craft#library">Craft</a> makes for an ideal tool for translating design into usable code.</p><h3><strong>How we did it</strong></h3><p><strong><em>Jessica:</em></strong><em> </em>We knew we only had two days to devote to this project, so we started with an asset inventory of all things Solaria Labs: our website, document templates, logos/icons, print artifacts, social profiles, etc. Then we took the opportunity to examine each item, standardize things like colors, fonts, and visual patterns, and discuss and change the things we noticed weren’t working so well in the field.</p><p><strong><em>Kate: </em></strong>This actually took the bulk of our two-day timebox, and it was the real collaborative work: honest talk about what we already had, making decisions as a team, and thinking in an architectural, scalable manner — even down to making sure our house fonts worked for our team members who were using older Windows PCs. Until now, we hadn’t had the opportunity to have these discussions, so we wanted to spend as much of our available time on that as possible.</p><p><strong><em>Jessica: </em></strong>And that’s why DSM ended up being such an awesome tool — we could spend more time actually making artifacts and standards and less time cataloguing them, because using DSM means the catalog is largely auto-generated. We still had to give careful consideration to balancing what items could be publicly available and what needed to be protected — basically, our rule of thumb was “could someone use this item to impersonate or otherwise harm us?” — but once we assembled all our artifacts, we dropped them either into DSM or Confluence, and annotated with usage guidelines. This process only took us about half a day!</p><p><strong><em>Kate:</em></strong> Then came the best part: socializing the new design patterns with the rest of the lab staff. Everyone loves a contest, so we challenged the team to update their email signatures with the new standard, and send us a note as proof. The winner received a sweet model DeLorean (actually, it was a re-gift of our own prize for being the winner of the lab hackathon!). And who wouldn’t want a DeLorean, even a toy-sized one?</p><h3><strong>What we liked, what we didn’t</strong></h3><p><strong><em>Kate:</em></strong> One of the goals of this exercise was to proof-test the Sketch/Craft/DSM workflow for generating design patterns on the fly, and we weren’t disappointed; the seamless integration of these tools made working a breeze. Plus, on the human side, it really enabled collaboration: Our UX team was able to work together, talking in the same room, but simultaneously working on different pieces of the project on our laptops.</p><p><strong><em>Jessica:</em></strong> Having less implementation stuff to worry about made for an unexpected teambuilding opportunity, too! The speed at which we were able to work meant we were able to take the time to have the really valuable human discussions. (I remember the “old days” when manually documenting a design system took months!) The only real stumbling block was setting up a combination of publicly and privately accessible resources in a way that was the least disruptive or confusing to the lab at large. Ideally, we’d like to password-protect artifacts from within DSM — InVision, if you’re reading, what do you think about getting this in your backlog?</p><p><strong><em>Kate:</em> </strong>We’re really looking forward to having this in the wild for a little while and gathering some feedback about how it could be easier for the lab to use. Plus, we’re also excited about building out another DSM instance for something that starts with a website (such as our <a href="http://www.trydwellbeing.com/">Dwellbeing</a> home-maintenance platform), rather than starting from off-Web assets, which is more the case with the Solaria brand.</p><h3><strong>What can you learn from our project?</strong></h3><p><strong><em>Jessica</em></strong><em>:</em> A design system is never overkill! Even if you’re a two-person design team — or a two-person company — making decisions about brand identity and implementation patterns early on can make things a whole lot easier as you scale. If nothing else, you don’t have to end up asking your whole team to change their email signatures!</p><p><strong><em>Kate:</em></strong> Consistency in how you present yourself is one of the most underrated — but most straightforward— ways to boost your brand. Never underestimate how consistent branding, visual design and language patterns can build trust, elevate your company’s message, and reach more customers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc9c35529f99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solaria-labs-blog/design-systems-at-startup-scale-yes-please-dc9c35529f99">Design Systems at Startup Scale: Yes, Please!</a> was originally published in <a href="https://medium.com/solaria-labs-blog">Solaria Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solaria Labs User Experience Principles]]></title>
            <link>https://medium.com/solaria-labs-blog/solaria-labs-user-experience-principles-b2eacd278471?source=rss-dbf8b945911c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2eacd278471</guid>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[solaria-labs]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Jessica Schilling]]></dc:creator>
            <pubDate>Mon, 20 Aug 2018 20:44:26 GMT</pubDate>
            <atom:updated>2018-08-20T20:44:26.567Z</atom:updated>
            <content:encoded><![CDATA[<p>Here at <a href="http://www.solarialabs.com/">Solaria Labs</a> — the innovation incubator at Liberty Mutual Insurance, and my home as a senior product designer and UX generalist — we’ve given a lot of thought into what makes for good user experience, and distilled it down to the following key principles. Knowing these is enough for the <strong><em>tl;dr</em></strong> version, but to dig a little deeper into what makes us tick, take a few minutes to read on. It’s worth it, we promise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*cfRtqw6-1qXABuv5ssN3wQ.jpeg" /></figure><ol><li>Good UX begins with research and testing.</li><li>Good UX plays well with the business.</li><li>Good UX plays well with developers.</li><li>Good UX is consistent, systematic and atomic.</li><li>Good UX is simple, efficient and intuitive.</li><li>Good UX has a delight-full, distinct personality.</li><li>Good UX inspires trust.</li></ol><h3>Principle #1: Good UX begins with research and testing.</h3><p>Before we design anything, we have to know what we need to design — and before that, why we need to design. This means research and testing come before any deliverables, and it means <strong>defining and understanding the underlying problems before we look for solutions to them</strong>. We don’t waste time solving the wrong problems, even if solving problems feels good.</p><p><strong>We’re committed to a wide range of testing methodologies</strong> because we have a variety of users, a variety of products, and a variety of problems and hypotheses. This might mean we don’t use every sort of user test for every product — and that’s OK.</p><p><strong>We acknowledge that intuition is powerful, but not foolproof.</strong> Our life stories, culture, cognitive styles and aesthetic preferences can be very different from our users’, so we know intuition can only get us so far — and it can even create a false sense of security. (That said, we absolutely let our previous adventures in user testing inform our future design work.)</p><p><strong>It’s obvious that early-stage testing saves time and wasted effort, but it’s true throughout the entire design process, too.</strong> If something doesn’t make sense while we’re designing, it’s our responsibility to stop and ask as many questions as necessary until we understand enough to keep going. This doesn’t mean we have to have everything pinned down all the time (that’s not Agile) but it does mean we need to bake in the time for ongoing research and testing as iterations continue — or risk going down the wrong path.</p><h3>Principle #2: Good UX plays well with the business.</h3><p>A UX team is at its most useful when it’s an <strong>integral part of the greater corporate culture.</strong> We aim to be visible and valuable within Solaria Labs (and Liberty Mutual) by leveraging our wide-ranging expertise on a team-by-team, project-by-project basis, while also leveling up our skills via ongoing education, curiosity, and balanced critique from within and without.</p><p><strong>Before we design, we define goals and KPIs</strong> — because as our process continues, these apply to the entire product, to each specific screen, and even to key elements on a screen. Every UX element we build needs to map to a measurable business goal. (Yes, “delight the user” should be a business goal.) Note, too, that good research helps us define KPIs.</p><p>We always enjoy nerding out on new ideas and experiments, but only ones that don’t disrupt or conflict with our core business values. <strong>We will never pursue a project or product unless it’s in the user’s best interest, nurtured by the business.</strong></p><p><strong>We design iteratively and with increasing specificity, because this is how Agile business works.</strong> We won’t do high-fidelity design until enough low-fi work has been tested and approved to ensure that we’re not wasting effort — there’s no point in discussing button colors if we’re validating concepts. After all, as design fidelity increases, so does our resistance to change … and the cost of such change when it occurs.</p><h3>Principle #3: Good UX plays well with developers.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*7Fc5vHf1VSnXbvBBLfW_gg.jpeg" /></figure><p>We <strong>design for iterative, modular development practices.</strong> Even if a project doesn’t have any plans post-MVP (yet), our goal is to design something that’s modular enough to easily accommodate continuous improvement. Think Legos, not log cabins.</p><p>We also <strong>design for performance.</strong> We won’t ask a developer to build something shiny when they — or we — suspect it will be slow. Shininess is just icing on the cake, after all.</p><h3>Principle #4: Good UX is consistent, systematic and atomic.</h3><p>If we have one UX axiom to rule them all, it’s this: <strong>Always be consistent.</strong> Consistency …</p><ul><li>Reduces overall cognitive load</li><li>Enables intuitiveness and learnability, making it easier for users to accept new features or flows over time</li><li>Reinforces your product’s personality through a unified visual or textual voice (this applies to “white-labeled” elements you’ve brought in from someone else, too!)</li><li>Implies stability and inspires trust</li></ul><p><strong>Our commitment to consistency considers the larger landscape in which our products live.</strong> Every OS has its own design patterns we must acknowledge. At an even wider level, people have been using the internet for decades now — which means that whether or not we approve, there are basic design patterns that we ignore at our own peril.</p><p><strong>We know that while we can sometimes “solve” problems by deviating from consistency, this is almost always too high a price to pay.</strong> When faced with situations like this, it’s usually better to refrain from a feature altogether, or dial it down in order to stay consistent.</p><p><strong>We know that establishing a strong design system early on keeps us from wasting work or alienating users.</strong> While a constantly-changing UX might seem “iterative”, it actually destroys trust. Minor change may go over just fine, but it’s better in the long run to take time to build tested and reasonably fully-formed experiences than to iterate significantly on major UX paradigms.</p><p><strong>We are committed to “atomic design” at an organization-wide level.</strong> Solaria’s role as a rapid incubator may mean we shouldn’t roll out detailed design systems for each project — but our overall design methodology can still be a framework-based one that encourages the atomic design of modular, extensible, swappable elements that map to similar building blocks in code. This includes making the most of widely-utilized open source design frameworks, as well as standardizing functional and visual patterns between products whenever practical.</p><h3>Principle #5: Good UX is simple, efficient and intuitive.</h3><p>In short, <strong>we are committed to improving the signal-to-noise ratio of our products.</strong> More specifically…</p><ul><li>We design task-based products that rely on contextual wayfinding cues, clear information hierarchies, and action-based information architecture in order to help users get their stuff done faster</li><li>We automate processes whenever possible (i.e. auto-filled forms) and hide conditional information whenever practical (i.e. pop-up text for definitions you’ll only read once or twice)</li><li>We limit distractions and design for consecutive (not concurrent) tasks, because people can’t really multitask</li><li>We remove choices unless they’re critical to the outcome … or delightful enough to be worth the cognitive cost</li><li>We aren’t ashamed to borrow patterns from Google, Facebook, Mac OS, or anyone else who has done what we’re trying to do either better or more pervasively</li></ul><p><strong>We believe that every element in a design must have a clear purpose.</strong> If something doesn’t add to the overall positivity of the user experience, it shouldn’t be there.</p><p><strong>We reduce cognitive workload by enabling intuition.</strong> What does this actually mean? Because intuition happens on an unconscious level, the more we enable it, the less we sacrifice the two types of cognitive workload: the effort it takes to do a specific task (<em>intrinsic</em> load), and the effort to understand an interface as a whole (<em>germane</em> load).</p><h3>Principle #6: Good UX has a delight-full, distinct personality.</h3><p><strong>We believe that a good product isn’t just easy to use; it’s also feels good to use.</strong> Depending on the product, this might mean we are warm, witty, kind, whimsical or whatever — but whatever we are, we need to be it consistently.</p><p><strong>We know the best design is by humans, for humans.</strong> Good UX assumes the user will be tired, distracted, stressed or feeling under the weather, and accommodates this with grace, compassion and good humor. At our best, we’re transparent and humane; we explain why we do what we do, and we do so in a way that doesn’t sound like a robot, a Magic 8 Ball, or a TV infomercial.</p><p><strong>We know when to blend in and when to stand out.</strong> Our users see hundreds of digital services every day, and sometimes it’s better to be a face in the crowd. When we’re quirky, we’re quirky for a reason, not to compensate for less-than-optimal UX or just to be that kid who raises his hand every time the teacher asks a question. A product doing its job well tickles one part of the brain; a product displaying personality tickles a different part. Done well, this inspires empathy, even affection — done poorly, it has the opposite result.</p><h3>Principle #7: Good UX inspires trust.</h3><p><strong>We believe that trust makes life easier for the user as well as the business.</strong> If we design intuitive, consistent experiences, we build trust, increasing conversion and making it more likely our product will become “invisible”, ubiquitous and friction-free over time.</p><p><strong>We believe that trust hinges upon providing good feedback and setting realistic expectations.</strong> Particularly in a beta-release environment like Solaria Labs, it’s important for trust’s sake not to overpromise and underdeliver. And giving feedback is critical to building trust for a number of reasons, whether on a micro-interaction level (is an action non-responsive or is the whole app broken?) or on a larger scale (a user is more likely to complete a multi-screen flow if she knows she’s on the last step of the process).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2eacd278471" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solaria-labs-blog/solaria-labs-user-experience-principles-b2eacd278471">Solaria Labs User Experience Principles</a> was originally published in <a href="https://medium.com/solaria-labs-blog">Solaria Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Better living through stuff that comes in boxes]]></title>
            <link>https://medium.com/@jessicaschilling/better-living-through-stuff-that-comes-in-boxes-f45b4630d7d2?source=rss-dbf8b945911c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f45b4630d7d2</guid>
            <dc:creator><![CDATA[Jessica Schilling]]></dc:creator>
            <pubDate>Tue, 23 Dec 2014 22:54:13 GMT</pubDate>
            <atom:updated>2014-12-23T22:55:36.397Z</atom:updated>
            <content:encoded><![CDATA[<p>Whatever you happen to celebrate for the winter holidays, this will make it better. Don’t turn your nose up at the ingredients; just trust me on this one, and get your holiday on, Iowa-style.</p><p>Grandma Ina’s Orange Salad</p><p>1 box vanilla pudding (“cook and serve” variety)<br>1 box tapioca pudding<br>1 box orange gelatin<br>1 10.5-ounce bag miniature marshmallows<br>1 8-ounce can crushed pineapple in juice<br>1 small tub non-dairy topping</p><p>Combine vanilla pudding, tapioca pudding, orange gelatin and 3 cups water over medium heat. Stir constantly until thick. Cool briefly. Fold in marshmallows. Cool significantly. Stir in pineapple (drained) and non-dairy topping. Refrigerate until firm.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f45b4630d7d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>