<?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 Chris Manning on Medium]]></title>
        <description><![CDATA[Stories by Chris Manning on Medium]]></description>
        <link>https://medium.com/@chrismanning?source=rss-ceb9aa899edc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mMDySJG6tDM733dU-xY4Ug.jpeg</url>
            <title>Stories by Chris Manning on Medium</title>
            <link>https://medium.com/@chrismanning?source=rss-ceb9aa899edc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:53:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrismanning/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[UI Redesign: Updating an e-commerce Site for Better Usability]]></title>
            <link>https://chrismanning.medium.com/ui-redesign-updating-an-e-commerce-site-for-better-usability-4d9a46bfa2ad?source=rss-ceb9aa899edc------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d9a46bfa2ad</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Chris Manning]]></dc:creator>
            <pubDate>Wed, 17 Mar 2021 04:58:28 GMT</pubDate>
            <atom:updated>2021-03-17T04:59:41.605Z</atom:updated>
            <content:encoded><![CDATA[<p>The assignment was to critique a site for its usability from its organizational structure and apply some best practices of user interface structural patterns in a quick redesign.</p><h3>Summary</h3><ul><li><strong>Assignment for UI Design Patterns for Successful Software course</strong></li><li><strong>Objective: Critique ecommerce site on its use of organizational patterns. Redesign problematic patterns to fit recognized best practices.</strong></li><li><strong>UI skills demonstrated: Visual hierarchy, top navigation, spacing of elements, adding obvious controls to slideshow, rearranging mega menu into discernible structure</strong></li><li><strong>Time Spent: 45 minutes</strong></li><li><strong>Tool used: Figma</strong></li></ul><h3>Critique</h3><p>I hope that the designer of this site isn’t attached to their design. As a designer, I am trying to treat each design I create as something of a procedure, a treatment, activities that must be done in sync with development and iterated upon over and over again in service of the product and more importantly of the people using it.</p><p>That said, there are several things that this site could change to make the site more familiar at a glance, help users gain their bearings, interact, and complete their tasks (hopefully for the site that entails making a purchase) quickly and efficiently.</p><p>First, top navigation is messy. Menus don’t line up well, and there is no way to tell what part of the site one is at. The logo for a quick home button is on the left, but its size is distracting from content. ‘My Account’ is on a line above the top navigation. It is on the usual right side, but it’s easy to miss because it’s grey and can easily blend in with browser tabs. The cart icon is unusual. I can tell it is a basket, but most sites use a shopping cart icon reminiscent of grocery carts. For most shoppers, this will be less familiar, putting slightly more cognitive burden on users.</p><p>The hamburger menu doesn’t function as it should and starts and stays open. However, a collapsable menu doesn’t seem advantageous except for on mobile where a menu of that size would need to be collapsable. The organization of the mega menu is confusing at the top, where it repeats the top navigation categories and after that goes in alphabetical order.</p><p>My other problem is the density of information. There have certainly been sites that have far less white space than this, but the density does make focusing on a single product or section challenging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YvVuRfdnAxQU01D2_NA3Jg.png" /><figcaption>There are several issues with this design that could be fixed using some UI organizational principles.</figcaption></figure><h3>Reordering and Streamlining</h3><p>The first thing I did was address top navigation. I shrunk the logo to keep it from distracting from content and moved the menu categories into a single line all spaced out 32px between each. I moved the ‘My Account’ icon in line with top navigation and put the shopping cart next to it. The shopping cart loses the items next to it, but that will be displayed as a red dot with the number of items in the cart. Next to that is the product search box. Having everything in line from left to right is familiar and appealing to the user, keeping their eyes from darting up and down to find what they are looking for.</p><p>Next, I replaced the slideshow with the ‘New Arrivals’ section, but the slides could be inserted just as easily. I added clear navigation buttons so users can go back and forth on their own without waiting for the slideshow to cycle through.</p><p>The last thing I did was look at all the categories under the hamburger menu. I decided that instead of repeating the top navigation bar followed by alphabetical order, it made more sense to arrange them into category groups. The main purpose of the store seems to be for people who want to build their own PC, so I approached it as such with an emphasis on system building.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EbP6cXN1smMuXKj7f6_q6w.png" /><figcaption>Redesign including putting all top menu items in a single row, identifying visually where the user is, back and next buttons for the section that include visual cues letting users know when they are at the beginning or end of the list. The mega menu was further broken down into categories, making it easier for users to find items they are there to purchase.</figcaption></figure><p>This was a quick exercise, but in a short period of time, I was able to address some key issues that together make the site less intimidating and a better experience for users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d9a46bfa2ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Improving the Doctor Patient Communication Experience]]></title>
            <link>https://chrismanning.medium.com/case-study-improving-the-doctor-patient-communication-experience-52798e87fd96?source=rss-ceb9aa899edc------2</link>
            <guid isPermaLink="false">https://medium.com/p/52798e87fd96</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Chris Manning]]></dc:creator>
            <pubDate>Mon, 08 Mar 2021 16:29:39 GMT</pubDate>
            <atom:updated>2021-03-08T16:29:39.799Z</atom:updated>
            <content:encoded><![CDATA[<p>This UX research and design project came about from a combination of experience taking my kids to the doctor and a product design exercise suggestion from <a href="https://productdesigninterview.com/weekly-ux-product-design-exercise">Artiom Dashinsky’s weekly newsletter</a> (which you should totally subscribe to!) His challenge was to redesign the check-in experience at the doctor. I wanted to go beyond just checking in and look at how a patient’s communication with receptionists, nurses and doctors are recorded and shared (or not) and how that could be improved.</p><h3>Summary</h3><ul><li><strong>Personal Project in the medical space</strong></li><li><strong>Objective: Look at how patient communications with staff from appointment booking through the doctor’s evaluation and follow up are recorded and shared and find ways to improve and streamline the experience.</strong></li><li><strong>Process: Interviewed staff at three medical offices; conducted a survey of people who had visited the doctor in the past year two or more times; document current experience, comparing each doctor’s office; read secondary sources from CDC; design new experience.</strong></li><li><strong>Deliverables: User Journey Maps, research report of findings, wireframes of new digital interactions and screens for medical professionals.</strong></li></ul><h3>Gathering Data and Synthesizing Information</h3><p>Speaking to three different receptionists at three different offices, I came away with a fairly uniform process of setting appointments and gathering information about the patient, the reason for their visit and their symptoms. For existing patients, it’s a matter of pulling up their information based on a couple of key identifiers like name and date of birth. After that is a mini triage to determine the urgency of the appointment. If it’s too urgent, they direct the patient to go to the emergency room. If it’s serious, but not life threatening, they may be squeezed in sooner, but if it’s something that can wait, they will schedule them to be seen at an open time slot that works for the patient. They take notes, sometimes able to select common conditions from a drop down or list, other times, just writing the information in the appointment notes. These notes are saved for nurses and doctors to reference when seeing the patient.</p><p>Nurses may see the reason for the visit, but there is a chance they won’t. In either case, they will ask questions of the patient, usually letting them tell the whole situation so they can get an understanding of what is going on without guiding or biasing the patient’s retelling of what is going on with them.</p><p>I couldn’t speak to any doctors, but I was able to get a picture of how those interactions went by speaking with people who had visited the doctor at least twice in the past year. I spoke to five people; two men and three women. From them, I found that three out of five had the doctor ask them about specific things they had spoken to the nurse about, but still had to mostly retell what they had told the nurse. The other two said they had to retell everything they had said to the nurse with the doctor only asking what was going on.</p><p>User surveys of people who self identified as having visited the doctor two or more times in the past 12 months showed that the majority felt like they missed telling the doctor something, or felt rushed. Several mentioned that they felt like they had to repeat several steps each time, from giving insurance and verifying personal information to repeating reasons for their visit.</p><p>I wanted to research information about medical appointments in America and found that some interesting stats:</p><ul><li><strong>84.3% of adults and 93.4% of children had contact with a health professional in 2016</strong></li><li><strong>883.7 million physician visits in 2016</strong></li><li><strong>277.9 visits per 100 people</strong></li><li><strong>54.5% of visits were to primary care physicians</strong></li></ul><p>—CDC National Center for Health Statistics<br>Ambulatory Care Use and Physician Office Visits</p><p>Synthesizing information from interviews, surveys, and secondary data from the CDC, I posited that 883.7 million visits means that <strong>patients had to share their symptoms over 3.5 billion times.</strong></p><h3>The State of Telemedicine</h3><p>Could patients providing information digitally decrease the number of visits to doctors? Meaning, could doctors offices triage patients prior to arriving, giving out prescriptions or medical advice digitally where appropriate?</p><p>Services like Teledoc, Connect Care, Kaiser etc show that virtual doctor visits can work in certain situations.</p><p>How might a doctor’s office adopt a hybrid model to better serve their patients?</p><h3>Starting Point</h3><p>The information I gained from interviews, walking through the process of getting an appointment myself, and survey data led me to map out what the current experience looks like for Carl. Carl is a dad who periodically takes his kids to the doctor. He also sees a sports MD to help with some injuries and like the rest of us, occasionally needs to be seen for an illness.</p><p>His time is valuable to him and he likes to feel that his interactions are authentic but also productive. This is especially true of appointments where he’s checking to see if he has an infection because he just wants to get well so he can go back to being a fun dad who can be active with his kids.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_mGPOKWiemZdiJBNZbOXeQ.png" /><figcaption>Quick sketch of Carl’s user journey. What most struck me was the many times he has to communicate the reason for his visit. This led me to wonder how this might be made more efficient, making Carl feel heard and improving healthcare workers opportunity to dig into what is ailing Carl, leading to better outcomes.</figcaption></figure><h3>Mapping a New Experience</h3><p>Based on the picture I was getting from the research, I decided to map out a possible new experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*h7-vhuabDlGhYE54XilwBA.png" /></figure><p>The main goal of this user experience was to make patients feel that they were being heard, that staff was on the same page, and that they could easily refer back to doctor’s orders.</p><p>I wanted to also wireframe some screens the patient would interact with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D1eCGxzD73i8i-WdCc4Q8w.png" /><figcaption>1. Gives an overview of the interaction with reception along with helpful button for rescheduling as well as a map to the office. 2. Information is already filled in for existing patients with the easy ability to edit anything that may have changed. 3. Shows patient that the receptionist listened to them and invites them to give more information about their symptoms and concerns along with allowing doctor’s office to cover common conditions. 4. Confirmation of appointment, button to add it to calendar, and what to expect next.</figcaption></figure><h3>Next Steps</h3><p>Using the prototyping tool in Figma, I am going to have users test out this appointment confirmation experience. Is this an improvement over having to fill out paperwork at the doctor’s office? What process needs to be in place to ensure a consistent communication experience between nurses, doctors and patients? How can information be best displayed for them in the most readable, at-a-glance way?</p><h3>Takeaways and Learnings</h3><p>The original challenge from <a href="https://twitter.com/hvost">Artiom Dashinsky</a> was just to improve the check in experience. To me, and many of those I interviewed and surveyed, that required further improvements to the way information is gathered and communicated to healthcare professionals and back to patients. This ended up being a lot to bite off for a single exercise that should have taken around eight hours. I’ve put around 12 hours into this project, and foresee at least twice that amount left to fully investigate, design and test all that should go into it. As someone who works 40 hours a week at a J-O-B, that is going to take me a long time. But I plan on continuing as my findings intrigue me and have awakened my passion for improving an experience that is both digital and human.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52798e87fd96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Machine Translation Goes Prime-Time]]></title>
            <link>https://medium.com/swlh/case-study-machine-translation-goes-prime-time-c67e4f89b80a?source=rss-ceb9aa899edc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c67e4f89b80a</guid>
            <category><![CDATA[machine-translation]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Chris Manning]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 05:32:00 GMT</pubDate>
            <atom:updated>2021-03-08T03:04:44.790Z</atom:updated>
            <content:encoded><![CDATA[<p>FamilySearch is a non-profit organization dedicated to helping people discover their family tree. Because of diasporas throughout human history spanning the globe, a person’s family makeup is complex and likely touches several countries speaking different languages. FamilySearch has a goal to make all historical records searchable regardless of language spoken. For FamilySearch’s first ten languages, this was challenging, but straightforward. Expanding the site into an additional 30+ languages in a single year was challenging enough, but there also had to be content in those languages.</p><h3>Summary</h3><ul><li><strong>Company: FamilySearch</strong></li><li><strong>Objective: Get more content to international users faster by using machine translation wherever acceptable</strong></li><li><strong>Process: Evaluate Machine Translation (MT) providers, gather quantitative data on MT performance and qualitative feedback from human translators; find the teams, systems and processes needed to incorporate machine translated content into the site, design solution, prototype, iterate</strong></li><li><strong>Deliverables: Analysis on existing players in MT, process map for MT-led translation, user/volunteer journey map, wireframe of feedback experience</strong></li><li><strong>Team: Rob Thomas, Chris Manning, Dan Call, Bryan Austed, Bryan Robinson and Randy Hoffman</strong></li><li><strong>My Role: Interviewing translators, analyzing data and visualizations from quantitative evaluations, user journey maps, leading design thinking sessions, running pilots with sample data. Design the wireframes for feedback screens</strong></li></ul><h3>Recognizing and Overcoming Objections</h3><p>I was tasked with selecting several machine translation engines to evaluate. The evaluation process included rigorous blind comparisons, feedback gathered from human translators, post-edit distance scores provided by the translation management system as well as a competitive analysis of the different MT providers.</p><p>Translators often have harsh biases against MT, partially due to the perceived threat to their continued livelihood. Getting them on board and feeling comfortable with these new MT engines was of the utmost importance. Since one of the main goals was to increase translation output, I was able to frame discussions with translators as evaluating potential aids for increasing their efficiency. This not only alleviated potential distrust, but also made translators excited to share their opinions with us.</p><h3>Evaluation Results</h3><p>By comparing MT providers A, B, and C, including limited training data sets fed to each engine we were able to determine that <strong>segments from engine C were preferred 54% of the time over the other engines.</strong></p><p>More importantly, comparisons showed that <strong>providing training data to the engine improved output between 2–4x depending on language. </strong>With this data, we were able to get executive buyoff to start a pilot with MT-led translation of content.</p><h3>Analogies from Software Development</h3><p>FamilySearch is an engineering-led organization. Like most modern software companies, they divide their work up into sprints. At FamilySearch, strings are already translated this way, being fed to the Translation Management System (TMS) from the Github repository whenever there is an update. I thought about taking this further and presented it to management.</p><p>There is an adage in the industry, “Shipped is better than perfect.” That has never applied to translation where every phrase and word is highly scrutinized. We identified low-risk content—geographic and historical facts based on country—that could be published immediately after MT. Content would be identified as translated by machine with an option to provide feedback on the translation. That way, content would go up quickly, and could be iterated on as feedback came in.</p><p>I explored two different methods of providing feedback, mapping both out in a user flow and architectural diagram.</p><p>The first was to simply give users a thumbs up, thumbs down on the content. Pros: very simple for users to engage, we would get more users to inform translation quality, and content reviews could be triggered by reaching a threshold of negative feedback. Cons: difficult to pinpoint specifically what users are referring to, reviewers would have to review the entire page.</p><p>The second method involved designing a feedback module that was more robust. It allowed users to offer an alternate translation, replace words, or even contribute their own content about their ancestors. This would create a brand new point of contact between users and FamilySearch. Pros: user feedback would be more specific, users who engaged may develop a sense of ownership and community because of their involvement. Cons: fewer users might contribute feedback, more detailed tagging of content would be required from the TMS so that segments identified by users could be mapped back to the same segment for review, which would require dev work from our TMS vendor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T6a38pQPC6ia59WO_9ZuzA.png" /><figcaption>Flowchart with wireframes of feedback module.</figcaption></figure><h3>Prototype Pilots</h3><p>We decided to set up small prototype projects to test both options with test groups. The scope of each was to use a small subset of content (10,000 words) in two of our largest established languages plus our new top priority language. I ran the content through machine translation and published it to two different pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*MsX6Ob1yC1ANLTG7rOznbw.png" /></figure><p>The first option was a simple thumbs up, thumbs down feedback module. Results were tallied in the CMS as an object, borrowed from the Help Center’s feedback module. Users liked the simplicity, but some commented that there wasn’t any way to elaborate, a concern we had had going into the prototype.</p><p>The second option was presented in wireframe so that we could get it out at the same time as the simple feedback module. It provided users the opportunity to basically edit the translation themselves. In the prototype, it didn’t link back to the TMS, but all edits were saved to a spreadsheet where they could be reviewed and pasted into the TMS later. It also provided users a way to give general feedback about the content. At the time, we were concerned about some of the content that had been created giving too much of a western point of view and thought the ability to give feedback in general would be of value. Lastly, we gave users the option to contribute their own content, upload media, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*sARJgVgdyLW6FpFyH3zCTQ.png" /></figure><h3>Learnings and Takeaways</h3><p>The feedback we received from our volunteer users, as well as product owners showed us that a combination of the two options would be best. We have shelved building it until the dev work needed to send user translation changes directly to the TMS can be done. And though the feature hasn’t been implemented, it gave FamilySearch confidence to use machine translation more agressively. The annual conference FamilySearch puts on, RootsTech, had all of the presenter bios go through machine translation and then reviewed by volunteers—many of whom only spoke the target language and were only reviewing to make sure the translation made sense and didn’t contain anything strange or offensive.</p><p>More importantly, it lead to highly innovative new ways to train MT and utilize locally sourced content as ways of improving future MT. There is a lot of potential in our learnings that could lead to a huge boon for the field of MT and neural systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wXjq9y7QJ6qv2M0PHi_mYg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c67e4f89b80a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/case-study-machine-translation-goes-prime-time-c67e4f89b80a">Case Study: Machine Translation Goes Prime-Time</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Employees are users too]]></title>
            <link>https://medium.com/design-bootcamp/employees-are-users-too-45b50191401e?source=rss-ceb9aa899edc------2</link>
            <guid isPermaLink="false">https://medium.com/p/45b50191401e</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Chris Manning]]></dc:creator>
            <pubDate>Thu, 25 Feb 2021 17:17:45 GMT</pubDate>
            <atom:updated>2021-03-08T03:16:03.478Z</atom:updated>
            <content:encoded><![CDATA[<p>Most of my career has been spent building and managing tools designed to be used for fellow employees to aid them in creating marketing content, build the company website and access creative assets. For the first bit, I created training documents and videos to aid users in navigating the tools. View and download numbers showed that the tool was only being used by a small percentage of users. I wanted to discover where my users were coming from, and meet them there, becoming a bridge for them to accomplish objectives and achieve company goals.</p><h3>Summary</h3><ul><li><strong>Company: NuSkin Enterprises</strong></li><li><strong>Objective: Increase usage of Asset Library, (Digital Asset Management tool) especially with new assets</strong></li><li><strong>Process: User surveys, user interviews, analytics, card sort activity, user journey map</strong></li><li><strong>Deliverables: New taxonomy and tagging system, new content newsletter template</strong></li><li><strong>My role: Interview country offices and corporate staff to determine the needs of users, write and conduct surveys, lead card sort activity, analyze feedback, create new taxonomy and architecture, wireframes</strong></li></ul><h3>Mind the Gap</h3><p>You may have come across this before: The executive team has a goal and objectives they want employees to hit, but the tools available to them and infrastructure force employees to change the way they work to fit tools and processes instead of playing to the employees’ strengths and using them to the fullest.</p><h3>My Research Process</h3><p>I started to see that tools I managed weren’t being used and creative assets weren’t even being seen. I began by sending out user surveys to staff about their experience with the digital asset management system and learned that the way it was organized did not match the way they organized their work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5_j_Sc8pBsjDZFcDhetz2g.png" /></figure><p>I then conducted a card sort activity with several different groups from area marketing to R&amp;I to legal. I had them identify a wide range of assets from images, to white papers, to videos; using post-it notes to label and group assets together. I was able to take the information gained to come up with new asset categories and tags that made finding and discovering assets easier and fit with the way staff worked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kk1E0WpWurq1iHG56vQ1IA.png" /></figure><p>Instead of being arranged only according to asset type or function, tags were created so users could see assets sorted based on a variety of filters that organized assets in ways that made sense for particular roles or jobs to be done. I hadn’t yet heard of the <em>jobs to be done</em> theory but making assets available in this way accomplished this for the majority of our internal users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JoMN0V34bZKj_78EjDy8Eg.png" /><figcaption>Assets used to be split up by asset type (images, videos, PIPs, etc.). Under the new taxonomy, product lines reign. It became simpler to filter by asset type and drill down into assets a user needed access to.</figcaption></figure><p>Reorganizing and tagging content made a huge difference but new content that was part of marketing campaigns wasn’t featured in a significant way, wasting valuable creative and marketing resources. To solve this, I held 1:1 interviews with key users throughout the organization to ascertain how they were choosing content for their local marketing microsites, print pieces, and presentations. It became clear that users were not able to consistently see when new content was added. I explored several solutions with our developers, but they were all rejected over budget and time constraints. I met with our marketing team and realized we had the solution right in front of us.</p><h3>Experience Goes Beyond the Tool</h3><p>Marketing teams know who their customers are. They craft content to reach them. We were doing that for our customers but forgetting to communicate internally with staff that relied on global marketing to do their jobs. I came up with a solution that involved using filters to batch new content by date and designed a newsletter template for new content that I began sending to staff on a weekly basis that corresponded with the content calendar. Staff loved this and felt like they were able to stay on top of the global strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a1idy9WiamNX7au-VkF5kg.png" /></figure><p>Staff began participating in weekly marketing updates more proactively. They came with questions about content for the next several weeks, examples of things they had created with creative assets for their local markets. This allowed management to address issues better and direct staff on how to work towards company objectives.</p><h3>Learnings and Takeaways</h3><p>Marketing staff in field offices wear a lot of hats. They don’t have the bandwidth to seek new assets amongst all the others. In addition to needing to be able to quickly find what they are looking for by product type, need to know <em>when</em> there are new assets. But marketing isn’t the only group using Asset Library. Other groups search for assets very differently and need to be able to quickly filter for the type of asset they are looking for instead of only seeing a product-focused taxonomy.</p><p>Without a big budget, my options were limited. In order to solve the problem my users had, I had to look outside of the box and look at the <em>process</em> of accessing new assets, which led to the creation of the newsletter. It linked to each new asset and improved their ability to take proactive action with them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45b50191401e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/employees-are-users-too-45b50191401e">Case Study: Employees are users too</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>