Category: Blog

Your blog category

  • Opportunities for AI in Accessibility

    Opportunities for AI in Accessibility

    I was completely moved by Joe Dolson’s current article on the crossroads of AI and availability because I found it to be both skeptical about how widespread use of AI is. Despite my role at Microsoft as an affordability technology tactician who helps manage the AI for Accessibility grant program, I’m very skeptical of AI myself. As with any tool, AI can be used in quite productive, equitable, and visible ways, and it can also be used in dangerous, unique, and dangerous ones. Additionally, there are a lot of uses in the subpar midsection as well.

    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 words

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

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

    If we can specifically station a design to examine image usage in context, it might help us more quickly determine which images are likely to be elegant and which ones are likely to need a description. That will help clarify which situations require image descriptions, and it will increase authors ‘ effectiveness in making their 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 would frequently leave many unanswered questions about the data, but let’s just assume that 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 telephones or smartphones?
    • How many more?
    • Do you know of any persons who don’t fall under either of these categories?
    • How many is that?

    Setting aside the realities of large language model ( LLM) hallucinations—where a model just makes up plausible-sounding “facts” —for a moment, the opportunity to learn more about images and data in this way could be revolutionary for blind and low-vision folks as well as for people with various forms of color blindness, cognitive disabilities, and so on. It might also be helpful in educational settings to assist those who can, because is, comprehend the data contained in these charts.

    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 graph? What if you could request your computer to transform the colors of the various lines so that it works better for your type of color blindness? What if you could request it to switch shades for 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 put her book Algorithms of Oppression, she hit the nail on the head. Although her book focused on the ways that search engines can foster racism, I believe it to be equally accurate to say that all computer models have the potential to amplify conflict, bias, and intolerance. We all know that poorly written and maintained algorithms are incredibly harmful, whether it’s Twitter constantly showing you the most recent tweet from a drowsy billionaire, YouTube sending us into a q-hole, or Instagram warping our ideas of what natural bodies look like. A large portion of this is attributable to the lack of diversity in those who create and shape them. When these platforms are built with inclusively baked in, however, there’s real potential for algorithm development to help people with disabilities.

    Take Mentra, for example. They serve as a network of people with disabilities. Based on more than 75 data points, they match job seekers with potential employers using an algorithm. On the job-seeker side of things, it considers each candidate’s strengths, their necessary and preferred workplace accommodations, environmental sensitivities, and so on. On the employer side, it considers each work environment, communication factors related to each job, and the like. Mentra made the decision to change the script when it came to typical employment websites because it was run by neurodivergent people. They lessen the emotional and physical labor needed for job seekers by using their algorithm to suggest available candidates to businesses who can then connect with job seekers they are interested in.

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

    Imagine if the social media company’s recommendation engine was tuned to prioritize follow recommendations for people who discussed topics similar to those that were important but who were not in your current sphere of influence in any significant way. For instance, if you followed a group of nondisabled white male academics who spoke about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also speak about AI. If you took its recommendations, perhaps you’d get a more holistic and nuanced understanding of what’s happening in the AI field. These same systems should also use their understanding of biases about particular communities—including, for instance, the disability community—to make sure that they aren’t recommending any of their users follow accounts that perpetuate biases against (or, worse, spewing hate toward ) those groups.

    Other ways that AI can helps people with disabilities

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

      Voice preservation. You may have seen the VALL-E paper or Apple’s Global Accessibility Awareness Day announcement or you may be familiar with the voice-preservation offerings from Microsoft, Acapela, or others. 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 ) or 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. LLMs of the current generation are quite capable of changing text without creating 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

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

    Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that 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 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 recomprehensible recommendations 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 creative.

    I am a creative.

    I am a artistic. What I do is alchemy. It is a puzzle. I prefer to let it be done through me rather than through me.

    I am a artistic. Not all aspiring artists approve of this brand. Not all people see themselves in this manner. Some innovative persons 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 progress is a diversion. That’s what my head does 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 is simple and flows like a beverage valley.

    Sometimes it does. Maybe what I need to make arrives 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 work until the thought strikes me. It occasionally arrives right away, but I don’t remind people for three weeks. Sometimes I blurt out the plan so quickly that I didn’t stop myself. like a child who discovered a reward in a box of Cracker Jacks. Often I get away with this. Maybe other people agree: yes, that is the best idea. Most days they don’t and I regret having given way to joy.

    Joy should be saved for the meeting, where it will matter. Certainly the informal get-together that comes before that meeting with two more meetings. Anyone knows why we have all these discussions. We keep saying we’re going to get rid of them, but we end up really trying to. They occasionally yet excel. But occasionally they detract from the real 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 design.

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

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

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

    I can nail apart, surround myself with information or photos, and maybe that works. I can go for a walk, and maybe that works. There is a Eureka, which has nothing to do with boiling pots and sizzling petrol, 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 part of the world once more in a mindless breeze 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. Theologians should circulate mass armies throughout their artistic globe, which they claim to be true. But that is another diversion. And it’s miserable. Possibly on a much bigger issue than whether or not I am creative. But that’s also a step backwards from what I’m trying to say.

    Often the process is mitigation. 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 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 understand artists.

    Disadvantages are aware of cons, just like queers are aware of queers, just like real rappers are aware of genuine rappers. Creatives feel enormous regard for creatives. We love, respect, emulate, and nearly deify the excellent ones. To revere any man is, of course, a horrible mistake. We have been warned. We know much. We know people are really people. They dispute, they are depressed, they regret their most critical decisions, they are weak and thirsty, they can be cruel, they can be just as terrible as we can, if, like us, they are clay. But. But. However, they produce something incredible. They give birth to something that may not occur without them and did not exist before them. They are the inspirations of thought. And I suppose, since it’s only lying it, I have to put that they are the mother of technology. Ba ho bum! 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 glory. That is brilliance straight out of the Bible. This half-starved small item that I made? It essentially fell off the pumpkin vehicle. And the carrots weren’t even new.

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

    I am a artistic. I haven’t worked in advertising in 30 years, but in my hallucinations, it’s my previous artistic managers who judge me. 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 artistic function.

    I am a artistic. Every project I create has a goal that makes Indiana Jones appear older and snoring in a deck head. The more I pursue my creative endeavors, the faster I progress in my work, and the more I slog through lines 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. Only that I spend twice as long putting the job 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 rush of delay. I’m still so scared of jumping.

    I am not an actor.

    I am a artistic. No an actor. Though I dreamed, as a child, 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 successes.

    I am a artistic. 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 innovative. I lament my lack of taste in almost all of the areas of human understanding that I know very little about. 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’d probably have to spend the majority of our time looking ourselves in the eye, which is something that almost none of us can do for very much. No seriously. No actually. Because many in existence, if you really look at it, is intolerable.

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

    Working frees me from worrying about my job.

    I am a artistic. I worry that my little product will disappear unexpectedly.

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

    I am a innovative. I think that method is the greatest mystery. I think I have to consider it so strongly that I actually made the foolish decision to publish an essay I wrote without having to go through or edit. I didn’t do this generally, I promise. But I did it right away because I was even more scared of forgetting what I was saying because I was as worried as I might be of you seeing through my sad gestures toward the gorgeous.

    There. I think I’ve said it.

  • Humility: An Essential Value

    Humility: An Essential Value

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

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

    The Tale of Justin’s Preposterous Pate

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

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

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

    Those are classic factors between non-career relationships and the world of design, even though I’m talking about a different time. What are your main passions, or ideals, that elevate medium? The main elements are all the same, basically the same as what we previously discussed earlier on the immediate parallels between what fulfills you, independent of the visible or online domains.

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

    For example, this iteration of my personal portfolio site (” the pseudoroom” ) from that era was experimental, if not a bit heavy- handed, in the visual communication of the concept of a living sketchbook. Very skeuomorphic. On this one, I worked with fellow designer and dear friend Marc Clancy, who is now a co-founder of the creative project organizing app Milanote, to sketch and then play with various user interactions. Then, I’d break it down and code it into a digital layout.

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

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

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

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

    The site’s backbone was a homegrown CMS, with the presentation layer consisting of global design + illustration + news author collaboration. And the collaboration effort here, in addition to experimentation on a’ brand’ and content delivery, was hitting my core. We were creating a larger-than-anyone experience and establishing a global audience.

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

    Why am I taking you on this journey of design memory lane, now? Two reasons.

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

    Today’s web design has been in a period of stagnation. There’s a good chance of seeing a website with a hero image or banner with text overlaying, perhaps with a lovely rotating carousel of images ( laying the snark on heavy there ), a call to action, and three columns of sub-content directly beneath. Perhaps an icon library is used with selections that only vaguely relate to their respective content is used.

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

    Pixel Problems

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

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

    These were 32 x 32 pixel creations, utilizing a 256-color palette, designed pixel-by-pixel as mini mosaics. This seemed to me to be the embodiment of digital visual communication under such absurd restrictions. And frequently, ridiculous restrictions lead to concept and theme purification.

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

    Expanding upon the notion of exploration, I wanted to see how I could push the limits of a 32×32 pixel grid with that 256-color palette. These absurd restrictions imposed a clarity of concept and presentation that I found incredibly appealing. The challenge of throwing the digital gauntlet had been thrown at me. And so, in my dorm room into the wee hours of the morning, I toiled away, bringing conceptual sketches into mini mosaic fruition.

    These are some of my creations that made use of ResEdit, the only program I had at the time, to create icons. ResEdit was a clumsy, built-in Mac OS utility that wasn’t really designed for what we were using it for. At the core of all of this work: Research. Challenge. Problem- solving. Again, these core connection-based values are agnostic of medium.

    One more design portal that serves as the second component of my story’s fusion also serves as a great source of information.

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

    For my part, the combination of my pixel art and web design work started to gain me some notoriety in the design community. K10k eventually figured out and added me as one of their very limited group of news writers to add content to the website.

    Amongst my personal work and side projects —and now with this inclusion—in the design community, this put me on the map. Additionally, my design work has started to appear on other design news portals, as well as in publications abroad and domestically. With that degree of success while in my early twenties, something else happened:

    I evolved—devolved, really—into a colossal asshole ( and in just about a year out of art school, no less ). What satisfied me was the praise and the press, which went on to completely alter my mind. They inflated my ego. I actually felt a little better than my fellow designers.

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

    I effectively stopped researching and discovering because I was so confident in my abilities. When my first instinct was to sketch concepts or iterate ideas in lead, I instead leaped right into Photoshop. I drew my inspiration from the tiniest of sources ( and with no discernible bias ). Any criticism of my work from my fellow students was frequently vehemently dissented. The most tragic loss: I had lost touch with my values.

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

    It was a gift I initially did not accept but which I, on the whole, was able to reflect on in depth. I was soon able to accept, and process, and course correct. The realization laid me low, but the re-awakening was essential. I let go of the “reward” of admiration and turned my attention to the issues that had sparked my passion for art school. Most importantly: I got back to my core values.

    Always Students

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

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

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

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

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

    I also had my first ethnographic observational experience, which involved visiting the Fermilab location and observing how the physicists used the tool in their own environments, on their own terminals. One takeaway was that the data columns ended up using white text on a dark gray background rather than black text-on-white because of the facility’s level of ambient light-driven contrast. This made it easier for them to pore over a lot of data during the day and lessen their strain on their eyes. Additionally, since Fermilab and CERN are government entities with strict accessibility standards, my knowledge in that field increased. The barrier-free design was another essential form of connection.

    So to those core drivers of my visual problem-solving soul and ultimate fulfillment: discovery, exposure to new media, observation, human connection, and evolution. Before I entered those values, I checked my ego before entering the door.

    An evergreen willingness to listen, learn, understand, grow, evolve, and connect yields our best work. In particular, I want to focus on the words’ grow’ and ‘ evolve’ in that statement. If we are constantly improving our craft, we are also continuously making ourselves available for improvement. Yes, we have years of practical design experience behind us. Or the focused lab training from a bootcamp for UX. Or the monogrammed portfolio of our work. Or, ultimately, decades of a career behind us.

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

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

  • Personalization Pyramid: A Framework for Designing with User Data

    Personalization Pyramid: A Framework for Designing with User Data

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

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

    Getting Started

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

    Popular circumstances for launching a personalization project:

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

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

    From top to bottom, the amounts include:

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

    We’ll go through each of these amounts sequentially. To make this more bearable, we created a deck of cards that accompany it to show particular examples from each stage. We’ve included example for you here because we think they’re useful for customisation brainstorming sessions.

    Beginning at the Top

    The tower has the following elements:

    North Star

    Ultimately, you want a North Star in your personalization program, whether big or small. The North Star identifies the (one ) overall goal of the personalization program. What do you wish to achieve? North Stars cast a ghost. The bigger the sun, the bigger the darkness. Example of North Starts may contain:

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

    Goals

    As in any great UX layout, personalization may help promote designing with client intentions. The goals are the military and tangible indicators that will support the success of the entire program. Start with your existing analytics and assessment system, as well as metrics that you can benchmark against. In some cases, fresh targets may be ideal. The most important thing to keep in mind is that personalisation is not a desired outcome. Popular targets include:

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

    Touchpoints

    Personalization takes place at connections. As a UX artist, this will be one of your largest areas of responsibility. The touchpoints you have will depend on how your personalization and the related technologies are configured, and they should be based on enhancing a person’s encounter at a specific point in the journey. Touchpoints can be multi-device ( mobile, in-store, website ) but also more granular ( web banner, web pop-up etc. ). Here are some examples:

    Channel-level Touchpoints

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

    Wireframe-level Touchpoints

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

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

    Contexts and Campaigns

    After you’ve outlined some touchpoints, you may consider the actual personal information a user may acquire. Many personalization tools will refer to these as” campaigns” ( so, for example, a campaign on a web banner for new visitors to the website ). These will be displayed automatically to specific customer segments at specific touchpoints, as defined by user data. At this stage, we find it helpful to contemplate two distinct concepts: a framework design and a willing design. The environment helps you consider the level of user engagement at the customisation moment, for instance, if they are just lightly browsing information rather than engaging in a deep dive. Think of it in conditions of activities for data recovery. The content model can then guide you in deciding which personalization to use in terms of the context ( for instance, an” Enrich” campaign that features related articles might be a good substitute for extant content ).

    Personalization Context Model:

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

    Personalization Content Model:

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

    We’ve written a lot more in depth about each of these concepts somewhere, so be sure to check out Colin’s Personalization Content Model and Jeff’s Personalization Context Model.

    User Parts

    Based on customer research, user segments can be created prescriptively or dynamically ( for example, using principles and logic tied to user behavior, or through A/B testing ). You will need to think about how to treat the logged-in visitor, the guest or returning visitor for whom you may have a stateful cookie ( or another post-cookie identifier ), or the authenticated visitor who is logged in at the very least. Here are a few illustrations from the personalisation pyramids:

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

    Actionable Data

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

    First-party data represents multiple advantages on the UX front, including being relatively simple to collect, more likely to be accurate, and less susceptible to the” creep factor” of third-party data. Therefore, determining which method of data collection is best for your audiences should be a crucial component of your UX strategy. Here are some examples:

    When it comes to recognizing and making decisions about various audiences and their signals, there is a trend of profiling. As time and confidence and data volume increase, it varies to more granular constructs about smaller and smaller cohorts of users.

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

    Pulling it Together

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

    One can begin to chart the entire course of a card’s “hand” from leadership focus to a tactical and tactical execution. It serves as the foundation for the workshops that both co-authors have conducted to build a program backlog, which would make a good article topic.

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

    Lay Down Your Cards

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

  • Beware the Cut ‘n’ Paste Persona

    Beware the Cut ‘n’ Paste Persona

    A machine learning algorithm is used to create individual encounters on this person does not occur. It takes actual photos and recombines them into false people faces. We just squirted past a LinkedIn post that claimed this website might be helpful “if you are developing a image and looking for a photo.”

    We concur that personas may remain excellent matches for computer-generated eyes, but not for the purpose you might think. Ironically, the website highlights the core issue of this very common design method: the person ( a ) does not exist. Personas are deliberately created, just like in the pictures. 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 identities. In their content” Personas- A Plain Introduction”, the Interaction Design Foundation defines profile as “fictional characters, which you create based upon your study in order to reflect the unique user types that might use your service, product, site, or brand”. Personas typically consist of a name, profile picture, quotes, demographics, goals, needs, behavior in relation to a particular service/product, emotions, and motivations ( for example, see Creative Companion’s Persona Core Poster ). According to design firm Designit, the goal of personas is to “make the research relateable, ]and ] easy to communicate, digest, reference, and apply to product and service development.”

    The decontextualization of personalities

    People are well-known because they make “dry” research information relevant and more people. However, this approach places a cap on the study’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 realize their decision-making method or allow you to connect to users ‘ thoughts and behavior, they lack stories. You are aware of the persona’s actions, but you lack the knowledge to know why. You end up with less human-like user images.

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

    People are assumed to be dynamic, according to people.

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

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

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

    Personas focus on individuals, not the environment

    You’re designing for a context, not an individual, in the real world. There are environmental, political, and social factors to consider when a person lives in a family, a community, or an ecosystem. A design is never meant for a single user. Instead, you create a product that is intended to be used by a certain number of people. However, personas do not explicitly describe how the user interacts with the environment but rather show the user alone.

    Would you always make the same decision over and over again? Despite your pledge to eat vegan, you may still choose to purchase some meat when your relatives visit. Your decisions, including your behavior, opinions, and statements, are not only completely accurate but highly contextual because they depend on a range of circumstances and variables. The persona that “represents” you wouldn’t take into account this dependency, because it doesn’t specify the premises of your decisions. It doesn’t offer a justification 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, personas are usually placed in a scenario that’s a” specific context with a problem they want to or have to solve “—does that mean context actually is considered? Unfortunately, what 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 like,” They took what I said 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 need, or emotion ) into whose own specific context you specify it, and then report it as an isolated finding ( or goal, need, or emotion ).

    But personas go a step further, extracting a decontextualized finding and joining it with another decontextualized finding from somebody else. The resultant set of findings frequently does not make sense because it is unclear or even contradictory because it lacks the underlying causes for and how that finding came about. It lacks any significance. And the persona doesn’t give you the full background of the person ( s ) to uncover this meaning: you would need to dive into the raw data for each single persona item to find it. What then is the persona’s usefulness?

    People’s relatability can be deceiving.

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

    It’s the finishing touch of a persona’s decontextualization: after having assumed that people’s personalities are fixed, dismissed the importance of their environment, and hidden meaning by joining isolated, non-generalizable findings, designers invent new context to create ( their own ) meaning. As with everything they produce, they do so by introducing a lot of biases. As Designit put it, as designers, we can” contextualize]the persona ] based on our reality and experience. We create connections that are familiar to us“. With every new detail added, this practice furthers stereotypes, doesn’t reflect real-world diversity, and gets further away from people’s actual reality.

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

    Dynamic Selves: The alternative to personas

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

    Designit suggested utilizing 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 doesn’t consider that people are a part of a system that controls their behavior, personality, and, yes, mindset. Therefore, Mindsets are also not absolute but change in regard to the situation. What determines a particular Mindset, remains to be seen.

    Another option is provided by Margaret P., the author of the article” Kill Your Personas,” who has argued for replacing personas with persona spectrums that include a range of user abilities. For example, a visual impairment could be permanent ( blindness ), temporary ( recovery from eye surgery ), or situational (screen glare ). Persona spectrums are very helpful for more inclusive and context-based design because they are based on the understanding that the context is the pattern, not the personality. However, their only drawback is that they have a very functional perspective on users that misses the relatability of a real person taken from within a spectrum.

    In developing an alternative to personas, we aim to transform the standard design process to be context-based. 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 settings

    Nothing can be more relatable and inspiring than reality. Therefore, we have to understand real individuals in their multi-faceted contexts, and use this understanding to fuel our design. This approach is known as Dynamic Selves.

    Let’s take a look at how the approach looks based on an illustration from 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 choose the individuals who best fit the “population” you’re designing for. If you select the right sample and 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. Once you’ve seen her in a few different settings, you’ve grasped Susan’s general scheme of action. Not Susan as an atomic being but Susan in relation to the surrounding environment: how she might act, feel, and think in different situations.

    It becomes clear why each person should be portrayed as an individual because each already represents an abstraction of a larger group of people in similar circumstances because each person is representative of a portion of the population you’re researching. You don’t want to see abstractions of abstractions! These selected people need to be understood and shown in their full expression, remaining in their microcosmos—and if you want to identify patterns you can focus on identifying patterns in contexts.

    However, the question persists: how do you choose a representative sample? 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 therefore recruited by enticing people to explain why and how they obtained a smart thermostat. There were those who had chosen to purchase it, those who had been influenced by others, and those who had discovered it in their homes. So we selected representatives of these three situations, from different age groups and geographical locations, with an equal balance of tech savvy and non-tech savvy participants.

    2. Conduct your research

    After having chosen and recruited your sample, conduct your research using ethnographic methodologies. This will give you more examples and anecdotes to enrich your qualitative data. Given COVID-19 restrictions, we transformed an internal ethnographic research project into remote family interviews conducted at home and accompanied by diary research for our example project.

    To gain an in-depth understanding of attitudes and decision-making trade-offs, the research focus was not limited to the interviewee alone but deliberately included the whole family. Each interviewee would provide a story that would then become much more interesting and precise with the additions made by their spouses, husbands, kids, or occasionally even pets. We also paid attention to the behaviors that came from having relationships with other meaningful people ( such as coworkers or distant relatives ) and the relationships that came from those relationships. 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. This “plan to be surprised” will allow for the most enlightening findings. One of our participants responded to our question about how his family controlled the house temperature by saying,” My wife has not installed the thermostat’s app; she uses WhatsApp instead. If she wants to turn on the heater and she is not home, she will text me. I serve as her thermostat.

    3. Analysis: Create the Dynamic Selves

    You begin to represent each individual as a series of dynamic selves during the research analysis, each” Self” representing a particular context. 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 important demographics were family type, number and type of houses 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. We depicted him hiking with his young daughter as a result.

    At the end of the research analysis, we displayed all of the Selves ‘” cards” on a single canvas, categorized by activities. Each card featured a situation, which was indicated by a quote and a distinctive image. Each participant had a different deck full of self-assessments.

    4. Identify potential designs

    You’ll start to notice patterns when you’ve written down all of the key phrases from the interview transcripts and diaries as self-cards. These patterns will highlight the opportunity areas for new product creation, new functionalities, and new services—for new design.

    There was a particularly intriguing insight around the concept of humidity in our example project. We became aware of the importance of monitoring humidity for health and 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, as well as the fact that people are surrounded by constantly 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 love technology who have families or are single, who are wealthy or poor. 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 about people and how difficult it is to feel empathy for others. We have the deepest compassion for people with whom we can directly relate.

    If you take a real person as inspiration for your design, you no longer need to create an artificial character. No more developing plot devices to “realize” the character, and no more need for additional bias. 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 perform daily design checks and may prevent you from taking shortcuts.

    And finally, real people in their specific contexts are a better basis for anecdotal storytelling and therefore are more effective in persuasion. To obtain this result, it is crucial to document real research. The circumstances of your design proposals resound in your mind when you encounter Alessandra. 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 provide a shortcut to deal with reality’s complexities, but this process of simplification can occasionally flatten out people’s lives into a few general characteristics.” Unfortunately, personas have been culprits in a crime of oversimplification. They fail to account for the complex nature of our users ‘ decision-making processes and don’t take into account the fact that people are immersed in contexts.

    Design needs to be simplified, but not to be a generalization. You have to look at the research elements that stand out: the sentences that captured your attention, the images that struck you, the sounds that linger. Avoid using those and use them to describe the person in all of their contexts. People and insights both come with 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.

  • Asynchronous Design Critique: Giving Feedback

    Asynchronous Design Critique: Giving Feedback

    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 opinions can lead to conflict on projects, lower morale, and long-term, undermine trust and teamwork. Quality suggestions can have a revolutionary effect.

    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 draw requests, designers make comments on their beloved design tools, and other things.

    Design criticism is frequently referred to as a form of collaborative suggestions that is used 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 bedrock of every effective analysis, so where do we need to begin? There are many designs that you can use to form your content. This one from Lara Hogan is the one I privately like best because it’s simple and actionable.

    Although this equation is typically used to provide feedback to individuals, it likewise fits really well in a style criticism because it finally addresses some 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 something that needs to be improved. You’ll have a mental model that will enable you to be more accurate and effective if you keep in mind the three components of the equation.

    Here is a comment that could be given as a part of some feedback, and it might look reasonable at a first glance: it seems to superficially fulfill the elements in the equation. But does it exist?

    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 on how to find 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, adding an additional reason why you think the suggestion is better might be helpful 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 between the request and question approaches can occasionally be influenced by one’s personal preferences. 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 companies. 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 a member of this other team who 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 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, boosting overall collaboration’s effectiveness and efficiency beyond the single comment. Consider the following example:” Let’s make sure that all screens have the same two forward and back buttons” instead. The designer receiving this feedback wouldn’t have much to go by, so they might just apply the change. The interface might change in later iterations or they might add new features, 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.

    The equation above is not intended to provide a predetermined template for feedback, but rather a mnemonic to reflect and enhance the practice. Even after years of active work on my critiques, I still from time to time go back to this formula and reflect on whether what I just wrote is effective.

    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 create a positive working environment. Over the years, I’ve tried to summarize the required soft skills in a formula that mirrors the one for content: the receptivity equation.

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

    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 early stages? Iteration later? Polishing work in progress? Each of these needs varies. The ideal setting will increase the likelihood that your feedback will be appreciated.

    Attitude is the equivalent of intent, and in the context of person-to-person feedback, it can be referred to as radical candor. That entails checking before writing to see if what we have in mind will actually help the person and improve the project overall. Perhaps we don’t want to admit that we don’t really appreciate that person when we reflect on them. 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 being a passive tyrant? 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, including the fact that occasionally certain words may cause specific reactions, that non-native speakers may not be able to comprehend all thenuances of some sentences, that our brains may be different, and that we may perceive the world differently. Neurodiversity is a requirement. Whatever the reason, it’s important to review not just what we write but how.

    I asked for some feedback on how I gave it a while back. 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 wasn’t my intention at all! I recently realized that I had been giving them months of feedback without ever feeling stupid. I was horrified … but also thankful. I quickly changed my situation by adding “oh” to my list of replaced words (your choice between aText, TextExpander, or others ) so that when I typed “oh,” it was immediately deleted.

    Something to keep in mind because it’s quite common, especially in teams with a strong group spirit, is that people frequently beat around the bush. It’s important to remember here that a positive attitude doesn’t mean going light on the feedback—it just means that even when you provide hard, difficult, or challenging feedback, you do so in a way that’s respectful and constructive. The best thing you can do for someone is to encourage their growth.

    Giving feedback in written form can be reviewed by someone else who isn’t directly involved, which can help to reduce or eliminate any bias that might exist. I found that the best, most insightful moments for me have happened when I’ve shared a comment and I’ve asked someone who I highly trusted,” How does this sound”?,” How can I do it better”, and even” How would you have written it” ?—and I’ve learned a lot by seeing the two versions side by side.

    The format

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

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

    In terms of clarity, start by grounding the critique that you’re about to give by providing context. This includes specifically describing where you’re coming from: do you have a thorough understanding of the project, or is this your first time seeing it? Are you bringing in a high-level perspective, or are you just learning the ins and outs? Are there regressions? Which user’s point of view do you consider when providing feedback? Is the design iteration at a point where it would be acceptable to ship this, or are there significant issues that need to be addressed first?

    Providing context is helpful even if you’re sharing feedback within a team that already has some information on the project. And context is a must when providing cross-team feedback. If I were to review a design that might be directly related to my work, I would say that, underlining my opinion as external, and if I had no idea how the project might have come to that conclusion.

    We often focus on the negatives, trying to outline all the things that could be done better. That’s obviously important, but it’s even more crucial to concentrate on the positive aspects, especially if you saw improvement in the previous iteration. Although this may seem superfluous, it’s important to keep in mind that design is a field with hundreds 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 things that are going well because those things will have been deemed significant in the long run. Positive feedback can also help, as an added bonus, prevent impostor syndrome.

    There’s one powerful approach that combines both context and a focus on the positives: frame how the design is better than the status quo ( compared to a previous iteration, competitors, or benchmarks ) and why, and then on that foundation, you can add what could be improved. This is powerful because there is a big difference between a critique of a design that is already in good shape and one that is critiqued for a design that isn’t quite there yet.

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

    One of the best ways to assist the designer who is reading 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, adding screenshots or identifying markers for the specific area of the interface you’re referring to can also be very helpful.

    One method that I’ve personally used to enhance the bullet points in some situations is using emojis. So a red square � � means that it’s something that I consider blocking, a yellow diamond � � is something that I can be convinced otherwise, but it seems to me that it should be changed, and a green circle � � is a detailed, positive confirmation. A blue spiral is also used for either 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, which conveys a positive action because green is typically seen as a confirmation color. Do we need to look for a different color?
    • 🔶Tiles—Given the number of items on the page, and the overall page hierarchy, it seems to me that the tiles shouldn’t be using the Subtitle 1 style but the Subtitle 2 style. This will help maintain consistency in the visual hierarchy.
    • Background: A light texture is effective, but I’m not sure if doing so will cause too much noise on this kind of page. What is the thinking in using that?

    What about using Figma or another design tool that enables in-place feedback to provide feedback directly? These are generally difficult to use because they conceal discussions and are harder to follow, but 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 more thing: Say the obvious. Sometimes we might feel good or bad about something, so we don’t say it. Or sometimes we might have a doubt that we don’t express because the question might sound stupid. Say it, that’s fine. Don’t hold it back. 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.

    Another benefit of asynchronous feedback is that written feedback automatically monitors decisions. Why did we do this, especially in large projects? could be a question that pops up from time to time, and there’s nothing better than open, transparent discussions that can be reviewed at any time. I advise using software to save these discussions so they can be hidden once they are resolved, for this reason.

    Content, tone, and format. Each one of these subjects provides a useful model, but working to improve eight areas—observation, impact, question, timing, attitude, form, clarity, and actionability—is a lot of work to put in all at once. One effective way to approach them is to start with the area you lack the most, either from your point of view or from 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.

  • That’s Not My Burnout

    That’s Not My Burnout

    Are you like me when I read about people who fade away as they age and who don’t have any sense of connection? Do you feel like your feelings are invisible to the earth because you’re experiencing burnout different? Our main comes through more when stress starts to press down on us. Beautiful, content hearts quieten and fade into that remote and distracted stress we’ve all read about. But some of us, those with fires constantly burning on the sides of our key, getting hotter. I am a blaze in my brain. When I’m in a burnout situation, I twice over, quad down, burn hotter and hotter to try to overcome the situation. I don’t fade— I am engulfed in a passionate stress.

    What on earth is a passionate fatigue, then?

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

    This person seems to need self-care because she has too much going on. But no, she doesn’t have occasion for that. She begins to feel as though she’s dropping balloons. Not enough is accomplished. 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 emotions become more and more real, her domestic tale becomes more and more important.

    Immediately she KNOWS what she needs to do! She ought to do more.

    This loop is challenging and risky. Understand why? Because when she doesn’t complete that new target, the narrative will only get worse. She immediately starts failing. She isn’t doing much. She is insufficient. She’ll discover more she may do because she might neglect, or perhaps her home. She doesn’t nap as much, proceed because much, all in the attempts to do more. Not succeeds in any objective target despite constantly trying to prove herself to herself. Always feeling “enough”

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

    I 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 always went without and also got an extra here or there because my mother was so competent and my father was so friendly.

    When my mother gave me food stamps as a child, I didn’t think shame; rather, I would have good started any debates about the subject, orally eviscerating anyone who dared to criticize the handicapped girl 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 begins meet impacted people 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 I had to put more of myself into it because I am the one who is. I learned first that when something frightens me, I can 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 people’s worries.

    And here I am, more than 30 years later, also feeling the urge to aimlessly force myself forward when faced with daunting tasks in front of me, assuming that I am the one who is and consequently does. I feel more motivated to show that I may make things happen if I put in more effort, put on more responsibilities, and do more.

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

    Why all this story, then? You see, stress is a volatile thing. Over the years, I’ve read and heard a bunch about stress. Stress is a real phenomenon. Especially today, with COVID, many of us are balancing more than we ever have before—all at again! It’s difficult, and so many wonderful experts are affected by the procrastination, avoidance, and shutting down. There are significant reports that, in my opinion, relate to the majority of people out there, but no me. That’s not what my fatigue looks like.

    The perilous visibility of passionate burnout

    In many workplaces, extra work, more energy, and general focused commitment are seen as an asset ( and occasionally that’s all it is ). They see anyone trying to rise to difficulties, never one stuck in their anxiety. Some well-intentioned companies have procedures in place to safeguard their teams from fatigue. However, in situations like this, alarms don’t usually ring, and some business members are surprised and depressed when the inevitable prevent occurs. And maybe even actually betrayed.

    Parents are praised for being so on top of it all when they may work, participate in the after-school activities, exercise self-care in the form of diet and exercise, and also meet friends for coffee or wines. More but mothers, statistically speaking. Many of us have watched countless streaming COVID shows to see how challenging it is for the adult character, but she is strong and interesting and can do it. It’s a “very special season” when she breaks down, cries in the bathroom, terribly admits she needs help, and only stops for a bit. Truth be told, countless people are avoiding tears or doomscrolling to flee. Although we are aware that the media is a lie to amuse us, a large portion of society has been perceived as being biased against it.

    Women and burnout

    I adore 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 must do more to” justify” their discontinuance from 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?

    You might not be the same as that. After all, we are all unique, and our responses to stressors are also unique. It’s part of what makes us human. Don’t put too much emphasis on how burnout manifests; rather, learn to recognize it in yourself. Here are a few questions I occasionally ask my friends if they worry about them.

    Are you happy? The first thing you should ask yourself should be this straightforward query. Even if you’re burning out doing all the things you love, you’ll probably stop enjoying yourself as you approach burnout.

    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” and not let the people around them be disappointed.

    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 could be just one more thing you need to learn, or it might just be crunch time. That occurs; life occurs. 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 strategy 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 conclusion

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

    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 be pretty bad by now 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 facilitate healing by justifying the amount of time you spend working on you if they are making you burn out.

    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, cooking for someone always comes naturally to my mind. 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 clear your head. I’ve always had the ability to locate a location on a map and prepare food from it ( thanks, Pinterest ). I love cooking Indian food, as the smells are warm, the bread needs just enough kneading to keep my hands busy, and the process takes real attention for me because it’s not what I was brought up making. And ultimately, we all triumph!

    Vent like a sniveling jerk.

    Be careful with this one!

    Over the past few years, I have made an effort to practice more gratitude, and I am aware of the real advantages of doing so. 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 to not judge you, to feel your pain, and, most importantly, to instruct you to take your own rectal cavity out of your cranium. Seriously, it’s about getting a reality check here! One of the things that I admire most about my husband is how he can simplify things down to the simplest of terms, even though sometimes after the fact. We’re spending our lives together, and I can’t wait to get over it. He’s spoken in this way about his devotion, love, and acceptance of me, and I couldn’t be more appreciative. It also, of course, has meant that I needed to remove my head from that rectal cavity. Again, those instances are typically appreciated in retrospect.

    Grab a book, 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 appeals to you. Among the titles that have stood out to me are:

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

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

    • The Drunken Botanist by Amy Stewart
    • Darin Olien’s Superlife
    • A Brief History of 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. Nothing about my life needs anything from me, and I just find the subject interesting.

    Give yourself a break.

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

    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 have greater power than the repressed fears that motivate us.

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

    I just learned that we are all euthanizing in our daily lives. 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 understand that none of these concepts will “fix it,” and that’s not their intention. None of us has complete control over our surroundings, but only how we react to them. These suggestions are to help stop the spiral effect so that you are empowered to address the underlying issues and choose your response. They are the things that largely work for me. They might be able to work for you.

    Does this sound familiar?

    If this sounds familiar, you’re not just going to know about it. Don’t let your negative self-talk indicate that you “even burn out wrong.” It’s not wrong. Even if I’m rooted in fear like my own drivers, I think this need to do more comes from a place 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 where Pooh ate so much at Rabbit’s house that his buttocks were unable to pass through the door? It came as no surprise when he abruptly declared that this was unacceptable because I already associate a lot with Rabbit. But do you recall what happened next? He made the most of the large butt in his kitchen by placing a shelf across poor Pooh’s ankles and decorations on his back.

    We are resourceful and aware that we can push ourselves when necessary, even when we are exhausted or have a ton of clutter in our room. None of us has to be afraid, as we can manage any obstacle put in front of us. And maybe that means we need to redefine success in order to make room for comfort for being uncomfortable human, but that doesn’t really sound that bad either.

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

  • Voice Content and Usability

    Voice Content and Usability

    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 speech, between spoken and written. 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 machines to interpret and know.

    This luxury is not available in spoken language. There are also verbal cues and vocal behaviors that modulate conversation in nuanced ways: how something is said, not what. These are also 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 significant challenges when it comes to voice interfaces, the machines with which we speak.

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

    A single conversation from beginning to end that achieves some outcome for the user, starting with the voice interface’s first greeting and ending with the user exiting the interface, also fits into these three categories, which I refer to as transactional, informational, and prosocial. Note here that a conversation in our human sense—a chat between people that leads to some result and lasts an arbitrary length of time—could encompass multiple transactional, informational, and prosocial voice interactions in succession. In other words, a voice interaction is a conversation, but it may not always be one voice interaction.

    Purely prosocial exchanges are more gimmicky than captivating in the majority of voice interfaces because machines are unable to yet have the capability to truly understand how we are doing and engage in the kind of glad-handing behavior that people crave. There’s also ongoing debate as to whether users actually prefer the sort of organic human conversation that begins with a prosocial voice interaction and shifts seamlessly into other types. In 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 a brief smattering of neighborly small talk to ordering a pizza ( generously topped with pineapple, as it should be ) when we walk up to the counter and place an order.

    Alison: Hey, how’s it going?

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

    Alison: Can I get a pizza from Hawaii with extra pineapple.

    Burhan: Yes, but what size?

    Alison: Large.

    Burhan: Anything else?

    Alison: No thanks, that’s it.

    Burhan: Something to drink?

    Alison, I’ll have a bottle of Coke.

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

    A service rendered or a product delivered: each progressive disclosure in this transactional conversation reveals more and more of the desired outcome of the transaction. 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 kosher or halal dishes, trying gluten-free dishes, or something else entirely. Even though we have a prosocial mini-conversation once more at the beginning to establish politeness, we’re after much more.

    Alison: Hey, how’s it going?

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

    Alison: Can I ask a few questions?

    Burhan: Of course! Continue straight ahead.

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

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

    Alison, what about pizzas that are gluten-free?

    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 now. Good to know. Thank you!

    Burhan: Anytime, come back soon!

    This is a very different dialogue. Here, the goal is to obtain a particular set of facts. Informational conversations are research expeditions to gather data, news, or facts, or they are investigative quests for the truth. 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 to ensure that the customer understands the main ideas.

    Voice Interfaces

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

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

    IVR ( interactive voice response ) systems

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

    IVR systems made it easier for businesses to cut down on call centers, but they soon gained a reputation 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.

    Screen readers are the norm

    Parallel to the evolution of IVR systems was the invention of the screen reader, a tool that transcribes visual content into synthesized speech. For Blind or visually impaired website users, it’s the predominant method of interacting with text, multimedia, or form elements. Screen readers are the norm 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 computers 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 for websites. 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” ( ).

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

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

    I disliked the operation of Screen Readers from the beginning. Why are they designed the way they are? It makes no sense to present information visually and then only to have that information translated into audio. All the effort and effort put into creating the ideal app user experience 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 find that voice interfaces, especially more contemporary voice assistants, provide a more streamlined experience.

    Voice-activated devices

    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-activated devices are akin to personal concierges that can answer questions, schedule appointments, conduct searches, and perform other common day-to-day tasks. And they’re rapidly gaining more attention from accessibility advocates for their assistive potential.

    Before the earliest IVR systems found success in the enterprise, Apple published a demonstration video in 1987 depicting the Knowledge Navigator, a voice assistant that could transcribe spoken words and recognize human speech to a great degree of accuracy. Then, in 2001, Tim Berners-Lee and others created their vision for a Semantic Web “agent” that would carry out routine tasks like” checking calendars, making appointments, and finding locations” (, behind paywall ). Apple’s Siri 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 Apple’s Siri and Microsoft’s Cortana were released, they couldn’t extend their 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, so even now it isn’t possible to program Siri to perform arbitrary functions.

    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 stifled by the limitations of Siri and Cortana are increasingly using programmable voice assistants that allow for customization and extensibility. Google Home enables the programming of arbitrary Google Assistant skills, while Amazon offers the Alexa Skills Kit, a developer framework for creating custom voice interfaces for Amazon Alexa. Today, users can choose from among thousands of custom-built skills within both the Amazon Alexa and Google Assistant ecosystems.

    As businesses like Amazon, Apple, Microsoft, and Google continue to occupy their positions, they’re also selling and open-sourcing an unheard array of tools and frameworks for designers and developers that aim to make creating voice interfaces as simple as possible, even without code.

    Often by necessity, voice assistants like Amazon Alexa tend to be monochannel—they’re tightly coupled to a device and can’t be accessed on a computer or smartphone instead. In contrast, many development platforms, such as Google’s Dialogflow, have omnichannel capabilities that allow users to create a single conversational interface that then becomes a voice interface, textual chatbot, and IVR system upon deployment. In Chapter 4, we’ll explore some of the possible effects these variables might have on how you build out your design artifacts, but I don’t recommend any particular implementation strategies in this design-focused book.

    Voice Content

    Simply put, voice content is voice-transmitted content. Voice content must be free-flowing and organic, contextless and concise—everything written content isn’t enough 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 initial foray into informational voice interfaces will likely be to provide user content, for many of us. There’s only one problem: any content we already have isn’t in any way ready for this new habitat. How can we improve the conversational content on our websites? 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. Informing delivery channels both established and novel, Microcontent provides the best opportunity to find out how your content can be stretched to the limits of its potential.

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

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

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

  • Designing for the Unexpected

    Designing for the Unexpected

    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 items that are functional on products that have not yet been created?

    Flash, Photoshop, and flexible pattern

    Photoshop was my go-to program when I first started creating blogs. I created a 960px paint and set about creating a design that I would eventually lose information in. Set widths, fixed heights, and complete placement were the keys to pixel-perfect accuracy during the development phase.

    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 style didn’t help my fear. My second project was to get an active fixed-width website and make it reactive. What I discovered the hard manner was that you can’t really put adaptability at the end of a job. To make smooth design, you need to prepare throughout the style stage.

    A novel method of architecture

    Developing flexible or smooth 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 smaller- 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 many more with washable parts.

    Our rely on multimedia queries resulted in parts that were tied to frequent window sizes. This is a real problem if element libraries are intended to be reused because they cannot be used when the devices being designed for match the pattern library’s viewport sizes, thus failing to achieve the “devices that don’t already occur” goal.

    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 sun or our lord?

    Container concerns have long been touted as an improvement upon multimedia questions, but at the time of composing are unsupported in most computers. Solutions for JavaScript exist, but they can lead to dependencies and connectivity issues. The basic principle underlying box queries is that elements may change based on the size of their family box and not the viewport diameter, as seen in the following illustrations.

    One of the biggest arguments in favor of box concerns is that they help us create elements or design designs that are really reusable because they can be picked up and placed somewhere in a design. This is a significant step in the direction of a component-based design that can be used on any device of any size.

    In other words, responsive components to replace responsive layouts.

    Container queries will enable us to design components that can be placed in a sidebar or in the main content rather than 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. This strategy will always be restrictive because we will still require pre-defined breakpoints. For this reason, my main question with container queries is, How would we decide when to change the CSS used by a component?

    A component library 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, and they would increase the possibilities for reuse and design at scale. 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 tied to page markup in the same way, 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”

    Intrinsic layouts can also make use of a mix of fixed and flexible units, letting the content choose how much space it occupies.

    What distinguishes intrinsic design is that 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.

    They now have the ability to adapt to the content both inside and outside of 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 instance of “everything changed,” in my opinion.

    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 with an existing codebase and use existing tools and frameworks.

    Another could be that I feel more prepared for change now. I was brand-new to design in general in 2010, and the shift 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 benefit when creating layout templates, intrinsic design and frameworks do not go hand in hand 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.

    Content first

    Content is variable. 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 left-to-right or 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 be used as values.

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

    —or as properties.

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

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

    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 % ( the preferred value ) of its container, with no exceptions for 300px and 600px.

    With these techniques, we have a content-first approach to responsive design. We can distinguish between markup and content, which means that user modifications will not 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 enabling more or less content to be displayed correctly by matching desired dimensions with adaptable alternatives.

    Situation first

    We can address device flexibility by changing our approach, which focuses on content and space rather than devices, as we’ve discussed so far. But what about that last bit of Jeffrey Zeldman’s quote,”… situations you haven’t imagined”?

    It’s a completely different design process for someone using a mobile phone and moving through a crowded street in glaring sunshine from a person 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

    There are places in the world where mobile data is prohibitively expensive and where there is little or no broadband infrastructure.

    ” 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 drops in connectivity while traveling on trains or other modes of transportation. 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.

    Image alt text

    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 required files should be downloaded for use.

    …

    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 return of media inquiries

    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 more than one situation. It’s less about one-size-fits-all and more about providing adaptable content.

    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 Unexpected

    In the end, the one thing we should always expect is for things to change. With foldable screens already available on the market, devices in particular change more quickly than we can keep up.

    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 content first and allowing that content to adapt to whatever space surrounds it.

    A lot of the CSS discussed here is about moving away from layouts and putting content at the heart of design. There is a lot 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 usable when people need them, whenever and wherever that may be. We can move closer to achieving this by involving users in our design decisions, by creating choice via browsers, and by giving control to our users with user-preference-based media queries.

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

  • Asynchronous Design Critique: Getting Feedback

    Asynchronous Design Critique: Getting Feedback

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

    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 down some insightful questions, just like we wouldn’t do any research without the right questions to obtain 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.

    Finally, we need to review what we received, get to the heart of its perspectives, and taking 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 who won’t comment on the boundaries of keys during a high-level flows review. 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? A number of elements are involved. One is that we don’t often consider asking as a part of the input method. Another is how healthy it is to leave the question open and assume that everyone else will agree. Another is that there are frequently no need to be that exact in nonprofessional dialogues. In short, we tend to underestimate the importance of the concerns, so we don’t work on improving them.

    The work of asking insightful questions guidelines and concentrates the criticism. It also serves as a form of acceptance, outlining your willingness to make remarks and the types of comments you want to receive. It puts people in the right emotional position, especially in situations when they weren’t expecting to provide feedback.

    There isn’t a second best way to ask for opinions. It simply needs to be certain, and precision can get a variety of forms. A design for design critique that I’ve found especially helpful in my training is the one of stage over depth.

    The term” period” refers to each of the stages of the process, in our case, the design phase. The type of input changes as the customer research moves on 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 user experience may serve as a starting point for possible questions. What are your job goals, exactly? User requirements? Funnality? Articles? Contact design? Data structures Interface design Navigation style? physical architecture 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 flow for any errors or steps I might have missed.
    • Information structures: We have two competing bits of information on this site. Does the framework make a good communication between them?
    • 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. Are there any ways to deal with this?
    • Are the thick alerts in the bottom-right corner of the page visible enough?

    The other 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 especially hard. 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 issues that we can consider when we want to accomplish more specific—and more effective—questions.

    Eliminating generic finals from your questions like “good,” “well,” “nice,” “bad,” “okay,” and” cool” is a simple technique. Asking,” When the stop opens and the switches appear, is this conversation great, 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 need a lot of feedback. Although that is uncommon, it is possible. 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 after someone’s first five seconds of viewing it, it becomes obvious that what you’re asking is open ended but focused on the subject.

    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 getting back into rabbit holes like those that could lead to even more refinement if what’s important right now isn’t.

    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.

    Create explicit checkpoints for discussion is the asynchronous design-critique strategy that I believe works the best. 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 a discussion thread of some kind. Any platform that can accommodate this type of structure can use this. By the way, when I refer to a “write-up or presentation“, I’m including video recordings or other media too: as long as it’s asynchronous, it works.

    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 a record 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. From there, there can be 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 to achieve
    2. The layout
    3. The list of changes
    4. The querys

    A goal for each project is likely to be one that has already been condensed into a single sentence, such as the request for the project owner, the product manager, or the client brief. So this is something that I’d repeat in every iteration post—literally copy and pasting it. The goal is to provide context and repeat what is required to complete each iteration post, avoiding having to search for information in different posts. 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 the design is then called. In short, it’s any design artifact. In the work’s final stages, I prefer to use the term “blank” to emphasize that I’ll be displaying complete flows rather than individual screens to facilitate comprehension of the larger picture.

    It might also be helpful to have clear names on the artifacts so that it is easier to refer to them. 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. Making a numbered list of questions available in the form of a number can also make it simpler to refer to each one by its name.

    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 iteration posts are written and intended as checkpoints, I want to point out that they are not by any means 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 eventually started using particular labels for incremental iterations, such as 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. One can quickly say,” This was discussed in i4″ with each project, and everyone knows where to go to review things.
    • Unassuming—It functions like versions ( such as v1, v2, and v3 ), but versions give the impression of something that is large, 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 bits that still need work and, in turn, need more iterations:” with i8 we reached RC” or “i12 is an RC” to illustrate this.

    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, using a different approach when we work asynchronously is more effective: adopting 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.

    Asynchronous feedback is particularly effective because of this shift, 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 own worth.

    The first friction is being forced to respond to every comment. Sometimes we write the iteration post, and we get replies from our team. It’s simple, straightforward, and doesn’t cause any issues. 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 responding to all comments, it can be effective, but when we consider 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:

      One is to let the next iteration speak for itself. When the design changes and we publish a follow-up iteration, that’s the response. 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 quickly summarize the comments before moving on. This may be particularly helpful if your workflow uses a simplified checklist to refer to 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 thing that one can hope that they might learn is that they could begin to acknowledge that they are doing this and that they could be more aware of where they are coming from. Swoop-by comments frequently prompt the simple thought,” We’ve already discussed this,” and it can be frustrating to have to keep coming back and forth.

    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, so it’s acceptable to repeat things occasionally!

    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 relation to the design could be the third friction point, which might cause us to feel defensive if the review turned out to be more of 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 specialization, and the designer has the most background and knowledge to make the best 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.