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 the familiar pattern, a brand-new engineering or thought emerges to shake things up and completely alter the 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 sequential connection between the front end and back end in the mid-2000s. Immediately, websites may update their information without needing to refresh. A grain of JavaScript systems, including Prototype, YUI, and jQuery, emerged to aid designers in creating more dependable client-side interactions across browsers with wildly varying standards support. Techniques like photo replacement enable skilled manufacturers and developers to show fonts of their choosing. And technology like Flash made it possible to include movies, sports, and even more engagement.

These new technology, standards, and approaches reinvigorated the market in many ways. As manufacturers and designers explored more diversified designs and layouts, website design flourished. However, we also depend on numerous 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 rely heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds (among other hacks ) for the appearance of full-length columns. All kinds of nested floats or absolute positioning were required for complicated layouts ( or both ). The use of flash and photo replacement for specialty fonts was a great first step in the direction of the big five typefaces, but both hacks caused accessibility and performance issues. Additionally, JavaScript libraries made it simple to add a dash of conversation to pages without having to spend the money to double or even quadruple the get size for basic websites.

The internet as program platform

The balance between the front end and the back end continued to improve, leading to the development of the latest web application time. 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 equipment came others, including creative type control, build technology, and shared bundle libraries. What was once mainly used for linked files turned into a world with limitless possibilities.

At the same time, wireless equipment became more ready, and they gave us online access in our wallets. Reliable architecture and mobile apps opened up possibilities for fresh relationships anytime.

This fusion of potent portable devices and potent development resources contributed to the growth of social media and various consolidated tools for user interaction and consumption. As it became easier and more popular to interact with others immediately on Twitter, Facebook, and yet Slack, the need for held private websites waned. Social media provided links on a worldwide scale, with both positive and negative outcomes.

Want a much more in-depth account of how we came to this, 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 journey of” Internet Artifacts.”

Where we are now

In the last couple of years, it’s felt like we’ve begun to achieve another big tone place. As social-media systems bone and fade, there’s been a growing interest in owning our personal information 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. We can create incredible personal websites and update them frequently, but without discovery and connection, it can feel as though we could as well be yelling into the void.

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. The barrier to using more recent techniques isn’t browser support anymore; it’s more often the speed at which designers and developers can learn what’s available and how to adopt it.

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 the initial cost of these frameworks may be saved in the beginning, it eventually becomes due as their upkeep and maintenance becomes a component 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. These same frameworks frequently come with performance costs, making users have to wait for scripts to load before interacting with or reading pages. 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. It’s occasionally just a hack that you’ve gotten used to. And occasionally, it prevents you from pursuing better options.

Start from standards. Although standards change over time, 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 primitive HTML from the 1990s still function flawlessly today. Even after a few years, the same can’t be said about websites created with frameworks.

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 consider more carefully and design with consideration rather than rush 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 neural connections, and the techniques you learn in one day may be useful for guiding future experiments.

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 special for yourself that you are only qualified to create. 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. I’m just trying to reject what he’s saying, but I’m just trying to give some context to initiatives and opportunities where AI can make a difference for 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 text

Joe’s article spends a lot of time examining how computer vision versions can create other words. He raises a number of legitimate points about the state of affairs 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 image types, in large part due to the absence of contextual contexts in which to look at images ( as a result of having separate “foundation” models for words 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 and provide a starting point for alt text, even if the rapid reads,” What is this BS?” That’s not correct at all … Let me try to offer a starting point— I think that’s a gain.

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 clarify which situations require image descriptions, and it will increase authors ‘ effectiveness in making their sites more visible.

Although complex images, such as graphs and charts, are challenging to summarize in any way ( even for humans ), the image example provided in the GPT4 announcement provides an intriguing opportunity as well. Let’s say you came across a map that merely stated the chart’s name and the type of representation it was:” Pie chart comparing smartphone use to have phone usage in 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 people could ask questions about the vivid if their browser knew that it was a pie chart ( because an onboard model determined this ).

• Perform more people use have apps or smartphones?
• How many more?
• Is there a group of people who don’t collapse under any 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 helpful in education settings to assist those who can see these charts as they are able to comprehend the data contained therein.

What if you could request your website to make a complicated chart simpler? What if you asked it to separate a single line from a range curve? What if you could request your website to transform the different lines ‘ colors so they match your color blindness better? What if you asked it to switch colours in favor of habits? Given these resources ‘ chat-based interface and our existing ability to manipulate photos in today’s AI devices, that seems like a chance.

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 call 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 to be equally accurate to say that all computer models have the potential to amplify conflict, bias, and intolerance. We all 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. Many of these are the result of a lack of diversity in the people who create and build them. When these platforms are built with inclusively baked in, however, there’s real potential for algorithm development to help people with disabilities.

Take Mentra, for example. They serve as a network of employment for people who are neurodivers. They match job seekers with potential employers using an algorithm based on more than 75 data points. On the job-seeker side of things, it considers each candidate’s strengths, their necessary and preferred workplace accommodations, environmental sensitivities, and so on. On the employer side, it considers each work environment, communication factors related to each job, and the like. Mentra made the decision to change the script when it came to the typical 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 that 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 a 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 different from your current sphere of influence in some fundamental ways. For instance, if you follow a group of white men who are not white or aren’t white and who also discuss AI, it might be wise to follow those who are also disabled or who are not white. 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

I’m sure I could go on and on about using AI to assist people with disabilities, but I’m going to make this last section into a bit of a lightning round if I weren’t trying to put this together in between other tasks. 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. It’s possible to train an artificial intelligence model to mimic your voice, which can be incredibly helpful for those who have ALS ( Lou Gehrig’s disease ), motor neuron disease, or other medical conditions that can make it difficult to talk. This is, of course, the same tech that can also be used to create audio deepfakes, so it’s something that we need to approach 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 or simplified versions, or even text that has been prepared for Bionic Reading.

The value of various teams and sources of data

Our differences must be acknowledged as important. 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. Our differences must be reflected in the data we use to develop new models, and those who provide it need to be compensated for doing so. Inclusive data sets produce stronger models that promote more justifiable outcomes.

Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that the training data includes information about disabilities written by people with a range of disabilities.

Want a model that doesn’t use ableist language? You might be able to use already-existing data sets to create a filter that can read and interpret ableist language before it is read. 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 secret. Instead of letting it get done by me, I do it.

I am a artistic. This tag is not appropriate for all creatives. No everyone see themselves in this manner. Some innovative individuals incorporate technology into their work. That is their reality, and I regard it. Sometimes I even envy them, a minor. But my operation is different—my becoming is unique.

Apologizing and qualifying in advance is a diversion. My head uses that to destroy me. I put it off for the moment. I may forgive and be qualified at any time. after I’ve said what I should have. Which is challenging enough.

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

Sometimes it does. Maybe I have to make something right away. I’ve learned to avoid saying it right away because they think you don’t work hard enough when you realize that sometimes the idea really comes along and it is the best plan and you know it is the best idea.

Sometimes I just keep working until the thought strikes me. Maybe it arrives right away, but I don’t remind people for three days. Maybe I get so excited about an idea that just came along that I blurt it out and didn’t stop myself. like a child who discovered a reward in a box of Cracker Jacks. I occasionally manage to escape this. Maybe other people agree: yes, that is the best idea. Most times they don’t and I regret having given way to joy.

Passion should only be saved for the meet, when it matters. not the informal gathering that two different gatherings precede that appointment. Anyone knows why we have all these sessions. We keep saying we’re going to get rid of them, but we end up merely trying to. They occasionally also are good. But occasionally they are a hindrance to the actual job. 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. Suddenly I digress. I am a artistic. That is the topic.

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

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

I am a artistic. 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 a Eureka, which has nothing to do with boiling pots and sizzling oil, and I may be making dinner. I frequently have a plan for action when I wake up. The idea that may have saved me disappears almost as frequently as I become aware and a part of the world once more as a senseless wind of oblivion. For imagination, I believe, comes from that other world. 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. And it’s for philosophers to build massive soldiers in their imaginative world that they claim to be true. But that is another diversion. And a sad one. Possibly on a much bigger issue than whether or not I am creative. But this is still a departure from what I said when I came around.

Often the process is evasion. And horror. 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 reality is correct, too. However, mine is for me.

Creatives identify artists.

Negatives are aware of cons, just like queers are aware of queers, just like real rappers are aware of true rappers. Creatives feel enormous regard for creatives. We love, respect, emulate, and almost 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 simply 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 something incredible. They give birth to something that was unable to occur before them or otherwise. 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 graphics! Also, I‘m no Miyazaki. Now THAT is brilliance. That is brilliance directly from God’s heart. This half-starved small item that I made? It essentially fell off the back of the pumpkin trailer. And the carrots weren’t even clean.

Creatives knows that, at best, they are Salieri. That is what Mozart’s artists do, also.

I am a artistic. I haven’t worked in advertising in 30 years, but in my hallucinations, it’s my former artistic managers who judge me. They are correct in doing so. I am very lazy, overly simplistic, and when it actually counts, my mind goes blank. There is no supplement for innovative 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 my creative endeavors, the faster I progress in my work, and the more I slog through loops and gaze blankly before beginning that task.

I can move ten times more quickly than those who aren’t creative, those who have just been creative for a short while, and those who have only been creative for a short time in their careers. Simply that I spend twice as long putting the work off as they do before I work ten times as quickly as they do. When I put my mind to it, I am so confident in my ability to do a great career. 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 innovative. No an actor. Though I dreamed, as a boy, of eventually being that. Some of us criticize our abilities and like our own selves because we are not Michelangelos and Warhols. That is narcissism—but at least we aren’t in elections.

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

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 love 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 seriously. No actually. 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 innovative. I worry that my little product will disappear unexpectedly.

I am a artistic. I spend way too much time making the next thing, given that almost nothing I create did achieve the level of greatness I conceive of.

I am a artistic. I think method is the most amazing secret. I think so strongly that I am actually foolish enough to post 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 wonderful.

There. I think I’ve said it.

I’ve been fascinated by shows since I was a child. I loved the heroes and the excitement—but most of all the stories. I aspired to be an artist. And I hoped that I would have the same opportunities as Indiana Jones did, leading to thrilling adventures. I also dreamed up suggestions for videos that my friends and I could render and sun in. But they never advanced. However, I did end up working in user experience ( UI). Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer research is story. And to get the most out of customer studies, you must tell a compelling story that involves stakeholders, including the product team and decision-makers, and piques their interest in learning more.

Think of your preferred film. More than likely it follows a three-act construction that’s frequently seen in story: the layout, the fight, and the quality. The second act provides an overview of the current events and allows you to understand the characters, their difficulties, and difficulties. Act two sets the scene for the fight and introduces the activity. Here, difficulties grow or get worse. The decision is the third and final action. This is where the problems are resolved and the figures grow and change. I believe that this architecture is also a great way to think about customer study, and I think that it can be particularly helpful in explaining person exploration to others.

Use story as a framework when conducting research.

It’s unfortunate to say that many people now view studies as being unprofitable. If finances or timelines are strong, analysis tends to be one of the first points to go. Some goods managers rely on designers or, worse, their own judgment to make the “right” decisions for users based on their own knowledge or accepted best practices rather than investing in research. That might lead to some groups getting in the way, but it’s too easy to overlook the real problems facing users. To be user-centered, this is something we really avoid. Design is enhanced by consumer study. It keeps it on track by pointing out issues and options. Being aware of the issues with your goods and reacting to them can help you stay ahead of your competition.

Each action in the three-act structure is crucial to telling the complete story, and each action corresponds to a specific stage of the process. Let’s take a look at the various functions and how they relate to consumer study.

Act one: installation

The rig consists entirely in comprehending the history, and that’s where basic research comes in. Foundational research aids in understanding people and identifying their issues ( also known as relational, discovery, or preliminary research ). You’re learning about what exists now, the obstacles people have, and how the problems affect them—just like in the videos. You can conduct contextual inquiries or diary studies ( or both! ) to conduct foundational research. ), which can assist you in identifying both prospects and problems. It doesn’t need to get a great investment in time or money.

Erika Hall discusses the most effective anthropology, which can be as straightforward as spending 15 hours with a customer and asking them to” Walk me through your morning yesterday.” That’s it. Current that one ask. Opened up and spend fifteen minutes listening to them. Do everything in your power to protect both your objectives and yourself. Bam, you’re doing ethnography”. According to Hall, “[This ] will probably prove quite fascinating. In the unlikely event that you don’t learn anything new or important, move on with more assurance in your direction.

This makes total sense to me. And I adore how customer research is now so simple. You can only attract participants and do it! You don’t need to create a lot of documentation. This can offer a wealth of knowledge about your customers, and it’ll help you better understand them and what’s going on in their life. That’s exactly what work one is all about: understanding where people are coming from.

Jared Spool discusses the significance of basic research and how it does make up the majority of your study. If you can pick from any further user data that you can get your hands on, such as surveys or analytics, that can complement what you’ve heard in the fundamental studies or even time to areas that need more research. All of this information helps to give a more in-depth picture of the state of issues and all of its flaws. And that’s the start of a gripping tale. It’s the place in the story where you realize that the principal characters—or the people in this case—are facing issues that they need to conquer. This is where you begin to develop compassion for the characters and support their success, much like in films. And hey, it looks like everyone else is doing the same. Their love may be with their company, which could be losing wealth because people didn’t complete certain tasks. Or perhaps they have empathy for people ‘ challenges. In either case, action one serves as your main strategy for piqueing interest and investment from the participants.

When partners begin to understand the value of basic research, that is open doors to more opportunities that involve users in the decision-making approach. And that can influence product teams ‘ focus on improving. Everyone benefits from this, including the product, stakeholders, and users. It’s like winning an Oscar in movie terms—it often leads to your product being well received and successful. And this might serve as a motivator for stakeholders to carry this out with other goods. The secret to this process is storytelling, and knowing how to tell a compelling story is the only way to entice stakeholders to do more research.

This brings us to act two, where you iteratively evaluate a design or concept to see whether it addresses the issues.

Act two: conflict

Act two is all about approving the issues you raised in act one. This usually involves directional research, such as usability tests, where you assess a potential solution ( such as a design ) to see whether it addresses the issues that you found. Unmet needs or issues with a flow or process that are making users uncomfortable could be the causes. More problems will come up in the process, much like in the second act of a film. It’s here that you learn more about the characters as they grow and develop through this act.

Usability tests should typically consist of five participants, according to Jakob Nielsen, who found that that number of users can typically identify the majority of the issues:” As you add more and more users, you learn less and less because you will keep seeing the same things again and again… After the fifth user, you are wasting your time by observing the same findings repeatedly but not learning much new.”

There are also similarities to storytelling here: if you try to tell a story with too many characters, the plot may become lost. Having fewer participants means that each user’s struggles will be more memorable and easier to relay to other stakeholders when talking about the research. This can help convey the problems that need to be solved while also highlighting the worth of conducting the research in the first place.

Usability tests have been conducted in person for decades, but you can also do them remotely using software like Microsoft Teams, Zoom, or other teleconferencing software. This approach has become increasingly popular since the beginning of the pandemic, and it works well. You might interpret in-person usability tests as a form of theater watching as opposed to remote testing. Each has advantages and disadvantages. In-person usability research is a much richer experience. The sessions are conducted with other stakeholders in mind. Additionally, you’ll also hear their reactions in real-time, including surprises, disagreements, and discussions of what they’re seeing. Much like going to a play, where audiences get to take in the stage, the costumes, the lighting, and the actors ‘ interactions, in-person research lets you see users up close, including their body language, how they interact with the moderator, and how the scene is set up.

If conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may be very different from one another. You can conduct usability testing in real life by creating a replica of the product’s user interface and conducting research there. Or you can go out to meet users at their location to do your research. With either option, you can see how things work in context, how things change, and how conversion can change completely in different ways depending on the circumstances. You have less control over how these sessions end as researchers, but this can occasionally help you understand users even better. Meeting users where they are can provide clues to the external forces that could be affecting how they use your product. Usability tests in person offer a level of detail that is frequently absent from remote testing.

That doesn’t mean that “movies” —remote sessions—aren’t a good option. Remote sessions can reach a wider audience. They make it possible for much more people to participate in the research and to observe what is happening. Additionally, they make access to a much wider user base geographically. But with any remote session there is the potential of time wasted if participants can’t log in or get their microphone working.

You can ask real users questions to understand their thoughts and understanding of the solution as a result of usability testing, whether it is conducted remotely or in person. This can help you identify issues as well as understand why they were initially issues. Furthermore, you can test hypotheses and gauge whether your thinking is correct. By the end of the sessions, you’ll have a much clearer understanding of how useful the designs are and whether or not they fulfill their intended purpose. The excitement is in the second act, but there are also potential surprises in the third. This is equally true of usability tests. Unexpected things that participants say frequently alter the way you look at things, and these unexpected revelations can lead to unexpected turns in the narrative.

Unfortunately, user research can occasionally be viewed as unreliable. And too often usability testing is the only research process that some stakeholders think that they ever need. There isn’t much to be gained by conducting usability testing in the first place if the designs you’re evaluating in the usability test aren’t grounded in thorough understanding of your users ( foundational research ). Because you’re narrowing the scope of what you’re receiving feedback on without understanding the needs of the users. As a result, there’s no way of knowing whether the designs might solve a problem that users have. In the context of a usability test, it’s only feedback on a particular design.

On the other hand, if you only do foundational research, you won’t know whether the object you’re building will actually solve the problem you might have intended to solve. This illustrates the importance of doing both foundational and directional research.

In act two, stakeholders will hopefully be able to observe the story develop during the user sessions, which reveal the conflict and tension in the current design’s highs and lows. And in turn, this can encourage stakeholders to take action on the issues raised.

Act three: resolution

The third act is about resolving the issues from the first two acts, while the first two acts are about understanding the background and the tensions that can compel stakeholders to take action. While having an audience for the first two acts is crucial, having them stay for the final act is also important. That means the whole product team, including developers, UX practitioners, business analysts, delivery managers, product managers, and any other stakeholders that have a say in the next steps. It allows the entire team to discuss what’s possible within the project’s constraints, ask questions, and discuss user feedback together. And it gives the UX design and research teams more time to clarify, suggest alternatives, or provide more context for their choices. So you can get everyone on the same page and get agreement on the way forward.

Voiceover narration of this act is typically used with audience input. The researcher serves as the narrator, who depicts the issues and what the product’s potential future might look like in light of what the team has learned. They give the stakeholders their recommendations and their guidance on creating this vision.

In the Harvard Business Review, Nancy Duarte describes a method for structuring presentations that follow a persuasive narrative. The most effective presenters” set up a conflict that needs to be resolved” using the same methods as great storytellers, Duarte writes. ” That tension helps them persuade the audience to adopt a new mindset or behave differently”.

This kind of structure is in line with research findings, particularly those from usability tests. It provides evidence for “what is “—the problems that you’ve identified. And “what might be “—your suggestions for how to respond to them. And so forth and forth.

You can reinforce your recommendations with examples of things that competitors are doing that could address these issues or with examples where competitors are gaining an edge. Or they can be visual, like quick sketches of how a new design could look that solves a problem. These can help create momentum and conversation. And this continues until the end of the session when you’ve wrapped everything up in the conclusion by summarizing the main issues and suggesting a way forward. This is the section where you make the most of the main themes or issues and what they mean for the finished product, or the story’s denial. The stakeholders will now have the opportunity to take the next steps, and hopefully the will-power to do so!

While we are nearly at the end of this story, let’s reflect on the idea that user research is storytelling. The three-act structure of user research contains all the components for a good story:

Act one: You encounter the protagonists ( the users ) and the antagonists ( the issues affecting users ). This is the beginning of the plot. Researchers might employ techniques like contextual inquiry, ethnography, diary studies, surveys, and analytics in act one. These techniques can produce personas, empathy maps, user journeys, and analytics dashboards.

Act two: Next, there’s character development. The protagonists face problems and difficulties, which they must overcome, and there is conflict and tension. Researchers might employ heuristics evaluation, usability testing, competitive benchmarking, and other methods in act two. The output of these can include usability findings reports, UX strategy documents, usability guidelines, and best practices.

Act three: The protagonists win, and you can see what a better future might look like. Researchers may use techniques like presentation decks, storytelling, and digital media in act three. The output of these can be: presentation decks, video clips, audio clips, and pictures.

The researcher performs a number of tasks: they are the producer, the director, and the storyteller. The participants only have a small part in the study, but they are significant characters ( in it ). And the stakeholders are the audience. However, the most crucial thing is to get the narrative straight and to use storytelling to research users ‘ stories. In the end, the parties should leave with a goal and an eagerness to fix the product’s flaws.

So the next time that you’re planning research with clients or you’re speaking to stakeholders about research that you’ve done, think about how you can weave in some storytelling. In the end, user research is beneficial for everyone, and all you need to do is pique stakeholders ‘ interest in how the story ends.

We concur that computer-generated eyes may be excellent candidates for personas, but not for the reason you might think otherwise. 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 snapshot that is taken out of context.

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

A step up, personalities

Most manufacturers have at least once in their careers created, used, or encountered personalities. 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 consist of a name, profile picture, quotes, demographics, goals, needs, behavior in relation to a particular service/product, emotions, and motivations ( for instance, see Creative Companion’s Persona Core Poster ). According to design firm Designit, the goal of personas is” to make the research relatable, ]and ] easy to communicate, digest, reference, and apply to product and service development.”

The decontextualization of identities

People are well-known because they make “dry” research information relevant and more people. However, this approach places a cap on the author’s data analysis, making it impossible for the investigated users to be excluded from their particular contexts. As a result, personalities don’t describe important factors that make you know 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 history knowledge to understand 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 dynamic, according to people.

Here’s a painfully obvious truth: people are not a fixed set of features. Although many businesses still try to box in their employees and customers with 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 type of person you are at each particular moment depends on the context, the impact of other people, your mood, and the whole history that preceded it.

Personalities do not account for this variation in their attempt to improve reality; instead, they present a consumer as a predetermined set of features. Like character tests, personas seize people away from real life. Even worse, individuals are labeled as” that kind of guy” with no means to practice their innate flexibility and are reduced to a brand. This behavior defies stereotypes, diminishes diversity, and doesn’t reveal reality.

Personas rely on people, not the environment

In the real world, you’re creating content for a situation, not an entity. There are economic, political, and cultural factors to consider when a person lives in a home, a community, or an ecosystem. A pattern is not meant for a single customer. Instead, you create a pattern for one or more specific situations where a certain product might be used by a large number of people. But, personas do not explicitly explain how the person interacts with the environment but rather present the user alone.

Do you usually make the same decision over and over again? Possibly you’ve made a commitment to veganism but still want to get some meat when your family visit. Your decisions, including your behavior, opinions, and statements, are not only completely accurate but very situational because they depend on a range of circumstances and variables. The image that “represents” you wouldn’t take into account this interdependence, because it doesn’t explain the grounds of your choices. It doesn’t offer a explanation for why you act in the way you do. 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, identities are often placed in a situation that’s a” specific environment with a problem they want to or have to solve “—does that mean environment actually is considered? Unfortunately, what frequently occurs is that you choose a fictional character to play with 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 synthesized from observations of many people. The famous example of the USA Air Force designing planes based on the average of 140 of their pilots ‘ physical dimensions and 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 was taken out of context? They uttered my words, but I didn’t mean it that way. 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. The intended purpose was lost as a result. You collect someone’s statement ( or goal, need, or emotion ) into which its meaning can only be understood if it is provided with its own specific context, and then report it as an isolated finding.

But personas go a step further, extracting a decontextualized finding and joining it with another decontextualized finding from somebody else. Because it lacks the underlying causes for and how that finding came about, the results of the analysis frequently fail to make sense. It’s unclear or even contradictory. 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 usefulness?

The validity of personas is deceiving.

To a certain extent, designers realize that a persona is a lifeless average. Designers create “relatable” personas to make them appear like real people in order to overcome this. Nothing better captures 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. You purposefully understate the fact that” John Doe” is an abstract representation of research findings, but wouldn’t it be much more responsible to emphasize that John is only an abstraction? Let’s say something is artificial.

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. They introduce a number of biases in doing so, as with everything they produce. As designers, as Designit puts it, we can” contextualize]the persona” based on our experience and reality. 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.

Everyone should use their own empathy and develop their own interpretation and emotional response if we want to conduct good design research by reporting the reality “as-is” and making it relatable for our audience.

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 being. Unfortunately, despite being a step in the right direction, this proposal disregards the fact that people are influenced by how their personality, behavior, and, yes, mindset are shaped by their surroundings. Therefore, Mindsets are also not absolute but change in regard to the situation. What determines a particular Mindset, remains to be seen.

Margaret P., the author of the article” Kill Your Personas,” who has argued for the use of persona spectrums that include a range of user abilities, offers an alternative. 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 viewed from within a spectrum.

In developing an alternative to personas, we aim to transform the standard design process to be context-based. Contexts are generalizable and have patterns that we can recognize, just like we tried to do this with people before. How can we identify these patterns, then? How do we ensure truly context-based design?

Understand real people in a variety of contexts

Nothing about reality can be more relatable and inspiring. Therefore, we have to understand real individuals in their multi-faceted contexts, and use this understanding to fuel our design. This approach is known 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]? ]” You don’t need to, which is the simple answer. 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. If this sample is chosen wisely and you have a deep understanding of the sampled people, you can infer how the rest of the population thinks and acts. There’s no need to study seven Susans and five Yuriys, one of each will do.

In the same way, you don’t need to comprehend Susan in fifteen different ways. You have understood Susan’s plan of action once you have seen her in a few different settings. 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 total population you’re researching. You don’t want to see abstracts of them! 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 remains: how do you select a sample representative? First, you must consider the target market 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 made the decision to purchase it, those who had been influenced by other people’s decisions, 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. Your qualitative data will be enriched with examples and anecdotes thanks to this. 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 later become much more interesting and precise with the additions made by their spouses, partners, 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. She uses me 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 serve as examples of the larger picture. 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. We also included the individual’s name and age, but they’re optional; they’ll help the stakeholders transition from personas and allow them to connect multiple actions and contexts to the same person.

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 ensuring that each participant’s various selves are truthful. Photos of the setting and anonymized actors are necessary to create realistic Selves in the case of real-life ethnographic research. 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. Therefore, we depicted him taking a hike with his young daughter.

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 a different deck full of self-assessments.

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.

A particularly intriguing finding was made in our example project regarding the concept of humidity. We became aware of the importance of monitoring humidity for health and how a climate that is 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

When you conduct your research using the Dynamic Selves method, you start to notice peculiar social relations, peculiar circumstances that people face and the consequences of their actions, and that people are surrounded by ever-changing environments. In our thermostat project, we have come to know one of the participants, Davide, as a boyfriend, dog-lover, and tech enthusiast.

Davide is a person we might have once referred to as 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.

Once you have fully grasped the underlying causes of Davide’s behavior and have understood them in detail, you can then generalize how he would act in a different circumstance. You can infer what he would think and do in the circumstances ( or scenarios ) you design for using your understanding of him.

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 empathy for people and how difficult it is to do so with other people. We have the deepest sympathy for people who are able to relate to us.

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 biases. Simply put, this person is 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 stop using shortcuts and reminds you to check your designs every day.

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 by adding more weight and urgency:” When I met Alessandra, the conditions of her workplace struck me. Noise, bad ergonomics, lack of light, you name it. I’m worried that her life will become more complicated if we choose to use this functionality.

Conclusion

In their article on Mindsets, Designit mentioned 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 environments.

Design needs to be simplified, not necessarily 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. Avoid using those and use them to describe 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.

What on earth is a passionate stress, 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 works for a lot of clients, all of whom she enjoys. 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.

Sounds like this person needs self-care because she has too much on her disk. But no, she doesn’t have occasion for that. She begins to feel as though she’s dropping pellets. Not enough is achieved. There’s not enough of her to be here and that, she is trying to divide her head in two all the time, all day, every day. She begins to question herself. And as those feelings grow more in, her domestic tale grows more and more important.

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

This loop is challenging and risky. Understand why? Because when she doesn’t complete that new purpose, the story will only get worse. She immediately starts failing. She isn’t doing much. She is insufficient. She does fail, she might refuse her family, but she’ll discover more to do. She doesn’t nap as much, proceed because much, all in the attempts to do more. Trying to prove herself to herself, but always succeeding in any endeavor. Always feeling “enough”

But, yeah, that’s what zealous burnout looks like for me. It doesn’t develop immediately in a great gesture; it develops gradually over the course of several weeks and months. Not a man losing concentration, but rather a burning out approach that seems to be speeding up. I rate up and up and up… and therefore I simply quit.

I am the only person who has the potential.

The things that shape us are interesting. Through the camera of youth, I viewed the worries, problems, and sacrifices of someone who had to make it all work without having much. I never went without and also received an extra here or there because my mom was so competent and my father was so friendly.

Growing up, I didn’t feel shame when my mom gave me food postcards; 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 in my house as the non-disabled people. 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 in charge of the problem. I’ve been told that I seem brave 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 person’s fears.

And here I am, surrounded by enormous tasks ahead of me, assuming that I am the one who is and therefore should, more than 30 times afterward, still feeling the urge to aimlessly drive myself forward. I feel more motivated to show that I can 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 failures, because I have seen how strong that tide can be—it pulls you along the way. I truly believe I have had the opportunity to avoid many of the difficulties that came with my youth. Having said that, I continue to believe that she should and am still” the one who can.” As a result, I would think I’ve failed if I had to struggle to make ends meet for my own family. Though I am supported and educated, most of this is due to good fortune. However, I’ll give myself the haughtiness of claiming that my choices were wise and that they had sparked that luck. My sense of self is the result of the notion that I am” the one who can” and feel compelled to accomplish the most. I can choose to stop, and with some quite literal cold water splashed in my face, I’ve made the choice to before. However, I don’t always choose to stop, so I move on, driven by a fear that is so present in me that I hardly ever notice until I’m completely worn out.

So why all the history? You see, burnout is a fickle thing. Over the years, I have read and heard a lot about burnout. Burnout is present. Especially now, with COVID, many of us are balancing more than we ever have before—all at once! It’s challenging, and so many amazing professionals are affected by the avoidance, the shutting down, and the procrastination. There are significant articles that, in my opinion, relate to the majority of people around, but not me. That’s not what my burnout looks like.

The perilous invisibility of zealous burnout

The extra hours, extra work, and overall focused commitment are often viewed as an asset in many workplaces ( and occasionally that’s all it is ). They see someone trying to rise to challenges, not someone stuck in their fear. Many well-intentioned organizations have measures in place to safeguard their employees from burnout. However, in situations like this, those alarms don’t always ring, and some organization members are surprised and depressed when the inevitable stop happens. And sometimes maybe even betrayed.

When it comes to parenting, which is more so when it comes to working, participating in after-school activities, practicing self-care in the form of diet and exercise, and still meeting with friends for coffee or wine, it is more often said that mothers are praised as being so on top of it all. Many of us watched endless streaming COVID episodes to see how challenging the female protagonist is, but she is strong, funny, and capable of doing it. It’s a “very special episode” when she breaks down, cries in the bathroom, woefully admits she needs help, and just stops for a bit. Truth 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, the perception that it’s what we should strive for frequently permeates much of society.

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 feel the pressure to do everything while giving absolutely everything. 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.

And there are costs that go beyond happiness. 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 so is our way of responding to stress. 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 you’ll just stop enjoying yourself as much as you do.

Do you feel empowered to say no? I’ve observed in myself and others that when someone is going out, they no longer feel like they can say no to things. Even those who don’t” speed up” feel pressured to say “yes” to avoid apprehension.

What are three things you’ve done for yourself? Another fact to keep in mind is that we all have a tendency to stop doing things for ourselves. 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, and/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 of work since January, then perhaps it’s not crunch time; perhaps it’s 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 end

Take the time to listen to your friend in the same way. 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.
• Leave the house.
• Take a break, please.
• Overall, practice self-care.

I find those challenging 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 things that I do when I start to feel like I’m going into a zealous burnout to help me remember the airline attendant advice to put the mask on yourself first.

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, do it for someone else. Most of us work in a digital world, so cooking can fill all of your senses and force you to be in the moment with all the ways you perceive the world. It can help you get a better perspective and help you get out of your head. I’ve been known to pick a location on a map and prepare food that comes from it ( thank you, Pinterest ) in my home. 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 that are really present. 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, approach a trusted friend and express your concerns verbally. 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 I admire most about my husband is how he can simplify things down to their simplest bits, despite often after the fact. 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 are typically appreciated in retrospect.

Grab a book, please!

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, a tactic I enjoy using is to read or listen to a book that is NOT related to my work-life balance. The following books helped me balance out after I’ve read them because my mind was pondering the subjects ‘ interesting points rather than circling them:

• The Drunken Botanist by Amy Stewart
• Darin Olien’s Superlife
• A Brief History of Every Person 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 countless permaculture and gardening topics. For the record, I do not have a particularly large food garden, nor do I own livestock of any kind… yet. I just find the subject fascinating, and it is unrelated to anything that needs to be done in my life.

Give yourself a break.

You are never going to be perfect—hell, it would be boring if you were. It’s acceptable to have flaws and imperfections. Being tired, depressed, and worried is human nature. It’s OK to not do it all. Although being imperfect is terrifying, you cannot be brave without being fearful.

This is the most crucial part: give 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.

This is challenging. It is hard for me. That it’s okay to stop is what inspired me to write this. It’s acceptable that you have to stop an unhealthy habit that could even help you and those around you. 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 tell you 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 of love, determination, motivation, and other wonderful qualities that contribute to your incredible persona. 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 we are needed, even when we are exhausted to the core 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 in human nature, but that doesn’t really sound so 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 be considerate.

One of the most powerful smooth abilities we have at our disposal is the ability to work together to improve our designs while developing our own abilities and perspectives, regardless of how it is used or what it might be called.

Feedback is also one of the most underestimated equipment, and generally by assuming that we’re already good at it, we settle, forgetting that it’s a talent that can be trained, grown, and improved. Bad comments can lead to conflict in projects, lower confidence, and long-term, undermine trust and teamwork. Quality opinions can be a revolutionary force.

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 comment on their beloved design tools, and so on.

Design criticism is frequently used as a term for a type of collaborative feedback 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 content of the feedback is the basis of every effective criticism, so where do we need to begin? There are many versions that you can use to design your information. This one from Lara Hogan is the one I personally like best because it’s obvious and actionable.

This formula is typically used to provide feedback to people, but it also fits really well in a pattern criticism because it finally addresses one of the main inquiries that we work on: 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 stream blueprint, and an outline of the decisions made. You notice a flaw in the situation. You’ll have a psychological unit that can help you become more precise and effective if you keep the three components of the equation in mind.

Here is a reply that could be given as a part of some comments, and it might seem reasonable at a first glance: it seems to casually serve the elements in the equation. But does it exist?

Concerning the buttons ‘ styles and hierarchy, it seems off. Can you change them?

Observation for design feedback doesn’t just mean pointing out which area of the interface your feedback touches, but it also means offering a perspective that’s as specific as possible. Do you offer the user’s viewpoint? Your expert perspective? From a business perspective? 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.

By provoking the designer’s critical thinking while receiving the feedback, the question approach is intended to provide open guidance. 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, the difference between the two can be demonstrated as an illustration:

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 you think the suggestion is better at this point.

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 the question or the request approach may also sometimes be a matter of personal preference. I spent a while working on improving my feedback, conducting anonymous feedback reviews and sharing feedback with others. 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. Surprise surprise, my next round of criticism from a specific 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 changed my feedback so that it included 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 times because some changes may be obvious ( the font used doesn’t follow our guidelines ), and others because the team may have a lot of internal knowledge, making some of the whys may be implied.

Therefore, the above equation serves 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 tone

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 have 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 logical, solid, and constructive. It’s the kind of feedback that, regardless of whether it’s positive or negative, is viewed as 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. When a new feature’s entire high-level information architecture is about to go on sale, it might still be relevant if the 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 morning? Iteration later? Polishing work in progress? Each of these needs a different one. 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. Before writing, it’s important to make sure the person we’re writing will actually benefit them and improve the overall project. 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 especially in diverse and cross-cultural workplaces because having excellent writing, perfect timing, and the right attitude might not be effective if the writing style leads to miscommunications. There could be many reasons for this: some words might cause particular reactions, some non-native speakers might not understand all the nuances of some sentences, and other times our brains might be different and we might perceive the world differently. 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 sound advice, but I also got a surprise comment. They pointed out that when I wrote” Oh, ]… ]”, I made them feel stupid. That’s not what I meant to say! 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 is that people frequently beat around the bush, especially in teams with strong group spirit. 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: we can devote more time to making sure that the suggestions ‘ clarity of communication and actionability fulfill 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 encounter with it? Do you have a high-level perspective, or are you just learning the ins and outs? Are there regressions? Which user’s point of view are you addressing when offering your feedback? Is the design iteration ready to ship this, or are important issues still 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 connected to my work, I would say that, underlining my opinion as external, and if I had no idea how the project came to that conclusion.

We often focus on the negatives, trying to outline all the things that could be done better. That’s obviously important, but it’s even more crucial to concentrate on the positives, especially if you saw improvement in the previous iteration. Although this may seem superfluous, it’s important to remember that design has a number of possible solutions to 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. There is a significant difference between a critique of a design that is already in good shape and one that isn’t quite there yet.

Depersonalizing the feedback is another way to improve it: comments should always be about the work and never the creator of it. It’s” This button isn’t well aligned” versus” You haven’t aligned this button well”. This can be changed in your writing very quickly by reviewing it just before sending.

One of the best ways to assist the designer who is reading your feedback is to divide it into bullet points or paragraphs, which are simpler to review and analyze one by one, in terms of actionability. For longer pieces of feedback, you might also consider splitting it into sections or even across multiple comments. Of course, it can also be particularly helpful to include screenshots or indicators of the specific area of the interface you’re referring to.

I’ve personally used emojis to enhance the bullet points in some situations. 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 an exploration, an open alternative, or just a note for something I’m not sure about. 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 a version 1. 1.0 release.
• � � 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. Should we 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 maintain consistency in the visual hierarchy.
• Background: Using 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 allows in-place feedback to provide feedback directly in Figma? These are generally difficult to use because they conceal discussions and are harder to follow, but in the right setting, they can be very effective. Just make sure that each of the comments is separate so that it’s easier to match each discussion to a single task, similar to the idea of splitting mentioned above.

One last word: avoid 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. You might have to reword it 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. For this reason, I suggest using software to save these discussions without keeping them hidden until they are resolved.

Content, tone, and format are all there. 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 other people’s feedback. Then the second, followed by 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 contributions to the initial draft of this article.

” Any post” you might have? is perhaps one of the worst ways to ask for opinions. It’s obscure and unreliable, and it doesn’t give a clear picture of what we’re looking for. Great feedback begins sooner than we might anticipate: it begins with the demand.

It might seem contradictory to start the process of receiving feedback with a problem, but that makes sense if we realize that getting feedback can be thought of as a form of pattern research. The best way to ask for feedback is to write strong questions, just like we wouldn’t do any studies without the right questions to get the insight we need.

Design criticism is never a one-time procedure. Sure, any great comments process continues until the project is finished, but this is especially true for layout because architecture work continues iteration after iteration, from a high level to the finest details. Each stage requires its unique set of questions.

Lastly, we need to review what we received, get to the heart of its conclusions, and take action, like with any good research. Problem, generation, and evaluation. Let’s take a closer look at each of those.

The query

Being available to input is important, but we need to be specific about what we’re looking for. Any comments,” What do you think,” or” I’d love to hear your mind” at the conclusion of a presentation are likely to garner a lot of different ideas, or worse, to make everyone follow the lead of the first speaker. And finally, we become irritated because ambiguous queries like those can result in people leaving reviews that don’t even consider keys. Which might be a savory matter, so it might be hard at that point to divert the crew to the topics that you had wanted to focus on.

But how do we enter this circumstance? It’s a combination of various aspects. One is that we don’t often consider asking as a part of the input approach. Another is how healthy it is to keep the issue open and assume that everyone else will agree. Another is that being extremely precise is frequently not necessary in non-professional conversations. In short, we tend to underestimate the importance of the concerns, so we don’t work on improving them.

The practice of asking nice questions guidelines and concentrates the criticism. It’s even a form of acceptance because it specifies what kind of opinions you’d like to receive and how you’re open to them. It puts people in the right emotional state, especially in situations when they weren’t expecting to give opinions.

There isn’t a second best way to ask for opinions. Sensitivity can take countless forms, and it just needs to be that. A design for design critique that I’ve found especially helpful in my training is the one of stage over depth.

The term” level” refers to each stage of the process, specifically the design phase. The kind of feedback changes as the person research moves forward to the final design. But within a single stage, one might also examine whether some assumptions are correct and whether there’s been a suitable language of the amassed input into updated designs as the job has evolved. The levels of consumer experience may serve as a starting point for possible questions. What are your project goals, exactly? User requirements? Funnality? Material? Contact design? a system of information layout Interface design Navigation style? Visual layout Brand?

Here’re a some example questions that are specific and to the place that refer to different levels:

• Functionality: Is it attractive to automate accounts creation?
• Contact design: Please review the updated movement and let me know if there are any steps or error points I may have missed.
• Information structures: We have two competing bits of information on this site. Does the architecture make a good communication between them both?
• User interface design: What do you think about the problem desk at the top of the page, which makes sure you see the following error even if it is outside the viewport?
• Navigation style: From study, we identified these second-level routing items, but when you’re on the webpage, the list feels very long and hard to understand. Do you have any ideas for how to handle this?
• The bottom-right corner’s slippery messages are clearly visible, but are they sufficient?

The another plane of sensitivity is about how heavy you’d like to go on what’s being presented. For instance, we may have introduced a new end-to-end movement, but you might want to know more about a particular viewpoint you found challenging. This can be particularly helpful from one generation to the next when it’s crucial to identify the areas that have changed.

There are other things that we can consider when we want to accomplish more specific—and more effective—questions.

A quick fix is to get rid of the general qualifiers from issues like “good”, “well,” “nice,” “bad,” “okay,” and” cool.” Asking,” When the stop opens and the switches appear, is this conversation excellent, for instance?” may seem precise, but you can place the “good” tournament, and transfer it to an even better query:” When the wall opens and the buttons appear, is it clear what the next action is”?

Sometimes we do want a lot of feedback. That’s uncommon, but it can occur. In that sense, you might still make it explicit that you’re looking for a wide range of opinions, whether at a high level or with details. Or perhaps you should just say,” At first glance, what do you think”? so that it is obvious that what you’re asking is open ended but focused on a person’s impression after their first five seconds of inquiry.

Sometimes the project is particularly expansive, and some areas may have already been explored in detail. In these circumstances, it might be helpful to state explicitly that some parts are already locked in and aren’t accessible for feedback. Although it’s not something I’d recommend in general, I’ve found it helpful in avoiding falling into rabbit holes like those that could lead to further refinement but aren’t what’s important right now.

Asking specific questions can completely change the quality of the feedback that you receive. People who have less refined critique abilities will now be able to provide more useful feedback, and even experienced designers will appreciate the clarity and effectiveness gained from concentrating solely on what is required. It can save a lot of time and frustration.

The iteration

Design iterations are probably the most recognizable component of the design process, and they act as a natural feedback loop. Many design tools have inline commenting, but many of them only display changes as a single fluid stream in the same file. In addition, these kinds of design tools automatically update shared UI components, make conversations disappear and require designs to always display the most recent version, unless these would-be useful features were manually disabled. The implied goal that these design tools seem to have is to arrive at just one final copy with all discussions closed, probably because they inherited patterns from how written documents are collaboratively edited. That approach to design critiques is probably not the best approach, but some teams might benefit from it even if I don’t want to be too prescriptive.

The asynchronous design-critique approach that I find most effective is to make explicit checkpoints for discussion. I’m going to use the term iteration post for this. It refers to a write-up or presentation of the design iteration that is followed by some sort of discussion thread. This can be used on any platform that can accommodate this structure. By the way, when I refer to a “write-up or presentation“, I’m including video recordings or other media too: as long as it’s asynchronous, it works.

There are many benefits to using iteration posts:

It establishes a rhythm in the design process, allowing the designer to review the feedback from each iteration and get ready for the following.
• It makes decisions visible for future review, and conversations are likewise always available.
• It keeps track of how the design evolved over time.
• It might also make it simpler to collect and act on feedback depending on the tool.

These posts of course don’t mean that no other feedback approach should be used, just that iteration posts could be the primary rhythm for a remote design team to use. And from there, there can develop additional feedback techniques ( such as live critique, pair designing, or inline comments ).

There isn’t, in my opinion, a universal format for iteration posts. But there are a few high-level elements that make sense to include as a baseline:

1. The objective is.
2. The layout
3. The list of changes
4. The querys

Each project is likely to have a goal, and it should most likely be one that has already been summarized in one sentence elsewhere, such as the client brief, the product manager’s outline, or the request of the project owner. So this is something that I’d repeat in every iteration post—literally copy and pasting it. To avoid having to search through information from multiple posts, the goal is to provide context and repeat what is necessary to complete each iteration post. The most recent iteration post will have everything I need if I want to know about the most recent design.

This copy-and-paste part introduces another relevant concept: alignment comes from repetition. Therefore, repeating information in posts is actually very effective at ensuring that everyone is on the same page.

The actual series of information-architecture outlines, diagrams, flows, maps, wireframes, screens, visuals, and any other design work that has been done is what is then called the design. In short, it’s any design artifact. In the final stages of the project, I prefer to use the term “blank” to indicate that I’ll be displaying complete flows rather than individual screens to make it simpler to comprehend the larger picture.

It might also be helpful to have clear names on the objects since it makes them look better to refer to. Write the post in a way that helps people understand the work. It’s not much different from creating a strong live presentation.

For a successful discussion, you should also include a bullet list of the changes made in the previous iteration to help people concentrate on what’s changed. This can be especially useful for larger pieces of work where keeping track, iteration after iteration, may prove difficult.

And finally, as noted earlier, it’s essential that you include a list of the questions to drive the design critique in the direction you want. Creating a numbered list of questions can also help make it simpler to refer to each one by its number.

Not every iteration is the same. Earlier iterations don’t need to be as tightly focused—they can be more exploratory and experimental, maybe even breaking some of the design-language guidelines to see what’s possible. Then, later, the iterations begin coming to a decision and improving it until the design process is complete and the feature is ready.

Even if these iterations posts are written and intended as checkpoints, they are not required to be exhaustive. A post might be a draft—just a concept to get a conversation going—or it could be a cumulative list of each feature that was added over the course of each iteration until the full picture is done.

I also started using specific labels for incremental iterations over time: i1, i2, i3, and so on. Although this may seem like a minor labeling tip, it can be useful in many ways:

• Unique—It’s a clear unique marker. Everyone knows where to go to review things, and it’s simple to say” This was discussed in i4″ with each project.
• Unassuming—Versions of the same thing ( such as v1, v2, and v3 ) give the impression of something enormous, exhaustive, and complete. Iterations must be able to be exploratory, incomplete, partial.
• Future proof—It resolves the “final” naming issue that versions can encounter. No more files with the title “final final complete no-really-its-done” Within each project, the largest number always represents the latest iteration.

The wording release candidate (RC ) could be used to indicate when a design is finished enough to be worked on, even if there are some areas that still need improvement and, in turn, require more iterations, such as” with i8 we reached RC” or “i12 is an RC” to indicate when it is finished.

The evaluation

What usually happens during a design critique is an open discussion, with a back and forth between people that can be very productive. This strategy is particularly successful when synchronous feedback is being received live. However, when we work asynchronously, using a different approach is more effective: we can adopt a user-research mindset. Written feedback from teammates, stakeholders, or others can be treated as if it were the result of user interviews and surveys, and we can analyze it accordingly.

This shift has some significant advantages, making asynchronous feedback particularly effective, especially around these friction points:

It makes it easier to respond to everyone.
1. It reduces the frustration from swoop-by comments.
2. It lessens our personal stakes.

The first friction point is having to press yourself to respond to each and every comment. Sometimes we write the iteration post, and we get replies from our team. It’s just a few of them, it’s simple, and there isn’t much of a problem with it. However, there may be times when some solutions may require more in-depth discussions and the number of replies may quickly rise, which can create tension between trying to be a good team player by responding to everyone and attempting the next design iteration. This might be especially true if the person who’s replying is a stakeholder or someone directly involved in the project who we feel that we need to listen to. We must come to terms with the fact that this pressure is perfectly normal and that it’s human nature to try to accommodate those we care about. When we treat a design critique more like user research, we realize that we don’t need to respond to every comment, and there are alternatives: In asynchronous spaces, responding to all comments can be effective.

One is to let the next iteration speak for itself. The response is received when the design changes and a follow-up iteration is made. You could tag everyone in the previous discussion, but that’s just a choice, not a requirement.
• Another is to briefly reply to acknowledge each comment, such as” Understood. Thank you,”” Good points— I’ll review,” or” Thanks. These will be included in the upcoming iteration. In some cases, this could also be just a single top-level comment along the lines of” Thanks for all the feedback everyone—the next iteration is coming soon”!
• Another option is to provide a quick summary of the comments before moving on. This may be particularly helpful if your workflow allows you to create a simplified checklist that you can use for the following iteration.

The second friction point is the swoop-by comment, which is the kind of feedback that comes from someone outside the project or team who might not be aware of the context, restrictions, decisions, or requirements —or of the previous iterations ‘ discussions. One can hope that they will learn something from them, starting with acknowledging that they are doing this and making their location more explicit. Swoop-by comments frequently prompt the simple thought,” We’ve already discussed this,” and it can be frustrating to have to keep saying the same thing over and over.

Let’s begin by acknowledging again that there’s no need to reply to every comment. However, a brief response with a link to the previous discussion for additional information is typically sufficient if responding to a previously litigated point might be helpful. Remember that repetition results in alignment; therefore, it’s acceptable to occasionally repeat things!

Swoop-by commenting can still be useful for two reasons: they might point out something that still isn’t clear, and they also have the potential to stand in for the point of view of a user who’s seeing the design for the first time. Yes, you’ll still be frustrated, but that might at least make things better for you.

The personal stake we might have in the design could be the third friction point, which might cause us to feel defensive if the review turned into a discussion. Treating feedback as user research helps us create a healthy distance between the people giving us feedback and our ego ( because yes, even if we don’t want to admit it, it’s there ). In the end, presenting everything in aggregated form helps us to prioritize our work more.

You don’t have to accept every piece of feedback, but you do need to listen to stakeholders, project owners, and specific advice. You have to analyze it and make a decision that you can justify, but sometimes “no” is the right answer.

You are in charge of making that choice as the designer leading the project. In the end, everyone has their area of expertise, and as a designer, you are the one with the most background and knowledge to make the right choice. And by listening to the feedback that you’ve received, you’re making sure that it’s also the best and most balanced decision.

Thanks to Mike Shelton and Brie Anne Demkiw for their initial review of this article.

We’ve been conversing for a long time. 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 English also has the advantage of face-to-face contact, which enables 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.

Spoken language lacks this luxury. There are verbal cues and vocal behaviors that modulate conversation in nuanced ways, including how something is said, not what. These are the nonverbal cues that decorate conversations with emphasis and emotional context. Whether rapid-fire, low-pitched, or high-decibel, whether sarcastic, stilted, or sighing, our spoken language conveys much more than the written word could ever muster. As designers and content strategists, we face exciting challenges when it comes to voice interfaces, the machines we use to communicate over the phone.

Voice-to-voice interactions

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 conversation as a result:

• we require something to be done ( such as a transaction ),
• we want to know something ( information of some sort ), or
• We are social creatures and seek out a conversation partner ( for the purpose of conversation ).

These three categories, which I refer to as transactional, informational, and prosocial, also apply to essentially every voice interaction: a single conversation that starts with the voice interface’s first greeting and ends with the user leaving the interface. Note here that a conversation in our human sense—a chat between people that leads to some result and lasts an arbitrary length of time—could encompass multiple transactional, informational, and prosocial voice interactions in succession. In other words, a voice interaction is a conversation, but it must not be one particular voice interaction.

Most voice interfaces are more gimmicky than captivating in pure prosocial conversations because most people find it difficult to trust their machines to actually understand how we’re doing and to give them the kind of glad-handing we 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 Voice User Interface Design, Michael Cohen, James Giangola, and Jennifer Balogh advise sticking to user expectations by imitating how they interact with other voice interfaces, which might lead to alienating them ( ).

That leaves two different types of conversations we can have with one another that a voice interface can also have easily, such as one that focuses on a transactional voice interaction ( buying iced tea ) and another on 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 an initial smattering of neighborly small talk to the actual task at hand, which is ordering a pizza ( generously topped with pineapple, as it should be ).

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 get a pizza from Hawaii with extra pineapple.

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 know it. That’ll be$ 13.55 and about fifteen minutes.

A service rendered or a product delivered is the desired outcome of the transaction, and each progressive disclosure in this transactional conversation reveals more and more of it. Conversations that are transactional have certain characteristics: they are direct, concise, and cost-effective. 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. We’re after much more than just a prosocial mini-conversation at the beginning, even though we do it once more to establish politeness.

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. Are you considering any additional dietary restrictions?

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 for you to answer?

Alison: That’s it for the moment. Good to know. Thank you.

Burhan: Anytime, please.

This is a very different dialogue. Here, the goal is to obtain a particular set of facts. Informational conversations are research expeditions that seek the truth through information gathering. Voice interactions that are informational might be more long-winded than transactional conversations by necessity. Responses are typically longer, more in-depth, and carefully communicated so that the customer is aware of the important lessons.

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 by voice. We’re most concerned in this book with pure voice interfaces because multimodal voice interfaces can lean on visual components like screens as crutches, which are completely dependent on spoken conversation and lack any visual component, making them much more nuanced and challenging to deal with.

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 used for computing for many years, but voice interfaces first started to appear in the early 1990s with text-to-speech ( TSS) 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. Similar to the corporate world, these systems were primarily created as metaphorical switchboards to direct customers to a real phone agent (” Say Reservations to book a flight or check an itinerary” ), and chances are you’ll have a conversation with one when you call an airline or hotel conglomerate. Despite their functional issues and users ‘ frustration with their inability to speak to an actual human right away, IVR systems proliferated in the early 1990s across a variety of industries (, PDF).

IVR systems have a reputation for having less scintillating conversations than we’re used to in real life ( or even in science fiction ), despite being extremely repetitive and monotonous conversations that typically don’t veer from a single format.

Readers of screens

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

Among the first screen readers known by that moniker was the Screen Reader for the BBC Micro and NEEC Portable developed by the Research Centre for the Education of the Visually Handicapped (RCEVH) at the University of Birmingham in 1986 ( ). 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 ) ( ).

With the rapid expansion of the web in the 1990s, there was an explosion in the demand for user-friendly tools. 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. in A List Apart, writes Aaron Gustafson, “into useful information.” ” 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. Screen readers may not be able to read websites ‘ visual structures, which can occasionally lead to awkward pronouncements that list every manipulable HTML element and make an announcement about every formatting change. 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 not appropriate 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. ( ) _ _ _

Well-designed voice interfaces can often be more effective than long-winded screen reader monologues in guiding users to their destination. 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” ( hinter paywall ). Apple’s Siri finally made voice assistants a reality for consumers until 2011 when they were available.

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, when they were released, core functionality for Apple’s Siri and Microsoft’s Cortana couldn’t be expanded beyond their already-existing capabilities. There are no other means by which developers can interact with Siri at a low level, aside from predefined categories of tasks like sending messages, hailing rideshares, making restaurant reservations, and other things, which are still unavoidable 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 dominate their markets, they are also selling and open-sourcing an unmatched range of tools and frameworks for designers and developers, aiming to make creating voice interfaces as simple as possible, even without the use of any 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, like Google’s Dialogflow, now support omnichannel features, allowing 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 voice-transmitted content. Voice content must be free-flowing, organic, contextless, and concise in order to preserve what makes human conversation so compelling in the first place.

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 first foray into informational voice interfaces will likely be to deliver content to users, for many of us. There’s only one problem: any content we already have isn’t in any way ready for this new habitat. 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, colossal vaults of what I call macrocontent: lengthy prose that can last for miles in a browser window, 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 must ensure that our microcontent performs well as voice content because it is essentially composed of individual 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.

Fundamentally, how voice content manifests in perceived time and space both affect the legibility and discoverability of our voice content.

Although I’m not certain when I first heard this statement, it has over the centuries stuck in my mind. How do you generate solutions for scenarios you can’t think? Or create materials that are functional on products that have not yet been created?

Flash, Photoshop, and flexible pattern

My go-to program when I first started designing sites was Photoshop. I created a 960px paint and set about creating a design that I would eventually lose information in. The growth phase aimed to achieve pixel-perfect accuracy by using set widths, fixed heights, and absolute placement.

Ethan Marcotte’s speak at An Event Off and subsequent content” Responsive Web Design” in A List Off in 2010 changed all this. I immediately became enthralled when I learned about flexible design. The pixel-perfect models full of special figures that I had formerly prided myself on producing were no longer good enough.

My first encounter with flexible design didn’t help my fear. My second project was to get an active fixed-width website and make it reactive. I quickly realized that you didn’t just put responsiveness at the end of a task. To make smooth design, you need to prepare throughout the style phase.

a novel architecture process

Developing flexible or liquid sites has always been about removing limitations, producing material that can be viewed on any system. It relies on using percentage-based layouts, which I immediately achieved using native CSS and power courses:

.column-span-6 { width: 49%; float: left; margin-right: 0.5%; margin-left: 0.5%;}.column-span-4 { width: 32%; float: left; margin-right: 0.5%; margin-left: 0.5%;}.column-span-3 { width: 24%; float: left; margin-right: 0.5%; margin-left: 0.5%;}

Then with Sass so I could take advantage of @includes to re-use repeated slabs of script and walk up to more semantic html:

.logo { @include colSpan(6);}.search { @include colSpan(3);}.social-share { @include colSpan(3);}

Media inquiries

The next ingredient for flexible design is press queries. Without them, regardless of whether the information was still readable, may reduce to fit the available space.

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

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

String premium was a mainstay of early flexible design, present in all the frequently used systems like Bootstrap and Skeleton.

 
1 of 7
 
2 of 7
 
3 of 7
 
4 of 7
 
5 of 7
 
6 of 7
 
7 of 7

Another difficulty arose as I moved from a design firm building websites for tiny- to medium-sized companies, to larger in-house teams where I worked across a collection of related sites. In those capacities, I began to work more with washable parts.

Our rely on multimedia queries resulted in parts that were tied to frequent window sizes. If part libraries are intended to be reused, this is a real problem because you can just use these components if the devices you’re designing for match the style library’s screen sizes, which prevents you from actually achieving the “devices that don’t yet exist” purpose.

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

Container queries: a false dawn or our savior?

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

One of the biggest arguments in favor of container queries is that they help us create components or design patterns that are truly reusable because they can be picked up and placed anywhere in a layout. This is a significant step in the direction of a component-based design that can be used with any device, regardless of size.

In other words, responsive components to replace responsive layouts.

Container queries will enable us to design components that can be inserted in a sidebar or the main content and respond accordingly rather than designing pages that respond to the browser or device size.

My concern is that we are still using layout to determine when a design needs to adapt. We will still require predetermined breakpoints, so this approach will always be restrictive. For this reason, my main question with container queries is, How would we decide when to change the CSS used by a component?

A component library that is disconnected from context and real content is probably not the best place to make that choice.

As the diagrams below illustrate, we can use container queries to create designs for specific container widths, but what if I want to change the design based on the image size or ratio?

The container’s dimensions shouldn’t be what should be the design in this example; rather, the image should be.

It’s hard to say for sure whether container queries will be a success story until we have solid cross-browser support for them. Responsive component libraries would undoubtedly change the way we design, enhancing reuse possibilities and scaling. But maybe we will always need to adjust these components to suit our content.

CSS is evolving.

Whilst the container query debate rumbles on, there have been numerous advances in CSS that change the way we think about design. The days of fixed-width elements measured in pixels and floated div elements used to cobble layouts together are long gone, consigned to history along with table layouts. Flexbox and CSS Grid have revolutionized layouts for the web. We can now create elements that wrap onto new rows when they run out of space, not when the device changes.

.wrapper { display: grid; grid-template-columns: repeat(auto-fit, 450px); gap: 10px;}

The repeat() function paired with auto-fit or auto-fill allows us to specify how much space each column should use while leaving it up to the browser to decide when to spill the columns onto a new line. Similar things can be achieved with Flexbox, as elements can wrap over multiple rows and “flex” to fill available space. 

.wrapper { display: flex; flex-wrap: wrap; justify-content: space-between;}.child { flex-basis: 32%; margin-bottom: 20px;}

The biggest benefit of all this is you don’t need to wrap elements in container rows. Without rows, content is not directly related to page markup, allowing for changes or additions to content without further development.

This is a significant improvement when it comes to developing designs that allow for dynamic content, but CSS Subgrid is the real game changer for flexible designs.

Remember the days of crafting perfectly aligned interfaces, only for the customer to add an unbelievably long header almost as soon as they’re given CMS access, like the illustration below?

Subgrid allows elements to respond to adjustments in their own content and in the content of sibling elements, helping us create designs more resilient to change.

.wrapper { display: grid; grid-template-columns: repeat(auto-fit, minmax(150px, 1fr)); grid-template-rows: auto 1fr auto; gap: 10px;}.sub-grid { display: grid; grid-row: span 3; grid-template-rows: subgrid; /* sets rows to parent grid */}

CSS Grid allows us to separate layout and content, thereby enabling flexible designs. Subgrid also enables us to create designs that can be modified to fit changing content. Subgrid at the time of writing is only supported in Firefox but the above code can be implemented behind an @supports feature query.

Intrinsic layouts

I’d be remiss not to mention intrinsic layouts, the term created by Jen Simmons to describe a mixture of new and old CSS features used to create layouts that respond to available space.

Columns with percentages are flexible in responsive layouts. Intrinsic layouts, on the other hand, use the fr unit to create flexible columns that won’t ever shrink so much that they render the content illegible.

frunits is a statement that says I want you to distribute the extra space in this manner, but never that it should be smaller than the content inside.

—Jen Simmons,” Designing Intrinsic Layouts”

Additionally, intrinsic layouts can mix and match both fixed and flexible units, letting the content choose how much space is taken up.

Intriguing design distinguishes itself because it not only creates designs that can withstand future devices but also helps scale designs without losing flexibility. Components and patterns can be lifted and reused without the prerequisite of having the same breakpoints or the same amount of content as in the previous implementation.

We can now make designs that work in harmony with the content inside and the content around them. With an intrinsic approach, we can construct responsive components without depending on container queries.

Another 2010 moment?

This intrinsic approach should in my view be every bit as groundbreaking as responsive web design was ten years ago. It’s another “everything changed” moment for me.

But it doesn’t seem to be moving quite as fast, I haven’t yet had that same career-changing moment I had with responsive design, despite the widely shared and brilliant talk that brought it to my attention.

One possible explanation for that might be that I now work for a sizable company, which is significantly different from the role I held as a design agency in 2010: In my agency days, every new project was a clean slate, a chance to try something new. Modern projects frequently improve existing websites using an existing codebase and use existing tools and frameworks.

Another could be that I feel more prepared for change now. I was relatively new to design in 2010; the shift was frightening and involved a lot of learning. Also, an intrinsic approach isn’t exactly all-new, it’s about using existing skills and existing CSS knowledge in a different way.

You can’t framework your way out of a content issue.

Another reason for the slightly slower adoption of intrinsic design could be the lack of quick-fix framework solutions available to kick-start the change.

Ten years ago, responsive grid systems were everywhere. With a framework like Bootstrap or Skeleton, you had a responsive design template at your fingertips.

Because having a selection of units is a hindrance when creating layout templates, intrinsic design and frameworks do not work together quite as well. The beauty of intrinsic design is combining different units and experimenting with techniques to get the best for your content.

There are also design tools. We probably all, at some point in our careers, used Photoshop templates for desktop, tablet, and mobile devices to drop designs in and show how the site would look at all three stages.

How do you do that right away, with each component reacting to content and layout flexing as needed? This type of design must happen in the browser, which personally I’m a big fan of.

Another topic that has persisted for years is the debate over whether designers should code. When designing a digital product, we should, at the very least, design for a best- and worst-case scenario when it comes to content. It’s not ideal to do this in a graphics-based software package. In code, we can add longer sentences, more radio buttons, and extra tabs, and watch in real time as the design adapts. Does it continue to function? Is the design too reliant on the current content?

I’m personally anticipating the day when a design component can truly be flexible and adapt to both its space and content without relying on the device or container dimensions. This is the day.

Content first

Content is not a fixed thing. After all, to design for the unknown or unexpected we need to account for content changes like our earlier Subgrid card example that allowed the cards to respond to adjustments to their own content and the content of sibling elements.

Thankfully, there’s more to CSS than layout, and plenty of properties and values can help us put content first. Subgrid and pseudo-elements like ::first-line and ::first-letter help to separate design from markup so we can create designs that allow for changes.

Instead of the dated markup tricks below,

 First line of text with different styling...

—we can target content based on where it appears.

.element::first-line { font-size: 1.4em;}.element::first-letter { color: red;}

Much bigger additions to CSS include logical properties, which change the way we construct designs using logical dimensions (start and end) instead of physical ones (left and right), something CSS Grid also does with functions like min(), max(), and clamp().

This flexibility allows for directional changes according to content, a common requirement when we need to present content in multiple languages. This was frequently accomplished with Sass mixins in the past, but it was frequently limited to a switch from a left-to-right to a right-to-left orientation.

In the Sass version, directional variables need to be set.

$direction: rtl;$opposite-direction: ltr;$start-direction: right;$end-direction: left;

These variables can also be used as values—

body { direction: $direction; text-align: $start-direction;}

—or as properties.

margin-#{$end-direction}: 10px;padding-#{$start-direction}: 10px;

However, with native logical properties, there is no longer a need to rely on Sass ( or another similar tool ) or pre-planning, which made using variables throughout a codebase necessary. These properties also start to break apart the tight coupling between a design and strict physical dimensions, creating more flexibility for changes in language and in direction.

margin-block-end: 10px;padding-block-start: 10px;

There are also native start and end values for properties like text-align, which means we can replace text-align: right with text-align: start.

Like the earlier examples, these properties help to build out designs that aren’t constrained to one language, the design will reflect the content’s needs.

Fluid and fixed

We briefly covered the power of combining fixed widths with fluid widths with intrinsic layouts. The min() and max() functions are a similar concept, allowing you to specify a fixed value with a flexible alternative. 

For min() this means setting a fluid minimum value and a maximum fixed value.

.element { width: min(50%, 300px);}

As long as the element’s width doesn’t exceed 300px, the element in the figure above will be 50 % of its container.

For max() we can set a flexible max value and a minimum fixed value.

.element { width: max(50%, 300px);}

As long as the element’s width is at least 300px, it will now cover 50 % of its container. This means we can set limits but allow content to react to the available space.

The clamp() function builds on this by allowing us to set a preferred value with a third parameter. Now we can allow the element to shrink or grow if it needs to without getting to a point where it becomes unusable.

.element { width: clamp(300px, 50%, 600px);}

This time, the element’s width will be 50 % of its container’s preferred value, with no exceptions for 300px and 600px.

With these techniques, we have a content-first approach to responsive design. We can’t change markup because content can’t be changed, so user modifications won’t have an impact on the design. We can start to future-proof designs by planning for unexpected changes in language or direction. Additionally, we can increase flexibility by specifying desired dimensions alongside adaptable alternatives, which will allow for the display of more or less content correctly.

Situation first

We can cover device flexibility by changing our approach, designing around content and space rather than catering to devices, thanks to what we’ve discussed so far. But what about that last bit of Jeffrey Zeldman’s quote,”… situations you haven’t imagined”?

It’s a lot different to design for someone using a mobile phone and walking through a crowded street in glaring sunshine than it is for someone using a desktop computer. Situations and environments are hard to plan for or predict because they change as people react to their own unique challenges and tasks.

This is why making a choice is so crucial. One size never fits all, so we need to design for multiple scenarios to create equal experiences for all our users.

Thankfully, there is a lot we can do to give people choices.

Responsible design

” Mobile data is prohibitively expensive in some places around the world, and broadband infrastructure is sparse or absent.”

” I Used the Web for a Day on a 50 MB Budget“

Chris Ashton

One of the biggest assumptions we make is that people interacting with our designs have a good wifi connection and a wide screen monitor. However, our users may be commuters using smaller mobile devices that may experience disconnects in connectivity in the real world. There is nothing more frustrating than a web page that won’t load, but there are ways we can help users use less data or deal with sporadic connectivity.

The srcset attribute allows the browser to decide which image to serve. This means we can create smaller ‘cropped’ images to display on mobile devices in turn using less bandwidth and less data.

The preload attribute can also help us to think about how and when media is downloaded. It can be used to tell a browser about any critical assets that need to be downloaded with high priority, improving perceived performance and the user experience. 

Additionally, there is native lazy loading, which indicates that only the most crucial files should be downloaded.

With srcset, preload, and lazy loading, we can start to tailor a user’s experience based on the situation they find themselves in. What none of this does, however, is allow the user themselves to decide what they want downloaded, as the decision is usually the browser’s to make. 

So how can we put users in control?

The media queries are returning.

Media inquiries have always been about much more than device sizes. They allow content to adapt to different situations, with screen size being just one of them.

We’ve long been able to check for media types like print and speech and features such as hover, resolution, and color. Because of these checks, we can offer options that work for multiple situations, not just one-size-fits-all.

As of this writing, the Media Queries Level 5 spec is still under development. It introduces some really intriguing queries that will enable us to design for a number of other unanticipated situations in the future.

For example, there’s a light-level feature that allows you to modify styles if a user is in sunlight or darkness. These features, which are enhanced by custom properties, make it simple to create designs or themes for particular environments.

@media (light-level: normal) { --background-color: #fff; --text-color: #0b0c0c; }@media (light-level: dim) { --background-color: #efd226; --text-color: #0b0c0c;}

Another key feature of the Level 5 spec is personalization. Instead of creating designs that are the same for everyone, users can choose what works for them. This is achieved by using features like prefers-reduced-data, prefers-color-scheme, and prefers-reduced-motion, the latter two of which already enjoy broad browser support. These features tap into preferences set via the operating system or browser so people don’t have to spend time making each site they visit more usable. 

Media inquiries like this go beyond choices made by a browser to grant more control to the user.

Expect the unanticipated

In the end, the one thing we should always expect is for things to change. With foldable screens already available, especially in the form of tablets, we can’t keep up with them.

We can’t design the same way we have for this ever-changing landscape, but we can design for content. We can create more robust, flexible designs that increase the longevity of our products by putting the customer first and allowing that customer to adapt to whatever environment surrounds them.

A lot of the CSS discussed here is about moving away from layouts and putting content at the heart of design. There is so much more we can do to adopt a more intrinsic approach, from responsive components to fixed and fluid units. Even better, we can test these techniques during the design phase by designing in-browser and watching how our designs adapt in real-time.

When it comes to unexpected circumstances, we need to make sure our goods are accessible whenever and wherever needed. We can move closer to achieving this by involving users in our design decisions, by creating choice via browsers, and by giving control to our users with user-preference-based media queries.

A good design for the unexpected should allow for change, give choice, and give control to the people we serve: our users themselves.