Category: Blog

The same holds true for those of us who are currently employed in design and development. Having worked on the web for about three years at this point, I’ve seen the typical wax and wane of concepts, strategies, and systems. Every day we as developers and designers re-enter a routine music, a brand-new concept or technology emerges to shake things up and completely alter our world.

How we got below

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 table elements, often with empty cells containing a single pixel spacer GIF to add empty space. We styled text with numerous font 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.

The beginning of website standards

At the turn of the century, a new cycle started. Crufty code littered with table layouts and font tags waned, and a push for web standards waxed. Newer technologies like CSS 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 W3C and browser vendors and heavy evangelism from folks like the Web Standards Project to build standards. A List Apart 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 progressive enhancement introduced the idea that content should be available for all browsers—with additional enhancements available for more advanced browsers. Meanwhile, sites like the CSS Zen Garden showcased just how powerful and versatile CSS can be when combined with a solid semantic HTML structure.

Server-side language like PHP, Java, and.NET took Perl as the primary back-end computers, and the cgi-bin was tossed in the garbage bin. With these better server-side instruments came the first time of online applications, starting with content-management systems ( especially in the blog space with tools like Blogger, Grey Matter, Movable Type, and WordPress ). AJAX opened the door to asynchronous interaction between the front end and back end in the mid-2000s. Suddenly, pages could update their content without needing to reload. A crop of JavaScript frameworks, including Prototype, YUI, and jQuery, were created to aid developers in creating more trustworthy client-side interactions across browsers with wildly varying standards support. Techniques like image replacement enable skilled designers and developers to use 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. As designers and developers explored more diversified styles and layouts, web design flourished. However, we still relied heavily on hacks. When it came to basic layout and text styling, early CSS was a significant improvement over table-based layouts, but its limitations at the time meant that designers and developers still relied heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds for the appearance of full-length columns (among other hacks ). All kinds of nested floats or absolute positioning ( or both ) were necessary for complicated layouts. The big five’s typefaces were widely varied, and flash and image replacement for custom fonts was a great first step, but both hacks caused accessibility and performance issues. And JavaScript libraries made it simple for anyone to add a dash of interaction to pages, even at the expense of double, even quadrupling, the download size of basic websites.

The web as software platform

The interplay between the front end and the back end continued to grow, which led to the development of 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 used for linked documents turned into a world with limitless possibilities.

At the same time, mobile devices became more capable, and they gave us internet access in our pockets. Mobile applications and responsive design opened up opportunities for fresh interactions anytime, anywhere.

This fusion of potent mobile devices and potent development tools contributed to the growth of social media and other centralized tools for user interaction and consumption. 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 made connections on a global scale, with both positive and negative outcomes.

Want to learn more about how we came to be where we are today, along with some other suggestions for improvement? ” Of Time and the Web” was written by Jeremy Keith. Or check out the” Web Design History Timeline” at the Web Design Museum. Additionally, Neal Agarwal takes a fascinating tour of” Internet Artifacts.”

Where we are now

In the last couple of years, it’s felt like we’ve begun to reach another major inflection point. As social-media platforms fracture and wane, there’s been a growing interest in owning our own content again. From the tried-and-true classic of hosting plain HTML files to static site generators and content management systems of all kinds, there are many different ways to create websites. Social media fracturing also has a price: we lose essential infrastructure for discovery and connection. Webmentions, RSS, ActivityPub, and other tools of the IndieWeb can help with this, but they’re still relatively underimplemented and hard to use for the less nerdy. Without discovery and connection, it can feel as though we could be shouting into the void when we can create incredible personal websites and continually update them.

Browser support for CSS, JavaScript, and other standards like web components has accelerated, especially through efforts like Interop. In a fraction of the time that they once did, new technologies gain universal support. When I first learn about a new feature, I frequently discover that its coverage is already over 80 % when I check the browser support. Browser support is frequently the only obstacle to using newer techniques today, rather than the time it takes to train and adopt new techniques.

Today, with a few commands and a couple of lines of code, we can prototype almost any idea. With today’s abundance of tools, starting something new is now simpler than ever. However, as we upgrade and maintain these frameworks, we eventually pay the upfront costs that these frameworks may initially save in terms of our technical debt.

Adopting new standards can sometimes take longer if we rely on third-party frameworks because we might 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. Users must wait for scripts to load before being able to read or interact with pages because these same frameworks frequently come with performance costs. And when scripts fail ( whether through poor code, network issues, or other environmental factors ), there’s often no alternative, leaving users with blank or broken pages.

Where do we go from here?

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 refuse to acknowledge that they are hacks or when we refuse to take their place. What can we do to create the web’s future that we want?

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 right now, 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 gotten used to. And occasionally it’s preventing you from choosing better options.

Start from standards. Standards change over time, but browsers have done a remarkably good job of staying current with outdated standards. The same isn’t always true of third-party frameworks. Even the most advanced HTML from the 1990s still function flawlessly today. The same can’t always be said of websites created with frameworks even after a few years.

Design with care. Whether your craft is code, pixels, or processes, consider the impacts of each decision. Many modern tools have the convenience of making the necessary decisions that have led to its design and not always considering the effects those decisions can have. Use the time saved by modern tools to think more carefully and make decisions with care rather than rushing to “move fast and break things”

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. Even if you were to concentrate solely on learning standards, you might end up focusing on something that won’t matter next year. ( Remember XHTML? ) However, ongoing learning opens up new connections in your brain, and the techniques you learn in one day may be used to guide different experiments in the future.

Play, experiment, and be weird! This web that we’ve built is the ultimate experiment. Despite being the single largest human endeavor in history, each of us has the ability to make our own money out of it. Be courageous and try new things. Build a playground for ideas. In your own bizarre science lab, perform bizarre experiments. Start your own small business. 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. Write something for A List Apart! But take the time to amplify others too: find new voices, learn from them, and share what they’ve taught you.

Go forth and make

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 something that you are only qualified to make for yourself. 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.

I’d like you to consider this a “yes … and” piece to complement Joe’s post. Instead of refuting everything he’s saying, I’m pointing out some areas where AI may produce real, positive impacts on people with disabilities. To be clear, I’m not saying that there aren’t true threats or pressing problems 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 hope that we’ll get there one day.

Other words

Joe’s article spends a lot of time addressing computer-vision types ‘ ability to create other words. He raises a lot of valid points about the state of the world right now. And while computer-vision concepts continue to improve in the quality and complexity of information in their information, their benefits aren’t wonderful. He argues to be accurate that the state of image research is currently very poor, especially for some graphic types, in large part due to the lack of context-based analysis that exists in the AI systems ( which is a result 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. However, I still think there’s possible in this area.

As Joe mentions, human-in-the-loop publishing of alt word should definitely be a factor. And if AI can intervene to provide a starting place for alt text, even if the swift might say What is this BS? That’s certainly correct at all … Let me try to offer a starting point— I think that’s a win.

If we can specifically station a design to examine image usage in context, it might help us more quickly determine which images are likely to be elegant and which ones are likely to need a description. That will help clarify which situations require image descriptions, and it will increase authors ‘ effectiveness in making their pages more accessible.

The image example provided in the GPT4 announcement provides an interesting opportunity as well, even though complex images like graphs and charts are challenging to describe in any kind of succinct way ( even for humans ). Let’s say you came across a chart that was simply the title of the chart and the type of visualization it was: Pie chart comparing smartphone usage to feature phone usage among US households making under$ 30, 000 annually. ( That would be a pretty bad alt text for a chart because it frequently leaves many unanswered questions about the data, but let’s just assume that was the description in place. ) Imagine a world where users could ask questions about the graphic if your browser knew that that image was a pie chart ( because an onboard model concluded this ).

• Do more people use feature phones or smartphones?
• How many more?
• Exists a group of people who don’t fall under either of these categories?
• How many is that?

Setting aside the realities of large language model ( LLM) hallucinations—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 might also be useful in educational settings to assist those who can, as is, comprehend the data contained in these charts.

What if you could ask your browser to make a complicated chart simpler? What if you asked it to separate a single line from a line graph? What if you could ask your browser to change the color combinations in your browser so that it works better for your type of color blindness? What if you could ask it to switch 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 specially designed model that could take the data 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!

Matching algorithms

When Safiya Umoja Noble chose to put her book Algorithms of Oppression, she hit the nail on the head. Although her book focused on the ways that search engines can foster racism, I believe it’s equally true that all computer models have the potential to foster conflict, prejudice, and intolerance. We all know know that poorly designed and maintained algorithms are incredibly harmful, whether it’s Twitter that keeps bringing you the most recent tweet from a drowsy billionaire, YouTube that keeps us in a q-hole, or Instagram that keeps us guessing what natural bodies look like. A large portion of this is attributable to the lack of diversity in those who create and shape them. When these platforms are built with inclusively baked in, however, there’s real potential for algorithm development to help people with disabilities.

Take Mentra, for example. They serve as a network of employment for people who are neurodivers. Based on more than 75 data points, they match job seekers with potential employers using an algorithm. 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. Mentra made the decision to change the script when it came to traditional employment websites because it was run by neurodivergent people. They lower the emotional and physical labor on the job-seeker side of things by recommending available candidates to companies who can then connect with job seekers they are interested in.

When more people with disabilities are involved in the development of algorithms, this can lower the likelihood that these algorithms will harm their communities. That’s why diverse teams are so important.

Imagine if the social media company’s recommendation engine was tuned to prioritize follow recommendations for people who discussed topics similar to those that were important but who were not in your current sphere of influence in any significant way. For instance, if you followed a group of nondisabled white male academics who spoke about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also speak 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.

Other ways that AI can helps people with disabilities

If I weren’t attempting to combine this with other tasks, I’m sure I could go on and on, giving various examples of how AI could be used to assist people with disabilities, but I’m going to make this last section into a bit of a lightning round. In no particular order:

Voice preservation. You may have seen the VALL-E paper or Apple’s Global Accessibility Awareness Day announcement or you may be familiar with the voice-preservation offerings from Microsoft, Acapela, or others. People who have ALS ( Lou Gehrig’s disease ), motor-neuron disease, or other medical conditions that can prevent them from talking can greatly benefit from having an AI model that can mimic your voice. 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 responsibly, but the tech has truly transformative potential.
• Voice recognition. Researchers are assisting people with disabilities in the collection of recordings of people with atypical speech, thanks to the assistance of the Speech Accessibility Project. 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. More people with disabilities will be able to use voice assistants, dictation software, and voice-response services as a result of this research, which will result in more inclusive data sets that will enable them to use their computers and other devices more easily and with just their voices.
• Text transformation. The most recent generation of LLMs is quite capable of changing existing text without giving off hallucinations. This is incredibly empowering for those who have cognitive disabilities and who may benefit from text summaries, simplified versions, or even text that has been prepared for Bionic Reading.

The value of various teams and sources of data

We must acknowledge that our differences matter. The intersections of the identities we exist in have an impact on our lived experiences. These lived experiences—with all their complexities ( and joys and pain ) —are valuable inputs to the software, services, and societies that we shape. The data we use to train new models must be based on our differences, and those who provide it to us need to be compensated for doing so. Stronger models can be created using inclusive data sets, which lead to more equitable outcomes.

Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that you include information about disabilities that has been written by people with a variety of disabilities in the training data.

Want a model that doesn’t use ableist language? Before ableist language reaches readers, you might be able to use already-existing data sets to create a filter that can intercept and correct it. That being said, when it comes to sensitivity reading, AI models won’t be replacing human copy editors anytime soon.

Want a copilot for coding that provides recommendations that are accessible after the jump? Train it on code that you know to be accessible.

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.

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.

I am a artistic. What I do is alchemy. It is a puzzle. Instead of letting it get done by me, I do it.

I am a artistic. Certainly all creative people approve of this brand. No everyone sees themselves in this way. Some innovative people practice technology in their work. That is their reality, and I regard it. Sometimes I even envy them, a minor. But my approach is different—my becoming is unique.

Apologizing and qualifying in progress is a diversion. My mind uses that to destroy me. I’ll leave it alone for today. I may forgive and be qualified at any time. After I’ve said what I originally said. Which is challenging enough.

Except when it is simple and flows like a wine valley.

Sometimes it does go that approach. Maybe I have to make something right away. When I say something at that moment, I’ve learned not to say it because people often don’t work hard enough to acknowledge that the idea is the best idea even when you know it’s the best idea.

Sometimes I just keep working until the plan strikes me. Maybe it arrives right away and I don’t remind people for three weeks. Maybe I get so excited about something that just happened that I blurt it out and didn’t stop myself. like a child who discovered a medal in one of his Cracker Jacks. I occasionally manage to get away with this. Maybe other people agree: yes, that is the best idea. Most times they don’t and I regret having given way to passion.

Passion should only be saved for the meet, when it matters. not the informal gathering that two different gatherings precede that meeting. Anyone knows why we have all these discussions. We keep saying we’re going to get rid of them, but we just keep trying to find different ways to get them. They occasionally yet excel. But occasionally they detract from the actual labor. The percentages between when conferences are important, and when they are a sad distraction, vary, depending on what you do and where you do it. also who you are and what you do. Once I digress. I am a innovative. That is the topic.

Often, a lot of hours of diligent and diligent work ends up with something that is barely useful. Maybe I have to take that and move on to the next task.

Don’t question about approach. I am a innovative.

I am a innovative. I don’t handle my goals. And I don’t handle my best tips.

I can nail aside, surround myself with information or photos, and maybe that works. I can go for a walk, and occasionally that functions. There is no connection between sizzling fuel and flowing pots, and I may be making dinner. I frequently have a sense of direction when I awaken. The idea that may have saved me disappears almost as frequently as I become aware and part of the world once more in a mindless breeze of oblivion. For imagination, I believe, comes from that other planet. The one we enter in aspirations, and possibly, before conception and after death. But that’s for writers to know, and I am not a writer. I am a artistic. Theologians are encouraged to build massive armies in their artistic globe, which they insist is genuine. But that is another diversion. And a sad one. Possibly on a much bigger issue than whether or not I am creative. But that’s not how I came around, though.

Often the process is mitigation. And hardship. You know the cliché about the tortured designer? 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 individuals who detest the idea of being called artistic perhaps been closeted artists, but that’s between them and their gods. No offence meant. Your wisdom is correct, too. However, mine is for me.

Creatives understand artists.

Disadvantages know cons, just like real rappers recognize actual rappers, just like queers recognize queers. Creatives feel enormous regard for creatives. We love, respect, emulate, and nearly deify the excellent ones. To idolize any man is, of course, a dreadful mistake. We have been warned. We know much. We know people are really people. They dispute, they are depressed, they regret their most critical decisions, they are weak and thirsty, they can be cruel, they can be just as terrible as we can, if, like us, they are clay. But. But. However, they produce this incredible issue. They give birth to something that may not exist without them and did not exist before them. They are the inspirations ‘ parents. And I suppose, since it’s only lying it, I have to put that they are the mother of technology. Ba ho backside! Okay, that’s done. Continue.

Creatives disparage our personal small successes, because we compare them to those of the wonderful people. Wonderful video! Also, I‘m no Miyazaki. Now THAT is glory. That is brilliance straight out of the mouth of God. This half-starved small item that I made? It essentially fell off the turnip vehicle. And the carrots weren’t even clean.

Creatives knows that, at best, they are Salieri. Yet Mozart’s original artists hold that opinion.

I am a artistic. I haven’t worked in advertising in 30 years, but in my hallucinations, it’s my previous artistic managers who judge me. And they are correct to do so. I am very lazy, overly simplistic, and when it actually counts, my mind goes blank. There is no supplement for artistic function.

I am a artistic. Every project I create has a goal that makes Indiana Jones appear older and snoring in a balcony head. The more I pursue creativity, the faster I can complete my work, and the longer I obsess over my ideas and whizz around in circles before I can complete that task.

I can move ten times more quickly than those who aren’t innovative, those who have just been creative for a short while, and those who have just had a short time of creative work. Only that I work twice as quickly as they do, putting the work away, just before I do it, When I put my mind to it, I am so confident in my ability to do a fantastic work. I am that attached to the excitement scramble of delay. I also have a fear of the climb.

I am not an actor.

I am a artistic. Not an actor. Though I dreamed, as a child, of eventually being that. Some of us criticize our abilities and fear our own selves because we are not Michelangelos and Warhols. That is narcissism—but at least we aren’t in elections.

I am a innovative. Though I believe in reason and science, I decide by intelligence and desire. And sit with what follows—the disasters as well as the successes.

I am a innovative. Every term I’ve said these may offend another artists, who see things differently. Ask two artists a problem, get three ideas. Our dispute, our enthusiasm about it, and our responsibility to our own reality are, at least to me, the facts that we are artists, no matter how we may think about it.

I am a artistic. I lament my lack of taste in the areas of human knowledge that I know quite small, that is to say about everything. And I trust my preference above all other items in the regions closest to my soul, or perhaps, more precisely, to my passions. Without my passions, I had probably have to spend time staring living in the eye, which almost none of us can do for very long. No actually. No really. Because many in existence, if you really look at it, is terrible.

I am a artistic. I believe, as a family believes, that when I am gone, some little good part of me will take on in the head of at least one other people.

Working frees me from worrying about my job.

I am a artistic. I fear that my little present will disappear without warning.

I am a innovative. I’m too busy making the next thing to devote too much time to it, especially since practically everything I create did achieve the level of success I conceive of.

I am a artistic. I think method is the most amazing secret. I think it is so important that I’m actually foolish enough to publish an essay I wrote into a small machine without having to go through or edit it. I didn’t do this generally, I promise. But I did it right away because I was even more frightened of forgetting what I was saying because I was afraid of you seeing through my sad movements toward the beautiful.

There. I think I’ve said it.

Humility, a writer’s necessary value—that has a good ring to it. What about sincerity, an business manager’s vital value? Or a surgeon’s? Or a teacher’s? They all good wonderful. When humility is our guiding light, the course is usually available for fulfillment, development, relation, and commitment. In this book, we’re going to discuss about why.

That said, this is a guide for developers, and to that conclusion, I’d like to begin with a story—well, a voyage, actually. It’s a personal one, and I’m going to make myself prone as well. I call it:

The Tale of Justin’s Preposterous Pate

When I was coming out of arts school, a long-haired, goateed novice, write was a known quantity to me, design on the web, however, was riddled with complexities to understand and learn, a problem to be solved. Though I had been fully trained in graphic design, font, and design, what fascinated me was how these classic skills may be applied to a budding online landscape. In the end, this topic may determine my career’s direction.

So I devoured HTML and JavaScript novels into the wee hours of the morning and self-taught myself how to code during my freshman year rather than student and go into print like many of my companions. I needed to understand the main ramifications of what my style choices may ultimately result in when rendered in a website.

The later ‘ 90s and early 2000s were the so-called” Wild West” of web design. Developers at the time were all trying to figure out how to incorporate design and visual connection into the online landscape. What were the laws? How may we break them and also engage, entertain, and present information? At a more micro level, how was my values, inclusive of modesty, admiration, and link, coincide in combination with that? I was looking for answers.

Those are amazing factors between non-career relationships and the world of design, even though I’m referring to a different era. What are your main passions, or ideals, that elevate medium? The main themes remain the same, much like the clear parallels between what fulfills you, who is independent of the physical or digital worlds.

First within tables, animated GIFs, Flash, then with Web Standards, divs, 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. On this one, I worked with fellow designer and dear friend Marc Clancy, who is now a co-founder of the creative project organizing app Milanote, to sketch and then play with various user interactions. Then, I’d break it down and code it into a digital layout.

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.

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 provided many of the custom downloads I previously mentioned as being accessible on my folio website but with a GUI Galaxy theme and branding.

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 creating something bigger than just one of us and establishing a global audience.

Collaboration and connection transcend media, which have a huge impact on my design career.

Why am I going down this design memory lane with you, now? 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. There’s a good chance you’ve seen a website with a hero image or banner with text overlay ( possibly with a lovely rotating carousel of images ), a call to action, and three columns of sub-content directly beneath. Perhaps an icon library is used with selections that only vaguely relate to their respective content is used.

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 user-friendly presentation that connects with people wherever they are. 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.

Pixel Problems

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

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. Under such absurd constraints, this seemed to me to be the embodiment of digital visual communication. And frequently, ridiculous limitations can lead to 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 32×32 pixel grid with that 256-color palette. These absurd restrictions imposed a clarity of concept and presentation that I found incredibly appealing. I was thrown the digital gauntlet, and that challenge fueled my determination. 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 that made use of ResEdit, the only program I had at the time, to create icons. ResEdit was a clunky, built-in Mac OS utility that was not specifically designed for our needs. At the core of all of this work: Research. Challenge. Problem- solving. Again, these core connection-based values are agnostic of medium.

One more design portal that I want to mention also serves as the second reason for my story to connect this all.

This is K10k, short for Kaliber 1000. Michael Schmidt and Toke Nygaard founded K10k in 1998, which served as the web’s design news source at the time. 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. The concept of GUI Galaxy was inspired by what these people were doing, respect where respect is due.

For my part, I gained some notoriety in the design industry as a result of combining my web design work with my pixel art exploration. K10k eventually figured out that I was one of their very limited group of news writers who could contribute content to the website.

Amongst my personal work and side projects —and now with this inclusion—in the design community, this put me on the map. Additionally, my design work has started to appear on other design news portals, as well as be published in various printed collections, in domestic and international magazines, and in various printed collections. 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 ). What satisfied me was the praise and the press, which went on to completely alter my mind. They inflated my ego. I actually felt a little better than my fellow designers.

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

I effectively stopped researching and discovering because I was so confident in my abilities. When my first instinct was to sketch concepts or iterate ideas in lead, I instead leaped right into Photoshop. I got my inspiration from the tiniest of sources ( while wearing a blindfold ). My peers frequently vehemently disapproved of any criticism of my work. The most tragic loss: I had lost touch with my values.

Some of my friendships and blossoming professional relationships almost ended up being destroyed by my ego. 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.

It was a gift I initially did not accept but which I, on the whole, was able to reflect on in depth. 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 admiration and turned my attention to the issues that had plagued my art school career. Most importantly: I got back to my core values.

Always Students

Following that short-term regression, I was able to push forward in my personal design and career. And as I grew older, I could reflect on myself to help with further development and course correction.

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

In one of my earlier professional roles, I about fifteen years ago created the interface for the application that produced the LHC’s particle collision diagrams. These diagrams are often regarded as works of art unto themselves because they depict what is actually happening inside the Collider during any given particle collision event.

I had a fascinating experience designing the interface for this application because I collaborated with Fermilab physicists to understand both how the application was intended to use it and how the physicists themselves would use it. To that end, in this role,

Working with the Fermilab team to iterate and make improvements to the interface, I cut my teeth on usability testing. To me, their language and the topics they discussed seemed foreign. And by making myself humble and operating under the impression that I was just a student, I made myself available to them in order to form that crucial bond.

I also had the opportunity to observe the physicists ‘ use of the tool in their own homes, on their own terminals, during my first ethnographic observation. One takeaway was that the data columns ended up using white text on a dark gray background rather than black text-on-white because of the facility’s level of ambient light-driven contrast. They were able to focus on their eyes while working during the day while poring over enormous amounts of data. Additionally, since Fermilab and CERN are government entities with strict accessibility requirements, my knowledge in that field also expanded. 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. I checked my ego before entering those values, which opened the door for those values.

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 constantly improving our craft, we are also continuously making ourselves available for improvement. Yes, we have completed years of design research. Or the focused lab training from a bootcamp for UX. or the work portfolio with monograms. Or, ultimately, decades of a career behind us.

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

The designer we are is our final form when we close our minds with an inner monologue of “knowing it all” or branding ourselves a” #thoughtleader” on social media. The artist we can be will never be there.

As a UX skilled in today’s data-driven landscape, it’s extremely likely that you’ve been asked to design a personal digital experience, whether it’s a common website, user portal, or local application. Although there is still a lot of advertising hype surrounding personalization programs, there are still very some standardized methods for implementing personalized UX.

That’s where we come in. We set ourselves the challenge of developing a systematic personalization framework especially for UX practitioners after finishing dozens of personalization tasks over the past few years. The Personalization Pyramid is a designer-centric model for standing up human-centered personalisation programs, spanning information, classification, content delivery, and general goals. By using this strategy, you will be able to understand the core elements of a modern, UX-driven personalization system ( or at the very least know enough to get started ).

Getting Started

For the sake of this article, we’ll believe you’re already familiar with the basics of online personalization. A nice guide can be found these: Website Personalization Planning. Although Graphic projects in this field can take a variety of forms, they frequently begin with similar starting points.

Popular circumstances for launching a personalization task:

• Your business or client made a purchase to support personalization with a content management system ( CMS ), marketing automation platform ( MAP ), or other related technology.
• The CMO, CDO, or CIO has identified customisation as a target
• User data is disjointed or confusing
• You are conducting some sporadic targeting or A/B assessment.
• On personalization method, participants disagree.
• Mandate of customer privacy rules ( e. g. GDPR ) requires revisiting existing user targeting practices

A powerful personalization system will need the same fundamental components regardless of where you begin. We’ve captured these as the “levels” on the tower. Whether you are a UX artist, scholar, or planner, understanding the core components may help make your contribution effective.

From top to bottom, the rates include:

North Star: What larger corporate goal is the personalisation initiative pursuing?
1. Objectives: What are the specific, tangible benefits of the system?
2. Touchpoints: Where will the personalized experience become served?
3. Contexts and Campaigns: What personalization information does the person view?
4. User Sections: What constitutes a special, suitable market?
5. What trustworthy and credible information does our professional platform collect to enable personalization?
6. Natural Data: What wider set of data is potentially available ( now in our environment ) allowing you to optimize?

We’ll go through each of these amounts sequentially. An associated deck of cards serves as an example of each level’s specific examples to make this more meaningful. We’ve included example for you here because we think they’re useful for customisation brainstorming sessions.

Starting at the top

The tower has the following elements:

North Star

With your personalisation plan, whether large or small, you aim for a general north star. The North Star identifies the (one ) overall goal of the personalization program. What do you wish to perform? North Stars cast a ghost. The bigger the sun, the bigger the dark. Example of North Starts may contain:

Function: Personalize based on basic customer input. Examples:” Raw” messages, basic search effects, system user settings and settings options, general flexibility, basic improvements
1. Feature: Self-contained customisation componentry. Examples:” Cooked” notifications, advanced optimizations ( geolocation ), basic dynamic messaging, customized modules, automations, recommenders
2. Experience: Personal user experiences across many interactions and consumer flows. Examples: Email campaigns, landing pages, advanced messaging ( i. e. C2C chat ) or conversational interfaces, larger user flows and content-intensive optimizations ( localization ).
3. Solution: Highly differentiating customized product experiences. Example: Standalone, branded encounters with personalization at their base, like the “algotorial” songs by Spotify quite as Discover Weekly.

Goals

As in any great UX style, personalization may help promote designing with client intentions. Objectives are the military and measurable indicators that will show the success of the overall program. Start with your existing analytics and measurement system, as well as metrics that you can benchmark against. In some cases, fresh targets may be ideal. The most important thing to keep in mind is that personalisation is never a desired outcome. It is a means to an end. Popular targets include:

• Conversion
• Time on work
• Net promoter score ( NPS)
• Consumer pleasure

Touchpoints

Personalization takes place at contacts. As a UX artist, this will be one of your largest areas of responsibility. The touchpoints you have will depend on how your personalization and the related technologies are implemented, and they should be based on enhancing a person’s encounter at a specific 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

• Email: Role
• Email: Occasion of available
• In-store display ( JSON endpoint )
• Native game
• Search

Wireframe-level Touchpoints

• Web overlay
• Web call club
• Web symbol
• Web content wall
• Web list

If you’re designing for online interface, for instance, you will likely need to include personal “zones” in your wireframes. Based on our next action, context, and campaigns, the articles for these can be presented dynamically in touchpoints.

Contexts and Campaigns

After you’ve outlined some touchpoints, you may consider the actual personal information a user may acquire. 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 be displayed automatically to specific customer sections, as defined by consumer data. At this stage, we find it helpful to contemplate two distinct concepts: a framework design and a willing design. The environment helps you consider the level of user engagement at the customisation moment, for instance, if they are just lightly browsing information rather than engaging in a deep dive. Think of it in conditions of activities for data recovery. The content model can then guide you in deciding what kind of personalization to use in the context ( for instance, an” Enrich” campaign that features related articles might be a good substitute for extant content ).

Personalization Context Model:

1. Browse
2. Skim
3. Nudge
4. Feast

Personalization Content Model:

1. Alert
2. Create Easier
3. Cross-Sell
4. Enrich

We’ve written a lot about each of these concepts abroad, so if you’d like to learn more, check out Colin’s Personalization Content Model and Jeff’s Personalization Context Model.

User Sections

User segments may be created based on consumer research, either prescriptively or dynamically ( for example, using principles and logic tied to set user actions or through A/B testing ). You will need to consider how to treat the logged-in visitor, the guest or returning visitor, for whom you may have a stateful cookie ( or another post-cookie identifier ), or the authenticated visitor at the least. Using the personalisation pyramids, here are some examples:

• Unknown
• Guest
• Authenticated
• Default
• Referred
• Role
• Cohort
• Unique ID

Actionable Data

Every business has access to data, regardless of its modern presence. It’s important to inquire about how to use the data you can ethically collect on users, its inherent reliability and value, and how to use it ( sometimes referred to as “data activation” ). Fortunately, the tide is turning to first-party information: a recent study by Twilio estimates some 80 % of companies are using at least some type of first-party information to personalize the customer experience.

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. Therefore, determining which method of data collection is best for your audiences should be a crucial component of your UX strategy. Here are some examples:

When it comes to recognizing and making decisions about various audiences and their signals, there is a trend of profiling. As user numbers increase in terms of time, confidence, and data volume, it varies more granularly.

Although some combination of implicit and explicit data is typically required for any implementation ( more commonly known as first party and third-party data ), ML efforts are typically not cost-effective right away. This is because optimization requires a strong data backbone and content repository. However, these approaches ought to be taken into account as part of the larger plan and may in fact help to speed up the organization’s progress overall. You’ll typically work together to create a profiling model with key stakeholders and product owners. The profiling model includes a defining framework for setting up profiles, profile keys, profile cards, and pattern cards. A multi-faceted approach to profiling which makes it scalable.

Pulling it Together

The cards serve as a starting point for an inventory of sorts ( we offer blanks for you to customize your own ), a set of potential levers and motivations for the personalization activities you aspire to deliver, but they are more valuable when grouped together.

One can begin to chart the entire course of a card’s “hand” from leadership focus to a tactical and tactical execution. It is also at the heart of the way that both co-authors have organized workshops to build a backlog of programs, which would make a good subject for a separate article.

In the meantime, it is important to note that each colored class of cards is helpful in understanding the range of options that you might have, as well as making specific choices about who will be made these decisions: when, when, and how.

Lay Down Your Cards

Any sustainable personalization strategy must consider near, mid and long-term goals. There is simply no “easy button” where a personalization program can be stood up and immediately see meaningful results, even with the leading CMS platforms like Sitecore and Adobe or the most exciting composable CMS DXP out there. 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.

The mobile-first style approach is great—it focuses on what really matters to the consumer, it’s well-practiced, and it’s been a popular style design for years. But developing your CSS mobile-first should also be fantastic, 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 min-width media queries for larger viewports (for a good overview see “What is Mobile First CSS and Why Does It Rock?”). 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?

Mobile-first CSS may yet be the best option for your own projects, but you need to first determine how ideal it is in light of the physical design and user interactions you’re trying to create. To help you get started, here’s how I go about tackling the elements you need to watch for, and I’ll discuss some alternative remedies if mobile-first doesn’t seem to fit your job.

Benefits of mobile-first

Some of the points to enjoy with mobile-first CSS growth —and why it’s been the de facto growth strategy for thus long—make a lot of feeling:

Development order. One thing you definitely get from mobile-first is a great development hierarchy—you only focus on the cellular view and get developing.

Tried and tested. It’s a tried-and-true method that has worked for years because it solves a problem actually also.

Prioritizes the smart see. The mobile view is the simplest and arguably the most significant because it covers all the crucial user journeys and frequently accounts for a higher proportion of user visits ( depending on the project ) ).

Inhibits desktop-centric growth. It can be tempting to first focus on the desktop perspective because desktop computers are used for growth. No one wants to spend their day retrofitting a desktop-centric website to work on mobile devices, but thinking about smart right away keeps us from getting stuck later on!

Drawbacks of mobile-first

Model declarations can be set at lower breakpoints and therefore overwritten at higher breakpoints:

More richness. The more unneeded code you inherit from lower thresholds the higher up the target order you ascend.

Higher CSS sensitivity. Styles that have been returned to the default value in a class name charter then have a higher sensitivity. When you want to preserve the CSS pickers as simple as possible, this can cause a headache on massive projects.

Requires more analysis tests. All higher thresholds must be regression tested if CSS changes at lower views ( such as adding a new fashion ).

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

The issue of home value surpasses

Overwriting values is not necessarily essentially wrong; CSS was created to do that. However, sharing incorrect values is counterproductive and can be burdensome and inadequate. When you have to overwrite styles to reset them to their defaults, which may cause issues later, especially if you are using a combination of bespoke CSS and utility classes, it can also lead to more style specificity. A style with a higher specificity that has been reset won’t be able to be used with a utility class.

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 max-width 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. However, if it appears that Grid would be much better for screens with large screens and Flexbox would be better for mobile, both can be accomplished entirely independently when the CSS is placed into closed media query ranges. Additionally, having a thorough understanding of any given component in all breakpoints upfront is necessary for developing simultaneously. This can help identify issues with the design more quickly in the development process. We don’t want to travel down the rabbit hole while creating complex mobile components, only to discover that the desktop designs are just as 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 Responsively App, Blisk, and many others.

Having said that, I don’t feel the order itself is particularly relevant. Stick to the classic development order if you like to concentrate on the mobile view, understand the requirements for other breakpoints, and prefer to work on multiple devices at once. It’s crucial to find common styles and exceptions in the appropriate stylesheet, which is a manual tree-shaking procedure! Personally, I find this a little easier when working on a component across breakpoints, but that’s by no means a requirement.

Closed media query ranges in practice

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:

• smaller than 768
• from 768 to below 1024
• 1024 and anything larger

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

.my-block { padding: 20px; @media (min-width: 768px) { padding: 40px; } @media (min-width: 1024px) { padding: 20px; }}

.my-block { padding: 20px; @media (min-width: 768px) and (max-width: 1023.98px) { padding: 40px; }}

The subtle difference is that the mobile-first example sets the default padding to “20px” and then overwrites it at each breakpoint, setting it three times in total. In contrast, the second example sets the default padding 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: 

• Only set styles when needed. 
• Not set them with the expectation of overwriting them later on, again and again. 

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 .my-block 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 padding in a closed media query range.

.my-block {  @media (max-width: 767.98px) {    padding: 20px;  }  @media (min-width: 768px) and (max-width: 1023.98px) {    padding: 40px;  }}

The browser default padding for our block is “0,” so instead of adding a desktop media query and using unset or “0” for the padding value (which we would need with mobile-first), we can wrap the mobile padding 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 padding style, as we want the browser default value.

separating the CSS from combining it

Due to the browser's concurrent request limit (typically around six ), it was crucial back then to keep the number of requests to a minimum. 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. By using a media query, we can separate the CSS into several files. The obvious benefit of this is that the browser can now request the CSS it currently requires with a higher priority than the CSS it doesn't. This is more effective and can shorten the amount of time a page is blocked overall.

Which HTTP version are you using?

To determine which version of HTTP you're using, go to your website and open your browser's dev tools. Next, go to the Network tab and check whether 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.

Also, if your site is still using HTTP/1... WHY?!! What are you anticipating? Excellent user support exists for HTTP/2.

Splitting the CSS

Separating the CSS into individual files is a worthwhile task. Linking the separate CSS files using the relevant media 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.

We can see that the mobile and default CSS are loaded with" Highest" priority in the following example of a website that is visited on a mobile breakpoint, since they are currently required 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.

Before rendering can begin, the browser will need to download and parse the CSS file when using bundled CSS.

While, as noted, with the CSS separated into different files linked and marked up with the relevant media 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 min-width 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. 

Depending on project requirements, the media queries and the number of separate CSS files may vary from one project to the next, but the example below may look similar.

Depending on the project’s deployment strategy, a change to one file (mobile.css, 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 site.css file, an approach that would normally trigger a full regression test.

Moving on

The adoption of mobile-first CSS was a significant milestone in web development because it allowed front-end developers to concentrate on mobile web applications rather than creating websites for desktop use and 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 to notice subtle simplifications in the CSS I write for myself as well as other developers, and that the testing and maintenance work is also a little more organized and effective.

In the end, simplifying CSS rule creation whenever possible is a more effective strategy than circling around with 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.

We concur that personas may remain excellent matches for computer-generated eyes, but not for the purpose you might think. Ironically, the website highlights the core issue of this very common design method: the person ( a ) does not exist. Personas are deliberately created, just like in the photos. Knowledge is combined into a sporadic, unreliable preview that is taken out of context.

But strangely enough, manufacturers use personalities to encourage their style for the real world.

A step up, identities

Most manufacturers have at least once in their careers created, used, or encountered identities. In their content” Personas- A Plain Introduction”, the Interaction Design Foundation defines profile as “fictional characters, which you create based upon your study in order to reflect the unique user types that might use your service, product, site, or brand”. Personas typically include a title, profile picture, rates, populations, goals, wants, behavior in relation to a particular service or product, feelings, and desires ( for instance, see Creative Companion’s Persona Core Poster ). According to design firm Designit, the goal of personas is to “make the research relateable, ]and ] easy to communicate, digest, reference, and apply to product and service development.”

The decontextualization of identities

Personalities are well-known because they make “dry” research information more realistic and people. However, this approach places a cap on the author’s ability to exclude the target users from their particular contexts. As a result, personalities don’t describe important factors that make you realize their decision-making method or allow you to connect to users ‘ thoughts and behavior, they lack stories. You are aware of the persona’s actions, but you lack the knowledge to know why. You end up with less human-like user images.

This “decontextualization” we see in identities happens in four way, which we’ll discuss below.

People are assumed to be stable, according to individuals.

Here’s a painfully obvious truth: people are not a fixed set of characteristics, despite the fact that many businesses still try to recruit and retain their employees and customers using outdated personality tests ( referring to you, Myers-Briggs ). You act, think, and feel different according to the conditions you experience. You appear distinct to different people, and you might act friendly toward some and harshly toward another. And you constantly change your mind regarding the selections you’ve made.

Modern psychology agree that while persons usually behave according to certain styles, it’s actually a combination of history and culture that determines how people act and take decisions. The context determines the kind of person you are at each particular time, including the environment, the effect of other people, your mood, and the whole story that led up to a situation.

Personas do not account for this variability in their attempt to simplify reality; instead, they present a user as a set of features. Like personality tests, personas snatch people away from real life. Even worse, people are labeled as” that kind of person” with no means to exercise their natural flexibility. This behavior discredits diversity, perpetuates stereotypes, and doesn’t reflect reality.

Personas focus on individuals, not the environment

You’re designing for a context, not an individual, in the real world. There are environmental, political, and social factors to consider when a person lives in a family, a community, or an ecosystem. A design is never meant for a single user. Instead, you create a product that is intended to be used by a certain number of people. However, personal experiences don’t explicitly describe how a user feels about the environment. Instead, they show the user only.

Would you always make the same decision over and over again? Possibly you’re a committed vegan but still decide to buy some meat when your relatives visit. Your decisions, including your behavior, opinions, and statements, are not only completely accurate but highly contextual because they vary with various circumstances and variables. 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 give a justification for your behavior. People practice the well-known attribution error, which states that they too often attribute others ‘ behavior to their personalities and not to the circumstances.

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, it’s common to pick a fictional character and build a character’s behavior around a particular circumstance based on the fiction. How could you possibly comprehend how someone you want to represent behave in new circumstances given that you haven’t even fully investigated and understood the current context of the people you want to represent?

Personas are meaningless averages

A persona is depicted as a specific person but is not a real person, as stated in Shlomo Goltz’s introduction article on Smashing Magazine; rather, it is made up of observations from numerous people. The famous USA Air Force design planes were designed based on the average of 140 of their pilots ‘ physical dimensions, with not a single pilot actually fit within that average seat, is a well-known criticism of this aspect of personas.

The same limitation applies to mental aspects of people. Have you ever heard a famous person say something like,” They took what I said out of context!” I didn’t mean it that way when they used my words. 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. In the end, the intended meaning was lost. You collect someone’s statement ( or need, or emotion ) into whose own specific context you specify it, and then report it as an isolated finding ( or goal, need, or emotion ).

But personas go a step further, extracting a decontextualized finding and joining it with another decontextualized finding from somebody else. The resultant set of findings frequently does not make sense because it is unclear or even contradictory because it lacks the underlying causes for and how that finding came about. It lacks any significance. 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 persona’s purposeful purpose?

The validity of personas is deceiving.

To a certain extent, designers realize that a persona is a lifeless average. To combat this, designers create and add “relatable” details to personas to make them appear to be real people. Nothing better explains the absurdity of this than a phrase from 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. Wouldn’t it be much more responsible to emphasize that John is only an abstraction while deliberately obscuring the fact that” John Doe” is an abstract representation of research findings? Let’s say something is artificial, and let’s say it’s that.

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. As with everything they produce, they do so by introducing a lot of biases. As Designit put it, as designers, we can” contextualize]the persona ] based on our reality and experience. We create connections that are familiar to us“. With each new detail added, this practice furthers stereotypes, doesn’t reflect real-world diversity, and takes people’s actual reality even further.

To conduct effective design research, we must report the actual situation and make it relatable for our audience, so that everyone can use their own empathy and develop their own interpretation and emotional response.

Dynamic Selves: The alternative to personas

What should we do instead if we shouldn’t use personas?

Designit suggests using mindsets rather than 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 avoid becoming fixated on just one person’s way of life. Unfortunately, despite being a step in the right direction, this proposal disregards the fact that people are a part of a system that controls their behavior, personality, and mindset. Therefore, Mindsets are also not absolute but change in regard to the situation. What determines a certain Mindset, is the question still unanswered.

Another option is provided by Margaret P., the author of the article” Kill Your Personas,” who has argued for replacing personas with persona spectrums that include a range of user abilities. For example, a visual impairment could be permanent ( blindness ), temporary ( recovery from eye surgery ), or situational (screen glare ). Because they recognize that the context is the pattern, not the personality, Persona spectrums are extremely useful for more inclusive and context-based design. However, their only drawback is that they have a very functional perspective 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. Similar to how we previously dealt with people, contexts are generalizable and have patterns that we can identify. How can we identify these patterns, then? How do we ensure truly context-based design?

Understand real people in a variety of settings

Nothing can be 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 method as Dynamic Selves.

Let’s take a look at how the approach looks based on an illustration of how one of us used it in a recent study that examined Italians ‘ habits 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.

1. Select the appropriate sample.

When we argue against personas, we’re often challenged with quotes 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 straightforward: you don’t have to. You don’t need to know a lot about everyone to have deep and meaningful insights.

In qualitative research, validity does not derive from quantity but from accurate sampling. You pick the people who best fit the “population” you’re designing for. You can infer how the rest of the population thinks and acts if this sample is chosen wisely and you have a deep understanding of the sampled people. There’s no need to study seven Susans and five Yuriys, one of each will do.

In fifteen different situations, Susan is not necessary. Once you’ve seen her in a few different settings, you’ve come to understand how Susan responds to various circumstances. Not Susan as an atomic being but Susan in relation to the surrounding environment: how she might act, feel, and think in different situations.

It becomes clear why each person should be portrayed as an individual because each already represents an abstraction of a larger group of people in similar circumstances because each person is representative of a portion of the population you’re researching. You oppose abstractions of abstraction! 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.

However, the question persists: how do you choose a sample representative? First of all, you must consider who the target market is for the product or service you are designing. It might be helpful to examine the company’s objectives and strategy, the current customer base, and/or a potential future target audience.

In our example project, we were designing an application for those who own a smart thermostat. Everyone in their home could have a smart thermostat in the future. However, only early adopters currently own one. To build a significant sample, we needed to understand the reason why these early adopters became such. We then recruited by enticing people to explain why and how they obtained a smart thermostat. There were those who had chosen to purchase it, those who had been influenced by others, and those who had discovered it in their homes. 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.

2. Conduct your research

After having chosen and recruited your sample, conduct your research using ethnographic methodologies. This will give you more examples and anecdotes to enrich your qualitative data. Given COVID-19 restrictions, we turned an internal ethnographic research project into home-based remote family interviews that were followed by diary research in our example project.

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 provide a story that would then become much more interesting and precise with the additions made by their spouses, husbands, kids, or occasionally even pets. We also paid attention to the behaviors that came from having relationships with other important people ( such as coworkers or distant relatives ), as well as the relationships that came into being with them. This wide research focus allowed us to shape a vivid mental image of dynamic situations with multiple actors.

It’s crucial that the scope of the study remain broad enough to cover all potential actors. Therefore, it typically works best to define broad research areas with broad questions. Interviews are best set up in a semi-structured way, where follow-up questions will dive into topics mentioned spontaneously by the interviewee. The most insightful findings will be made with this open-minded “plan to be surprised.” One of our participants responded to our question about how his family controlled the house temperature by saying,” 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 serve as her thermostat.

3. Analysis: Create the Dynamic Selves

You begin to represent each individual with several Dynamic Selves, each” Self” representing one of the circumstances you have examined throughout the research analysis. A quote serves as the foundation of each Dynamic Self, which is supported by a photo and a few relevant demographics that help to illustrate the larger context. The research findings themselves will show which demographics are relevant to show. The key demographics were family type, number and type of homes owned, economic status, and technological maturity in our case because our research focused on families and their way of life to understand their needs for thermal regulation. To facilitate the stakeholders ‘ transition from personas and be able to connect multiple actions and contexts to the same person, we also included the individual’s name and age, but they are optional.

To capture exact quotes, interviews need to be video-recorded and notes need to be taken verbatim as much as possible. This is crucial to the completeness of each participant’s various selves. To create authentic selves in ethnographic research using real-world actors and photos of the setting are necessary. 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. One of our interviewees, for instance, shared a story of how he used to spend weekends with his family in his mountain home. We depicted him hiking with his young daughter as a result.

At the end of the research analysis, we displayed all of the Selves ‘” cards” on a single canvas, categorized by activities. A quote and a unique photo were displayed on each card, each illustrating a situation. Each participant had several cards about themselves.

4. Identify creative uses

You will notice patterns beginning to appear once you have taken all of the main quotes from the interview transcripts and diaries and written them down as self-cards. These patterns will highlight the opportunity areas for new product creation, new functionalities, and new services—for new design.

There was a particularly intriguing insight around the concept of humidity in our example project. We became aware of the importance of monitoring humidity for health and that people don’t know what it is because an environment that’s too dry or wet can cause respiratory problems or worsen already existing ones. This highlighted a big opportunity for our client to educate users on this concept and become a health advisor.

Benefits of Dynamic Selves

People are surrounded by changing environments, peculiar situations that people face, and the actions that follow when using the Dynamic Selves approach for research. In our thermostat project, we have come to know one of the participants, Davide, as a boyfriend, dog-lover, and tech enthusiast.

Davide is a person we might have once consigned to the persona of a “tech enthusiast.” However, there are also those who are wealthy or poor who are tech enthusiasts, whether they are single or have families. Their motivations and priorities when deciding to purchase a new thermostat can be opposite according to these different frames.

You can generalize how he would act in a different situation once you have understood Davide in more detail and have fully understood the underlying causes of his behavior for each circumstance. You can use your understanding of him to predict what he would think and act in the situations ( or scenarios ) you create.

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 crucial because scale affects how we feel about people and how difficult it is to feel empathy for others. We have the deepest compassion for people with whom we can directly relate.

If you take a real person as inspiration for your design, you no longer need to create an artificial character. No more creating new plot devices to “realize” the character, no more implausible bias. Simply put, this is how they are in real life. In fact, in our experience, personas quickly become nothing more than a name in our priority guides and prototype screens, as we all know that these characters don’t really exist.

Another important benefit of Dynamic Selves is that it raises the stakes of your work: someone you and the team know and have met will experience the consequences if you violate your design. It might prompt you to check your designs every day and might prevent you from making shortcuts.

And finally, real people in their specific contexts are a better basis for anecdotal storytelling and therefore are more effective in persuasion. Real research documentation is necessary to obtain this result. It reinforces your design arguments with more urgency and weight:” When I met Alessandra, the conditions of her workplace struck me. Noise, bad ergonomics, lack of light, you name it. I’m afraid that if we choose to use this functionality, we’ll add complexity to her life.

Conclusion

Designit stated in their article on Mindsets that “design thinking tools offer a shortcut to deal with reality’s complexities, but this process of simplification can occasionally flatten out people’s lives into a few general characteristics.” Unfortunately, personas have been culprits in a crime of oversimplification. They fail to account for the complex nature of our users ‘ decision-making processes and don’t take into account the fact that people are immersed in contexts.

Design needs to be simplified, but not generalized. 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. Use those as metaphors for the person in all of their contexts. People and insights are subject to a context, but they cannot be removed because it would detract from the context’s 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.

One of the most successful soft knowledge we have at our disposal is the ability to work together to improve our patterns while developing our own abilities and opinions, in whatever form it takes, and whatever it may be called.

Feedback is also one of the most underestimated equipment, and generally by assuming that we’re now great at it, we settle, forgetting that it’s a skill that can be trained, grown, and improved. Bad feedback can cause conflict in jobs, lower motivation, and negatively impact faith and teamwork over the long term. A revolutionary force can get quality feedback.

Practicing our knowledge is absolutely a good way to enhance, but the learning gets yet faster when it’s paired with a good base that programs and focuses the exercise. What are some fundamental components of providing effective opinions? And how can input be changed for workplaces where workers are located and distributed?

On the web, we may discover a long history of sequential suggestions: from the early weeks of open source, script was shared and discussed on email addresses. Developers and sprint masters discuss ideas on tickets, designers make comments in their favourite design tools, and so on.

Design criticism is frequently used as a term for a type of collaborative suggestions that is provided to improve our work. So it shares a lot of the rules with comments in public, but it also has some variations.

The information

The material of the feedback serves as the foundation for all effective critiques, so we need to start there. There are many designs that you can use to form your content. This one from Lara Hogan is the one I personally like best because it’s obvious and actionable.

This equation, which is typically used to provide feedback to users, even fits really well in a design critique because it finally addresses one of the main issues that we address: What? Where? Why? How? Imagine that you’re giving some comments about some pattern function that spans several screens, like an onboard movement: there are some pages shown, a circulation blueprint, and an outline of the decisions made. You notice something that needs to be improved. You’ll have a mental model that will enable you to be more accurate and effective if you keep in mind the three components of the equation.

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 exist?

Not sure about the hierarchy and styles of the buttons; it seems off. Can you change them?

Finding a perspective that is as specific as possible when conducting design feedback refers to more than just pointing out which area of the interface. Do you offer the user’s viewpoint? Your expert perspective? from a business perspective? From the perspective of the project manager? A first-time user’s perspective?

I anticipate one to go forward and the other to go back when I see these two buttons.

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.

I anticipate one to go forward and the other to go back when I see these two buttons. 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.

The question approach is intended to give the designer some open guidance by provoking the designer’s critical thinking when they receive the feedback. Notably, Lara’s equation includes a second approach: request, which instead provides instructions for a particular 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.

For the question approach, consider the difference between the two:

I anticipate one to go forward and the other to go back when I see these two buttons. 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?

Or, for the request approach:

I anticipate one to go forward and the other to go back when I see these two buttons. 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.

In some situations, it might be helpful to include an additional reason why: why you think the suggestion is better.

I anticipate one to go forward and the other to go back when I see these two buttons. 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.

Choosing between the request and question approaches can occasionally be influenced by one’s personal preferences. I did rounds of anonymous feedback and I reviewed feedback with other people a while back when I was putting a lot of effort into improving my feedback. 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 switched teams. Quite unexpected, my next round of criticism from one particular person wasn’t very positive. 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. However, there was one person in this other team who now preferred specific guidance. So I modified my feedback 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. Yes, but also no. Let’s look at 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. Additionally, if we zoom out, it may lessen misunderstandings and back-and-forth conversations in the future, thereby increasing overall effectiveness and efficiency of collaboration beyond the single comment. Consider the example above where the feedback would be simply” 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 new features might be introduced, and perhaps that change no longer makes sense. Without explaining the why, the designer might assume that the change is one of 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 type of feedback is not always effective because some comments don’t always need to be thorough, some may be obvious because of the team’s internal knowledge, which may lead to some explanations of the whys.

Therefore, the equation above is intended to serve as a mnemonic to reflect and enhance the practice rather than a strict template for feedback. 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.

The atmosphere

The foundation of feedback is well-rounded content, 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. It has been demonstrated that only positive feedback can lead to sustained change in people. It can be determined by tone alone whether content is rejected or welcomed.

Tone is crucial to work on because our goal is to be understood and create a positive working environment. Over the years, I’ve tried to summarize the required soft skills in a formula that mirrors the one for content: the receptivity equation.

Respectful feedback comes across as grounded, solid, and constructive. It’s the kind of feedback that, regardless of whether it’s positive or negative, is thought to be useful and fair.

Timing refers to when the feedback happens. If given at the wrong time, to-the-point feedback has little chance of being well received. If a new feature’s entire high-level information architecture is about to go live when it’s about to be released, it might still be relevant if that questioning raises a significant blocker that no one saw, but those concerns are much more likely to have to wait for a later revision. So in general, attune your feedback to the stage of the project. Iteration in the early stages? Iteration later? Polishing work in progress? Each of these needs varies. The ideal setting will increase the likelihood that your feedback will be appreciated.

Attitude is the equivalent of intent, and in the context of person-to-person feedback, it can be referred to as radical candor. That entails checking before writing to see if what we have in mind will actually help the person and improve the project overall. Sometimes it might be difficult to reflect on this because we might not want to admit our deep appreciation for that person. Hopefully that’s not the case, but that can happen, and that’s okay. How would I write if I really cared about them, if you could help you make up for it? How can I stop acting aggressively? How can I be more constructive?

Form is important in multicultural and cross-cultural workplaces because having excellent writing, perfect timing, and the right attitude might not be as effective if the writing style leads to miscommunications. There could be many reasons for this, including the fact that occasionally certain words may cause specific reactions, that nonnative speakers may not be able to comprehend all thenuances of some sentences, that our brains may be different and that our world may be perceived differently; hence, neurodiversity must be taken into account. Whatever the reason, it’s important to review not just what we write but how.

A few years ago, I asked for some feedback on how I respond. I was given some helpful advice, but I also found a surprise in my comment. They pointed out that when I wrote” Oh, ]… ]”, I made them feel stupid. That wasn’t my intention at all! I just realized that I had been giving them feedback for months and that I had always made them feel foolish. I was horrified … but also thankful. I quickly changed my situation by adding “oh” to my list of replaced words (your choice between aText, TextExpander, or others ) so that when I typed “oh,” it was immediately deleted.

Something to keep in mind because it’s quite common, especially in teams with a strong group spirit, is that people frequently 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 best thing you can do for someone is to encourage their growth.

Giving feedback in written form can be reviewed by someone else who isn’t directly involved, which can help to reduce or eliminate any bias that might exist. 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.

The format

Asynchronous feedback also has a significant inherent benefit: it allows us to spend more time making sure that the suggestions ‘ clarity and actionability meet two main objectives.

Let’s imagine that someone shared a design iteration for a project. You are commenting on it while reviewing it. There are many ways to accomplish this, and context is of course important, but let’s try to think about some things that might be worthwhile to take into account.

In terms of clarity, start by grounding the critique that you’re about to give by providing context. This includes specifically describing where you’re coming from: do you have a thorough understanding of the project, or is this your first time seeing it? Are you bringing in a high-level perspective, or are you just learning the ins and outs? Are there regressions? Which user’s point of view do you consider when providing feedback? Is the design iteration at a point where it would be acceptable to ship this, or are there significant issues 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 a must when providing cross-team feedback. If I were to review a design that might be directly related to my work, I would say that, underlining my opinion as external, and if I had no idea how the project might have come to that conclusion.

We often focus on the negatives, trying to outline all the things that could be done better. That is obviously important, but focusing on the positives, especially if you saw improvement in the previous iteration, is even more crucial. Although this may seem superfluous, it’s important to keep in mind that design is a field with hundreds of possible solutions for each 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. Sharing positive feedback can help prevent regressions in the long run because those things will have been identified as crucial. Positive feedback can also help, as an added bonus, prevent 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 is a big difference between a critique of a design that is already in good shape and one that is critiqued for a design that isn’t quite there yet.

Depersonalizing your feedback is another way to make it better: it should never be about the creator of the piece of art. It’s” This button isn’t well aligned” versus” You haven’t aligned this button well”. Just before sending, review your writing to make changes to this.

One of the best ways to assist the designer who is reading through your feedback in terms of actionability is to divide 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 identifying markers for the specific area of the interface you’re referring to can also be very helpful.

One method that I’ve personally used to enhance the bullet points in some situations is 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. A blue spiral is also used for either something I’m uncertain about, an exploration, an open alternative, or just a note. However, I’d only use this strategy on teams where I’ve already established a high level of trust because it might turn out to be quite demoralizing if I deliver a lot of red squares and change how I communicate that.

Let’s see how this would work by reusing the example that we used earlier as the first bullet point in this list:

• 🔶 Navigation—I anticipate one to go forward and the other to go back when I see these two buttons. 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.
• Overall, I believe the page is strong, and this is a good candidate for our version 1. 1.0 release candidate.
• � � Metrics—Good improvement in the buttons on the metrics area, the improved contrast and new focus style make them more accessible.
• Button Style: Using the green accent in this context gives the impression that it’s a positive action because green is typically seen as a confirmation color. Do we need to look for a different color?
• 🔶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 help maintain consistency in the visual hierarchy.
• Background: A light texture is effective, but I’m not sure if doing so will cause too much noise on this kind of page. What is the thinking in using that?

What about using Figma or another design tool that enables in-place feedback to provide feedback directly? These are generally difficult to use because they conceal discussions and are harder to follow, but they can be very useful in the right context. 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 more thing: Say the obvious. Sometimes we might feel good or bad about something, 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 fine. Don’t hold it back, though, because you might need to change the phrasing a little to make the reader feel more at ease. Good feedback is transparent, even when it may be obvious.

Asynchronous feedback also has the benefit of automatically guiding decisions, according to writing. Why did we do this, especially in large projects? 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. I advise using software to save these discussions so they can be hidden once they are resolved, for this reason.

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 way to approach them is to start with the area you lack the most, either from your point of view or from feedback from others, first. Then the third, 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 Mike Shelton and Brie Anne Demkiw for their initial review of this article.

What on earth is a passionate fatigue, then?

Envision a person who is determined to accomplish everything. She has two wonderful children whom she, along with her father who is also working mildly, is homeschooling during a crisis. She loves everyone at work because of how demanding her work is. She wakes up early to get some movement in ( or frequently catch up on work ), prepares dinner as the kids are having breakfast, and works while positioning herself near “fourth grade” to listen in as she balances clients, tasks, and budgets. Sound like a bit? It works well with a friendly group at home and at work.

This girl seems to need self-care because she has too much going on. But no, she doesn’t have occasion for that. In reality, she begins to feel as though she’s dropping balloons. Not enough is achieved. There’s not enough of her to be here and there, she is trying to divide her head in two all the time, all time, every time. She begins to question herself. And her interior narrative grows more and more crucial as those feelings grow in.

Instantly she KNOWS what she needs to accomplish! She ought to do more.

This pattern is challenging and risky. Hear why? Because the narrative only gets worse when she doesn’t complete that novel goal. She immediately starts failing. She isn’t doing much. She is insufficient. She’ll discover more she may do because she might neglect, or perhaps her home. She doesn’t nap as much, proceed because much, all in the attempts to do more. caught in this pattern of attempting to prove herself to herself without ever succeeding. Always feeling “enough”

But, yeah, that’s what zealous burnout looks like for me. It doesn’t develop over in some grand gesture, but it does rather develop gradually over the course of several weeks and months. My using operation appears to be moving more quickly than I have lost my focus. I rate up and up and up… and therefore I simply stop.

I have the potential to do so.

It’s funny how things affect us. Through the glass of youth, I viewed the worries, problems, and sacrifices of someone who had to make it all work without having much. I always went without and also got an extra here or there because my mother was so competent and my father was so friendly.

Growing up, I didn’t feel shame when my mom gave me food passports; in fact, I would have likely sparked debates about the subject, orally eviscerating anyone who dared to criticize the disabled person who was attempting to ensure all of our needs were met with so little. As a child, I watched the way the worry of not making those ends meet impacted persons I love. Because I was” the one who was” make our lives a little easier, I would take on many of the physical things as the non-disabled people in my house. I soon realized that putting more of myself into it was linked to fears or confusion; I am the one who does. I learned first that when something frightens me, I may double down and work harder to make it better. I am capable of taking on the issue. I’ve been told that I seem courageous when people have seen this in me as an adult, but make no mistake, I’m no. If I seem courageous, it’s because this behavior was forged from another people’s worries.

And here I am, more than 30 years later, despite the overwhelming pressures that come with putting my mind to work on them when I have many things to do and that I may. I feel more motivated to show that I may make things happen if I put in more effort, put on more responsibilities, and do more.

I do not see people who struggle financially as problems, because I have seen how powerful that tide is be—it takes you along the way. I certainly understand that I have had the opportunity to avoid many of the difficulties that were present in my children. Having said that, I am also” the one who can” who believes she should, so I would think I had failed if I had to struggle to make ends meet for my own home. Though I am supported and educated, most of this is due to great riches. But, I’ll give myself the haughtiness of claiming that my choices were wise and that they had sparked that success. My sense of identity comes from the notion that I am” the one who can” and feel compelled to accomplish the most. I can choose to halt, and with some pretty precise warm water splashed in my experience, I’ve made the choice to previously. However, I don’t always choose to stop; instead, I move forwards, driven by a concern that is so present that I hardly notice until I’m completely worn out.

So why all the story? You see, stress is a volatile thing. Over the years, I have read and heard a lot about stress. Stress is a real thing. Particularly today, with COVID, many of us are balancing more than we ever have before—all at once! It’s challenging, and so many wonderful experts are affected by the mitigation, the shutting down, and the procrastination. There are significant papers that, in my opinion, relate to the majority of people around, but not me. That’s not what my fatigue looks like.

The perilous darkness of passionate burnout

The extra days, more work, and overall focused commitment are often viewed as an advantage in many workplaces ( and occasionally that’s all it is ). They see anyone trying to rise to difficulties, never people stuck in their anxiety. Some well-intentioned businesses have measures in place to safeguard their employees from stress. However, in situations like this, those alarms don’t always go off, and some business members are surprised and depressed when the inevitable prevent occurs. And maybe even actually betrayed.

When it comes to parenting, which is more so for parents, mathematically speaking, are praised for being so on top of it all when they can work, participate in after-school activities, exercise self-care in the form of diet and exercise, and also join pals for coffee or wines. Many of us have watched endless streaming episodes of COVID to see how challenging the female hero is, but she is powerful and interesting, and can do it. It’s a “very special show” when she breaks down, shouts in the bathroom, terribly admits she needs help, and only stops for a bit. Truth be told, countless people are hidden in tears or doom-scrolling to escape. Although we are aware that the media is a lie to amuse us, a large portion of society has been persuaded that it is what we should aim for.

Women and burnout

I cherish men. And even though I don’t love every man ( heads up, I don’t love every woman or nonbinary person either ), I believe there is a wonderful range of people who fit 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 at work experience the pressure to do everything “mom” while giving 100 %. Mothers who are not employed 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 so ingrained in our culture and vicious and systemic that we frequently are unaware of how much pressure we place on ourselves and others.

Beyond happiness, there are costs. Harvard Health Publishing released a study a decade ago that “uncovered strong links between women’s job stress and cardiovascular disease”. According to the CDC,” Heart disease is the leading cause of death for women in the United States, killing 299,578 women in 2017—or roughly 1 in every 5 female deaths,”

According to what I’ve read, this connection between work stress and health is more dangerous for women than it is for their non-female counterparts.

But what if your burnout isn’t like that either?

That might not be you either. After all, we are all unique, and how we respond to stressors is also unique. It’s part of what makes us human. Don’t put too much emphasis on how burnout looks; instead, learn to recognize it in yourself. What are a few questions I occasionally ask my friends if they worry about them.

Are you happy? You should ask yourself this straightforward question first. Even if you’re burning out doing all the things you love, chances are that as you get closer to burnout, you’ll just stop consuming as much joy from it all.

Do you feel empowered to say no? I’ve observed in both myself and others that no longer feel like they can turn down opportunities. Even those who don’t” speed up” feel pressured to say “yes” and not let the people around them be disappointed.

What are three things you’ve done for yourself? We all have a tendency to stop doing things for ourselves, according to another observation. anything from avoiding conversations with friends to skipping showers and eating poorly. These can be red flags.

Are you using justifications? Many of us make an effort to avoid feeling worn out. 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 actually be crunch time, a single objective, or a set of skills you need to master. Life happens because of that. BUT if this doesn’t stop, be honest with yourself. If you’ve worked more than 50 hours per week since January, you might be thinking that it’s not crunch time; rather, it might be a bad situation you’re finding yourself in.

Do you have a method for overcoming this feeling? If something is truly temporary and you do need to just push through, then it has an exit route with a
defined the end

Take the time to listen to yourself like you would a friend. Be honest, allow yourself to be uncomfortable, and break the thought cycles that prevent you from healing.

So what do we do now?

What I just described is a different path to burnout, but it’s still burnout. There are well-established approaches to working through burnout:

• Get enough sleep.
• Eat well.
• Work out.
• Go outside.
• Take a break, please.
• Overall, practice self-care.

These are challenging for me because they seem like more chores. Doing any of the above for me feels like a waste if I’m in the burnout cycle. 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, don’t they?

Your inner voice might already be pretty bad if you’re deeply in the cycle. If you need to, tell yourself you need to take care of the person your people depend on. Use your roles to help make healing easier by defending the time you spend working on you if they are pushing you toward burnout.

I have come up with a few suggestions for me to help me remember the airline attendant’s advice to put on your face first when I feel burned out.

Cook an elaborate meal for someone!

Okay, since I’m a “food-focused” person, I’ve always been a fan. In my home, there are countless tales of people coming into the kitchen, turning right, and leaving when they noticed I was” chopping angrily.” But it’s more than that, and you should give it a try. Seriously. If you don’t feel like giving time for yourself, make it a priority 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 help you get a better perspective and clear your head. I’ve always had the ability to locate a location on a map and prepare food from it ( thanks, 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 ultimately, we all triumph!

Vent like a sniveling jerk.

Be careful with this one!

Over the past few years, I have made an effort to practice more gratitude, and I am aware of the benefits. Having said that, sometimes you just need to let it all out, even the ugly ones. 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 required, turn to a trusted friend and give yourself some pure verbal diarrhea by expressing all your concerns. You must have faith in this friend not to judge you, to feel your pain, and, most importantly, to advise you to get your cranium removed from your own rectal cavity. Seriously, it’s about getting a reality check here! One of the things that I admire most about my husband is how he manages to simplify things down to the simplest. We’re spending our lives together, and I can’t wait to get over it. I’m so grateful for his words of dedication, love, and acceptance of me. It also, of course, has meant that I needed to remove my head from that rectal cavity. Again, those instances are typically appreciated in retrospect.

Grab a book!

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. You might discover something that resonates with you. Among the titles that have stood out to me are:

• Thrive by Arianna Huffington
• Tim Ferriss ‘ book Tools of Titans
• Girl, Stop Apologizing by Rachel Hollis
• Dare to Lead by Brené Brown

Or, another method I enjoy using is to read or listen to a book that is NOTHING to do with my work-life balance. I’ve read the following books, and I think they helped to balance me out because my mind was thinking about the subjects they were interested in rather than whizzing around:

• The Drunken Botanist by Amy Stewart
• Darin Olien’s Superlife
• A Brief History of Everyone Who Ever Lived by Adam Rutherford
• Gaia’s Garden by Toby Hemenway

Choose a topic on YouTube or subscribe to a podcast if you don’t enjoy reading. In addition to learning about raising chickens and ducks, I’ve watched a lot of gardening and permaculture topics. For the record, I do not have a particularly large food garden, nor do I own livestock of any kind… yet. Nothing about my life needs anything from me, and I just find the subject interesting.

Give yourself a break.

You are never going to be perfect—hell, it would be boring if you were. It can be imperfect and broken. It’s human to be depressed, anxious, and sad. It’s OK to not do it all. You can’t be brave without being imperfect, which is scary, but you can’t be brave without being imperfect.

The most crucial thing to remember is to grant yourself permission to NOT do it all. You never promised to be everything to everyone at all times. We are stronger than the anxieties that motivate us.

It’s challenging. It is hard for me. That it’s acceptable to stop is what inspired me to write this. It’s acceptable that your unhealthy habit, which might even be beneficial to those around you, needs to end. You can still be successful in life.

We are all eulogizing how we live, according to a recent article I read. What will your professional accomplishments say, knowing that yours won’t be mentioned in that speech? What do you want it to say?

Look, I get it that none of these concepts will “fix it,” which is not their intention. Only how we react to the things around us is what we control. These suggestions are to help stop the spiral effect so that you are empowered to address the underlying issues and choose your response. Most of the time, I find these to be effective. They might be able to help you.

Does this sound familiar?

If something sounds familiar, you are not alone. Don’t let your sluggish self-talk indicate that you “even burn out wrong.” It’s not wrong. Even if I’m rooted in fear like my own drivers, I think this need to do more comes from a place where you have the same kind of love, determination, motivation, and other wonderful qualities that make you the amazing person you are. We’re going to be fine, you see. 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 recall the Winnie the Pooh cartoon in which Pooh ate so much at Rabbit’s house that his buttocks couldn’t fit through the door? It came as no surprise when he abruptly declared that this was unacceptable because I already associate a lot with Rabbit. But do you recall what happened next? He made the most of the large butt in his kitchen by placing a shelf across poor Pooh’s ankles and decorations on his back.

We are resourceful and aware that we can push ourselves when necessary, even when we are exhausted or have a ton of clutter 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 need to redefine success in order to make room for comfort for being uncomfortable human, but that doesn’t really sound that bad either.

So, if you’re anywhere right now, take a deep breath. Do what you need to do to get out of your head. Give thanks and take precaution.

We’ve been conversing for many thousands of years. Whether to present information, perform transactions, or just to check in on one another, people have yammered aside, chattering and gesticulating, through spoken discussion for many generations. Only recently have we begun to write our conversations, and only recently have we outsourced them to the system, a system that exhibits a far greater affection for written communications than for the vernacular rigors of spoken speech.

Computers have issues because conversation is more important than written language in spoken and written writing. To have productive conversations with us, machines may struggle with the messiness of mortal speech: the disfluencies and pauses, the gestures and body language, and the variations in word choice and spoken dialect that is stymie even the most carefully crafted human-computer interaction. Speaking language also has the advantage of face-to-face contact, which allows us to perceive visual social cues in the human-to-human scenario.

In contrast, written language develops its own fossil record of dated terms and phrases as we report it and retain utilization long after they are no longer relevant in spoken communication ( for example, the welcome” To whom it may concern” ). Because it tends to be more consistent, smooth, and proper, written word is necessarily far easier for devices to interpret and know.

This pleasure is not available in spoken speech. There are verbal cues and vociferous behaviors that mimic conversation in complex ways, including how something is said, never what. These are the nonverbal cues that ornament conversations with emphasis and emotional context. Whether rapid-fire, low-pitched, or high-decibel, whether satirical, awkward, or groaning, our spoken speech conveys much more than the written word had ever muster. But as designers and content strategists, we face exciting challenges when it comes to voice interfaces, the machines we use to execute spoken conversations.

Voice Compositions

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 ( ). We typically strike up a discussion by:

• we require something ( such as a transaction ),
• we want to know something ( information of some sort ), or
• We are sociable creatures, and we need a talk partner.

A second talk from beginning to end that achieves some goal for the user, starting with the voice interface’s initial greeting and ending with the user exiting the interface, also fits into these three categories, which I refer to as interpersonal, technical, and prosocial. 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 it may not always be one voice interaction.

Most voice interfaces are more gimmicky than captivating in purely prosocial conversations because machines are unable to yet be truly interested in our progress and engage in the kind of glad-handing behavior that people 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, Michael Cohen, James Giangola, and Jennifer Balogh advise sticking to user expectations by imitating how they interact with other voice interfaces rather than trying too hard to be human, which could lead to alienation of them ( ).

A voice interface can also have two types of conversations we can have with one another that are both transactional and informational, each learning something new ( “discuss a musical” ).

Transactional voice interactions

When you order a Hawaiian pizza with extra pineapple, you’re typically having a conversation and a voice interaction when you’re tapping buttons on a food delivery app. The conversation quickly shifts from a brief smattering of neighborly small talk to ordering a pizza ( generously topped with pineapple, as it should be ) when we walk up to the counter and place an order.

Alison: Hey, how’s it going?

Burhan: Hello and welcome to Crust Deluxe! It’s chilly outside. How can I help you?

Can I get a Hawaiian pizza with extra pineapple, Alison?

Burhan: Yes, but what size?

Alison: Large.

Burhan: Anything else?

Alison: No, that’s it.

Burhan: Something to drink?

Alison, I’ll have a bottle of Coke.

Burhan: You are aware of it. That’ll be$ 13.55 and about fifteen minutes.

A service rendered or a product delivered, as each incremental disclosure in this transactional conversation reveals more and more of the desired transactional outcome. Transactional conversations exhibit a few key characteristics: they’re direct, to the point, and economical. They quickly dispense with pleasantries.

Informational voice interactions

In the meantime, some conversations are primarily about getting 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 interested in trying halal or kosher dishes, gluten-free options, or something else entirely. Even though we have a prosocial mini-conversation once more at the beginning to practice politeness, we are after much more.

Alison: Hey, how’s it going?

Burhan: Hello and welcome to Crust Deluxe! It’s chilly outside. How can I help you?

Alison: Can I ask a few questions?

Burhan: Of course! Continue straight ahead.

Alison: Do you have any halal options on the menu?

Burhan: Absolutely! On request, we can make any pie halal. We also have lots of vegetarian, ovo-lacto, and vegan options. Do you have any other dietary restrictions in mind?

Alison, what about pizzas that don’t contain gluten?

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 say to you to help?

Alison: That’s it for now. Good to know. Thank you!

Burhan: Anytime, come back soon!

This is a very different dialogue. Here, the goal is to obtain a particular set of facts. Informational conversations are research expeditions to gather data, news, or facts in search of the truth. Voice interactions that are informational might be more long-winded than transactional conversations by necessity. In order for the customer to understand the key takeaways, responses are typically longer, more in-depth, and carefully communicated.

Voice-to-text interfaces

At their core, voice interfaces employ speech to support users in reaching their goals. However, just because an interface has a voice component doesn’t mean that every user interaction with it is mediated through voice. We’re most concerned with pure voice interfaces, which depend entirely on spoken conversation and lack any visual component, making multimodal voice interfaces much more nuanced and challenging to deal with because they can lean on visual components like screens as crutches.

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.

IVR ( interactive voice response ) systems

Written conversational interfaces have been a part of computing for many decades, but voice interfaces first started to appear 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 made it easier for businesses to cut down on call centers, but they soon gained notoriety for their clunkiness. These systems, which are commonplace in the corporate world, were primarily intended as metaphorical switchboards to direct customers to real phone agents (” Say Reservations to book a flight or check an itinerary” ), and it is likely that when you call an airline or hotel conglomerate, you will have the opportunity to have a conversation with one. 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 (, PDF).

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

Screen readers

Parallel to the evolution of IVR systems was the invention of the screen reader, a tool that transcribes visual content into synthesized speech. It is the most popular way for blind or visually impaired website users to interact with text, multimedia, or form elements. Perhaps the closest thing we have today to an out-of-the-box implementation of content delivered through voice is represented by screen readers.

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 ( ). The first IBM Screen Reader for text-based computers was created by Jim Thatcher in the same year, which was later recreated for a computer with graphical user interfaces ( GUIs ) ( ).

The demand for accessible website tools exploded as a result of the web’s explosive growth in the 1990s. 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,” according to Aaron Gustafson in A List Apart. ” At least they do when documents are authored thoughtfully” ( ).

Although incredibly instructive for voice interface designers, screen readers have a major flaw: they’re challenging to use and consistently verbose. Sometimes unwieldy pronouncements that name every manipulable HTML element and announce every formatting change are made because the visual structures of websites and web navigation don’t translate well to screen readers. For many screen reader users, working with web-based interfaces exacts a cognitive toll.

Accessibility advocate and voice engineer Chris Maury examines why the screen reader experience is ill-suited for users who rely on voice in Wired:

I disliked the operation of Screen Readers from the beginning. Why are they designed the way they are? It makes no sense to present information visually and then only to have that information translated into audio. All the effort and thought that goes into creating the ideal user experience for an app is wasted, or worse, having a negative effect on blind users ‘ experience. ( ) _ _ _

In many cases, well-designed voice interfaces can deliver users ‘ requests more quickly than rambling screen reader monologues. After all, users of the visual interface have the advantage of freely scurrying around the viewport to find information, ignoring areas that are unimportant to them. Blind users, meanwhile, are obligated to listen to every utterance synthesized into speech and therefore prize brevity and efficiency. Users with disabilities who have long had no choice but to use clumsy screen readers might benefit from more streamlined user interfaces, especially more advanced voice assistants.

Voice-overseers

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-overseers 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 created their vision for a Semantic Web “agent” that would carry out routine tasks like” checking calendars, making appointments, and finding locations” (, behind paywall ). Apple’s Siri only became a reality until 2011 when it finally made voice assistants a 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 but vendor-provided features are locked down. For instance, at the time of their release, the core functionality of Apple’s Siri and Microsoft’s Cortana couldn’t be expanded beyond their already-existing capabilities. There are no other means of developers communicating with Siri at a low level, aside from predefined categories of tasks like messaging, hailing rideshares, making restaurant reservations, and other things, which are still possible today.

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, developers who feel constrained by the limitations of Siri and Cortana are increasingly using programmable voice assistants that are extensibable and customizable. Google Home has the ability to program arbitrary Google Assistant skills, while Amazon offers the Alexa Skills Kit, a developer framework for creating custom voice interfaces for Amazon Alexa. Today, users can choose from among thousands of custom-built skills within both the Amazon Alexa and Google Assistant ecosystems.

As businesses like Amazon, Apple, Microsoft, and Google continue to occupy their positions, they are also selling and open-sourcing an unheard array of tools and frameworks for designers and developers, aiming to make creating voice interfaces as simple 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. In contrast, many development platforms, such as Google’s Dialogflow, have omnichannel capabilities that allow users to create a single conversational interface that then becomes a voice interface, textual chatbot, and IVR system upon deployment. In this design-focused book, I don’t recommend any specific implementation strategies, but in Chapter 4 we’ll discuss some of the possible effects that these variables might have on the way you construct your design artifacts.

Voice Content

Simply put, voice content is content that is delivered through voice. Voice content must be free-flowing and organic, contextless and concise in order to preserve what makes human conversation so compelling in the first place. Everything written content is not.

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. We’re most concerned with the content in this book being delivered auditorically, not as an option but as a necessity.

Our initial foray into informational voice interfaces will likely be to provide user content, for many of us. There’s only one problem: any content we already have isn’t in any way ready for this new habitat. So how can we make the content on our websites more conversational? And how do we create fresh copy that works with voice-activated text?

Lately, we’ve begun slicing and dicing our content in unprecedented ways. Websites are, in many ways, massive vaults of what I call macrocontent: lengthy prose that can last for miles in a browser window while extending like microfilm viewers of newspaper archives. Microcontent was defined as permalinked pieces of content that could be read in any environment, such as email or text messages back in 2002, well before the present-day ubiquity of voice assistants.

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. ( ) _ _ _

I would update Dash’s definition of microcontent to include all instances of bite-sized content that transcends 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. The best way to learn how to stretch your content to the limits of its potential is through microcontent, which will inform both established and new delivery methods.

Voice content stands out as being unique because it illustrates how content is experienced in space as opposed to time. 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.

We need to make sure that our microcontent truly performs well as voice content because it is essentially composed of isolated blobs without any connection to the channels in which they will eventually end up. This means focusing on the two most crucial characteristics of robust voice content: voice content legibility and voice content discoverability.

Our voice content’s legibility and discoverability in general both depend on how it manifests in terms of perceived space and time.