<?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 Kathleen Anderson on Medium]]></title>
        <description><![CDATA[Stories by Kathleen Anderson on Medium]]></description>
        <link>https://medium.com/@kathleenandersonn?source=rss-2f711965ccbc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vP9CqpysndYTT39q6oaCvg.jpeg</url>
            <title>Stories by Kathleen Anderson on Medium</title>
            <link>https://medium.com/@kathleenandersonn?source=rss-2f711965ccbc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:32:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kathleenandersonn/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[When Place Changes Perspective: How Our Abroad Designers Shape Work at SAS]]></title>
            <link>https://medium.com/sas-software-design/when-place-changes-perspective-how-our-abroad-designers-shape-work-at-sas-ae188fd95c0e?source=rss-2f711965ccbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae188fd95c0e</guid>
            <category><![CDATA[perspective]]></category>
            <category><![CDATA[flexible-work]]></category>
            <category><![CDATA[working-abroad]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[product-designer]]></category>
            <dc:creator><![CDATA[Kathleen Anderson]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 16:11:56 GMT</pubDate>
            <atom:updated>2026-03-02T16:11:56.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KjEavi4ZUjLSrweNllDUYA.png" /></figure><h3>When Place Changes Perspective: How Our Abroad Designers Shape Work at SAS</h3><p>Over several decades, a handful of SAS’s User Experience Designers have relocated from the US to Europe. This experience has expanded their perspectives, influenced their work, and allowed them to embody SAS’s flexible, world-class environment that inspires innovation.</p><p>I’m one of these designers. In sharing our stories, I hope to highlight the incredible impact cross-country collaboration has on personal growth, professional expertise, and teamwork.</p><h3>Meet our designers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FP6HmKNkhJjBZGQJ9dzpNw.png" /></figure><p><strong><em>Thor</em></strong>: Principal UX Designer. From Olafsfjord, Iceland. Lived in the United States for 25 years. Currently lives in Copenhagen, Denmark.</p><p><strong><em>Maribel</em></strong>: Principal UX Designer. From Baltimore, Maryland. Currently lives in Helsinki, Finland.</p><p><strong><em>Mike</em></strong>: Head of User Research and UX Designer. From Narragansett, Rhode Island. Currently lives in Heidelberg, Germany.</p><p><strong><em>Kathleen</em></strong>: Associate UX Designer. From Philadelphia, Pennsylvania. Currently lives in Glasgow, Scotland.</p><h3>Why move abroad?</h3><p>Living abroad provides experiences different from those offered by life in the United States. One designer may move to immerse themselves further in a new language and culture, while another seeks flexibility to make their dream of traveling through Europe more accessible. Moving allowed Thor to support his spouse’s career, which brought her to Denmark, and to more easily visit family in Iceland. Maribel found herself looking for a new home that would reflect the kind of society she wanted to live in:</p><p><em>“The priorities of Finland, in terms of its foreign policy, domestic policy, social safety nets, security, all aligns far more closely with [my wife’s and my] values and ethics than present-day US.” — Maribel</em></p><p>I personally moved abroad in hopes to expand the world as I know it. Spending most of my childhood and college years on the East Coast, I knew there was so much of the world I’d yet to explore, and so much to gain from participating in new experiences. Relocating to Glasgow pushed me outside my comfort zone in more ways than I could have imagined, and I’m a stronger, more confident person for it!</p><p>While our individual reasons vary, we all found ourselves pulled across the Atlantic in pursuit of opportunity.</p><h3>Gaining different perspectives</h3><p>Experiences in new countries help us to see and interact with the world from different perspectives:</p><p><em>“You’ve never really experienced another culture until you speak their language.” — Mike</em></p><p>Those of us born in the States voice how these experiences helped rewire our American-centric mindsets, challenging our assumptions and changing our relationships with people, places, and things.</p><p>This shift in perspective provides us with a deeper understanding of culture differences, and the important role these play in social situations. Tailoring interactions to the customs of those you’re communicating with allows for deeper, more meaningful connections. I personally value timeliness with friends and colleagues from the Nordics, and the power of sharing a good laugh with those from the UK.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aj-2UmoTiYp_Y52kTJNzpg.png" /><figcaption>Our Europe-based designers celebrating the holidays with a Pikkujoulu (“little Christmas in Finnish!”)</figcaption></figure><h3>A culture revolving around flexibility</h3><p>SAS prides itself on providing a “<a href="https://www.sas.com/en_gb/careers/culture.html">flexible work environment offering personal choice in how and where we work</a>.” We embrace this opportunity to shape our lives with intention. One way this manifests is by shaping our schedules around our most productive hours and building in time for midday fitness classes or workouts:</p><p><em>“This flexibility allows me to pick an optimal time to go to the gym, which ultimately is good for the company because it helps me stay energetic and fit while taking less time than if I went during rush hour.”</em> <em>— Thor</em></p><p>Besides allowing us to lean into our preferred work patterns and healthy habits, this flexibility more broadly enables us to prioritize the people and commitments that matter most. For Thor, this flexibility made a “tremendous difference” in his personal life, as he could support his wife’s move to Europe for a new job. Being EU citizens made the move for them relatively simple, but it helped that his manager and SAS were also very supportive. Mike and I, both avid travelers, also have the freedom to pursue our travel goals while balancing our adventures with deadlines.</p><p>While living abroad grants us flexibility, it also asks us to extend the same in return. Working in teams spread across different time zones requires our adaptability. For some, this looks like dedicating mornings to uninterrupted design time and leaving the afternoon free for meetings with colleagues in the US. For others, it means adjusting work hours entirely, starting the day earlier or ending later to accommodate cross-continent collaboration. To us, flexibility is a mutually beneficial two-way street.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vc1vDHyK72trYOG0DZEeog.png" /></figure><h3>Designers as champions &amp; storytellers</h3><p>We are in a unique place, living in Europe but with strong ties to the US, where most of our designers reside and where SAS is headquartered. This puts us in a special position:</p><p><em>“The [European] design team is smaller, but we play such a big role. We are advocates that can represent varying regions and the differences that might happen between the regions, which is incredibly nice to have.” — Mike</em></p><p>Mike, accustomed to German, understands the accessibility and visual design issues that come along with this compound language, and incorporates solutions that accommodate its longer, denser words. These solutions often affect the layout and usability patterns for the entire design team, worldwide. In this way, we are champions of usability, speaking up to make sure SAS’s designs are consistent across languages and regions.</p><p>Designers are known for wearing many hats. We’re analysts, advocates, strategists, among many roles. At SAS, a particularly important hat is that of a storyteller. Stories are at the core of effective communication; they drive how users connect with our products and make sense of information.</p><p>Stories also influence our organization, shaping the way we exchange ideas, celebrate wins, and align globally. Maribel makes an intentional effort to report on company wins in Finland, even if they’re not design-related. She takes her role as a storyteller very seriously, finding it crucial to promote the contributions of all colleagues, especially considering that — culturally — it is not Finnish nature to boast about accomplishments:</p><p><em>“We must share our stories. We have to. I think those of us from the US who are now starting to scatter around the world, we are the ambassadors because Cary is still [the company’s] nucleus. When your crew has a big win, whether or not it has anything to do with design, it doesn’t matter, share it!” — Maribel</em></p><h3>Contextualising our user experiences</h3><p>Often, the offices abroad we work in are not design hubs. For a company as large as SAS, this is a prime opportunity for us to connect and converse with colleagues from across different departments — marketing, sales, IT support, etc. — that we perhaps wouldn’t encounter in the US:</p><p><em>“It gives you stronger sense of purpose in your design to know people that are talking with customers daily. Being in [the Copenhagen office], you really sense the urgency behind the needs of customers, their requirements, their likes and dislikes. You don’t feel like you’re designing in isolation for some theoretical customer out there.” — Thor</em></p><p>Designers aren’t intended to work in isolation. Staying in constant touch with customers and markets is crucial for understanding the realities in which our products exist. Our offices abroad enable us to bridge gaps between design thinking and real-life use cases, so we can build better user experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*asfwsngnQbhmVEx02bWS2Q.png" /><figcaption>Maribel visiting Thor in Copenhagen</figcaption></figure><h3>Values we live by</h3><p>A popular mantra at SAS reads, “our culture — more than a job, an experience.” For those of us abroad, this is more than just a slogan. We bring these words to life:</p><p><em>“There is a push for us to work hard but have a life outside of work.” — Kathleen</em></p><p>I find this balance crucial, finding that I’m more motivated to tackle my design tasks when I have the time to pursue goals outside work, too. We are multifaceted, devoting ourselves to life and work in a way that strengthens both.</p><p>Culture depends heavily on the people who partake in it. For Thor, there’s a series of traits he’s seen in colleagues across the world in his many years working at SAS. Enthusiasm, authenticity, friendliness, and curiosity are qualities he often encounters, which makes SAS feel like not just a company, but a community:</p><p><em>“There are definitely differences between the cultures in the offices. But as one of my colleagues said recently, there is such a thing as a SAS personality. There is something more genuine about the culture here than I’ve felt elsewhere.” — Thor</em></p><h3>The power of cross-country collaboration</h3><p>While we moved with different motivations, Thor, Maribel, Mike and I are all connected by our passion for design and commitment to SAS. Time spent living in the US and abroad equips us with a unique set of experiences and perspectives that strengthens our entire design team. We are better positioned to confront culture nuances, market differences, and align with colleagues across the world. This article is, above all, a testament to the power of cross-country collaboration, and the impact it has on individuals and entire teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae188fd95c0e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sas-software-design/when-place-changes-perspective-how-our-abroad-designers-shape-work-at-sas-ae188fd95c0e">When Place Changes Perspective: How Our Abroad Designers Shape Work at SAS</a> was originally published in <a href="https://medium.com/sas-software-design">SAS Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to be a better fact-checker]]></title>
            <link>https://medium.com/@kathleenandersonn/how-to-be-a-better-fact-checker-062674e00e7d?source=rss-2f711965ccbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/062674e00e7d</guid>
            <category><![CDATA[fact-checking]]></category>
            <category><![CDATA[misinformation]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[media-literacy]]></category>
            <dc:creator><![CDATA[Kathleen Anderson]]></dc:creator>
            <pubDate>Thu, 23 Jan 2025 14:09:56 GMT</pubDate>
            <atom:updated>2025-01-23T14:10:47.588Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ferUp3MgqW07l1w-XCnu4g.png" /></figure><p>Coincidentally, I finished reading <em>How to Lie With Statistics</em> by Darrell Huff the same week <a href="https://www.nytimes.com/live/2025/01/07/business/meta-fact-checking">Meta announced it will end its fact-checking program on social media posts</a>. This book’s examination of the subtle ways statistics can manipulate our understanding of facts and figures felt incredibly timely.</p><p>Meta — or more aptly Zuckerberg’s — decision to end fact-checking will only exacerbate the issue of massive, continuous, unregulated streams of information available for consumption on social media.</p><p>This is problematic for many reasons, including:</p><ul><li>The emphasis on short-form content means information distributed via social media platforms like Instagram, X, and TikTok is not usually as comprehensive as information found through traditional news outlets.</li><li>Inaccurate news emerges from an overwhelming number of unqualified sources, prompting <a href="https://www.apa.org/topics/journalism-facts/misinformation-disinformation">mis- and disinformation</a>.</li><li>The passive way in which we often consume content on social media makes us more susceptible to believing what we see without questioning.</li></ul><blockquote>“The secret language of statistics, so appealing in a fact-minded culture, is employed to sensationalize, inflate, confuse, and oversimplify.” –Darrell Huff</blockquote><p>We can do a better job at being our own fact-checkers, though. Learning to spot how statistics on social media can manipulate our understanding of a certain subject or event is a good place to start.</p><p>While <em>How to Lie With Statistics</em> was published in 1954, I believe many of the concepts Huff explains in his book are incredibly useful for helping us fact-check in our current digital environment.</p><h4>Samples with built-in bias</h4><p>Often, when we see a statistic on social media, we’re only given a link to its source, if that. This leaves us with little to no idea <em>how</em> the statistic was computed.</p><p>Huff writes, “the result of a sampling study is no better than the sample it is based on.” Dependability can be skewed by visible biases like small sample sizes, non-random sampling, or lack of diversity. It can equally be skewed by invisible biases like non-responses, industry/funding interests, or cultural norms.</p><blockquote>A TikTok influencer claims that “AI resumes receive 75% more job callbacks,” but omits how this statistic comes from a study focused solely on entry-level tech jobs. Therefore, this percentage is not an accurate measure across industries and experience levels.</blockquote><p>It’s best to allow some degree of skepticism whenever there’s a possibility of bias in a study — especially when you don’t know exactly how the figure was calculated. Don’t trust social media statistics wholeheartedly. The nature of short-form content often lends itself to a lack of context, even if unintentionally.</p><h4>The well-chosen average</h4><p>Many people use the word “average” interchangeably with “mean,” but the two are not synonymous. “Average” has a much broader meaning, encompassing mean, median, and mode. Which average a statistic represents can make all the difference in interpreting its meaning.</p><blockquote>An Instagram reel claims, “The average salary for entry-level tech jobs is now $120,000.” If this figure refers to the mean, it could be inflated by a small number of high earners, with the majority earning much less than the “average” salary indicates. This creates an unrealistic picture of tech salaries.</blockquote><p>The type of average chosen to illustrate a figure isn’t random — it’s often picked to make the data look more favorable. Watch our for unnamed averages. “Average” isn’t a helpful term unless you can determine <em>what kind</em> of average it is and analyze the statistic suitably from there.</p><h4>When correlation isn’t causation</h4><blockquote>A post on X claims, “Statistics show that the rise in AI use is causing widespread job losses.” How reliable is this conclusion? While AI can automate certain tasks, job losses might also be influenced by non-AI-related factors. Economic downturns, shifting industry demands, or company cost-cutting strategies could also contribute.</blockquote><p>The correlation between rising AI use and job losses does not automatically imply causation. According to Huff’s logic, it’s probable both are products of a third unnamed factor.</p><p>Watch out for statistics that could be products of ongoing trends or broader societal shifts, rather than genuine cause-and-effect relationships. Statistics don’t always tell the entire story.</p><h4>Top tips to be your own fact-checker</h4><ol><li>Understand that statistics can’t always be taken at face value. Facts and figures may be manipulated to prove specific points, especially in this polarized age.</li><li>Try to identify how the statistic was computed. What was the sample size? Was it inclusive? Could biases be manipulating the results?</li><li>If a post links to a source, check to see if it’s from an established outlet. If so, read/watch/listen to the original source instead. Social media can be a great tool for referring us to other, more reliable informants.</li><li>When something catches your eye, dig deeper. Seek out credible sources instead of simply regurgitating information you see in your feed.</li><li>Think critically about the facts and figures you encounter. Ask yourself question like, “Does this statistic seem plausible?”, “Am I missing important context?”, “How might the wording of this post influence its meaning?”</li></ol><p>This article focuses mainly on fact-checking statistics on social media, but the bottom line holds true for all the content we consume on social media: be skeptical, think critically, and make sure you understand the full picture. We must go the extra mile to ensure we form the most accurate and informed conclusions possible.</p><p>I’m Kathleen, a current Cornell student studying Information Science. I enjoy learning and writing about product design and AI ethics.</p><p>Find me on <a href="https://www.linkedin.com/in/kathleen-anderson-97ab69203/">LinkedIn</a> here!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=062674e00e7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Product Design & A UX Approach to the Future of Data]]></title>
            <link>https://medium.com/sas-software-design/data-product-design-a-ux-approach-to-the-future-of-data-9f10c8a867bd?source=rss-2f711965ccbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f10c8a867bd</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Kathleen Anderson]]></dc:creator>
            <pubDate>Mon, 09 Sep 2024 16:20:26 GMT</pubDate>
            <atom:updated>2024-09-09T20:02:04.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7COjjW-vr-JMJc2jeBOt3A.png" /><figcaption>Image generated via Microsoft Copilot</figcaption></figure><h3><strong>Introducing data products</strong></h3><p>Despite significant changes in the data management lifecycle over the past few decades, the goal to optimize this process for better data, insights, and business outcomes remains. There exists an abundance of literature on the topic, with new ideas emerging to meet the evolving requirements needed to see this lifecycle succeed.</p><p><strong>One widely discussed idea on how to revolutionize the data management process is data products.</strong> While the idea of treating data as an asset has been discussed in various ways over the past decade, the term “data as a product” can be traced back to Zhamak Dehghani’s 2019 article <a href="https://martinfowler.com/articles/data-monolith-to-mesh.html"><em>How to Move Beyond a Monolithic Data Lake to a Distributed Data Mesh</em></a>.</p><p>Dehghani identifies data as a product as a core principle in her concept of data mesh. Her overarching idea is that “domain data teams must apply product thinking with similar rigor to the datasets they provide; considering their data assets as their products and the rest of the organization’s data scientists, machine learning and data engineers as their customers.”</p><p>Product thinking, with its emphasis on solving problems and delivering value for users, would revolutionize the data management process. <strong>By viewing data as a product that needs to be managed, maintained, and optimized just as physical products are, this transforms the way users think and use data. </strong>Dehghani goes on to specify some important elements for data products:</p><p><em>1. Qualities to define the user experience</em><strong>: </strong>Dehghani defines eight characteristics for successful data products:</p><p>Discoverable: Consumers, engineers, and scientists should be able to locate a dataset easily, so that it can be more quickly understood and consumed.</p><p>Addressable: Data products should have a unique address and share common conventions so that, once located, users can programmatically access them.</p><p>Trustworthy and truthful: Each data product should establish and guarantee its intended level of integrity and accuracy through a set of Service Level Objectives (SLOs).</p><p>Self-describing semantics and syntax: Data products should be built so they are easy to use, and can be independently discovered, understood, and consumed.</p><p>Inter-operable and governed by global standards: The key to effectively correlating data across different domains lies in adhering to specific standards and harmonization rules. These standardizations should be governed globally to ensure interoperability between diverse, multilingual domain datasets.</p><p>Secure and governed by global access control: It is essential to access data products securely.</p><p><em>2. Cross-functional teams</em>:<strong> </strong>Another crucial component of data products is the people who work with them, data product owners and data engineers. Dehghani imagines data product owners managing the vision, roadmap, and lifecycle of data products. They ensure consumer satisfaction by defining success criteria and KPIs (key performance indicators) and continually monitoring data for quality improvements. She stresses the importance of removing specialized silos to broaden the organization’s overall skillset. To ensure a successful, well-rounded product, different teams need to contribute their skills and perspectives — this is no different for data products. No collaboration prompts imbalanced products and unsatisfied consumers, but “cross-skill pollination” helps organizations build better, higher quality data assets.</p><p><em>3. Data infrastructure as a platform: </em>To eliminate the duplicated effort and skills needed to operate the data pipelines’ (series of processes that automate the extraction, transformation, and loading (ETL) of data from various sources to a destination for analysis or storage) technology stack and infrastructure in each domain, organizations can build data infrastructure as a platform. The keys to creating this infrastructure are “(a) to not include any domain specific concepts or business logic, keeping it domain agnostic, and (b) make sure the platform hides all the underlying complexity and provides the data infrastructure components in a self-service manner.”</p><p><strong>While data as a product may initially seem like a technical solution to be implemented on an architectural level, upon further evaluation, we see that this concept is grounded in the strategy of applying product thinking to datasets.</strong> Dehghani’s recommendations of promoting consumer satisfaction, uniting teams, and designing a self-service platform are all tasks that UX design can facilitate, decoupled from platform architecture.</p><p>So, might there be a way to implement data products into the data management process without needing to completely reconstruct the architecture underneath, by focusing on a UX-oriented solution to the problem?</p><h3><strong>What problems do data products solve?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PMQBI8AVK2qvYmyQkIfcUw.png" /><figcaption>An example of siloed ownership, the separation of technology from business departments. Image by <a href="https://www.linkedin.com/in/kathleenandersonn/">Kathleen Anderson</a></figcaption></figure><p>To effectively implement data products as a solution, it is essential to first understand what problems they must resolve. Where do these problems originate in the broader data management system? Rather than addressing surface-level issues, the goal is always to design solutions for root causes.</p><p>In the process of identifying problems, patterns often emerge. While conducting multimethod research, one such pattern repeatedly appeared in our investigation of academic writing, articles by thought leaders in the data product space, and conversations with subject matter experts here at SAS. This problem is: siloed and hyper-specialized ownership.</p><p>Dehghani mentions siloed and hyper-specialized ownership as a shortcoming of the current enterprise data platform architecture in <a href="https://martinfowler.com/articles/data-monolith-to-mesh.html"><em>How to Move Beyond a Monolithic Data Lake to a Distributed Data Mesh</em></a><em>.</em> <strong>The issue is: when the teams who build and own data platforms are hyper-specialized and siloed from the operational units where data originates and is used, this results in engineers who lack business and domain knowledge.</strong> Dehghani contends that engineers “need to provide data for a diverse set of needs […] without a clear understanding of the application of the data and access to the consuming domain’s experts.” Operating in their own spheres with little to no communication with outside teams, organizations struggle to provide accurate and meaningful data.</p><p>Chad Sanderson and Mark Freeman similarly discuss the detriment of siloing in their book <em>Data Contracts</em>. When teams split into multiple silos with different strategies and work less closely to one another, this leads to a breakdown in communication causing data quality problems known as “Garbage In, Garbage Out” (GIGO). Sanderson and Freeman warn that GIGO can cost organizations in a multitude of ways, including lost revenue, operational inefficiencies, and customer dissatisfaction.</p><p>When I spoke with data management subject matter experts (SMEs) at SAS, people who talk with customers about their pain points daily, the issue of siloed work also emerged. Often, organizations begin the data management process by onboarding and analyzing large amounts of data. This makes it hard to decipher what data is important to an organization, and what is just cluttering up the pipeline. Hence, organizations suffer GIGO problems exactly like the ones Sanderson and Freeman mention.</p><p><strong>The bottom line is data without purpose is meaningless. Data needs to serve a specific function within the context of the organization; therefore, it is important to attach business objectives to data early in the data management pipeline.</strong> This attitude is mirrored by Dehghani’s concept of data product owners, those who give data purpose by furnishing it with a vision and KPIs, as well as monitoring its journey through the pipeline.</p><p>While data quality is the surface-level problem that data products solve, the root cause of this problem runs deeper. It stems from a disconnect that Dehghani summarizes well: “Current architecture and organizational structure does not scale nor deliver the promised value of creating a data-driven organization.”</p><h3><strong>How DO you create a data-driven organization?</strong></h3><p>Siloed and hyper-specialized ownership is a large problem for many organizations, one that has little to do with the underlying architecture that data management system runs on, but rather the <em>people </em>who attend to the system. Engineers are isolated from other engineers, and business stakeholders are not collaborating with technical users to make sure data entering the pipeline has a purpose.</p><p><strong>I argue that a UX-forward approach to implementing data products into the data management lifecycle presents a new perspective on a widely discussed pain point.</strong> This approach would align teams in a way that is decoupled from the platform architecture, without requiring an overhaul of the system’s foundations.</p><p><strong>What I imagine is a solution that enables data products to act as bridges that unite people, facilitating communication and collaboration between typically separate teams, a connection that translates to meaningful, data-driven business objectives established at the beginning of the data management lifecycle.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2VJ3q05b2xjgi8EiUFLVCw.png" /><figcaption><em>With the correct implementation, data products can serve as the bridge between business and technical stakeholders. Image by </em><a href="https://www.linkedin.com/in/kathleenandersonn/"><em>Kathleen Anderson</em></a></figcaption></figure><p>My theory, based on the research my team conducted, is that if the people who attend to data along the pipeline do not work together, it doesn’t matter how much work you put into perfecting the architecture and underlying platform, there will still be problems. This is because the true value of data cannot be fully realized without people making sense of where it fits into real-world objectives.</p><p>So, what if we started by tackling the people-oriented issue of siloed and hyper-specialized ownership? Then, after resolving this, address any remaining — and likely fewer — issues?</p><h3><strong>Implementing data products with a design-first strategy</strong></h3><p>This summer my team focused on integrating data products into Information Catalog, a SAS-designed tool that helps users organize, manage, and discover data assets within their organization by providing metadata management and search capabilities. While we imagine data products to be present throughout the pipeline, I selected one specific problem to solve: the siloing of business stakeholders from technical users.</p><p><strong>This project provides a different, human-centered approach to implementing data products. I present the following examples to demonstrate how data products can be imagined as a user experience. This makes the data management lifecycle a more accessible process, with the goal of facilitating collaboration, ensuring trustworthy data that provides meaningful insights to an organization.</strong></p><p>The following are some important attributes of our data product concept.</p><h3><strong>A new way to define and monitor data</strong></h3><p>Early on, it became clear that data products would exist as an entirely new feature within Information Catalog. After attaching the dataset(s) to a data product, the product serves a “container” that facilitates all data-related operations.</p><p><strong>The main aim here is to create cross-organization collaboration that inspires meaningful data collection and governing, to help businesses maximize opportunities and reach their goals.</strong></p><p>What would this look like? We worked to create a feature where users can collaboratively define and manage data products. Carefully making design choices to ensure that both technical and non-technical stakeholders can navigate the feature easily, we aimed to ensure alignment, clear communication, and transparency, so that data can be managed and used to its fullest potential.</p><p><strong>The ultimate job of data product pages is to allow users to find data, develop requirements for their data needs, and subsequently govern this data responsibly and effectively.</strong></p><h3><strong>Begin with business objectives</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r_KjSb-oUjC9_3ZvEQwLvQ.png" /><figcaption>Business objectives importantly inform other parts of the data pipeline. Image by <a href="https://www.linkedin.com/in/kathleenandersonn/">Kathleen Anderson</a></figcaption></figure><p>It is no good for engineers to commit time and effort delivering data from one end of the pipeline to the other just to be told by the business “this isn’t what we want.” This is inefficient and a waste of time, ultimately hurting organizations.</p><p>Business stakeholders must define their objectives early in the data management lifecycle to ensure that the work the engineers do provides meaning to the organization. Drawing on Dehghani’s idea of data product owners, <strong>we wanted to design a process with a designated space for business-oriented users to think about organizational impact and specify what data they need to further their objectives, such as creating financial reports for clients or complying with audits.</strong></p><p>We decided to integrate this process into the creation of data contracts. Typically created at the beginning of the pipeline, these contracts serve as formal agreements that map out how data is structured, formatted, and exchanged. Our reasoning here being that 1) this would successfully embed business objectives into the beginning of the pipeline and 2) clearly specifying what purpose data would serve would strengthen a contract’s importance.</p><h3><strong>Wielding the power of AI</strong></h3><p>Business objectives can be added after dataset(s) have been attached to data products, however, we also see a large benefit in being able to initiate the data journey directly from business objectives. This would minimize GIGO problems early on and ensure that the data entering the pipeline has a specified use further downstream. To do this, we would want business stakeholders to be able to initiate a data contract.</p><p>However, the process of constructing data contracts is often a technical one, requiring things like advanced query languages, data modeling, and ETL tools. How to maneuver around this technical barrier? <strong>We began to research how Generative AI could present an opportunity for nontechnical users to contribute to creating data contracts.</strong></p><p>While I cannot currently share what this interface looks like from a user’s perspective, I can share more about what this model would include from a technical perspective:</p><ol><li><em>Retrieval Augmented Generation (RAG): </em>Retrieves relevant information from business data sources based on the user’s natural language query, generating accurate and contextually relevant answers.</li><li><em>Utilizing SLM &amp; LLM</em>: Combines the strengths of retrieval models and generative models, making it highly effective in scenarios where information needs to be precise.</li><li><em>Privacy-focused</em>: The LLM is only used to map the user’s natural language prompt to appropriate tools, bypassing compliance regulations that prohibit private data from being passed to external LLMs. The locally running SLM receives the prompt, interprets it, and generates a response that appears on the user’s screen, based on information coming from secure data centers.</li></ol><p><a href="https://thenewstack.io/federated-language-models-slms-at-the-edge-plus-cloud-llms/">This article</a> presents a similar model to the one we envision this feature being powered on, if you want to learn more.</p><h3><strong>Conclusion</strong></h3><p><strong>This article explains a different approach to data products and introduces a specific use case in which they can facilitate the creation of data contracts in a more accessible and collaborative way.</strong></p><p>We are currently working towards integrating data products into other areas of the data management lifecycle to further improve how stakeholders define, manage, deliver, and govern data. For example, incorporating data products into a monitoring system to detect and mitigate bias in datasets, ensuring fair and inclusive data usage.</p><p>I believe there is power in adopting new perspectives on widely discussed topics. Thinking about data products in a UX-forward way unveils new avenues and approaches to solutions in the data product lifecycle.</p><p>I hope my project and this article can inspire discourse on how to think about data products in a different light, prioritizing user needs and human-centered design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f10c8a867bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sas-software-design/data-product-design-a-ux-approach-to-the-future-of-data-9f10c8a867bd">Data Product Design &amp; A UX Approach to the Future of Data</a> was originally published in <a href="https://medium.com/sas-software-design">SAS Product Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflections on my summer design internship]]></title>
            <link>https://medium.com/design-bootcamp/reflections-on-my-summer-design-internship-98afbfe06f4?source=rss-2f711965ccbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/98afbfe06f4</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Kathleen Anderson]]></dc:creator>
            <pubDate>Sat, 23 Sep 2023 18:25:35 GMT</pubDate>
            <atom:updated>2024-06-04T03:33:12.341Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y2l40MPrKxJavSa3aXGO-Q.png" /></figure><p>This past summer I worked as a Product Design Intern at SAS.</p><p>Some highlights were: winning first place in the intern Data Story Challenge, getting to present my summer project to an audience at Intern Expo, and creating connections with a team of amazing designers who I continuously learned from week after week.</p><p>Alongside some memorable experiences this summer gave me the opportunity to tremendously strengthen a wide array of my design skills.</p><h3><em>Technical improvements</em></h3><p>I made it a mission to improve my visual design skills over the summer. I consulted all sorts of resources from books to articles to YouTube videos outside of my work hours and would put my findings into practice during the weekdays. It paid off, towards the end of the summer I was designing high-fidelity screens with a pixel perfect (literally) attention to detail. Instead of saying something “looks wrong” I can now confidently reference principles like alignment and proximity when speaking about designs.</p><p>Working with an extensive design system was also a very rewarding experience. While overwhelming at first, I enjoyed exploring a massive catalog of components and their variants, and learning how to effectively wield these to streamline my design process. I’m hoping to build on my understanding of design systems this fall, as I build out an entirely new system for <a href="https://apps.apple.com/us/app/eatery-cornell-dining/id1089672962">Eatery</a>.</p><h3><em>Developing an understanding of industry</em></h3><p>In industry, product design is typically one piece of the puzzle that constitutes the entire company. <strong>Witnessing the way product designers interact with other departments was an eye-opening experience, from which I learned three valuable lessons:</strong></p><blockquote><strong>1. Designers wear different hats.</strong></blockquote><p>Designers are not just creators, we are communicators. I’ve discovered that designers must switch viewpoints and adjust how they communicate depending on who they are talking to. <strong>Being able to speak in a way that truly allows others to understand your ideas makes people more likely to invest in your designs.</strong></p><p>Going into the summer I understood this at a base level. But, working in the tech industry took this understanding to an entirely new level. At large companies there are many departments, and many teams within each department. Each team has their own goals and objectives, which will usually be different than yours. Being able to identify what is top-priority to them, and communicate your designs in a way that aligns with these priorities goes a long way.</p><blockquote><strong>2. You need to be the biggest hype-man for your designs.</strong></blockquote><p><strong>If you don’t believe in your designs, no one else will.</strong> Fostering an enthusiasm for your designs can be contagious, and being able to answer questions in a way that generates interest and excitement is essential for buy-in. Referring back to my first point, sometimes this requires putting on your “marketing hat” and selling your designs to those within the company.</p><blockquote><strong>3. Adaptability is needed in the design process.</strong></blockquote><p>In industry, it is possible to encounter situations where resources or access are limited for certain steps in the design process. <strong>It is the designer’s job to engineer workarounds and figure out how to produce the highest quality of work, even if some aspects of the design process are incomplete.</strong></p><p>I discovered this quite early into my summer when I wanted to conduct user interviews to learn more about our target users. But, since I was working on a pre-market product,<em> there were no users yet</em>. What now? Was I supposed to skip this step in the design process? That wouldn’t do. I pieced together another strategy. Using a combination of market research, product research, and legislation research I explored and crafted an understanding of users.</p><p>After the first iteration of designs I was still not satisfied with my level of understanding. I continued to brainstorm ways to workaround the absence of actual users. Finally, I came up with the idea to interview subject matter experts (SMEs) working at SAS–<strong>people who would be our target users once the solution launched</strong>–which ultimately proved very informative.</p><h3><em>Learning through conversation with others</em></h3><p>Throughout the summer I talked to an assortment of designers who came from different backgrounds than I do such as engineering, computer science, industrial design, and graphic design. <strong>Listening to their stories and asking question about their experiences helped me become more in tune with my own design journey.</strong> These conversations pushed me to think about the work I did over the summer from new perspectives and within different contexts.</p><p>A great example of this is how my “<strong>You need to be the biggest hype-man for your designs” </strong>point was inspired by a conversation I had with the Director of the Product Design department at SAS. Chatting about his path from industrial design into UX led us into a discussion about the importance of fostering a passion about your work, which I then evolved into the “biggest hype-man” notion.</p><h3><em>What a summer!</em></h3><p>I had an amazing summer interning at SAS, and as I transition back into the school year I’m feeling more confident in my design skills than ever before. I’m looking forward to putting what I’ve learned to use in new design projects and beyond!</p><p>👋 Hi, I’m Kathleen, a current student at Cornell studying Information Science with a passion for product design and writing.</p><p>Find me on <a href="https://www.linkedin.com/in/kathleen-anderson-97ab69203/">LinkedIn</a> here!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98afbfe06f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/reflections-on-my-summer-design-internship-98afbfe06f4">Reflections on my summer design internship</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>
        <item>
            <title><![CDATA[Lessons I learned in my first year as a designer]]></title>
            <link>https://medium.com/design-bootcamp/lessons-i-learned-in-my-first-year-as-a-designer-4c6f5e9c295c?source=rss-2f711965ccbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c6f5e9c295c</guid>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Kathleen Anderson]]></dc:creator>
            <pubDate>Fri, 14 Jul 2023 08:50:21 GMT</pubDate>
            <atom:updated>2023-09-23T00:37:50.991Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nYBCBdkwEqCVMO9xwzOrzQ.png" /></figure><p>Last June I decided to switch my major from English to Information Science. I took this leap of faith to focus my studies on product design, a subject that sparked an excitement and enthusiasm in me for life after college that I had never felt before.</p><p><strong>I knew this was a decision that would impact my future. What I didn’t know was just how far this impact would stretch, or how quickly.</strong></p><p>Over this past year I have taken on coursework that would have horrified my high-school self, been invited to work as an artist in my college’s psychology department, met some of my closest friends, and nurtured my passion for design into something I am proud of.</p><p>So far, this road has been overwhelmingly transformative for me, but far from easy and bump-less. I write this article not only as a reflection on how much I’ve learned as a designer, but as a testament to the inevitable role of failure in the learning process. I want to be transparent about my journey thus far. Therefore, I’m sharing 5 lessons I learned in my first year as a designer, what sort of mistake or misunderstanding each originated from, and what the experience ultimately taught me.</p><blockquote>Lesson 1: <strong>There is no one way to be a designer.</strong></blockquote><p>As a chronic overthinker, it was only natural for me to worry about my design journey before it had even begun.</p><blockquote>Do I have what it takes to be a STEM major?</blockquote><blockquote>Will my background in English put me at a disadvantage?</blockquote><blockquote>How will I catch up with my peers who are already a full year into their design education?</blockquote><p>My panic arose from the idea that, because I previously focused most of my academic attention on the study of writing and literature, I would not not be as qualified of a designer as those with backgrounds and experiences in design-related fields.</p><p>Eager to learn how to become a true designer, when I arrived at school in the fall, I took the opportunity to connect with any designers that I could. I attended school-coordinated events, initiated coffee chats with other students, and made the effort to connect with fellow designers on my project team. Slowly but surely I created a design community for myself.</p><p>I began to hear an assortment of stories about how various qualifications, interests, and affinities had provided designers with unique advantages on their own projects and teams. <strong>From these stories I learned designers come from all different backgrounds, and these differences do not make us weaker, but stronger. </strong>Ironically, in seeking out answers to how I could become a true designer, I realized I already was one.</p><p>I can attribute a large part in my development as a designer over this past year to the design community I immersed myself in. The people I met and the stories I listened to allowed me to think about my own design journey in a different light, and I began to wield my unique attributes as advantages.</p><blockquote>Lesson 2:<strong> You are not the user (even if you are A user)!</strong></blockquote><p>Never one for being patient, I set out on a mission to learn as much about product design as I could before classes officially began in August. I spent hours watching Figma tutorials, listening to podcasts, and reading countless articles on the design process. By the end of the summer I decided I was ready to take on the challenge of creating my very first project.</p><p><strong>What I didn’t know at the time was that I had doomed my project before it began by entering the design process with a solution already mapped out in my mind.</strong></p><p>I chose to build my first project around the wildly popular mobile app, TikTok. This decision was not so much because of the problem space I identified, but rather because I had already brainstormed a solution that <em>I</em> believed would solve one of <em>my</em> biggest issues with the app. This polluted my project with heavy amounts of <a href="https://en.wikipedia.org/wiki/Confirmation_bias">confirmation bias</a>. For example, during the user interviews stage I asked questions like:</p><blockquote>What do you like least about TikTok’s sound features?</blockquote><blockquote>Do you wish TikTok did things differently with your favorite sounds?</blockquote><p>It is easy to see how I “uncovered” pain points that aligned with the solution I hoped to create. By asking biased questions I acted like a shepherd herding my users to the answers I wanted.</p><p>However, this mistake proved valuable in the long-run, because it gave me a first-hand understanding of why user-centered design is so crucial. It is <em>not</em> the designer’s job to steer users toward solutions. It is the designer’s job to uncover users’ true pain points, and build a solution addressing their wants and needs.</p><blockquote>Lesson 3:<strong> Document more than just your design process.</strong></blockquote><p>When I took the class <a href="https://www.cornellappdev.com/courses/dpd">Introduction to Digital Product Design</a> last fall, the instructors preached the importance of documenting your work from the very first assignment.</p><p>This made sense– I recalled what a tough time I had over the summer writing my first case study with no notes on the design decisions I made, or why I had made them. So, throughout the course of the fall semester, I kept a well-organized catalog of my design decisions the rationale that backed them.</p><p>However, when I sat down to write my case study at the end of the semester <strong>I still struggled to create the larger story surrounding my designs</strong>. It was difficult to find words for the spark that inspired my project to begin with, or for the frustration I felt when my first solution didn’t solve the user’s problems like I imagined.</p><p>This experience taught me that it is important to make note of thoughts, feelings, and reactions that emerge at different stages within the design process. <strong>Documenting your methodology and workflow helps set a foundation for your design presentations. Documenting your emotions helps tell the story that ties these foundations together. Both are important.</strong></p><p>Leading to my next point…</p><blockquote>Lesson 4:<strong> How you present matters just as much, if not more, than what you present.</strong></blockquote><p>The first time I ever presented a case study was in front of a panel of other designers during a final round interview for a school project team. I watched as the interviewees’ eyes began to wander as I clicked through slide after slide crowded with mountains of text and mock-ups. I felt their restlessness grow with every minute that I formulaically explained each step in my design process.</p><p>Despite my energy and enthusiasm for the project,<strong> because of my lack of presentation skills, the audience simply wasn’t very interested in what I had to say.</strong></p><p>I didn’t get the position. In the spring, I applied again. More confident in my skills as a designer, I decided to break away from framing my project through the double diamond design process, and to tell my own story this time around.</p><p>In this presentation I added hand-drawn cartoons to illustrate the ideas I spoke about. I replaced blocks of text with with annotated prototypes. I practiced taking dramatic pauses before delivering essential pieces of information. <strong>Combining visual, written, and verbal communication, I told a unique story.</strong></p><p>My project was not only more enjoyable to present, but the delivery was much more engaging and effective. (And I made the team that time! Yay!)</p><p>Through trial and error, I learned the power that lies in the delivery of information. <strong>In order to make people care about your designs, you must first make them listen to what you have to say.</strong> This means getting creative and telling a story they haven’t heard a thousand times before.</p><blockquote>Lesson 5:<strong> Embrace mistakes. Capitalize on what they teach you.</strong></blockquote><p>I once had a field hockey coach that preached, “I don’t care about about the bad play, I care about the recovery.”</p><p>While I lived by this saying on the field, refusing to let one error dictate my entire performance in a game, I ignored the application of this concept in other aspects of my life. I constantly lived in fear that one bad grade would tank my GPA, or a big fight with a friend would sour the entire relationship.</p><p>Historically, I avoided situations in which I would be likely to make mistakes. But, a few weeks into the beginning of the school year I realized that in order to succeed at both my new major, and as a designer, I would need to continuously put myself in positions with the potential to make mistakes. Taking a chance to succeed also meant I needed to take a chance at failing.</p><p>The result being: I failed. A lot. But I also succeeded in many ways that mattered. <strong>Amidst numerous failures I learned there is no reason to be afraid of mistakes, but rather to embrace the lessons that manifest in their aftermath.</strong></p><p>Now, with this mindset I consciously make an effort to take a step back after each failure and ask myself, <em>what did this teach me? </em>Very rarely am I left without an answer.</p><p>I don’t like making mistakes. I don’t know anyone who does. But I can confidently say that the mistakes I’ve made in this past year have shaped me into the intelligent and informed designer I am today.</p><blockquote><strong>That’s all, folks!</strong></blockquote><p>If I could say anything to the newbie designer I was last year at this time, I would tell her that things would not go exactly the way she planned,<strong> but that things would work out anyways.</strong></p><p>I passed all the classes I was worried about needing to take. I got to experiment with subjects I enjoy. Design introduced me to some awesome friends, and I landed a summer internship that makes me excited to get up every morning and log into my laptop.</p><p>By sharing my experiences I hope that other designers, or anyone questioning their current academic and/or career path will also embrace the idea that failure is an inherent part of the learning process.</p><p>This article contains a few lessons that I consider milestones in my design journey over the past year. I have no doubt they will serve as strong foundations as I continue to grow as a designer. It’s exciting to think–if this is where I am after one year, where will I be in another? In five, in ten?</p><p>👋 Hi, I’m Kathleen, a current student at Cornell studying Information Science with a passion for product design and writing.</p><p>Find me on <a href="https://www.linkedin.com/in/kathleen-anderson-97ab69203/">LinkedIn</a> here!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c6f5e9c295c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/lessons-i-learned-in-my-first-year-as-a-designer-4c6f5e9c295c">Lessons I learned in my first year as a designer</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>
        <item>
            <title><![CDATA[Why your designs should be CRAP]]></title>
            <link>https://medium.com/design-bootcamp/why-your-designs-should-be-crap-f8c0a37f1fa5?source=rss-2f711965ccbc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8c0a37f1fa5</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[visual-design]]></category>
            <dc:creator><![CDATA[Kathleen Anderson]]></dc:creator>
            <pubDate>Fri, 30 Jun 2023 07:41:00 GMT</pubDate>
            <atom:updated>2023-06-30T07:41:00.793Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mp2RX22sBSSTHVYS3_Q1Fw.png" /></figure><p>Yes, you read that right. No, it’s probably not what you think.</p><p>If I could go back in time and place one book into the hands of my newbie designer self, it would be Robin Williams’s <em>The Non-Designer’s Design Book</em>.</p><p>Before any formal design education, I always considered myself to have an eye for visual design– I could look at things and tell when they looked “right” and when they looked “wrong”. However, I didn’t know <em>why.</em></p><p>It took me months to learn the principles and develop a vocabulary to describe what drew me to certain designs and drove me away from others. However, <strong><em>The Non-Designer’s Design Book </em>lays solid foundations for understanding a few key principles that allow you to immediately begin identifying good design practices, and implementing them into your work.</strong> These four principles are: contrast, repetition, alignment, and proximity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KSxT5XuGUpwuIAAuxm-tSw.png" /><figcaption>The CRAP acronym</figcaption></figure><p>Although marketed towards non-designers, I argue this is a book for <em>every</em> designer, beginners and experts alike. For beginners it serves as a not-too-overwhelming introduction to the underlying principles that govern great visual design. For more advanced designers, it is a refresher on the overall importance of these principles and their utility.</p><p>The CRAP acronym serves as an important point of guidance because these <strong>principles don’t go away. While they might be basic, they are foundational to great design, and appear in the work of designers at all levels of expertise. </strong>Being able to understand, recognize, and wield these tools will make you a powerful designer.</p><h3>Contrast</h3><p>In the image below there are three variations of the same text. Which one draws your attention the most?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YNL0uEAJ5PoLNF-x-PKBrA.png" /><figcaption>Three variations of the same paragraph– each heading weighted differently</figcaption></figure><p>Likely, you said the far right. But <em>why? </em>These paragraphs all contain the same words, in the same font, in the same size. The sole difference is that the headers all possess different levels of contrast. The far right header holds no contrast– it is exactly the same as the body. The middle header is medium weighted, providing a slight contrast to the regular weighted body. And… the far right header’s condensed black weight provides a striking contrast to the body’s regular weight.</p><p>Simply put: different draws attention. And this is the purpose of contrast.</p><p>Whether you are looking to emphasize important information, create a sense of organization on the page, or enhance legibility, contrast serves as a crucial tool to grab the viewer’s attention.</p><p>To effectively wield contrast in your design, you need to lean into the power of dissimilarity. There needs to be a noticeable difference between the elements you are contrasting. Designers most commonly achieve this using size, shape, color, or weight. As shown in the example above, slight differences like using a regular vs. medium font weight don’t do an efficient enough job of generating interest.</p><p>As Williams advises in her book:</p><blockquote>“Don’t be a wimp. If you’re going to contrast, do it with strength.”</blockquote><h3>Repetition</h3><p>You’ve created visual repetition before– whether you know it or not. Think back to your high school years, all those essays you wrote. Indenting every new paragraph, assigning numbers to the top left corner of each page, citing each quote using parentheses that contain the author’s last name– all these repetitions contributed to creating a visual consistency that persisted throughout your entire paper.</p><p>Good start! However, for repetition to become a powerful tool in your design, it needs to surpass subtleness.</p><blockquote>“Repetition goes beyond just being naturally consistent– it is a conscious effort to unify all parts of a design.”</blockquote><p>By intentionally using certain elements again and again you create consistency. This is important because it drives unity and cohesion within your design. A great example of intentional repetition is the Google app logos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gntQxSCdo51Yk_OPsn83w.jpeg" /><figcaption>Google app logos via <a href="https://www.androidpolice.com/">Android Police</a></figcaption></figure><p>If you’re staring at a crowded homepage, it is easy to identify which apps are Google ones. <em>Why?</em> The deliberate use of the same colors, shapes, patterns, and size generate a resounding sense of harmony and understanding.</p><p>This is repetition wielded effectively: never making viewers question what’s connected and what’s not. Consciously repeat certain elements throughout your design to create meaningful associations.</p><h3>Alignment</h3><p>The mere act of where you place elements on the page is something that heavily impacts a design’s coherence. Therefore, it should not be an arbitrary act.</p><blockquote>“Every element should have some visual connection with another element on the page.”</blockquote><p>When you align elements on a page it brings an immediate sense of order to your work by creating connections. Alignment can become a nuanced topic when you introduce things like grids, but at its base is <em>the principle of the invisible line.</em></p><p>Remember back in calculus when you used the vertical line test to determine whether or not a graph was a function? Here’s what I call the invisible line test: do all related elements align on an invisible vertical line?</p><p>If the answer is yes, you’ve passed! If it’s no, you might have some work to do.</p><p>Below is an example of the same content, aligned in two different ways. One version passes the invisible line test, the other does not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bFx5kbDbC1oXd9rysyfR0g.png" /><figcaption>Two frames containing the same content, but aligned differently</figcaption></figure><p>Notice how the design that passes the invisible line test–which is represented with an actual line here to prove my point–looks much more organized? The invisible line test is a rule that can be broken, but generally speaking, if your design passes, you have succeeded in creating some level of unity and balance in your work.</p><h3>Proximity</h3><p>When staring at a blank page with no idea how to start designing, proximity is the easiest place to start (in my opinion). Let one simple question guide your initial layout: What are the different relationships between all this content? If elements are related, group them together. If they’re not, use space to separate them. This is the essence of proximity.</p><p>Look at the image below. How many different groups of related elements do you count in each frame?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ZWERS_ZBpPyUXcsg3TejQ.png" /><figcaption>Three frames containing the same content, yet each groups the content differently</figcaption></figure><p>Even though each frame is filled only with identical black dots that possess no inherent meaning, it is clear that there are two groups in the left image, one in the middle, three on the left, and that the grouped together dots are <em>somehow related to each other</em>. This is the work of proximity.</p><p>Proximity is perhaps the easiest way to create organization within your design because it requires no editing of the content itself, but instead uses whitespace to create both visual connections and separations. Yet, it is important not to overlook this simple principle, because it is powerful.</p><blockquote>“If the information is organized, it is more likely to be read and more likely to be remembered.”</blockquote><p>Use proximity in your designs to make sure viewers never have to guess what content belongs together, and what doesn’t.</p><h3>Conclusion</h3><p>Yes, you’re design should be CRAP, but not that kind! We’re talking about the acronym for the powerful principles of contrast, repetition, alignment, and proximity.</p><p>While it is true that these rules can be successfully broken, <strong>I guarantee you that by abiding to the CRAP acronym, you will design more professional-looking, eye-catching work.</strong></p><p><em>All quotes are from Robin Williams’s </em>The Non-Designer’s Design Book<em>. Find it on Amazon </em><a href="https://www.amazon.com/Non-Designers-Design-Book-4th/dp/0133966151/ref=sr_1_1?hvadid=241886564158&amp;hvdev=c&amp;hvlocphy=9007343&amp;hvnetw=g&amp;hvqmt=e&amp;hvrand=11089106399451753031&amp;hvtargid=kwd-420665645&amp;hydadcr=16431_10305303&amp;keywords=the+non+designer%27s+design+book&amp;qid=1687967343&amp;sr=8-1"><em>here</em></a><em>!</em></p><p>👋 Hi, I’m Kathleen, a current student at Cornell studying Information Science with a passion for product design and writing.</p><p>Find me on <a href="https://www.linkedin.com/in/kathleen-anderson-97ab69203/">LinkedIn</a> here!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8c0a37f1fa5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/why-your-designs-should-be-crap-f8c0a37f1fa5">Why your designs should be CRAP</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>