<?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[TeleTracking Design - Medium]]></title>
        <description><![CDATA[Designing a future where #nopatientwaits. - Medium]]></description>
        <link>https://medium.com/teletracking-design?source=rss----20d3e79b2a10---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>TeleTracking Design - Medium</title>
            <link>https://medium.com/teletracking-design?source=rss----20d3e79b2a10---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:15:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/teletracking-design" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Designing for Consumers in an Enterprise World]]></title>
            <link>https://medium.com/teletracking-design/designing-for-consumers-in-an-enterprise-world-2014a5ded7b9?source=rss----20d3e79b2a10---4</link>
            <guid isPermaLink="false">https://medium.com/p/2014a5ded7b9</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Katy Watkins]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 14:31:06 GMT</pubDate>
            <atom:updated>2019-01-31T14:31:05.924Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kD4KE8HdRIG6V0OfBZEyBg.jpeg" /></figure><p>Let’s set the stage. At TeleTracking, we have nearly three decades of experience building software that helps health systems provide patients with the care they need more efficiently. This means a large portfolio of enterprise products. And with that portfolio comes a lot of existing knowledge, habits, patterns, and technical debt to be accounted for; a lot to wrap my head around when I first started.</p><p>To get specific for a minute, that means that business as usual for TeleTracking is building enterprise software for specialized users who historically have been operating in very specific contexts. We have a great team and are continually improving and evolving our software, but the reality is that the vast majority of it is immensely complex, with a long history, viewed on large monitors. As a result, it’s supported only on specific desktop resolutions. Hardly unheard of in the enterprise software world.</p><blockquote>Enter <a href="https://www.teletracking.com/resources/community-scheduling-and-workflow">Community Scheduling &amp; Workflow</a><strong>™</strong> (CS&amp;W).</blockquote><p>Community Scheduling &amp; Workflow<strong>™</strong> is a relatively new solution for us. Newer code, though it’s still playing by the same rules as other solutions and only officially supporting desktop resolutions. It helps improve wait times and patient experience for ambulatory care centers and includes the ability for patients to schedule their own appointments.</p><p>The most important part here is <strong>patients </strong>can schedule their own appointments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eNCprL0nZmAwb17NWo_YKA.png" /><figcaption>Designing for consumers (in this case, patients) means we need to think about a much wider range of contexts.</figcaption></figure><p>Up until CS&amp;W, we were <em>always</em> designing for employees of a hospital or health system. These are people who use our software to do their job day after day.</p><p>Suddenly we’re also building a set of features targeted for a much larger group of people. It’s not something that will be used by the same person day after day any more. And it’s a publicly accessible website, so these users are definitely going to be accessing it with more devices than just desktop computers.</p><blockquote>So what do you do when you join a team working on software for a new set of users and contexts, but continuing to build it as if it’s business as usual?</blockquote><h3>Talk About the Differences Early…</h3><p>This might be obvious, but I can’t stress it enough: Communication is key.</p><p>Designers don’t work in a vacuum, and as a new team member coming from the consumer software world, I had a useful outside perspective. But it wasn’t the only perspective, or even the most important one. TeleTracking is full of smart people with many years of experience in healthcare and in building these types of solutions. So I put my views out there and listened to what my coworkers had to say in response.</p><p>Fortunately we have a great team. Everyone was on board with the idea that patient self-scheduling functionality would sometimes need to be handled a bit differently than other solutions had been. The list of capabilities we could improve or change grew pretty quickly from these discussions.</p><h3>… and Talk About Them Often</h3><p>I probably sounded like a broken record at some points, but mindsets and habits are hard to change, especially when they’ve been ingrained for years.</p><blockquote>It’s easy to just lump our solutions together in the same bucket — one process and set of standards to rule them all.</blockquote><p>So any time I noticed we were generalizing things, I piped up and pointed out that we may find CS&amp;W could use a different set of patterns or requirements. The goal wasn’t to immediately demand a bunch of changes, it was to start changing mindsets so we are all thinking about our patient self-scheduling solution a little differently.</p><p>The persistence paid off. Over time others have started saying similar things as well, which is great to see. That’s always the goal—for everyone to be thinking critically about what we’re doing. It’s particularly important for us with CS&amp;W because this is a new solution space.</p><h3>Start User Testing ASAP</h3><p>Up until recently our experience with user testing has been in hospitals with very specialized users. Once we started talking in depth about the fact that our users could be anyone, we came to the realization that user testing for our patient self-scheduling functionality could be a lot simpler than it is for other solutions. As everyone has been a patient at some point in their lives, pretty much anyone could give us useful feedback.</p><p>To get us started, a team member posted in a company Slack channel asking for anyone interested in helping to test our patient self-scheduling functionality to react to her post with an emoji. That gave us a lot of folks to reach out to and start testing with, and the end result was a ton of valuable feedback that will inform our design work going forward.</p><h3>Find the Quick Wins</h3><p>The byproduct of testing and talking to people on and outside your team is that you learn more and identify opportunities for improvement. It also starts to become apparent which opportunities are going to be easy wins, and which are going to take more time.</p><p>The list of things we’d like to improve is pretty large: accessibility, cross-browser support, testing (manual and automated), prototyping, and responsiveness just to name a few.</p><blockquote>The important part is finding realistic and achievable goals to start making concrete improvements.</blockquote><p>Thanks to the relatively small feature set in patient self-scheduling (compared to TeleTracking’s other solutions), we found we could pretty easily set a course for improving our standards in two key areas: accessibility and responsive design.</p><p>We have a great team and product manager who didn’t need to hear about <a href="https://www.w3.org/WAI/business-case/#minimize-legal-risk">legal risks</a> to be on board with focusing on accessibility. And the design team had already been working to improve accessibility across all of TeleTracking’s products. The public-facing nature of patient self-scheduling just means it makes sense for us to prioritize it a little more, and the smaller scope of functionality helps us achieve it quickly.</p><p>As for responsive design, the “easy” win was a quick and dirty responsive retrofit. CS&amp;W already uses a fair bit of Bootstrap, it just wasn’t being designed or developed to account for a variety of screen sizes. So going in after the fact to ensure that everything at least resized and scaled appropriately was a reasonable task. Changing how we design from the start to better accommodate mobile will be a larger process, but viewing responsive design as a requirement is a solid start.</p><h3>Document the Differences &amp; Decisions</h3><p>Talking about the differences between solutions and their contexts is all well and good, but if it’s not written down as a concrete part of what we do and what others reference, it’s harder for it to really stick long term.</p><p>The most valuable tool for designers here at TeleTracking is our <a href="https://medium.com/teletracking-design/mosaic-design-system-living-solution-d5df4a752e9b">Mosaic Design System</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*TnwyGaU3a_0P7TIouUC2Lg.png" /></figure><p>Mosaic helps us build a cohesive platform and work more efficiently. Plus, our internal Mosaic website functions as a place for us to document patterns and processes for everyone to reference, helping us stay consistent.</p><p>So to start, we’ll be highlighting internally that supported browsers and screen sizes differ depending on whether or not the product is for a consumer audience.</p><h3>Keep Pushing for Progress</h3><p>The process of improvement never stops, especially on a solution that’s so different from everything else being built around it. But the best part about having consumer-facing software in this enterprise world is that thanks to our collaborative team and our design system, almost everything we do to push our patient self-scheduling functionality forward can benefit the platform as a whole.</p><p>We don’t want to change things just to be different because the users of this product are different. But we do want to make sure we’re meeting (and exceeding!) our users’ needs. So when we do the work and find out changes from our standard patterns and processes are justified, we want to make sure we define and document them for future reference. That helps all of us work smarter instead of harder.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2014a5ded7b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teletracking-design/designing-for-consumers-in-an-enterprise-world-2014a5ded7b9">Designing for Consumers in an Enterprise World</a> was originally published in <a href="https://medium.com/teletracking-design">TeleTracking Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tell Me a Story: Storytelling as a Research Framework]]></title>
            <link>https://medium.com/teletracking-design/tell-me-a-story-storytelling-as-a-research-framework-8dd5e226383a?source=rss----20d3e79b2a10---4</link>
            <guid isPermaLink="false">https://medium.com/p/8dd5e226383a</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Tonya Sand]]></dc:creator>
            <pubDate>Thu, 20 Dec 2018 18:54:33 GMT</pubDate>
            <atom:updated>2019-01-02T13:44:56.252Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yZ9kVUI5tP05rB8STSAedw.png" /></figure><p>“I want to know the story.”</p><p>This was the last thing the manager of patient placement told me before our interview was cut short by an urgent staff request. I was on-site at a large hospital observing and interviewing her staff in an effort to understand the chaotic world of transferring patients in and out of a health system.</p><p>Her comment stuck with me and back at the office, it would often resurface during design workshops, roadmap planning and brainstorming sessions:</p><p><em>“We should tell the story of the patient’s journey to receive care.”</em></p><p><em>“What’s the client’s story? Do we understand their motivations and challenges?”</em></p><p><em>“Do we know our corporate story? Where have we been and where are we going?”</em></p><p>We all want to hear a good story. It’s a big part of what makes us human. Whether it’s a riveting movie, a great book, or an emotional play, stories allow us to learn about others and experience situations we might never encounter. We can go further into the mundane and discover dimensions of beauty and challenges of everyday life that aren’t always clear.</p><p>Stories educate, inspire and bring people together. When we take the elements of a story and apply them to our research, we can uncover deep truths and meaning. Sharing those discoveries with others in the same format helps us find commonality, spark creativity, and foster empathy. These elements relate to almost every situation in our work lives from targeting a new market to designing a game-changing product.</p><p>So, let’s go write a story…</p><p><strong>The 5 elements of a story</strong></p><p>Every good story is made up of five foundational elements. These elements are essential for a well-rounded, meaningful, and complete story. They also translate nicely into the very types of information to gather during any research phase:</p><p>· Characters</p><p>· Setting</p><p>· Plot</p><p>· Conflict</p><p>· Resolution</p><p><strong>Setting</strong></p><p>The setting describes the location of where the story takes place. An author should describe the immediate and general surroundings of the setting with enough detail for a reader to picture the scene. This helps portray how characters interact in the setting and how they relate to their environment.</p><p><strong>Characters</strong></p><p>The characters are the focus of the story. Typically, a story will revolve around the main characters and any supporting characters. When writing about your characters, it’s important to include detailed information so that a reader can visualize them: personality traits, motivations, physical attributes, and any relevant experiences that shape how they view the world.</p><p><strong>Plot</strong></p><p>The plot is a series of events that make up a story. It is the cause and effect relationship of these events that describe the meaning behind why certain actions and thought processes arise.</p><p><strong>Conflict</strong></p><p>Conflict in a story happens when a problem or challenge arises. The characters must face and ultimately resolve conflict in order for them to achieve their initial goals. Sometimes, conflict can’t be resolved. When this happens, the characters often learn new lessons, formulate new goals and create new solutions.</p><p><strong>Resolution</strong></p><p>Resolution of conflict allows characters to solve their problems before the story ends. It is a necessary story element to provide the reader with closure.</p><p>Let’s use the story elements to illustrate storytelling as a research framework.</p><p><em>Here’s the setup:</em></p><p>Your company’s main product is an application that helps teachers communicate student information to parents called <strong>Progress U</strong>. Teachers set up student profiles, update the profiles with grade reports, and authorize parents to view the information via a browser based account. Ever since the roll-out, your company has received good feedback about how the application enables parents to become more active in their children’s education goals.</p><p>However, reports have been coming in that a new competitor, <strong>TeacherConnect </strong>has introduced a similar product to the market. Their product has all of the same features that <strong>Progress U </strong>does plus additional flexibility like a streamlined mobile app and a direct texting feature so that parents can chat with teachers. You have been tasked to research some clients to see how they can use these features in an effort to make <strong>Progress U </strong>more competitive with <strong>TeacherConnect</strong>.</p><p>You create a research plan that incorporates the 5 elements of a story and then use it to guide your observations and interviews with teachers at client schools and some parents who use <strong>Progress U</strong>. I’ll focus on how this might look using one school.</p><p>Let’s pretend that your research plan has already been underway for a while. When you first started out, you outlined the 5 main elements of a story in your notebook. Read below to see how your story begins to form after gathering data during your research trips.</p><p><strong><em>Setting</em></strong></p><p>North Village Elementary is a large public school that educates around 2,000 students in grades K-5. The school is located in North Village, a suburban area 5 miles outside of a major city called Riverdale. North Village also borders a vast rural area on one side called Northway.</p><p><strong><em>Characters</em></strong></p><p>Teachers:</p><p>50% of the teachers at North Village Elementary are between 35–45 years old, 30% are under 35 years old and the remaining 20% are over 45 years old. Most are comfortable with modern technology such as social media, online collaboration tools and mobile apps. However, many of the older teachers (45+ years) do not own a modern smartphone or use social media regularly.</p><p>Due to the overcrowding and resource issues at the school, most teachers are overworked. They must manage large classes of students from extremely diverse backgrounds, work together to fill in for a class when a teacher is absent, and make do with limited materials. Many teachers claim that they feel depleted at the end of the day.</p><p>Students:</p><p>North Village Elementary students come from varied backgrounds. A large portion (about 50%) live in the suburb of North Village while the other half of the population is split between students who live in either the city or the rural area around North Village.</p><p>There is a large disparity between student educational needs and the ability to provide sufficient staff coverage. With such a large school population, many students require additional help. Unfortunately, some students are frustrated with the lack of support in these areas, which contributes to frequent educational and behavioral issues.</p><p>Parents:</p><p>School parents span a large array of different backgrounds and socio-economic situations. Many households include two parents working full time jobs (70%), but a large number of households have either one parent working either full time (20%) or part time (10%.)</p><p>Most parents mentioned that they have a hard time getting information from the school, mostly due to their busy schedules and/or unavailability due to work obligations. A large percentage complained of not knowing how to help their child when they are having academic problems. Parents often call the school in an effort to find out more about their children’s status.</p><p><strong><em>Plot</em></strong></p><p>The school implemented <strong>Progress U </strong>two years ago and has had mixed results. Originally, the decision was made to use <strong>Progress U </strong>after a large group of parents complained that they wanted to know more about how their children were doing. The application roll-out had some success because it gave teachers a centralized place to put student information. However, school officials are looking into the competitor’s app because it offers more functionality.</p><p><strong>Conflict</strong></p><p>When <strong>Progress U </strong>was implemented, North Village Elementary was already growing exponentially and this contributed to a lot of overcrowding. Some classes take place in trailers on school property due to lack of space. Classes tend to be very large and there is also a shortage of teachers in some areas due to budget cuts. This problem has become worse over the past year.</p><p>Since teachers are overburdened, they don’t update student profiles with grade information in <strong>Progress U </strong>very often. Parents who have created accounts in the system become frustrated by the lack of information and will often resort to calling the school. Since the school is experiencing an extreme drain on resources, calls aren’t returned in a timely fashion, which causes more issues.</p><p><strong><em>Resolution</em></strong></p><p>The overburdened teachers at North Village Elementary need an easy way to communicate student information to parents. The solution needs to take their overworked schedules into account and allow timely, on-demand information access.</p><p>A chat feature might not be the best answer in this situation, because teachers are not available enough to consistently use it. A mobile friendly version of the application has potential, because it allows access on the fly. The recommendation is to look into an upfront collection of student progress data before it hits <strong>Progress U</strong>. All teachers have to update a system for school records, so making a connection from that to <strong>Progress U </strong>eliminates the need to have to remember to update a second application.</p><p>So, the story of North Village Elementary wraps up with some interesting findings. At the beginning of this research project, you were tasked with finding out how<em> </em>a chat feature would benefit the school. It was already assumed that your company would be adding chat functionality to <strong>Progress U </strong>so it would match<strong> </strong>your competitor’s solution. But, your actual research reveals a strong argument for <em>not</em> investing too much in that type of feature.</p><p>This is where the multidimensional framework of storytelling brings so much value. By taking all 5 story elements into account, you uncover a fuller, richer view of the subject matter. Of course, if this were a real project, you’d want to repeat this exercise with multiple schools in order to get a larger sample for better analysis. But, this small example still demonstrates how wrong we can be when we assume first and research later. Especially when we don’t take the time to research thoroughly.</p><p>What else can you do with a story? Present it to your clients and read it back to them. Invite them to author it with you. Create one about your organization and discover new ways to improve processes. Use it to help different people relate to each other better. There are so many ways to use the story paradigm to foster communication, empathize, seek collaboration, and foster innovation.</p><p>I’d love to hear from a story you’ve written or plan to write. Let me know in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8dd5e226383a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teletracking-design/tell-me-a-story-storytelling-as-a-research-framework-8dd5e226383a">Tell Me a Story: Storytelling as a Research Framework</a> was originally published in <a href="https://medium.com/teletracking-design">TeleTracking Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get Real]]></title>
            <link>https://medium.com/teletracking-design/get-real-89148e9895c9?source=rss----20d3e79b2a10---4</link>
            <guid isPermaLink="false">https://medium.com/p/89148e9895c9</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Thomas Havranek Jr.]]></dc:creator>
            <pubDate>Thu, 20 Dec 2018 11:30:49 GMT</pubDate>
            <atom:updated>2018-12-20T13:39:45.860Z</atom:updated>
            <content:encoded><![CDATA[<h3>Get Real: The problem with using a lot of words and not really saying anything.</h3><h4>We’ve all been there…</h4><p>You’ve just listened to a presentation filled with loads of concepts, data, and jargon. The presenter asks if there are any questions or comments. Someone says something about slide 9 having a typo. Another person raises an arbitrary concern that’s really just a plug for their own project. The rest remain silent.</p><p>The presenter smiles and thanks everyone for their time. The meeting is adjourned and the assumption is that all parties now have a shared understanding of the material.</p><p>And yet they don’t.</p><p>You know they don’t. They know they don’t. The presenter even has a pretty good idea that they don’t. But the meeting is finally over and you can all get back to that thing you need to finish before the end of the day.</p><p>How does this happen? Why are we trapped in this cycle? I have a theory: It’s because we are far too reliant on words. Yeah I know, words matter. But they’re also notoriously unreliable.</p><p>Words are not concrete, but rather an abstraction of real life. If they were concrete there wouldn’t be 2,000+ languages spoken today; each one having been uniquely abstracted from a shared, concrete reality.</p><p>Words are also too easy. Anybody can fill a presentation deck with words and make it look like they accomplished something. But it takes significant energy and rumination to move past the abstract and articulate something concretely. It also requires something better than words.</p><h4>Systems Thinking &amp; The Importance of Diagramming</h4><p>It’s been said that if you can’t explain something simply, you don’t understand it well enough. It’s a great sentiment, but how does one go about properly understanding something? The first step is to adopt a systems mindset and embrace the fact that “<a href="https://medium.com/disruptive-design/tools-for-systems-thinkers-getting-into-systems-dynamics-and-bathtubs-1f961f7c4073">our world is made up of interconnected and interdependent systems.</a>” — Dr. Leyla Acaroglu.</p><p>Systems are inescapable. And the field of Experience Design exists to serve systems, whether we acknowledge it or not. Be it workflows, journey maps, user networks, etc. Make no mistake, we are designing for and within systems.</p><p>“But <em>I</em> care about the <em>user</em>,” you might say with your chest puffed and left eyebrow cocked. Great. Is your user alone on an island with zero dependence on his or her surroundings? Of course not. Your user is one component of a complex system. One element in an elaborate <a href="https://medium.com/teletracking-design/solve-for-x-1818099bdb9c">equation</a>.</p><p>As designers we are constantly stepping into new spaces and having to make sense of systems that are completely foreign to us. And the best way to make sense of any system is to <em>diagram</em> it.</p><blockquote>di·a·gram: a simplified drawing showing the appearance, structure, or workings of something; a schematic representation.</blockquote><p>The <strong><em>workings</em></strong> of something… That term doesn’t get tossed around as much as it should. It raises a very interesting question; do we truly understand the workings of our systems or are we just pretending that we do by using a lot of words? The process of diagramming forces us to answer this question by separating the abstract from the concrete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bsDYOyH4p1_Yy5itEFNKEw.png" /></figure><p>Without properly diagramming a system, our understanding of that system is often a complicated mess of concrete and abstract ideas (usually represented by a lot of words). This is a problem because what is abstract is often subjective, ambiguous, contradicting, and unreliable. If we aren’t careful to draw that out, the same will be true of our understanding of the system.</p><h4>Example: The Human Circulatory System</h4><p>Let’s take a look at a system we’re all intimately familiar with; the Human Circulatory System.</p><p>An overview of the Human Circulatory System might look something like this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fDs5z3NI4-kHeRXP9q98LQ.png" /></figure><p>But is this a system? No. This is terminology. Terminology is used to <em>describe</em> the system. Terminology is abstract. And because it’s abstract, it doesn’t tell us anything about the appearance, structure, or workings of this system. So let’s focus on what is concrete…</p><p><strong>Purpose:</strong> The purpose of this system is to circulate blood through the human body. This is critical… <em>Blood</em> is the focus of this system. If we don’t maintain that focus, there’s nothing stopping us from diagramming the entire human anatomy.</p><p><strong>Elements:</strong> As we can clearly see above, there are many different terms for the elements of this system, but when you break them down, there are really just two <em>core</em> elements; Blood Vessels and Organs.</p><p><strong>Functions:</strong> There are four functions that these elements can perform; oxygenate blood, pump blood, carry blood, or process blood.</p><p><strong>States:</strong> There are two states in which blood can be; either oxygen-rich, or oxygen-poor.</p><p><strong>Blood Flow Direction:</strong> Last, there are two directions that blood can be flowing; away from the heart, or toward the heart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqi-U9QCdTN3t46MsFw5lA.png" /></figure><p>Now we have some very objective categories, and we can use these to properly frame this system. For example, we all have an innate understanding of our lungs. But when we use the term “Lungs,” what does that really mean in the context of this system?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t5ZQZH00A-jAUyrz76xMbQ.png" /></figure><p>Objectively, “lungs” are an organ that oxygenates oxygen-poor blood in this system. Of course that sounds like a mouthful, but avoid the temptation to oversimplify this just for the sake of convenience. Convenience comes at the cost of properly understanding.</p><p>What about a “vein?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cq0Zn6YaxS9kTgSq5u5-nQ.png" /></figure><p>And an “artery?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y-k9cPD06bDVCLbZMnR-EQ.png" /></figure><p>Starting to get the idea? When we focus on these concrete elements, we can begin to properly diagram this system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdjij-aidZJaaLgeP1X7Qw.png" /></figure><p>Even if we strip away all of the terminology, we can still get a sense of how this system works with just a few key items explained; it’s a network of organs and blood vessels, moving blood through various states of oxygenation and use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sct53QiWTW4bB6M2sBNQRg.png" /></figure><p>No words required. In fact, the Circulatory System offers a great example of words being unreliable: 85% of the time the term “artery” implies a blood vessel that is carrying oxygen-rich blood (red), and “vein” implies a blood vessel that is carrying oxygen-poor blood (blue). But there is one pair of blood vessels where this pattern breaks down and the terminology is actually opposite than the rest. Any guess where that occurs?</p><p><strong>Answer:</strong> The Pulmonary Vein and Artery, which connect the lungs and the heart together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kxs0HZ0jdQW9T-Z8l2H_Aw.png" /></figure><p>This is essentially the sub-system that is responsible for recycling, or oxygenating, the blood. So it’s the one place in the system where the terminology essentially contradicts itself. In this case, the concrete category that is driving the terminology is the direction of blood flow (away/toward heart), rather than the oxygenation state of the blood.</p><p>This type of synthesis requires a lot of work and critical thinking, but if done correctly can prove invaluable; allowing teams to focus on solving problems rather than constantly relearning domain knowledge. But when we neglect to do this heavy lifting up front, the burden doesn’t magically disappear. It gets pushed downstream, manifesting itself in the form of unproductive meetings, redundant conversations, and far too many words.</p><p>Get real. Do the work. And focus on what is concrete.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89148e9895c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teletracking-design/get-real-89148e9895c9">Get Real</a> was originally published in <a href="https://medium.com/teletracking-design">TeleTracking Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Efficient Consistency with the Mosaic Design System]]></title>
            <link>https://medium.com/teletracking-design/mosaic-design-system-living-solution-d5df4a752e9b?source=rss----20d3e79b2a10---4</link>
            <guid isPermaLink="false">https://medium.com/p/d5df4a752e9b</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[style-guides]]></category>
            <dc:creator><![CDATA[Benjamin Martin]]></dc:creator>
            <pubDate>Fri, 12 Oct 2018 01:14:24 GMT</pubDate>
            <atom:updated>2019-01-10T18:43:15.280Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9DR6ULv0L42DEyAWO1uNg.png" /></figure><h3>I am in a World of Shit</h3><p>I am the type of person who is never happy with the current state. I believe there is always room for improvement; to grow, to change, to become better. The company I work for is also not afraid to change, to grow, or to become better. We need to change, because we are at a pivotal time in our history, the mission is clear and time to act is now. We are going to war and we need the best talent, tools and processes to win. As the president of our company Chris Johnson says “better never stops.”</p><p>Years ago, all of our products, whether internally built or bought, looked completely different.</p><blockquote><em>“I am….in a world….of shit.”</em></blockquote><blockquote>-Private Gomer Pyle</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/0*tYdgali-8anraOdI.gif" /></figure><p>In a world of design shit, that is. Because our products functioned and met very important, real world needs, and ultimately saved many lives, they just did not look related. They also did not share common UI patterns, leading to a fragmented user experience.</p><blockquote>“In other words, it’s a huge shit sandwich, and we’re all gonna have to take a bite.”</blockquote><blockquote>-Private Joker</blockquote><p>And we did. We all took a bite. Our team can now say that all of our products look related.</p><p>It’s a beautiful thing.</p><p>Fast forward a year.</p><p>We started to explore ways to improve and create cohesiveness and consistency between Design and Engineering. I spent endless days and nights, dreaming and waking in the middle of the night, with thoughts and ideas on how to make it a reality. This was not out of stress, but pure passion for what could be.</p><p>The solution needed to fuse with the tools we already use, be automated when possible, create consistency across Design and Engineering, and serve multiple complex enterprise web and mobile applications of varying technologies.</p><p>We needed a way to consistently share styles, components, and UI patterns across multiple products.</p><p>Our products looked related, but they needed become a family. The goal was to create a system with one source of truth, that would automatically update and keep all our designs and products in sync.</p><p>To win this war, we needed to increase efficiency between Design and Engineering, create consistency, and reduce time to market.</p><p>Over the last year, our team at <a href="https://www.teletracking.com/">TeleTracking Technologies</a> has been building our design system. We spent a lot of time in defining what a design system meant to us and most importantly how it could benefit us.</p><p>With much respect to the famous design systems of the world, this is a story of how ours is unique.</p><p>Mosaic is our design system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*FfAkBygUodc8R1O6ARyZ3w.png" /></figure><p>The Mosaic Design System is made up of ideas, processes, patterns, principles and tools. And in this war, it’s our weapon of choice.</p><h3>What is Your Major Malfunction?</h3><p>We had inconsistency in many areas, including styles, UI patterns, naming conventions, language, CSS class implementation, and more. We had various problems to fix, but our major malfunction was inconsistency. We aimed to build a system to solve it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/115/1*O3KlyuqjhjJQEDZXT3Ny6A.png" /><figcaption>Shades of gray from our platform. Discovered with curiosity and by auditing our CSS.</figcaption></figure><blockquote><em>“I didn’t know they stacked shit that high.”</em></blockquote><blockquote>-Gunnery Sgt. Hartman</blockquote><p>We did.</p><p>We had no centralized standardization or a central source of truth for design elements. One that could inform multiple products and projects. Our platform contained over 110+ colors and 23+ font sizes. That is just our recently built, cloud platform, and does not take into account several older product suites. Or mobile. This standardization could increase cohesiveness and consistency.</p><p>The amount of time we spent pixel twiddling and begging engineers to comply with our requests was costly. We needed centralized components that could be placed anywhere in the UI and scale size accordingly. They should be easily shared across all our products and projects. They should be getting their styles from the standardized source. This could increase efficiency and consistency, effectively saving time and money.</p><p>Our CSS was unmaintainable and we continued to accumulate technical and design debt. We only had product specific CSS, limited reusable classes, no standard naming conventions, no CSS pre-processing and a general direction in Engineering that CSS was the least important code. They had to focus on functionality over aesthetics. Our CSS, like our components, needed to be centralized, modular, object-oriented, and easily served between multiple systems. This could increase understanding, reduce code, and decrease maintenance.</p><p>We had designers and engineers approaching similar needs differently. We had no reference for up-to-date styles, components, UI patterns, and guidelines. An up-to-date resource with minimal maintenance could increase consistency and alignment.</p><p>Design and Engineering weren’t speaking the same language. We needed to refer to the naming of components, patterns, and SASS variables with common understanding. This shared vocabulary could create efficient conversations and reduce rework.</p><p>We needed an answer for our major malfunction; inconsistency spanning a wide range of areas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ONsPmmZd_PrYgnCTwvJ-RQ.png" /><figcaption>Questions we set out to address.</figcaption></figure><h3>Boot Camp (One Source to Rule Them All)</h3><p>If we are going to win this war, with our weapon of choice (Mosaic, in case you missed it) we needed it by our side as we entered consistency boot camp.</p><p>Phase one of the Mosaic Design System was defining centralized consistent platform building blocks. Colors, icons, icon sizes, font sizes, shadows, border radiuses, etc. The lowest level of the UI that can be used to build any element.</p><p>Collaborating with multiple designers on the team we whittled the 110+ colors to a standardized set of roughly 18. We reduced the font sizes from 23+ to 8.</p><p>We did an inventory of all the icons used within our platform, named, and categorized them based off contextual use and created a standard set of icon sizes that match the defined font sizes.</p><p>We continued to define platform standards for the remaining building blocks such as spacing, gradients, media queries, animation timings, borders, shadows, etc.</p><p>These standardized styles became the Mosaic building blocks. They act as the source of truth and are used to build and maintain order across our products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r-ZYP2b9GA9gHugRXdbdpA.png" /></figure><p>Next phase. We needed to name the building blocks defined in the first phase. To fill the void of a CSS naming convention/methodology we went with BEM. The <a href="http://getbem.com/">BEM naming convention</a> solved a lot of the issues we were having in our CSS. We had inconsistent naming structures, ambiguous class names and classes applied to inappropriate elements.</p><p>Abundant consideration went into naming the SASS variables and when to create a specific targeted variable name versus a more general name. We have some very general variables like $color__green where we style general branding elements and allows us to white label if needed. We also have variables like $color__error which we use for error icons and text. This allows us to target a color change to all error colors with one update. In certain situations we get very specific such as $color__text-field-label which allows us to update all the field labels with one change.</p><p>Once we had defined and named the building blocks, we needed a place to store them. We determined the building blocks should live in JSON files. The JSON data format is easily ingested by multiple systems across Design and Engineering.</p><p>We also needed to structure the JSON file in a way that made it easy for multiple systems to consume. The example object below is from our ui.color-palette.json file.</p><pre>{<br>  &quot;variable_name&quot;: &quot;$color__success&quot;,<br>  &quot;value&quot;: &quot;1fb25a&quot;,<br>  &quot;uses&quot;: &quot;Used for success feedback&quot;,<br>  &quot;category&quot;: &quot;Messaging Colors&quot;,<br>  &quot;sketch_include&quot;: true<br>},</pre><p>The &quot;variable_name&quot; and &quot;value&quot; attributes are used to create SASS variables. All of the values are also read and displayed in our Mosaic Design System website and Sketch plugin, but more on that later.</p><p>SASS variable created from the JSON file.</p><pre>$color__success: #1fb25a;</pre><p>These variable names are baked into both Design and Engineering workflows giving us a common language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e00_17gCMK27kvy48_gN_Q.png" /></figure><p>The living aspect of Mosaic addressed the remaining questions and I will get into detail on that in the next section. A change to a building block value will update that value in all designer files and all product UIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mfW0j2NL6zb9kvSbnMRLZg.png" /></figure><p>With standardization work complete and the main questions answered, Mosaic graduated from boot camp.</p><h3>The Living Solution</h3><p>The living solution allows our UIs to stay consistent across Design and Engineering. We can update multiple products and all our designer files with one change. The graphic below shows the ecosystem at a very high level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0vI_3yKVY1SHp3S4ARMSKg.png" /></figure><p>All of the code, that makes up the living side of the Mosaic Design System, resides in our Mosaic-UI repository in Bitbucket. The Mosaic-UI repository contains the JSON source of truth files defined in boot camp, the SASS partials generated from the JSON, along with other assets. If something needs to be distributed across projects it lives here.</p><p>Adding more detail, the graphic below shows the living aspect of the Mosaic Design System and how Mosaic keeps it together. In the next two sections I will walk through each side of this graphic. I will explain in detail how a change to the source of truth flows through Design and Engineering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cBiqnvP50YsfiFncxCkllw.png" /></figure><h3>Mosaic and Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/165/1*8eIEB23ue5GgeGXJYg8XUA.png" /></figure><p>Mosaic keeps design files consistent across our team. At a high level this is how that happens.</p><p>A value is updated in a JSON source of truth file.</p><p>That update needs to propagate across the design team. Since all designers on our team don’t interact with code I wanted this to be an automated process and not force interaction with Bitbucket.</p><p>Sorry designer friends, it’s about to get technical up in here.</p><p>A simple shell script was created to automate the setup process. This was a one-time setup on every teammates MAC. The shell script generates an SSH key, creates the needed directories, clones our Mosaic-UI Bitbucket repository, and installs a cron job. Using SSH key authentication, the cron job does a git pull (gets latest code) every minute, from the dev branch in our Mosaic-UI Bitbucket repository. If the building block JSON files get updated, those changes will be on all designers local machines within one minute.</p><p>The building blocks are always up-to-date.</p><p>Previously, our design team used assorted applications. Some of us (me) correctly preferred Photoshop while others (you know who you are) incorrectly preferred InDesign. While we agreed to disagree on that, we all agreed on the fact that neither of those tools were meeting all our needs. After some trial runs with various applications we settled on Abstract, Sketch, and InVision as our main design tools.</p><p>The timing of this change, in tools and process, perfectly coincided with the implementation of the living side of Mosaic. This granted me the opportunity to write a custom Sketch plugin to complete the design pipeline.</p><p>I worked with a couple of engineers to get a custom Sketch plugin off the ground. I continued to develop the plugin through the summer of 2017 and learned more than I ever wanted to learn about <a href="https://developer.sketchapp.com/guides/cocoascript/">cocoascript</a>.</p><p>The Mosaic Building Blocks plugin is installed on all our machines. It’s one of the things that makes Mosaic unique.</p><p>When ran, the plugin loops through all the JSON files and renders the data in Sketch. The plugin utilizes all the attributes in the JSON file.</p><p>It displays the &quot;variable_name” and &quot;value” for each defined JSON object. The plugin groups all colors into their relevant &quot;category&quot; and lists the &quot;uses”. Lastly, if &quot;sketch_include” set to true it renders that object in the plugin.</p><pre>{<br>  &quot;variable_name&quot;: &quot;$color__green&quot;,<br>  &quot;value&quot;: &quot;1fb25a&quot;,<br>  &quot;uses&quot;: &quot;Green, don&#39;t use for text. See text colors.&quot;,<br>  &quot;category&quot;: &quot;Base Colors&quot;,<br>  &quot;sketch_include&quot;: true<br>},</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ac1b0aru1cvgA76bzWawQg.gif" /></figure><p>The Mosaic Building Blocks are now viewable within Sketch. Sharing the same source of truth between Design and Engineering creates consistency and enables designers and engineers to speak the same language, while also holding each other accountable. If a designer wants to introduce the 33rd gray into our platform a engineer can call bullshit. If an engineer wants to use a SASS variable strictly defined for text on a background we can call shenanigans.</p><p>The most powerful part of the plugin is the mapping feature. We can map colors and icons from the plugin to colors and icons within our Sketch symbol libraries. The ability to map additional building blocks is in our backlog. Behind the scenes, the plugin creates a unique JSON mapping file for each individual Sketch library document. The contents of the mapping file are similar to below.</p><pre>[{&quot;layer_id&quot;:&quot;F597CBDE-D353-492B-8488-00E889E32965&quot;,&quot;fill_variable&quot;:&quot;$color__icon-default&quot;,&quot;border_variable&quot;:&quot;&quot;,&quot;icon_class&quot;:&quot;glyph__collapse-all&quot;},{&quot;layer_id&quot;:&quot;72EDDE94-A6E6-4EC8-81D2-DFEF3676D960&quot;,&quot;fill_variable&quot;:&quot;$color__text-field-label&quot;,&quot;border_variable&quot;:&quot;&quot;,&quot;icon_class&quot;:&quot;&quot;},{&quot;layer_id&quot;:&quot;F01D4EEB-985A-4849-B841-FF6735244327&quot;,&quot;fill_variable&quot;:&quot;$color__error&quot;,&quot;border_variable&quot;:&quot;&quot;,&quot;icon_class&quot;:&quot;glyph__error&quot;}]</pre><p>A object mapping is created by selecting a layer in Sketch and applying a fill color, border color, or icon. This creates a mapping between the unique &quot;layer_id&quot; (input field, icon, button, etc.) to the &quot;fill_variable” and/or &quot;border_variable” and/or &quot;icon_class&quot;. In the mapping file example above we see the &quot;icon_class&quot; has a value because those unique layers are icons.</p><p>We can check if mappings exist on symbols by selecting their layers and clicking the “Check for Mapping” button within our plugin.</p><p>Below is an example showing the mapping of the $color__button-primary color to a Primary Button symbol in Sketch. And then checking if a mapping exist for the Primary Button layer, which obviously it does because we just mapped it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODgCwURgDi-6zOf_QZ7waw.gif" /></figure><p>We can also select multiple layers and check for mappings. The screenshot below shows that of the 4 layers that were selected in Sketch, 3 of them are mapped to our building blocks.</p><p>This allows us to understand what layers have been mapped to our building blocks without digging through JSON mapping files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3TYj_p5_wjhg0Izq" /></figure><p>Now the best part, because better never stops.</p><p>When the plugin runs it loops through every page, every artboard and every layer, checking if a mapping exists. Each time it finds a layer where a mapping exists, it applies the value from the JSON file to the layer. If the color value in the JSON file changed, that layer gets updated to the new color. If a icon value changed, the layer gets updated to the new icon.</p><p>Let’s say we decided to make our primary buttons blue. We would update the hex value in the JSON file for $color__button-primary. The next time the plugin ran the button color would update to blue.</p><p>This updates the symbol in the library and every designer project using the symbol will get the update.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HcJfMVDeLkRPeFJ_n1ELcQ.gif" /><figcaption>Example of the Mosaic Building Blocks plugin applying color update.</figcaption></figure><p>These mappings only need to be created in our Sketch symbol libraries. The mapping files for the libraries are checked into Bitbucket. A field label color, for example, can be mapped to the plugin. That field label symbol can then be nested into 15 other symbols (select list, text area, type ahead, etc.) using Sketch’s nested symbols. When the field label symbol gets an update from the source of truth, all nested symbols get updated. And every project file, across the team, that is using symbols from the library get updated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i6PDT0JUKmc-QBq6_RCz_A.png" /></figure><p>Previously, if the color of a UI element changed, we would need to manually update all of our files, and hope that we caught every instance of that change. Now we can easily keep our files consistent without relying on memory or manual upkeep.</p><h3>Mosaic and Engineering</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/165/1*F8fvLE2rEdyyqook34S9fQ.png" /></figure><p>Mosaic keeps our UI’s consistent across our products. At a high level this is how that happens.</p><p>A value is updated in a JSON source of truth file.</p><p>The JSON files along with the rest of Mosaic-UI is treated the same as all our code. The code change follows the same pull request (code review) approval process.</p><p>When the code change is merged to the relevant branch in Bitbucket, a build for the Mosaic-UI project is kicked off in Jenkins. The Jenkins build executes the Grunt build within the Mosaic-UI project.</p><p>The Grunt build reads the JSON files and writes SASS files on the fly. These files contain SASS variables and mixins, the building blocks of our design system. These variables and mixins are then referenced throughout Mosaic-UI to create and maintain consistency.</p><pre>$color__orange: #f27d05;<br>$color__orange--dark: #cb6b0b;<br>$color__header-background: #ffffff;<br>$color__header-background--night: #111111;<br>$color__text-field-label: #666666;</pre><p>Similar to our field label example above, if the value of $color__text-field-label variable changes every instance will be updated. There may be 6 components using a mixin similar to below.</p><pre>@mixin text__field-label {<br>color: $color__text-field-label;<br>font-size: $font_size — x-small;<br>}</pre><p>Every component using that mixin is updated with the change.</p><p>At the end of the Jenkins build process, on the master branch, it creates a Mosaic-UI NPM package and deploys it to the Mosaic ProGet feed.</p><p>The package is now updated with any changes.</p><p>Multiple enterprise applications, mobile and our living style guide all consume the Mosaic-UI package and get all updates.</p><h3>Mosaic Living Style Guide</h3><p>Like most companies, we struggled to create a style guide that is up-to-date and easy to maintain. Ours is the by-product of our design system.</p><p>The living style guide lives in our Mosaic Design System website. The Mosaic Living Style Guide consumes the Mosaic-UI NPM package and reads the JSON building block files, to render a up-to-date, low maintenance, consistent style guide.</p><p>It is a reference for Design and Engineering to view our standardized building blocks; color palette, variable names, icons, sizing and spacing variables, etc.</p><p>Our near future plan is for our Angular and React components, styled from our building blocks, to also live on the site. When those components update, so does our living style guide.</p><p>We wanted a style guide that would not become stale and outdated the minute we looked away. One that didn’t need to be manually updated to match style changes. Mosaic’s living system made that possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GXezxV70_Z6UUvFwEyZb8g.png" /></figure><h3>4112 Basic Military Journalism</h3><blockquote><em>“Jesus H. Christ you’re not a writer, you’re a killer.”</em></blockquote><blockquote>-Gunnery Sgt. Hartman</blockquote><blockquote><em>“A killer, yes sir!”</em></blockquote><blockquote>-Private Joker</blockquote><p>So, a killer I will be, as we look to exterminate inefficiency and win this war against inconsistency. With Mosaic, as our ammunition of choice, we will efficiently march forward in perfect cadence. The system is ready and the time is now.</p><p>I am not a writer, I am a killer.</p><p>The passing of Gunnery Sergeant Hartman (Ronald Lee Ermey) on April 15, 2018 coincided with our internal release of the Mosaic Design System. I thought it was fitting to pay tribute to him, or at least try, as I am not a writer. May he rest in peace.</p><blockquote><em>“If God wanted you up there I am sure he would have miracled your ass up there by now…”</em></blockquote><blockquote>-Gunnery Sgt. Hartman</blockquote><p>We cannot expect to win this war without continuing to getting better. Nothing is going to be handed to us. We created the Mosaic Design System to give us the best chance to influence change and solve the problems we were facing.</p><p>Because “better never stops.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5df4a752e9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teletracking-design/mosaic-design-system-living-solution-d5df4a752e9b">Efficient Consistency with the Mosaic Design System</a> was originally published in <a href="https://medium.com/teletracking-design">TeleTracking Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>