Blog

  • Opportunities for AI in Accessibility

    Opportunities for AI in Accessibility

    I was completely moved by Joe Dolson’s subsequent 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 accessibility technology tactician who helps manage the AI for Accessibility give 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. And there are a lot of uses for the poor midsection as well.

    I’d like you to consider this a “yes … and” piece to complement Joe’s post. I’m not trying to reject any of what he’s saying, but rather to give some context to initiatives and options where AI may produce real, positive impacts on people with disabilities. To be clear, I’m not saying that there aren’t true threats or pressing problems with AI that need to be addressed—there are, and we’ve needed to address them, like, yesterday—but I want to take a little time to talk about what’s possible in hope that we’ll get there one day.

    Other words

    Joe’s article spends a lot of time addressing computer-vision models ‘ ability to create other words. He raises a number of true points about the state of affairs right now. And while computer-vision concepts continue to improve in the quality and complexity of information in their information, their benefits aren’t wonderful. He argues to be accurate that the state of image research is currently very poor, especially for some image types, in large part due to the absence of contextual contexts in which to look at images ( as a result of having separate “foundation” models for words analysis and image analysis ). Today’s models aren’t trained to distinguish between images that are contextually relevant ( that should probably have descriptions ) and those that are purely decorative ( which might not need a description ) either. 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 and provide a starting point for alt text, even if the rapid reads,” What is this BS?” That’s not correct at all … Let me try to offer a starting point— I think that’s a gain.

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

    The image example provided in the GPT4 announcement provides an intriguing opportunity, even though complex images like graphs and charts are challenging to summarize succinctly ( even for humans ). Let’s say you came across a chart that was simply the description of the chart’s title and the type of visualization it was: Pie chart comparing smartphone usage to feature phone usage in US households earning 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 users could ask questions about the graphic if their browser knew that it was a pie chart ( because an onboard model determined this ).

    • Are there more smartphone users than feature phones?
    • How many more?
    • Exists a group of people who don’t fall under either of these categories?
    • How many is that?

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

    What if you could ask your browser to make a complicated chart simpler? What if you demanded that the line graph be isolated into just one line? What if you could ask your browser to change the color combinations in your browser so that it works better for your type of color blindness? What if you demanded that it switch colors in favor of patterns? Given these tools ‘ chat-based interfaces and our existing ability to manipulate images in today’s AI tools, that seems like a possibility.

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

    Matching algorithms

    When Safiya Umoja Noble chose to put her book Algorithms of Oppression, she hit the nail on the head. Although her book focused on the ways that search engines can foster racism, I believe it’s equally true that all computer models have the potential to foster conflict, prejudice, and intolerance. We all know 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 employment for people who are neurodivers. Based on more than 75 data points, they match job seekers with potential employers using an algorithm. On the job-seeker side of things, it considers each candidate’s strengths, their necessary and preferred workplace accommodations, environmental sensitivities, and so on. On the employer side, it considers each work environment, communication factors related to each job, and the like. Mentra made the decision to change the script when it came to traditional employment websites because it was run by neurodivergent people. They lower the emotional and physical labor on the job-seeker side of things by recommending available candidates to companies who can then connect with job seekers they are interested in.

    More people with disabilities can be used to create algorithms, which can lessen the likelihood that they 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 from people who discussed topics of interest to those who were fundamentally different from your current sphere of influence. For instance, if you followed a group of nondisabled white male academics who spoke about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also speak about AI. If you took its recommendations, perhaps you’d get a more holistic and nuanced understanding of what’s happening in the AI field. These same systems should also use their understanding of biases about particular communities—including, for instance, the disability community—to make sure that they aren’t recommending any of their users follow accounts that perpetuate biases against (or, worse, spewing hate toward ) those groups.

    Other ways that AI can helps people with disabilities

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

      Voice preservation. You may have seen the VALL-E paper or Apple’s Global Accessibility Awareness Day announcement or you may be familiar with the voice-preservation offerings from Microsoft, Acapela, or others. People who have ALS ( Lou Gehrig’s disease ), motor-neuron disease, or other medical conditions that can prevent them from talking can greatly benefit from having an AI model that can mimic your voice. This is, of course, the same tech that can also be used to create audio deepfakes, so it’s something that we need to approach responsibly, but the tech has truly transformative potential.
    • Voice recognition. Researchers like those involved in the Speech Accessibility Project are offering compensation to people with disabilities for their assistance in the collection of audio recordings of people with atypical speech. As I type, they are actively recruiting people with Parkinson’s and related conditions, and they have plans to expand this to other conditions as the project progresses. 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 lead to more inclusive data sets that enable them to use their computers and other devices more effectively and with just their voices.
    • Text transformation. The most recent generation of LLMs is quite capable of changing existing text without giving off hallucinations. This is incredibly empowering for those who have cognitive disabilities and who may benefit from text summaries or simplified versions, or even text that has been prepared for Bionic Reading.

    The value of various teams and sources of data

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

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

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

    Want a coding copilot who can provide you with useful 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.

  • The Wax and the Wane of the Web

    The Wax and the Wane of the Web

    When you begin to believe you have everything figured out, everyone does change, in my experience. Simply as you start to get the hang of injections, diapers, and ordinary sleep, it’s time for solid foods, potty training, and nighttime sleep. When those are determined, school and occasional naps are in order. The pattern continues.

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

    How we got below

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

    The beginning of website standards

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

    Server-side language like PHP, Java, and.NET took Perl as the primary back-end computers, and the cgi-bin was tossed in the garbage bin. With these better server-side instruments came the first time of online applications, starting with content-management systems ( especially in the blog space with tools like Blogger, Grey Matter, Movable Type, and WordPress ). AJAX opened the door to sequential connection between the front end and back end in the mid-2000s. Immediately, websites may update their information without needing to refresh. Developers created a crop of credible client-side interactions across browsers with wildly varying standards aid, such as Prototype, YUI, and jQuery. Techniques like photo replacement enable skilled manufacturers and developers to show fonts of their choosing. And technology like Flash made it possible to include movies, sports, and even more engagement.

    These new technology, standards, and approaches reinvigorated the market in many ways. As manufacturers and designers explored more diversified designs and layouts, website design flourished. However, we also relied heavily on tricks. When it came to basic layout and text styling, early CSS was a significant improvement over table-based layouts, but its limitations at the time meant that designers and developers still rely heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds (among other hacks ) for the appearance of full-length columns. All kinds of nested floats or absolute positioning ( or both ) were necessary for complicated layouts. The big five typefaces were initially influenced by beam and photo replacement, but both tricks caused accessibility and performance issues. Additionally, JavaScript libraries made it simple for anyone to add a dash of contact to pages, even at the expense of double or even quadrupling the get size of basic websites.

    The internet as program platform

    The balance between the front end and the back end continued to improve, leading to the development of the existing web application time. Between expanded server-side programming languages ( which kept growing to include Ruby, Python, Go, and others ) and newer front-end tools like React, Vue, and Angular, we could build fully capable software on the web. Alongside these equipment came others, including creative type control, build technology, and shared bundle libraries. What was once mainly used for linked papers turned into a world with limitless possibilities.

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

    This fusion of potent portable devices and potent creation tools contributed to the growth of social media and other centralized resources for people to use and interact with. As it became easier and more popular to interact with others immediately on Twitter, Facebook, and yet Slack, the need for held private sites waned. Social media provided connections on a global scale, with both the positive and negative effects.

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

    Where we are now

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

    Browser support for CSS, JavaScript, and other standards like web components has accelerated, especially through efforts like Interop. In a fraction of the time that they once did, new technologies gain universal support. I frequently find out about a new feature and check its browser support only to discover that its coverage has already exceeded 80 %. The barrier to using more recent techniques isn’t browser support anymore; it’s more often the speed at which designers and developers can learn what’s available and how to adopt it.

    Today, with a few commands and a couple of lines of code, we can prototype almost any idea. With all the tools we currently have, it is simpler than ever to launch a new venture. However, the upfront cost these frameworks may save in initial delivery eventually comes down as the maintenance and upgrading they become a part of our technical debt.

    Adopting new standards can sometimes take longer if we rely on third-party frameworks because we might have to wait for those frameworks to adopt them. These frameworks—which used to let us adopt new techniques sooner—have now become hindrances instead. Users must wait for scripts to load before being able to read or interact with pages because these same frameworks frequently come with performance costs. And when scripts fail ( whether through poor code, network issues, or other environmental factors ), there’s often no alternative, leaving users with blank or broken pages.

    Where do we go from here?

    Today’s hacks help to shape tomorrow’s standards. And there’s nothing inherently wrong with embracing hacks —for now—to move the present forward. Problems only arise when we refuse to acknowledge that they are hacks or when we refuse to take their place. What can we do to create the web’s future that we want?

    Build for the long haul. Optimize for performance, for accessibility, and for the user. Weigh the costs of those developer-friendly tools. How might they affect everything else if they make your job a little easier today? What’s the cost to users? To future developers? To standards adoption? The convenience may be worthwhile in some circumstances. It’s occasionally just a hack that you’ve gotten used to. And occasionally it’s preventing you from choosing better options.

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

    Design with care. Whether your craft is code, pixels, or processes, consider the impacts of each decision. Many modern tools have the convenience of having the ability to always understand the decisions that underlie their creation and to never consider the effects those decisions may have. Use the time saved by modern tools to think more carefully and make decisions with care rather than rushing to “move fast and break things”

    Always be learning. If you’re always learning, you’re also growing. Sometimes it may be hard to pinpoint what’s worth learning and what’s just today’s hack. Even if you were to concentrate solely on learning standards, you might end up focusing on something that won’t matter next year. ( Remember XHTML? ) However, ongoing learning opens up new neural connections in your brain, and the techniques you learn in one day may be used to inform different experiments in the future.

    Play, experiment, and be weird! This web that we’ve built is the ultimate experiment. Despite being the single largest human endeavor in history, each of us has the ability to make our own money out of it. Be courageous and try new things. Build a playground for ideas. In your own bizarre science lab, perform bizarre experiments. Start your own small business. There has never been a more empowering place to be creative, take risks, and explore what we’re capable of.

    Share and amplify. As you experiment, play, and learn, share what’s worked for you. Write on your own website, post on whichever social media site you prefer, or shout it from a TikTok. Write something for A List Apart! But take the time to amplify others too: find new voices, learn from them, and share what they’ve taught you.

    Go forth and make

    As designers and developers for the web ( and beyond ), we’re responsible for building the future every day, whether that may take the shape of personal websites, social media tools used by billions, or anything in between. Let’s imbue our values into the things that we create, and let’s make the web a better place for everyone. Create something that you are only qualified to make for yourself. Then share it, make it better, make it again, or make something new. Learn. Make. Share. Grow. Rinse and repeat. Every time you think that you’ve mastered the web, everything will change.

  • To Ignite a Personalization Practice, Run this Prepersonalization Workshop

    To Ignite a Personalization Practice, Run this Prepersonalization Workshop

    Picture this. You’ve joined a squad at your company that’s designing new product features with an emphasis on automation or AI. Or your company has just implemented a personalization engine. Either way, you’re designing with data. Now what? When it comes to designing for personalization, there are many cautionary tales, no overnight successes, and few guides for the perplexed. 

    Between the fantasy of getting it right and the fear of it going wrong—like when we encounter “persofails” in the vein of a company repeatedly imploring everyday consumers to buy additional toilet seats—the personalization gap is real. It’s an especially confounding place to be a digital professional without a map, a compass, or a plan.

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

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

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

    We call it prepersonalization.

    Behind the music

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

    We’re used to seeing the polished final result of a personalization feature. Before the year-end award, the making-of backstory, or the behind-the-scenes victory lap, a personalized feature had to be conceived, budgeted, and prioritized. Before any personalization feature goes live in your product or service, it lives amid a backlog of worthy ideas for expressing customer experiences more dynamically.

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

    ​From Big Tech to fledgling startups, we’ve seen the same evolution up close with our clients. In our experiences with working on small and large personalization efforts, a program’s ultimate track record—and its ability to weather tough questions, work steadily toward shared answers, and organize its design and technology efforts—turns on how effectively these prepersonalization activities play out.

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

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

    1. customer experience optimization (CXO, also known as A/B testing or experimentation)
    2. always-on automations (whether rules-based or machine-generated)
    3. mature features or standalone product development (such as Spotify’s DJ experience)

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

    Set your kitchen timer

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

    The full arc of the wider workshop is threefold:

    1. Kickstart: This sets the terms of engagement as you focus on the opportunity as well as the readiness and drive of your team and your leadership. .
    2. Plan your work: This is the heart of the card-based workshop activities where you specify a plan of attack and the scope of work.
    3. Work your plan: This phase is all about creating a competitive environment for team participants to individually pitch their own pilots that each contain a proof-of-concept project, its business case, and its operating model.

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

    Kickstart: Whet your appetite

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

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

    This is all about setting the table. What are the possible paths for the practice in your organization? If you want a broader view, here’s a long-form primer and a strategic framework.

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

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

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

    The third and final kickstart activity is about naming your personalization gap. Is your customer journey well documented? Will data and privacy compliance be too big of a challenge? Do you have content metadata needs that you have to address? (We’re pretty sure that you do: it’s just a matter of recognizing the relative size of that need and its remedy.) In our cards, we’ve noted a number of program risks, including common team dispositions. Our Detractor card, for example, lists six stakeholder behaviors that hinder progress.

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

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

    Hit that test kitchen

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

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

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

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

    Verify your ingredients

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

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

    1. compare findings toward a unified approach for developing features, not unlike when artists paint with the same palette; 
    2. specify a consistent set of interactions that users find uniform or familiar; 
    3. and develop parity across performance measurements and key performance indicators too. 

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

    Compose your recipe

    What ingredients are important to you? Think of a who-what-when-why construct

    • Who are your key audience segments or groups?
    • What kind of content will you give them, in what design elements, and under what circumstances?
    • And for which business and user benefits?

    We first developed these cards and card categories five years ago. We regularly play-test their fit with conference audiences and clients. And we still encounter new possibilities. But they all follow an underlying who-what-when-why logic.

    Here are three examples for a subscription-based reading app, which you can generally follow along with right to left in the cards in the accompanying photo below. 

    1. Nurture personalization: When a guest or an unknown visitor interacts with  a product title, a banner or alert bar appears that makes it easier for them to encounter a related title they may want to read, saving them time.
    2. Welcome automation: When there’s a newly registered user, an email is generated to call out the breadth of the content catalog and to make them a happier subscriber.
    3. Winback automation: Before their subscription lapses or after a recent failed renewal, a user is sent an email that gives them a promotional offer to suggest that they reconsider renewing or to remind them to renew.

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

    You can think of the later stages of the workshop as moving from recipes toward a cookbook in focus—like a more nuanced customer-journey mapping. Individual “cooks” will pitch their recipes to the team, using a common jobs-to-be-done format so that measurability and results are baked in, and from there, the resulting collection will be prioritized for finished design and delivery to production.

    Better kitchens require better architecture

    Simplifying a customer experience is a complicated effort for those who are inside delivering it. Beware anyone who says otherwise. With that being said,  “Complicated problems can be hard to solve, but they are addressable with rules and recipes.”

    When personalization becomes a laugh line, it’s because a team is overfitting: they aren’t designing with their best data. Like a sparse pantry, every organization has metadata debt to go along with its technical debt, and this creates a drag on personalization effectiveness. Your AI’s output quality, for example, is indeed limited by your IA. Spotify’s poster-child prowess today was unfathomable before they acquired a seemingly modest metadata startup that now powers its underlying information architecture.

    You can definitely stand the heat…

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

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

    While there are associated costs toward investing in this kind of technology and product design, your ability to size up and confront your unique situation and your digital capabilities is time well spent. Don’t squander it. The proof, as they say, is in the pudding.

  • User Research Is Storytelling

    User Research Is Storytelling

    I’ve been fascinated by shows since I was a child. I loved the heroes and the excitement—but most of all the reports. I aspired to be an artist. And I figured out that I would be able to embark on interesting activities in the same way that Indiana Jones did. I also dreamed up suggestions for videos that my friends and I could render and sun in. But they never advanced more. However, I did end up working in user experience ( UI). Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer research is story. And you must tell a compelling story to entice stakeholders, such as the product team and decision-makers, to learn more in order to get the most out of consumer research.

    Consider your preferred film. More than likely it follows a three-act construction that’s frequently seen in story: the layout, the fight, and the quality. The second act provides an overview of what is happening now, and it also serves as a primer for the heroes and the difficulties and issues they face. Act two sets the scene for the fight and the activity begins. Here, issues grow or get worse. The decision comes in the third and final action. This is where the problems are resolved and the figures grow and change. I believe that this architecture is also a great way to think about customer study, and I think that it can be particularly helpful in explaining person exploration to others.

    Use story as a framework when conducting research.

    Unfortunately, some people now believe that study is unprofitable. If finances or timelines are small, analysis tends to be one of the first points to go. Some goods managers rely on developers or, worse, their own judgment to make the “right” decisions for customers based on their experience or accepted best practices rather than investing in research. That may get groups a little bit out of the way, but that approach is therefore easily miss out on resolving people ‘ real issues. To be user-centered, this is something we really avoid. User study improves pattern. It keeps it on track by pointing out issues and prospects. Being aware of the issues with your goods and reacting to them can help you stay ahead of your competition.

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

    Act one: layout

    Fundamental analysis comes in handy because the layout is all about comprehending the background. Basic research ( also known as relational, discovery, or preliminary research ) assists in understanding users and identifying their issues. You’re learning about what exists now, the obstacles people have, and how the problems affect them—just like in the videos. You can conduct contextual inquiries or diary studies ( or both! ) to conduct foundational research. ), which may assist you in identifying both problems and opportunities. It doesn’t need to be a great investment in time or money.

    Erika Hall writes about the most effective anthropology, which can be as straightforward as spending 15 hours with a customer and asking them to” Walk me through your morning yesterday.” That’s it. Current that one ask. Opened up and spend fifteen days listening. Do everything in your power to keep yourself and your pursuits out of it. Bam, you’re doing ethnography”. Hall predicts that “[This ] will definitely prove quite fascinating. In the unlikely event that you don’t learn anything valuable or fresh, you can move forward with greater self-assurance.

    This makes total sense to me. And I adore how users research is now so simple. You can simply attract participants and carry out the recruitment process without having to create a lot of paperwork! This can offer a wealth of knowledge about your customers, and it’ll help you better understand them and what’s going on in their life. That’s what action one is really all about: understanding where people are coming from.

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

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

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

    Act two: conflict

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

    According to Jakob Nielsen, five users should be typically in usability tests, which means that this number of users can typically identify the majority of the issues:” As you add more and more users, you learn less and less because you will keep seeing the same things again and again… After the fifth user, you are wasting your time by observing the same findings repeatedly but not learning much new.”

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

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

    If conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may be very different from one another. You can conduct usability testing in the real world by creating a replica of the environment where users interact with the product and then conducting your research there. Or you can go out to meet users at their location to do your research. With either option, you can see how things work in context, how things change, and how conversion can change completely in different ways depending on the circumstances. You have less control over how these sessions run as researchers, but this can occasionally improve your understanding of users. Meeting users where they are can provide clues to the external forces that could be affecting how they use your product. In-person usability tests add a level of detail that remote usability tests frequently lack.

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

    You can ask real users questions to understand their thoughts and understanding of the solution as a result of usability testing, whether it is conducted remotely or in person. This can help you identify issues as well as understand why they were initially issues. Furthermore, you can test hypotheses and gauge whether your thinking is correct. By the end of the sessions, you’ll be able to see for yourself whether the designs are useful and effective. Act two is where the excitement is at the heart of the narrative, but there are also potential surprises. This is equally true of usability tests. Unexpected things that are said by participants frequently alter how you view things, and these unexpected developments in the story can lead to unexpected turns in your perception.

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

    On the other hand, if you only do foundational research, you won’t know whether the thing you’re building will actually solve that problem, despite the fact that you might have set out to solve the right problem. This illustrates the importance of doing both foundational and directional research.

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

    Act three: resolution

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

    This act is primarily told in voiceover with some audience participation. The researcher serves as the narrator, who depicts the issues and what the product’s potential future might look like in light of what the team has learned. They give the stakeholders their recommendations and their guidance on creating this vision.

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

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

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

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

      Act one: You encounter both the users ‘ protagonists and the antagonists ( the user-related issues ). This is the beginning of the plot. Researchers might employ techniques like contextual inquiry, ethnography, diary studies, surveys, and analytics in act one. These techniques can produce personas, empathy maps, user journeys, and analytics dashboards.
      Act two: Next, there’s character development. The protagonists encounter problems and difficulties, which they must overcome, and there is conflict and tension. Researchers might use heuristics evaluation, usability testing, competitive benchmarking, and other methods in act two. The output of these can include usability findings reports, UX strategy documents, usability guidelines, and best practices.
      Act three: The main characters win, and the audience is shown a better future. Researchers may use techniques like storytelling, presentation decks, and digital media in act three. The output of these can be: presentation decks, video clips, audio clips, and pictures.

    The researcher plays a variety of roles, including producer, director, and storyteller. Although the participants are only a small part in the study, they are significant characters. And the stakeholders are the audience. However, the most crucial thing is to get the narrative straight and to use storytelling to research users ‘ stories. By the end, the parties should leave with a goal and an eagerness to address the product’s flaws.

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

  • How Doctor Who Books Formed a Path to Writing the TV Show

    How Doctor Who Books Formed a Path to Writing the TV Show

    Between 1990 and 2005, when Doctor Who wasn’t on Television, the present generally existed as original works. Many of the show’s fresh writers were chosen from the authors of those spin-off books when Russell T. Davies, Julie Gardner, and Jane Tranter brought it back in 2005, including Davies and Steven Moffat, the show’s upcoming director. While they ]… ]

    The article How Doctor Who Books Formed a Journey to Writing the TV Show first appeared on Den of Geek.

    Dope Girls is not your grandmother’s historical play (unless, of program, your grandmother has lived a life, has good taste in television, and was, in fact, do with a little more respect and condescension from those who assume she won’t be able to see anything that Alan Titchmarsh doesn’t give a damn ).

    To try once therefore, Dope Girls is no Downton Abbey. Although it may be set during the same time period, this story of Soho girls dancing with danger, death, and other performers at bars where they work is a world away from the elegant machinations of the Earl of Grantham.

    With a solid including players from the US, Australia and the UK, how’s who’s playing who in BBC One’s fresh Saturday night line.

    cnx. command. push ( function ( ) {cnx ( {playerId:” 106e33c0-3911-473c-b599-b1426db57530″, }). render ( “0270c398a82f44f49c23c16122516796” ), }),

    Eliza Scanlen as Violet Davies

    Violet, a recent addition to the Metropolitan Police Service, is aiming to get chosen for the UK’s first female officer experiment,” The Adult Experiment” in which the first female officials were hired. She&#8217, s hard, only and has nothing to lose, which makes her a dangerous idea.

    She’s played by American actor Eliza Scanlen, whose breakthrough jobs came in HBO’s 2018 version of Gillian Flynn’s Sharp Objects, and in Greta Gerwig’s 2019 have video Little Women, in which Scanlen played second-to-youngest March girl Beth. She most recently appeared in the National Theatre production of The Importance of Being Earnest this year opposite Doctor Who‘s Ncuti Gatwa.

    Julianne Nicholson as Kate Galloway

    A brunette woman in a black coat in BBC One's Dope Girls

    After losing her job, Kate is cruelly forced to find her own way, and she must go to extreme lengths to support her and her teenage daughter Evie, a smart girl who has the potential to be one of the first women in the UK to study.

    Julianne Nicholson, a US actor, is currently seen as the wealthy Sinatra in the Disney/Hulu political thriller Paradise, which has just been renewed for a second season. She’s known for Law &amp, Order, The Outsider, having played Esther in Boardwalk Empire, Lillian in Masters of Sex and Lorri in the first season of Kate Winslet-starring crime drama Mare of Easttown.

    Umi Myers as Billie Cassidy

    Umi Meyers wearing a dress and fur coat in BBC One's Dope Girls

    With her singer friend Eddie Cobb, Billie lives a bohemian, drink- and drug-fuelled lifestyle in a Soho nightclub. Umi Myers, a recent graduate of the Guildhall School of Music and Drama, has previously appeared on stage and in Bob Marley: One Love. Myers ‘ first television lead role is Dope Girls.

    Geraldine James as Isabella Salucci

    Geraldine James in a blue dress in BBC One's Dope Girls

    Isabella, the matriarch of the feared Salucci crime family, is a ruthless survivor who&#8217, kept her clan together throughout the War and many more. Geraldine James, a well-known actor and actress who has a long and successful career dating back to the late 1970s, plays her. To some TV viewers, she’ll always be indivisible from the part of Sarah in The Jewel in the Crown, to others, she’ll be best recognised as Rose from Band of Gold, Milner in Channel 4’s Utopia, Mrs Hudson in the Guy Ritchie Sherlock Holmes films, and Marissa in Anne With an E, to name just a few.

    Dustin Demri-Burns as Damaso Salucci

    Dustin Demri-Burns wearing a dark suit in BBC One's Dope Girls

    Damaso, a Salucci son, has a terrifyingly brutal side and belongs to a powerful Soho crime family. He’s played by Dustin Demri-Burns, who’s well known for comedy roles in Cardinal Burns, Stath Lets Flats, GameFace and Am I Being Unreasonable?, but has an equally healthy career in dramas with a comedic edge from The Great to Slow Horses, Britannia, Sweetpea and The Decameron.

    Ian Bonar as Sgt Frank Turner

    A profile of Ian Bonar's face in BBC One's Dope Girls

    Sgt Turner is helping to run The Female Experiment, which saw the UK&#8217, s first female police officers. He&#8217, s a complicated man who does n&#8217, t wield his power well, and makes an early enemy of Violet. He’s played by Ian Bonar, who recently appeared opposite Peter Capaldi in Apple TV +’s Criminal Record, as well as roles across various TV genres, from I May Destroy You to New Blood, Vera and many more.

    Fiona Button as Sophie Asquith-Gore

    Fiona Button wearing a white and green dress in BBC One's Dope Girls

    Sophie, the wife of a wealthy and powerful government minister and Alice’s friend, is grieving her brother’s passing and believes she can still communicate with him via a medium. She’s played by actor-director Fiona Button, who’s known for the role of Rose Defoe in Abi Morgan’s legal drama The Split, and was recently seen as Denise in series three of Industry, as well as in Grantchester, Out of Her Mind, and plenty of theatre productions.

    Nabhaan Rizwan as Silas Huxley

    Nabhaan Rizwan in BBC One's Dope Girls

    Silus Huxley, a medium and occultist, extorts money from the wealthy to make contact with the dead. He’s played by Nabhaan Rizwan, who recently played Dionysus in Netflix’s KAOS, as well as appearing opposite his brother Mawaan Rizwan in his sitcom Juice, and in the US playing Frank in Station Eleven, after his breakout role in 2018’s BBC crime drama Informer.

    Will Keen as Frederick Asquith-Gore

    A powerful government minister who&#8217, s set on rooting out the rot in London &#8217, s seedy nightclubs, Frederick Asquith-Gore is played by screen and stage actor Will Keen ( incidentally, the father of Logan and His Dark Materials ‘ Dafne Keen ), who recently appeared in BBC drama Wolf Hall as Thomas Cranmer, as well as playing Lord Belzagar in the second season of Lord of the Rings: The Rings of Power, Norfolk in My Lady Jane, the Queen’s private secretary in The Crown, and David in Ridley Road, as well as appearing in feature film Operation Mincemeat and more.

    ALSO APPEARING

    A man holding two fans in BBC One's Dope Girls

    Michael Duke, a musical stage and screen actor, portrays Eddie Cobb as a club singer.
    The Outrun and The Power‘s Eilidh Fisher as Kate’s daughter Evie Galloway.
    The Bay, The Reckoning, True Detective and Strike‘s Eloise Thomas as Evie’s schoolfriend Alice Asquith-Gore.
    The Sixth Commandment‘s, Ghosts‘ and Lead Balloon‘s Anna Crilly as butcher Anne Sanders.
    Bridgerton and The Bastard Son and the Devil Himself‘s Priya Kansara as nightclub dancer Lily Lee.
    Heartstopper‘s Ben Hope, aka Sebastian Croft as nightclub owner Silvio Salucci.
    The Newsreader and The Inheritance‘s Rory Fleck Byrne as returned soldier Luca Salucci.

    Dope Girls is available on BBC One and available on BBC iPlayer.

    The post Dope Girls Cast: Meet the 1920s-Set BBC Drama&#8217, s Characters appeared first on Den of Geek.

  • A Thousand Blows Ending Explained: What Next For Hezekiah, Mary & Sugar in Series 2?

    A Thousand Blows Ending Explained: What Next For Hezekiah, Mary & Sugar in Series 2?

    Warning: contains tournament clues for A Thousand Knocks. ” To been continued …” reads the message at the end of A Thousand Blows line one, and alas for viewers, it isn’t followed by a question mark. Two six-episode series of Steven Knight’s historical drama were filmed back-to-back, which means that a second run is guaranteed to arrive ]… ]

    The blog A Thousand Blows Ending Explained: What Next For Hezekiah, Mary &amp, Sugar in Series 2? second appeared on Den of Geek.

    Dope Women is not your grandmother’s historical drama (unless, of course, your grandmother has lived a existence, has good taste in television, and could, in fact, do with a little more value and a little less disdain from those who assume she won’t be able to see anything that isn’t presented by Alan Titchmarsh ).

    To try once therefore, Dope Girls is no Downton Abbey. Although it may be set during the same time period, this story of Soho girls dancing with danger, death, and other dancing at bars where they work is far from the Earl of Grantham’s gentrifying intrigues.

    With a solid including players from the US, Australia and the UK, how’s who’s playing who in BBC One’s fresh Saturday night line.

    cnx. powershell. push ( function ( ) {cnx ( {playerId:” 106e33c0-3911-473c-b599-b1426db57530″, }). render ( “0270c398a82f44f49c23c16122516796” ), }),

    Eliza Scanlen as Violet Davies

    Violet, a newcomer to the Metropolitan police company, is aiming to be chosen for the film series” The Female Experiment” in which first female officials were hired in the UK. She&#8217, s hard, only and has nothing to lose, which makes her a dangerous idea.

    She’s played by American actor Eliza Scanlen, whose breakthrough jobs came in HBO’s 2018 version of Gillian Flynn’s Sharp Objects, and in Greta Gerwig’s 2019 have video Little Women, in which Scanlen played second-to-youngest March girl Beth. Ncuti Gatwa from Doctor Who recently starred in this year’s National Theatre generation of The Importance of Being Earnest.

    Julianne Nicholson as Kate Galloway

    A brunette woman in a black coat in BBC One's Dope Girls

    After losing her work, Kate is ruthlessly forced to find her own way, and she must go to extraordinary lengths to support her and her young daughter Evie, a smart woman who has the potential to be one of the first women in the UK to study.

    Julianne Nicholson, a US actor, is currently seen as the wealthy Sinatra in the Disney/Hulu political thriller Paradise ( which has just been renewed for a second season ). She’s known for Law &amp, Order, The Outsider, having played Esther in Boardwalk Empire, Lillian in Masters of Sex and Lorri in the first season of Kate Winslet-starring crime drama Mare of Easttown.

    Umi Myers as Billie Cassidy

    Umi Meyers wearing a dress and fur coat in BBC One's Dope Girls

    Billie is a Soho nightclub dancer who lives a bohemian, drink- and drug-fuelled lifestyle with her friend Eddie Cobb, a singer. Umi Myers, a recent graduate of the Guildhall School of Music and Drama, has previously appeared on stage and in Bob Marley: One Love. Myers ‘ first television lead role was in Dope Girls.

    Geraldine James as Isabella Salucci

    Geraldine James in a blue dress in BBC One's Dope Girls

    Isabella, the matriarch of the feared Salucci crime family, is a ruthless survivor who, through the War and many other things, has kept her clan together. Geraldine James, a well-known actor and actress who has a long and successful career dating back to the late 1970s, plays her. To some TV viewers, she’ll always be indivisible from the part of Sarah in The Jewel in the Crown, to others, she’ll be best recognised as Rose from Band of Gold, Milner in Channel 4’s Utopia, Mrs Hudson in the Guy Ritchie Sherlock Holmes films, and Marissa in Anne With an E, to name just a few.

    Dustin Demri-Burns as Damaso Salucci

    Dustin Demri-Burns wearing a dark suit in BBC One's Dope Girls

    Damaso, a Salucci son, belongs to a powerful Soho crime family and has a terrifyingly brutal side. He’s played by Dustin Demri-Burns, who’s well known for comedy roles in Cardinal Burns, Stath Lets Flats, GameFace and Am I Being Unreasonable?, but has an equally healthy career in dramas with a comedic edge from The Great to Slow Horses, Britannia, Sweetpea and The Decameron.

    Ian Bonar as Sgt Frank Turner

    A profile of Ian Bonar's face in BBC One's Dope Girls

    Sgt Turner is helping to run The Female Experiment, which saw the UK&#8217, s first female police officers. He&#8217, s a complicated man who does n&#8217, t wield his power well, and makes an early enemy of Violet. He’s played by Ian Bonar, who recently appeared opposite Peter Capaldi in Apple TV +’s Criminal Record, as well as roles across various TV genres, from I May Destroy You to New Blood, Vera and many more.

    Fiona Button as Sophie Asquith-Gore

    Fiona Button wearing a white and green dress in BBC One's Dope Girls

    Sophie, the wife of a wealthy and powerful government minister and the mother of Evie&#8217’s friend Alice, grieves her brother and believes she can still speak to him via a medium. She’s played by actor-director Fiona Button, who’s known for the role of Rose Defoe in Abi Morgan’s legal drama The Split, and was recently seen as Denise in series three of Industry, as well as in Grantchester, Out of Her Mind, and plenty of theatre productions.

    Nabhaan Rizwan as Silas Huxley

    Nabhaan Rizwan in BBC One's Dope Girls

    Silus Huxley, a medium and occultist, extorts money from the wealthy to make contact with the dead. He’s played by Nabhaan Rizwan, who recently played Dionysus in Netflix’s KAOS, as well as appearing opposite his brother Mawaan Rizwan in his sitcom Juice, and in the US playing Frank in Station Eleven, after his breakout role in 2018’s BBC crime drama Informer.

    Will Keen as Frederick Asquith-Gore

    A powerful government minister who&#8217, s set on rooting out the rot in London &#8217, s seedy nightclubs, Frederick Asquith-Gore is played by screen and stage actor Will Keen ( incidentally, the father of Logan and His Dark Materials ‘ Dafne Keen ), who recently appeared in BBC drama Wolf Hall as Thomas Cranmer, as well as playing Lord Belzagar in the second season of Lord of the Rings: The Rings of Power, Norfolk in My Lady Jane, the Queen’s private secretary in The Crown, and David in Ridley Road, as well as appearing in feature film Operation Mincemeat and more.

    ALSO APPEARING

    A man holding two fans in BBC One's Dope Girls

    Michael Duke, a musical stage and screen actor, portrays Eddie Cobb as a club singer.
    The Outrun and The Power‘s Eilidh Fisher as Kate’s daughter Evie Galloway.
    The Bay, The Reckoning, True Detective and Strike‘s Eloise Thomas as Evie’s schoolfriend Alice Asquith-Gore.
    The Sixth Commandment‘s, Ghosts‘ and Lead Balloon‘s Anna Crilly as butcher Anne Sanders.
    Bridgerton and The Bastard Son and the Devil Himself‘s Priya Kansara as nightclub dancer Lily Lee.
    Heartstopper‘s Ben Hope, aka Sebastian Croft as nightclub owner Silvio Salucci.
    The Newsreader and The Inheritance‘s Rory Fleck Byrne as returned soldier Luca Salucci.

    Dope Girls is available on BBC One and BBC iPlayer.

    The post Dope Girls Cast: Meet the 1920s-Set BBC Drama&#8217, s Characters appeared first on Den of Geek.

  • Beware the Cut ‘n’ Paste Persona

    Beware the Cut ‘n’ Paste Persona

    This Person Does Not Exist is a website that uses a machine learning algorithm to create individual faces. It takes actual photos and recombines them into false people faces. We just squirted past a LinkedIn article that claimed this site might be helpful “if you are developing a image and looking for a photo.”

    We concur that personas could be 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 an isolated preview that is detached from reality and taken out of the normal context.

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

    A step up, identities

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

    The decontextualization of identities

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

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

    People are assumed to be dynamic, according to people.

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

    Modern psychology agree that while persons usually behave according to certain styles, it’s actually a combination of history and culture that determines how people act and take decisions. The type of person you are in each particular moment depends on the context, the impact of other people, your mood, and the whole history that led to the situation.

    Personas provide a consumer as a predetermined set of features in an effort to improve reality, but do so without taking this variability into account. Like character tests, personas seize people away from real life. Even worse, individuals are labeled as” that kind of guy” with no means to practice their innate flexibility and are reduced to a brand. This behavior discredits variety, perpetuates stereotypes, and doesn’t reveal reality.

    Personas rely on people, not the environment

    In the real world, you’re creating content for a situation, no an entity. There are economic, political, and social factors to consider when a man lives in a home, a community, or an ecosystem. A pattern is not meant for a single customer. Instead, you create a layout for one or more specific situations where a certain product might be used by a large number of people. However, personal experiences don’t explicitly explain how a person feels about the surroundings. Instead, they show the user only.

    Do you generally make the same decision over and over again? Possibly you’ve made a commitment to veganism but still want to get some meat when your family visit. Your decisions, including your behavior, opinions, and statements, are not absolute but greatly contextual because they depend on various circumstances and factors. The image that “represents” you wouldn’t take into account this interdependence, because it doesn’t explain the grounds of your choices. It doesn’t give a rationale for your behavior. People practice the well-known attribution error, which states that they too often attribute others ‘ behavior to their personalities and not to the circumstances.

    As mentioned by the Interaction Design Foundation, identities are often placed in a situation that’s a” specific environment with a problem they want to or have to solve “—does that mean environment actually is considered? Unfortunately, it’s common to pick a fictional character and build a character’s behavior around a particular circumstance based on the fiction. How could you possibly understand how someone you want to represent behave in new circumstances if you hadn’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 in Shlomo Goltz’s introduction to Smashing Magazine, according to Shlomo Goltz’s introduction article. It is instead made up of observations from numerous people. The famous USA Air Force design planes were designed based on the average of 140 of their pilots ‘ physical dimensions, with not a single pilot actually fit within that average seat, is a well-known criticism of this aspect of personas.

    The same limitation applies to mental aspects of people. Have you ever heard a famous person say something was taken out of context? I didn’t mean it that way when they used my words. The celebrity’s statement was reported literally, but the reporter failed to explain the context around the statement and didn’t describe the non-verbal expressions. The intended purpose was lost as a result. You collect someone’s statement ( or goal, need, or emotion ) into which its meaning can only be understood if it is provided with its own specific context, and then report it as an isolated finding.

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

    The validity of personas 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 explains the absurdity of this than the Interaction Design Foundation’s phrase,” 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 if you purposefully conceal the fact that” John Doe” is an abstract representation of research findings? Let’s say something is artificial, and let’s say it is.

    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 suggests, as designers, we can” contextualize]the persona” based on our experience and reality. 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 of using 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 life. Unfortunately, despite being a step in the right direction, this proposal disregards the fact that people are a part of a system that controls their behavior, personality, and mindset. Therefore, Mindsets are also not absolute but change in regard to the situation. What determines a certain Mindset, remains to be seen.

    Margaret P., the author of the article” Kill Your Personas,” who has argued for the use of persona spectrums that include a range of user abilities, offers an alternative. For example, a visual impairment could be permanent ( blindness ), temporary ( recovery from eye surgery ), or situational (screen glare ). 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. Similar to how we tried to do this before with people, contexts are generalizable and have patterns that we can identify. How do we find these patterns, then? How do we ensure truly context-based design?

    Understand real people in a variety of contexts

    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. Dynamic Selves is how we define it.

    Let’s take a look at how the approach looks based on an illustration of how one of us used it in a recent study that examined Italians ‘ habits around energy consumption. We drafted a design research plan aimed at investigating people’s attitudes toward energy consumption and sustainable behavior, with a focus on smart thermostats.

    1. Select the appropriate sample.

    When we argue against personas, we’re often challenged with quotes such as” Where are you going to find a single person that encapsulates all the information from one of these advanced personas]? ]” The simple answer is that you are not required to. Your insights need not be extensive and meaningful, as you don’t need to know much about everyone.

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

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

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

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

    In our example project, we were designing an application for those who own a smart thermostat. Everyone in their home could have a smart thermostat in the future. However, only early adopters currently own one. To build a significant sample, we needed to understand the reason why these early adopters became such. We then recruited by enticing people to explain why and how they obtained a smart thermostat. There were those who had made the decision to purchase it, those who had been influenced by others to do so, and those who had located it in their homes. So we selected representatives of these three situations, from different age groups and geographical locations, with an equal balance of tech savvy and non-tech savvy participants.

    2. Conduct your research

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

    To gain an in-depth understanding of attitudes and decision-making trade-offs, the research focus was not limited to the interviewee alone but deliberately included the whole family. Each interviewee would provide a story that would later become much more interesting and precise with the additions made by their spouses, partners, kids, or occasionally even pets. We also paid attention to the behaviors that came from having relationships with other important people ( such as coworkers or distant relatives ), as well as the relationships that came 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. The most insightful findings will be made with this open-minded “plan to be surprised.” One of our participants responded,” My wife has not installed the thermostat’s app; she uses WhatsApp instead,” when we asked how his family controlled the house temperature. 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 key demographics were family type, number and type of homes owned, economic status, and technological maturity in our case because our research focused on families and their way of life to understand their needs for thermal regulation. The individuals ‘ names and ages are optional, but they were included to facilitate 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 several cards about themselves.

    4. Identify creative uses

    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.

    A particularly intriguing finding was made in our example project regarding the concept of humidity. We became aware of the importance of monitoring humidity for health and how a climate that is too dry or wet can cause respiratory problems or worsen already existing ones. This highlighted a big opportunity for our client to educate users on this concept and become a health advisor.

    Benefits of Dynamic Selves

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

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

    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 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. This is exactly how this person lives out. 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 significant benefit of the Dynamic Selves approach is that it raises the stakes of your work: if you ruin your design, someone you and the team know and have met will suffer the consequences. 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. In order to obtain this result, documentation of real research is necessary. It reinforces your design arguments by adding more weight and urgency:” When I met Alessandra, the conditions of her workplace struck me. Noise, bad ergonomics, lack of light, you name it. I’m worried that her life will become more complicated if we choose to use this functionality.

    Conclusion

    In their article on Mindsets, Designit mentioned that “design thinking tools 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, not necessarily generalized. You have to look at the research elements that stand out: the sentences that captured your attention, the images that struck you, the sounds that linger. Use those to characterize the person in all of their contexts, and portray them. People and insights are subject to a context, but they cannot be removed because it would detract from the context’s meaning.

    It’s high time for design to move away from fiction, and embrace reality—in its messy, surprising, and unquantifiable beauty—as our guide and inspiration.

  • That’s Not My Burnout

    That’s Not My Burnout

    Are you like me, reading about people fading away as they burn out, and feeling unable to relate? Do you feel like your feelings are invisible to the world because you’re experiencing burnout differently? When burnout starts to push down on us, our core comes through more. Beautiful, peaceful souls get quieter and fade into that distant and distracted burnout we’ve all read about. But some of us, those with fires always burning on the edges of our core, get hotter. In my heart I am fire. When I face burnout I double down, triple down, burning hotter and hotter to try to best the challenge. I don’t fade—I am engulfed in a zealous burnout

    So what on earth is a zealous burnout?

    Imagine a woman determined to do it all. She has two amazing children whom she, along with her husband who is also working remotely, is homeschooling during a pandemic. She has a demanding client load at work—all of whom she loves. She gets up early to get some movement in (or often catch up on work), does dinner prep as the kids are eating breakfast, and gets to work while positioning herself near “fourth grade” to listen in as she juggles clients, tasks, and budgets. Sound like a lot? Even with a supportive team both at home and at work, it is. 

    Sounds like this woman has too much on her plate and needs self-care. But no, she doesn’t have time for that. In fact, she starts to feel like she’s dropping balls. Not accomplishing enough. There’s not enough of her to be here and there; she is trying to divide her mind in two all the time, all day, every day. She starts to doubt herself. And as those feelings creep in more and more, her internal narrative becomes more and more critical.

    Suddenly she KNOWS what she needs to do! She should DO MORE. 

    This is a hard and dangerous cycle. Know why? Because once she doesn’t finish that new goal, that narrative will get worse. Suddenly she’s failing. She isn’t doing enough. SHE is not enough. She might fail, she might fail her family…so she’ll find more she should do. She doesn’t sleep as much, move as much, all in the efforts to do more. Caught in this cycle of trying to prove herself to herself, never reaching any goal. Never feeling “enough.” 

    So, yeah, that’s what zealous burnout looks like for me. It doesn’t happen overnight in some grand gesture but instead slowly builds over weeks and months. My burning out process looks like speeding up, not a person losing focus. I speed up and up and up…and then I just stop.

    I am the one who could

    It’s funny the things that shape us. Through the lens of childhood, I viewed the fears, struggles, and sacrifices of someone who had to make it all work without having enough. I was lucky that my mother was so resourceful and my father supportive; I never went without and even got an extra here or there. 

    Growing up, I did not feel shame when my mother paid with food stamps; in fact, I’d have likely taken on any debate on the topic, verbally eviscerating anyone who dared to criticize the disabled woman trying to make sure all our needs were met with so little. As a child, I watched the way the fear of not making those ends meet impacted people I love. As the non-disabled person in my home, I would take on many of the physical tasks because I was “the one who could” make our lives a little easier. I learned early to associate fears or uncertainty with putting more of myself into it—I am the one who can. I learned early that when something frightens me, I can double down and work harder to make it better. I can own the challenge. When people have seen this in me as an adult, I’ve been told I seem fearless, but make no mistake, I’m not. If I seem fearless, it’s because this behavior was forged from other people’s fears. 

    And here I am, more than 30 years later still feeling the urge to mindlessly push myself forward when faced with overwhelming tasks ahead of me, assuming that I am the one who can and therefore should. I find myself driven to prove that I can make things happen if I work longer hours, take on more responsibility, and do more

    I do not see people who struggle financially as failures, because I have seen how strong that tide can be—it pulls you along the way. I truly get that I have been privileged to be able to avoid many of the challenges that were present in my youth. That said, I am still “the one who can” who feels she should, so if I were faced with not having enough to make ends meet for my own family, I would see myself as having failed. Though I am supported and educated, most of this is due to good fortune. I will, however, allow myself the arrogance of saying I have been careful with my choices to have encouraged that luck. My identity stems from the idea that I am “the one who can” so therefore feel obligated to do the most. I can choose to stop, and with some quite literal cold water splashed in my face, I’ve made the choice to before. But that choosing to stop is not my go-to; I move forward, driven by a fear that is so a part of me that I barely notice it’s there until I’m feeling utterly worn away.

    So why all the history? You see, burnout is a fickle thing. I have heard and read a lot about burnout over the years. Burnout is real. Especially now, with COVID, many of us are balancing more than we ever have before—all at once! It’s hard, and the procrastinating, the avoidance, the shutting down impacts so many amazing professionals. There are important articles that relate to what I imagine must be the majority of people out there, but not me. That’s not what my burnout looks like.

    The dangerous invisibility of zealous burnout

    A lot of work environments see the extra hours, extra effort, and overall focused commitment as an asset (and sometimes that’s all it is). They see someone trying to rise to challenges, not someone stuck in their fear. Many well-meaning organizations have safeguards in place to protect their teams from burnout. But in cases like this, those alarms are not always tripped, and then when the inevitable stop comes, some members of the organization feel surprised and disappointed. And sometimes maybe even betrayed. 

    Parents—more so mothers, statistically speaking—are praised as being so on top of it all when they can work, be involved in the after-school activities, practice self-care in the form of diet and exercise, and still meet friends for coffee or wine. During COVID many of us have binged countless streaming episodes showing how it’s so hard for the female protagonist, but she is strong and funny and can do it. It’s a “very special episode” when she breaks down, cries in the bathroom, woefully admits she needs help, and just stops for a bit. Truth is, countless people are hiding their tears or are doom-scrolling to escape. We know that the media is a lie to amuse us, but often the perception that it’s what we should strive for has penetrated much of society.

    Women and burnout

    I love men. And though I don’t love every man (heads up, I don’t love every woman or nonbinary person either), I think there is a beautiful spectrum of individuals who represent that particular binary gender. 

    That said, women are still more often at risk of burnout than their male counterparts, especially in these COVID stressed times. Mothers in the workplace feel the pressure to do all the “mom” things while giving 110%. Mothers not in the workplace feel they need to do more to “justify” their lack of traditional employment. Women who are not mothers often feel the need to do even more because they don’t have that extra pressure at home. It’s vicious and systemic and so a part of our culture that we’re often not even aware of the enormity of the pressures we put on ourselves and each other. 

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

    This relationship between work stress and health, from what I have read, is more dangerous for women than it is for their non-female counterparts.

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

    That might not be you either. After all, each of us is so different and how we respond to stressors is too. It’s part of what makes us human. Don’t stress what burnout looks like, just learn to recognize it in yourself. Here are a few questions I sometimes ask friends if I am concerned about them.

    Are you happy? This simple question should be the first thing you ask yourself. Chances are, even if you’re burning out doing all the things you love, as you approach burnout you’ll just stop taking as much joy from it all.

    Do you feel empowered to say no? I have observed in myself and others that when someone is burning out, they no longer feel they can say no to things. Even those who don’t “speed up” feel pressure to say yes to not disappoint the people around them.

    What are three things you’ve done for yourself? Another observance is that we all tend to stop doing things for ourselves. Anything from skipping showers and eating poorly to avoiding talking to friends. These can be red flags. 

    Are you making excuses? Many of us try to disregard feelings of burnout. Over and over I have heard, “It’s just crunch time,” “As soon as I do this one thing, it will all be better,” and “Well I should be able to handle this, so I’ll figure it out.” And it might really be crunch time, a single goal, and/or a skill set you need to learn. That happens—life happens. BUT if this doesn’t stop, be honest with yourself. If you’ve worked more 50-hour weeks since January than not, maybe it’s not crunch time—maybe it’s a bad situation that you’re burning out from.

    Do you have a plan to stop feeling this way? If something is truly temporary and you do need to just push through, then it has an exit route with a
    defined end.

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

    So now what?

    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 healthy.
    • Work out.
    • Get outside.
    • Take a break.
    • Overall, practice self-care.

    Those are hard for me because they feel like more tasks. If I’m in the burnout cycle, doing any of the above for me feels like a waste. The narrative is that if I’m already failing, why would I take care of myself when I’m dropping all those other balls? People need me, right? 

    If you’re deep in the cycle, your inner voice might be pretty awful by now. If you need to, tell yourself you need to take care of the person your people depend on. If your roles are pushing you toward burnout, use them to help make healing easier by justifying the time spent working on you. 

    To help remind myself of the airline attendant message about putting the mask on yourself first, I have come up with a few things that I do when I start feeling myself going into a zealous burnout.

    Cook an elaborate meal for someone! 

    OK, I am a “food-focused” individual so cooking for someone is always my go-to. There are countless tales in my home of someone walking into the kitchen and turning right around and walking out when they noticed I was “chopping angrily.” But it’s more than that, and you should give it a try. Seriously. It’s the perfect go-to if you don’t feel worthy of taking time for yourself—do it for someone else. Most of us work in a digital world, so cooking can fill all of your senses and force you to be in the moment with all the ways you perceive the world. It can break you out of your head and help you gain a better perspective. In my house, I’ve been known to pick a place on the map and cook food that comes from wherever that is (thank you, Pinterest). I love cooking Indian food, as the smells are warm, the bread needs just enough kneading to keep my hands busy, and the process takes real attention for me because it’s not what I was brought up making. And in the end, we all win!

    Vent like a foul-mouthed fool

    Be careful with this one! 

    I have been making an effort to practice more gratitude over the past few years, and I recognize the true benefits of that. That said, sometimes you just gotta let it all out—even the ugly. Hell, I’m a big fan of not sugarcoating our lives, and that sometimes means that to get past the big pile of poop, you’re gonna wanna complain about it a bit. 

    When that is what’s needed, turn to a trusted friend and allow yourself some pure verbal diarrhea, saying all the things that are bothering you. You need to trust this friend not to judge, to see your pain, and, most importantly, to tell you to remove your cranium from your own rectal cavity. Seriously, it’s about getting a reality check here! One of the things I admire the most about my husband (though often after the fact) is his ability to break things down to their simplest. “We’re spending our lives together, of course you’re going to disappoint me from time to time, so get over it” has been his way of speaking his dedication, love, and acceptance of me—and I could not be more grateful. It also, of course, has meant that I needed to remove my head from that rectal cavity. So, again, usually those moments are appreciated in hindsight.

    Pick up a book! 

    There are many books out there that aren’t so much self-help as they are people just like you sharing their stories and how they’ve come to find greater balance. Maybe you’ll find something that speaks to you. Titles that have stood out to me include:

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

    Or, another tactic I love to employ is to read or listen to a book that has NOTHING to do with my work-life balance. I’ve read the following books and found they helped balance me out because my mind was pondering their interesting topics instead of running in circles:

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

    If you’re not into reading, pick up a topic on YouTube or choose a podcast to subscribe to. I’ve watched countless permaculture and gardening topics in addition to how to raise chickens and ducks. For the record, I do not have a particularly large food garden, nor do I own livestock of any kind…yet. I just find the topic interesting, and it has nothing to do with any aspect of my life that needs anything from me.

    Forgive yourself 

    You are never going to be perfect—hell, it would be boring if you were. It’s OK to be broken and flawed. It’s human to be tired and sad and worried. It’s OK to not do it all. It’s scary to be imperfect, but you cannot be brave if nothing were scary.

    This last one is the most important: allow yourself permission to NOT do it all. You never promised to be everything to everyone at all times. We are more powerful than the fears that drive us. 

    This is hard. It is hard for me. It’s what’s driven me to write this—that it’s OK to stop. It’s OK that your unhealthy habit that might even benefit those around you needs to end. You can still be successful in life.

    I recently read that we are all writing our eulogy in how we live. Knowing that your professional accomplishments won’t be mentioned in that speech, what will yours say? What do you want it to say? 

    Look, I get that none of these ideas will “fix it,” and that’s not their purpose. None of us are in control of our surroundings, only how we respond to them. These suggestions are to help stop the spiral effect so that you are empowered to address the underlying issues and choose your response. They are things that work for me most of the time. Maybe they’ll work for you.

    Does this sound familiar? 

    If this sounds familiar, it’s not just you. Don’t let your negative self-talk tell you that you “even burn out wrong.” It’s not wrong. Even if rooted in fear like my own drivers, I believe that this need to do more comes from a place of love, determination, motivation, and other wonderful attributes that make you the amazing person you are. We’re going to be OK, ya know. The lives that unfold before us might never look like that story in our head—that idea of “perfect” or “done” we’re looking for, but that’s OK. Really, when we stop and look around, usually the only eyes that judge us are in the mirror. 

    Do you remember that Winnie the Pooh sketch that had Pooh eat so much at Rabbit’s house that his buttocks couldn’t fit through the door? Well, I already associate a lot with Rabbit, so it came as no surprise when he abruptly declared that this was unacceptable. But do you recall what happened next? He put a shelf across poor Pooh’s ankles and decorations on his back, and made the best of the big butt in his kitchen. 

    At the end of the day we are resourceful and know that we are able to push ourselves if we need to—even when we are tired to our core or have a big butt of fluff ‘n’ stuff in our room. None of us has to be afraid, as we can manage any obstacle put in front of us. And maybe that means we will need to redefine success to allow space for being uncomfortably human, but that doesn’t really sound so bad either. 

    So, wherever you are right now, please breathe. Do what you need to do to get out of your head. Forgive and take care.

  • Asynchronous Design Critique: Giving Feedback

    Asynchronous Design Critique: Giving Feedback

    Feedback, in whichever form it takes, and whatever it may be called, is one of the most effective soft skills that we have at our disposal to collaboratively get our designs to a better place while growing our own skills and perspectives.

    Feedback is also one of the most underestimated tools, and often by assuming that we’re already good at it, we settle, forgetting that it’s a skill that can be trained, grown, and improved. Poor feedback can create confusion in projects, bring down morale, and affect trust and team collaboration over the long term. Quality feedback can be a transformative force. 

    Practicing our skills is surely a good way to improve, but the learning gets even faster when it’s paired with a good foundation that channels and focuses the practice. What are some foundational aspects of giving good feedback? And how can feedback be adjusted for remote and distributed work environments? 

    On the web, we can identify a long tradition of asynchronous feedback: from the early days of open source, code was shared and discussed on mailing lists. Today, developers engage on pull requests, designers comment in their favorite design tools, project managers and scrum masters exchange ideas on tickets, and so on.

    Design critique is often the name used for a type of feedback that’s provided to make our work better, collaboratively. So it shares a lot of the principles with feedback in general, but it also has some differences.

    The content

    The foundation of every good critique is the feedback’s content, so that’s where we need to start. There are many models that you can use to shape your content. The one that I personally like best—because it’s clear and actionable—is this one from Lara Hogan.

    While this equation is generally used to give feedback to people, it also fits really well in a design critique because it ultimately answers some of the core questions that we work on: What? Where? Why? How? Imagine that you’re giving some feedback about some design work that spans multiple screens, like an onboarding flow: there are some pages shown, a flow blueprint, and an outline of the decisions made. You spot something that could be improved. If you keep the three elements of the equation in mind, you’ll have a mental model that can help you be more precise and effective.

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

    Not sure about the buttons’ styles and hierarchy—it feels off. Can you change them?

    Observation for design feedback doesn’t just mean pointing out which part of the interface your feedback refers to, but it also refers to offering a perspective that’s as specific as possible. Are you providing the user’s perspective? Your expert perspective? A business perspective? The project manager’s perspective? A first-time user’s perspective?

    When I see these two buttons, I expect one to go forward and one to go back.

    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.

    When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow.

    The question approach is meant to provide open guidance by eliciting the critical thinking in the designer receiving the feedback. Notably, in Lara’s equation she provides a second approach: request, which instead provides guidance toward a specific solution. While that’s a viable option for feedback in general, for design critiques, in my experience, defaulting to the question approach usually reaches the best solutions because designers are generally more comfortable in being given an open space to explore.

    The difference between the two can be exemplified with, for the question approach:

    When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Would it make sense to unify them?

    Or, for the request approach:

    When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same pair of forward and back buttons.

    At this point in some situations, it might be useful to integrate with an extra why: why you consider the given suggestion to be better.

    When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.

    Choosing the question approach or the request approach can also at times be a matter of personal preference. A while ago, I was putting a lot of effort into improving my feedback: I did rounds of anonymous feedback, and I reviewed feedback with other people. After a few rounds of this work and a year later, I got a positive response: my feedback came across as effective and grounded. Until I changed teams. To my shock, my next round of feedback from one specific person wasn’t that great. The reason is that I had previously tried not to be prescriptive in my advice—because the people who I was previously working with preferred the open-ended question format over the request style of suggestions. But now in this other team, there was one person who instead preferred specific guidance. So I adapted my feedback for them to include requests.

    One comment that I heard come up a few times is that this kind of feedback is quite long, and it doesn’t seem very efficient. No… but also yes. Let’s explore both sides.

    No, this style of feedback is actually efficient because the length here is a byproduct of clarity, and spending time giving this kind of feedback can provide exactly enough information for a good fix. Also if we zoom out, it can reduce future back-and-forth conversations and misunderstandings, improving the overall efficiency and effectiveness of collaboration beyond the single comment. Imagine that in the example above the feedback were instead just, “Let’s make sure that all screens have the same two forward and back buttons.” The designer receiving this feedback wouldn’t have much to go by, so they might just apply the change. In later iterations, the interface might change or they might introduce new features—and maybe that change might not make sense anymore. Without the why, the designer might imagine that the change is about consistency… but what if it wasn’t? So there could now be an underlying concern that changing the buttons would be perceived as a regression.

    Yes, this style of feedback is not always efficient because the points in some comments don’t always need to be exhaustive, sometimes because certain changes may be obvious (“The font used doesn’t follow our guidelines”) and sometimes because the team may have a lot of internal knowledge such that some of the whys may be implied.

    So the equation above isn’t meant to suggest a strict template for feedback but a mnemonic to reflect and improve the practice. Even after years of active work on my critiques, I still from time to time go back to this formula and reflect on whether what I just wrote is effective.

    The tone

    Well-grounded content is the foundation of feedback, but that’s not really enough. The soft skills of the person who’s providing the critique can multiply the likelihood that the feedback will be well received and understood. Tone alone can make the difference between content that’s rejected or welcomed, and it’s been demonstrated that only positive feedback creates sustained change in people.

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

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

    Timing refers to when the feedback happens. To-the-point feedback doesn’t have much hope of being well received if it’s given at the wrong time. Questioning the entire high-level information architecture of a new feature when it’s about to ship might still be relevant if that questioning highlights a major blocker that nobody saw, but it’s way more likely that those concerns will have to wait for a later rework. So in general, attune your feedback to the stage of the project. Early iteration? Late iteration? Polishing work in progress? These all have different needs. The right timing will make it more likely that your feedback will be well received.

    Attitude is the equivalent of intent, and in the context of person-to-person feedback, it can be referred to as radical candor. That means checking before we write to see whether what we have in mind will truly help the person and make the project better overall. This might be a hard reflection at times because maybe we don’t want to admit that we don’t really appreciate that person. Hopefully that’s not the case, but that can happen, and that’s okay. Acknowledging and owning that can help you make up for that: how would I write if I really cared about them? How can I avoid being passive aggressive? How can I be more constructive?

    Form is relevant especially in a diverse and cross-cultural work environments because having great content, perfect timing, and the right attitude might not come across if the way that we write creates misunderstandings. There might be many reasons for this: sometimes certain words might trigger specific reactions; sometimes nonnative speakers might not understand all the nuances of some sentences; sometimes our brains might just be different and we might perceive the world differently—neurodiversity must be taken into consideration. Whatever the reason, it’s important to review not just what we write but how.

    A few years back, I was asking for some feedback on how I give feedback. I received some good advice but also a comment that surprised me. They pointed out that when I wrote “Oh, […],” I made them feel stupid. That wasn’t my intent! I felt really bad, and I just realized that I provided feedback to them for months, and every time I might have made them feel stupid. I was horrified… but also thankful. I made a quick fix: I added “oh” in my list of replaced words (your choice between: macOS’s text replacement, aText, TextExpander, or others) so that when I typed “oh,” it was instantly deleted. 

    Something to highlight because it’s quite frequent—especially in teams that have a strong group spirit—is that people tend to beat around the bush. It’s important to remember here that a positive attitude doesn’t mean going light on the feedback—it just means that even when you provide hard, difficult, or challenging feedback, you do so in a way that’s respectful and constructive. The nicest thing that you can do for someone is to help them grow.

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

    The format

    Asynchronous feedback also has a major inherent advantage: we can take more time to refine what we’ve written to make sure that it fulfills two main goals: the clarity of communication and the actionability of the suggestions.

    Let’s imagine that someone shared a design iteration for a project. You are reviewing it and leaving a comment. There are many ways to do this, and of course context matters, but let’s try to think about some elements that may be useful to consider.

    In terms of clarity, start by grounding the critique that you’re about to give by providing context. Specifically, this means describing where you’re coming from: do you have a deep knowledge of the project, or is this the first time that you’re seeing it? Are you coming from a high-level perspective, or are you figuring out the details? Are there regressions? Which user’s perspective are you taking when providing your feedback? Is the design iteration at a point where it would be okay to ship this, or are there major things that need to be addressed first?

    Providing context is helpful even if you’re sharing feedback within a team that already has some information on the project. And context is absolutely essential when giving cross-team feedback. If I were to review a design that might be indirectly related to my work, and if I had no knowledge about how the project arrived at that point, I would say so, highlighting my take as external.

    We often focus on the negatives, trying to outline all the things that could be done better. That’s of course important, but it’s just as important—if not more—to focus on the positives, especially if you saw progress from the previous iteration. This might seem superfluous, but it’s important to keep in mind that design is a discipline where there are hundreds of possible solutions for every problem. So pointing out that the design solution that was chosen is good and explaining why it’s good has two major benefits: it confirms that the approach taken was solid, and it helps to ground your negative feedback. In the longer term, sharing positive feedback can help prevent regressions on things that are going well because those things will have been highlighted as important. As a bonus, positive feedback can also help reduce impostor syndrome.

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

    Another way that you can improve your feedback is to depersonalize the feedback: the comments should always be about the work, never about the person who made it. It’s “This button isn’t well aligned” versus “You haven’t aligned this button well.” This is very easy to change in your writing by reviewing it just before sending.

    In terms of actionability, one of the best approaches to help the designer who’s reading through your feedback is to split it into bullet points or paragraphs, which are easier to review and analyze one by one. For longer pieces of feedback, you might also consider splitting it into sections or even across multiple comments. Of course, adding screenshots or signifying markers of the specific part of the interface you’re referring to can also be especially useful.

    One approach that I’ve personally used effectively in some contexts is to enhance the bullet points with four markers using emojis. So a red square 🟥 means that it’s something that I consider blocking; a yellow diamond 🔶 is something that I can be convinced otherwise, but it seems to me that it should be changed; and a green circle 🟢 is a detailed, positive confirmation. I also use a blue spiral 🌀 for either something that I’m not sure about, an exploration, an open alternative, or just a note. But I’d use this approach only on teams where I’ve already established a good level of trust because if it happens that I have to deliver a lot of red squares, the impact could be quite demoralizing, and I’d reframe how I’d communicate that a bit.

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

    • 🔶 Navigation—When I see these two buttons, I expect one to go forward and one to go back. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.
    • 🟢 Overall—I think the page is solid, and this is good enough to be our release candidate for a version 1.0.
    • 🟢 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 creates the impression that it’s a positive action because green is usually perceived as a confirmation color. Do we need to explore a different color?
    • 🔶Tiles—Given the number of items on the page, and the overall page hierarchy, it seems to me that the tiles shouldn’t be using the Subtitle 1 style but the Subtitle 2 style. This will keep the visual hierarchy more consistent.
    • 🌀 Background—Using a light texture works well, but I wonder whether it adds too much noise in this kind of page. What is the thinking in using that?

    What about giving feedback directly in Figma or another design tool that allows in-place feedback? In general, I find these difficult to use because they hide discussions and they’re harder to track, but in the right context, they can be very effective. Just make sure that each of the comments is separate so that it’s easier to match each discussion to a single task, similar to the idea of splitting mentioned above.

    One final note: say the obvious. Sometimes we might feel that something is obviously good or obviously wrong, and so we don’t say it. Or sometimes we might have a doubt that we don’t express because the question might sound stupid. Say it—that’s okay. You might have to reword it a little bit to make the reader feel more comfortable, but don’t hold it back. Good feedback is transparent, even when it may be obvious.

    There’s another advantage of asynchronous feedback: written feedback automatically tracks decisions. Especially in large projects, “Why did we do this?” could be a question that pops up from time to time, and there’s nothing better than open, transparent discussions that can be reviewed at any time. For this reason, I recommend using software that saves these discussions, without hiding them once they are resolved. 

    Content, tone, and format. Each one of these subjects provides a useful model, but working to improve eight areas—observation, impact, question, timing, attitude, form, clarity, and actionability—is a lot of work to put in all at once. One effective approach is to take them one by one: first identify the area that you lack the most (either from your perspective or from feedback from others) and start there. Then the second, then the third, and so on. At first you’ll have to put in extra time for every piece of feedback that you give, but after a while, it’ll become second nature, and your impact on the work will multiply.

    Thanks to Brie Anne Demkiw and Mike Shelton for reviewing the first draft of this article.

  • Asynchronous Design Critique: Getting Feedback

    Asynchronous Design Critique: Getting Feedback

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

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

    Design analysis is not 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 findings, and taking action, as with any great 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 opinion” at the conclusion of a presentation are likely to generate a lot of divergent ideas, or worse, to make people follow the lead of the first speaker. And finally, we become irritated because ambiguous queries like those can result in people leaving reviews that don’t even consider keys. Which might be a savory matter, so it might be hard at that point to divert the crew to the topics that you had wanted to focus on.

    But how do we enter this circumstance? It’s a combination of various aspects. One is that we don’t often consider asking as a part of the input approach. Another is how healthy it is to assume that everyone else will agree with the problem and leave it alone. 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 issues, so we don’t work on improving them.

    Great questioning helps to guide and concentrate the criticism. It also serves as a form of acceptance, outlining your willingness to make comments and the types of comments you want to receive. It puts people in the right emotional state, especially in situations when they weren’t expecting to give opinions.

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

    The term” period” refers to each of the stages of the process, in our case, the design phase. The kind of feedback changes as the customer research moves forward to the final design. But within a single stage, one might also examine whether some assumptions are correct and whether there’s been a suitable language of the amassed input into updated designs as the job has evolved. The levels of user experience may serve as a starting point for possible questions. What are your project goals, exactly? User requirements? Funnality? Information? Contact design? Data infrastructure Interface style Navigation style? Physical layout packaging?

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

    • Features: Is it appealing to automate accounts creation?
    • Interaction style: Take a look at the updated flowing and let me know if there are any steps or failure states I may have missed.
    • Information infrastructure: We have two competing bits of information on this site. Does the framework make a good communication between them both?
    • User interface design: What do you think about the top-of-the-page error counter, which makes sure you can see the future error even when the error 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 overly long and hard to understand. Exist any recommendations for resolving 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 difficult. 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 strategy. Asking,” When the stop opens and the switches appear, is this conversation excellent, for instance?” may seem precise, but you can place the “good” tournament, and transfer it to an even better query:” When the prevent opens and the buttons appear, is it clear what the next action is”?

    Sometimes we do want a lot of feedback. Although that’s uncommon, it can occur. In that sense, you might still make it explicit that you’re looking for a wide range of opinions, whether at a high level or with details. Or perhaps you should just say,” At first glance, what do you think”? so that 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

    The most widely visible aspect of the design process is probably the design iteration, which serves 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 design iteration write-up or presentation followed by some sort of discussion thread. 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.

    Using iteration posts has a number of benefits:

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

    These posts of course don’t mean that no other feedback approach should be used, just that iteration posts could be the primary rhythm for a remote design team to use. 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

    Each project is likely to have a goal, and it should most likely be one that has already been summarized in one sentence elsewhere, such as the client brief, the product manager’s outline, or the request of the project owner. So this is something that I’d repeat in every iteration post—literally copy and pasting it. 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 kind of design work that has been done is then the design. 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. Creating a numbered list of questions can also help make it simpler to refer to each one by its number.

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

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

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

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

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

    The evaluation

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

    Asynchronous feedback is particularly effective because of this shift, especially around these friction points:

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

    The first friction point is having to feel pressured to respond to each and every comment. Sometimes we write the iteration post, and we get replies from our team. It’s just a few of them, it’s simple, and there isn’t much to worry about. Sometimes, however, some solutions may require more in-depth discussions, and responding to everyone quickly can add up to the pressure of trying to be a good team player by doing the same 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 is 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. That is the response when the design changes and we publish a follow-up iteration. 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. ” Thanks,”” Good points— I’ll review,” or” Thanks. These will be included in the upcoming iteration. In some cases, this could also be just a single top-level comment along the lines of” Thanks for all the feedback everyone—the next iteration is coming soon”!
    • Another option is to provide a quick summary of the comments before moving on. This may be particularly helpful if your workflow 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 ). And in the end, presenting everything in aggregated form helps us to prioritize our work more.

    Remember to always remember that you don’t have to accept every piece of feedback, even though you 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 project designer. In the end, everyone has their area of expertise, and as a designer, you are the one with the most background and knowledge to make the right choice. And by listening to the feedback that you’ve received, you’re making sure that it’s also the best and most balanced decision.

    Thanks to Mike Shelton and Brie Anne Demkiw for their contributions to the initial draft of this article.