FEED Validator

for Atom and RSS and KML

Sorry

This feed does not validate.

line 27, column 7: Undefined author element: a (23 occurrences) [help]

				by <a itemprop="url" class="author" rel="author" href="https://alistapar ...
       ^

line 27, column 243: Invalid email address: by , (20 occurrences) [help]

... ffmacintyre/">Jeffrey MacIntyre</a>					</author>
                                             ^

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 3709, column 0: description should not contain is attribute (9 occurrences) [help]
```

```
line 5893, column 4: Missing atom:link with rel="self" [help]
```
				</channel>
    ^
```

Source: https://alistapart.com/main/feed/

<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
<channel>
<title>
<![CDATA[A List Apart: The Full Feed]]> </title>
<link>
https://alistapart.com </link>
<description>Articles for people who make web sites.</description>
<dc:language>
en-US </dc:language>
<dc:creator>The fine folks at A List Apart</dc:creator>
<dc:date>
2024-04-18T07:30:04+00:00 </dc:date>
<item>
<title>
<![CDATA[To Ignite a Personalization Practice, Run this Prepersonalization Workshop]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/colineagan/">Colin Eagan</a>, <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/jeffmacintyre/">Jeffrey MacIntyre</a> </author>
<link>
https://alistapart.com/article/prepersonalization-workshop/ </link>
<guid>
https://alistapart.com/article/prepersonalization-workshop/ </guid>
<description>
<![CDATA[
Picture this. You’ve joined a squad at your company that’s designing new product features with an emphasis on automation or AI. Or your company has just implemented a <a href="https://en.wikipedia.org/wiki/Personalization_management_system">personalization engine</a>. Either way, you’re designing with data. Now what? When it comes to <a href="https://alistapart.com/article/personalization-pyramid/">designing for personalization</a>, there are many cautionary tales, no overnight successes, and few guides for the perplexed.


Between the fantasy of getting it right and the fear of it going wrong—like when we encounter “<a href="https://visit.bucketbriga.de/c/personalization-failure-persofail/">persofails</a>” in the vein of a company <a href="https://twitter.com/jeffmacintyre/status/1505878250937061378">repeatedly imploring everyday consumers to buy additional toilet seats</a>—the personalization gap is real. It’s an especially confounding place to be a digital professional without a map, a compass, or a plan.


For those of you venturing into personalization, there’s no Lonely Planet and few tour guides because effective personalization is so specific to each organization’s talent, technology, and market position. 


But you can ensure that your team has packed its bags sensibly.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/suggested-vistas-1024x684.jpg" alt="A sign at a mountain scene says “People who liked this also liked,” which is followed by photographs of other scenic landscapes. Satirical art installation by Scott Kelly and Ben Polkinghome." class="wp-image-7174341"/><figcaption class="wp-element-caption">Designing for personalization makes for strange bedfellows. A savvy art-installation satire on the challenges of humane design in the era of the algorithm. Credit:<a href="https://www.scottconradkelly.com/signs-of-the-times"> Signs of the Times</a>, Scott Kelly and Ben Polkinghome.</figcaption></figure>


There’s a DIY formula to increase your chances for success. At minimum, you’ll defuse your boss’s irrational exuberance. Before the party you’ll need to effectively prepare.


We call it prepersonalization.


<h2 class="wp-block-heading">Behind the music</h2>


Consider Spotify’s DJ feature, which debuted this past year.


<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
https://www.youtube.com/watch?v=ok-aNnc0Dko
</div></figure>


We’re used to seeing the polished final result of a personalization feature. Before <a href="https://www.linkedin.com/posts/daniel-ek-1b52093a_spotify-dj-the-200-best-inventions-of-2023-activity-7122612194923483137-rRNc/">the year-end award</a>, the <a href="https://newsroom.spotify.com/2023-10-18/how-spotify-uses-design-to-make-personalization-features-delightful/">making-of backstory</a>, or the behind-the-scenes <a href="https://newsroom.spotify.com/2023-03-08/spotify-new-personalized-ai-dj-how-it-works/">victory lap</a>, a personalized feature had to be conceived, budgeted, and prioritized. Before any personalization feature goes live in your product or service, it lives amid a backlog of worthy ideas for expressing customer experiences more dynamically.


So how do you know where to place your personalization bets? How do you design consistent interactions that won’t trip up users or—worse—breed mistrust? We’ve found that for many budgeted programs to justify their ongoing investments, they first needed one or more workshops to convene key stakeholders and internal customers of the technology. Make yours count.


From <a href="https://en.wikipedia.org/wiki/Big_Tech#:~:text=Alphabet%2C%20the%20parent%20company%20of,Amazon%2C%20Netflix%2C%20and%20Google.">Big Tech</a> to fledgling startups, we’ve seen the same evolution up close with our clients. In our experiences with working on small and large personalization efforts, a program’s ultimate track record—and its ability to weather tough questions, work steadily toward shared answers, and organize its design and technology efforts—turns on how effectively these prepersonalization activities play out.


Time and again, we’ve seen effective workshops separate future success stories from unsuccessful efforts, saving countless time, resources, and collective well-being in the process.


A personalization practice involves a multiyear effort of testing and feature development. It’s not a switch-flip moment in your tech stack. It’s best managed as a backlog that often evolves through three steps: 


<ol>
<li>customer experience optimization (CXO, also known as A/B testing or experimentation)</li>


<li>always-on automations (whether rules-based or machine-generated)</li>


<li>mature features or standalone product development (such as Spotify’s DJ experience)</li>
</ol>


This is why we created our progressive personalization framework and why we’re field-testing an accompanying <a href="http://progressivepersonalization.com/">deck of cards</a>: we believe that there’s a base grammar, a set of “nouns and verbs” that your organization can use to design experiences that are customized, personalized, or automated. You won’t need these cards. But we strongly recommend that you create something similar, whether that might be digital or physical.


<h2 class="wp-block-heading">Set your kitchen timer</h2>


How long does it take to cook up a prepersonalization workshop? The surrounding assessment activities that we recommend including can (and often do) span weeks. For the core workshop, we recommend aiming for two to three days. Here’s a summary of our broader approach along with details on the essential first-day activities.


The full arc of the wider workshop is threefold:


<ol>
<li>Kickstart: This sets the terms of engagement as you focus on the opportunity as well as the readiness and drive of your team and your leadership. .</li>


<li>Plan your work: This is the heart of the card-based workshop activities where you specify a plan of attack and the scope of work.</li>


<li>Work your plan: This phase is all about creating a competitive environment for team participants to individually pitch their own pilots that each contain a proof-of-concept project, its business case, and its operating model.</li>
</ol>


Give yourself at least a day, split into two large time blocks, to power through a concentrated version of those first two phases.


<h2 class="wp-block-heading">Kickstart: Whet your appetite</h2>


We call the first lesson the “landscape of connected experience.” It explores the personalization possibilities in your organization. A connected experience, in our parlance, is any UX requiring the orchestration of multiple systems of record on the backend. This could be a content-management system combined with a marketing-automation platform. It could be a digital-asset manager combined with a customer-data platform.


Spark conversation by naming consumer examples and business-to-business examples of connected experience interactions that you admire, find familiar, or even dislike. This should cover a representative range of personalization patterns, including automated app-based interactions (such as onboarding sequences or wizards), notifications, and recommenders. We have a catalog of these in the cards. Here’s a list of <a href="https://www.dynamicyield.com/personalization-examples/">142 different interactions</a> to jog your thinking.


This is all about setting the table. What are the possible paths for the practice in your organization? If you want a broader view, here’s a <a href="https://visit.bucketbriga.de/c/field-notes/navigating-the-personalization-gap-a-field-guide">long-form primer</a> and a <a href="https://visit.bucketbriga.de/c/field-notes/progressive-personalization-a-decisionmaking-model-for-better-outcomes-in-personalized-ux">strategic framework</a>.


Assess each example that you discuss for its complexity and the level of effort that you estimate that it would take for your team to deliver that feature (or something similar). In our cards, we divide connected experiences into five levels: functions, features, experiences, complete products, and portfolios. Size your own build here. This will help to focus the conversation on the merits of ongoing investment as well as the gap between what you deliver today and what you want to deliver in the future.


Next, have your team plot each idea on the following 2×2 grid, which lays out the four enduring arguments for a personalized experience. This is critical because it emphasizes how personalization can not only help your external customers but also affect your own ways of working. It’s also a reminder (which is why we used the word argument earlier) of the broader effort beyond these tactical interventions.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/arguments-for-personalization-1024x575.jpg" alt="A two-by-two grid shows the four areas of emphasis for a personalization program in an organization: Business efficiency, customer experience, business orchestration, and customer understanding. The focus varies from front-stage to back-stage and from business-focused to customer-focused outcomes." class="wp-image-7174342"/><figcaption class="wp-element-caption">Getting intentional about the desired outcomes is an important component to a large-scale personalization program. Credit: <a href="https://bucket.studio/">Bucket Studio</a>.</figcaption></figure>


Each team member should vote on where they see your product or service putting its emphasis. Naturally, you can’t prioritize all of them. The intention here is to flesh out how different departments may view their own upsides to the effort, which can vary from one to the next. Documenting your desired outcomes lets you know how the team internally aligns across representatives from different departments or functional areas.


The third and final kickstart activity is about naming your personalization gap. Is your customer journey well documented? Will data and privacy compliance be too big of a challenge? Do you have <a href="https://aws.amazon.com/blogs/machine-learning/selecting-the-right-metadata-to-build-high-performing-recommendation-models-with-amazon-personalize/">content metadata needs</a> that you have to address? (We’re pretty sure that you do: it’s just a matter of recognizing the relative size of that need and its remedy.) In our cards, we’ve noted a number of program risks, including common team dispositions. Our Detractor card, for example, lists six stakeholder behaviors that hinder progress.


Effectively collaborating and managing expectations is critical to your success. Consider the potential barriers to your future progress. Press the participants to name specific steps to overcome or mitigate those barriers in your organization. As studies have shown, personalization efforts face many common barriers.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/barriers-to-personalization-1024x483.jpg" alt="Barriers to personalization according to a Boston Consulting Group 2016 research study. The top items include “too few personnel dedicated to personalization,” “lack of a clear roadmap,” and “inadequate cross-functional coordination and project management.”" class="wp-image-7174343"/><figcaption class="wp-element-caption">The largest management consultancies have established practice areas in personalization, and they regularly research program risks and challenges. Credit: <a href="https://www.bcg.com/publications/2017/retail-marketing-sales-profiting-personalization">Boston Consulting Group</a>.</figcaption></figure>


At this point, you’ve hopefully discussed sample interactions, emphasized a key area of benefit, and flagged key gaps? Good—you’re ready to continue.


<h2 class="wp-block-heading">Hit that test kitchen</h2>


Next, let’s look at what you’ll need to bring your personalization recipes to life. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. Their capabilities are sweeping and powerful, and they present broad options for how your organization can conduct its activities. This presents the question: Where do you begin when you’re configuring a connected experience?


What’s important here is to avoid treating the installed software like it were a dream kitchen from some fantasy remodeling project (as one of our client executives memorably put it). These software engines are more like test kitchens where your team can begin devising, tasting, and refining the snacks and meals that will become a part of your personalization program’s regularly evolving menu.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/personalization-pyramid-1024x576.jpg" alt="The Progressive Personalization Model v2: A pyramid with the following layers, starting at the base and working up: Raw Data (millions), Actionable Data (hundreds of thousands), Segments (thousands), Customer Experience Patterns (many), Interactions (dozens), and Goals (handful)." class="wp-image-7174344"/><figcaption class="wp-element-caption">Progressive personalization, a framework for designing connected experiences. Credit: <a href="https://bucket.studio/">Bucket Studio</a> and Colin Eagan.</figcaption></figure>


The ultimate menu of the prioritized backlog will come together over the course of the workshop. And creating “dishes” is the way that you’ll have individual team stakeholders construct personalized interactions that serve their needs or the needs of others.


The dishes will come from recipes, and those recipes have set ingredients.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/personalization-poker-deck-1024x576.jpg" alt="A photo of the Progressive Personalization deck of cards with accompanying text reading: Align on key terms and tactics. Draft and groom a full backlog, designing with data." class="wp-image-7174345"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/poker-deck-cards-1024x660.jpg" alt="A zoomed out view of many of the cards in the deck. Cards have colors corresponding to the layers of the personalization pyramid and include actionable details." class="wp-image-7174346"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/poker-deck-recipes-1024x572.jpg" alt="Progressive personalization is a model of designing for personalized interactions that uses playing cards to assemble the typical parts for such features and functionality." class="wp-image-7174347"/><figcaption class="wp-element-caption">In the same way that ingredients form a recipe, you can also create <a href="http://progressivepersonalization.com/">cards</a> to break down a personalized interaction into its constituent parts. Credit: <a href="https://bucket.studio/">Bucket Studio</a> and Colin Eagan.</figcaption></figure>


<h2 class="wp-block-heading">Verify your ingredients</h2>


Like a good product manager, you’ll make sure—andyou’ll validate with the right stakeholders present—that you have all the ingredients on hand to cook up your desired interaction (or that you can work out what needs to be added to your pantry). These ingredients include the audience that you’re targeting, content and design elements, the context for the interaction, and your measure for how it’ll come together. 


This isn’t just about discovering requirements. Documenting your personalizations as a series of if-then statements lets the team: 


<ol>
<li>compare findings toward a unified approach for developing features, not unlike when artists paint with the same palette; </li>


<li>specify a consistent set of interactions that users find uniform or familiar; </li>


<li>and develop parity across performance measurements and key performance indicators too. </li>
</ol>


This helps you streamline your designs and your technical efforts while you deliver a shared palette of core motifs of your personalized or automated experience.


<h2 class="wp-block-heading">Compose your recipe</h2>


What ingredients are important to you? Think of a who-what-when-why <a href="https://en.wikipedia.org/wiki/Five_Ws">construct</a>: 


<ul>
<li>Who are your key audience segments or groups?</li>


<li>What kind of content will you give them, in what design elements, and under what circumstances?</li>


<li>And for which business and user benefits?</li>
</ul>


We first developed these <a href="https://alistapart.com/article/personalization-pyramid/">cards and card categories</a> five years ago. We regularly play-test their fit with conference audiences and clients. And we still encounter new possibilities. But they all follow an underlying who-what-when-why logic. Here are three examples for a subscription-based reading app, which you can generally follow along with right to left in the cards in the accompanying photo below. 


<ol>
<li>Nurture personalization: When a guest or an unknown visitor interacts with  a product title, a banner or alert bar appears that makes it easier for them to encounter a related title they may want to read, saving them time.</li>


<li>Welcome automation: When there’s a newly registered user, an email is generated to call out the breadth of the content catalog and to make them a happier subscriber.</li>


<li>Winback automation: Before their subscription lapses or after a recent failed renewal, a user is sent an email that gives them a promotional offer to suggest that they reconsider renewing or to remind them to renew.</li>
</ol>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/recipe-nurture-1024x573.jpg" alt="A selection of prompt cards assembled to represent the key parameters of a “nurture” user flow." class="wp-image-7174348"/><figcaption class="wp-element-caption">A “nurture” automation may trigger a banner or alert box that promotes content that makes it easier for users to complete a common task, based on behavioral profiling of two user types. Credit: <a href="https://bucket.studio/">Bucket Studio</a>.</figcaption></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/recipe-welcome-1024x574.jpg" alt="A selection of prompt cards assembled to represent the key parameters of a “welcome”, or onboarding, user flow." class="wp-image-7174349"/><figcaption class="wp-element-caption">A “welcome” automation may be triggered for any user that sends an email to help familiarize them with the breadth of a content library, and this email ideally helps them consider selecting various titles (no matter how much time they devote to reviewing the email’s content itself). Credit: <a href="https://bucket.studio/">Bucket Studio</a>.</figcaption></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2024/04/recipe-winback-1024x573.jpg" alt="A selection of prompt cards assembled to represent the key parameters of a “winback”, or customer-churn risk, user flow." class="wp-image-7174350"/><figcaption class="wp-element-caption">A “winback” automation may be triggered for a specific group, such as users with recently failed credit-card transactions or users at risk of churning out of active usage, that present them with a specific offer to mitigate near-future inactivity. Credit: <a href="https://bucket.studio/">Bucket Studio</a>.</figcaption></figure>


A useful preworkshop activity may be to think through a first draft of what these cards might be for your organization, although we’ve also found that this process sometimes flows best through cocreating the recipes themselves. Start with a set of blank cards, and begin labeling and grouping them through the design process, eventually distilling them to a refined subset of highly useful candidate cards.


You can think of the later stages of the workshop as <a href="https://visit.bucketbriga.de/c/field-notes/pre-personalization-workshop">moving from recipes toward a cookbook</a> in focus—like a more nuanced customer-journey mapping. Individual “cooks” will pitch their recipes to the team, using a common <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">jobs-to-be-done</a> format so that measurability and results are baked in, and from there, the resulting collection will be prioritized for finished design and delivery to production.


<h2 class="wp-block-heading">Better kitchens require better architecture</h2>


Simplifying a customer experience is a complicated effort for those who are inside delivering it. Beware anyone who says otherwise. With that being said,  “Complicated problems can be hard to solve, but <a href="https://sloanreview.mit.edu/article/the-critical-difference-between-complex-and-complicated/">they are addressable with rules and recipes</a>.”


When personalization becomes a laugh line, it’s because a team is <a href="https://aws.amazon.com/what-is/overfitting/">overfitting</a>: they aren’t designing with their best data. Like a sparse pantry, every organization has metadata debt to go along with its technical debt, and this creates a drag on personalization effectiveness. Your AI’s output quality, for example, is indeed limited by your <a href="https://en.wikipedia.org/wiki/Information_architecture">IA</a>. Spotify’s poster-child prowess today was unfathomable before they <a href="https://www.theguardian.com/technology/2014/mar/06/spotify-echo-nest-streaming-music-deal">acquired</a> a seemingly modest <a href="https://en.wikipedia.org/wiki/The_Echo_Nest">metadata startup</a> that now <a href="https://techcrunch.com/2014/10/19/the-sonic-mad-scientists/">powers</a> its underlying information architecture.


<h2 class="wp-block-heading">You can definitely stand the heat…</h2>


Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach will bring about the necessary focus and intention to succeed. So banish the dream kitchen. Instead, hit the test kitchen to save time, preserve job satisfaction and security, and safely dispense with the fanciful ideas that originate upstairs of the doers in your organization. There are meals to serve and mouths to feed.


This workshop framework gives you a fighting shot at lasting success as well as sound beginnings. Wiring up your information layer isn’t an overnight affair. But if you use the same cookbook and shared recipes, you’ll have solid footing for success. We designed these activities to make your organization’s needs concrete and clear, long before the hazards pile up.


While there are associated costs toward investing in this kind of technology and product design, your ability to size up and confront your unique situation and your digital capabilities is time well spent. Don’t squander it. The proof, as they say, is in the pudding.
]]> </description>
<dc:subject>
<![CDATA[Content Strategy, Information Architecture, User Experience]]> </dc:subject>
<dc:date>
2024-04-16T19:51:34+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[The Wax and the Wane of the Web]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/stegrainer/">Ste Grainer</a> </author>
<link>
https://alistapart.com/article/the-wax-and-the-wane-of-the-web/ </link>
<guid>
https://alistapart.com/article/the-wax-and-the-wane-of-the-web/ </guid>
<description>
<![CDATA[
I offer a single bit of advice to friends and family when they become new parents: When you start to think that you’ve got everything figured out, everything will change. Just as you start to get the hang of feedings, diapers, and regular naps, it’s time for solid food, potty training, and overnight sleeping. When you figure those out, it’s time for preschool and rare naps. The cycle goes on and on.


The same applies for those of us working in design and development these days. Having worked on the web for almost three decades at this point, I’ve seen the regular wax and wane of ideas, techniques, and technologies. Each time that we as developers and designers get into a regular rhythm, some new idea or technology comes along to shake things up and remake our world.


<h2 class="wp-block-heading">How we got here</h2>


I built my first website in the mid-’90s. Design and development on the web back then was a free-for-all, with few established norms. For any layout aside from a single column, we used <code>table</code> elements, often with empty cells containing a single pixel spacer GIF to add empty space. We styled text with numerous <code>font</code> tags, nesting the tags every time we wanted to vary the font style. And we had only three or four typefaces to choose from: Arial, Courier, or Times New Roman. When Verdana and Georgia came out in 1996, we rejoiced because our options had nearly doubled. The only safe colors to choose from were the 216 “web safe” colors known to work across platforms. The few interactive elements (like contact forms, guest books, and counters) were mostly powered by CGI scripts (predominantly written in Perl at the time). Achieving any kind of unique look involved a pile of hacks all the way down. Interaction was often limited to specific pages in a site.


<h3 class="wp-block-heading">The birth of web standards</h3>


At the turn of the century, a new cycle started. Crufty code littered with <code>table</code> layouts and <code>font</code> tags waned, and a push for web standards waxed. <a href="https://alistapart.com/article/fear/">Newer technologies like CSS</a> got more widespread adoption by browsers makers, developers, and designers. This shift toward standards didn’t happen accidentally or overnight. It took active engagement between the <a href="https://www.w3.org/">W3C</a> and browser vendors and heavy evangelism from folks like the <a href="https://www.webstandards.org/">Web Standards Project </a>to build standards. <a href="https://alistapart.com/">A List Apart</a> and books like Designing with Web Standards by Jeffrey Zeldman played key roles in teaching developers and designers why standards are important, how to implement them, and how to sell them to their organizations. And approaches like <a href="http://hesketh.com/publications/progressive_enhancement_and_the_future_of_web_design.html">progressive enhancement</a> introduced the idea that content should be available for all browsers—with additional enhancements available for more advanced browsers. Meanwhile, sites like the <a href="https://csszengarden.com/">CSS Zen Garden</a> showcased just how powerful and versatile CSS can be when combined with a solid semantic HTML structure.


Server-side languages like PHP, Java, and .NET overtook Perl as the predominant back-end processors, and the cgi-bin was tossed in the trash bin. With these better server-side tools came the first era of web applications, starting with content-management systems (particularly in the blogging space with tools like <a href="https://web.archive.org/web/19991012022531/http://blogger.com/">Blogger</a>, <a href="https://web.archive.org/web/20010124065100/http://noahgrey.com/greysoft/">Grey Matter</a>, <a href="https://web.archive.org/web/20101206044705/http://www.movabletype.com/blog/2001/10/please-read-before-downloading.html">Movable Type</a>, and <a href="https://wordpress.org/news/2003/05/wordpress-now-available/">WordPress</a>). In the mid-2000s, <a href="https://alistapart.com/article/gettingstartedwithajax/">AJAX</a> opened doors for asynchronous interaction between the front end and back end. Suddenly, pages could update their content without needing to reload. A crop of JavaScript frameworks like <a href="http://prototypejs.org/">Prototype</a>, <a href="https://web.archive.org/web/20080611093629/http://yuiblog.com/blog/2006/02/13/the-yahoo-user-interface-library/">YUI</a>, and <a href="https://web.archive.org/web/20060204064635/https://jquery.com/">jQuery</a> arose to help developers build more reliable client-side interaction across browsers that had wildly varying levels of standards support. Techniques like <a href="https://alistapart.com/article/dynatext/">image replacement</a> let crafty designers and developers display fonts of their choosing. And technologies like Flash made it possible to add animations, games, and even more interactivity.


These new technologies, standards, and techniques reinvigorated the industry in many ways. Web design flourished as designers and developers explored more diverse styles and layouts. But we still relied on tons of hacks. Early CSS was a huge improvement over table-based layouts when it came to basic layout and text styling, but its limitations at the time meant that designers and developers still relied heavily on images for <a href="https://alistapart.com/article/slidingdoors/">complex shapes (such as rounded or angled corners)</a> and tiled backgrounds for <a href="https://alistapart.com/article/fauxcolumns/">the appearance of full-length columns</a> (among other hacks). Complicated layouts required all manner of nested floats or absolute positioning (or both). Flash and image replacement for custom fonts was a great start toward varying the typefaces from the big five, but both hacks introduced accessibility and performance problems. And JavaScript libraries made it easy for anyone to add a dash of interaction to pages, although at the cost of doubling or even quadrupling the download size of simple websites.


<h3 class="wp-block-heading">The web as software platform</h3>


The symbiosis between the front end and back end continued to improve, and that led to the current era of modern web applications. Between expanded server-side programming languages (which kept growing to include Ruby, Python, Go, and others) and newer front-end tools like React, Vue, and Angular, we could build fully capable software on the web. Alongside these tools came others, including collaborative version control, build automation, and shared package libraries. What was once primarily an environment for linked documents became a realm of infinite possibilities.


At the same time, mobile devices became more capable, and they gave us internet access in our pockets. <a href="https://abookapart.com/products/mobile-first">Mobile apps</a> and <a href="https://alistapart.com/article/responsive-web-design/">responsive design</a> opened up opportunities for new interactions anywhere and any time.


This combination of capable mobile devices and powerful development tools contributed to the waxing of social media and other centralized tools for people to connect and consume. As it became easier and more common to connect with others directly on Twitter, Facebook, and even Slack, the desire for hosted personal sites waned. Social media offered connections on a global scale, with both the good and bad that that entails.


Want a much more extensive history of how we got here, with some other takes on ways that we can improve? Jeremy Keith wrote “<a href="https://adactio.com/articles/20638">Of Time and the Web</a>.” Or check out the “<a href="https://www.webdesignmuseum.org/web-design-history">Web Design History Timeline</a>” at the <a href="https://www.webdesignmuseum.org/">Web Design Museum</a>. Neal Agarwal also has a fun tour through “<a href="https://neal.fun/internet-artifacts/">Internet Artifacts</a>.”


<h2 class="wp-block-heading">Where we are now</h2>


In the last couple of years, it’s felt like we’ve begun to reach another major inflection point. As <a href="https://techcrunch.com/2024/02/07/how-twitters-descent-into-chaos-is-paving-the-way-for-a-new-web/">social-media platforms fracture</a> and wane, there’s been a <a href="https://matthiasott.com/articles/into-the-personal-website-verse">growing interest in owning our own content</a> again. There are many different ways to make a website, from the tried-and-true classic of hosting plain HTML files to <a href="https://www.cloudflare.com/learning/performance/static-site-generator/">static site generators</a> to content management systems of all flavors. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. <a href="https://indieweb.org/Webmention">Webmentions</a>, <a href="https://www.rssboard.org/rss-specification">RSS</a>, <a href="https://activitypub.rocks/">ActivityPub</a>, and other tools of the <a href="https://indieweb.org/">IndieWeb</a> can help with this, but they’re still relatively underimplemented and <a href="https://mxb.dev/blog/the-indieweb-for-everyone/#h-lowering-the-barrier">hard to use for the less nerdy</a>. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.


Browser support for CSS, JavaScript, and other standards like web components has accelerated, especially through efforts like <a href="https://github.com/web-platform-tests/interop">Interop</a>. New technologies gain support across the board in a fraction of the time that they used to. I often learn about a new feature and <a href="https://caniuse.com/">check its browser support</a> only to find that its coverage is already above 80 percent. Nowadays, the barrier to using newer techniques often isn’t browser support but simply the limits of how quickly designers and developers can learn what’s available and how to adopt it.


Today, with <a href="https://daverupert.com/2024/01/time-to-unmaintainable/">a few commands and a couple of lines of code</a>, we can prototype almost any idea. All the tools that we now have available make it easier than ever to start something new. But the upfront cost that these frameworks may save in initial delivery eventually comes due as upgrading and maintaining them becomes a part of our technical debt.


If we rely on third-party frameworks, adopting new standards can sometimes take longer since we may have to wait for those frameworks to adopt those standards. These frameworks—which used to let us adopt new techniques sooner—have now become hindrances instead. These same frameworks often come with <a href="https://tonsky.me/blog/js-bloat/">performance costs</a> too, forcing users to wait for scripts to load before they can read or interact with pages. And when <a href="https://www.kryogenix.org/code/browser/everyonehasjs.html">scripts fail</a> (whether through poor code, network issues, or other environmental factors), there’s often no alternative, leaving users with blank or broken pages.


<h2 class="wp-block-heading">Where do we go from here?</h2>


Today’s hacks help to shape tomorrow’s standards. And there’s nothing inherently wrong with embracing hacks—for now—to move the present forward. Problems only arise when we’re unwilling to admit that they’re hacks or we hesitate to replace them. So what can we do to create the future we want for the web?


Build for the long haul. Optimize for performance, for accessibility, and for the user. Weigh the costs of those developer-friendly tools. They may make your job a little easier today, but how do they affect everything else? What’s the cost to users? To future developers? To standards adoption? Sometimes the convenience may be worth it. Sometimes it’s just a hack that you’ve grown accustomed to. And sometimes it’s holding you back from even better options.


Start from standards. Standards continue to evolve over time, but browsers have done a remarkably good job of continuing to support older standards. The same isn’t always true of third-party frameworks. Sites built with even the hackiest of HTML from the ’90s still <a href="https://www.vortex.com/">work</a><a href="https://www.spacejam.com/1996/"> just fine</a> today. The same can’t always be said of sites built with frameworks even after just a couple years.


Design with care. Whether your craft is code, pixels, or processes, consider the impacts of each decision. The convenience of many a modern tool comes at the cost of not always understanding the underlying decisions that have led to its design and not always considering the impact that those decisions can have. Rather than rushing headlong to “move fast and break things,” use the time saved by modern tools to consider more carefully and design with deliberation.


Always be learning. If you’re always learning, you’re also growing. Sometimes it may be hard to pinpoint what’s worth learning and what’s just today’s hack. You might end up focusing on something that won’t matter next year, even if you were to focus solely on learning standards. (<a href="https://alistapart.com/article/webstandards2008/">Remember XHTML?</a>) But constant learning opens up new connections in your brain, and the hacks that you learn one day may help to inform different experiments another day.


Play, experiment, and be weird! This web that we’ve built is the ultimate experiment. It’s the single largest human endeavor in history, and yet each of us can create our own pocket within it. <a href="https://www.rollingstone.com/culture/culture-commentary/internet-future-about-to-get-weird-1234938403/">Be courageous and try new things</a>. Build a <a href="https://lynnandtonic.com/work/">playground</a> for ideas. Make <a href="https://a-k-apart.com/">goofy experiments</a> in your own mad <a href="https://neal.fun/">science</a> <a href="https://labs.jensimmons.com/">lab</a>. Start your own <a href="https://www.zeldman.com/2023/11/28/fly-my-designers-fly/">small business</a>. There has never been a more empowering place to be creative, take risks, and explore what we’re capable of.


Share and amplify. As you experiment, play, and learn, share what’s worked for you. Write on your own website, post on whichever social media site you prefer, or shout it from a TikTok. <a href="https://alistapart.com/about/contribute/">Write something for A List Apart</a>! But take the time to <a href="https://hidde.blog/sharing-links/">amplify others</a> too: find new voices, learn from them, and share what they’ve taught you.


<h3 class="wp-block-heading">Go forth and make</h3>


As designers and developers for the web (and beyond), we’re responsible for building the future every day, whether that may take the shape of personal websites, social media tools used by billions, or anything in between. Let’s imbue our values into the things that we create, and let’s make the web a better place for everyone. Create that thing that only you are uniquely qualified to make. Then share it, make it better, make it again, or make something new. Learn. Make. Share. Grow. Rinse and repeat. Every time you think that you’ve mastered the web, everything will change.
]]> </description>
<dc:subject>
<![CDATA[State of the Web, Web Strategy]]> </dc:subject>
<dc:date>
2024-02-29T14:45:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Opportunities for AI in Accessibility]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/agustafson/">Aaron Gustafson</a> </author>
<link>
https://alistapart.com/article/opportunities-for-ai-in-accessibility/ </link>
<guid>
https://alistapart.com/article/opportunities-for-ai-in-accessibility/ </guid>
<description>
<![CDATA[
In reading <a href="https://www.joedolson.com/2023/06/accessibility-and-artificial-intelligence/">Joe Dolson’s recent piece on the intersection of AI and accessibility</a>, I absolutely appreciated the skepticism that he has for AI in general as well as for the ways that many have been using it. In fact, I’m very skeptical of AI myself, despite my role at Microsoft as an accessibility innovation strategist who helps run the AI for Accessibility grant program. As with any tool, AI can be used in very constructive, inclusive, and accessible ways; and it can also be used in destructive, exclusive, and harmful ones. And there are a ton of uses somewhere in the mediocre middle as well.


I’d like you to consider this a “yes… and” piece to complement Joe’s post. I’m not trying to refute any of what he’s saying but rather provide some visibility to projects and opportunities where AI can make meaningful differences for people with disabilities. To be clear, I’m not saying that there aren’t real risks or pressing issues with AI that need to be addressed—there are, and we’ve needed to address them, like, yesterday—but I want to take a little time to talk about what’s possible in hopes that we’ll get there one day.


<h2 class="wp-block-heading">Alternative text</h2>


Joe’s piece spends a lot of time talking about computer-vision models generating alternative text. He highlights a ton of valid issues with the current state of things. And while computer-vision models continue to improve in the quality and richness of detail in their descriptions, their results aren’t great. As he rightly points out, the current state of image analysis is pretty poor—especially for certain image types—in large part because current AI systems examine images in isolation rather than within the contexts that they’re in (which is a consequence of having separate “foundation” models for text analysis and image analysis). Today’s models aren’t trained to distinguish between images that are contextually relevant (that should probably have descriptions) and those that are purely decorative (which might not need a description) either. Still, I still think there’s potential in this space.


As Joe mentions, human-in-the-loop authoring of alt text should absolutely be a thing. And if AI can pop in to offer a starting point for alt text—even if that starting point might be a prompt saying What is this BS? That’s not right at all… Let me try to offer a starting point—I think that’s a win.


Taking things a step further, if we can specifically train a model to analyze image usage in context, it could help us more quickly identify which images are likely to be decorative and which ones likely require a description. That will help reinforce which contexts call for image descriptions and it’ll improve authors’ efficiency toward making their pages more accessible.


While complex images—like graphs and charts—are challenging to describe in any sort of succinct way (even for humans), <a href="https://openai.com/research/gpt-4#:~:text=Visual%20inputs:%20VGA%20charger">the image example shared in the GPT4 announcement</a> points to an interesting opportunity as well. Let’s suppose that you came across a chart whose description was simply the title of the chart and the kind of visualization it was, such as: Pie chart comparing smartphone usage to feature phone usage among US households making under $30,000 a year. (That would be a pretty awful alt text for a chart since that would tend to leave many questions about the data unanswered, but then again, let’s suppose that that was the description that was in place.) If your browser knew that that image was a pie chart (because an onboard model concluded this), imagine a world where users could ask questions like these about the graphic:


<ul>
<li>Do more people use smartphones or feature phones?</li>


<li>How many more?</li>


<li>Is there a group of people that don’t fall into either of these buckets?</li>


<li>How many is that?</li>
</ul>


Setting aside the realities of <a href="https://machinelearningmastery.com/a-gentle-introduction-to-hallucinations-in-large-language-models/">large language model (LLM) hallucinations</a>—where a model just makes up plausible-sounding “facts”—for a moment, the opportunity to learn more about images and data in this way could be revolutionary for blind and low-vision folks as well as for people with various forms of color blindness, cognitive disabilities, and so on. It could also be useful in educational contexts to help people who can see these charts, as is, to understand the data in the charts.


Taking things a step further: What if you could ask your browser to simplify a complex chart? What if you could ask it to isolate a single line on a line graph? What if you could ask your browser to transpose the colors of the different lines to work better for form of color blindness you have? What if you could ask it to swap colors for patterns? Given these tools’ chat-based interfaces and our existing ability to manipulate images in today’s AI tools, that seems like a possibility.


Now imagine a purpose-built model that could extract the information from that chart and convert it to another format. For example, perhaps it could turn that pie chart (or better yet, a series of pie charts) into more accessible (and useful) formats, like spreadsheets. That would be amazing!


<h2 class="wp-block-heading">Matching algorithms</h2>


Safiya Umoja Noble absolutely hit the nail on the head when she titled her book <a href="http://algorithmsofoppression.com/">Algorithms of Oppression</a>. While her book was focused on the ways that search engines reinforce racism, I think that it’s equally true that all computer models have the potential to amplify conflict, bias, and intolerance. Whether it’s Twitter always showing you the latest tweet from a bored billionaire, YouTube sending us into a Q-hole, or Instagram warping our ideas of what natural bodies look like, we know that poorly authored and maintained algorithms are incredibly harmful. A lot of this stems from a lack of diversity among the people who shape and build them. When these platforms are built with inclusively baked in, however, there’s real potential for algorithm development to help people with disabilities.


Take <a href="https://www.mentra.com/">Mentra</a>, for example. They are an employment network for neurodivergent people. They use an algorithm to match job seekers with potential employers based on over 75 data points. On the job-seeker side of things, it considers each candidate’s strengths, their necessary and preferred workplace accommodations, environmental sensitivities, and so on. On the employer side, it considers each work environment, communication factors related to each job, and the like. As a company run by neurodivergent folks, Mentra made the decision to flip the script when it came to typical employment sites. They use their algorithm to propose available candidates to companies, who can then connect with job seekers that they are interested in; reducing the emotional and physical labor on the job-seeker side of things.


When more people with disabilities are involved in the creation of algorithms, that can reduce the chances that these algorithms will inflict harm on their communities. That’s why diverse teams are so important.


Imagine that a social media company’s recommendation engine was tuned to analyze who you’re following and if it was tuned to prioritize follow recommendations for people who talked about similar things but who were different in some key ways from your existing sphere of influence. For example, if you were to follow a bunch of nondisabled white male academics who talk about AI, it could suggest that you follow academics who are disabled or aren’t white or aren’t male who also talk about AI. If you took its recommendations, perhaps you’d get a more holistic and nuanced understanding of what’s happening in the AI field. These same systems should also use their understanding of biases about particular communities—including, for instance, the disability community—to make sure that they aren’t recommending any of their users follow accounts that perpetuate biases against (or, worse, spewing hate toward) those groups.


<h2 class="wp-block-heading">Other ways that AI can helps people with disabilities</h2>


If I weren’t trying to put this together between other tasks, I’m sure that I could go on and on, providing all kinds of examples of how AI could be used to help people with disabilities, but I’m going to make this last section into a bit of a lightning round. In no particular order:


<ul>
<li>Voice preservation. You may have seen <a href="https://arxiv.org/abs/2301.02111">the VALL-E paper</a> or <a href="https://www.apple.com/newsroom/2023/05/apple-previews-live-speech-personal-voice-and-more-new-accessibility-features/">Apple’s Global Accessibility Awareness Day announcement</a> or you may be familiar with the voice-preservation offerings from <a href="https://learn.microsoft.com/en-us/azure/cognitive-services/speech-service/custom-neural-voice">Microsoft</a>, <a href="https://www.acapela-group.com/voices/voice-banking/">Acapela</a>, or others. It’s possible to train an AI model to replicate your voice, which can be a tremendous boon for people who have ALS (Lou Gehrig’s disease) or motor-neuron disease or other medical conditions that can lead to an inability to talk. This is, of course, the same tech that can also be used to create audio deepfakes, so it’s something that we need to approach <a href="https://www.microsoft.com/en-us/ai/responsible-ai">responsibly</a>, but the tech has truly transformative potential.</li>


<li>Voice recognition. Researchers like those in the <a href="https://speechaccessibilityproject.beckman.illinois.edu/">Speech Accessibility Project</a> are paying people with disabilities for their help in collecting recordings of people with atypical speech. As I type, they are actively recruiting people with Parkinson’s and related conditions, and they have plans to expand this to other conditions as the project progresses. This research will result in more inclusive data sets that will let more people with disabilities use voice assistants, dictation software, and voice-response services as well as control their computers and other devices more easily, using only their voice.</li>


<li>Text transformation. The current generation of LLMs is quite capable of adjusting existing text content without injecting hallucinations. This is hugely empowering for people with cognitive disabilities who may benefit from text summaries or simplified versions of text or even text that’s prepped for <a href="https://bionic-reading.com/">Bionic Reading</a>.</li>
</ul>


<h2 class="wp-block-heading">The importance of diverse teams and data</h2>


We need to recognize that our differences matter. Our lived experiences are influenced by the intersections of the identities that we exist in. These lived experiences—with all their complexities (and joys and pain)—are valuable inputs to the software, services, and societies that we shape. Our differences need to be represented in the data that we use to train new models, and the folks who contribute that valuable information need to be compensated for sharing it with us. Inclusive data sets yield more robust models that foster more equitable outcomes.


Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that you have content about disabilities that’s authored by people with a range of disabilities, and make sure that that’s well represented in the training data.


Want a model that doesn’t use ableist language? You may be able to use <a href="https://www.selfdefined.app/">existing data sets</a> to build a filter that can intercept and remediate ableist language before it reaches readers. That being said, when it comes to sensitivity reading, AI models won’t be replacing human copy editors anytime soon. 


Want a coding copilot that gives you accessible recommendations from the jump? Train it on code that you know to be accessible.


<hr class="wp-block-separator has-alpha-channel-opacity is-style-dots"/>


I have no doubt that AI can and will harm people… today, tomorrow, and well into the future. But I also believe that we can acknowledge that and, with an eye towards accessibility (and, more broadly, inclusion), make thoughtful, considerate, and intentional changes in our approaches to AI that will reduce harm over time as well. Today, tomorrow, and well into the future.


<hr class="wp-block-separator has-alpha-channel-opacity is-style-dots"/>


Many thanks to Kartik Sawhney for helping me with the development of this piece, Ashley Bischoff for her invaluable editorial assistance, and, of course, Joe Dolson for the prompt.
]]> </description>
<dc:subject>
<![CDATA[Accessibility, Code, Content, Workflow & Tools]]> </dc:subject>
<dc:date>
2024-02-07T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[I am a creative.]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/zeldman/">Jeffrey Zeldman</a> </author>
<link>
https://alistapart.com/article/i-am-a-creative/ </link>
<guid>
https://alistapart.com/article/i-am-a-creative/ </guid>
<description>
<![CDATA[
I am a creative. What I do is alchemy. It is a mystery. I do not so much do it, as let it be done through me.


I am a creative. Not all creative people like this label. Not all see themselves this way. Some creative people see science in what they do. That is their truth, and I respect it. Maybe I even envy them, a little. But my process is different—my being is different.


Apologizing and qualifying in advance is a distraction. That’s what my brain does to sabotage me. I set it aside for now. I can come back later to apologize and qualify. After I’ve said what I came to say. Which is hard enough. 


Except when it is easy and flows like a river of wine.


Sometimes it does come that way. Sometimes what I need to create comes in an instant. I have learned not to say it at that moment, because if you admit that sometimes the idea just comes and it is the best idea and you know it is the best idea, they think you don’t work hard enough.


Sometimes I work and work and work until the idea comes. Sometimes it comes instantly and I don’t tell anyone for three days. Sometimes I’m so excited by the idea that came instantly that I blurt it out, can’t help myself. Like a boy who found a prize in his Cracker Jacks. Sometimes I get away with this. Sometimes other people agree: yes, that is the best idea. Most times they don’t and I regret having  given way to enthusiasm. 


Enthusiasm is best saved for the meeting where it will make a difference. Not the casual get-together that precedes that meeting by two other meetings. Nobody knows why we have all these meetings. We keep saying we’re doing away with them, but then just finding other ways to have them. Sometimes they are even good. But other times they are a distraction from the actual work. The proportion between when meetings are useful, and when they are a pitiful distraction, varies, depending on what you do and where you do it. And who you are and how you do it. Again I digress. I am a creative. That is the theme.


Sometimes many hours of hard and patient work produce something that is barely serviceable. Sometimes I have to accept that and move on to the next project.


<h2 class="wp-block-heading">Don’t ask about process. I am a creative. </h2>


I am a creative. I don’t control my dreams. And I don’t control my best ideas. 


I can hammer away, surround myself with facts or images, and sometimes that works. I can go for a walk, and sometimes that works. I can be making dinner and there’s a Eureka having nothing to do with sizzling oil and bubbling pots. Often I know what to do the instant I wake up. And then, almost as often, as I become conscious and part of the world again, the idea that would have saved me turns to vanishing dust in a mindless wind of oblivion. For creativity, I believe, comes from that other world. The one we enter in dreams, and perhaps, before birth and after death. But that’s for poets to wonder, and I am not a poet. I am a creative. And it’s for theologians to mass armies about in their creative world that they insist is real. But that is another digression. And a depressing one. Maybe on a much more important topic than whether I am a creative or not. But still a digression from what I came here to say.


Sometimes the process is avoidance. And agony. You know the cliché about the tortured artist? It’s true, even when the artist (and let’s put that noun in quotes) is trying to write a soft drink jingle, a callback in a tired sitcom, a budget request.


Some people who hate being called creative may be closeted creatives, but that’s between them and their gods. No offense meant. Your truth is true, too. But mine is for me. 


<h2 class="wp-block-heading">Creatives recognize creatives.</h2>


Creatives recognize creatives like queers recognize queers, like real rappers recognize real rappers, like cons know cons. Creatives feel massive respect for creatives. We love, honor, emulate, and practically deify the great ones. To deify any human is, of course, a tragic mistake. We have been warned. We know better. We know people are just people. They squabble, they are lonely, they regret their most important decisions, they are poor and hungry, they can be cruel, they can be just as stupid as we can, because, like us, they are clay. But. But. But they make this amazing thing. They birth something that did not exist before them, and could not exist without them. They are the mothers of ideas. And I suppose, since it’s just lying there, I have to add that they are the mothers of invention. Ba dum bum! OK, that’s done. Continue.


Creatives belittle our own small achievements, because we compare them to those of the great ones. Beautiful animation! Well, I’m no Miyazaki. Now THAT is greatness. That is greatness straight from the mind of God. This half-starved little thing that I made? It more or less fell off the back of the turnip truck. And the turnips weren’t even fresh.


Creatives knows that, at best, they are <a href="https://www.wikiwand.com/en/Antonio_Salieri">Salieri</a>. Even the creatives who are Mozart believe that. 


I am a creative. I haven’t worked in advertising in 30 years, but in my nightmares, it’s my former creative directors who judge me. And they are right to do so. I am too lazy, too facile, and when it really counts, my mind goes blank. There is no pill for creative dysfunction.


I am a creative. Every deadline I make is an adventure that makes Indiana Jones look like a pensioner snoring in a deck chair. The longer I remain a creative, the faster I am when I do my work and the longer I brood and walk in circles and stare blankly before I do that work. 


I am still 10 times faster than people who are not creative, or people who have only been creative a short while, or people who have only been professionally creative a short while. It’s just that, before I work 10 times as fast as they do, I spend twice as long as they do putting the work off. I am that confident in my ability to do a great job when I put my mind to it. I am that addicted to the adrenaline rush of postponement. I am still that afraid of the jump.


<h2 class="wp-block-heading">I am not an artist.</h2>


I am a creative. Not an artist. Though I dreamed, as a lad, of someday being that. Some of us belittle our gifts and dislike ourselves because we are not Michelangelos and Warhols. That is narcissism—but at least we aren’t in politics.


I am a creative. Though I believe in reason and science, I decide by intuition and impulse. And live with what follows—the catastrophes as well as the triumphs. 


I am a creative. Every word I’ve said here will annoy other creatives, who see things differently. Ask two creatives a question, get three opinions. Our disagreement, our passion about it, and our commitment to our own truth are, at least to me, the proofs that we are creatives, no matter how we may feel about it.


I am a creative. I lament my lack of taste in the areas about which I know very little, which is to say almost all areas of human knowledge. And I trust my taste above all other things in the areas closest to my heart, or perhaps, more accurately, to my obsessions. Without my obsessions, I would probably have to spend my time looking life in the eye, and almost none of us can do that for long. Not honestly. Not really. Because much in life, if you really look at it, is unbearable.


I am a creative. I believe, as a parent believes, that when I am gone, some small good part of me will carry on in the mind of at least one other person.


<h2 class="wp-block-heading">Working saves me from worrying about work.</h2>


I am a creative. I live in dread of my small gift suddenly going away.


I am a creative. I am too busy making the next thing to spend too much time deeply considering that almost nothing I make will come anywhere near the greatness I comically aspire to.


I am a creative. I believe in the ultimate mystery of process. I believe in it so much, I am even fool enough to publish an essay I dictated into a tiny machine and didn’t take time to review or revise. I won’t do this often, I promise. But I did it just now, because, as afraid as I might be of your seeing through my pitiful gestures toward the beautiful, I was even more afraid of forgetting what I came to say. 


There. I think I’ve said it. 
]]> </description>
<dc:subject>
<![CDATA[Career, Content, Creativity, Design, Industry & Business, Process, Writing]]> </dc:subject>
<dc:date>
2024-01-29T15:53:09+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Humility: An Essential Value]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/justindauer/">Justin Dauer</a> </author>
<link>
https://alistapart.com/article/humility-an-essential-value/ </link>
<guid>
https://alistapart.com/article/humility-an-essential-value/ </guid>
<description>
<![CDATA[
Humility, a designer’s essential value—that has a nice ring to it. What about humility, an office manager’s essential value? Or a dentist’s? Or a librarian’s? They all sound great. When humility is our guiding light, the path is always open for fulfillment, evolution, connection, and engagement. In this chapter, we’re going to talk about why.


That said, this is a book for designers, and to that end, I’d like to start with a story—well, a journey, really. It’s a personal one, and I’m going to make myself a bit vulnerable along the way. I call it:


<h2 class="wp-block-heading">The Tale of Justin’s Preposterous Pate</h2>


When I was coming out of art school, a long-haired, goateed neophyte, print was a known quantity to me; design on the web, however, was rife with complexities to navigate and discover, a problem to be solved. Though I had been formally trained in graphic design, typography, and layout, what fascinated me was how these traditional skills might be applied to a fledgling digital landscape. This theme would ultimately shape the rest of my career.


So rather than graduate and go into print like many of my friends, I devoured HTML and JavaScript books into the wee hours of the morning and taught myself how to code during my senior year. I wanted—nay, needed—to better understand the underlying implications of what my design decisions would mean once rendered in a browser.


The late ’90s and early 2000s were the so-called “Wild West” of web design. Designers at the time were all figuring out how to apply design and visual communication to the digital landscape. What were the rules? How could we break them and still engage, entertain, and convey information? At a more macro level, how could my values, inclusive of humility, respect, and connection, align in tandem with that? I was hungry to find out.


Though I’m talking about a different era, those are timeless considerations between non-career interactions and the world of design. What are your core passions, or values, that transcend medium? It’s essentially the same concept we discussed earlier on the direct parallels between what fulfills you, agnostic of the tangible or digital realms; the core themes are all the same.


First within tables, animated GIFs, Flash, then with Web Standards, <code>div</code>s, and CSS, there was personality, raw unbridled creativity, and unique means of presentment that often defied any semblance of a visible grid. Splash screens and “browser requirement” pages aplenty. Usability and accessibility were typically victims of such a creation, but such paramount facets of any digital design were largely (and, in hindsight, unfairly) disregarded at the expense of experimentation.


For example, this iteration of my personal portfolio site (“the pseudoroom”) from that era was experimental, if not a bit heavy- handed, in the visual communication of the concept of a living sketchbook. Very skeuomorphic. I collaborated with fellow designer and dear friend Marc Clancy (now a co-founder of the creative project organizing app Milanote) on this one, where we’d first sketch and then pass a Photoshop file back and forth to trick things out and play with varied user interactions. Then, I’d break it down and code it into a digital layout.


<figure class="wp-block-image size-full is-resized"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2023/06/designers-journey-2-1.jpg" alt="" class="wp-image-7173967" width="846"/><figcaption class="wp-element-caption">Figure 1: “the pseudoroom” website, hitting the sketchbook metaphor hard.</figcaption></figure>


Along with design folio pieces, the site also offered free downloads for Mac OS customizations: desktop wallpapers that were effectively design experimentation, custom-designed typefaces, and desktop icons.


From around the same time, GUI Galaxy was a design, pixel art, and Mac-centric news portal some graphic designer friends and I conceived, designed, developed, and deployed.


<figure class="wp-block-image size-large is-resized"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2023/06/designers-journey-2-2-1024x907.jpg" alt="" class="wp-image-7173968" width="846"/><figcaption class="wp-element-caption">Figure 2: GUI Galaxy, web standards-compliant design news portal</figcaption></figure>


Design news portals were incredibly popular during this period, featuring (what would now be considered) Tweet-size, small-format snippets of pertinent news from the categories I previously mentioned. If you took Twitter, curated it to a few categories, and wrapped it in a custom-branded experience, you’d have a design news portal from the late 90s / early 2000s.


We as designers had evolved and created a bandwidth-sensitive, web standards award-winning, much more accessibility-conscious website. Still ripe with experimentation, yet more mindful of equitable engagement. You can see a couple of content panes here, noting general news (tech, design) and Mac-centric news below. We also offered many of the custom downloads I cited before as present on my folio site but branded and themed to GUI Galaxy.


The site’s backbone was a homegrown CMS, with the presentation layer consisting of global design + illustration + news author collaboration. And the collaboration effort here, in addition to experimentation on a ‘brand’ and content delivery, was hitting my core. We were designing something bigger than any single one of us and connecting with a global audience.


Collaboration and connection transcend medium in their impact, immensely fulfilling me as a designer.


Now, why am I taking you down this trip of design memory lane? Two reasons.


First, there’s a reason for the nostalgia for that design era (the “Wild West” era, as I called it earlier): the inherent exploration, personality, and creativity that saturated many design portals and personal portfolio sites. Ultra-finely detailed pixel art UI, custom illustration, bespoke vector graphics, all underpinned by a strong design community.


Today’s web design has been in a period of stagnation. I suspect there’s a strong chance you’ve seen a site whose structure looks something like this: a hero image / banner with text overlaid, perhaps with a lovely rotating carousel of images (laying the snark on heavy there), a call to action, and three columns of sub-content directly beneath. Maybe an icon library is employed with selections that vaguely relate to their respective content.


Design, as it’s applied to the digital landscape, is in dire need of thoughtful layout, typography, and visual engagement that goes hand-in-hand with all the modern considerations we now know are paramount: usability. Accessibility. Load times and bandwidth- sensitive content delivery. A responsive presentation that meets human beings wherever they’re engaging from. We must be mindful of, and respectful toward, those concerns—but not at the expense of creativity of visual communication or via replicating cookie-cutter layouts.


<h2 class="wp-block-heading">Pixel Problems</h2>


Websites during this period were often designed and built on Macs whose OS and desktops looked something like this. This is Mac OS 7.5, but 8 and 9 weren’t that different.


<figure class="wp-block-image size-large is-resized"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2023/06/designers-journey-2-3-1024x768.jpg" alt="" class="wp-image-7173969" width="846"/><figcaption class="wp-element-caption">Figure 3: A Mac OS 7.5-centric desktop.</figcaption></figure>


Desktop icons fascinated me: how could any single one, at any given point, stand out to get my attention? In this example, the user’s desktop is tidy, but think of a more realistic example with icon pandemonium. Or, say an icon was part of a larger system grouping (fonts, extensions, control panels)—how did it also maintain cohesion amongst a group?


These were 32 x 32 pixel creations, utilizing a 256-color palette, designed pixel-by-pixel as mini mosaics. To me, this was the embodiment of digital visual communication under such ridiculous constraints. And often, ridiculous restrictions can yield the purification of concept and theme.


So I began to research and do my homework. I was a student of this new medium, hungry to dissect, process, discover, and make it my own.


Expanding upon the notion of exploration, I wanted to see how I could push the limits of a 32x32 pixel grid with that 256-color palette. Those ridiculous constraints forced a clarity of concept and presentation that I found incredibly appealing. The digital gauntlet had been tossed, and that challenge fueled me. And so, in my dorm room into the wee hours of the morning, I toiled away, bringing conceptual sketches into mini mosaic fruition.


These are some of my creations, utilizing the only tool available at the time to create icons called ResEdit. ResEdit was a clunky, built-in Mac OS utility not really made for exactly what we were using it for. At the core of all of this work: Research. Challenge. Problem- solving. Again, these core connection-based values are agnostic of medium.


<figure class="wp-block-image size-large is-resized"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2023/06/designers-journey-2-4-1024x977.png" alt="" class="wp-image-7173970" width="846"/><figcaption class="wp-element-caption">Figure 4: A selection of my pixel art design, 32x32 pixel canvas, 8-bit palette</figcaption></figure>


There’s one more design portal I want to talk about, which also serves as the second reason for my story to bring this all together.


This is K10k, short for Kaliber 1000. K10k was founded in 1998 by Michael Schmidt and Toke Nygaard, and was the design news portal on the web during this period. With its pixel art-fueled presentation, ultra-focused care given to every facet and detail, and with many of the more influential designers of the time who were invited to be news authors on the site, well... it was the place to be, my friend. With respect where respect is due, GUI Galaxy’s concept was inspired by what these folks were doing.


<figure class="wp-block-image size-full is-resized"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2023/06/designers-journey-2-5.png" alt="" class="wp-image-7173971" width="846"/><figcaption class="wp-element-caption">Figure 5: The K10k website</figcaption></figure>


For my part, the combination of my web design work and pixel art exploration began to get me some notoriety in the design scene. Eventually, K10k noticed and added me as one of their very select group of news authors to contribute content to the site.


Amongst my personal work and side projects—and now with this inclusion—in the design community, this put me on the map. My design work also began to be published in various printed collections, in magazines domestically and overseas, and featured on other design news portals. With that degree of success while in my early twenties, something else happened:


I evolved—devolved, really—into a colossal asshole (and in just about a year out of art school, no less). The press and the praise became what fulfilled me, and they went straight to my head. They inflated my ego. I actually felt somewhat superior to my fellow designers.


The casualties? My design stagnated. Its evolution—my evolution— stagnated.


I felt so supremely confident in my abilities that I effectively stopped researching and discovering. When previously sketching concepts or iterating ideas in lead was my automatic step one, I instead leaped right into Photoshop. I drew my inspiration from the smallest of sources (and with blinders on). Any critique of my work from my peers was often vehemently dismissed. The most tragic loss: I had lost touch with my values.


My ego almost cost me some of my friendships and burgeoning professional relationships. I was toxic in talking about design and in collaboration. But thankfully, those same friends gave me a priceless gift: candor. They called me out on my unhealthy behavior.


Admittedly, it was a gift I initially did not accept but ultimately was able to deeply reflect upon. I was soon able to accept, and process, and course correct. The realization laid me low, but the re-awakening was essential. I let go of the “reward” of adulation and re-centered upon what stoked the fire for me in art school. Most importantly: I got back to my core values.


<h2 class="wp-block-heading">Always Students</h2>


Following that short-term regression, I was able to push forward in my personal design and career. And I could self-reflect as I got older to facilitate further growth and course correction as needed.


As an example, let’s talk about the Large Hadron Collider. The LHC was designed “to help answer some of the fundamental open questions in physics, which concern the basic laws governing the interactions and forces among the elementary objects, the deep structure of space and time, and in particular the interrelation between quantum mechanics and general relativity.” Thanks, Wikipedia.


Around fifteen years ago, in one of my earlier professional roles, I designed the interface for the application that generated the LHC’s particle collision diagrams. These diagrams are the rendering of what’s actually happening inside the Collider during any given particle collision event and are often considered works of art unto themselves.


Designing the interface for this application was a fascinating process for me, in that I worked with Fermilab physicists to understand what the application was trying to achieve, but also how the physicists themselves would be using it. To that end, in this role,


I cut my teeth on usability testing, working with the Fermilab team to iterate and improve the interface. How they spoke and what they spoke about was like an alien language to me. And by making myself humble and working under the mindset that I was but a student, I made myself available to be a part of their world to generate that vital connection.


I also had my first ethnographic observation experience: going to the Fermilab location and observing how the physicists used the tool in their actual environment, on their actual terminals. For example, one takeaway was that due to the level of ambient light-driven contrast within the facility, the data columns ended up using white text on a dark gray background instead of black text-on-white. This enabled them to pore over reams of data during the day and ease their eye strain. And Fermilab and CERN are government entities with rigorous accessibility standards, so my knowledge in that realm also grew. The barrier-free design was another essential form of connection.


So to those core drivers of my visual problem-solving soul and ultimate fulfillment: discovery, exposure to new media, observation, human connection, and evolution. What opened the door for those values was me checking my ego before I walked through it.


An evergreen willingness to listen, learn, understand, grow, evolve, and connect yields our best work. In particular, I want to focus on the words ‘grow’ and ‘evolve’ in that statement. If we are always students of our craft, we are also continually making ourselves available to evolve. Yes, we have years of applicable design study under our belt. Or the focused lab sessions from a UX bootcamp. Or the monogrammed portfolio of our work. Or, ultimately, decades of a career behind us.


But all that said: experience does not equal “expert.”


As soon as we close our minds via an inner monologue of ‘knowing it all’ or branding ourselves a “#thoughtleader” on social media, the designer we are is our final form. The designer we can be will never exist.
]]> </description>
<dc:subject>
<![CDATA[Design]]> </dc:subject>
<dc:date>
2023-06-22T13:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Personalization Pyramid: A Framework for Designing with User Data]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/colineagan/">Colin Eagan</a>, <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/jeffmacintyre/">Jeffrey MacIntyre</a> </author>
<link>
https://alistapart.com/article/personalization-pyramid/ </link>
<guid>
https://alistapart.com/article/personalization-pyramid/ </guid>
<description>
<![CDATA[
As a UX professional in today’s data-driven landscape, it’s increasingly likely that you’ve been asked to design a personalized digital experience, whether it’s a public website, user portal, or native application. Yet while there continues to be no shortage of marketing hype around personalization platforms, we still have very few standardized approaches for implementing personalized UX.


That’s where we come in. After completing dozens of personalization projects over the past few years, we gave ourselves a goal: could you create a holistic personalization framework specifically for UX practitioners? The Personalization Pyramid is a designer-centric model for standing up human-centered personalization programs, spanning data, segmentation, content delivery, and overall goals. By using this approach, you will be able to understand the core components of a contemporary, UX-driven personalization program (or at the very least know enough to get started).


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image20-1024x595.png" alt="A chart answering the question Do you have the resources you need to run personalization in your organization? Globally, 13% don’t 33% have limited access, 39% have it (on demand), and 15% have it dedicated." class="wp-image-7173666"/><figcaption class="wp-element-caption">Growing tools for personalization: According to a Dynamic Yield survey, 39% of respondents felt support is available on-demand when a business case is made for it (up 15% from 2020).Source: “The State of Personalization Maturity – Q4 2021” Dynamic Yield conducted its annual maturity survey across roles and sectors in the Americas (AMER), Europe and the Middle East (EMEA), and the Asia-Pacific (APAC) regions. This marks the fourth consecutive year publishing our research, which includes more than 450 responses from individuals in the C-Suite, Marketing, Merchandising, CX, Product, and IT.</figcaption></figure>


<h2>Getting Started</h2>


For the sake of this article, we’ll assume you’re already familiar with the basics of digital personalization. A good overview can be found here: <a href="https://www.uxbooth.com/articles/website-personalization-planning/">Website Personalization Planning</a>. While UX projects in this area can take on many different forms, they often stem from similar starting points.      


Common scenarios for starting a personalization project:


<ul>
<li>Your organization or client purchased a content management system (CMS) or marketing automation platform (MAP) or related technology that supports personalization</li>


<li>The CMO, CDO, or CIO has identified personalization as a goal</li>


<li>Customer data is disjointed or ambiguous</li>


<li>You are running some isolated targeting campaigns or A/B testing</li>


<li>Stakeholders disagree on personalization approach</li>


<li>Mandate of customer privacy rules (e.g. GDPR) requires revisiting existing user targeting practices</li>
</ul>


<figure class="wp-block-image size-full is-resized"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image22.png" alt="Two men and a woman discussing personalization using a card deck. They are seated at a round table in a hotel conference room. The workshop leaders, two women, are at a podium in the background." class="wp-image-7173667" width="768" height="576"/><figcaption class="wp-element-caption">Workshopping personalization at a conference.</figcaption></figure>


Regardless of where you begin, a successful personalization program will require the same core building blocks. We’ve captured these as the “levels” on the pyramid. Whether you are a UX designer, researcher, or strategist, understanding the core components can help make your contribution successful.  


<figure class="wp-block-image size-large is-resized"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image14-975x1024.png" alt="The Personalization Pyramid visualized. The pyramid is stacks labeled, from the bottom, raw data (1m+), actionable data (100k+), user segments (1k+), contexts & campaigns (100s), touchpoints (dozens), goals (handful). The North Star (one) is above. An arrow for prescriptive, business driven data goes up the left side and an arrow for adaptive user-driven data goes down the right side." class="wp-image-7173665" width="488" height="512"/><figcaption class="wp-element-caption">From the ground up: Soup-to-nuts personalization, without going nuts.</figcaption></figure>


From top to bottom, the levels include:


<ol>
<li>North Star: What larger strategic objective is driving the personalization program? </li>


<li>Goals: What are the specific, measurable outcomes of the program? </li>


<li>Touchpoints: Where will the personalized experience be served?</li>


<li>Contexts and Campaigns: What personalization content will the user see?</li>


<li>User Segments: What constitutes a unique, usable audience? </li>


<li>Actionable Data: What reliable and authoritative data is captured by our technical platform to drive personalization?  </li>


<li>Raw Data: What wider set of data is conceivably available (already in our setting) allowing you to personalize?</li>
</ol>


We’ll go through each of these levels in turn. To help make this actionable, we created an accompanying deck of cards to illustrate specific examples from each level. We’ve found them helpful in personalization brainstorming sessions, and will include examples for you here.


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image2.png" alt="A deck of personalization brainstorming cards (the size of playing cards) against a black background." class="wp-image-7173668"/><figcaption class="wp-element-caption">Personalization pack: Deck of cards to help kickstart your personalization brainstorming.</figcaption></figure>


<h2>Starting at the Top</h2>


The components of the pyramid are as follows:


<h3>North Star</h3>


A north star is what you are aiming for overall with your personalization program (big or small). The North Star defines the (one) overall mission of the personalization program. What do you wish to accomplish? North Stars cast a shadow. The bigger the star, the bigger the shadow. Example of North Starts might include: 


<ol>
<li>Function: Personalize based on basic user inputs. Examples: “Raw” notifications, basic search results, system user settings and configuration options, general customization, basic optimizations</li>


<li>Feature: Self-contained personalization componentry. Examples: “Cooked” notifications, advanced optimizations (geolocation), basic dynamic messaging, customized modules, automations, recommenders</li>


<li>Experience: Personalized user experiences across multiple interactions and user flows. Examples: Email campaigns, landing pages, advanced messaging (i.e. C2C chat) or conversational interfaces, larger user flows and content-intensive optimizations (localization).</li>


<li>Product: Highly differentiating personalized product experiences. Examples: Standalone, branded experiences with personalization at their core, like the “algotorial” playlists by Spotify such as Discover Weekly.</li>
</ol>


<figure class="wp-block-gallery has-nested-images columns-default is-cropped">
<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image7-656x1024.jpg" alt="Function: React to basic user inputs" class="wp-image-7173669"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image18-656x1024.jpg" alt="Feature: personalized modules" class="wp-image-7173670"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image8-656x1024.jpg" alt="Experience: Integrated personalization" class="wp-image-7173671"/></figure>
<figcaption class="blocks-gallery-caption wp-element-caption">North star cards. These can help orient your team towards a common goal that personalization will help achieve; Also, these are useful for characterizing the end-state ambition of the presently stated personalization effort.</figcaption></figure>


<h3>Goals</h3>


As in any good UX design, personalization can help accelerate <a href="https://www.uxbooth.com/articles/designing-for-customer-intentions-part-1/">designing with customer intentions</a>. Goals are the tactical and measurable metrics that will prove the overall program is successful. A good place to start is with your current analytics and measurement program and metrics you can benchmark against. In some cases, new goals may be appropriate. The key thing to remember is that personalization itself is not a goal, rather it is a means to an end. Common goals include:


<ul>
<li>Conversion</li>


<li>Time on task</li>


<li>Net promoter score (NPS)</li>


<li>Customer satisfaction </li>
</ul>


<figure class="wp-block-gallery has-nested-images columns-default is-cropped">
<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image12-656x1024.jpg" alt="NPS: Net Promoter Score" class="wp-image-7173674"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image23-656x1024.jpg" alt="Time on Task: Users move quicker" class="wp-image-7173672"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image13-656x1024.jpg" alt="Conversion: Move more of the thing" class="wp-image-7173673"/></figure>
<figcaption class="blocks-gallery-caption wp-element-caption">Goal cards. Examples of some common KPIs related to personalization that are concrete and measurable.</figcaption></figure>


<h3>Touchpoints</h3>


Touchpoints are where the personalization happens. As a UX designer, this will be one of your largest areas of responsibility. The touchpoints available to you will depend on how your personalization and associated technology capabilities are instrumented, and should be rooted in improving a user’s experience at a particular point in the journey. Touchpoints can be multi-device (mobile, in-store, website) but also more granular (web banner, web pop-up etc.). Here are some examples:


Channel-level Touchpoints


<ul>
<li>Email: Role</li>


<li>Email: Time of open</li>


<li>In-store display (JSON endpoint)</li>


<li>Native app</li>


<li>Search</li>
</ul>


Wireframe-level Touchpoints


<ul>
<li>Web overlay</li>


<li>Web alert bar</li>


<li>Web banner</li>


<li>Web content block</li>


<li>Web menu</li>
</ul>


<figure class="wp-block-gallery has-nested-images columns-default is-cropped">
<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image25-656x1024.jpg" alt="In-store Display: End-cap interfaces" class="wp-image-7173677"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image11-656x1024.jpg" alt="Email: Time, personalize at time of open" class="wp-image-7173675"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image19-656x1024.jpg" alt="Content Block: Into the woodwork" class="wp-image-7173676"/></figure>
<figcaption class="blocks-gallery-caption wp-element-caption">Touchpoint cards. Examples of common personalization touchpoints: these can vary from narrow (e.g., email) to broad (e.g., in-store).</figcaption></figure>


If you’re designing for web interfaces, for example, you will likely need to include personalized “zones” in your wireframes. The content for these can be presented programmatically in touchpoints based on our next step, contexts and campaigns.


<figure class="wp-block-gallery has-nested-images columns-default is-cropped">
<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image21.png" alt="" class="wp-image-7173678"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image17.png" alt="" class="wp-image-7173679"/></figure>
<figcaption class="blocks-gallery-caption wp-element-caption">Targeted Zones: Examples from Kibo of personalized “zones” on page-level wireframes occurring at various stages of a user journey (Engagement phase at left and Purchase phase at right.) Source: “Essential Guide to End-to-End Personaliztion” by Kibo.</figcaption></figure>


<h3>Contexts and Campaigns</h3>


Once you’ve outlined some touchpoints, you can consider the actual personalized content a user will receive. Many personalization tools will refer to these as “campaigns” (so, for example, a campaign on a web banner for new visitors to the website). These will programmatically be shown at certain touchpoints to certain user segments, as defined by user data. At this stage, we find it helpful to consider two separate models: a context model and a content model. The context helps you consider the level of engagement of the user at the personalization moment, for example a user casually browsing information vs. doing a deep-dive. Think of it in terms of information retrieval behaviors. The content model can then help you determine what type of personalization to serve based on the context (for example, an “Enrich” campaign that shows related articles may be a suitable supplement to extant content).


Personalization Context Model:


<ol>
<li>Browse</li>


<li>Skim</li>


<li>Nudge</li>


<li>Feast</li>
</ol>


Personalization Content Model:


<ol>
<li>Alert</li>


<li>Make Easier</li>


<li>Cross-Sell</li>


<li>Enrich</li>
</ol>


We’ve written extensively about each of these models elsewhere, so if you’d like to read more you can check out Colin’s <a href="https://alistapart.com/article/emerging-ux-role-in-personalization/">Personalization Content Model</a> and Jeff’s <a href="https://bucket.circle.so/c/field-notes/progressive-personalization-a-decisionmaking-model-for-better-outcomes-in-personalized-ux">Personalization Context Model</a>. 


<figure class="wp-block-gallery has-nested-images columns-default is-cropped">
<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image28-656x1024.jpg" alt="Cross Sell: You may also like…" class="wp-image-7173681"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image3-656x1024.jpg" alt="Enrich: You might find this interesting" class="wp-image-7173682"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image27-656x1024.jpg" alt="Browse: Lean back, shallow engagement" class="wp-image-7173680"/></figure>
<figcaption class="blocks-gallery-caption wp-element-caption">Campaign and Context cards: This level of the pyramid can help your team focus around the types of personalization to deliver end users and the use-cases in which they will experience it.</figcaption></figure>


<h3>User Segments</h3>


User segments can be created prescriptively or adaptively, based on user research (e.g. via rules and logic tied to set user behaviors or via A/B testing). At a minimum you will likely need to consider how to treat the unknown or first-time visitor, the guest or returning visitor for whom you may have a stateful cookie (or equivalent post-cookie identifier), or the authenticated visitor who is logged in. Here are some examples from the personalization pyramid:


<ul>
<li>Unknown</li>


<li>Guest</li>


<li>Authenticated</li>


<li>Default</li>


<li>Referred</li>


<li>Role</li>


<li>Cohort</li>


<li>Unique ID</li>
</ul>


<figure class="wp-block-gallery has-nested-images columns-default is-cropped">
<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image16-656x1024.jpg" alt="Authenticated: Logged in with token" class="wp-image-7173685"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image10-656x1024.jpg" alt="Unknown: Could be anyone really" class="wp-image-7173683"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image9-656x1024.jpg" alt="Guest: Dropped a cookie" class="wp-image-7173684"/></figure>
<figcaption class="blocks-gallery-caption wp-element-caption">Segment cards. Examples of common personalization segments: at a minimum, you will need to consider the anonymous, guest, and logged in user types. Segmentation can get dramatically more complex from there.</figcaption></figure>


<h3>Actionable Data</h3>


Every organization with any digital presence has data. It’s a matter of asking what data you can ethically collect on users, its inherent reliability and value, as to how can you use it (sometimes known as “data activation.”) Fortunately, the tide is turning to first-party data: a recent study by Twilio estimates some 80% of businesses are using at least some type of first-party data to personalize the customer experience. 


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image6-1024x714.png" alt="Chart that answers the question "Why is your company focusing on using first-party data for personalization?" The top answer (at 53%) is "it’s higher quality." That is followed by "It’s easier to manage" (46%), "it provides better privacy" (45%), "it’s easier to obtain" (42%), "it’s more cost-effective" (40%), "it’s more ethical" (37%), "our customers want us to" (36%), "it’s the industry norm" (27%), "it’s easier to comply with regulations" (27%), and "we are phasing out 3rd party cookies" (21%)." class="wp-image-7173686"/><figcaption class="wp-element-caption">Source: “The State of Personalization 2021” by Twilio. Survey respondents were n=2,700 adult consumers who have purchased something online in the past 6 months, and n=300 adult manager+ decision-makers at consumer-facing companies that provide goods and/or services online. Respondents were from the United States, United Kingdom, Australia, and New Zealand.Data was collected from April 8 to April 20, 2021.</figcaption></figure>


First-party data represents multiple advantages on the UX front, including being relatively simple to collect, more likely to be accurate, and less susceptible to the “creep factor” of third-party data. So a key part of your UX strategy should be to determine what the best form of data collection is on your audiences. Here are some examples:


<figure class="wp-block-gallery has-nested-images columns-default is-cropped">
<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image15-656x1024.jpg" alt="Quizes: Tell us what you like" class="wp-image-7173691"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image5-656x1024.jpg" alt="Behavioral profiling: Males 40+ who wear fedoras" class="wp-image-7173689"/></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image1-656x1024.jpg" alt="Campaign Source: Your discount code 29780…" class="wp-image-7173688"/></figure>
</figure>


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image4.png" alt="Chart showing the impact of personalization across different phases of personalization maturity. It shows that effort is high in the early phases, but drops off quickly starting in phase 3 (machine learning) while at the same time conversion rates, AOV, and ROI increase from a relatively low level to off the chart." class="wp-image-7173692"/><figcaption class="wp-element-caption">Figure 1.1.2: Example of a personalization maturity curve, showing progression from basic recommendations functionality to true individualization. Credit: https://kibocommerce.com/blog/kibos-personalization-maturity-chart/</figcaption></figure>


There is a progression of profiling when it comes to recognizing and making decisioning about different audiences and their signals. It tends to move towards more granular constructs about smaller and smaller cohorts of users as time and confidence and data volume grow.


While some combination of implicit / explicit data is generally a prerequisite for any implementation (more commonly referred to as first party and third-party data) ML efforts are typically not cost-effective directly out of the box. This is because a strong data backbone and content repository is a prerequisite for optimization. But these approaches should be considered as part of the larger roadmap and may indeed help accelerate the organization’s overall progress. Typically at this point you will partner with key stakeholders and product owners to design a profiling model. The profiling model includes defining approach to configuring profiles, profile keys, profile cards and pattern cards. A multi-faceted approach to profiling which makes it scalable.


<h2>Pulling it Together</h2>


While the cards comprise the starting point to an inventory of sorts (we provide blanks for you to tailor your own), a set of potential levers and motivations for the style of personalization activities you aspire to deliver, they are more valuable when thought of in a grouping. 


In assembling a card “hand”, one can begin to trace the entire trajectory from leadership focus down through a strategic and tactical execution. It is also at the heart of the way both co-authors have conducted workshops in assembling a program backlog—which is a fine subject for another article.


In the meantime, what is important to note is that each colored class of card is helpful to survey in understanding the range of choices potentially at your disposal, it is threading through and making concrete decisions about for whom this decisioning will be made: where, when, and how.


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/12/image26.jpg" alt="Cards on a table. At the top: Function is the north star & customer satisfaction is the goal. User segment is unknown, the actionable data is a quiz, context is a nudge, campaign is to make something easier, and the touchpoint is a banner." class="wp-image-7173693"/><figcaption class="wp-element-caption">Scenario A: We want to use personalization to improve customer satisfaction on the website. For unknown users, we will create a short quiz to better identify what the user has come to do. This is sometimes referred to as “badging” a user in onboarding contexts, to better characterize their present intent and context.</figcaption></figure>


<h2>Lay Down Your Cards</h2>


Any sustainable personalization strategy must consider near, mid and long-term goals. Even with the leading CMS platforms like Sitecore and Adobe or the most exciting composable CMS DXP out there, there is simply no “easy button” wherein a personalization program can be stood up and immediately view meaningful results. That said, there is a common grammar to all personalization activities, just like every sentence has nouns and verbs. These cards attempt to map that territory.



]]> </description>
<dc:subject>
<![CDATA[Content, Interaction Design]]> </dc:subject>
<dc:date>
2022-12-08T15:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Mobile-First CSS: Is It Time for a Rethink?]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/patrick-clancey/">Patrick Clancey</a> </author>
<link>
https://alistapart.com/article/mobile-first-css-is-it-time-for-a-rethink/ </link>
<guid>
https://alistapart.com/article/mobile-first-css-is-it-time-for-a-rethink/ </guid>
<description>
<![CDATA[
The mobile-first design methodology is great—it focuses on what really matters to the user, it’s well-practiced, and it’s been a common design pattern for years. So developing your CSS mobile-first should also be great, too…right? 


Well, not necessarily. Classic mobile-first CSS development is based on the principle of overwriting style declarations: you begin your CSS with default style declarations, and overwrite and/or add new styles as you add breakpoints with <code>min-width</code> media queries for larger viewports (for a good overview see “<a href="https://www.mightyminnow.com/2013/11/what-is-mobile-first-css-and-why-does-it-rock/">What is Mobile First CSS and Why Does It Rock?</a>”). But all those exceptions create complexity and inefficiency, which in turn can lead to an increased testing effort and a code base that’s harder to maintain. Admit it—how many of us willingly want that?


On your own projects, mobile-first CSS may yet be the best tool for the job, but first you need to evaluate just how appropriate it is in light of the visual design and user interactions you’re working on. To help you get started, here’s how I go about tackling the factors you need to watch for, and I’ll discuss some alternate solutions if mobile-first doesn’t seem to suit your project.


<h2>Advantages of mobile-first</h2>


Some of the things to like with mobile-first CSS development—and why it’s been the de facto development methodology for so long—make a lot of sense:


Development hierarchy. One thing you undoubtedly get from mobile-first is a nice development hierarchy—you just focus on the mobile view and get developing. 


Tried and tested. It’s a tried and tested methodology that’s worked for years for a reason: it solves a problem really well.


Prioritizes the mobile view. The mobile view is the simplest and arguably the most important, as it encompasses all the key user journeys, and often accounts for a higher proportion of user visits (depending on the project). 


Prevents desktop-centric development. As development is done using desktop computers, it can be tempting to initially focus on the desktop view. But thinking about mobile from the start prevents us from getting stuck later on; no one wants to spend their time retrofitting a desktop-centric site to work on mobile devices!


<h2>Disadvantages of mobile-first</h2>


Setting style declarations and then overwriting them at higher breakpoints can lead to undesirable ramifications:


More complexity. The farther up the breakpoint hierarchy you go, the more unnecessary code you inherit from lower breakpoints. 


Higher CSS specificity. Styles that have been reverted to their browser default value in a class name declaration now have a higher specificity. This can be a headache on large projects when you want to keep the CSS selectors as simple as possible.


Requires more regression testing. Changes to the CSS at a lower view (like adding a new style) requires all higher breakpoints to be regression tested.


The browser can’t prioritize CSS downloads. At wider breakpoints, classic mobile-first <code>min-width</code> media queries don’t leverage the browser’s capability to download CSS files in priority order.


<h2>The problem of property value overrides</h2>


There is nothing inherently wrong with overwriting values; CSS was designed to do just that. Still, inheriting incorrect values is unhelpful and can be burdensome and inefficient. It can also lead to increased style specificity when you have to overwrite styles to reset them back to their defaults, something that may cause issues later on, especially if you are using a combination of bespoke CSS and utility classes. We won’t be able to use a utility class for a style that has been reset with a higher specificity.


With this in mind, I’m developing CSS with a focus on the default values much more these days. Since there’s no specific order, and no chains of specific values to keep track of, this frees me to develop breakpoints simultaneously. I concentrate on finding common styles and isolating the specific exceptions in closed media query ranges (that is, any range with a <code>max-width</code> set). 


This approach opens up some opportunities, as you can look at each breakpoint as a clean slate. If a component’s layout looks like it should be based on Flexbox at all breakpoints, it’s fine and can be coded in the default style sheet. But if it looks like Grid would be much better for large screens and Flexbox for mobile, these can both be done entirely independently when the CSS is put into closed media query ranges. Also, developing simultaneously requires you to have a good understanding of any given component in all breakpoints up front. This can help surface issues in the design earlier in the development process. We don’t want to get stuck down a rabbit hole building a complex component for mobile, and then get the designs for desktop and find they are equally complex and incompatible with the HTML we created for the mobile view!


Though this approach isn’t going to suit everyone, I encourage you to give it a try. There are plenty of tools out there to help with concurrent development, such as <a href="https://responsively.app/">Responsively App</a>, <a href="https://blisk.io/">Blisk</a>, and many others. 


Having said that, I don’t feel the order itself is particularly relevant. If you are comfortable with focusing on the mobile view, have a good understanding of the requirements for other breakpoints, and prefer to work on one device at a time, then by all means stick with the classic development order. The important thing is to identify common styles and exceptions so you can put them in the relevant stylesheet—a sort of manual tree-shaking process! Personally, I find this a little easier when working on a component across breakpoints, but that’s by no means a requirement.


<h2>Closed media query ranges in practice </h2>


In classic mobile-first CSS we overwrite the styles, but we can avoid this by using media query ranges. To illustrate the difference (I’m using SCSS for brevity), let’s assume there are three visual designs: 


<ul><li>smaller than 768</li><li>from 768 to below 1024</li><li>1024 and anything larger </li></ul>


Take a simple example where a block-level element has a default <code>padding</code> of “20px,” which is overwritten at tablet to be “40px” and set back to “20px” on desktop.


<figure class="wp-block-table">
<table><tbody>
<tr>
<td valign="top">Classic <code>min-width</code> mobile-first
<pre><code class="language-css">.my-block {
padding: 20px;
@media (min-width: 768px) {
padding: 40px;
}
@media (min-width: 1024px) {
padding: 20px;
}
}</code></pre></td>
<td valign="top">Closed media query range
<pre><code class="language-css">.my-block {
padding: 20px;
@media (min-width: 768px) and (max-width: 1023.98px) {
padding: 40px;
}
}</code></td>
</tr>
</tbody></table>
</figure>


The subtle difference is that the mobile-first example sets the default <code>padding</code> to “20px” and then overwrites it at each breakpoint, setting it three times in total. In contrast, the second example sets the default <code>padding</code> to “20px” and only overrides it at the relevant breakpoint where it isn’t the default value (in this instance, tablet is the exception).


The goal is to: 


<ul><li>Only set styles when needed. </li><li>Not set them with the expectation of overwriting them later on, again and again. </li></ul>


To this end, closed media query ranges are our best friend. If we need to make a change to any given view, we make it in the CSS media query range that applies to the specific breakpoint. We’ll be much less likely to introduce unwanted alterations, and our regression testing only needs to focus on the breakpoint we have actually edited. 


Taking the above example, if we find that <code>.my-block</code> spacing on desktop is already accounted for by the margin at that breakpoint, and since we want to remove the padding altogether, we could do this by setting the mobile <code>padding</code> in a closed media query range. 


<figure class="wp-block-table">
<pre><code class="language-css">.my-block {
  @media (max-width: 767.98px) {
    padding: 20px;
  }
  @media (min-width: 768px) and (max-width: 1023.98px) {
    padding: 40px;
  }
}</code></pre>
</figure>


The browser default <code>padding</code> for our block is “0,” so instead of adding a desktop media query and using <code>unset</code> or “0” for the <code>padding</code> value (which we would need with mobile-first), we can wrap the mobile <code>padding</code> in a closed media query (since it is now also an exception) so it won’t get picked up at wider breakpoints. At the desktop breakpoint, we won’t need to set any <code>padding</code> style, as we want the browser default value.


<h2>Bundling versus separating the CSS</h2>


Back in the day, keeping the number of requests to a minimum was very important due to the browser’s limit of concurrent requests (typically around six). As a consequence, the use of image sprites and CSS bundling was the norm, with all the CSS being downloaded in one go, as one stylesheet with highest priority. 


With HTTP/2 and HTTP/3 now on the scene, the number of requests is no longer the big deal it used to be. This allows us to separate the CSS into multiple files by media query. The clear benefit of this is the browser can now request the CSS it currently needs with a higher priority than the CSS it doesn’t. This is more performant and can reduce the overall time <a href="https://web.dev/critical-rendering-path-render-blocking-css/">page rendering is blocked</a>.


<h3>Which HTTP version are you using?</h3>


To determine which version of HTTP you’re using, go to your website and open your browser’s dev tools. Next, select the Network tab and make sure the Protocol column is visible. If “h2” is listed under Protocol, it means HTTP/2 is being used. 


Note: to view the Protocol in your browser’s dev tools, go to the Network tab, reload your page, right-click any column header (e.g., Name), and check the Protocol column.


<figure class="wp-block-image"><img src="https://lh4.googleusercontent.com/O8lxNeIY3Hb0YDs2EP7QFhGdGsBXOG7mSTCdAJBd5xkm-6RwrpkS1BN63W7RurVCP3nOH9sNpAR9JNGvIGnUTzG0NYm4sUqI5bU2QPhXYEawmKfeUJ_6YwWAIid2ZDHEdRzaQ1LxzUNTGbGk5g" alt="Chrome dev tools, Network tab filtered by document, Protocol column"/><figcaption>Note: for a summarized comparison, see ImageKit’s “<a href="https://imagekit.io/blog/http2-vs-http1-performance/">HTTP/2 vs. HTTP/1</a>.”</figcaption></figure>


Also, if your site is still using HTTP/1...WHY?!! What are you waiting for? There is <a href="https://caniuse.com/http2">excellent user support for HTTP/2</a>.


<h2>Splitting the CSS</h2>


Separating the CSS into individual files is a worthwhile task. Linking the separate CSS files using the relevant <code>media</code> attribute allows the browser to identify which files are needed immediately (because they’re render-blocking) and which can be deferred. Based on this, it allocates each file an appropriate priority.


In the following example of a website visited on a mobile breakpoint, we can see the mobile and default CSS are loaded with “Highest” priority, as they are currently needed to render the page. The remaining CSS files (print, tablet, and desktop) are still downloaded in case they’ll be needed later, but with “Lowest” priority. 


<figure class="wp-block-image"><img src="https://lh5.googleusercontent.com/RZOq-S7kbVsavDiFctQl6STFgGm6puwG8L22V6j6U1vUfo73Opq3Cspj2N94T2BU5lpYUD7Bb_4krFCXlePvBE8xXJVMFwbc_At8pzc-C5ug-6lrPViwMIIXgbKiJA-2fQ3beDoYfkCflCVgwg" alt="Chrome dev tools, Network tab filtered by css, Priority column"/></figure>


With bundled CSS, the browser will have to download the CSS file and parse it before rendering can start. While, as noted, with the CSS separated into different files linked and marked up with the relevant <code>media</code> attribute, the browser can prioritize the files it currently needs. Using closed media query ranges allows the browser to do this at all widths, as opposed to classic mobile-first <code>min-width</code> queries, where the desktop browser would have to download all the CSS with Highest priority. We can’t assume that desktop users always have a fast connection. For instance, in many rural areas, internet connection speeds are still slow.


The media queries and number of separate CSS files will vary from project to project based on project requirements, but might look similar to the example below.


<figure class="wp-block-table">
<table><tbody>
<tr>
<td valign="top">
Bundled CSS
<code><link href="site.css" rel="stylesheet"></code> 
This single file contains all the CSS, including all media queries, and it will be downloaded with Highest priority.
</td>
<td valign="top">
Separated CSS
<code><link href="default.css" rel="stylesheet"><link href="mobile.css" media="screen and (max-width: 767.98px)" rel="stylesheet"><link href="tablet.css" media="screen and (min-width: 768px) and (max-width: 1083.98px)" rel="stylesheet"><link href="desktop.css" media="screen and (min-width: 1084px)" rel="stylesheet"><link href="print.css" media="print" rel="stylesheet"></code> 
Separating the CSS and specifying a <code>media</code> attribute value on each <code>link</code> tag allows the browser to prioritize what it currently needs. Out of the five files listed above, two will be downloaded with Highest priority: the default file, and the file that matches the current media query. The others will be downloaded with Lowest priority.
</td>
</tr>
</tbody></table>
</figure>


Depending on the project’s deployment strategy, a change to one file (<code>mobile.css</code>, for example) would only require the QA team to regression test on devices in that specific media query range. Compare that to the prospect of deploying the single bundled <code>site.css</code> file, an approach that would normally trigger a full regression test.


<h2>Moving on</h2>


The uptake of mobile-first CSS was a really important milestone in web development; it has helped front-end developers focus on mobile web applications, rather than developing sites on desktop and then attempting to retrofit them to work on other devices.


I don’t think anyone wants to return to that development model again, but it’s important we don’t lose sight of the issue it highlighted: that things can easily get convoluted and less efficient if we prioritize one particular device—any device—over others. For this reason, focusing on the CSS in its own right, always mindful of what is the default setting and what’s an exception, seems like the natural next step. I’ve started noticing small simplifications in my own CSS, as well as other developers’, and that testing and maintenance work is also a bit more simplified and productive.


In general, simplifying CSS rule creation whenever we can is ultimately a cleaner approach than going around in circles of overrides. But whichever methodology you choose, it needs to suit the project. Mobile-first may—or may not—turn out to be the best choice for what’s involved, but first you need to solidly understand the trade-offs you’re stepping into.
]]> </description>
<dc:subject>
<![CDATA[Code, CSS]]> </dc:subject>
<dc:date>
2022-06-09T02:13:10+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Designers, (Re)define Success First]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/lennartoverkamp/">Lennart Overkamp</a> </author>
<link>
https://alistapart.com/article/redefine-success-first/ </link>
<guid>
https://alistapart.com/article/redefine-success-first/ </guid>
<description>
<![CDATA[
About two and a half years ago, I introduced the idea of <a href="https://alistapart.com/article/daily-ethical-design/">daily ethical design</a>. It was born out of my frustration with the many obstacles to achieving design that’s usable and equitable; protects people’s privacy, agency, and focus; benefits society; and restores nature. I argued that we need to overcome the inconveniences that prevent us from acting ethically and that we need to elevate design ethics to a more practical level by structurally integrating it into our daily work, processes, and tools.


Unfortunately, we’re still very far from this ideal. 


At the time, I didn’t know yet how to structurally integrate ethics. Yes, I had found some tools that had worked for me in previous projects, such as using checklists, assumption tracking, and “dark reality” sessions, but I didn’t manage to apply those in every project. I was still struggling for time and support, and at best I had only partially achieved a higher (moral) quality of design—which is far from my definition of structurally integrated.


I decided to dig deeper for the root causes in business that prevent us from practicing daily ethical design. Now, after much research and experimentation, I believe that I’ve found the key that will let us structurally integrate ethics. And it’s surprisingly simple! But first we need to zoom out to get a better understanding of what we’re up against.


<h2>Influence the system</h2>


Sadly, we’re trapped in a capitalistic system that reinforces <a href="https://www.nature.com/articles/s41467-020-16941-y">consumerism</a> and <a href="https://www.aljazeera.com/economy/2022/1/11/brace-yourself-for-an-even-more-unequal-post-pandemic-world-wef">inequality</a>, and it’s obsessed with the <a href="https://www.goodreads.com/book/show/53328332-less-is-more">fantasy of endless growth</a>. Sea levels, temperatures, and our demand for energy continue to rise unchallenged, while the gap between rich and poor continues to widen. Shareholders expect ever-higher returns on their investments, and companies feel forced to set short-term objectives that reflect this. Over the last decades, those objectives have <a href="https://creativegood.com/blog/21/losing-faith-in-ux.html">twisted our well-intended human-centered mindset into a powerful machine</a> that promotes ever-higher levels of consumption. When we’re working for an organization that pursues “double-digit growth” or “aggressive sales targets” (which is 99 percent of us), that’s very hard to resist while remaining human friendly. Even with our best intentions, and even though we like to say that we create solutions for people, we’re a part of the problem.


What can we do to change this?


We can start by acting on the right level of the system. Donella H. Meadows, a system thinker, once listed <a href="https://www.goodreads.com/book/show/3828902-thinking-in-systems">ways to influence a system</a> in order of effectiveness. When you apply these to design, you get:


<ul><li>At the lowest level of effectiveness, you can affect numbers such as usability scores or the number of design critiques. But none of that will change the direction of a company.</li><li>Similarly, affecting buffers (such as team budgets), stocks (such as the number of designers), flows (such as the number of new hires), and delays (such as the time that it takes to hear about the effect of design) won’t significantly affect a company.</li><li>Focusing instead on feedback loops such as management control, employee recognition, or design-system investments can help a company become better at achieving its objectives. But that doesn’t change the objectives themselves, which means that the organization will still work against your ethical-design ideals.</li><li>The next level, information flows, is what most ethical-design initiatives focus on now: the exchange of ethical methods, toolkits, articles, conferences, workshops, and so on. This is also where ethical design has remained mostly theoretical. We’ve been focusing on the wrong level of the system all this time.</li><li>Take rules, for example—they beat knowledge every time. There can be widely accepted rules, such as how finance works, or a scrum team’s definition of done. But ethical design can also be smothered by unofficial rules meant to maintain profits, often revealed through comments such as “the client didn’t ask for it” or “don’t make it too big.”</li><li>Changing the rules without holding official power is very hard. That’s why the next level is so influential: self-organization. Experimentation, bottom-up initiatives, passion projects, self-steering teams—all of these are examples of self-organization that improve the resilience and creativity of a company. It’s exactly this diversity of viewpoints that’s needed to structurally tackle big systemic issues like consumerism, wealth inequality, and climate change.</li><li>Yet even stronger than self-organization are objectives and metrics. Our companies want to make more money, which means that everything and everyone in the company does their best to… make the company more money. And once I realized that profit is nothing more than a measurement, I understood how crucial a very specific, defined metric can be toward pushing a company in a certain direction.</li></ul>


The takeaway? If we truly want to incorporate ethics into our daily design practice, we must first change the measurable objectives of the company we work for, from the bottom up.


<h2>Redefine success</h2>


Traditionally, <a href="https://designthinking.ideo.com/">we consider a product or service successful if it’s desirable to humans, technologically feasible, and financially viable</a>. You tend to see these represented as equals; if you type the three words in a search engine, you’ll find diagrams of three equally sized, evenly arranged circles.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/05/image01-1024x576.png" alt="A Venn diagram with three overlapping circles representing Viable, Desirable, and Feasible with the target directly in the central intersection of all three." class="wp-image-7173407" /></figure>


But in our hearts, we all know that the three dimensions aren’t equally weighted: it’s viability that ultimately controls whether a product will go live. So a more realistic representation might look like this:


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/05/image02-1024x576.png" alt="A Venn diagram with two circles (Desirable and Feasible) overlapping. An arrow points from their intersection to a separate circle marked as Viable, with a target inside it." class="wp-image-7173408" /></figure>


Desirability and feasibility are the means; viability is the goal. Companies—outside of nonprofits and charities—exist to make money.


A genuinely purpose-driven company would try to reverse this dynamic: it would recognize finance for what it was intended for: a means. So both feasibility and viability are means to achieve what the company set out to achieve. It makes intuitive sense: to achieve most anything, you need resources, people, and money. (Fun fact: the Italian language knows no difference between feasibility and viability; both are simply fattibilità.)


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/05/image03-1024x576.png" alt="A Venn diagram with two circles (Viable and Feasible) overlapping. An arrow points from their intersection to a separate circle marked as Desirable, with a target inside it." class="wp-image-7173409" /></figure>


But simply swapping viable for desirable isn’t enough to achieve an ethical outcome. Desirability is still linked to consumerism because the associated activities aim to identify what people want—whether it’s good for them or not. Desirability objectives, such as user satisfaction or conversion, don’t consider whether a product is healthy for people. They don’t prevent us from creating products that distract or manipulate people or stop us from contributing to society’s wealth inequality. They’re unsuitable for establishing a healthy balance with nature.


There’s a fourth dimension of success that’s missing: our designs also need to be ethical in the effect that they have on the world.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/05/image04-1024x576.png" alt="The original Venn diagram of three circles (Desirable, Viable, and Feasible) overlapping with the target in their central intersection. This time, a fourth circle named Ethical encompasses all three." class="wp-image-7173410" /></figure>


This is hardly a new idea. Many similar models exist, some calling the fourth dimension accountability, integrity, or responsibility. What I’ve never seen before, however, is the necessary step that comes after: to influence the system as designers and to make ethical design more practical, we must create objectives for ethical design that are achievable and inspirational. There’s no one way to do this because it highly depends on your culture, values, and industry. But I’ll give you the version that I developed with a group of colleagues at a design agency. Consider it a template to get started.


<h2>Pursue well-being, equity, and sustainability</h2>


We created objectives that address design’s effect on three levels: individual, societal, and global.


An objective on the individual level tells us what success is beyond the typical focus of usability and satisfaction—instead considering matters such as how much time and attention is required from users. We pursued well-being:


<blockquote class="wp-block-quote">We create products and services that allow for people’s health and happiness. Our solutions are calm, transparent, nonaddictive, and nonmisleading. We respect our users’ time, attention, and privacy, and help them make healthy and respectful choices.</blockquote>


An objective on the societal level forces us to consider our impact beyond just the user, widening our attention to the economy, communities, and other indirect stakeholders. We called this objective equity:


<blockquote class="wp-block-quote">We create products and services that have a positive social impact. We consider economic equality, racial justice, and the inclusivity and diversity of people as teams, users, and customer segments. We listen to local culture, communities, and those we affect.</blockquote>


Finally, the objective on the global level aims to ensure that we remain in balance with the only home we have as humanity. Referring to it simply as sustainability, our definition was:


<blockquote class="wp-block-quote">We create products and services that reward sufficiency and reusability. Our solutions support the circular economy: we create value from waste, repurpose products, and prioritize sustainable choices. We deliver functionality instead of ownership, and we limit energy use.</blockquote>


In short, ethical design (to us) meant achieving wellbeing for each user and an equitable value distribution within society through a design that can be sustained by our living planet. When we introduced these objectives in the company, for many colleagues, design ethics and responsible design suddenly became tangible and achievable through practical—and even familiar—actions.


<h2>Measure impact </h2>


But defining these objectives still isn’t enough. What truly caught the attention of senior management was the fact that we created a way to measure every design project’s well-being, equity, and sustainability.


This overview lists example metrics that you can use as you pursue well-being, equity, and sustainability:


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/05/image05-1024x576.png" alt="A list of example metrics for ethical impact at individual, societal, and planetary levels. Individual well-being examples include increased calmness, lower screen time, improved safety and privacy. Societal equity examples include improved accessibility, increased team and stakeholder diversity, and increased progressive enhancement. Finally, planetary sustainability examples include reduced energy use, reduced website carbon emissions and device turnover, and increased expert involvement." class="wp-image-7173411" /></figure>


There’s a lot of power in measurement. As the saying goes, what gets measured gets done. <a href="https://www.goodreads.com/book/show/3828902-thinking-in-systems">Donella Meadows</a> once shared this example:


<blockquote class="wp-block-quote">“If the desired system state is national security, and that is defined as the amount of money spent on the military, the system will produce military spending. It may or may not produce national security.”</blockquote>


This phenomenon explains why desirability is a poor indicator of success: it’s typically <a href="https://www.interaction-design.org/literature/article/google-s-heart-framework-for-measuring-ux">defined as the increase in customer satisfaction, session length, frequency of use, conversion rate, churn rate, download rate</a>, and so on. But none of these metrics increase the health of people, communities, or ecosystems. What if instead we measured success through metrics for (digital) well-being, such as (reduced) <a href="https://en.wikipedia.org/wiki/Screen_time#Physical_health_effects">screen time</a> or software energy consumption?


There’s another important message here. Even if we set an objective to build a calm interface, if we were to choose the wrong metric for calmness—say, the number of interface elements—we could still end up with a screen that induces anxiety. Choosing the wrong metric can completely undo good intentions. 


Additionally, choosing the right metric is enormously helpful in focusing the design team. Once you go through the exercise of <a href="https://www.franklincovey.com/the-4-disciplines-old/discipline-2-act/">choosing metrics for our objectives</a>, you’re forced to consider what success looks like concretely and how you can prove that you’ve reached your ethical objectives. It also forces you to consider what we as designers have control over: what can I include in my design or change in my process that will lead to the right type of success? The answer to this question brings a lot of clarity and focus.


And finally, it’s good to remember that traditional businesses run on measurements, and managers love to spend much time discussing charts (ideally hockey-stick shaped)—especially if they concern profit, the one-above-all of metrics. For good or ill, to improve the system, to have a serious discussion about ethical design with managers, we’ll need to speak that business language.


<h2>Practice daily ethical design</h2>


Once you’ve defined your objectives and you have a reasonable idea of the potential metrics for your design project, only then do you have a chance to structurally practice ethical design. It “simply” becomes a matter of using your creativity and choosing from all the knowledge and toolkits already available to you.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/05/image06-1024x576.png" alt="A set of example methods and tools for practicing at the individual, societal, and planetary level. Individual tools include the principle of minimum necessary data, white-hat persuasion techniques, calm-technology guidelines, and more. Societal tools include stakeholder mapping, inclusive sampling and testing, progressive enhancement, accessibility principles, and more. Planetary tools include the flourishing business canvas, extended-service blueprint, website carbon calculators, product-lifecycle mapping, and more." class="wp-image-7173412" /></figure>


I think this is quite exciting! It opens a whole new set of challenges and considerations for the design process. Should you go with that energy-consuming video or would a simple illustration be enough? Which typeface is the most calm and inclusive? Which new tools and methods do you use? When is the website’s end of life? How can you provide the same service while requiring less attention from users? How do you make sure that those who are affected by decisions are there when those decisions are made? How can you measure our effects?


The redefinition of success will completely change what it means to do good design.


There is, however, a final piece of the puzzle that’s missing: convincing your client, product owner, or manager to be mindful of well-being, equity, and sustainability. For this, it’s essential to engage stakeholders in a dedicated kickoff session.


<h2>Kick it off or fall back to status quo</h2>


The kickoff is the most important meeting that can be so easy to forget to include. It consists of two major phases: 1) the alignment of expectations, and 2) the definition of success.


In the first phase, the entire (design) team goes over the project brief and meets with all the relevant stakeholders. Everyone gets to know one another and express their expectations on the outcome and their contributions to achieving it. Assumptions are raised and discussed. The aim is to get on the same level of understanding and to in turn avoid preventable miscommunications and surprises later in the project.


For example, for a recent freelance project that aimed to design a digital platform that facilitates US student advisors’ documentation and communication, we conducted an online kickoff with the client, a subject-matter expert, and two other designers. We used a combination of canvases on Miro: one with questions from “<a href="https://www.manualof.me/">Manual of Me</a>” (to get to know each other), a <a href="https://www.theteamcanvas.com/">Team Canvas</a> (to express expectations), and a version of the <a href="http://www.projectcanvas.dk/">Project Canvas</a> to align on scope, timeline, and other practical matters.


The above is the traditional purpose of a kickoff. But just as important as expressing expectations is agreeing on what success means for the project—in terms of desirability, viability, feasibility, and ethics. What are the objectives in each dimension?


Agreement on what success means at such an early stage is crucial because you can rely on it for the remainder of the project. If, for example, the design team wants to build an inclusive app for a diverse user group, they can raise diversity as a specific success criterion during the kickoff. If the client agrees, the team can refer back to that promise throughout the project. “As we agreed in our first meeting, having a diverse user group that includes A and B is necessary to build a successful product. So we do activity X and follow research process Y.” Compare those odds to a situation in which the team didn’t agree to that beforehand and had to ask for permission halfway through the project. The client might argue that that came on top of the agreed scope—and she’d be right.


In the case of this freelance project, to define success I prepared a round canvas that I call the Wheel of Success. It consists of an inner ring, meant to capture ideas for objectives, and a set of outer rings, meant to capture ideas on how to measure those objectives. The rings are divided into five dimensions of successful design: healthy, equitable, sustainable, desirable, feasible, and viable.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/05/image07-956x1024.jpg" alt="The wheel of success. The central circle reads 'The product is a success when it is'. The next ring outside lists example values such as healthy, equitable, sustainable, viable, feasible, and desirable. The next ring out lists out measurable objectives for those values, and the outermost ring lists tools that can measure those objectives." class="wp-image-7173413" /></figure>


We went through each dimension, writing down ideas on digital sticky notes. Then we discussed our ideas and verbally agreed on the most important ones. For example, our client agreed that sustainability and progressive enhancement are important success criteria for the platform. And the subject-matter expert emphasized the importance of including students from low-income and disadvantaged groups in the design process.


After the kickoff, we summarized our ideas and shared understanding in a project brief that captured these aspects:


<ul><li>the project’s origin and purpose: why are we doing this project?</li><li>the problem definition: what do we want to solve?</li><li>the concrete goals and metrics for each success dimension: what do we want to achieve?</li><li>the scope, process, and role descriptions: how will we achieve it?</li></ul>


With such a brief in place, you can use the agreed-upon objectives and concrete metrics as a checklist of success, and your design team will be ready to pursue the right objective—using the tools, methods, and metrics at their disposal to achieve ethical outcomes.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2022/05/image08-1024x576.png" alt="A drawing of a set of mountains that also looks vaguely like a graph. The leftmost valley has 'Pursue the right objective' pointing at it. The middle valley has 'Solve the right problem' and the rightmost valley is labelled 'Build the right solution.' Below the mountains, a timeline shows from left to right: Kick-off, Problem space, Solution space, and Development." class="wp-image-7173414" /></figure>


<h2>Conclusion</h2>


Over the past year, quite a few colleagues have asked me, “Where do I start with ethical design?” My answer has always been the same: organize a session with your stakeholders to (re)define success. Even though you might not always be 100 percent successful in agreeing on goals that cover all responsibility objectives, that beats the alternative (the status quo) every time. If you want to be an ethical, responsible designer, there’s no skipping this step.


To be even more specific: if you consider yourself a strategic designer, your challenge is to define ethical objectives, set the right metrics, and conduct those kick-off sessions. If you consider yourself a system designer, your starting point is to understand how your industry contributes to consumerism and inequality, understand how finance drives business, and brainstorm which levers are available to influence the system on the highest level. Then redefine success to create the space to exercise those levers.


And for those who consider themselves service designers or UX designers or UI designers: if you truly want to have a positive, meaningful impact, stay away from the toolkits and meetups and conferences for a while. Instead, gather your colleagues and define goals for well-being, equity, and sustainability through design. Engage your stakeholders in a workshop and challenge them to think of ways to achieve and measure those ethical goals. Take their input, make it concrete and visible, ask for their agreement, and hold them to it.


Otherwise, I’m genuinely sorry to say, you’re wasting your precious time and creative energy.


Of course, engaging your stakeholders in this way can be uncomfortable. Many of my colleagues expressed doubts such as “What will the client think of this?,” “Will they take me seriously?,” and “Can’t we just do it within the design team instead?” In fact, a product manager once asked me why ethics couldn’t just be a structured part of the design process—to just do it without spending the effort to define ethical objectives. It’s a tempting idea, right? We wouldn’t have to have difficult discussions with stakeholders about what values or which key-performance indicators to pursue. It would let us focus on what we like and do best: designing.


But as systems theory tells us, that’s not enough. For those of us who aren’t from marginalized groups and have the privilege to be able to speak up and be heard, that uncomfortable space is exactly where we need to be if we truly want to make a difference. We can’t remain within the design-for-designers bubble, enjoying our privileged working-from-home situation, disconnected from the real world out there. For those of us who have the possibility to speak up and be heard: if we solely keep talking about ethical design and it remains at the level of articles and toolkits—we’re not designing ethically. It’s just theory. We need to actively engage our colleagues and clients by challenging them to redefine success in business.


With a bit of courage, determination, and focus, we can break out of this cage that finance and business-as-usual have built around us and become facilitators of a new type of business that can see beyond financial value. We just need to agree on the right objectives at the start of each design project, find the right metrics, and realize that we already have everything that we need to get started. That’s what it means to do daily ethical design.


For their inspiration and support over the years, I would like to thank Emanuela Cozzi Schettini, José Gallegos, Annegret Bönemann, Ian Dorr, Vera Rademaker, Virginia Rispoli, Cecilia Scolaro, Rouzbeh Amini, and many others.
]]> </description>
<dc:subject>
<![CDATA[Industry, User Experience, Workflow & Tools]]> </dc:subject>
<dc:date>
2022-05-12T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Breaking Out of the Box]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/patrick-brosset/">Patrick Brosset</a> </author>
<link>
https://alistapart.com/article/breaking-out-of-the-box/ </link>
<guid>
https://alistapart.com/article/breaking-out-of-the-box/ </guid>
<description>
<![CDATA[
CSS is about styling boxes. In fact, the whole web is made of boxes, from the browser viewport to elements on a page. But every once in a while a new feature comes along that makes us rethink our design approach.


<a href="https://www.w3.org/TR/css-round-display-1/">Round displays</a>, for example, make it fun to play with circular clip areas. <a href="https://css-tricks.com/the-notch-and-css/">Mobile screen notches</a> and <a href="https://www.w3.org/TR/virtual-keyboard/">virtual keyboards</a> offer challenges to best organize content that stays clear of them. And <a href="https://blogs.windows.com/msedgedev/2020/09/14/introducing-dual-screen-foldable-web-apis/">dual screen or foldable devices</a> make us rethink how to best use available space in a number of different <a href="https://w3c.github.io/device-posture/">device postures</a>.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/12/fig1-1024x482.png" alt="" class="wp-image-7173226"/><figcaption>Sketches of a round display, a common rectangular mobile display, and a device with a foldable display.</figcaption></figure>


These recent evolutions of the web platform made it both more challenging and more interesting to design products. They’re great opportunities for us to break out of our rectangular boxes.


I’d like to talk about a new feature similar to the above: the Window Controls Overlay for Progressive Web Apps (PWAs).


<a href="https://alistapart.com/article/yes-that-web-project-should-be-a-pwa/">Progressive Web Apps</a> are blurring the lines between apps and websites. They combine the best of both worlds. On one hand, they’re stable, linkable, searchable, and responsive just like websites. On the other hand, they provide additional powerful capabilities, work offline, and read files just like native apps.


As a design surface, PWAs are really interesting because they challenge us to think about what mixing web and device-native user interfaces can be. On desktop devices in particular, we have more than <a href="https://en.wikipedia.org/wiki/History_of_the_graphical_user_interface">40 years of history</a> telling us what applications should look like, and it can be hard to break out of this mental model.


At the end of the day though, PWAs on desktop are constrained to the window they appear in: a rectangle with a title bar at the top.


Here’s what a typical desktop PWA app looks like:


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/12/fig2-1024x323.png" alt="" class="wp-image-7173227"/><figcaption>Sketches of two rectangular user interfaces representing the desktop Progressive Web App status quo on the macOS and Windows operating systems, respectively. </figcaption></figure>


Sure, as the author of a PWA, you get to choose the color of the title bar (using the Web Application Manifest <a href="https://developer.mozilla.org/en-US/docs/Web/Manifest/theme_color">theme_color</a> property), but that’s about it.


What if we could think outside this box, and reclaim the real estate of the app’s entire window? Doing so would give us a chance to make our apps more beautiful and feel more integrated in the operating system.


This is exactly what the <a href="https://web.dev/window-controls-overlay/">Window Controls Overlay</a> offers. This new PWA functionality makes it possible to take advantage of the full surface area of the app, including where the title bar normally appears.


<h2>About the title bar and window controls</h2>


Let’s start with an explanation of what the title bar and window controls are.


The title bar is the area displayed at the top of an app window, which usually contains the app’s name. Window controls are the affordances, or buttons, that make it possible to minimize, maximize, or close the app’s window, and are also displayed at the top.


<figure class="wp-block-image"><img src="https://lh5.googleusercontent.com/1s_lFmqiRm6Fv3wzeELtsDDiDvOkEJuSRH5K9YIrZZ8rh8rYCxUqbSnfd-f7YrsRvcDzF67fexnEJFlDtw53SKKmOgVk8sv_VUyCQveoR18HkNgACPxcQTtEOb6SmEuRIDlX3EcI" alt=""/><figcaption>A sketch of a rectangular application user interface highlighting the title bar area and window control buttons.</figcaption></figure>


Window Controls Overlay removes the physical constraint of the title bar and window controls areas. It frees up the full height of the app window, enabling the title bar and window control buttons to be overlaid on top of the application’s web content. 


<figure class="wp-block-image"><img src="https://lh6.googleusercontent.com/k_6o1fBePhbjvtmxoTW3tG1134Gvbo31r2fy7zxmOB39d_eKpjThbh7QL8pVXrA1aLvEWzkoJ_rY4af451BU9XyKZXbSouCTvDJMnRKGlcOhcEpXw_rjQAR8_SFjhrm_-22OxKiR" alt=""/><figcaption>A sketch of a rectangular application user interface using Window Controls Overlay. The title bar and window controls are no longer in an area separated from the app’s content.</figcaption></figure>


If you are reading this article on a desktop computer, take a quick look at other apps. Chances are they’re already doing something similar to this. In fact, the very web browser you are using to read this uses the top area to display tabs.


<figure class="wp-block-image"><img src="https://lh6.googleusercontent.com/BLL9Rc5othPsw6xYApyyNOZ73j32wi4XkyoZpl4QOv0OL4MnxMe3bl1xLR0O7WSoAvi3KhyeP83hUh4-EezTmGg2axN4RiOVtgiF5ZiapcjUL6gtLqExZOHGCtkOBbthMTgh5Tmr" alt=""/><figcaption>A screenshot of the top area of a browser’s user interface showing a group of tabs that share the same horizontal space as the app window controls.</figcaption></figure>


Spotify displays album artwork all the way to the top edge of the application window.


<figure class="wp-block-image"><img src="https://lh3.googleusercontent.com/SzPcq94_7Yu_ARf13Z6dRD0tpdlPM_MdrY-7CA_mv4Yu3fBIL3pJnXirP83cCDVoQxnnIEwDoBwbGzfftHmZ3PZZUfsw_oP-m4QLkB2SqekX8JupR9_xmI0tG1q65IfNFbnXIHUh" alt=""/><figcaption>A screenshot of an album in Spotify’s desktop application. Album artwork spans the entire width of the main content area, all the way to the top and right edges of the window, and the right edge of the main navigation area on the left side. The application and album navigation controls are overlaid directly on top of the album artwork.</figcaption></figure>


Microsoft Word uses the available title bar space to display the auto-save and search functionalities, and more.


<figure class="wp-block-image"><img src="https://lh6.googleusercontent.com/VdREVwFFjYHxHF0Gg3l079hxsa8WKPEWiuvuL7cWbGnEDJ2yc3JiOWQK5lUyaeEgzpd1Przji0cNLeooPD7riPKbcMixa6IkXanprdqPJVkQrYSerxSaNmzbJPd1YsA55mlYd9xt" alt=""/><figcaption>A screenshot of Microsoft Word’s toolbar interface. Document file information, search, and other functionality appear at the top of the window, sharing the same horizontal space as the app’s window controls.</figcaption></figure>


The whole point of this feature is to allow you to make use of this space with your own content while providing a way to account for the window control buttons. And it enables you to offer this modified experience on a range of platforms while not adversely affecting the experience on browsers or devices that don’t support Window Controls Overlay. After all, PWAs are all about <a href="https://alistapart.com/article/understandingprogressiveenhancement/">progressive enhancement</a>, so this feature is a chance to enhance your app to use this extra space when it’s available.


<h2>Let’s use the feature</h2>


For the rest of this article, we’ll be working on a demo app to learn more about using the feature.


The demo app is called <a href="https://stupefied-edison-a4ee55.netlify.app/">1DIV</a>. It’s a simple CSS playground where users can create designs using CSS and a single HTML element.


The app has two pages. The first lists the existing CSS designs you’ve created:


<figure class="wp-block-image"><img src="https://lh3.googleusercontent.com/pW2iUTucKfwMJZrAlPGK19vVnEPaHjYT4N-18P-vm9qkhAdGJcRBMexOCu1q9nN9BAfZ7MH6itNP__kY4HPl9uVPucXkbmSX-E9g6AdVAI_uu6TyEsEdH0LUCXdN1f4kqZNgDr30" alt=""/><figcaption>A screenshot of the 1DIV app displaying a thumbnail grid of CSS designs a user created.</figcaption></figure>


The second page enables you to create and edit CSS designs:


<figure class="wp-block-image"><img src="https://lh5.googleusercontent.com/faaJ3uHbzXg-TFinvOqR_7gyjVPvlk7fuVWuN4aIH6IUxXNAp4GXtIcuVPpo6bd1IOKO1_EMDt4pUgErUh_X2_2r3WnkQ4PzovPp6Zjg0l98W9NBrHA0xAuTNf0uNVBatRsMJzEm" alt=""/><figcaption>A screenshot of the 1DIV app editor page. The top half of the window displays a rendered CSS design, and a text editor on the bottom half of the window displays the CSS used to create it.</figcaption></figure>


Since I’ve added a simple web manifest and service worker, we can install the app as a PWA on desktop. Here is what it looks like on macOS:


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/12/fig10-1024x497.png" alt="" class="wp-image-7173228"/><figcaption>Screenshots of the 1DIV app thumbnail view and CSS editor view on macOS. This version of the app’s window has a separate control bar at the top for the app name and window control buttons.</figcaption></figure>


And on Windows:


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/12/fig11-1024x534.png" alt="" class="wp-image-7173229"/><figcaption>Screenshots of the 1DIV app thumbnail view and CSS editor view on the Windows operating system. This version of the app’s window also has a separate control bar at the top for the app name and window control buttons.</figcaption></figure>


Our app is looking good, but the white title bar in the first page is wasted space. In the second page, it would be really nice if the design area went all the way to the top of the app window.


Let’s use the Window Controls Overlay feature to improve this.


<h2>Enabling Window Controls Overlay</h2>


The feature is still experimental at the moment. To try it, you need to enable it in one of the supported browsers.


As of now, it has been implemented in Chromium, as a collaboration between Microsoft and Google. We can therefore use it in Chrome or Edge by going to the internal about://flags page, and enabling the Desktop PWA Window Controls Overlay flag.


<h2>Using Window Controls Overlay</h2>


To use the feature, we need to add the following display_override member to our web app’s manifest file:


<pre><code class="language-javascript">{
"name": "1DIV",
"description": "1DIV is a mini CSS playground",
"lang": "en-US",
"start_url": "/",
"theme_color": "#ffffff",
"background_color": "#ffffff",
"display_override": [
"window-controls-overlay"
],
"icons": [
...
]
}
</code></pre>


On the surface, the feature is really simple to use. This manifest change is the only thing we need to make the title bar disappear and turn the window controls into an overlay.


However, to provide a great experience for all users regardless of what device or browser they use, and to make the most of the title bar area in our design, we’ll need a bit of CSS and JavaScript code.


Here is what the app looks like now:


<figure class="wp-block-image"><img src="https://lh6.googleusercontent.com/YbSJ4vMtrc88Jr8sh7F8uWED-9OVFvLkXNT3xVP9gdmQt9XwC-wGHPmaspcKnfSpPMjSotYzRISGPag1Ugq3mxWTslaVhPK9iP8IHLjFnE_FcIkM0y3olJ4Gzw5ejrZFTRbz9avF" alt=""/><figcaption>Screenshot of the 1DIV app thumbnail view using Window Controls Overlay on macOS. The separate top bar area is gone, but the window controls are now blocking some of the app’s interface</figcaption></figure>


The title bar is gone, which is what we wanted, but our logo, search field, and NEW button are partially covered by the window controls because now our layout starts at the top of the window.


It’s similar on Windows, with the difference that the close, maximize, and minimize buttons appear on the right side, grouped together with the PWA control buttons:


<figure class="wp-block-image"><img src="https://lh6.googleusercontent.com/ytqSauTsKKNI6N7YzxlIqhNatK7LwaPw6yY74jq2egOsBIHbzl2vFGPMRK6dqx6tE-UqSCCWS8f1YftsXZygxEB6KALUYfGU9XW4poE1NPpjYKV66bk1k6dy91rh6TMZ1qb3Rph-" alt=""/><figcaption>Screenshot of the 1DIV app thumbnail display using Window Controls Overlay on the Windows operating system. The separate top bar area is gone, but the window controls are now blocking some of the app’s content.</figcaption></figure>


<h2>Using CSS to keep clear of the window controls</h2>


Along with the feature, new CSS environment variables have been introduced:


<ul><li><code>titlebar-area-x</code></li><li><code>titlebar-area-y</code></li><li><code>titlebar-area-width</code></li><li><code>titlebar-area-height</code></li></ul>


You use these variables with the CSS <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/env()">env()</a> function to position your content where the title bar would have been while ensuring it won’t overlap with the window controls. In our case, we’ll use two of the variables to position our header, which contains the logo, search bar, and NEW button. 


<pre><code class="language-css">header {
position: absolute;
left: env(titlebar-area-x, 0);
width: env(titlebar-area-width, 100%);
height: var(--toolbar-height);
}
</code></pre>


The <code>titlebar-area-x </code>variable gives us the distance from the left of the viewport to where the title bar would appear, and <code>titlebar-area-width</code> is its width. (Remember, this is not equivalent to the width of the entire viewport, just the title bar portion, which as noted earlier, doesn’t include the window controls.)


By doing this, we make sure our content remains fully visible. We’re also defining fallback values (the second parameter in the <code>env()</code> function) for when the variables are not defined (such as on non-supporting browsers, or when the Windows Control Overlay feature is disabled).


<figure class="wp-block-image"><img src="https://lh5.googleusercontent.com/AYZ7D2ZqvPLip8FtF6IzI6XSAEoajjviCG5fo40_ynrksUesFQBjZVEN6dsTOA8F9CCqXbFWb32ZYUN73hEAkMlyzKnX_1Qzjy7kR6jl42TyyJOeg1FWK7A9WeWn-_7SD57-EOdt" alt=""/><figcaption>Screenshot of the 1DIV app thumbnail view on macOS with Window Controls Overlay and our CSS updated. The app content that the window controls had been blocking has been repositioned.</figcaption></figure>


<figure class="wp-block-image"><img src="https://lh6.googleusercontent.com/ZxtH5F4v2io8ntHHi8V0YhqgBc_GD5pcq4g52zZy4_bEhbtjC3G7WdyZqQmwc6-D_NIp7Z8dvjsG8qz42DIg7RDhC6HbPHThXEFsknbOgcEfkF7d_cqx45T9vTi6z23pVe0-1nxA" alt=""/><figcaption>Screenshot of the 1DIV app thumbnail view on the Windows operating system with Window Controls Overlay and our updated CSS. The app content that the window controls had been blocking has been repositioned.</figcaption></figure>


Now our header adapts to its surroundings, and it doesn’t feel like the window control buttons have been added as an afterthought. The app looks a lot more like a native app.


<h2>Changing the window controls background color so it blends in</h2>


Now let’s take a closer look at our second page: the CSS playground editor.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/12/fig16-1024x518.png" alt="" class="wp-image-7173230"/><figcaption>Screenshots of the 1DIV app CSS editor view with Window Controls Overlay in macOS and Windows, respectively. The window controls overlay areas have a solid white background color, which contrasts with the hot pink color of the example CSS design displayed in the editor.</figcaption></figure>


Not great. Our CSS demo area does go all the way to the top, which is what we wanted, but the way the window controls appear as white rectangles on top of it is quite jarring.


We can fix this by changing the app’s theme color. There are a couple of ways to define it:


<ul><li>PWAs can define a theme color in the web app manifest file using the <a href="https://developer.mozilla.org/en-US/docs/Web/Manifest/theme_color">theme_color</a> manifest member. This color is then used by the OS in different ways. On desktop platforms, it is used to provide a background color to the title bar and window controls.</li><li>Websites can use the <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta/name/theme-color">theme-color meta tag</a> as well. It’s used by browsers to customize the color of the UI around the web page. For PWAs, this color can override the manifest <code>theme_color</code>.</li></ul>


In our case, we can set the manifest <code>theme_color</code> to white to provide the right default color for our app. The OS will read this color value when the app is installed and use it to make the window controls background color white. This color works great for our main page with the list of demos.


The <code>theme-color</code> meta tag can be changed at runtime, using JavaScript. So we can do that to override the white with the right demo background color when one is opened.


Here is the function we’ll use:


<pre><code class="language-javascript">function themeWindow(bgColor) {
document.querySelector("meta[name=theme-color]").setAttribute('content', bgColor);
}</code></pre>


With this in place, we can imagine how using color and CSS transitions can produce a smooth change from the list page to the demo page, and enable the window control buttons to blend in with the rest of the app’s interface.


<figure class="wp-block-image"><img src="https://lh4.googleusercontent.com/YVYktaP8CkIQJFlCtWlwVU4dequS4MutbDJfm-vS8kGx_nedIgzziuHeZICeJ-vsu33VR0rydqwKH0JVIFKjWjlrvbWPYssNvxr7rBsCKKdag7PHMhA_NLV3w0nzBuBzurk1fr1i" alt=""/><figcaption>Screenshot of the 1DIV app CSS editor view on the Windows operating system with Window Controls Overlay and updated CSS demonstrating how the window control buttons blend in with the rest of the app’s interface.</figcaption></figure>


<h2>Dragging the window</h2>


Now, getting rid of the title bar entirely does have an important accessibility consequence: it’s much more difficult to move the application window around.


The title bar provides a sizable area for users to click and drag, but by using the Window Controls Overlay feature, this area becomes limited to where the control buttons are, and users have to very precisely aim between these buttons to move the window.


Fortunately, this can be fixed using CSS with the <code>app-region</code> property. This property is, for now, only supported in Chromium-based browsers and needs the <code>-webkit-</code> vendor prefix. 


To make any element of the app become a dragging target for the window, we can use the following: 


<code>-webkit-app-region: drag;</code>


It is also possible to explicitly make an element non-draggable: 


<code>-webkit-app-region: no-drag; </code>


These options can be useful for us. We can make the entire header a dragging target, but make the search field and NEW button within it non-draggable so they can still be used as normal.


However, because the editor page doesn’t display the header, users wouldn’t be able to drag the window while editing code. So let's use a different approach. We’ll create another element before our header, also absolutely positioned, and dedicated to dragging the window.


<pre><code class="language-markup"><div class="drag"></div>
<header>...</header></code></pre>


<pre><code class="language-css">.drag {
position: absolute;
top: 0;
width: 100%;
height: env(titlebar-area-height, 0);
-webkit-app-region: drag;
}</code></pre>


With the above code, we’re making the draggable area span the entire viewport width, and using the <code>titlebar-area-height</code> variable to make it as tall as what the title bar would have been. This way, our draggable area is aligned with the window control buttons as shown below.


And, now, to make sure our search field and button remain usable:


<pre><code class="language-css">header .search,
header .new {
-webkit-app-region: no-drag;
}</code></pre>


With the above code, users can click and drag where the title bar used to be. It is an area that users expect to be able to use to move windows on desktop, and we’re not breaking this expectation, which is good.


<figure class="wp-block-image"><img src="https://lh5.googleusercontent.com/sU0QjlT2R7SrF91GI--WcdHRy0shD7CfnKpfzvgXGz5VptZY6hyoDX_SYFqxFG85dxMgbLidjb8cwJOcnqzd4OAWeNjIVgSiKpaz68orEZEU7DgKHHLkM3NXU5rkALkpUrEl7Pp_" alt=""/><figcaption>An animated view of the 1DIV app being dragged across a Windows desktop with the mouse.</figcaption></figure>


<h2>Adapting to window resize</h2>


It may be useful for an app to know both whether the window controls overlay is visible and when its size changes. In our case, if the user made the window very narrow, there wouldn’t be enough space for the search field, logo, and button to fit, so we’d want to push them down a bit.


The Window Controls Overlay feature comes with a JavaScript API we can use to do this: <code>navigator.windowControlsOverlay</code>.


The API provides three interesting things:


<ul><li><code>navigator.windowControlsOverlay.visible</code> lets us know whether the overlay is visible.</li><li><code>navigator.windowControlsOverlay.getBoundingClientRect()</code> lets us know the position and size of the title bar area.</li><li><code>navigator.windowControlsOverlay.ongeometrychange</code> lets us know when the size or visibility changes.</li></ul>


Let’s use this to be aware of the size of the title bar area and move the header down if it’s too narrow.


<pre><code class="language-javascript">if (navigator.windowControlsOverlay) {
navigator.windowControlsOverlay.addEventListener('geometrychange', () => {
const { width } = navigator.windowControlsOverlay.getBoundingClientRect();
document.body.classList.toggle('narrow', width < 250);
});
}</code></pre>


In the example above, we set the <code>narrow</code> class on the <code>body</code> of the app if the title bar area is narrower than 250px. We could do something similar with a media query, but using the <code>windowControlsOverlay</code> API has two advantages for our use case:


<ul><li>It’s only fired when the feature is supported and used; we don’t want to adapt the design otherwise.</li><li>We get the size of the title bar area across operating systems, which is great because the size of the window controls is different on Mac and Windows. Using a media query wouldn’t make it possible for us to know exactly how much space remains.</li></ul>


<pre><code class="language-css">.narrow header {
top: env(titlebar-area-height, 0);
left: 0;
width: 100%;
}</code></pre>


Using the above CSS code, we can move our header down to stay clear of the window control buttons when the window is too narrow, and move the thumbnails down accordingly.


<figure class="wp-block-image"><img src="https://lh5.googleusercontent.com/e4oVs-No9pSWdYyfqTJ0QKcKrDzlv11bsoTwSVvFBhi1bUo9dP2ub71MlWa90QLEFUc5C9e81mQtg3xwGpB5Kkfvu1dNqdBVhqetz74N_0TSWh7_RfZ5NkDNJEuhv5_ZVvw-vpDG" alt=""/><figcaption>A screenshot of the 1DIV app on Windows showing the app’s content adjusted for a much narrower viewport.</figcaption></figure>


<h2>Thirty pixels of exciting design opportunities</h2>


 Using the Window Controls Overlay feature, we were able to take our simple demo app and turn it into something that feels so much more integrated on desktop devices. Something that reaches out of the usual window constraints and provides a custom experience for its users.


In reality, this feature only gives us about 30 pixels of extra room and comes with challenges on how to deal with the window controls. And yet, this extra room and those challenges can be turned into exciting design opportunities.


More devices of all shapes and forms get invented all the time, and the web keeps on evolving to adapt to them. New features get added to the web platform to allow us, web authors, to integrate more and more deeply with those devices. From watches or foldable devices to desktop computers, we need to evolve our design approach for the web. Building for the web now lets us think outside the rectangular box.


So let’s embrace this. Let’s use the standard technologies already at our disposal, and experiment with new ideas to provide tailored experiences for all devices, all from a single codebase!


If you get a chance to try the Window Controls Overlay feature and have feedback about it, you can <a href="https://github.com/WICG/window-controls-overlay/issues">open issues on the spec’s repository</a>. It’s still early in the development of this feature, and you can help make it even better. Or, you can take a look at the <a href="https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/window-controls-overlay">feature’s existing documentation</a>, or this <a href="https://stupefied-edison-a4ee55.netlify.app/">demo app</a> and its <a href="https://github.com/captainbrosset/1DIV">source code</a>.
]]> </description>
<dc:subject>
<![CDATA[Code, CSS]]> </dc:subject>
<dc:date>
2021-12-09T15:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[How to Sell UX Research with Two Simple Questions]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/sophiavoychehovski/">Sophia V. Prater</a> </author>
<link>
https://alistapart.com/article/how-to-sell-ux-research/ </link>
<guid>
https://alistapart.com/article/how-to-sell-ux-research/ </guid>
<description>
<![CDATA[
Do you find yourself designing screens with only a vague idea of how the things on the screen relate to the things elsewhere in the system? Do you leave stakeholder meetings with unclear directives that often seem to contradict previous conversations? You know a better understanding of user needs would help the team get clear on what you are actually trying to accomplish, but time and budget for research is tight. When it comes to asking for more direct contact with your users, you might feel like poor Oliver Twist, timidly asking, “Please, sir, I want some more.”


Here’s the trick. You need to get stakeholders themselves to identify high-risk assumptions and hidden complexity, so that they become just as motivated as you to get answers from users. Basically, you need to make them think it’s their idea. 


In this article, I’ll show you how to collaboratively expose misalignment and gaps in the team’s shared understanding by bringing the team together around two simple questions:


<ol><li>What are the objects?</li><li>What are the relationships between those objects?</li></ol>


<h2>A gauntlet between research and screen design</h2>


These two questions align to the first two steps of the ORCA process, which might become your new best friend when it comes to reducing guesswork. Wait, what’s ORCA?! Glad you asked.


ORCA stands for Objects, Relationships, CTAs, and Attributes, and it outlines a process for creating solid object-oriented user experiences. <a href="https://alistapart.com/article/object-oriented-ux/">Object-oriented UX</a> is my design philosophy. ORCA is an iterative methodology for synthesizing user research into an elegant structural foundation to support screen and interaction design. <a href="https://alistapart.com/article/ooux-a-foundation-for-interaction-design/">OOUX</a> and ORCA have made my work as a UX designer more collaborative, effective, efficient, fun, strategic, and meaningful.


The ORCA process has four iterative rounds and a whopping fifteen steps. In each round we get more clarity on our Os, Rs, Cs, and As.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/10/selling-ux-image1-1.jpg?resize=1024,576" alt="" class="wp-image-7173149" /><figcaption>The four rounds and fifteen steps of the ORCA process. In the OOUX world, we love color-coding. Blue is reserved for objects! (Yellow is for core content, pink is for metadata, and green is for calls-to-action. Learn more about the <a href="https://alistapart.com/article/object-oriented-ux/">color-coded object map</a> and <a href="https://alistapart.com/article/ooux-a-foundation-for-interaction-design/">connecting CTAs to objects</a>.)</figcaption></figure>


I sometimes say that ORCA is a “garbage in, garbage out” process. To ensure that the testable prototype produced in the final round actually tests well, the process needs to be fed by good research. But if you don’t have a ton of research, the beginning of the ORCA process serves another purpose: it helps you sell the need for research.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/10/selling-ux-image2-1.jpg?resize=1024,639" alt="" class="wp-image-7173150" /><figcaption>ORCA strengthens the weak spot between research and design by helping distill research into solid information architecture—scaffolding for the screen design and interaction design to hang on.</figcaption></figure>


In other words, the ORCA process serves as a gauntlet between research and design. With good research, you can gracefully ride the killer whale from research into design. But without good research, the process effectively spits you back into research and with a cache of specific open questions.


<h2>Getting in the same curiosity-boat</h2>


<blockquote class="wp-block-quote">What gets us into trouble is not what we don’t know. It’s what we know for sure that just ain’t so.<cite>Mark Twain</cite></blockquote>


The first two steps of the ORCA process—Object Discovery and Relationship Discovery—shine a spotlight on the dark, dusty corners of your team’s misalignments and any inherent complexity that’s been swept under the rug. It begins to expose what this classic comic so beautifully illustrates:


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/10/selling-ux-image3-2.jpg" alt="" class="wp-image-7173151" /><figcaption>The original “Tree Swing Project Management” cartoon dates back to the 1960s or 1970s and has no artist attribution we could find.</figcaption></figure>


This is one reason why so many UX designers are frustrated in their job and why many projects fail. And this is also why we often can’t sell research: every decision-maker is confident in their own mental picture. 


Once we expose hidden fuzzy patches in each picture and the differences between them all, the case for user research makes itself.


But how we do this is important. However much we might want to, we can’t just tell everyone, “YOU ARE WRONG!” Instead, we need to facilitate and guide our team members to self-identify holes in their picture. When stakeholders take ownership of assumptions and gaps in understanding, BAM! Suddenly, UX research is not such a hard sell, and everyone is aboard the same curiosity-boat.


Say your users are doctors. And you have no idea how doctors use the system you are tasked with redesigning.


You might try to sell research by honestly saying: “We need to understand doctors better! What are their pain points? How do they use the current app?” But here’s the problem with that. Those questions are vague, and the answers to them don’t feel acutely actionable.


Instead, you want your stakeholders themselves to ask super-specific questions. This is more like the kind of conversation you need to facilitate. Let’s listen in:


“Wait a sec, how often do doctors share patients? Does a patient in this system have primary and secondary doctors?”


“Can a patient even have more than one primary doctor?”


“Is it a ‘primary doctor’ or just a ‘primary caregiver’… Can’t that role be a nurse practitioner?”


“No, caregivers are something else… That’s the patient’s family contacts, right?”


“So are caregivers in scope for this redesign?”


“Yeah, because if a caregiver is present at an appointment, the doctor needs to note that. Like, tag the caregiver on the note… Or on the appointment?”


Now we are getting somewhere. Do you see how powerful it can be getting stakeholders to debate these questions themselves? The diabolical goal here is to shake their confidence—gently and diplomatically.


When these kinds of questions bubble up collaboratively and come directly from the mouths of your stakeholders and decision-makers, suddenly, designing screens without knowing the answers to these questions seems incredibly risky, even silly.


If we create software without understanding the real-world information environment of our users, we will likely create software that does not align to the real-world information environment of our users. And this will, hands down, result in a more confusing, more complex, and less intuitive software product.


<h2>The two questions</h2>


But how do we get to these kinds of meaty questions diplomatically, efficiently, collaboratively, and reliably? 


We can do this by starting with those two big questions that align to the first two steps of the ORCA process:


<ol><li>What are the objects?</li><li>What are the relationships between those objects?</li></ol>


In practice, getting to these answers is easier said than done. I’m going to show you how these two simple questions can provide the outline for an Object Definition Workshop. During this workshop, these “seed” questions will blossom into dozens of specific questions and shine a spotlight on the need for more user research.


<h2>Prep work: Noun foraging</h2>


In the next section, I’ll show you how to run an Object Definition Workshop with your stakeholders (and entire cross-functional team, hopefully). But first, you need to do some prep work.


Basically, look for nouns that are particular to the business or industry of your project, and do it across at least a few sources. I call this noun foraging.


Here are just a few great noun foraging sources:


<ul><li>the product’s marketing site</li><li>the product’s competitors’ marketing sites (competitive analysis, anyone?)</li><li>the existing product (look at labels!)</li><li>user interview transcripts</li><li>notes from stakeholder interviews or vision docs from stakeholders</li></ul>


Put your detective hat on, my dear Watson. Get resourceful and leverage what you have. If all you have is a marketing website, some screenshots of the existing legacy system, and access to customer service chat logs, then use those.


As you peruse these sources, watch for the nouns that are used over and over again, and start listing them (preferably on blue sticky notes if you’ll be creating an object map later!).


You’ll want to focus on nouns that might represent objects in your system. If you are having trouble determining if a noun might be object-worthy, remember the acronym SIP and test for:


<ol><li>Structure</li><li>Instances</li><li>Purpose</li></ol>


Think of a library app, for example. Is “book” an object?


Structure: can you think of a few attributes for this potential object? Title, author, publish date… Yep, it has structure. Check!


Instance: what are some examples of this potential “book” object? Can you name a few? The Alchemist, Ready Player One, Everybody Poops… OK, check!


Purpose: why is this object important to the users and business? Well, “book” is what our library client is providing to people and books are why people come to the library… Check, check, check!


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/10/selling-ux-image4-1.jpg?resize=1024,678" alt="" class="wp-image-7173152" /><figcaption>SIP: Structure, Instances, and Purpose! (Here’s a <a href="https://whimsical.com/is-it-a-object-in-the-ooux-world-PubTHzL4Hs1Kr6Xs6b8y2J">flowchart</a> where I elaborate even more on SIP.)</figcaption></figure>


As you are noun foraging, focus on capturing the nouns that have SIP. Avoid capturing components like dropdowns, checkboxes, and calendar pickers—<a href="https://alistapart.com/article/a-content-model-is-not-a-design-system/">your UX system is not your design system</a>! Components are just the packaging for objects—they are a means to an end. No one is coming to your digital place to play with your dropdown! They are coming for the VALUABLE THINGS and what they can do with them. Those things, or objects, are what we are trying to identify.


Let’s say we work for a startup disrupting the email experience. This is how I’d start my noun foraging.


First I’d look at my own email client, which happens to be Gmail. I’d then look at Outlook and the new HEY email. I’d look at Yahoo, Hotmail…I’d even look at Slack and Basecamp and other so-called “email replacers.” I’d read some articles, reviews, and forum threads where people are complaining about email. While doing all this, I would look for and write down the nouns.


(Before moving on, feel free to go noun foraging for this hypothetical product, too, and then scroll down to see how much our lists match up. Just don’t get lost in your own emails! Come back to me!)


Drumroll, please…


Here are a few nouns I came up with during my noun foraging:


<ul><li>email message</li><li>thread</li><li>contact</li><li>client</li><li>rule/automation</li><li>email address that is not a contact?</li><li>contact groups</li><li>attachment</li><li>Google doc file / other integrated file</li><li>newsletter? (HEY treats this differently)</li><li>saved responses and templates</li></ul>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/10/selling-ux-image5-1.jpg?resize=1024,683" alt="" class="wp-image-7173153" /><figcaption>In the OOUX world, we love color-coding. Blue is reserved for objects! (Yellow is for core content, pink is for metadata, and green is for calls-to-action. Learn more about the <a href="https://alistapart.com/article/object-oriented-ux/">color coded object map</a> and <a href="https://alistapart.com/article/ooux-a-foundation-for-interaction-design/">connecting CTAs to objects</a>.)</figcaption></figure>


Scan your list of nouns and pick out words that you are completely clueless about. In our email example, it might be client or automation. Do as much homework as you can before your session with stakeholders: google what’s googleable. But other terms might be so specific to the product or domain that you need to have a conversation about them.


Aside: here are some real nouns foraged during my own past project work that I needed my stakeholders to help me understand:


<ul><li>Record Locator</li><li>Incentive Home</li><li>Augmented Line Item</li><li>Curriculum-Based Measurement Probe</li></ul>


This is really all you need to prepare for the workshop session: a list of nouns that represent potential objects and a short list of nouns that need to be defined further.


<h2>Facilitate an Object Definition Workshop</h2>


You could actually start your workshop with noun foraging—this activity can be done collaboratively. If you have five people in the room, pick five sources, assign one to every person, and give everyone ten minutes to find the objects within their source. When the time’s up, come together and find the overlap. Affinity mapping is your friend here!


If your team is short on time and might be reluctant to do this kind of grunt work (which is usually the case) do your own noun foraging beforehand, but be prepared to show your work. I love presenting screenshots of documents and screens with all the nouns already highlighted. Bring the artifacts of your process, and start the workshop with a five-minute overview of your noun foraging journey.


HOT TIP: before jumping into the workshop, frame the conversation as a requirements-gathering session to help you better understand the scope and details of the system. You don’t need to let them know that you’re looking for gaps in the team’s understanding so that you can prove the need for more user research—that will be our little secret. Instead, go into the session optimistically, as if your knowledgeable stakeholders and PMs and biz folks already have all the answers.


Then, let the question whack-a-mole commence.


<h3>1. What is this thing?</h3>


Want to have some real fun? At the beginning of your session, ask stakeholders to privately write definitions for the handful of obscure nouns you might be uncertain about. Then, have everyone show their cards at the same time and see if you get different definitions (you will). This is gold for exposing misalignment and starting great conversations.


As your discussion unfolds, capture any agreed-upon definitions. And when uncertainty emerges, quietly (but visibly) start an “open questions” parking lot. 😉


After definitions solidify, here’s a great follow-up:


<h3>2. Do our users know what these things are? What do users call this thing?</h3>


Stakeholder 1: They probably call email clients “apps.” But I’m not sure.


Stakeholder 2: Automations are often called “workflows,” I think. Or, maybe users think workflows are something different.


If a more user-friendly term emerges, ask the group if they can agree to use only that term moving forward. This way, the team can better align to the users’ language and mindset.


OK, moving on. 


If you have two or more objects that seem to overlap in purpose, ask one of these questions:


<h3>3. Are these the same thing? Or are these different? If they are not the same, how are they different?</h3>


You: Is a saved response the same as a template?


Stakeholder 1: Yes! Definitely.


Stakeholder 2: I don’t think so… A saved response is text with links and variables, but a template is more about the look and feel, like default fonts, colors, and placeholder images. 


Continue to build out your growing glossary of objects. And continue to capture areas of uncertainty in your “open questions” parking lot.


If you successfully determine that two similar things are, in fact, different, here’s your next follow-up question:


<h3>4. What’s the relationship between these objects?</h3>


You: Are saved responses and templates related in any way?


Stakeholder 3:  Yeah, a template can be applied to a saved response.


You, always with the follow-ups: When is the template applied to a saved response? Does that happen when the user is constructing the saved response? Or when they apply the saved response to an email? How does that actually work?


Listen. Capture uncertainty. Once the list of “open questions” grows to a critical mass, pause to start assigning questions to groups or individuals. Some questions might be for the dev team (hopefully at least one developer is in the room with you). One question might be specifically for someone who couldn’t make it to the workshop. And many questions will need to be labeled “user.” 


Do you see how we are building up to our UXR sales pitch?


<h3>5. Is this object in scope?</h3>


Your next question narrows the team’s focus toward what’s most important to your users. You can simply ask, “Are saved responses in scope for our first release?,” but I’ve got a better, more devious strategy.


By now, you should have a list of clearly defined objects. Ask participants to sort these objects from most to least important, either in small breakout groups or individually. Then, like you did with the definitions, have everyone reveal their sort order at once. Surprisingly—or not so surprisingly—it’s not unusual for the VP to rank something like “saved responses” as #2 while everyone else puts it at the bottom of the list. Try not to look too smug as you inevitably expose more misalignment.


I did this for a startup a few years ago. We posted the three groups’ wildly different sort orders on the whiteboard.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/10/selling-ux-image6-1.jpg?resize=1024,831" alt="" class="wp-image-7173154" /><figcaption>Here’s a snippet of the very messy middle from this session: three columns of object cards, showing the same cards prioritized completely differently by three different groups.</figcaption></figure>


The CEO stood back, looked at it, and said, “This is why we haven’t been able to move forward in two years.”


Admittedly, it’s tragic to hear that, but as a professional, it feels pretty awesome to be the one who facilitated a watershed realization.


Once you have a good idea of in-scope, clearly defined things, this is when you move on to doing more relationship mapping.


<h3>6. Create a visual representation of the objects’ relationships</h3>


We’ve already done a bit of this while trying to determine if two things are different, but this time, ask the team about every potential relationship. For each object, ask how it relates to all the other objects. In what ways are the objects connected? To visualize all the connections, pull out your trusty boxes-and-arrows technique. Here, we are connecting our objects with verbs. I like to keep my verbs to simple “has a” and “has many” statements.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/10/selling-ux-image7-1.jpg?resize=1024,700" alt="" class="wp-image-7173155" /><figcaption>A work-in-progress system model of our new email solution.</figcaption></figure>


This system modeling activity brings up all sorts of new questions:


<ul><li>Can a saved response have attachments?</li><li>Can a saved response use a template? If so, if an email uses a saved response with a template, can the user override that template?</li><li>Do users want to see all the emails they sent that included a particular attachment? For example, “show me all the emails I sent with ProfessionalImage.jpg attached. I’ve changed my professional photo and I want to alert everyone to update it.” </li></ul>


Solid answers might emerge directly from the workshop participants. Great! Capture that new shared understanding. But when uncertainty surfaces, continue to add questions to your growing parking lot.


<h2>Light the fuse</h2>


You’ve positioned the explosives all along the floodgates. Now you simply have to light the fuse and BOOM. Watch the buy-in for user research flooooow.


Before your workshop wraps up, have the group reflect on the list of open questions. Make plans for getting answers internally, then focus on the questions that need to be brought before users.


Here’s your final step. Take those questions you’ve compiled for user research and discuss the level of risk associated with NOT answering them. Ask, “if we design without an answer to this question, if we make up our own answer and we are wrong, how bad might that turn out?” 


With this methodology, we are cornering our decision-makers into advocating for user research as they themselves label questions as high-risk. Sorry, not sorry. 


Now is your moment of truth. With everyone in the room, ask for a reasonable budget of time and money to conduct 6–8 user interviews focused specifically on these questions. 


HOT TIP: if you are new to UX research, please note that you’ll likely need to rephrase the questions that came up during the workshop before you present them to users. Make sure your questions are open-ended and don’t lead the user into any default answers.


<h2>Final words: Hold the screen design!</h2>


Seriously, if at all possible, do not ever design screens again without first answering these fundamental questions: what are the objects and how do they relate?


I promise you this: if you can secure a shared understanding between the business, design, and development teams before you start designing screens, you will have less heartache and save more time and money, and (it almost feels like a bonus at this point!) users will be more receptive to what you put out into the world. 


I sincerely hope this helps you win time and budget to go talk to your users and gain clarity on what you are designing before you start building screens. If you find success using noun foraging and the Object Definition Workshop, there’s more where that came from in the rest of the ORCA process, which will help prevent even more late-in-the-game scope tugs-of-war and strategy pivots. 


All the best of luck! Now go sell research!
]]> </description>
<dc:subject>
<![CDATA[User Experience, User Research]]> </dc:subject>
<dc:date>
2021-10-21T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[A Content Model Is Not a Design System]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/mike-wills/">Mike Wills</a> </author>
<link>
https://alistapart.com/article/a-content-model-is-not-a-design-system/ </link>
<guid>
https://alistapart.com/article/a-content-model-is-not-a-design-system/ </guid>
<description>
<![CDATA[
Do you remember when having a great website was enough? Now, people are getting answers from Siri, Google search snippets, and mobile apps, not just our websites. Forward-thinking organizations have adopted an omnichannel content strategy, whose mission is to reach audiences across multiple digital channels and platforms.


But how do you set up a content management system (CMS) to reach your audience now and in the future? I learned the hard way that creating a <a href="https://alistapart.com/article/content-modelling-a-master-skill/">content model</a>—a definition of content types, attributes, and relationships that let people and systems understand content—with my more familiar design-system thinking would capsize my customer’s omnichannel content strategy. You can avoid that outcome by creating content models that are semantic and that also connect related content.


I recently had the opportunity to lead the CMS implementation for a Fortune 500 company. The client was excited by the benefits of an omnichannel content strategy, including content reuse, multichannel <a href="https://bluemodus.com/articles/a-content-first-approach-in-a-multi-channel-world">marketing</a>, and <a href="https://alistapart.com/article/conversations-with-robots/">robot delivery</a>—designing content to be intelligible to bots, Google knowledge panels, snippets, and voice user interfaces.


A content model is a critical foundation for an omnichannel content strategy, and for our content to be understood by multiple systems, the model needed semantic types—types named according to their meaning instead of their presentation. Our goal was to let authors create content and reuse it wherever it was relevant. But as the project proceeded, I realized that supporting content reuse at the scale that my customer needed required the whole team to recognize a new pattern.


Despite our best intentions, we kept drawing from what we were more familiar with: <a href="https://alistapart.com/article/learning-from-lego-a-step-forward-in-modular-web-design/">design systems</a>. Unlike web-focused content strategies, an omnichannel content strategy can’t rely on WYSIWYG tools for design and layout. Our tendency to approach the content model with our familiar design-system thinking constantly led us to veer away from one of the primary purposes of a content model: delivering content to audiences on multiple marketing channels.


<h2>Two essential principles for an effective content model</h2>


We needed to help our designers, developers, and stakeholders understand that we were doing something very different from their prior web projects, where it was natural for everyone to think about content as visual building blocks fitting into layouts. The previous approach was not only more familiar but also more intuitive—at least at first—because it made the designs feel more tangible. We discovered two principles that helped the team understand how a content model differs from the design systems that we were used to:


<ol><li>Content models must define semantics instead of layout.</li><li>And content models should connect content that belongs together.</li></ol>


<h3>Semantic content models</h3>


A semantic content model uses type and attribute names that reflect the meaning of the content, not how it will be displayed. For example, in a nonsemantic model, teams might create types like teasers, media blocks, and cards. Although these types might make it easy to lay out content, they don’t help delivery channels understand the content’s meaning, which in turn would have opened the door to the content being presented in each marketing channel. In contrast, a semantic content model uses type names like product, service, and testimonial so that each delivery channel can understand the content and use it as it sees fit.


When you’re creating a semantic content model, a great place to start is to look over the types and properties defined by <a href="https://schema.org/">Schema.org</a>, a community-driven resource for type definitions that are intelligible to platforms like Google search.


A semantic content model has several benefits:


<ul><li>Even if your team doesn’t care about omnichannel content, a semantic content model decouples content from its presentation so that teams can evolve the website’s design without needing to refactor its content. In this way, content can withstand disruptive website redesigns. </li><li>A semantic content model also provides a competitive edge. By adding <a href="https://developers.google.com/search/docs/guides/intro-structured-data">structured data</a> based on Schema.org’s types and properties, a website can provide hints to help Google understand the content, display it in search snippets or knowledge panels, and use it to answer voice-interface user questions. Potential visitors could discover your content without ever setting foot in your website.</li><li>Beyond those practical benefits, you’ll also need a semantic content model if you want to deliver omnichannel content. To use the same content in multiple marketing channels, delivery channels need to be able to understand it. For example, if your content model were to provide a list of questions and answers, it could easily be rendered on a frequently asked questions (FAQ) page, but it could also be used in a <a href="https://alistapart.com/article/usability-testing-for-voice-content/">voice interface</a> or by a bot that answers <a href="https://alistapart.com/article/the-faq-as-advice-column/">common questions</a>.</li></ul>


For example, using a semantic content model for articles, events, people, and locations lets A List Apart provide cleanly structured data for search engines so that users can read the content on the website, in Google knowledge panels, and even with hypothetical voice interfaces in the future.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/09/image2.png?w=960" alt="Image showing an event in a CMS passing data to a Google knowledge panel, a website, and a voice interface" class="wp-image-7173120"/></figure>


<h3>Content models that connect</h3>


After struggling to describe what makes a good content model, I’ve come to realize that the best models are those that are semantic and that also connect related content components (such as a FAQ item’s question and answer pair), instead of slicing up related content across disparate content components. A good content model connects content that should remain together so that multiple delivery channels can use it without needing to first put those pieces back together.


Think about writing an article or essay. An article’s meaning and usefulness depends upon its parts being kept together. Would one of the headings or paragraphs be meaningful on their own without the context of the full article? On our project, our familiar design-system thinking often led us to want to create content models that would slice content into disparate chunks to fit the web-centric layout. This had a similar impact to an article that were to have been separated from its headline. Because we were slicing content into standalone pieces based on layout, content that belonged together became difficult to manage and nearly impossible for multiple delivery channels to understand.


To illustrate, let’s look at how connecting related content applies in a real-world scenario. The design team for our customer presented a complex layout for a software product page that included multiple tabs and sections. Our instincts were to follow suit with the content model. Shouldn’t we make it as easy and as flexible as possible to add any number of tabs in the future?


Because our design-system instincts were so familiar, it felt like we had needed a content type called “tab section” so that multiple tab sections could be added to a page. Each tab section would display various types of content. One tab might provide the software’s overview or its specifications. Another tab might provide a list of resources. 


Our inclination to break down the content model into “tab section” pieces would have led to an unnecessarily complex model and a cumbersome editing experience, and it would have also created content that couldn’t have been understood by additional delivery channels. For example, how would another system have been able to tell which “tab section” referred to a product’s specifications or its resource list—would that other system have to have resorted to counting tab sections and content blocks? This would have prevented the tabs from ever being reordered, and it would have required adding logic in every other delivery channel to interpret the design system’s layout. Furthermore, if the customer were to have no longer wanted to display this content in a tab layout, it would have been tedious to migrate to a new content model to reflect the new page redesign.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/09/image3.png?w=723" alt="Illustration showing a data tree flowing into a list of cards (data), flowing into a navigation menu on a website" class="wp-image-7173121"/><figcaption>A content model based on design components is unnecessarily complex, and it’s unintelligible to systems.</figcaption></figure>


We had a breakthrough when we discovered that our customer had a specific purpose in mind for each tab: it would reveal specific information such as the software product’s overview, specifications, related resources, and pricing. Once implementation began, our inclination to focus on what’s visual and familiar had obscured the intent of the designs. With a little digging, it didn’t take long to realize that the concept of tabs wasn’t relevant to the content model. The meaning of the content that they were planning to display in the tabs was what mattered.


In fact, the customer could have decided to display this content in a different way—without tabs—somewhere else. This realization prompted us to define content types for the software product based on the meaningful attributes that the customer had wanted to render on the web. There were obvious semantic attributes like name and description as well as rich attributes like screenshots, software requirements, and feature lists. The software’s product information stayed together because it wasn’t sliced across separate components like “tab sections” that were derived from the content’s presentation. Any delivery channel—including future ones—could understand and present this content.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/09/image1.png?w=695" alt="Illustration showing a data tree flowing into a formatted list, flowing into a navigation menu on a website" class="wp-image-7173119"/><figcaption>A good content model connects content that belongs together so it can be easily managed and reused.</figcaption></figure>


<h2>Conclusion</h2>


In this omnichannel marketing project, we discovered that the best way to keep our content model on track was to ensure that it was semantic (with type and attribute names that reflected the meaning of the content) and that it kept content together that belonged together (instead of fragmenting it). These two concepts curtailed our temptation to shape the content model based on the design. So if you’re working on a content model to support an omnichannel content strategy—or even if you just want to make sure that Google and other interfaces understand your content—remember:


<ul><li>A design system isn’t a content model. Team members may be tempted to conflate them and to make your content model mirror your design system, so you should protect the semantic value and contextual structure of the content strategy during the entire implementation process. This will let every delivery channel consume the content without needing a magic decoder ring.</li><li>If your team is struggling to make this transition, you can still reap some of the benefits by using Schema.org–based structured data in your website. Even if additional delivery channels aren’t on the immediate horizon, the benefit to search engine optimization is a compelling reason on its own.</li><li>Additionally, remind the team that decoupling the content model from the design will let them update the designs more easily because they won’t be held back by the cost of content migrations. They’ll be able to create new designs without the obstacle of compatibility between the design and the content, and they’ll be ready for the next big thing. </li></ul>


By rigorously advocating for these principles, you’ll help your team treat content the way that it deserves—as the most critical asset in your user experience and the best way to connect with your audience.
]]> </description>
<dc:subject>
<![CDATA[Content, Content Strategy]]> </dc:subject>
<dc:date>
2021-09-23T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Design for Safety, An Excerpt]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/eva-penzeymoog/">Eva PenzeyMoog</a> </author>
<link>
https://alistapart.com/article/design-for-safety-excerpt/ </link>
<guid>
https://alistapart.com/article/design-for-safety-excerpt/ </guid>
<description>
<![CDATA[
Antiracist economist Kim Crayton says that “intention without strategy is chaos.” We’ve discussed how our biases, assumptions, and inattention toward marginalized and vulnerable groups lead to dangerous and unethical tech—but what, specifically, do we need to do to fix it? The intention to make our tech safer is not enough; we need a strategy.


This chapter will equip you with that plan of action. It covers how to integrate safety principles into your design work in order to create tech that’s safe, how to convince your stakeholders that this work is necessary, and how to respond to the critique that what we actually need is more diversity. (Spoiler: we do, but diversity alone is not the antidote to fixing unethical, unsafe tech.)


<h2>The process for inclusive safety</h2>


When you are designing for safety, your goals are to:


<ul><li>identify ways your product can be used for abuse,</li><li>design ways to prevent the abuse, and</li><li>provide support for vulnerable users to reclaim power and control.</li></ul>


The Process for Inclusive Safety is a tool to help you reach those goals (Fig 5.1). It’s a methodology I created in 2018 to capture the various techniques I was using when designing products with safety in mind. Whether you are creating an entirely new product or adding to an existing feature, the Process can help you make your product safe and inclusive. The Process includes five general areas of action:


<ul><li>Conducting research</li><li>Creating archetypes</li><li>Brainstorming problems</li><li>Designing solutions</li><li>Testing for safety</li></ul>


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/dfs-fig-5-1.jpg" alt="" class="wp-image-7173096"/><figcaption>Fig 5.1: Each aspect of the Process for Inclusive Safety can be incorporated into your design process where it makes the most sense for you. The times given are estimates to help you incorporate the stages into your design plan.</figcaption></figure>


The Process is meant to be flexible—it won’t make sense for teams to implement every step in some situations. Use the parts that are relevant to your unique work and context; this is meant to be something you can insert into your existing design practice.


And once you use it, if you have an idea for making it better or simply want to provide context of how it helped your team, please get in touch with me. It’s a living document that I hope will continue to be a useful and realistic tool that technologists can use in their day-to-day work.


If you’re working on a product specifically for a vulnerable group or survivors of some form of trauma, such as an app for survivors of domestic violence, sexual assault, or drug addiction, be sure to read Chapter 7, which covers that situation explicitly and should be handled a bit differently. The guidelines here are for prioritizing safety when designing a more general product that will have a wide user base (which, we already know from statistics, will include certain groups that should be protected from harm). Chapter 7 is focused on products that are specifically for vulnerable groups and people who have experienced trauma.


<h3>Step 1: Conduct research</h3>


Design research should include a broad analysis of how your tech might be weaponized for abuse as well as specific insights into the experiences of survivors and perpetrators of that type of abuse. At this stage, you and your team will investigate issues of interpersonal harm and abuse, and explore any other safety, security, or inclusivity issues that might be a concern for your product or service, like data security, racist algorithms, and harassment.


<h4>Broad research</h4>


Your project should begin with broad, general research into similar products and issues around safety and ethical concerns that have already been reported. For example, a team building a smart home device would do well to understand the multitude of ways that existing smart home devices have been used as tools of abuse. If your product will involve AI, seek to understand the potentials for racism and other issues that have been reported in existing AI products. Nearly all types of technology have some kind of potential or actual harm that’s been reported on in the news or written about by academics. <a href="https://scholar.google.com">Google Scholar</a> is a useful tool for finding these studies.


<h4>Specific research: Survivors</h4>


When possible and appropriate, include direct research (surveys and interviews) with people who are experts in the forms of harm you have uncovered. Ideally, you’ll want to interview advocates working in the space of your research first so that you have a more solid understanding of the topic and are better equipped to not retraumatize survivors. If you’ve uncovered possible domestic violence issues, for example, the experts you’ll want to speak with are survivors themselves, as well as workers at domestic violence hotlines, shelters, other related nonprofits, and lawyers.


Especially when interviewing survivors of any kind of trauma, it is important to pay people for their knowledge and lived experiences. Don’t ask survivors to share their trauma for free, as this is exploitative. While some survivors may not want to be paid, you should always make the offer in the initial ask. An alternative to payment is to donate to an organization working against the type of violence that the interviewee experienced. We’ll talk more about how to appropriately interview survivors in Chapter 6.


<h4>Specific research: Abusers</h4>


It’s unlikely that teams aiming to design for safety will be able to interview self-proclaimed abusers or people who have broken laws around things like hacking. Don’t make this a goal; rather, try to get at this angle in your general research. Aim to understand how abusers or bad actors weaponize technology to use against others, how they cover their tracks, and how they explain or rationalize the abuse.


<h3>Step 2: Create archetypes</h3>


Once you’ve finished conducting your research, use your insights to create abuser and survivor archetypes. Archetypes are not personas, as they’re not based on real people that you interviewed and surveyed. Instead, they’re based on your research into likely safety issues, much like when we design for accessibility: we don’t need to have found a group of blind or low-vision users in our interview pool to create a design that’s inclusive of them. Instead, we base those designs on existing research into what this group needs. Personas typically represent real users and include many details, while archetypes are broader and can be more generalized.


The abuser archetype is someone who will look at the product as a tool to perform harm (Fig 5.2). They may be trying to harm someone they don’t know through surveillance or anonymous harassment, or they may be trying to control, monitor, abuse, or torment someone they know personally.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/5.2-abuser-archetype-Harry-Oleson.jpg?resize=1024,766" alt="" class="wp-image-7173097"/><figcaption>Fig 5.2: Harry Oleson, an abuser archetype for a fitness product, is looking for ways to stalk his ex-girlfriend through the fitness apps she uses.</figcaption></figure>


The survivor archetype is someone who is being abused with the product. There are various situations to consider in terms of the archetype’s understanding of the abuse and how to put an end to it: Do they need proof of abuse they already suspect is happening, or are they unaware they’ve been targeted in the first place and need to be alerted (Fig 5.3)?


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/5.3-survivor-archetype-Lisa-Zwaan.jpg?resize=1024,766" alt="" class="wp-image-7173098"/><figcaption>Fig 5.3: The survivor archetype Lisa Zwaan suspects her husband is weaponizing their home’s IoT devices against her, but in the face of his insistence that she simply doesn’t understand how to use the products, she’s unsure. She needs some kind of proof of the abuse.</figcaption></figure>


You may want to make multiple survivor archetypes to capture a range of different experiences. They may know that the abuse is happening but not be able to stop it, like when an abuser locks them out of IoT devices; or they know it’s happening but don’t know how, such as when a stalker keeps figuring out their location (Fig 5.4). Include as many of these scenarios as you need to in your survivor archetype. You’ll use these later on when you design solutions to help your survivor archetypes achieve their goals of preventing and ending abuse.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/5.4-survivor-archetype-Eric-Mitchell.jpg?resize=1024,766" alt="" class="wp-image-7173099"/><figcaption>Fig 5.4: The survivor archetype Eric Mitchell knows he’s being stalked by his ex-boyfriend Rob but can’t figure out how Rob is learning his location information.</figcaption></figure>


It may be useful for you to create persona-like artifacts for your archetypes, such as the three examples shown. Instead of focusing on the demographic information we often see in personas, focus on their goals. The goals of the abuser will be to carry out the specific abuse you’ve identified, while the goals of the survivor will be to prevent abuse, understand that abuse is happening, make ongoing abuse stop, or regain control over the technology that’s being used for abuse. Later, you’ll brainstorm how to prevent the abuser’s goals and assist the survivor’s goals.


And while the “abuser/survivor” model fits most cases, it doesn’t fit all, so modify it as you need to. For example, if you uncovered an issue with security, such as the ability for someone to hack into a home camera system and talk to children, the malicious hacker would get the abuser archetype and the child’s parents would get survivor archetype.


<h3>Step 3: Brainstorm problems</h3>


After creating archetypes, brainstorm novel abuse cases and safety issues. “Novel” means things not found in your research; you’re trying to identify completely new safety issues that are unique to your product or service. The goal with this step is to exhaust every effort of identifying harms your product could cause. You aren’t worrying about how to prevent the harm yet—that comes in the next step.


How could your product be used for any kind of abuse, outside of what you’ve already identified in your research? I recommend setting aside at least a few hours with your team for this process.


If you’re looking for somewhere to start, try doing a Black Mirror brainstorm. This exercise is based on the show Black Mirror, which features stories about the dark possibilities of technology. Try to figure out how your product would be used in an episode of the show—the most wild, awful, out-of-control ways it could be used for harm. When I’ve led Black Mirror brainstorms, participants usually end up having a good deal of fun (which I think is great—it’s okay to have fun when designing for safety!). I recommend time-boxing a Black Mirror brainstorm to half an hour, and then dialing it back and using the rest of the time thinking of more realistic forms of harm.


After you’ve identified as many opportunities for abuse as possible, you may still not feel confident that you’ve uncovered every potential form of harm. A healthy amount of anxiety is normal when you’re doing this kind of work. It’s common for teams designing for safety to worry, “Have we really identified every possible harm? What if we’ve missed something?” If you’ve spent at least four hours coming up with ways your product could be used for harm and have run out of ideas, go to the next step.


It’s impossible to guarantee you’ve thought of everything; instead of aiming for 100 percent assurance, recognize that you’ve taken this time and have done the best you can, and commit to continuing to prioritize safety in the future. Once your product is released, your users may identify new issues that you missed; aim to receive that feedback graciously and course-correct quickly.


<h3>Step 4: Design solutions</h3>


At this point, you should have a list of ways your product can be used for harm as well as survivor and abuser archetypes describing opposing user goals. The next step is to identify ways to design against the identified abuser’s goals and to support the survivor’s goals. This step is a good one to insert alongside existing parts of your design process where you’re proposing solutions for the various problems your research uncovered.


Some questions to ask yourself to help prevent harm and support your archetypes include:


<ul><li>Can you design your product in such a way that the identified harm cannot happen in the first place? If not, what roadblocks can you put up to prevent the harm from happening?</li><li>How can you make the victim aware that abuse is happening through your product?</li><li>How can you help the victim understand what they need to do to make the problem stop?</li><li>Can you identify any types of user activity that would indicate some form of harm or abuse? Could your product help the user access support?</li></ul>


In some products, it’s possible to proactively recognize that harm is happening. For example, a pregnancy app might be modified to allow the user to report that they were the victim of an assault, which could trigger an offer to receive resources for local and national organizations. This sort of proactiveness is not always possible, but it’s worth taking a half hour to discuss if any type of user activity would indicate some form of harm or abuse, and how your product could assist the user in receiving help in a safe manner.


That said, use caution: you don’t want to do anything that could put a user in harm’s way if their devices are being monitored. If you do offer some kind of proactive help, always make it voluntary, and think through other safety issues, such as the need to keep the user in-app in case an abuser is checking their search history. We’ll walk through a good example of this in the next chapter.


<h3>Step 5: Test for safety</h3>


The final step is to test your prototypes from the point of view of your archetypes: the person who wants to weaponize the product for harm and the victim of the harm who needs to regain control over the technology. Just like any other kind of product testing, at this point you’ll aim to rigorously test out your safety solutions so that you can identify gaps and correct them, validate that your designs will help keep your users safe, and feel more confident releasing your product into the world.


Ideally, safety testing happens along with usability testing. If you’re at a company that doesn’t do usability testing, you might be able to use safety testing to cleverly perform both; a user who goes through your design attempting to weaponize the product against someone else can also be encouraged to point out interactions or other elements of the design that don’t make sense to them.


You’ll want to conduct safety testing on either your final prototype or the actual product if it’s already been released. There’s nothing wrong with testing an existing product that wasn’t designed with safety goals in mind from the onset—“retrofitting” it for safety is a good thing to do.


Remember that testing for safety involves testing from the perspective of both an abuser and a survivor, though it may not make sense for you to do both. Alternatively, if you made multiple survivor archetypes to capture multiple scenarios, you’ll want to test from the perspective of each one.


As with other sorts of usability testing, you as the designer are most likely too close to the product and its design by this point to be a valuable tester; you know the product too well. Instead of doing it yourself, set up testing as you would with other usability testing: find someone who is not familiar with the product and its design, set the scene, give them a task, encourage them to think out loud, and observe how they attempt to complete it.


<h4>Abuser testing</h4>


The goal of this testing is to understand how easy it is for someone to weaponize your product for harm. Unlike with usability testing, you want to make it impossible, or at least difficult, for them to achieve their goal. Reference the goals in the abuser archetype you created earlier, and use your product in an attempt to achieve them.


For example, for a fitness app with GPS-enabled location features, we can imagine that the abuser archetype would have the goal of figuring out where his ex-girlfriend now lives. With this goal in mind, you’d try everything possible to figure out the location of another user who has their privacy settings enabled. You might try to see her running routes, view any available information on her profile, view anything available about her location (which she has set to private), and investigate the profiles of any other users somehow connected with her account, such as her followers.


If by the end of this you’ve managed to uncover some of her location data, despite her having set her profile to private, you know now that your product enables stalking. Your next step is to go back to step 4 and figure out how to prevent this from happening. You may need to repeat the process of designing solutions and testing them more than once.


<h4>Survivor testing</h4>


Survivor testing involves identifying how to give information and power to the survivor. It might not always make sense based on the product or context. Thwarting the attempt of an abuser archetype to stalk someone also satisfies the goal of the survivor archetype to not be stalked, so separate testing wouldn’t be needed from the survivor’s perspective.


However, there are cases where it makes sense. For example, for a smart thermostat, a survivor archetype’s goals would be to understand who or what is making the temperature change when they aren’t doing it themselves. You could test this by looking for the thermostat’s history log and checking for usernames, actions, and times; if you couldn’t find that information, you would have more work to do in step 4.


Another goal might be regaining control of the thermostat once the survivor realizes the abuser is remotely changing its settings. Your test would involve attempting to figure out how to do this: are there instructions that explain how to remove another user and change the password, and are they easy to find? This might again reveal that more work is needed to make it clear to the user how they can regain control of the device or account.


<h4>Stress testing</h4>


To make your product more inclusive and compassionate, consider adding stress testing. This concept comes from <a href="https://abookapart.com/products/design-for-real-life">Design for Real Life</a> by Eric Meyer and Sara Wachter-Boettcher. The authors pointed out that personas typically center people who are having a good day—but real users are often anxious, stressed out, having a bad day, or even experiencing tragedy. These are called “stress cases,” and testing your products for users in stress-case situations can help you identify places where your design lacks compassion. Design for Real Life has more details about what it looks like to incorporate stress cases into your design as well as many other great tactics for compassionate design.
]]> </description>
<dc:subject>
<![CDATA[Process, Usability, User Experience, User Research]]> </dc:subject>
<dc:date>
2021-08-26T15:01:43+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Sustainable Web Design, An Excerpt]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/tom-greenwood/">Tom Greenwood</a> </author>
<link>
https://alistapart.com/article/sustainable-web-design-excerpt/ </link>
<guid>
https://alistapart.com/article/sustainable-web-design-excerpt/ </guid>
<description>
<![CDATA[
In the 1950s, many in the elite running community had begun to believe it wasn’t possible to run a mile in less than four minutes. Runners had been attempting it since the late 19th century and were beginning to draw the conclusion that the human body simply wasn’t built for the task. 


But on May 6, 1956, Roger Bannister took everyone by surprise. It was a cold, wet day in Oxford, England—conditions no one expected to lend themselves to record-setting—and yet Bannister did just that, running a mile in 3:59.4 and becoming the first person in the record books to run a mile in under four minutes. 


This shift in the benchmark had profound effects; the world now knew that the four-minute mile was possible. Bannister’s record lasted only forty-six days, when it was snatched away by Australian runner John Landy. Then a year later, three runners all beat the four-minute barrier together in the same race. Since then, over 1,400 runners have officially <a href="https://en.wikipedia.org/wiki/Four-minute_mile">run a mile in under four minutes</a>; the current record is 3:43.13, held by Moroccan athlete Hicham El Guerrouj.


We achieve far more when we believe that something is possible, and we will believe it’s possible only when we see someone else has already done it—and as with human running speed, so it is with what we believe are the hard limits for how a website needs to perform.


<h2>Establishing standards for a sustainable web</h2>


In most major industries, the key metrics of environmental performance are fairly well established, such as miles per gallon for cars or energy per square meter for homes. The tools and methods for calculating those metrics are standardized as well, which keeps everyone on the same page when doing environmental assessments. In the world of websites and apps, however, we aren’t held to any particular environmental standards, and only recently have gained the tools and methods we need to even make an environmental assessment.


The primary goal in sustainable web design is to reduce carbon emissions. However, it’s almost impossible to actually measure the amount of CO2 produced by a web product. We can’t measure the fumes coming out of the exhaust pipes on our laptops. The emissions of our websites are far away, out of sight and out of mind, coming out of power stations burning coal and gas. We have no way to trace the electrons from a website or app back to the power station where the electricity is being generated and actually know the exact amount of greenhouse gas produced. So what do we do?


If we can’t measure the actual carbon emissions, then we need to find what we can measure. The primary factors that could be used as indicators of carbon emissions are:


<ol><li>Data transfer </li><li>Carbon intensity of electricity</li></ol>


Let’s take a look at how we can use these metrics to quantify the energy consumption, and in turn the carbon footprint, of the websites and web apps we create.


<h3>Data transfer</h3>


Most researchers use kilowatt-hours per gigabyte (kWh/GB) as a metric of energy efficiency when measuring the amount of data transferred over the internet when a website or application is used. This provides a great reference point for energy consumption and carbon emissions. As a rule of thumb, the more data transferred, the more energy used in the data center, telecoms networks, and end user devices.


For web pages, data transfer for a single visit can be most easily estimated by measuring the page weight, meaning the transfer size of the page in kilobytes the first time someone visits the page. It’s fairly easy to measure using the developer tools in any modern web browser. Often your web hosting account will include statistics for the total data transfer of any web application (Fig 2.1).


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/2-1.png" alt="" class="wp-image-7173077" /><figcaption>Fig 2.1: The Kinsta hosting dashboard displays data transfer alongside traffic volumes. If you divide data transfer by visits, you get the average data per visit, which can be used as a metric of efficiency.</figcaption></figure>


The nice thing about page weight as a metric is that it allows us to compare the efficiency of web pages on a level playing field without confusing the issue with constantly changing traffic volumes. 


Reducing page weight requires a large scope. By early 2020, the median page weight was 1.97 MB for setups the HTTP Archive classifies as “desktop” and 1.77 MB for “mobile,” with desktop increasing 36 percent since January 2016 and mobile page weights nearly <a href="https://httparchive.org/reports/state-of-the-web#bytesTotal">doubling in the same period</a> (Fig 2.2). Roughly half of this data transfer is image files, making images the single biggest source of carbon emissions on the average website.


History clearly shows us that our web pages can be smaller, if only we set our minds to it. While most technologies become ever more energy efficient, including the underlying technology of the web such as data centers and transmission networks, websites themselves are a technology that becomes less efficient as time goes on.


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/2-2.png" alt="" class="wp-image-7173078" /><figcaption>Fig 2.2: The historical page weight data from HTTP Archive can teach us a lot about what is possible in the future.</figcaption></figure>


You might be familiar with the concept of performance budgeting as a way of focusing a project team on creating faster user experiences. For example, we might specify that the website must load in a maximum of one second on a broadband connection and three seconds on a 3G connection. Much like speed limits while driving, performance budgets are upper limits rather than vague suggestions, so the goal should always be to come in under budget.


Designing for fast performance does often lead to reduced data transfer and emissions, but it isn’t always the case. Web performance is often more about the subjective perception of load times than it is about the true efficiency of the underlying system, whereas page weight and transfer size are more objective measures and more reliable benchmarks for sustainable web design. 


We can set a page weight budget in reference to a benchmark of industry averages, using data from sources like HTTP Archive. We can also benchmark page weight against competitors or the old version of the website we’re replacing. For example, we might set a maximum page weight budget as equal to our most efficient competitor, or we could set the benchmark lower to guarantee we are best in class. 


If we want to take it to the next level, then we could also start looking at the transfer size of our web pages for repeat visitors. Although page weight for the first time someone visits is the easiest thing to measure, and easy to compare on a like-for-like basis, we can learn even more if we start looking at transfer size in other scenarios too. For example, visitors who load the same page multiple times will likely have a high percentage of the files cached in their browser, meaning they don’t need to transfer all of the files on subsequent visits. Likewise, a visitor who navigates to new pages on the same website will likely not need to load the full page each time, as some global assets from areas like the header and footer may already be cached in their browser. Measuring transfer size at this next level of detail can help us learn even more about how we can optimize efficiency for users who regularly visit our pages, and enable us to set page weight budgets for additional scenarios beyond the first visit.


Page weight budgets are easy to track throughout a design and development process. Although they don’t actually tell us carbon emission and energy consumption analytics directly, they give us a clear indication of efficiency relative to other websites. And as transfer size is an effective analog for energy consumption, we can actually use it to estimate energy consumption too.


In summary, reduced data transfer translates to energy efficiency, a key factor to reducing carbon emissions of web products. The more efficient our products, the less electricity they use, and the less fossil fuels need to be burned to produce the electricity to power them. But as we’ll see next, since all web products demand some power, it’s important to consider the source of that electricity, too.


<h3>Carbon intensity of electricity</h3>


Regardless of energy efficiency, the level of pollution caused by digital products depends on the carbon intensity of the energy being used to power them. Carbon intensity is a term used to define the grams of CO2 produced for every kilowatt-hour of electricity (gCO2/kWh). This varies widely, with renewable energy sources and nuclear having <a href="https://www.carbonbrief.org/solar-wind-nuclear-amazingly-low-carbon-footprints">an extremely low carbon intensity</a> of less than 10 gCO2/kWh (even when factoring in their construction); whereas fossil fuels have <a href="https://www.volker-quaschning.de/datserv/CO2-spez/index_e.php">very high carbon intensity</a> of approximately 200–400 gCO2/kWh.


Most electricity comes from national or state grids, where energy from a variety of different sources is mixed together with varying levels of carbon intensity. The distributed nature of the internet means that a single user of a website or app might be using energy from multiple different grids simultaneously; a website user in Paris uses electricity from the French national grid to power their home internet and devices, but the website’s data center could be in Dallas, USA, pulling electricity from the Texas grid, while the telecoms networks use energy from everywhere between Dallas and Paris.


We don’t have control over the full energy supply of web services, but we do have some control over where we host our projects. With a data center using a significant proportion of the energy of any website, locating the data center in an area with low carbon energy will tangibly reduce its carbon emissions. Danish startup Tomorrow reports and <a href="https://www.electricitymap.org/map">maps this user-contributed data</a>, and a glance at their map shows how, for example, choosing a data center in France will have significantly lower carbon emissions than a data center in the Netherlands (Fig 2.3).


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/2-3.png" alt="" class="wp-image-7173079" /><figcaption>Fig 2.3: Tomorrow’s electricityMap shows live data for the carbon intensity of electricity by country.</figcaption></figure>


That said, we don’t want to locate our servers too far away from our users; it takes energy to transmit data through the telecom’s networks, and the further the data travels, the more energy is consumed. Just like food miles, we can think of the distance from the data center to the website’s core user base as “megabyte miles”—and we want it to be as small as possible.


Using the distance itself as a benchmark, we can use website analytics to identify the country, state, or even city where our core user group is located and measure the distance from that location to the data center used by our hosting company. This will be a somewhat fuzzy metric as we don’t know the precise center of mass of our users or the exact location of a data center, but we can at least get a rough idea. 


For example, if a website is hosted in London but the primary user base is on the West Coast of the USA, then we could look up the distance from London to San Francisco, which is 5,300 miles. That’s a long way! We can see that hosting it somewhere in North America, ideally on the West Coast, would significantly reduce the distance and thus the energy used to transmit the data. In addition, locating our servers closer to our visitors helps reduce latency and delivers better user experience, so it’s a win-win.


<h3>Converting it back to carbon emissions</h3>


If we combine carbon intensity with a calculation for energy consumption, we can calculate the carbon emissions of our websites and apps. A tool my team created does this by measuring the data transfer over the wire when loading a web page, calculating the amount of electricity associated, and then converting that into a figure for CO2 (Fig 2.4). It also factors in whether or not the web hosting is powered by renewable energy.


If you want to take it to the next level and tailor the data more accurately to the unique aspects of your project, the <a href="https://docs.google.com/spreadsheets/d/1gQeUwNFHp7ck4AS7r-d_EwfriM-UFoQ6ApBek9n-hqo/edit#gid=1896136078">Energy and Emissions Worksheet</a> accompanying this book shows you how.


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/2-4.png" alt="" class="wp-image-7173080" /><figcaption>Fig 2.4: The <a href="https://www.websitecarbon.com">Website Carbon Calculator</a> shows how the Riverford Organic website embodies their commitment to sustainability, being both low carbon and hosted in a data center using renewable energy.</figcaption></figure>


With the ability to calculate carbon emissions for our projects, we could actually take a page weight budget one step further and set carbon budgets as well. CO2 is not a metric commonly used in web projects; we’re more familiar with kilobytes and megabytes, and can fairly easily look at design options and files to assess how big they are. Translating that into carbon adds a layer of abstraction that isn’t as intuitive—but carbon budgets do focus our minds on the primary thing we’re trying to reduce, and support the core objective of sustainable web design: reducing carbon emissions.


<h3>Browser Energy</h3>


Data transfer might be the simplest and most complete analog for energy consumption in our digital projects, but by giving us one number to represent the energy used in the data center, the telecoms networks, and the end user’s devices, it can’t offer us insights into the efficiency in any specific part of the system.


One part of the system we can look at in more detail is the energy used by end users’ devices. As front-end web technologies become more advanced, the computational load is increasingly moving from the data center to users’ devices, whether they be phones, tablets, laptops, desktops, or even smart TVs. Modern web browsers allow us to implement more complex styling and animation on the fly using CSS and JavaScript. Furthermore, JavaScript libraries such as Angular and React allow us to create applications where the “thinking” work is done partly or entirely in the browser.


All of these advances are exciting and open up new possibilities for what the web can do to serve society and create positive experiences. However, more computation in the user’s web browser means more energy used by their devices. This has implications not just environmentally, but also for user experience and inclusivity. Applications that put a heavy processing load on the user’s device can inadvertently exclude users with older, slower devices and cause batteries on phones and laptops to drain faster. Furthermore, if we build web applications that require the user to have up-to-date, powerful devices, people throw away old devices much more frequently. This isn’t just bad for the environment, but it puts a disproportionate financial burden on the poorest in society.


In part because the tools are limited, and partly because there are so many different models of devices, it’s difficult to measure website energy consumption on end users’ devices. One tool we do currently have is the Energy Impact monitor inside the developer console of the Safari browser (Fig 2.5).


<figure class="wp-block-image size-full"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/08/2-5.png" alt="" class="wp-image-7173081" /><figcaption>Fig 2.5: The Energy Impact meter in Safari (on the right) shows how a website consumes CPU energy.</figcaption></figure>


You know when you load a website and your computer’s cooling fans start spinning so frantically you think it might actually take off? That’s essentially what this tool is measuring. 


It shows us the percentage of CPU used and the duration of CPU usage when loading the web page, and uses these figures to generate an energy impact rating. It doesn’t give us precise data for the amount of electricity used in kilowatts, but the information it does provide can be used to benchmark how efficiently your websites use energy and set targets for improvement.
]]> </description>
<dc:subject>
<![CDATA[Design, Web Strategy]]> </dc:subject>
<dc:date>
2021-08-05T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Voice Content and Usability]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/preston-so/">Preston So</a> </author>
<link>
https://alistapart.com/article/voice-content-and-usability/ </link>
<guid>
https://alistapart.com/article/voice-content-and-usability/ </guid>
<description>
<![CDATA[
We’ve been having conversations for thousands of years. Whether to convey information, conduct transactions, or simply to check in on one another, people have yammered away, chattering and gesticulating, through spoken conversation for countless generations. Only in the last few millennia have we begun to commit our conversations to writing, and only in the last few decades have we begun to outsource them to the computer, a machine that shows much more affinity for written correspondence than for the slangy vagaries of spoken language.


Computers have trouble because between spoken and written language, speech is more primordial. To have successful conversations with us, machines must grapple with the messiness of human speech: the disfluencies and pauses, the gestures and body language, and the variations in word choice and spoken dialect that can stymie even the most carefully crafted human-computer interaction. In the human-to-human scenario, spoken language also has the privilege of face-to-face contact, where we can readily interpret nonverbal social cues.


In contrast, written language immediately concretizes as we commit it to record and retains usages long after they become obsolete in spoken communication (the salutation “To whom it may concern,” for example), generating its own fossil record of outdated terms and phrases. Because it tends to be more consistent, polished, and formal, written text is fundamentally much easier for machines to parse and understand.


Spoken language has no such luxury. Besides the nonverbal cues that decorate conversations with emphasis and emotional context, there are also verbal cues and vocal behaviors that modulate conversation in nuanced ways: how something is said, not what. Whether rapid-fire, low-pitched, or high-decibel, whether sarcastic, stilted, or sighing, our spoken language conveys much more than the written word could ever muster. So when it comes to voice interfaces—the machines we conduct spoken conversations with—we face exciting challenges as designers and content strategists.


<h2 id="E1287">Voice Interactions</h2>


We interact with voice interfaces for a variety of reasons, but according to Michael McTear, Zoraida Callejas, and David Griol in The Conversational Interface, those motivations by and large mirror the reasons we initiate conversations with other people, too (<a is="qowt-hyperlink" href="http://bkaprt.com/vcu36/01-01" target="_blank" rel="noreferrer noopener">http://bkaprt.com/vcu36/01-01</a>). Generally, we start up a conversation because:


<ul><li>we need something done (such as a transaction),</li><li>we want to know something (information of some sort), or</li><li>we are social beings and want someone to talk to (conversation for conversation’s sake).</li></ul>


These three categories—which I call transactional, informational, and prosocial—also characterize essentially every voice interaction: a single conversation from beginning to end that realizes some outcome for the user, starting with the voice interface’s first greeting and ending with the user exiting the interface. Note here that a conversation in our human sense—a chat between people that leads to some result and lasts an arbitrary length of time—could encompass multiple transactional, informational, and prosocial voice interactions in succession. In other words, a voice interaction is a conversation, but a conversation is not necessarily a single voice interaction.


Purely prosocial conversations are more gimmicky than captivating in most voice interfaces, because machines don’t yet have the capacity to really want to know how we’re doing and to do the sort of glad-handing humans crave. There’s also ongoing debate as to whether users actually prefer the sort of organic human conversation that begins with a prosocial voice interaction and shifts seamlessly into other types. In fact, in Voice User Interface Design, Michael Cohen, James Giangola, and Jennifer Balogh recommend sticking to users’ expectations by mimicking how they interact with other voice interfaces rather than trying too hard to be human—potentially alienating them in the process (<a is="qowt-hyperlink" href="http://bkaprt.com/vcu36/01-01" target="_blank" rel="noreferrer noopener">http://bkaprt.com/vcu36/01-01</a>).


That leaves two genres of conversations we can have with one another that a voice interface can easily have with us, too: a transactional voice interaction realizing some outcome (“buy iced tea”) and an informational voice interaction teaching us something new (“discuss a musical”).


<h2 id="E1403">Transactional voice interactions</h2>


Unless you’re tapping buttons on a food delivery app, you’re generally having a conversation—and therefore a voice interaction—when you order a Hawaiian pizza with extra pineapple. Even when we walk up to the counter and place an order, the conversation quickly pivots from an initial smattering of neighborly small talk to the real mission at hand: ordering a pizza (generously topped with pineapple, as it should be).


<blockquote class="wp-block-quote">Alison: Hey, how’s it going?Burhan: Hi, welcome to Crust Deluxe! It’s cold out there. How can I help you?Alison: Can I get a Hawaiian pizza with extra pineapple?Burhan: Sure, what size?Alison: Large.Burhan: Anything else?Alison: No thanks, that’s it.Burhan: Something to drink?Alison: I’ll have a bottle of Coke.Burhan: You got it. That’ll be $13.55 and about fifteen minutes.</blockquote>


Each progressive disclosure in this transactional conversation reveals more and more of the desired outcome of the transaction: a service rendered or a product delivered. Transactional conversations have certain key traits: they’re direct, to the point, and economical. They quickly dispense with pleasantries.


<h2 id="E1471">Informational voice interactions</h2>


Meanwhile, some conversations are primarily about obtaining information. Though Alison might visit Crust Deluxe with the sole purpose of placing an order, she might not actually want to walk out with a pizza at all. She might be just as interested in whether they serve halal or kosher dishes, gluten-free options, or something else. Here, though we again have a prosocial mini-conversation at the beginning to establish politeness, we’re after much more.


<blockquote class="wp-block-quote">Alison: Hey, how’s it going?Burhan: Hi, welcome to Crust Deluxe! It’s cold out there. How can I help you?Alison: Can I ask a few questions?Burhan: Of course! Go right ahead.Alison: Do you have any halal options on the menu?Burhan: Absolutely! We can make any pie halal by request. We also have lots of vegetarian, ovo-lacto, and vegan options. Are you thinking about any other dietary restrictions?Alison: What about gluten-free pizzas?Burhan: We can definitely do a gluten-free crust for you, no problem, for both our deep-dish and thin-crust pizzas. Anything else I can answer for you?Alison: That’s it for now. Good to know. Thanks!Burhan: Anytime, come back soon!</blockquote>


This is a very different dialogue. Here, the goal is to get a certain set of facts. Informational conversations are investigative quests for the truth—research expeditions to gather data, news, or facts. Voice interactions that are informational might be more long-winded than transactional conversations by necessity. Responses tend to be lengthier, more informative, and carefully communicated so the customer understands the key takeaways.


<h2 id="E1560">Voice Interfaces</h2>


At their core, voice interfaces employ speech to support users in reaching their goals. But simply because an interface has a voice component doesn’t mean that every user interaction with it is mediated through voice. Because multimodal voice interfaces can lean on visual components like screens as crutches, we’re most concerned in this book with pure voice interfaces, which depend entirely on spoken conversation, lack any visual component whatsoever, and are therefore much more nuanced and challenging to tackle.


Though voice interfaces have long been integral to the imagined future of humanity in science fiction, only recently have those lofty visions become fully realized in genuine voice interfaces.


<h3 id="E1593">Interactive voice response (IVR) systems</h3>


Though written conversational interfaces have been fixtures of computing for many decades, voice interfaces first emerged in the early 1990s with text-to-speech (TTS) dictation programs that recited written text aloud, as well as speech-enabled in-car systems that gave directions to a user-provided address. With the advent of interactive voice response (IVR) systems, intended as an alternative to overburdened customer service representatives, we became acquainted with the first true voice interfaces that engaged in authentic conversation.


IVR systems allowed organizations to reduce their reliance on call centers but soon became notorious for their clunkiness. Commonplace in the corporate world, these systems were primarily designed as metaphorical switchboards to guide customers to a real phone agent (“Say Reservations to book a flight or check an itinerary”); chances are you will enter a conversation with one when you call an airline or hotel conglomerate. Despite their functional issues and users’ frustration with their inability to speak to an actual human right away, IVR systems proliferated in the early 1990s across a variety of industries (<a is="qowt-hyperlink" href="http://bkaprt.com/vcu36/01-02" target="_blank" rel="noreferrer noopener">http://bkaprt.com/vcu36/01-02</a>, PDF).


While IVR systems are great for highly repetitive, monotonous conversations that generally don’t veer from a single format, they have a reputation for less scintillating conversation than we’re used to in real life (or even in science fiction).


<h3 id="E1666">Screen readers</h3>


Parallel to the evolution of IVR systems was the invention of the screen reader, a tool that transcribes visual content into synthesized speech. For Blind or visually impaired website users, it’s the predominant method of interacting with text, multimedia, or form elements. Screen readers represent perhaps the closest equivalent we have today to an out-of-the-box implementation of content delivered through voice.


Among the first screen readers known by that moniker was the Screen Reader for the BBC Micro and NEEC Portable developed by the Research Centre for the Education of the Visually Handicapped (RCEVH) at the University of Birmingham in 1986 (<a is="qowt-hyperlink" href="http://bkaprt.com/vcu36/01-03" target="_blank" rel="noreferrer noopener">http://bkaprt.com/vcu36/01-03</a>). That same year, Jim Thatcher created the first IBM Screen Reader for text-based computers, later recreated for computers with graphical user interfaces (GUIs) (<a is="qowt-hyperlink" href="http://bkaprt.com/vcu36/01-04" target="_blank" rel="noreferrer noopener">http://bkaprt.com/vcu36/01-04</a>).


With the rapid growth of the web in the 1990s, the demand for accessible tools for websites exploded. Thanks to the introduction of semantic HTML and especially ARIA roles beginning in 2008, screen readers started facilitating speedy interactions with web pages that ostensibly allow disabled users to traverse the page as an aural and temporal space rather than a visual and physical one. In other words, screen readers for the web “provide mechanisms that translate visual design constructs—proximity, proportion, etc.—into useful information,” writes Aaron Gustafson in A List Apart. “At least they do when documents are authored thoughtfully” (<a is="qowt-hyperlink" rel="noreferrer noopener" href="http://bkaprt.com/vcu36/01-05" target="_blank">http://bkaprt.com/vcu36/01-05</a>).


Though deeply instructive for voice interface designers, there’s one significant problem with screen readers: they’re difficult to use and unremittingly verbose. The visual structures of websites and web navigation don’t translate well to screen readers, sometimes resulting in unwieldy pronouncements that name every manipulable HTML element and announce every formatting change. For many screen reader users, working with web-based interfaces exacts a cognitive toll.


In Wired, accessibility advocate and voice engineer Chris Maury considers why the screen reader experience is ill-suited to users relying on voice:


<blockquote class="wp-block-quote">From the beginning, I hated the way that Screen Readers work. Why are they designed the way they are? It makes no sense to present information visually and then, and only then, translate that into audio. All of the time and energy that goes into creating the perfect user experience for an app is wasted, or even worse, adversely impacting the experience for blind users. (<a is="qowt-hyperlink" rel="noreferrer noopener" href="http://bkaprt.com/vcu36/01-06" target="_blank">http://bkaprt.com/vcu36/01-06</a>)</blockquote>


In many cases, well-designed voice interfaces can speed users to their destination better than long-winded screen reader monologues. After all, visual interface users have the benefit of darting around the viewport freely to find information, ignoring areas irrelevant to them. Blind users, meanwhile, are obligated to listen to every utterance synthesized into speech and therefore prize brevity and efficiency. Disabled users who have long had no choice but to employ clunky screen readers may find that voice interfaces, particularly more modern voice assistants, offer a more streamlined experience.


<h3 id="E1775">Voice assistants</h3>


When we think of voice assistants (the subset of voice interfaces now commonplace in living rooms, smart homes, and offices), many of us immediately picture HAL from 2001: A Space Odyssey or hear Majel Barrett’s voice as the omniscient computer in Star Trek. Voice assistants are akin to personal concierges that can answer questions, schedule appointments, conduct searches, and perform other common day-to-day tasks. And they’re rapidly gaining more attention from accessibility advocates for their assistive potential.


Before the earliest IVR systems found success in the enterprise, Apple published a demonstration video in 1987 depicting the Knowledge Navigator, a voice assistant that could transcribe spoken words and recognize human speech to a great degree of accuracy. Then, in 2001, Tim Berners-Lee and others formulated their vision for a Semantic Web “agent” that would perform typical errands like “checking calendars, making appointments, and finding locations” (<a is="qowt-hyperlink" href="http://bkaprt.com/vcu36/01-07" target="_blank" rel="noreferrer noopener">http://bkaprt.com/vcu36/01-07</a>, behind paywall). It wasn’t until 2011 that Apple’s Siri finally entered the picture, making voice assistants a tangible reality for consumers.


Thanks to the plethora of voice assistants available today, there is considerable variation in how programmable and customizable certain voice assistants are over others (Fig 1.1). At one extreme, everything except vendor-provided features is locked down; for example, at the time of their release, the core functionality of Apple’s Siri and Microsoft’s Cortana couldn’t be extended beyond their existing capabilities. Even today, it isn’t possible to program Siri to perform arbitrary functions, because there’s no means by which developers can interact with Siri at a low level, apart from predefined categories of tasks like sending messages, hailing rideshares, making restaurant reservations, and certain others.


At the opposite end of the spectrum, voice assistants like Amazon Alexa and Google Home offer a core foundation on which developers can build custom voice interfaces. For this reason, programmable voice assistants that lend themselves to customization and extensibility are becoming increasingly popular for developers who feel stifled by the limitations of Siri and Cortana. Amazon offers the Alexa Skills Kit, a developer framework for building custom voice interfaces for Amazon Alexa, while Google Home offers the ability to program arbitrary Google Assistant skills. Today, users can choose from among thousands of custom-built skills within both the Amazon Alexa and Google Assistant ecosystems.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/1.1-Voice-assistant-programmability.png?resize=1024,550" alt="" class="wp-image-7173070"/><figcaption>Fig 1.1: Voice assistants like Amazon Alexa and Google Home tend to be more programmable, and thus more flexible, than their counterpart Apple Siri.</figcaption></figure>


As corporations like Amazon, Apple, Microsoft, and Google continue to stake their territory, they’re also selling and open-sourcing an unprecedented array of tools and frameworks for designers and developers that aim to make building voice interfaces as easy as possible, even without code.


Often by necessity, voice assistants like Amazon Alexa tend to be monochannel—they’re tightly coupled to a device and can’t be accessed on a computer or smartphone instead. By contrast, many development platforms like Google’s Dialogflow have introduced omnichannel capabilities so users can build a single conversational interface that then manifests as a voice interface, textual chatbot, and IVR system upon deployment. I don’t prescribe any specific implementation approaches in this design-focused book, but in Chapter 4 we’ll get into some of the implications these variables might have on the way you build out your design artifacts.


<h2 id="E1952">Voice Content</h2>


Simply put, voice content is content delivered through voice. To preserve what makes human conversation so compelling in the first place, voice content needs to be free-flowing and organic, contextless and concise—everything written content isn’t.


Our world is replete with voice content in various forms: screen readers reciting website content, voice assistants rattling off a weather forecast, and automated phone hotline responses governed by IVR systems. In this book, we’re most concerned with content delivered auditorily—not as an option, but as a necessity.


For many of us, our first foray into informational voice interfaces will be to deliver content to users. There’s only one problem: any content we already have isn’t in any way ready for this new habitat. So how do we make the content trapped on our websites more conversational? And how do we write new copy that lends itself to voice interactions?


Lately, we’ve begun slicing and dicing our content in unprecedented ways. Websites are, in many respects, colossal vaults of what I call macrocontent: lengthy prose that can extend for infinitely scrollable miles in a browser window, like microfilm viewers of newspaper archives. Back in 2002, well before the present-day ubiquity of voice assistants, technologist Anil Dash defined microcontent as permalinked pieces of content that stay legible regardless of environment, such as email or text messages:


<blockquote class="wp-block-quote">A day’s weather forcast [sic], the arrival and departure times for an airplane flight, an abstract from a long publication, or a single instant message can all be examples of microcontent. (<a is="qowt-hyperlink" rel="noreferrer noopener" href="http://bkaprt.com/vcu36/01-08" target="_blank">http://bkaprt.com/vcu36/01-08</a>)</blockquote>


I’d update Dash’s definition of microcontent to include all examples of bite-sized content that go well beyond written communiqués. After all, today we encounter microcontent in interfaces where a small snippet of copy is displayed alone, unmoored from the browser, like a textbot confirmation of a restaurant reservation. Microcontent offers the best opportunity to gauge how your content can be stretched to the very edges of its capabilities, informing delivery channels both established and novel.


As microcontent, voice content is unique because it’s an example of how content is experienced in time rather than in space. We can glance at a digital sign underground for an instant and know when the next train is arriving, but voice interfaces hold our attention captive for periods of time that we can’t easily escape or skip, something screen reader users are all too familiar with.


Because microcontent is fundamentally made up of isolated blobs with no relation to the channels where they’ll eventually end up, we need to ensure that our microcontent truly performs well as voice content—and that means focusing on the two most important traits of robust voice content: voice content legibility and voice content discoverability.


Fundamentally, the legibility and discoverability of our voice content both have to do with how voice content manifests in perceived time and space.
]]> </description>
<dc:subject>
<![CDATA[Content, Usability, User Experience]]> </dc:subject>
<dc:date>
2021-07-29T13:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Designing for the Unexpected]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/cathydutton/">Cathy Dutton</a> </author>
<link>
https://alistapart.com/article/designing-for-the-unexpected/ </link>
<guid>
https://alistapart.com/article/designing-for-the-unexpected/ </guid>
<description>
<![CDATA[
I’m not sure when I first heard this quote, but it’s something that has stayed with me over the years. How do you create services for situations you can’t imagine? Or design products that work on devices yet to be invented?


<h2>Flash, Photoshop, and responsive design</h2>


When I first started designing websites, my go-to software was Photoshop. I created a 960px canvas and set about creating a layout that I would later drop content in. The development phase was about attaining pixel-perfect accuracy using fixed widths, fixed heights, and absolute positioning.


Ethan Marcotte’s talk at An Event Apart and subsequent article “<a href="https://alistapart.com/article/responsive-web-design/">Responsive Web Design</a>” in A List Apart in 2010 changed all this. I was sold on responsive design as soon as I heard about it, but I was also terrified. The pixel-perfect designs full of magic numbers that I had previously prided myself on producing were no longer good enough.


The fear wasn’t helped by my first experience with responsive design. My first project was to take an existing fixed-width website and make it responsive. What I learned the hard way was that you can’t just add responsiveness at the end of a project. To create fluid layouts, you need to plan throughout the design phase.


<h3>A new way to design</h3>


Designing responsive or fluid sites has always been about removing limitations, producing content that can be viewed on any device. It relies on the use of percentage-based layouts, which I initially achieved with native CSS and utility classes:


<pre><code class="language-css">.column-span-6 {
width: 49%;
float: left;
margin-right: 0.5%;
margin-left: 0.5%;
}
.column-span-4 {
width: 32%;
float: left;
margin-right: 0.5%;
margin-left: 0.5%;
}
.column-span-3 {
width: 24%;
float: left;
margin-right: 0.5%;
margin-left: 0.5%;
}</code></pre>


Then with Sass so I could take advantage of @includes to re-use repeated blocks of code and move back to more semantic markup:


<pre><code class="language-css">.logo {
@include colSpan(6);
}
.search {
@include colSpan(3);
}
.social-share {
@include colSpan(3);
}</code></pre>


<h3>Media queries</h3>


The second ingredient for responsive design is media queries. Without them, content would shrink to fit the available space regardless of whether that content remained readable (The exact opposite problem occurred with the introduction of a mobile-first approach).


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image5.png?w=652" alt="Wireframes showing three boxes at a large size, and three very narrow boxes at a mobile size" class="wp-image-7173046"/><figcaption>Components becoming too small at mobile breakpoints</figcaption></figure>


Media queries prevented this by allowing us to add breakpoints where the design could adapt. Like most people, I started out with three breakpoints: one for desktop, one for tablets, and one for mobile. Over the years, I added more and more for phablets, wide screens, and so on. 


For years, I happily worked this way and improved both my design and front-end skills in the process. The only problem I encountered was making changes to content, since with our Sass grid system in place, there was no way for the site owners to add content without amending the markup—something a small business owner might struggle with. This is because each row in the grid was defined using a <code>div</code> as a container. Adding content meant creating new row markup, which requires a level of HTML knowledge.


Row markup was a staple of early responsive design, present in all the widely used frameworks like Bootstrap and Skeleton.


<pre><code class="language-markup"><section class="row">
<div class="column-span-4">1 of 7</div>
<div class="column-span-4">2 of 7</div>
<div class="column-span-4">3 of 7</div>
</section>
<section class="row">
<div class="column-span-4">4 of 7</div>
<div class="column-span-4">5 of 7</div>
<div class="column-span-4">6 of 7</div>
</section>
<section class="row">
<div class="column-span-4">7 of 7</div>
</section></code></pre>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image10.png?w=451" alt="Wireframe showing three rows of boxes" class="wp-image-7173051"/><figcaption>Components placed in the rows of a Sass grid</figcaption></figure>


Another problem arose as I moved from a design agency building websites for small- to medium-sized businesses, to larger in-house teams where I worked across a suite of related sites. In those roles I started to work much more with reusable components. 


Our reliance on media queries resulted in components that were tied to common viewport sizes. If the goal of component libraries is reuse, then this is a real problem because you can only use these components if the devices you’re designing for correspond to the viewport sizes used in the pattern library—in the process not really hitting that “devices that don’t yet exist”  goal.


Then there’s the problem of space. Media queries allow components to adapt based on the viewport size, but what if I put a component into a sidebar, like in the figure below?


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image8.png?w=960" alt="Wireframes showing different configurations of boxes at three different sizes" class="wp-image-7173049"/><figcaption>Components responding to the viewport width with media queries</figcaption></figure>


<h3>Container queries: our savior or a false dawn?</h3>


Container queries have long been touted as an improvement upon media queries, but at the time of writing are unsupported in most browsers. There are JavaScript workarounds, but they can create dependency and compatibility issues. The basic theory underlying container queries is that elements should change based on the size of their parent container and not the viewport width, as seen in the following illustrations.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image11.png?w=951" alt="Wireframes showing different configurations of boxes at different sizes" class="wp-image-7173052"/><figcaption>Components responding to their parent container with container queries</figcaption></figure>


One of the biggest arguments in favor of container queries is that they help us create components or design patterns that are truly reusable because they can be picked up and placed anywhere in a layout. This is an important step in moving toward a form of component-based design that works at any size on any device.


In other words, responsive components to replace responsive layouts.


Container queries will help us move from designing pages that respond to the browser or device size to designing components that can be placed in a sidebar or in the main content, and respond accordingly.


My concern is that we are still using layout to determine when a design needs to adapt. This approach will always be restrictive, as we will still need pre-defined breakpoints. For this reason, my main question with container queries is, How would we decide when to change the CSS used by a component? 


A component library removed from context and real content is probably not the best place for that decision. 


As the diagrams below illustrate, we can use container queries to create designs for specific container widths, but what if I want to change the design based on the image size or ratio?


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image4.png?w=905" alt="Wireframes showing different layouts at 600px and 400px" class="wp-image-7173045"/><figcaption>Cards responding to their parent container with container queries</figcaption></figure>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image7.png?w=960" alt="Wireframes showing different configurations of content at the same size" class="wp-image-7173048"/><figcaption>Cards responding based on their own content</figcaption></figure>


In this example, the dimensions of the container are not what should dictate the design; rather, the image is.


It’s hard to say for sure whether container queries will be a success story until we have solid cross-browser support for them. Responsive component libraries would definitely evolve how we design and would improve the possibilities for reuse and design at scale. But maybe we will always need to adjust these components to suit our content.


<h3>CSS is changing</h3>


Whilst the container query debate rumbles on, there have been numerous advances in CSS that change the way we think about design. The days of fixed-width elements measured in pixels and floated <code>div</code> elements used to cobble layouts together are long gone, consigned to history along with table layouts. Flexbox and CSS Grid have revolutionized layouts for the web. We can now create elements that wrap onto new rows when they run out of space, not when the device changes.


<pre><code class="language-css">.wrapper {
display: grid;
grid-template-columns: repeat(auto-fit, 450px);
gap: 10px;
}</code></pre>


The <code>repeat()</code> function paired with <code>auto-fit</code> or <code>auto-fill</code> allows us to specify how much space each column should use while leaving it up to the browser to decide when to spill the columns onto a new line. Similar things can be achieved with Flexbox, as elements can wrap over multiple rows and “flex” to fill available space. 


<pre><code class="language-css">.wrapper {
display: flex;
flex-wrap: wrap;
justify-content: space-between;
}
.child {
flex-basis: 32%;
margin-bottom: 20px;
}</code></pre>


The biggest benefit of all this is you don’t need to wrap elements in container rows. Without rows, content isn’t tied to page markup in quite the same way, allowing for removals or additions of content without additional development.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image13.png?w=451" alt="A wireframe showing seven boxes in a larger container" class="wp-image-7173054"/><figcaption>A traditional Grid layout without the usual row containers</figcaption></figure>


This is a big step forward when it comes to creating designs that allow for evolving content, but the real game changer for flexible designs is CSS Subgrid. 


Remember the days of crafting perfectly aligned interfaces, only for the customer to add an unbelievably long header almost as soon as they're given CMS access, like the illustration below?


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image1.png?w=932" alt="" class="wp-image-7173042"/><figcaption>Cards unable to respond to a sibling’s content changes</figcaption></figure>


Subgrid allows elements to respond to adjustments in their own content and in the content of sibling elements, helping us create designs more resilient to change.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image9.png?w=932" alt="Wireframes showing several boxes with the contents aligned across boxes" class="wp-image-7173050"/><figcaption>Cards responding to content in sibling cards</figcaption></figure>


<pre><code class="language-css">.wrapper {
display: grid;
grid-template-columns: repeat(auto-fit, minmax(150px, 1fr));
grid-template-rows: auto 1fr auto;
gap: 10px;
}
.sub-grid {
display: grid;
grid-row: span 3;
grid-template-rows: subgrid; /* sets rows to parent grid */
}</code></pre>


CSS Grid allows us to separate layout and content, thereby enabling flexible designs. Meanwhile, Subgrid allows us to create designs that can adapt in order to suit morphing content. Subgrid at the time of writing is only supported in Firefox but the above code can be implemented behind an @supports feature query. 


<h3>Intrinsic layouts </h3>


I’d be remiss not to mention <a href="https://aneventapart.com/news/post/designing-intrinsic-layouts-aea-video">intrinsic layouts</a>, the term created by Jen Simmons to describe a mixture of new and old CSS features used to create layouts that respond to available space. 


Responsive layouts have flexible columns using percentages. Intrinsic layouts, on the other hand, use the fr unit to create flexible columns that won’t ever shrink so much that they render the content illegible.


<code>fr</code> units is a way to say I want you to distribute the extra space in this way, but...don’t ever make it smaller than the content that’s inside of it.


—Jen Simmons, “Designing Intrinsic Layouts”


Intrinsic layouts can also utilize a mixture of fixed and flexible units, allowing the content to dictate the space it takes up.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image12.png?w=960" alt="A slide from a presentation showing two boxes with max content and one with auto" class="wp-image-7173053"/><figcaption>Slide from “Designing Intrinsic Layouts” by Jen Simmons</figcaption></figure>


What makes intrinsic design stand out is that it not only creates designs that can withstand future devices but also helps scale design without losing flexibility. Components and patterns can be lifted and reused without the prerequisite of having the same breakpoints or the same amount of content as in the previous implementation. 


We can now create designs that adapt to the space they have, the content within them, and the content around them. With an intrinsic approach, we can construct responsive components without depending on container queries.


<h3>Another 2010 moment?</h3>


This intrinsic approach should in my view be every bit as groundbreaking as responsive web design was ten years ago. For me, it’s another “everything changed” moment. 


But it doesn’t seem to be moving quite as fast; I haven’t yet had that same career-changing moment I had with responsive design, despite <a href="https://aneventapart.com/news/post/everything-you-know-about-web-design-just-changed-by-jen-simmons">the widely shared and brilliant talk</a> that brought it to my attention. 


One reason for that could be that I now work in a large organization, which is quite different from the design agency role I had in 2010. In my agency days, every new project was a clean slate, a chance to try something new. Nowadays, projects use existing tools and frameworks and are often improvements to existing websites with an existing codebase. 


Another could be that I feel more prepared for change now. In 2010 I was new to design in general; the shift was frightening and required a lot of learning. Also, an intrinsic approach isn’t exactly all-new; it’s about using existing skills and existing CSS knowledge in a different way. 


<h3>You can’t framework your way out of a content problem</h3>


Another reason for the slightly slower adoption of intrinsic design could be the lack of quick-fix framework solutions available to kick-start the change. 


Responsive grid systems were all over the place ten years ago. With a framework like Bootstrap or Skeleton, you had a responsive design template at your fingertips.


Intrinsic design and frameworks do not go hand in hand quite so well because the benefit of having a selection of units is a hindrance when it comes to creating layout templates. The beauty of intrinsic design is combining different units and experimenting with techniques to get the best for your content.


And then there are design tools. We probably all, at some point in our careers, used Photoshop templates for desktop, tablet, and mobile devices to drop designs in and show how the site would look at all three stages.


How do you do that now, with each component responding to content and layouts flexing as and when they need to? This type of design must happen in the browser, which personally I’m a big fan of. 


The debate about “whether designers should code” is another that has rumbled on for years. When designing a digital product, we should, at the very least, design for a best- and worst-case scenario when it comes to content. To do this in a graphics-based software package is far from ideal. In code, we can add longer sentences, more radio buttons, and extra tabs, and watch in real time as the design adapts. Does it still work? Is the design too reliant on the current content?


Personally, I look forward to the day intrinsic design is the standard for design, when a design component can be truly flexible and adapt to both its space and content with no reliance on device or container dimensions.


<h2>Content first </h2>


Content is not constant. After all, to design for the unknown or unexpected we need to account for content changes like our earlier Subgrid card example that allowed the cards to respond to adjustments to their own content and the content of sibling elements.


Thankfully, there’s more to CSS than layout, and plenty of properties and values can help us put content first. Subgrid and pseudo-elements like <code>::first-line</code> and <code>::first-letter</code> help to separate design from markup so we can create designs that allow for changes.


Instead of old markup hacks like this—


<pre><code class="language-markup">
First line of text with different styling...
</code></pre>


—we can target content based on where it appears.


<pre><code class="language-css">.element::first-line {
font-size: 1.4em;
}
.element::first-letter {
color: red;
}</code></pre>


Much bigger additions to CSS include l<a href="https://www.w3.org/TR/css-logical-1/">ogical properties, which </a>change the way we construct designs using logical dimensions (start and end) instead of physical ones (left and right), something CSS Grid also does with functions like <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/min()"><code>min()</code></a>, <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/max()"><code>max()</code></a><code>,</code> and <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/clamp()"><code>clamp()</code></a>.


This flexibility allows for directional changes according to content, a common requirement when we need to present content in multiple languages. In the past, this was often achieved with Sass mixins but was often limited to switching from left-to-right to right-to-left orientation.


In the Sass version, directional variables need to be set.


<pre><code class="language-css">$direction: rtl;
$opposite-direction: ltr;
$start-direction: right;
$end-direction: left;</code></pre>


These variables can be used as values—


<pre><code class="language-css">body {
direction: $direction;
text-align: $start-direction;
}</code></pre>


—or as properties.


<pre><code class="language-css">margin-#{$end-direction}: 10px;
padding-#{$start-direction}: 10px;</code></pre>


However, now we have native logical properties, removing the reliance on both Sass (or a similar tool) and pre-planning that necessitated using variables throughout a codebase. These properties also start to break apart the tight coupling between a design and strict physical dimensions, creating more flexibility for changes in language and in direction.


<pre><code class="language-css">margin-block-end: 10px;
padding-block-start: 10px;</code></pre>


There are also native start and end values for properties like <code>text-align</code>, which means we can replace <code>text-align: right</code> with <code>text-align: start</code>.


Like the earlier examples, these properties help to build out designs that aren’t constrained to one language; the design will reflect the content’s needs.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image14.png?w=960" alt="Wireframe showing different text alignment options" class="wp-image-7173055"/></figure>


<h3>Fixed and fluid </h3>


We briefly covered the power of combining fixed widths with fluid widths with intrinsic layouts. The <code>min()</code> and <code>max()</code> functions are a similar concept, allowing you to specify a fixed value with a flexible alternative. 


For <code>min()</code> this means setting a fluid minimum value and a maximum fixed value.


<pre><code class="language-css">.element {
width: min(50%, 300px);
}</code></pre>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image6.png?w=960" alt="Wireframe showing a 300px box inside of an 800px box, and a 200px box inside of a 400px box" class="wp-image-7173047"/></figure>


The element in the figure above will be 50% of its container as long as the element’s width doesn’t exceed 300px.


For <code>max()</code> we can set a flexible max value and a minimum fixed value.


<pre><code class="language-css">.element {
width: max(50%, 300px);
}</code></pre>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image3.png?w=960" alt="Wireframe showing a 400px box inside of an 800px box, and a 300px box inside of a 400px box" class="wp-image-7173044"/></figure>


Now the element will be 50% of its container as long as the element’s width is at least 300px. This means we can set limits but allow content to react to the available space. 


The <code>clamp()</code> function builds on this by allowing us to set a preferred value with a third parameter. Now we can allow the element to shrink or grow if it needs to without getting to a point where it becomes unusable.


<pre><code class="language-css">.element {
width: clamp(300px, 50%, 600px);
}</code></pre>


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/07/image2.png?w=960" alt="Wireframe showing an 800px box inside of a 1400px box, a 400px box inside of an 800px box, and a 300px box inside of a 400px box" class="wp-image-7173043"/></figure>


This time, the element’s width will be 50% (the preferred value) of its container but never less than 300px and never more than 600px.


With these techniques, we have a content-first approach to responsive design. We can separate content from markup, meaning the changes users make will not affect the design. We can start to future-proof designs by planning for unexpected changes in language or direction. And we can increase flexibility by setting desired dimensions alongside flexible alternatives, allowing for more or less content to be displayed correctly.


<h2>Situation first</h2>


Thanks to what we’ve discussed so far, we can cover device flexibility by changing our approach, designing around content and space instead of catering to devices. But what about that last bit of Jeffrey Zeldman’s quote, “...situations you haven’t imagined”?


It’s a very different thing to design for someone seated at a desktop computer as opposed to someone using a mobile phone and moving through a crowded street in glaring sunshine. Situations and environments are hard to plan for or predict because they change as people react to their own unique challenges and tasks.


This is why choice is so important. One size never fits all, so we need to design for multiple scenarios to create equal experiences for all our users.


Thankfully, there is a lot we can do to provide choice.


<h3>Responsible design </h3>


<blockquote class="wp-block-quote">“There are parts of the world where mobile data is prohibitively expensive, and where there is little or no broadband infrastructure.”“<a href="https://www.smashingmagazine.com/2019/07/web-on-50mb-budget/">I Used the Web for a Day on a 50 MB Budget</a>”Chris Ashton</blockquote>


One of the biggest assumptions we make is that people interacting with our designs have a good wifi connection and a wide screen monitor. But in the real world, our users may be commuters traveling on trains or other forms of transport using smaller mobile devices that can experience drops in connectivity. There is nothing more frustrating than a web page that won’t load, but there are ways we can help users use less data or deal with sporadic connectivity.


The <a href="https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/srcset"><code>srcset</code></a> attribute allows the browser to decide which image to serve. This means we can create smaller ‘cropped’ images to display on mobile devices in turn using less bandwidth and less data.


<pre><code class="language-markup"><img
src="image-file.jpg"
srcset="large.jpg 1024w,
medium.jpg 640w,
small.jpg 320w"
alt="Image alt text" /></code></pre>


The <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types/preload"><code>preload</code></a> attribute can also help us to think about how and when media is downloaded. It can be used to tell a browser about any critical assets that need to be downloaded with high priority, improving perceived performance and the user experience. 


<pre><code class="language-markup"><link rel="stylesheet" href="style.css"> 
<link rel="preload" href="style.css" as="style"> </code></pre>


There’s also native <a href="https://developer.mozilla.org/en-US/docs/Web/Performance/Lazy_loading">lazy loading</a>, which indicates assets that should only be downloaded when they are needed.


<pre><code class="language-markup"><img src="image.png" loading="lazy" alt="…"></code></pre>


With <code>srcset</code>, <code>preload</code>, and lazy loading, we can start to tailor a user’s experience based on the situation they find themselves in. What none of this does, however, is allow the user themselves to decide what they want downloaded, as the decision is usually the browser’s to make. 


So how can we put users in control?


<h3>The return of media queries </h3>


Media queries have always been about much more than device sizes. They allow content to adapt to different situations, with screen size being just one of them.


We’ve long been able to check for media types like print and speech and features such as hover, resolution, and color. These checks allow us to provide options that suit more than one scenario; it’s less about one-size-fits-all and more about serving adaptable content. 


As of this writing, the <a href="https://www.w3.org/TR/mediaqueries-5/">Media Queries Level 5 spec</a> is still under development. It introduces some really exciting queries that in the future will help us design for multiple other unexpected situations.


For example, there’s a light-level feature that allows you to modify styles if a user is in sunlight or darkness. Paired with <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/--*">custom properties</a>, these features allow us to quickly create designs or themes for specific environments.


<pre><code class="language-css">@media (light-level: normal) {
--background-color: #fff;
--text-color: #0b0c0c;
}
@media (light-level: dim) {
--background-color: #efd226;
--text-color: #0b0c0c;
}</code></pre>


Another key feature of the Level 5 spec is personalization. Instead of creating designs that are the same for everyone, users can choose what works for them. This is achieved by using features like <code>prefers-reduced-data</code>, <code>prefers-color-scheme</code>, and <code>prefers-reduced-motion</code>, the latter two of which already enjoy broad browser support. These features tap into preferences set via the operating system or browser so people don’t have to spend time making each site they visit more usable.


Media queries like this go beyond choices made by a browser to grant more control to the user.


<h2>Expect the unexpected</h2>


In the end, the one thing we should always expect is for things to change. Devices in particular change faster than we can keep up, with foldable screens already on the market.


We can’t design the same way we have for this ever-changing landscape, but we can design for content. By putting content first and allowing that content to adapt to whatever space surrounds it, we can create more robust, flexible designs that increase the longevity of our products. 


A lot of the CSS discussed here is about moving away from layouts and putting content at the heart of design. From responsive components to fixed and fluid units, there is so much more we can do to take a more intrinsic approach. Even better, we can test these techniques during the design phase by designing in-browser and watching how our designs adapt in real-time.


When it comes to unexpected situations, we need to make sure our products are usable when people need them, whenever and wherever that might be. We can move closer to achieving this by involving users in our design decisions, by creating choice via browsers, and by giving control to our users with user-preference-based media queries. 


Good design for the unexpected should allow for change, provide choice, and give control to those we serve: our users themselves.
]]> </description>
<dc:subject>
<![CDATA[Design, Responsive Design]]> </dc:subject>
<dc:date>
2021-07-15T13:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Asynchronous Design Critique: Getting Feedback]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/erin-casali/">Erin Casali</a> </author>
<link>
https://alistapart.com/article/asynchronous-design-critique-giving-feedback-part2/ </link>
<guid>
https://alistapart.com/article/asynchronous-design-critique-giving-feedback-part2/ </guid>
<description>
<![CDATA[
“Any comment?” is probably one of the worst ways to ask for feedback. It’s vague and open ended, and it doesn’t provide any indication of what we’re looking for. Getting good feedback starts earlier than we might expect: it starts with the request. 


It might seem counterintuitive to start the process of receiving feedback with a question, but that makes sense if we realize that getting feedback can be thought of as a form of design research. In the same way that we wouldn’t do any research without the right questions to get the insights that we need, the best way to ask for feedback is also to craft sharp questions.


Design critique is not a one-shot process. Sure, any good feedback workflow continues until the project is finished, but this is particularly true for design because design work continues iteration after iteration, from a high level to the finest details. Each level needs its own set of questions.


And finally, as with any good research, we need to review what we got back, get to the core of its insights, and take action. Question, iteration, and review. Let’s look at each of those.


<h2>The question</h2>


Being open to feedback is essential, but we need to be precise about what we’re looking for. Just saying “Any comment?”, “What do you think?”, or “I’d love to get your opinion” at the end of a presentation—whether it’s in person, over video, or through a written post—is likely to get a number of varied opinions or, even worse, get everyone to follow the direction of the first person who speaks up. And then... we get frustrated because vague questions like those can turn a high-level flows review into people instead commenting on the borders of buttons. Which might be a hearty topic, so it might be hard at that point to redirect the team to the subject that you had wanted to focus on.


But how do we get into this situation? It’s a mix of factors. One is that we don’t usually consider asking as a part of the feedback process. Another is how natural it is to just leave the question implied, expecting the others to be on the same page. Another is that in nonprofessional discussions, there’s often no need to be that precise. In short, we tend to underestimate the importance of the questions, so we don’t work on improving them.


The act of asking good questions guides and focuses the critique. It’s also a form of consent: it makes it clear that you’re open to comments and what kind of comments you’d like to get. It puts people in the right mental state, especially in situations when they weren’t expecting to give feedback.


There isn’t a single best way to ask for feedback. It just needs to be specific, and specificity can take many shapes. A model for design critique that I’ve found particularly useful in my coaching is the one of stage versus depth.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/06/fig1.png?resize=1024,453" alt="A chart showing Depth on one axis and Stage on another axis, with Depth decreasing as Stage increases" class="wp-image-7173027"/></figure>


“Stage” refers to each of the steps of the process—in our case, the design process. In progressing from user research to the final design, the kind of feedback evolves. But within a single step, one might still review whether some assumptions are correct and whether there’s been a proper translation of the amassed feedback into updated designs as the project has evolved. A starting point for potential questions could derive from the <a href="http://www.jjg.net/elements/pdf/elements_ch02.pdf">layers of user experience</a>. What do you want to know: Project objectives? User needs? Functionality? Content? Interaction design? Information architecture? UI design? Navigation design? Visual design? Branding?


Here’re a few example questions that are precise and to the point that refer to different layers:


<ul><li>Functionality: Is automating account creation desirable?</li><li>Interaction design: Take a look through the updated flow and let me know whether you see any steps or error states that I might’ve missed.</li><li>Information architecture: We have two competing bits of information on this page. Is the structure effective in communicating them both?</li><li>UI design: What are your thoughts on the error counter at the top of the page that makes sure that you see the next error, even if the error is out of the viewport? </li><li>Navigation design: From research, we identified these second-level navigation items, but once you’re on the page, the list feels too long and hard to navigate. Are there any suggestions to address this?</li><li>Visual design: Are the sticky notifications in the bottom-right corner visible enough?</li></ul>


The other axis of specificity is about how deep you’d like to go on what’s being presented. For example, we might have introduced a new end-to-end flow, but there was a specific view that you found particularly challenging and you’d like a detailed review of that. This can be especially useful from one iteration to the next where it’s important to highlight the parts that have changed.


There are other things that we can consider when we want to achieve more specific—and more effective—questions.


A simple trick is to remove generic qualifiers from your questions like “good,” “well,” “nice,” “bad,” “okay,” and “cool.” For example, asking, “When the block opens and the buttons appear, is this interaction good?” might look specific, but you can spot the “good” qualifier, and convert it to an even better question: “When the block opens and the buttons appear, is it clear what the next action is?”


Sometimes we actually do want broad feedback. That’s rare, but it can happen. In that sense, you might still make it explicit that you’re looking for a wide range of opinions, whether at a high level or with details. Or maybe just say, “At first glance, what do you think?” so that it’s clear that what you’re asking is open ended but focused on someone’s impression after their first five seconds of looking at it.


Sometimes the project is particularly expansive, and some areas may have already been explored in detail. In these situations, it might be useful to explicitly say that some parts are already locked in and aren’t open to feedback. It’s not something that I’d recommend in general, but I’ve found it useful to avoid falling again into rabbit holes of the sort that might lead to further refinement but aren’t what’s most important right now.


Asking specific questions can completely change the quality of the feedback that you receive. People with less refined critique skills will now be able to offer more actionable feedback, and even expert designers will welcome the clarity and efficiency that comes from focusing only on what’s needed. It can save a lot of time and frustration.


<h2>The iteration</h2>


Design iterations are probably the most visible part of the design work, and they provide a natural checkpoint for feedback. Yet a lot of design tools with inline commenting tend to show changes as a single fluid stream in the same file, and those types of design tools make conversations disappear once they’re resolved, update shared UI components automatically, and compel designs to always show the latest version—unless these would-be helpful features were to be manually turned off. The implied goal that these design tools seem to have is to arrive at just one final copy with all discussions closed, probably because they inherited patterns from how written documents are collaboratively edited. That’s probably not the best way to approach design critiques, but even if I don’t want to be too prescriptive here: that could work for some teams.


The asynchronous design-critique approach that I find most effective is to create explicit checkpoints for discussion. I’m going to use the term iteration post for this. It refers to a write-up or presentation of the design iteration followed by a discussion thread of some kind. Any platform that can accommodate this structure can use this. By the way, when I refer to a “write-up or presentation,” I’m including video recordings or other media too: as long as it’s asynchronous, it works.


Using iteration posts has many advantages:


<ul><li>It creates a rhythm in the design work so that the designer can review feedback from each iteration and prepare for the next.</li><li>It makes decisions visible for future review, and conversations are likewise always available.</li><li>It creates a record of how the design changed over time.</li><li>Depending on the tool, it might also make it easier to collect feedback and act on it.</li></ul>


These posts of course don’t mean that no other feedback approach should be used, just that iteration posts could be the primary rhythm for a remote design team to use. And other feedback approaches (such as live critique, pair designing, or inline comments) can build from there.


I don’t think there’s a standard format for iteration posts. But there are a few high-level elements that make sense to include as a baseline:


<ol><li>The goal</li><li>The design</li><li>The list of changes</li><li>The questions</li></ol>


Each project is likely to have a goal, and hopefully it’s something that’s already been summarized in a single sentence somewhere else, such as the client brief, the product manager’s outline, or the project owner’s request. So this is something that I’d repeat in every iteration post—literally copy and pasting it. The idea is to provide context and to repeat what’s essential to make each iteration post complete so that there’s no need to find information spread across multiple posts. If I want to know about the latest design, the latest iteration post will have all that I need.


This copy-and-paste part introduces another relevant concept: alignment comes from repetition. So having posts that repeat information is actually very effective toward making sure that everyone is on the same page.


The design is then the actual series of information-architecture outlines, diagrams, flows, maps, wireframes, screens, visuals, and any other kind of design work that’s been done. In short, it’s any design artifact. For the final stages of work, I prefer the term blueprint to emphasize that I’ll be showing full flows instead of individual screens to make it easier to understand the bigger picture. 


It can also be useful to label the artifacts with clear titles because that can make it easier to refer to them. Write the post in a way that helps people understand the work. It’s not too different from organizing a good live presentation. 


For an efficient discussion, you should also include a bullet list of the changes from the previous iteration to let people focus on what’s new, which can be especially useful for larger pieces of work where keeping track, iteration after iteration, could become a challenge.


And finally, as noted earlier, it’s essential that you include a list of the questions to drive the design critique in the direction you want. Doing this as a numbered list can also help make it easier to refer to each question by its number.


Not all iterations are the same. Earlier iterations don’t need to be as tightly focused—they can be more exploratory and experimental, maybe even breaking some of the design-language guidelines to see what’s possible. Then later, the iterations start settling on a solution and refining it until the design process reaches its end and the feature ships.


I want to highlight that even if these iteration posts are written and conceived as checkpoints, by no means do they need to be exhaustive. A post might be a draft—just a concept to get a conversation going—or it could be a cumulative list of each feature that was added over the course of each iteration until the full picture is done.


Over time, I also started using specific labels for incremental iterations: i1, i2, i3, and so on. This might look like a minor labelling tip, but it can help in multiple ways:


<ul><li>Unique—It’s a clear unique marker. Within each project, one can easily say, “This was discussed in i4,” and everyone knows where they can go to review things.</li><li>Unassuming—It works like versions (such as v1, v2, and v3) but in contrast, versions create the impression of something that’s big, exhaustive, and complete. Iterations must be able to be exploratory, incomplete, partial.</li><li>Future proof—It resolves the “final” naming problem that you can run into with versions. No more files named “final final complete no-really-its-done.” Within each project, the largest number always represents the latest iteration.</li></ul>


To mark when a design is complete enough to be worked on, even if there might be some bits still in need of attention and in turn more iterations needed, the wording release candidate (RC) could be used to describe it: “with i8, we reached RC” or “i12 is an RC.”


<h2>The review</h2>


What usually happens during a design critique is an open discussion, with a back and forth between people that can be very productive. This approach is particularly effective during live, synchronous feedback. But when we work asynchronously, it’s more effective to use a different approach: we can shift to a user-research mindset. Written feedback from teammates, stakeholders, or others can be treated as if it were the result of user interviews and surveys, and we can analyze it accordingly.


This shift has some major benefits that make asynchronous feedback particularly effective, especially around these friction points:


<ol><li>It removes the pressure to reply to everyone.</li><li>It reduces the frustration from swoop-by comments.</li><li>It lessens our personal stake.</li></ol>


The first friction point is feeling a pressure to reply to every single comment. Sometimes we write the iteration post, and we get replies from our team. It’s just a few of them, it’s easy, and it doesn’t feel like a problem. But other times, some solutions might require more in-depth discussions, and the amount of replies can quickly increase, which can create a tension between trying to be a good team player by replying to everyone and doing the next design iteration. This might be especially true if the person who’s replying is a stakeholder or someone directly involved in the project who we feel that we need to listen to. We need to accept that this pressure is absolutely normal, and it’s human nature to try to accommodate people who we care about. Sometimes replying to all comments can be effective, but if we treat a design critique more like user research, we realize that we don’t have to reply to every comment, and in asynchronous spaces, there are alternatives:


<ul><li>One is to let the next iteration speak for itself. When the design evolves and we post a follow-up iteration, that’s the reply. You might tag all the people who were involved in the previous discussion, but even that’s a choice, not a requirement. </li><li>Another is to briefly reply to acknowledge each comment, such as “Understood. Thank you,” “Good points—I’ll review,” or “Thanks. I’ll include these in the next iteration.” In some cases, this could also be just a single top-level comment along the lines of “Thanks for all the feedback everyone—the next iteration is coming soon!”</li><li>Another is to provide a quick summary of the comments before moving on. Depending on your workflow, this can be particularly useful as it can provide a simplified checklist that you can then use for the next iteration.</li></ul>


The second friction point is the swoop-by comment, which is the kind of feedback that comes from someone outside the project or team who might not be aware of the context, restrictions, decisions, or requirements—or of the previous iterations’ discussions. On their side, there’s something that one can hope that they might learn: they could start to acknowledge that they’re doing this and they could be more conscious in outlining where they’re coming from. Swoop-by comments often trigger the simple thought “We’ve already discussed this…”, and it can be frustrating to have to repeat the same reply over and over.


Let’s begin by acknowledging again that there’s no need to reply to every comment. If, however, replying to a previously litigated point might be useful, a short reply with a link to the previous discussion for extra details is usually enough. Remember, alignment comes from repetition, so it’s okay to repeat things sometimes!


Swoop-by commenting can still be useful for two reasons: they might point out something that still isn’t clear, and they also have the potential to stand in for the point of view of a user who’s seeing the design for the first time. Sure, you’ll still be frustrated, but that might at least help in dealing with it.


The third friction point is the personal stake we could have with the design, which could make us feel defensive if the review were to feel more like a discussion. Treating feedback as user research helps us create a healthy distance between the people giving us feedback and our ego (because yes, even if we don’t want to admit it, it’s there). And ultimately, treating everything in aggregated form allows us to better prioritize our work.


Always remember that while you need to listen to stakeholders, project owners, and specific advice, you don’t have to accept every piece of feedback. You have to analyze it and make a decision that you can justify, but sometimes “no” is the right answer. 


As the designer leading the project, you’re in charge of that decision. Ultimately, everyone has their specialty, and as the designer, you’re the one who has the most knowledge and the most context to make the right decision. And by listening to the feedback that you’ve received, you’re making sure that it’s also the best and most balanced decision.


Thanks to Brie Anne Demkiw and Mike Shelton for reviewing the first draft of this article.
]]> </description>
<dc:subject>
<![CDATA[Design, Process, User Experience]]> </dc:subject>
<dc:date>
2021-07-01T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Asynchronous Design Critique: Giving Feedback]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/erin-casali/">Erin Casali</a> </author>
<link>
https://alistapart.com/article/async-design-critique-giving-feedback/ </link>
<guid>
https://alistapart.com/article/async-design-critique-giving-feedback/ </guid>
<description>
<![CDATA[
Feedback, in whichever form it takes, and whatever it may be called, is one of the most effective soft skills that we have at our disposal to collaboratively get our designs to a better place while growing our own skills and perspectives.


Feedback is also one of the most underestimated tools, and often by assuming that we’re already good at it, we settle, forgetting that it’s a skill that can be trained, grown, and improved. Poor feedback can create confusion in projects, bring down morale, and affect trust and team collaboration over the long term. Quality feedback can be a transformative force. 


Practicing our skills is surely a good way to improve, but the learning gets even faster when it’s paired with a good foundation that channels and focuses the practice. What are some foundational aspects of giving good feedback? And how can feedback be adjusted for remote and distributed work environments? 


On the web, we can identify a long tradition of asynchronous feedback: from the early days of open source, code was shared and discussed on mailing lists. Today, developers engage on pull requests, designers comment in their favorite design tools, project managers and scrum masters exchange ideas on tickets, and so on.


Design critique is often the name used for a type of feedback that’s provided to make our work better, collaboratively. So it shares a lot of the principles with feedback in general, but it also has some differences.


<h2>The content</h2>


The foundation of every good critique is the feedback’s content, so that’s where we need to start. There are many models that you can use to shape your content. The one that I personally like best—because it’s clear and actionable—is this one from <a href="https://larahogan.me/blog/feedback-equation/">Lara Hogan</a>.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/06/async-critique-feedback-equation.png?resize=1024,293" alt="An equation: Observation plus impact plus question equals actionable feedback." class="wp-image-7173014" /></figure>


While this equation is generally used to give feedback to people, it also fits really well in a design critique because it ultimately answers some of the core questions that we work on: What? Where? Why? How? Imagine that you’re giving some feedback about some design work that spans multiple screens, like an onboarding flow: there are some pages shown, a flow blueprint, and an outline of the decisions made. You spot something that could be improved. If you keep the three elements of the equation in mind, you’ll have a mental model that can help you be more precise and effective.


Here is a comment that could be given as a part of some feedback, and it might look reasonable at a first glance: it seems to superficially fulfill the elements in the equation. But does it?


<blockquote class="wp-block-quote">Not sure about the buttons’ styles and hierarchy—it feels off. Can you change them?</blockquote>


Observation for design feedback doesn’t just mean pointing out which part of the interface your feedback refers to, but it also refers to offering a perspective that’s as specific as possible. Are you providing the user’s perspective? Your expert perspective? A business perspective? The project manager’s perspective? A first-time user’s perspective?


<blockquote class="wp-block-quote">When I see these two buttons, I expect one to go forward and one to go back.</blockquote>


Impact is about the why. Just pointing out a UI element might sometimes be enough if the issue may be obvious, but more often than not, you should add an explanation of what you’re pointing out.


<blockquote class="wp-block-quote">When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow.</blockquote>


The question approach is meant to provide open guidance by eliciting the critical thinking in the designer receiving the feedback. Notably, in Lara’s equation she provides a second approach: request, which instead provides guidance toward a specific solution. While that’s a viable option for feedback in general, for design critiques, in my experience, defaulting to the question approach usually reaches the best solutions because designers are generally more comfortable in being given an open space to explore.


The difference between the two can be exemplified with, for the question approach:


<blockquote class="wp-block-quote">When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Would it make sense to unify them?</blockquote>


Or, for the request approach:


<blockquote class="wp-block-quote">When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same pair of forward and back buttons.</blockquote>


At this point in some situations, it might be useful to integrate with an extra why: why you consider the given suggestion to be better.


<blockquote class="wp-block-quote">When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.</blockquote>


Choosing the question approach or the request approach can also at times be a matter of personal preference. A while ago, I was putting a lot of effort into improving my feedback: I did rounds of anonymous feedback, and I reviewed feedback with other people. After a few rounds of this work and a year later, I got a positive response: my feedback came across as effective and grounded. Until I changed teams. To my shock, my next round of feedback from one specific person wasn’t that great. The reason is that I had previously tried not to be prescriptive in my advice—because the people who I was previously working with preferred the open-ended question format over the request style of suggestions. But now in this other team, there was one person who instead preferred specific guidance. So I adapted my feedback for them to include requests.


One comment that I heard come up a few times is that this kind of feedback is quite long, and it doesn’t seem very efficient. No… but also yes. Let’s explore both sides.


No, this style of feedback is actually efficient because the length here is a byproduct of clarity, and spending time giving this kind of feedback can provide exactly enough information for a good fix. Also if we zoom out, it can reduce future back-and-forth conversations and misunderstandings, improving the overall efficiency and effectiveness of collaboration beyond the single comment. Imagine that in the example above the feedback were instead just, “Let’s make sure that all screens have the same two forward and back buttons.” The designer receiving this feedback wouldn’t have much to go by, so they might just apply the change. In later iterations, the interface might change or they might introduce new features—and maybe that change might not make sense anymore. Without the why, the designer might imagine that the change is about consistency… but what if it wasn’t? So there could now be an underlying concern that changing the buttons would be perceived as a regression.


Yes, this style of feedback is not always efficient because the points in some comments don’t always need to be exhaustive, sometimes because certain changes may be obvious (“The font used doesn’t follow our guidelines”) and sometimes because the team may have a lot of internal knowledge such that some of the whys may be implied.


So the equation above isn’t meant to suggest a strict template for feedback but a mnemonic to reflect and improve the practice. Even after years of active work on my critiques, I still from time to time go back to this formula and reflect on whether what I just wrote is effective.


<h2>The tone</h2>


Well-grounded content is the foundation of feedback, but that’s not really enough. The soft skills of the person who’s providing the critique can multiply the likelihood that the feedback will be well received and understood. Tone alone can make the difference between content that’s rejected or welcomed, and it’s been demonstrated that <a href="https://pubmed.ncbi.nlm.nih.gov/23802125/">only positive feedback creates sustained change</a> in people.


Since our goal is to be understood and to have a positive working environment, tone is essential to work on. Over the years, I’ve tried to summarize the required soft skills in a formula that mirrors the one for content: the receptivity equation.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/06/async-critique-receptivity-equation.png?resize=1024,293" alt="Another equation: Timing plus attitude plus form equals respectful feedback." class="wp-image-7173015" /></figure>


Respectful feedback comes across as grounded, solid, and constructive. It’s the kind of feedback that, whether it’s positive or negative, is perceived as useful and fair.


Timing refers to when the feedback happens. To-the-point feedback doesn’t have much hope of being well received if it’s given at the wrong time. Questioning the entire high-level information architecture of a new feature when it’s about to ship might still be relevant if that questioning highlights a major blocker that nobody saw, but it’s way more likely that those concerns will have to wait for a later rework. So in general, attune your feedback to the stage of the project. Early iteration? Late iteration? Polishing work in progress? These all have different needs. The right timing will make it more likely that your feedback will be well received.


Attitude is the equivalent of intent, and in the context of person-to-person feedback, it can be referred to as <a href="https://www.radicalcandor.com/radical-candor-not-brutal-honesty/">radical candor</a>. That means checking before we write to see whether what we have in mind will truly help the person and make the project better overall. This might be a hard reflection at times because maybe we don’t want to admit that we don’t really appreciate that person. Hopefully that’s not the case, but that can happen, and that’s okay. Acknowledging and owning that can help you make up for that: how would I write if I really cared about them? How can I avoid being passive aggressive? How can I be more constructive?


Form is relevant especially in a diverse and cross-cultural work environments because having great content, perfect timing, and the right attitude might not come across if the way that we write creates misunderstandings. There might be many reasons for this: sometimes certain words might trigger specific reactions; sometimes nonnative speakers might not understand all the nuances of some sentences; sometimes our brains might just be different and we might perceive the world differently—neurodiversity must be taken into consideration. Whatever the reason, it’s important to review not just what we write but how.


A few years back, I was asking for some feedback on how I give feedback. I received some good advice but also a comment that surprised me. They pointed out that when I wrote “Oh, […],” I made them feel stupid. That wasn’t my intent! I felt really bad, and I just realized that I provided feedback to them for months, and every time I might have made them feel stupid. I was horrified… but also thankful. I made a quick fix: I added “oh” in my list of replaced words (your choice between: macOS’s text replacement, aText, TextExpander, or others) so that when I typed “oh,” it was instantly deleted.


Something to highlight because it’s quite frequent—especially in teams that have a strong group spirit—is that people tend to beat around the bush. It’s important to remember here that a positive attitude doesn’t mean going light on the feedback—it just means that even when you provide hard, difficult, or challenging feedback, you do so in a way that’s respectful and constructive. The nicest thing that you can do for someone is to help them grow.


We have a great advantage in giving feedback in written form: it can be reviewed by another person who isn’t directly involved, which can help to reduce or remove any bias that might be there. I found that the best, most insightful moments for me have happened when I’ve shared a comment and I’ve asked someone who I highly trusted, “How does this sound?,” “How can I do it better,” and even “How would you have written it?”—and I’ve learned a lot by seeing the two versions side by side.


<h2>The format</h2>


Asynchronous feedback also has a major inherent advantage: we can take more time to refine what we’ve written to make sure that it fulfills two main goals: the clarity of communication and the actionability of the suggestions.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/06/async-critique-format.png?resize=1024,293" alt="Clarity plus Actionability" class="wp-image-7173016" /></figure>


Let’s imagine that someone shared a design iteration for a project. You are reviewing it and leaving a comment. There are many ways to do this, and of course context matters, but let’s try to think about some elements that may be useful to consider.


In terms of clarity, start by grounding the critique that you’re about to give by providing context. Specifically, this means describing where you’re coming from: do you have a deep knowledge of the project, or is this the first time that you’re seeing it? Are you coming from a high-level perspective, or are you figuring out the details? Are there regressions? Which user’s perspective are you taking when providing your feedback? Is the design iteration at a point where it would be okay to ship this, or are there major things that need to be addressed first?


Providing context is helpful even if you’re sharing feedback within a team that already has some information on the project. And context is absolutely essential when giving cross-team feedback. If I were to review a design that might be indirectly related to my work, and if I had no knowledge about how the project arrived at that point, I would say so, highlighting my take as external.


We often focus on the negatives, trying to outline all the things that could be done better. That’s of course important, but it’s just as important—if not more—to focus on the positives, especially if you saw progress from the previous iteration. This might seem superfluous, but it’s important to keep in mind that design is a discipline where there are hundreds of possible solutions for every problem. So pointing out that the design solution that was chosen is good and explaining why it’s good has two major benefits: it confirms that the approach taken was solid, and it helps to ground your negative feedback. In the longer term, sharing positive feedback can help prevent regressions on things that are going well because those things will have been highlighted as important. As a bonus, positive feedback can also help reduce impostor syndrome.


There’s one powerful approach that combines both context and a focus on the positives: frame how the design is better than the status quo (compared to a previous iteration, competitors, or benchmarks) and why, and then on that foundation, you can add what could be improved. This is powerful because there’s a big difference between a critique that’s for a design that’s already in good shape and a critique that’s for a design that isn’t quite there yet.


Another way that you can improve your feedback is to depersonalize the feedback: the comments should always be about the work, never about the person who made it. It’s “This button isn’t well aligned” versus “You haven’t aligned this button well.” This is very easy to change in your writing by reviewing it just before sending.


In terms of actionability, one of the best approaches to help the designer who’s reading through your feedback is to split it into bullet points or paragraphs, which are easier to review and analyze one by one. For longer pieces of feedback, you might also consider splitting it into sections or even across multiple comments. Of course, adding screenshots or signifying markers of the specific part of the interface you’re referring to can also be especially useful.


One approach that I’ve personally used effectively in some contexts is to enhance the bullet points with four markers using emojis. So a red square 🟥 means that it’s something that I consider blocking; a yellow diamond 🔶 is something that I can be convinced otherwise, but it seems to me that it should be changed; and a green circle 🟢 is a detailed, positive confirmation. I also use a blue spiral 🌀 for either something that I’m not sure about, an exploration, an open alternative, or just a note. But I’d use this approach only on teams where I’ve already established a good level of trust because if it happens that I have to deliver a lot of red squares, the impact could be quite demoralizing, and I’d reframe how I’d communicate that a bit.


Let’s see how this would work by reusing the example that we used earlier as the first bullet point in this list:


<ul><li>🔶 Navigation—When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.</li><li>🟢 Overall—I think the page is solid, and this is good enough to be our release candidate for a version 1.0.</li><li>🟢 Metrics—Good improvement in the buttons on the metrics area; the improved contrast and new focus style make them more accessible.</li><li> 🟥  Button Style—Using the green accent in this context creates the impression that it’s a positive action because green is usually perceived as a confirmation color. Do we need to explore a different color?</li><li>🔶Tiles—Given the number of items on the page, and the overall page hierarchy, it seems to me that the tiles shouldn’t be using the Subtitle 1 style but the Subtitle 2 style. This will keep the visual hierarchy more consistent.</li><li>🌀 Background—Using a light texture works well, but I wonder whether it adds too much noise in this kind of page. What is the thinking in using that?</li></ul>


What about giving feedback directly in Figma or another design tool that allows in-place feedback? In general, I find these difficult to use because they hide discussions and they’re harder to track, but in the right context, they can be very effective. Just make sure that each of the comments is separate so that it’s easier to match each discussion to a single task, similar to the idea of splitting mentioned above.


One final note: say the obvious. Sometimes we might feel that something is obviously good or obviously wrong, and so we don’t say it. Or sometimes we might have a doubt that we don’t express because the question might sound stupid. Say it—that’s okay. You might have to reword it a little bit to make the reader feel more comfortable, but don’t hold it back. Good feedback is transparent, even when it may be obvious.


There’s another advantage of asynchronous feedback: written feedback automatically tracks decisions. Especially in large projects, “Why did we do this?” could be a question that pops up from time to time, and there’s nothing better than open, transparent discussions that can be reviewed at any time. For this reason, I recommend using software that saves these discussions, without hiding them once they are resolved. 


Content, tone, and format. Each one of these subjects provides a useful model, but working to improve eight areas—observation, impact, question, timing, attitude, form, clarity, and actionability—is a lot of work to put in all at once. One effective approach is to take them one by one: first identify the area that you lack the most (either from your perspective or from feedback from others) and start there. Then the second, then the third, and so on. At first you’ll have to put in extra time for every piece of feedback that you give, but after a while, it’ll become second nature, and your impact on the work will multiply.


Thanks to Brie Anne Demkiw and Mike Shelton for reviewing the first draft of this article.
]]> </description>
<dc:subject>
<![CDATA[Design, Process, User Experience]]> </dc:subject>
<dc:date>
2021-06-17T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[That’s Not My Burnout]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/donna-bungard/">Donna Bungard</a> </author>
<link>
https://alistapart.com/article/thats-not-my-burnout/ </link>
<guid>
https://alistapart.com/article/thats-not-my-burnout/ </guid>
<description>
<![CDATA[
Are you like me, reading about people fading away as they burn out, and feeling unable to relate? Do you feel like your feelings are invisible to the world because you’re experiencing burnout differently? When burnout starts to push down on us, our core comes through more. Beautiful, peaceful souls get quieter and fade into that distant and distracted burnout we’ve all read about. But some of us, those with fires always burning on the edges of our core, get hotter. In my heart I am fire. When I face burnout I double down, triple down, burning hotter and hotter to try to best the challenge. I don’t fade—I am engulfed in a zealous burnout.


<h2>So what on earth is a zealous burnout?</h2>


Imagine a woman determined to do it all. She has two amazing children whom she, along with her husband who is also working remotely, is homeschooling during a pandemic. She has a demanding client load at work—all of whom she loves. She gets up early to get some movement in (or often catch up on work), does dinner prep as the kids are eating breakfast, and gets to work while positioning herself near “fourth grade” to listen in as she juggles clients, tasks, and budgets. Sound like a lot? Even with a supportive team both at home and at work, it is.


Sounds like this woman has too much on her plate and needs self-care. But no, she doesn’t have time for that. In fact, she starts to feel like she’s dropping balls. Not accomplishing enough. There’s not enough of her to be here and there; she is trying to divide her mind in two all the time, all day, every day. She starts to doubt herself. And as those feelings creep in more and more, her internal narrative becomes more and more critical.


Suddenly she KNOWS what she needs to do! She should DO MORE. 


This is a hard and dangerous cycle. Know why? Because once she doesn’t finish that new goal, that narrative will get worse. Suddenly she’s failing. She isn’t doing enough. SHE is not enough. She might fail, she might fail her family...so she’ll find more she should do. She doesn’t sleep as much, move as much, all in the efforts to do more. Caught in this cycle of trying to prove herself to herself, never reaching any goal. Never feeling “enough.” 


So, yeah, that’s what zealous burnout looks like for me. It doesn’t happen overnight in some grand gesture but instead slowly builds over weeks and months. My burning out process looks like speeding up, not a person losing focus. I speed up and up and up...and then I just stop.


<h2>I am the one who could</h2>


It’s funny the things that shape us. Through the lens of childhood, I viewed the fears, struggles, and sacrifices of someone who had to make it all work without having enough. I was lucky that my mother was so resourceful and my father supportive; I never went without and even got an extra here or there. 


Growing up, I did not feel shame when my mother paid with food stamps; in fact, I’d have likely taken on any debate on the topic, verbally eviscerating anyone who dared to criticize the disabled woman trying to make sure all our needs were met with so little. As a child, I watched the way the fear of not making those ends meet impacted people I love. As the non-disabled person in my home, I would take on many of the physical tasks because I was “the one who could” make our lives a little easier. I learned early to associate fears or uncertainty with putting more of myself into it—I am the one who can. I learned early that when something frightens me, I can double down and work harder to make it better. I can own the challenge. When people have seen this in me as an adult, I’ve been told I seem fearless, but make no mistake, I’m not. If I seem fearless, it’s because this behavior was forged from other people’s fears.


And here I am, more than 30 years later still feeling the urge to mindlessly push myself forward when faced with overwhelming tasks ahead of me, assuming that I am the one who can and therefore should. I find myself driven to prove that I can make things happen if I work longer hours, take on more responsibility, and do more. 


I do not see people who struggle financially as failures, because I have seen how strong that tide can be—it pulls you along the way. I truly get that I have been privileged to be able to avoid many of the challenges that were present in my youth. That said, I am still “the one who can” who feels she should, so if I were faced with not having enough to make ends meet for my own family, I would see myself as having failed. Though I am supported and educated, most of this is due to good fortune. I will, however, allow myself the arrogance of saying I have been careful with my choices to have encouraged that luck. My identity stems from the idea that I am “the one who can” so therefore feel obligated to do the most. I can choose to stop, and with some quite literal cold water splashed in my face, I’ve made the choice to before. But that choosing to stop is not my go-to; I move forward, driven by a fear that is so a part of me that I barely notice it’s there until I’m feeling utterly worn away.


So why all the history? You see, burnout is a fickle thing. I have heard and read a lot about burnout over the years. Burnout is real. Especially now, with COVID, many of us are balancing more than we ever have before—all at once! It’s hard, and the procrastinating, the avoidance, the shutting down impacts so many amazing professionals. There are important articles that relate to what I imagine must be the majority of people out there, but not me. That’s not what my burnout looks like.


<h2>The dangerous invisibility of zealous burnout</h2>


A lot of work environments see the extra hours, extra effort, and overall focused commitment as an asset (and sometimes that’s all it is). They see someone trying to rise to challenges, not someone stuck in their fear. Many well-meaning organizations have safeguards in place to protect their teams from burnout. But in cases like this, those alarms are not always tripped, and then when the inevitable stop comes, some members of the organization feel surprised and disappointed. And sometimes maybe even betrayed.


Parents—more so mothers, statistically speaking—are praised as being so on top of it all when they can work, be involved in the after-school activities, practice self-care in the form of diet and exercise, and still meet friends for coffee or wine. During COVID many of us have binged countless streaming episodes showing how it’s so hard for the female protagonist, but she is strong and funny and can do it. It’s a “very special episode” when she breaks down, cries in the bathroom, woefully admits she needs help, and just stops for a bit. Truth is, countless people are hiding their tears or are doom-scrolling to escape. We know that the media is a lie to amuse us, but often the perception that it’s what we should strive for has penetrated much of society.


<h2>Women and burnout</h2>


I love men. And though I don’t love every man (heads up, I don’t love every woman or nonbinary person either), I think there is a beautiful spectrum of individuals who represent that particular binary gender. 


That said, women are still more often at risk of burnout than their male counterparts, especially in these COVID stressed times. Mothers in the workplace feel the pressure to do all the “mom” things while giving 110%. Mothers not in the workplace feel they need to do more to “justify” their lack of traditional employment. Women who are not mothers often feel the need to do even more because they don’t have that extra pressure at home. It’s vicious and systemic and so a part of our culture that we’re often not even aware of the enormity of the pressures we put on ourselves and each other.


And there are prices beyond happiness too. <a href="https://www.health.harvard.edu/heart-health/job-strain-and-heart-disease-risk-in-women">Harvard Health Publishing released a study</a> a decade ago that “uncovered strong links between women’s job stress and cardiovascular disease.” <a href="https://www.cdc.gov/heartdisease/women.htm">The CDC noted,</a> “Heart disease is the leading cause of death for women in the United States, killing 299,578 women in 2017—or about 1 in every 5 female deaths.”


This relationship between work stress and health, from what I have read, is more dangerous for women than it is for their non-female counterparts.


<h2>But what if your burnout isn’t like that either?</h2>


That might not be you either. After all, each of us is so different and how we respond to stressors is too. It’s part of what makes us human. Don’t stress what burnout looks like, just learn to recognize it in yourself. Here are a few questions I sometimes ask friends if I am concerned about them.


Are you happy? This simple question should be the first thing you ask yourself. Chances are, even if you’re burning out doing all the things you love, as you approach burnout you’ll just stop taking as much joy from it all.


Do you feel empowered to say no? I have observed in myself and others that when someone is burning out, they no longer feel they can say no to things. Even those who don’t “speed up” feel pressure to say yes to not disappoint the people around them.


What are three things you’ve done for yourself? Another observance is that we all tend to stop doing things for ourselves. Anything from skipping showers and eating poorly to avoiding talking to friends. These can be red flags. 


Are you making excuses? Many of us try to disregard feelings of burnout. Over and over I have heard, “It’s just crunch time,” “As soon as I do this one thing, it will all be better,” and “Well I should be able to handle this, so I’ll figure it out.” And it might really be crunch time, a single goal, and/or a skill set you need to learn. That happens—life happens. BUT if this doesn’t stop, be honest with yourself. If you’ve worked more 50-hour weeks since January than not, maybe it’s not crunch time—maybe it’s a bad situation that you’re burning out from.


Do you have a plan to stop feeling this way? If something is truly temporary and you do need to just push through, then it has an exit route with a defined end.


Take the time to listen to yourself as you would a friend. Be honest, allow yourself to be uncomfortable, and break the thought cycles that prevent you from healing. 


<h2>So now what?</h2>


What I just described is a different path to burnout, but it’s still burnout. There are well-established approaches to working through burnout:


<ul><li>Get enough sleep.</li><li>Eat healthy.</li><li>Work out.</li><li>Get outside.</li><li>Take a break.</li><li>Overall, practice self-care.</li></ul>


Those are hard for me because they feel like more tasks. If I’m in the burnout cycle, doing any of the above for me feels like a waste. The narrative is that if I’m already failing, why would I take care of myself when I’m dropping all those other balls? People need me, right? 


If you’re deep in the cycle, your inner voice might be pretty awful by now. If you need to, tell yourself you need to take care of the person your people depend on. If your roles are pushing you toward burnout, use them to help make healing easier by justifying the time spent working on you. 


To help remind myself of the airline attendant message about putting the mask on yourself first, I have come up with a few things that I do when I start feeling myself going into a zealous burnout.


<h3>Cook an elaborate meal for someone! </h3>


OK, I am a “food-focused” individual so cooking for someone is always my go-to. There are countless tales in my home of someone walking into the kitchen and turning right around and walking out when they noticed I was “chopping angrily.” But it’s more than that, and you should give it a try. Seriously. It’s the perfect go-to if you don’t feel worthy of taking time for yourself—do it for someone else. Most of us work in a digital world, so cooking can fill all of your senses and force you to be in the moment with all the ways you perceive the world. It can break you out of your head and help you gain a better perspective. In my house, I’ve been known to pick a place on the map and cook food that comes from wherever that is (thank you, Pinterest). I love cooking Indian food, as the smells are warm, the bread needs just enough kneading to keep my hands busy, and the process takes real attention for me because it’s not what I was brought up making. And in the end, we all win!


<h3>Vent like a foul-mouthed fool</h3>


Be careful with this one! 


I have been making an effort to practice more gratitude over the past few years, and I recognize the true benefits of that. That said, sometimes you just gotta let it all out—even the ugly. Hell, I’m a big fan of not sugarcoating our lives, and that sometimes means that to get past the big pile of poop, you’re gonna wanna complain about it a bit. 


When that is what’s needed, turn to a trusted friend and allow yourself some pure verbal diarrhea, saying all the things that are bothering you. You need to trust this friend not to judge, to see your pain, and, most importantly, to tell you to remove your cranium from your own rectal cavity. Seriously, it’s about getting a reality check here! One of the things I admire the most about my husband (though often after the fact) is his ability to break things down to their simplest. “We’re spending our lives together, of course you’re going to disappoint me from time to time, so get over it” has been his way of speaking his dedication, love, and acceptance of me—and I could not be more grateful. It also, of course, has meant that I needed to remove my head from that rectal cavity. So, again, usually those moments are appreciated in hindsight.


<h3>Pick up a book! </h3>


There are many books out there that aren’t so much self-help as they are people just like you sharing their stories and how they’ve come to find greater balance. Maybe you’ll find something that speaks to you. Titles that have stood out to me include:


<ul><li>Thrive by Arianna Huffington</li><li>Tools of Titans by Tim Ferriss</li><li>Girl, Stop Apologizing by Rachel Hollis</li><li>Dare to Lead by Brené Brown</li></ul>


Or, another tactic I love to employ is to read or listen to a book that has NOTHING to do with my work-life balance. I’ve read the following books and found they helped balance me out because my mind was pondering their interesting topics instead of running in circles:


<ul><li>The Drunken Botanist by Amy Stewart</li><li>Superlife by Darin Olien</li><li>A Brief History of Everyone Who Ever Lived by Adam Rutherford</li><li>Gaia’s Garden by Toby Hemenway </li></ul>


If you’re not into reading, pick up a topic on YouTube or choose a podcast to subscribe to. I’ve watched countless permaculture and gardening topics in addition to how to raise chickens and ducks. For the record, I do not have a particularly large food garden, nor do I own livestock of any kind...yet. I just find the topic interesting, and it has nothing to do with any aspect of my life that needs anything from me.


<h3>Forgive yourself </h3>


You are never going to be perfect—hell, it would be boring if you were. It’s OK to be broken and flawed. It’s human to be tired and sad and worried. It’s OK to not do it all. It’s scary to be imperfect, but you cannot be brave if nothing were scary.


This last one is the most important: allow yourself permission to NOT do it all. You never promised to be everything to everyone at all times. We are more powerful than the fears that drive us. 


This is hard. It is hard for me. It’s what’s driven me to write this—that it’s OK to stop. It’s OK that your unhealthy habit that might even benefit those around you needs to end. You can still be successful in life.


I recently read that we are all writing our eulogy in how we live. Knowing that your professional accomplishments won’t be mentioned in that speech, what will yours say? What do you want it to say? 


Look, I get that none of these ideas will “fix it,” and that’s not their purpose. None of us are in control of our surroundings, only how we respond to them. These suggestions are to help stop the spiral effect so that you are empowered to address the underlying issues and choose your response. They are things that work for me most of the time. Maybe they’ll work for you.


<h2>Does this sound familiar? </h2>


If this sounds familiar, it’s not just you. Don’t let your negative self-talk tell you that you “even burn out wrong.” It’s not wrong. Even if rooted in fear like my own drivers, I believe that this need to do more comes from a place of love, determination, motivation, and other wonderful attributes that make you the amazing person you are. We’re going to be OK, ya know. The lives that unfold before us might never look like that story in our head—that idea of “perfect” or “done” we’re looking for, but that’s OK. Really, when we stop and look around, usually the only eyes that judge us are in the mirror.


Do you remember that Winnie the Pooh sketch that had Pooh eat so much at Rabbit’s house that his buttocks couldn’t fit through the door? Well, I already associate a lot with Rabbit, so it came as no surprise when he abruptly declared that this was unacceptable. But do you recall what happened next? He put a shelf across poor Pooh’s ankles and decorations on his back, and made the best of the big butt in his kitchen. 


At the end of the day we are resourceful and know that we are able to push ourselves if we need to—even when we are tired to our core or have a big butt of fluff ‘n’ stuff in our room. None of us has to be afraid, as we can manage any obstacle put in front of us. And maybe that means we will need to redefine success to allow space for being uncomfortably human, but that doesn’t really sound so bad either. 


So, wherever you are right now, please breathe. Do what you need to do to get out of your head. Forgive and take care.
]]> </description>
<dc:subject>
<![CDATA[Career, Creativity]]> </dc:subject>
<dc:date>
2021-05-20T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Beware the Cut ‘n’ Paste Persona]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/emanuela-cozzi/">Emanuela Cozzi</a>, <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/lennartoverkamp/">Lennart Overkamp</a> </author>
<link>
https://alistapart.com/article/beware-the-cut-n-paste-persona/ </link>
<guid>
https://alistapart.com/article/beware-the-cut-n-paste-persona/ </guid>
<description>
<![CDATA[
<a href="https://thispersondoesnotexist.com/">This Person Does Not Exist</a> is a website that generates human faces with a machine learning algorithm. It takes real portraits and recombines them into fake human faces. We recently scrolled past a LinkedIn post stating that this website could be useful “if you are developing a persona and looking for a photo.” 


We agree: the computer-generated faces could be a great match for personas—but not for the reason you might think. Ironically, the website highlights the core issue of this very common design method: the person(a) does not exist. Like the pictures, personas are artificially made. Information is taken out of natural context and recombined into an isolated snapshot that’s detached from reality. 


But strangely enough, designers use personas to inspire their design for the real world. 


<h2>Personas: A step back</h2>


Most designers have created, used, or come across personas at least once in their career. In their article “<a href="https://www.interaction-design.org/literature/article/personas-why-and-how-you-should-use-them">Personas - A Simple Introduction</a>,” the Interaction Design Foundation defines personas as “fictional characters, which you create based upon your research in order to represent the different user types that might use your service, product, site, or brand.” In their most complete expression, personas typically consist of a name, profile picture, quotes, demographics, goals, needs, behavior in relation to a certain service/product, emotions, and motivations (for example, see Creative Companion’s <a href="https://creativecompanion.wordpress.com/2011/05/05/the-persona-core-poster/">Persona Core Poster</a>). The purpose of personas, as <a href="https://medium.designit.com/mindset-over-matter-a-new-design-trick-for-your-toolbox-part-one-91bc5f82360f">stated by</a> design agency Designit, is “to make the research relatable, [and] easy to communicate, digest, reference, and apply to product and service development.”


<h2>The decontextualization of personas</h2>


Personas are popular because they make “dry” research data more relatable, more human. However, this method constrains the researcher’s data analysis in such a way that the investigated users are removed from their unique contexts. As a result, personas don’t portray key factors that make you understand their decision-making process or allow you to relate to users’ thoughts and behavior; they lack stories. You understand what the persona did, but you don’t have the background to understand why. You end up with representations of users that are actually less human.


This “decontextualization” we see in personas happens in four ways, which we’ll explain below. 


<h3>Personas assume people are static </h3>


Although many companies still try to box in their employees and customers with outdated personality tests (referring to you, Myers-Briggs), here’s a painfully obvious truth: people are not a fixed set of features. You act, think, and feel differently according to the situations you experience. You appear different to different people; you might act friendly to some, rough to others. And you change your mind all the time about decisions you’ve taken. 


<a href="https://en.wikipedia.org/wiki/Person%E2%80%93situation_debate#Current_directions">Modern psychologists agree</a> that while people generally behave according to certain patterns, it’s actually a combination of background and environment that determines how people act and take decisions. The context—the environment, the influence of other people, your mood, the entire history that led up to a situation—determines the kind of person you are in each specific moment. 


In their attempt to simplify reality, personas do not take this variability into account; they present a user as a fixed set of features. Like personality tests, personas snatch people away from real life. Even worse, people are reduced to a label and categorized as “that kind of person” with no means to exercise their innate flexibility. This practice reinforces stereotypes, lowers diversity, and doesn’t reflect reality. 


<h3>Personas focus on individuals, not the environment</h3>


In the real world, you’re designing for a context, not for an individual. Each person lives in a family, a community, an ecosystem, where there are environmental, political, and social factors you need to consider. A design is never meant for a single user. Rather, you design for one or more particular contexts in which many people might use that product. Personas, however, show the user alone rather than describe how the user relates to the environment. 


Would you always make the same decision over and over again? Maybe you’re a committed vegan but still decide to buy some meat when your relatives are coming over. As they depend on different situations and variables, your decisions—and behavior, opinions, and statements—are not absolute but highly contextual. The persona that “represents” you wouldn’t take into account this dependency, because it doesn’t specify the premises of your decisions. It doesn’t provide a justification of why you act the way you do. Personas enact the well-known bias called <a href="https://en.wikipedia.org/wiki/Fundamental_attribution_error">fundamental attribution error</a>: explaining others’ behavior too much by their personality and too little by the situation.


As mentioned by the Interaction Design Foundation, personas are usually placed in a scenario that’s a “specific context with a problem they want to or have to solve”—does that mean context actually is considered? Unfortunately, what often happens is that you take a fictional character and based on that fiction determine how this character might deal with a certain situation. This is made worse by the fact that you haven’t even fully investigated and understood the current context of the people your persona seeks to represent; so how could you possibly understand how they would act in new situations?


<h3>Personas are meaningless averages</h3>


As mentioned in Shlomo Goltz’s <a href="https://www.smashingmagazine.com/2014/08/a-closer-look-at-personas-part-1/">introductory article</a> on Smashing Magazine, “a persona is depicted as a specific person but is not a real individual; rather, it is synthesized from observations of many people.” A well-known critique to this aspect of personas is that the average person does not exist, as per the <a href="https://www.goodreads.com/book/show/24186666-the-end-of-average">famous example</a> of the USA Air Force designing planes based on the average of 140 of their pilots’ physical dimensions and not a single pilot actually fitting within that average seat.


The same limitation applies to mental aspects of people. Have you ever heard a famous person say, “They took what I said out of context! They used my words, but I didn’t mean it like that.” The celebrity’s statement was reported literally, but the reporter failed to explain the context around the statement and didn’t describe the non-verbal expressions. As a result, the intended meaning was lost. You do the same when you create personas: you collect somebody’s statement (or goal, or need, or emotion), of which the meaning can only be understood if you provide its own specific context, yet report it as an isolated finding.


But personas go a step further, extracting a decontextualized finding and joining it with another decontextualized finding from somebody else. The resulting set of findings often does not make sense: it’s unclear, or even contrasting, because it lacks the underlying reasons on why and how that finding has arisen. It lacks meaning. And the persona doesn’t give you the full background of the person(s) to uncover this meaning: you would need to dive into the raw data for each single persona item to find it. What, then, is the usefulness of the persona?


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/05/cut-n-paste-persona-fig3.jpg?resize=1024,1024" alt="Composite image of a man composed of many different photos" class="wp-image-7172942"/></figure>


<h3>The relatability of personas is deceiving</h3>


To a certain extent, designers realize that a persona is a lifeless average. To overcome this, designers invent and add “relatable” details to personas to make them resemble real individuals. Nothing captures the absurdity of this better than a sentence by the Interaction Design Foundation: “Add a few fictional personal details to make the persona a realistic character.” In other words, you add non-realism in an attempt to create more realism. You deliberately obscure the fact that “John Doe” is an abstract representation of research findings; but wouldn’t it be much more responsible to emphasize that John is only an abstraction? If something is artificial, let’s present it as such.


It’s the finishing touch of a persona’s decontextualization: after having assumed that people’s personalities are fixed, dismissed the importance of their environment, and hidden meaning by joining isolated, non-generalizable findings, designers invent new context to create (their own) meaning. In doing so, as with everything they create, they introduce a host of biases. As phrased by Designit, as designers we can “contextualize [the persona] based on our reality and experience. We create connections that are familiar to us.” This practice reinforces stereotypes, doesn’t reflect real-world diversity, and gets further away from people’s actual reality with every detail added.


To do good design research, we should report the reality “as-is” and make it relatable for our audience, so everyone can use their own empathy and develop their own interpretation and emotional response.


<h2>Dynamic Selves: The alternative to personas</h2>


If we shouldn’t use personas, what should we do instead? 


Designit has proposed using <a href="https://medium.designit.com/mindset-over-matter-a-new-design-trick-for-your-toolbox-part-two-f56bd248319a">Mindsets</a> instead of personas. Each Mindset is a “spectrum of attitudes and emotional responses that different people have within the same context or life experience.” It challenges designers to not get fixated on a single user’s way of being. Unfortunately, while being a step in the right direction, this proposal doesn’t take into account that people are part of an environment that determines their personality, their behavior, and, yes, their mindset. Therefore, Mindsets are also not absolute but change in regard to the situation. The question remains, what determines a certain Mindset?


Another alternative comes from Margaret P., author of the article “<a href="https://medium.com/microsoft-design/kill-your-personas-1c332d4908cc">Kill Your Personas</a>,” who has argued for replacing personas with persona spectrums that consist of a range of user abilities. For example, a visual impairment could be permanent (blindness), temporary (recovery from eye surgery), or situational (screen glare). Persona spectrums are highly useful for more inclusive and context-based design, as they’re based on the understanding that the context is the pattern, not the personality. Their limitation, however, is that they have a very functional take on users that misses the relatability of a real person taken from within a spectrum.


In developing an alternative to personas, we aim to transform the standard design process to be context-based. Contexts are generalizable and have patterns that we can identify, just like we tried to do previously with people. So how do we identify these patterns? How do we ensure truly context-based design? 


<h2>Understand real individuals in multiple contexts</h2>


Nothing is more relatable and inspiring than reality. Therefore, we have to understand real individuals in their multi-faceted contexts, and use this understanding to fuel our design. We refer to this approach as Dynamic Selves.


Let’s take a look at what the approach looks like, based on an example of how one of us applied it in a recent project that researched habits of Italians around energy consumption. We drafted a design research plan aimed at investigating people’s attitudes toward energy consumption and sustainable behavior, with a focus on smart thermostats. 


<h4>1. Choose the right sample</h4>


When we argue against personas, we’re often challenged with <a href="https://ux.stackexchange.com/questions/8647/why-not-use-a-real-person-as-a-persona">quotes</a> such as “Where are you going to find a single person that encapsulates all the information from one of these advanced personas[?]” The answer is simple: you don’t have to. You don’t need to have information about many people for your insights to be deep and meaningful. 


In qualitative research, validity does not derive from quantity but from accurate sampling. You select the people that best represent the “population” you’re designing for. If this sample is chosen well, and you have understood the sampled people in sufficient depth, you’re able to infer how the rest of the population thinks and behaves. There’s no need to study seven Susans and five Yuriys; one of each will do. 


Similarly, you don’t need to understand Susan in fifteen different contexts. Once you’ve seen her in a couple of diverse situations, you’ve understood the scheme of Susan’s response to different contexts. Not Susan as an atomic being but Susan in relation to the surrounding environment: how she might act, feel, and think in different situations. 


Given that each person is representative of a part of the total population you’re researching, it becomes clear why each should be represented as an individual, as each already is an abstraction of a larger group of individuals in similar contexts. You don’t want abstractions of abstractions! These selected people need to be understood and shown in their full expression, remaining in their microcosmos—and if you want to identify patterns you can focus on identifying patterns in contexts.


Yet the question remains: how do you select a representative sample? First of all, you have to consider what’s the target audience of the product or service you are designing: it might be useful to look at the company’s goals and strategy, the current customer base, and/or a possible future target audience. 


In our example project, we were designing an application for those who own a smart thermostat. In the future, everyone could have a smart thermostat in their house. Right now, though, only early adopters own one. To build a significant sample, we needed to understand the reason why these early adopters became such. We therefore recruited by asking people why they had a smart thermostat and how they got it. There were those who had chosen to buy it, those who had been influenced by others to buy it, and those who had found it in their house. So we selected representatives of these three situations, from different age groups and geographical locations, with an equal balance of tech savvy and non-tech savvy participants.


<h4>2. Conduct your research</h4>


After having chosen and recruited your sample, conduct your research using ethnographic methodologies. This will make your qualitative data rich with anecdotes and examples. In our example project, given COVID-19 restrictions, we converted an in-house ethnographic research effort into remote family interviews, conducted from home and accompanied by diary studies.


To gain an in-depth understanding of attitudes and decision-making trade-offs, the research focus was not limited to the interviewee alone but deliberately included the whole family. Each interviewee would tell a story that would then become much more lively and precise with the corrections or additional details coming from wives, husbands, children, or sometimes even pets. We also focused on the relationships with other meaningful people (such as colleagues or distant family) and all the behaviors that resulted from those relationships. This wide research focus allowed us to shape a vivid mental image of dynamic situations with multiple actors.


It’s essential that the scope of the research remains broad enough to be able to include all possible actors. Therefore, it normally works best to define broad research areas with macro questions. Interviews are best set up in a semi-structured way, where follow-up questions will dive into topics mentioned spontaneously by the interviewee. This open-minded “plan to be surprised” will yield the most insightful findings. When we asked one of our participants how his family regulated the house temperature, he replied, “My wife has not installed the thermostat’s app—she uses WhatsApp instead. If she wants to turn on the heater and she is not home, she will text me. I am her thermostat.”


<h4>3. Analysis: Create the Dynamic Selves</h4>


During the research analysis, you start representing each individual with multiple Dynamic Selves, each “Self” representing one of the contexts you have investigated. The core of each Dynamic Self is a quote, which comes supported by a photo and a few relevant demographics that illustrate the wider context. The research findings themselves will show which demographics are relevant to show. In our case, as our research focused on families and their lifestyle to understand their needs for thermal regulation, the important demographics were family type, number and nature of houses owned, economic status, and technological maturity. (We also included the individual’s name and age, but they’re optional—we included them to ease the stakeholders’ transition from personas and be able to connect multiple actions and contexts to the same person).


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/05/cut-n-paste-persona-fig1.png?resize=1024,554" alt="Three cards, each showing a different lifestyle photo, a quote that correlates to that dynamic self's attitude about technology, and some basic demographic info" class="wp-image-7172943"/></figure>


To capture exact quotes, interviews need to be video-recorded and notes need to be taken verbatim as much as possible. This is essential to the truthfulness of the several Selves of each participant. In the case of real-life ethnographic research, photos of the context and anonymized actors are essential to build realistic Selves. Ideally, these photos should come directly from field research, but an evocative and representative image will work, too, as long as it’s realistic and depicts meaningful actions that you associate with your participants. For example, one of our interviewees told us about his mountain home where he used to spend every weekend with his family. Therefore, we portrayed him hiking with his little daughter.


At the end of the research analysis, we displayed all of the Selves’ “cards” on a single canvas, categorized by activities. Each card displayed a situation, represented by a quote and a unique photo. All participants had multiple cards about themselves.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/05/cut-n-paste-persona-fig2.png?resize=1024,437" alt="A collection of many cards representing many dynamic self personas" class="wp-image-7172944"/></figure>


<h4>4. Identify design opportunities</h4>


Once you have collected all main quotes from the interview transcripts and diaries, and laid them all down as Self cards, you will see patterns emerge. These patterns will highlight the opportunity areas for new product creation, new functionalities, and new services—for new design. 


In our example project, there was a particularly interesting insight around the concept of humidity. We realized that people don’t know what humidity is and why it is important to monitor it for health: an environment that’s too dry or too wet can cause respiratory problems or worsen existing ones. This highlighted a big opportunity for our client to educate users on this concept and become a health advisor.


<h3>Benefits of Dynamic Selves</h3>


When you use the Dynamic Selves approach in your research, you start to notice unique social relations, peculiar situations real people face and the actions that follow, and that people are surrounded by changing environments. In our thermostat project, we have come to know one of the participants, Davide, as a boyfriend, dog-lover, and tech enthusiast. 


Davide is an individual we might have once reduced to a persona called “tech enthusiast.” But we can have tech enthusiasts who have families or are single, who are rich or poor. Their motivations and priorities when deciding to purchase a new thermostat can be opposite according to these different frames. 


Once you have understood Davide in multiple situations, and for each situation have understood in sufficient depth the underlying reasons for his behavior, you’re able to generalize how he would act in another situation. You can use your understanding of him to infer what he would think and do in the contexts (or scenarios) that you design for.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/05/cut-n-paste-persona-fig4.png?resize=1024,576" alt="A comparison. On one side, three people are fused into one to create a persona; in the second, the three people exist as separate dynamic selves." class="wp-image-7172945"/></figure>


The Dynamic Selves approach aims to dismiss the conflicted dual purpose of personas—to summarize and empathize at the same time—by separating your research summary from the people you’re seeking to empathize with. This is important because our empathy for people is <a href="https://www.epicpeople.org/commodified-empathy/">affected by scale</a>: the bigger the group, the harder it is to feel empathy for others. We feel the strongest empathy for individuals we can personally relate to.


If you take a real person as inspiration for your design, you no longer need to create an artificial character. No more inventing details to make the character more “realistic,” no more unnecessary additional bias. It’s simply how this person is in real life. In fact, in our experience, personas quickly become nothing more than a name in our <a href="https://alistapart.com/article/priority-guides-a-content-first-alternative-to-wireframes/">priority guides</a> and prototype screens, as we all know that these characters don’t really exist.


Another powerful benefit of the Dynamic Selves approach is that it raises the stakes of your work: if you mess up your design, someone real, a person you and the team know and have met, is going to feel the consequences. It might stop you from taking shortcuts and will remind you to conduct <a href="https://alistapart.com/article/daily-ethical-design/">daily</a> checks on your designs.


And finally, real people in their specific contexts are a better basis for anecdotal storytelling and therefore are more effective in persuasion. Documentation of real research is essential in achieving this result. It adds weight and urgency behind your design arguments: “When I met Alessandra, the conditions of her workplace struck me. Noise, bad ergonomics, lack of light, you name it. If we go for this functionality, I’m afraid we’re going to add complexity to her life.”


<h2>Conclusion</h2>


Designit mentioned in their article on Mindsets that “design thinking tools offer a shortcut to deal with reality’s complexities, but this process of simplification can sometimes flatten out people’s lives into a few general characteristics.” Unfortunately, personas have been culprits in a crime of oversimplification. They are unsuited to represent the complex nature of our users’ decision-making processes and don’t account for the fact that humans are immersed in contexts.


Design needs simplification but not generalization. You have to look at the research elements that stand out: the sentences that captured your attention, the images that struck you, the sounds that linger. Portray those, use them to describe the person in their multiple contexts. Both insights and people come with a context; they cannot be cut from that context because it would remove meaning. 


It’s high time for design to move away from fiction, and embrace reality—in its messy, surprising, and unquantifiable beauty—as our guide and inspiration.
]]> </description>
<dc:subject>
<![CDATA[User Experience, User Research]]> </dc:subject>
<dc:date>
2021-05-06T14:00:00+00:00 </dc:date>
</item>
<item>
<title>
<![CDATA[Immersive Content Strategy]]> </title>
<author>
by <a itemprop="url" class="author" rel="author" href="https://alistapart.com/author/preston-so/">Preston So</a> </author>
<link>
https://alistapart.com/article/immersive-content-strategy/ </link>
<guid>
https://alistapart.com/article/immersive-content-strategy/ </guid>
<description>
<![CDATA[
Beyond the severe toll of the coronavirus pandemic, perhaps no other disruption has transformed user experiences quite like how the tethers to our formerly web-biased era of content have frayed. We’re transitioning to a new world of remote work and digital content. We’re also experimenting with unprecedented content channels that, not too long ago, elicited chuckles at the watercooler, like voice interfaces, digital signage, augmented reality, and virtual reality.


Many factors are responsible. Perhaps it’s because we yearn for immersive spaces that temporarily resurrect the Before Times, or maybe it’s due to the boredom and tedium of our now-cemented stuck-at-home routines. But aural user experiences slinging <a href="https://alistapart.com/article/usability-testing-for-voice-content/">voice content</a>, and immersive user experiences unlocking new forms of interacting with formerly web-bound content, are no longer figments of science fiction. They’re fast becoming a reality in the here and now.


The idea of immersive experiences is all the rage these days, and content strategists and designers are now seriously examining this still-amorphous trend. Immersive experiences embrace concepts like geolocation, digital signage, and extended reality (XR). XR encompasses augmented reality (AR) and virtual reality (VR) as well as their fusion: mixed reality (MR). Sales of immersive equipment like gaming and VR headsets <a href="https://www.thetimes.co.uk/article/virtual-reality-pandemic-leads-to-rise-in-headset-sales-to-escape-lockdown-jhhn8wghn">have skyrocketed during the pandemic</a>, and content strategists are increasingly attuned to the kaleidoscope of devices and interfaces users now interact with on a daily basis to acquire information.


Immersive user experiences are becoming commonplace, and, more importantly, <a href="https://www.smashingmagazine.com/2020/10/using-webxr-with-babylonjs/">new tools and frameworks are emerging</a> for designers and developers looking to get their hands dirty. But that doesn’t mean our content is ready for prime time in settings unbound from the web like physical spaces, digital signage, or extended reality. Recasting your fixed web content in more immersive ways will enable more than just newfangled user experiences; it’ll prepare you for flexibility in an unpredictable future as well.


<h2>Agnostic content for immersive experiences</h2>


These days, we interact with content through a slew of devices. It’s no longer the case that we navigate information on a single desktop computer screen. In my upcoming book <a href="https://preston.so/books/voice-content">Voice Content and Usability</a> (A Book Apart, coming June 2021), I draw a distinction between what I call macrocontent—the unwieldy long-form copy plastered across browser viewports—and <a href="https://anildash.com/2002/11/13/introducing-microcontent-client/">Anil Dash’s definition of microcontent</a>: the kind of brisk, contextless bursts of content that we find nowadays on Apple Watches, Samsung TVs, and Amazon Alexas.


Today, content also has to be ready for contextless situations—not only in truncated form when we struggle to make out tiny text on our smartwatches or scroll through new television series on Roku but also in places it’s never ended up before. As the twenty-first century continues apace, our clients and our teams are beginning to come to terms with the fact that the way copy is consumed in just a few decades will bear no resemblance whatsoever to the prosaic browsers and even smartphones of today.


<h3>What do we mean by immersive content?</h3>


Immersive experiences are those that, <a href="https://www.cmswire.com/customer-experience/immersive-experiences-be-there-or-be-left-behind/">according to Forrester</a>, blur “the boundaries between the human, digital, physical, and virtual realms” to facilitate smarter, more interactive user experiences. But what do we mean by immersive content? I define immersive content as content that plays in the sandbox of physical and virtual space—copy and media that are situationally or locationally aware rather than rooted in a static, unmoving computer screen.


Whether a space is real or virtual, immersive content (or spatialcontent) will be a key way in which our customers and users deal with information in the coming years. Unlike voice content, which deals with time and sound, immersive content works with space and sight. Immersive content operates not along the axis of links and page changes but rather along situational changes, as the following figure illustrates.


<div class="wp-block-image"><figure class="aligncenter size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/04/situational-change-diagram.png" alt="" class="wp-image-7172894" /><figcaption>In this illustration, each rectangle represents different displays that appear based on situational changes such as movement in space or adjustment of perspective that result in the delivery of different content from the previous context. One of these, such as the rightmost display, can be a web-enabled content display with links to other content presented in the same display. This illustration thus demonstrates two forms of navigation: traditional link navigation and immersive situational navigation.</figcaption></figure></div>


Acknowledging the actual or imagined surroundings of where we are as human beings will have vast implications for content strategy, omnichannel marketing, usability testing, and accessibility. Before we dig deeper, let’s define a few clear categories of immersive content:


<ul><li>Digital signage content. Though it may seem a misnomer, digital signage is one of the most widespread examples of immersive content already in use today. For example, you may have seen it used to display a guide of stores at a mall or to aid wayfinding in an airport. While still largely bound to flat screens, it’s an example of content in space.</li><li>Locational content. Locational content involves copy that is delivered to a user on a personal device based on their current location in the world or within an identified physical space. Most often mediated through Bluetooth low-energy (BLE) beacon technology or GPS location services, it’s an example of content at a point in space.</li><li>Augmented reality content. Unlike locational content, which doesn’t usually adjust itself seamlessly based on how users move in real-world space, AR content is now common in museums and other environments—typically as overlays that are superimposed over actual physical surroundings and adjust dynamically according to the user’s position and perspective. It’s content projected into real-world space.</li><li>Virtual reality content. Like AR content, VR content is dependent on its imagined surroundings in terms of how it displays, but it’s part of a nonexistent space that is fully immersive, an example of content projected into virtual space.</li><li>Navigable content. Long a gimmicky playground for designers and developers interested in pushing the envelope, navigable content is copy that users can move across and sift through as if it were a physical space itself: true content as space.</li></ul>


The following illustration depicts these types of immersive content in their typical habitats.


<figure class="wp-block-image size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/04/types-of-immersive-content.jpg?resize=1024,682" alt="Digital signage content typically appears to everyone within a space. Locational content is delivered via personal devices. AR is content projected into the real world through an overlay, while VR creates an immersive virtual environment. Finally, navigable content is content as the space itself." class="wp-image-7172895" /></figure>


<h3>Why auditing immersive content is important</h3>


Alongside conversational and voice content, immersive content is a compelling example of <a href="https://www.youtube.com/watch?v=I1Chq_E8uBM">breaking content out of the limiting box</a> where it has long lived: the browser viewport, the computer screen, and the 8.5”x11” or broadsheet borders of print media. For centuries, our written copy has been affixed to the staid standards of whatever bookbinders, newspaper printing presses, and screen manufacturers decided. Today, however, for the first time, we’re surmounting those arbitrary barriers and situating content in contexts that challenge all the assumptions we’ve made since the era of Gutenberg—and, arguably, since clay tablets, papyrus manuscripts, and ancient scrolls.


Today, it’s never been more pressing to implement an <a href="https://preston.so/writing/building-usable-conversations-conversational-content-strategy/">omnichannel content strategy</a> that centers the reality our customers increasingly live in: a world in which information can end up on any device, even if it has no tether to a clickable or scrollable setting. One of the most important elements of such a future-proof content strategy is an omnichannel content audit that evaluates your content from a variety of standpoints so you can manage and plan it effectively. These audits generally consist of several steps:


<ul><li>Write a questionnaire. Each content item needs to be examined from the perspective of each channel through a series of channel-relevant questions, like whether content is legible or discoverable on every conduit through which it travels.</li><li>Settle the criteria. No questionnaire is complete for a content audit without evaluation criteria that measure how the content performs and recommendation criteria that determine necessary steps to improve its efficacy.</li><li>Discuss with stakeholders. At the end of any content audit, it’s important to leaf through the results and any recommendations in a frank discussion with stakeholders, including content strategists, editors, designers, and others.</li></ul>


In <a href="https://alistapart.com/article/usability-testing-for-voice-content/">my previous article for A List Apart</a>, I shared the work we did on <a href="https://www.youtube.com/watch?v=kAy6AP-MZ4o">a conversational content audit for Ask GeorgiaGov</a>, the first (but now decommissioned) <a href="https://www.youtube.com/watch?v=evHeWxeznUg">Alexa skill for residents of the state of Georgia</a>. Such a content audit is just one facet of the multifaceted omnichannel content strategy along various dimensions you’ll need to consider. Nonetheless, there are a few things all content audits share in terms of foundational evaluation criteria across all content delivery channels:


<ul><li>Content legibility. Is the content readable or easily consumable from a variety of vantage points and perspectives? In the case of immersive content, this can include examining verbosity tolerance (how long content can be before users zone out, a big factor in digital signage) and phantom references (like links and calls to action that make sense on the web but not on a VR headset).</li><li>Content discoverability. It’s no longer guaranteed in immersive content experiences that every piece of content can be accessed from other content items, and content loses almost all of its context when displayed unmoored from other content in digital signs or AR overlays. For discoverability’s sake, avoid relegating content to unreachable siloes, whether content is inaccessible due to physical conditions (like walls or other obstacles) or technical ones (like a finicky VR headset).</li></ul>


Like voice content, immersive content requires ample attention to the ways in which users approach and interact with content in physical and virtual spaces. And as I write in Voice Content and Usability, it’s also the case that cross-channel interactions can influence how we work with copy and media. After all, how often do subway and rail commuters glance up while scrolling through service advisories on their smartphones to consult a potentially more up-to-date alert on a digital sign?


<h2>Digital signage content: Content in space</h2>


Signage has long been a fixture of how we find our way through physical spaces, ever since the earliest roads crisscrossed civilizations. Today, digital signs are becoming ubiquitous across shopping centers, university campuses, and especially transit systems, with the New York City subway recently introducing countdown clocks that display service advisories on a ticker along the bottom of the screen, just below train arrival times.


Digital signs can deliver critical content at important times, such as during emergencies, without the limitations imposed by the static nature of analog signs. News tickers on digital signs, for instance, can stretch for however long they need to, though succinctness is still highly prized. But digital signage’s rich potential to deliver immersive content also presents challenges when it comes to content modeling and governance.


Are news items delivered to digital signs simply teaser or summary versions of full articles? Without a fully functional and configurable digital sign in your office, how will you preview them in context before they go live? To solve this problem for the New York City subway, the Metropolitan Transportation Authority (MTA) <a href="https://www.acquia.com/resources/case-studies/metropolitan-transportation-authority">manages all digital signage content across all signs</a> within a central Drupal content management system (CMS), which synthesizes data such as train arrival times from real-time feeds and transit messages administered in the CMS for arbitrary delivery to any platform across the network.


How to present content items in digital signs also poses problems. As the following figure illustrates, do you overtake the entire screen at the risk of obscuring other information, do you leave it in a ticker that may be ignored, or do you use both depending on the priority or urgency of the content you’re presenting?


<div class="wp-block-image"><figure class="aligncenter size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/04/digital-signage-info-priority.png" alt="On the left are examples of digital signage where informational messages obscure important data. On the right are examples of digital signage where informational messages are constricted to a small scrolling ticker at the bottom of the screen." class="wp-image-7172896" /></figure></div>


While some digital signs have the benefit of touch screens and occupying entire digital kiosks, many are tasked with providing key information in as little space as possible, where users don’t have the luxury of manipulating the interface to customize the content they wish to view. The New York City subway makes a deliberate choice to allow urgent alerts to spill across the entire screen, which limits the sign’s usefulness for those who simply need to know when the next train is arriving in the interest of more important information that is relevant to all passengers—and those who need captions for loudspeaker announcements.


<h3>Auditing for digital signage content</h3>


Because digital signs value brevity and efficiency, digital signage content often isn’t the main focus of what’s displayed. Digital signs on the São Paulo metro, for instance, juggle service alerts, breaking news, and health advisories. For this reason, auditing digital signage content for legibility and discoverability is key to ensuring users can interact with it gracefully, regardless of how often it appears, how highly prioritized it is, or what it covers.


When it comes to legibility, ask yourself these questions and consider the digital sign content you’re authoring based on these concerns:


<ul><li>Font size and typography. Many digital signs use sans-serif typefaces, which are easier to read from a distance, and many also employ uppercase for all text, especially in tickers. Consider which typefaces advance rather than obscure legibility, even when the digital sign content overtakes the entire screen.</li><li>Angles and perspective. Is your digital sign content readily readable from various angles and various vantage points? Does the reflectivity of the screen impact your content’s legibility when standing just below the sign? How does your content look when it’s displayed to a user craning their neck and peering at it askew?</li><li>Color contrast and lighting. Digital signs are no longer just fixtures of subterranean worlds; they’re above-ground and in well-lit spaces too. Color contrast and lighting strongly influence how legible your digital sign content can be.</li></ul>


As for discoverability, digital signs present challenges of both physical discoverability (can the sign itself be easily found and consulted?) and content discoverability (how long does a reader have to stare at the sign for the content they need to show up?):


<ul><li>Physical discoverability. Are signs placed in prominent locations where users will come across them? The MTA was criticized for <a href="https://www.amny.com/transit/subway-countdown-clocks-at-some-stations-are-difficult-to-see-riders-say-1-14115447/">the poor placement of many of its digital countdown clocks</a> in the New York City subway, something that can block a user from ever accessing content they need.</li><li>Content discoverability. Because digital signs can only display so much content at once, even if there’s a large amount of copy to deliver eventually, users of digital signs may need to wait too long for their desired content to appear, or the content they seek may be too deprioritized for it to show up while they’re looking at the sign.</li></ul>


Both legibility and discoverability of digital sign content require thorough approaches when authoring, designing, and implementing content for digital signs.


<h3>Usability and accessibility in digital signage content</h3>


In addition to audits, in any physical environment, immersive content on digital signs requires a careful and bespoke approach to consider not only how content will be consumed on the sign itself but also all the ways in which users move around and refer to digital signage as they consult it for information. After all, our content is no longer couched in a web page or recited by a screen reader, both objects we can control ourselves; instead, it’s flashed and displayed on flat screens and kiosks in physical spaces.


Consider how the digital sign and the content it presents appear to people who use mobility aids such as wheelchairs or walkers. Is the surrounding physical environment accessible enough so that wheelchair users can easily read and discover the content they seek on a digital sign, which may be positioned too high for a seated reader? By the same token, can colorblind and dyslexic people read the chosen typeface in the color scheme it’s rendered in? Is there an aural equivalent of the content for Blind people navigating your digital signage, in close proximity to the sign itself, serving as synchronized captions?


<h2>Locational content: Content at a point in space</h2>


Unlike digital signage content, which is copy or media displayed in a space, locational (or geolocational) content is copy or media delivered to a device—usually a phone or watch—based on a point in space (if precise location is acquired through GPS location services) or a swath of space (typically driven by Bluetooth Low Energy beacons that have certain ranges). For smartphone and smartwatch users, GPS location services can often pinpoint a relatively accurate sense of where a person is, while Bluetooth Low Energy (BLE) beacons can triangulate their position based on devices that have Bluetooth enabled.


<div class="wp-block-image"><figure class="aligncenter size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/04/locational-content.png" alt="Examples of locational content might include links to more detailed information online, coupons, and sales relevant to merchandise or objects near the person viewing it." class="wp-image-7172897" /></figure></div>


Though BLE beacons remain a fairly finicky and untested realm of spatial technology, they’ve quickly gained traction in large shopping centers and <a href="https://www.youtube.com/watch?v=I2MuPdt5anI">public spaces such as airports</a> where users agree to receive content relevant to their current location, most often in the form of push notifications that whisk users away into a separate view with more comprehensive information. But because these tiny chunks of copy are often tightly contained and contextless, teams designing for locational content need to focus on how users interact with their devices as they move through physical spaces.


<h3>Auditing for locational content</h3>


Fortunately, because locational content is often delivered to the same visual devices that we use on a regular basis—smartphones, smartwatches, and tablets—auditing for content legibility can embrace many of the same principles we employ to evaluate other content. For discoverability, some of the most important considerations include:


<ul><li>Locational discoverability. BLE beacons are notorious for their imprecision, though they continue to improve in quality. GPS location, too, can be an inaccurate measure of where someone is at any given time. The last thing you want your customers to experience is an incorrect triangulation of where they are leading to embarrassing mistakes and bewilderment when unexpected content travels down the wire.</li><li>Proximity. Because of the relative lack of precision when it comes to BLE beacons and GPS location services, placing content items too close together in a coordinate map may trigger too many notifications or resource deliveries to a user, thus overwhelming them, or a certain content item may inadvertently supersede another because they’re spaced too closely together.</li></ul>


As push notifications and location sharing become more common, locational content is rapidly becoming an important way to funnel users toward somewhat longer-form content that might otherwise go unnoticed when a customer is in a brick-and-mortar store.


<h3>Usability and accessibility in locational content</h3>


Because locational content requires users to move around physical spaces and trigger triangulation, consider how different types of users will move and also whether unforeseen issues can arise. For example, researchers in Japan found that users who walk while staring at their phones are <a href="https://www.nytimes.com/2021/03/18/science/distracted-walking-phone.html">highly disruptive to the flow and movement of those around them</a>. Is your locational content possibly creating a situation where users bump into others, or worse, get into accidents? For instance, writing copy that’s quick and to the point or preventing notifications from being prematurely dismissed could allow users to ignore their devices until they have time to safely glance at them.


Limited mobility and cognitive disabilities can place many disabled users of locational content at a deep disadvantage. While gamification may encourage users to seek as many items of locational content as possible in a given span of time for promotional purposes, consider whether it excludes wheelchair users or people who encounter obstacles when switching between contexts rapidly. There are good use cases for locational content, but what’s compelling for some users might be confounding for others.


<h2>AR and VR content: Content projected into space</h2>


Augmented reality, once the stuff of science fiction holograms and futuristic cityscapes, is becoming more available to the masses thanks to wearable AR devices, high-performing smartphones and tablets, and innovation in machine vision capabilities, though the utopian future of true “holographic” content remains as yet unrealized. Meanwhile, virtual reality has seen incredible growth over the pandemic as homebound users—by interacting with copy and media in fictional worlds—increasingly seek escapist ways to access content normally spread across flat screens.


While AR and VR content is still in its infancy, the vast majority is currently couched in overlays that are superimposed over real-world environments or objects and can be opaque (<a href="https://commons.wikimedia.org/wiki/File:Augmented_reality_at_Museu_de_Matar%C3%B3_linking_to_Catalan_Wikipedia_%2818%29.JPG">occupying some of a device’s field of vision</a>) or semi-transparent (creating an eerie, shimmery film on which text or media is displayed). Thanks to advancements in machine vision, these content overlays can track the motion of perceived objects in the physical or virtual world, bamboozling us into thinking these overlays are traveling in our fields of vision just like the things we see around us do.


Formerly restricted to realms like museums, expensive video games, and gimmicky prototypes, AR and VR content is now becoming much more popular among companies that are <a href="https://www.forbes.com/sites/theyec/2019/02/06/augmented-reality-in-business-how-ar-may-change-the-way-we-work/">interested in more immersive experiences</a> capable of <a href="https://www.information-age.com/augmented-reality-revolutionising-way-people-shop-123469739/">delivering content alongside objects</a> in real-life brick-and-mortar environments, as well as virtual or imagined landscapes, like fully immersive brand experiences that transport customers to a pop-up store in their living room.


To demonstrate this, my former team at Acquia Labs built an experimental proof of concept that examines <a href="https://dri.es/virtual-reality-on-campus-with-drupal">how VR content can be administered within a CMS</a> and a pilot project for grocery stores that explores what can happen when <a href="https://dri.es/shopping-with-augmented-reality">product information is displayed as AR content</a> next to consumer goods in supermarket aisles. The following illustration shows, in the context of this latter experiment, how a smartphone camera interacts with a machine vision service and a Drupal CMS to acquire information to render alongside the item.


<div class="wp-block-image"><figure class="aligncenter size-large"><img src="https://149572954.v2.pressablecdn.com/wp-content/uploads/2021/04/ar-cms-example.jpg" alt="A diagram depicting how someone might look at a physical object through their phone, and AR tools can connect to a CMS to download and display relevant information about the object virtually beside it." class="wp-image-7172898" /></figure></div>


<h3>Auditing for AR and VR content</h3>


Because AR and VR content, unlike other forms of immersive content, fundamentally plays in the same sandbox as the real world (or an imaginary one), legibility and discoverability can become challenging. The potential risks for AR and VR content are in many regards a fusion of the problems found in both digital signage and locational content, encompassing both physical placement and visual perspective, especially when it comes to legibility:


<ul><li>Content visibility. Is the AR or VR overlay too transparent to comfortably read the copy or view the image contained therein, or is it so opaque that it obscures its surroundings? AR and VR content must coexist gracefully with its exterior, and the two must enhance rather than obfuscate each other. Does the way your content is delivered compromise a user’s feeling of immersion in the environment behind it?</li><li>Content perspective. Unless you’re limited to a smartphone or similar handheld device, many AR and VR overlays, especially in immersive headsets, don’t display content or media as an immobile rectangular box, as it defeats the purpose of the illusion and can be jarring to users as they adjust their field of vision, breaking them out of the fantasy you’re hoping to create. For this reason, your AR or VR experience must not only dictate how environments and objects are angled and lit but also how the content associated with them is perceived. Is your content readable from various angles and points in the AR view or VR world?</li></ul>


When it comes to discoverability of your AR and VR content, issues like accuracy in machine vision and triangulation of your user’s location and orientation become much more important:


<ul><li>Machine vision. Most relevantly for AR content, if your copy or media is predicated on machine vision that perceives an object by identifying it according to certain characteristics, how accurate is that prediction? Does some content go undiscovered because certain objects go undetected in your AR-enabled device?</li><li>Location accuracy. If your content relies on the user’s current location and orientation in relation to some point in space, as is common in both AR and VR content use cases, how accurately do devices dictate correct delivery at just the right time and place? Are the ranges within which content is accessible too limited, leading to flashes of content as you take a step to the left or right? Are there locations that simply can’t be reached, leading to forever-siloed copy or media?</li></ul>


Due to the intersection of technical considerations and design concerns, AR and VR content, like voice content and indeed other forms of immersive content, requires a concerted effort across multiple teams to ensure resources are delivered not just legibly but also discoverably.


<h3>Usability and accessibility in AR and VR content</h3>


Out of all the forms of immersive content we’ve covered so far, AR and VR content is possibly the medium that demands the most assiduously crafted solutions in accessibility testing and usability testing. Because AR and VR content, especially in headsets or wearable devices, requires motion through real or imagined space, its impact on accessibility cannot be overstated. Adding a third dimension—and arguably, a fourth: time—to our perception of content requires attention not only to how content is accessed but also all the other elements that comprise a fully immersive visual experience.


VR headsets commonly induce <a href="https://abcnews.go.com/Technology/feel-motion-sickness-virtual-reality/story?id=65153805">virtual reality motion sickness</a> in many individuals. Poorly implemented transitions between states occurring in quick succession where content is visible and then invisible, and then visible again, can lead to epileptic seizures if not built with the utmost care. Finally, users moving quickly through spaces may inadvertently trigger vertigo in themselves or even collide with hazardous objects, resulting in potentially serious injuries. There’s a reason we aren’t wearing wearable headsets outside carefully secured environments.


<h2>Navigable content: Content as space</h2>


This is only the beginning of immersive content. Increasingly, we’re also toying with ideas that seemed harebrained even a few decades ago, like navigable content—copy and media that can be traversed as if the content itself were a navigable space. Imagine zooming in and out of tracts of text and stepping across glyphs like hopping between islands in a Super Mario game. Ambitious designers and developers are exploring this emerging concept of navigable content in exciting ways, both in and out of AR and VR. In many ways, truly navigable content is the endgame of how virtual reality presents information.


Imagining an encyclopedia that we can browse like the classic <a href="https://www.youtube.com/watch?v=jR0vRuZkxdw">1990s opening sequence of the BBC’s Eyewitness television episodes</a> is no longer as far-fetched as we think. Consider, for instance, <a href="http://www.rleonardi.com/interactive-resume/">Robby Leonardi’s interactive résumé</a>, which invites you to play a character as you learn about his career, or <a href="https://bruno-simon.com/">Bruno Simon’s ambitious portfolio</a>, where you drive an animated truck around his website. For navigable content, the risks and rewards for user experience and accessibility remain largely unexplored, just like the hazy fringes of the infinite maps VR worlds make possible.


<h2>Conclusion</h2>


The story of immersive content is in its early stages. As newly emerging channels for content see greater adoption, requiring us to relay resources like text and media to never-before-seen destinations like digital signage, location-enabled devices, and AR and VR overlays, the demands on our content strategy and design approaches will become both fascinating and frustrating. As seemingly fantastical new interfaces continue to emerge over the horizon, we’ll need an omnichannel content strategy to guide our own journeys as creatives and to orient the voyages of our users into the immersive.


Content audits and effective content strategies aren’t just the domain of staid websites and boxy mobile or tablet interfaces—or even <a href="https://preston.so/books/voice-content">aurally rooted voice interfaces</a>. They’re a key component of our increasingly digitized spaces, too, cornerstones of immersive experiences that beckon us to consume content where we are at any moment, unmoored from a workstation or a handheld. Because it lacks long-standing motifs of the web like context and clickable links, immersive content invites us to revisit our content with a fresh perspective. How will immersive content reinvent how we deliver information like the web did only a few decades ago, like voice has done in the past ten years?


Only the test of time, and the allure of immersion, will tell.
]]> </description>
<dc:subject>
<![CDATA[Content Strategy, Usability, User Experience]]> </dc:subject>
<dc:date>
2021-04-29T14:00:00+00:00 </dc:date>
</item>
</channel>
</rss>

Home · About · News · Docs · Terms