Category: Blog

Your blog category

  • To Ignite a Personalization Practice, Run this Prepersonalization Workshop

    To Ignite a Personalization Practice, Run this Prepersonalization Workshop

    Image this. You’ve joined a club at your business that’s designing innovative product features with an focus on technology or AI. Or perhaps your business only started using a personalization website. In any case, you’re designing using files. Then what? There are many warning stories, no immediately achievement, and some guides for the baffled when it comes to designing for customisation.

    The personalization space is real, between the dream of getting it right and the worry of it going wrong ( like when we encounter “persofails” similar to a company’s constant plea to regular people to purchase additional bathroom seats ). It’s an particularly confusing place to be a modern professional without a map, a map, or a strategy.

    There are no Lonely Planet and some tour guides for those of you who want to personalize because successful personalization depends so much on each group’s talent, technology, and market position.

    However, you can make sure your team has properly packed its carriers.

    There’s a DIY method to increase your chances for victory. You’ll at least at least disarm your boss ‘ irrational exuberance. You’ll need to properly plan before the celebration.

    We call it prepersonalization.

    Behind the song

    Take into account the DJ have on Spotify, which was introduced last year.

    We’re used to seeing the polished final outcome of a personalization have. A personal have had to be developed, budgeted, and given priority before the year-end prize, the making-of-backstory, or the behind-the-scenes success chest. A delay of thought-provoking tips to enhance customer experiences is present before any personalization function is implemented in your product or service.

    So how do you understand where to position your personalization bet? How can you create regular interactions that didn’t irritate users or worse, breed trust? We’ve discovered that several budgeted programs initially needed one or more workshops to join key stakeholders and domestic customers of the technology to justify their continuing investments. Create it count.

    We’ve witnessed the same evolution up near with our clients, from big tech to budding companies. How effective these prepersonalization actions play out, in our experiences working on small and large customisation efforts, and how effective is the program’s best track record and its ability to weather challenging questions, work steadily toward shared answers, and manage its design and engineering efforts.

    Time and again, we’ve seen successful workshops individual coming success stories from fruitless efforts, saving many time, resources, and social well-being in the process.

    A yearlong project involving tests and feature development is a customisation practice. Your software load is not experiencing a switch-flip. It’s ideal managed as a delay that usually evolves through three actions:

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

    We think there is a basic language, a set of “nouns and verbs” that your business can use to create personalized, personalized, or automatic experiences, which is why we created our democratic personalization platform and why we’re testing an accompanying deck of cards. You won’t require these accounts. But we highly recommend that you create something similar, whether that might be online or natural.

    Set the timer for your home.

    How much does a prepersonalization factory take to prepare? The surrounding assessment activities that we recommend including can ( and often do ) span weeks. We suggest aiming for two to three days for the main workshop. Information on the necessary first-day activities are included in a summary of our broad approach.

    The whole episode of the wider studio is twofold:

      Kickstart: This specifies the terms of relationship as you concentrate on both the potential and the team’s and leadership’s readiness and generate.
    1. Plan your function: This is where the card-based workshop activities take place, giving you a work plan and the work scope.
    2. Work your plan: This stage is all about creating a competitive environment for staff participants to singularly pitch their personal pilots that each contain a proof-of-concept task, its business situation, and its operating model.

    Give yourself at least a day, divided into two long time blocks, to work through a concentrated version of those initial two phases.

    Kickstart: Apt your appetite

    We call the first lesson the “landscape of connected experience“. It looks at the possibilities for personalization in your company. Any UX that necessitates the orchestration of multiple systems of record on the backend is a connected experience, in our opinion. This could be a content-management system combined with a marketing-automation platform. A customer-data platform and a digital asset manager could be combined.

    Give examples of connected experience interactions that you admire, find familiar, or even dislike, as examples of consumer and business-to-business examples. This should cover a representative range of personalization patterns, including automated app-based interactions ( such as onboarding sequences or wizards ), notifications, and recommenders. These cards contain a catalog, which we have. To jog your mind, here are 142 different interactions.

    This is all about setting the table. What are the potential paths for the practice in your organization? Here’s a long-form primer and a strategic framework for a broad perspective.

    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 ). We categorize connected experiences in our cards according to their functions, features, experiences, complete products, and portfolios. Build your own size in this. 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 concept on the following 2 2 grid, which lists the four enduring justifications for a unique experience. This is crucial because it emphasizes how personalization can affect your own methods of working as well as your external customers. 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 give them all a prioritization. Here, the goal is to demonstrate how various departments may view their own advantages over the effort, which can be different from one department 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 filling in the personalization gap. Is the customer journey well documented in your business? Will data and privacy compliance be too big of a challenge? Do you have any needs for content metadata that you must address? ( We’re pretty sure you do; it’s just a matter of acknowledging the magnitude of that need and finding a solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six intractable stakeholder attitudes that prevent progress.

    Your success depends on collaborating effectively and managing expectations. Consider the potential barriers to your future progress. Ask the participants to list specific actions you can take to help your organization overcome or reduce those obstacles. According to research, personalization initiatives face a number of common obstacles.

    You should have at this point discussed sample interactions, emphasized a significant benefit area, and identified significant gaps. Good—you’re ready to continue.

    Hit the test kitchen

    Next, let’s take a look at what you’ll need to create personalization recipes. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. They give you a variety of options for how your organization can conduct its activities because of their broad and potent capabilities. This raises the question: When creating a connected experience, where do you start?

    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 creating, testing, and improving the snacks and meals that will be included on the regularly changing menu of your personalization program.

    Over the course of the workshop, the ultimate menu of the prioritized backlog will come together. And making “dishes” is the way that you’ll have different team members create customized interactions that either serve their or others ‘ needs.

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

    Verify your ingredients

    Like a good product manager, you’ll make sure you have everything you need to make your desired interaction ( or that you can figure out what needs to be added to your pantry ) and that you validate with the right stakeholders present. These elements include the audience you’re targeting, the content and design elements, the interaction’s context, and your overall ensemble.

    This isn’t just about discovering requirements. The team can: Identify your personalizations as a series of if-then statements by documenting them as a series of if-then statements.

    1. compare findings to a common method for developing features, similar to how artists paint with the same color palette,
    2. specify a consistent set of interactions that users find uniform or familiar,
    3. and establish parity among performance indicators and key performance indicators as well.

    As a result, you can deliver a common palette of the main themes of your personalized or automated experience while reducing the number of technical efforts required.

    Compose your recipe

    What elements are significant to you? Consider the construct “what-what-when-why”

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

    We first developed these cards and card categories five years ago. We regularly test their suitability with clients and audience members at conferences. And there are still fresh possibilities. But they all follow an underlying who-what-when-why logic.

    In the cards in the accompanying photo below, you can typically follow along with right to left in three examples of subscription-based reading apps.

    1. When a visitor or an unidentified visitor interacts with a product title, a banner or alert bar appears that makes it simpler for them to find a related title they might like 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: A user receives an email before their subscription expires or after a recent failed renewal to request that they reconsider renew or request that they be reminded to do so.

    We’ve also found that sometimes this process comes together more effectively by cocreating the recipes themselves, so a good preworkshop activity might be to think about what these cards might be for your organization. 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.

    The workshop’s later stages could be characterized as shifting from focusing on a cookbook to a more nuanced customer-journey mapping. Individual” cooks” will pitch their recipes to the team using a standard jobs-to-be-done format to ensure consistency and outcomes, and from there, the resulting collection will be prioritized for finished design and production delivery.

    Better kitchens require better architecture

    For those who are inside delivering it, simplifying a customer experience is a challenging task. Avoid those who make up their mind. With that being said,” Complicated problems can be hard to solve, but they are addressable with rules and recipes“.

    A team overfitting: they aren’t designing with their best data, is what causes personalization to become a laugh line. Every organization has metadata debt to go along with its technical debt, which causes a drag on the effectiveness of personalization, much like a sparse pantry. Your AI’s output quality, for example, is indeed limited by your IA. Before they acquired a seemingly modest metadata startup that now powers its underlying information architecture, Spotify’s poster-child prowess today was beyond belief.

    You can’t stand the heat, unquestionably…

    Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach will produce the necessary concentration and intention for success. Banish your ideal 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 mouths to feed and meals to be served.

    You have a better chance of lasting success and sound beginnings with this workshop framework. Wiring up your information layer isn’t an overnight affair. However, if you use the same cookbook and the same recipe combination, you’ll have solid ground for success. We created these activities to ensure that your organization’s needs are clear and concise before the risks start to accumulate.

    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 waste it. The pudding is the proof, as they say.

  • 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, everything will change. This is a one piece of advice I can give to friends and family when they become innovative families. 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 sleeps 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 re-enter the familiar pattern, a brand-new technology or thought emerges to shake things up and completely alter the world.

    How we got below

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

    The beginning of website standards

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

    Server-side language like PHP, Java, and.NET took Perl as the primary back-end computers, and the cgi-bin was tossed in the garbage bin. With these better server-side instruments came the first time of online applications, starting with content-management systems ( especially in the blog space with tools like Blogger, Grey Matter, Movable Type, and WordPress ). AJAX opened the door to sequential connection between the front end and back end in the mid-2000s. Immediately, sites may update their information without needing to refresh. Developers created a crop of trusted client-side interactions across browsers with wildly varying standards aid, such as Prototype, YUI, and jQuery. Techniques like photo alternative enable the use of fonts by skilled developers and developers. 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 styles and designs, 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 to add a dash of connection to pages without having to spend the money to double or even quadruple the download size for basic websites.

    The internet as technology platform

    The balance between the front end and the back end continued to improve, leading to the development of the latest online 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 a place for linked records evolved into a world with endless possibilities.

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

    This fusion of potent portable devices and potent 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 websites waned. Social media provided links on a global level, with both positive and negative outcomes.

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

    Where we are now

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

    Browser support for CSS, JavaScript, and other standards like web components has accelerated, especially through efforts like Interop. In a fraction of the time that they once did, new technologies receive 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 %. Browser support is frequently the only obstacle to using newer techniques today, rather than the time it takes to train and adopt new techniques.

    Today, with a few commands and a couple of lines of code, we can prototype almost any idea. With today’s abundance of tools, starting something new is now simpler than ever. However, as the initial cost of these frameworks may be saved in the beginning, it eventually becomes due as their upkeep and maintenance becomes a component of our technical debt.

    Adopting new standards can sometimes take longer if we rely on third-party frameworks because we might have to wait for those frameworks to adopt those standards. These frameworks—which used to let us adopt new techniques sooner—have now become hindrances instead. Users must wait for scripts to load before they can read or interact with pages, as these same frameworks frequently come with performance costs as well. 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 desire?

    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? Sometimes the convenience may be worth it. Sometimes it’s just a hack that you’ve gotten used to. And occasionally, it prevents you from pursuing better options.

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

    Design with care. Whether your craft is code, pixels, or processes, consider the impacts of each decision. Many modern tools have the convenience of 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 consider more carefully and design with consideration rather than rush to “move fast and break things”

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

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

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

    Go forth and make

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

  • Opportunities for AI in Accessibility

    Opportunities for AI in Accessibility

    I was completely moved by Joe Dolson’s current article on the crossroads of AI and convenience, both in terms of the suspicion he has regarding AI in general and how many people have been using it. 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 center 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 examining how computer vision models can create other words. He raises a lot of appropriate points regarding the state of the world right now. And while computer-vision concepts continue to improve in the quality and complexity of information in their information, their benefits aren’t wonderful. He argues to be accurate that the state of image research is currently very poor, especially for some graphic types, in large part due to the absence of contextual contexts in which to look at images ( as a result of having separate “foundation” models for words analysis and image analysis ). Today’s models aren’t trained to distinguish between images that are contextually relevant ( that should probably have descriptions ) and those that are purely decorative ( which might not need a description ) either. However, I still think there’s possible in this area.

    As Joe mentions, human-in-the-loop publishing of alt word should definitely be a factor. And if AI can intervene and provide a starting point for alt text, even if the quick 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 teach a design to consider image usage in context, it might be able to help us more swiftly distinguish between images that are likely to be beautiful and those that are more descriptive. That will help clarify which situations require image descriptions, and it will increase authors ‘ effectiveness in making their sites more visible.

    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 map that was simply the description of the chart’s name and the type of representation it was: Pie map comparing smartphone usage to have 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 people could ask questions about the visual if your computer knew that that picture was a dessert chart ( because an ship model concluded this ).

    • Are there more smartphone users than have devices?
    • 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 helpful in education settings to assist those who can see these charts as they are able to comprehend the data contained therein.

    What if you could request your website to make a complicated map simpler? What if you asked it to separate a single line from a collection curve? What if you could request your website to change the color combinations in your website so that it works better for your type of color blindness? What if you could request it to switch tones for habits? Given these resources ‘ chat-based interface and our existing ability to manipulate photos in today’s AI devices, that seems like a chance.

    Imagine a specially designed unit that could extract the data from that chart and transfer 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 awesome!

    Matching systems

    When Safiya Umoja Noble chose to write her reserve Algorithms of Oppression, she hit the nail on the head. Although her book focused on how search engines can foster racism, I believe it’s equally true that all computer types have the potential to foster fight, prejudice, and hatred. We all know that poorly written and maintained techniques are extremely dangerous, whether it’s Online constantly showing you the most recent post from a drowsy businessman, YouTube sending us into a q-hole, or Instagram warping our ideas of what normal bodies seem like. A large portion of this is a result of a lack of diversity in the people who design and construct them. When these platforms are built with inclusively baked in, however, there’s real potential for algorithm development to help people with disabilities.

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

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

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

    Other ways that AI can helps people with disabilities

    I’m sure I could go on and on about using AI to assist people with disabilities, but I’m going to make this last section into a bit of a lightning round if I weren’t trying to put this together in between other tasks. In no particular order:

      Voice preservation. You m others. It’s possible to train an artificial intelligence model to mimic your voice, which can be incredibly helpful for those who have ALS ( Lou Gehrig’s disease ), motor neuron disease, or other medical conditions that can make it difficult to talk. This is, of course, the same tech that can also be used to create audio deepfakes, so it’s something that we need to approach responsibly, but the tech has truly transformative potential.
    • Voice recognition. Researchers are assisting people with disabilities in the collection of recordings of people with atypical speech, thanks to the assistance of the Speech Accessibility Project. As I type, they are actively recruiting people with Parkinson’s and related conditions, and they have plans to expand this to other conditions as the project progresses. More people with disabilities will be able to use voice assistants, dictation software, and voice-response services, as well as to use only their voices to control computers and other devices, according to this research.
    • Text transformation. The most recent generation of LLMs is capable of altering already-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 data

    We must acknowledge that our differences matter. The intersections of the identities we live in have an impact on our lived experiences. These lived experiences—with all their complexities ( and joys and pain ) —are valuable inputs to the software, services, and societies that we shape. Our differences must be reflected in the data we use to develop new models, and those who provide it need to be compensated for doing so. More robust models are produced by inclusive data sets, which promote more justifiable outcomes.

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

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

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


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


    Many thanks to Kartik Sawhney for helping me with the development of this piece, Ashley Bischoff for her invaluable editorial assistance, and, of course, Joe Dolson for the prompt.

  • I am a creative.

    I am a creative.

    I am a artistic. What I do is alchemy. It is a puzzle. I don’t perform it as much as I let it be done by me.

    I am a innovative. No all creative people approve of this brand. Not all people see themselves in this manner. Some innovative people practice scientific in their work. That is their reality, and I respect it. Sometimes I even envy them, a minor. But my approach is different—my becoming is unique.

    Apologizing and qualifying in advance is a diversion. That’s what my head does to destroy me. I’ll leave it alone for today. I may come back later to make amends and count. After I’ve said what I should have. Which is challenging enough.

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

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

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

    Passion should only be saved for the meet, when it matters. not the informal gathering that two different gatherings precede that appointment. Anyone knows why we have all these discussions. We keep saying we’re getting rid of them, but we keep discovering new ways to get them. They occasionally yet excel. Sometimes they detract from the real function, though. The percentages between when conferences are important, and when they are a sad distraction, vary, depending on what you do and where you do it. And who you are and how you go about doing it. Suddenly I digress. I am a innovative. That is the style.

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

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

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

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

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

    Some individuals who detest being called artistic perhaps been closeted artists, but that’s between them and their gods. No offence meant. Your wisdom is correct, too. However, mine is for me.

    Creatives understand artists.

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

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

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

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

    I am a innovative. Every experience I create has the potential to make Indiana Jones look older while snoring in a deck head. The more I pursue creativity, the faster I can complete my work, and the longer I obsess over my ideas and whizz around in circles before I can complete that task.

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

    I am not an actor.

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

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

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

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

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

    Working frees me from worrying about my job.

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

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

    I am a innovative. I think that approach is the greatest secret. I think it is so important that I’m actually foolish enough to publish an essay I wrote into a little machine without having to go through or edit it. I didn’t do this generally, I promise. But I did it right away because I was even more scared of forgetting what I was saying because I was as scared as I might be of you seeing through my sad gestures toward the gorgeous.

    There. I think I’ve said it.

  • The Best PC Games of the ’90s, Ranked

    The Best PC Games of the ’90s, Ranked

    In the ‘ 90s, there was a dramatic series between system and PC games. Some PC games that were first released on Computers never received system ports ( and vice versa ), and the majority of PC games were built entirely with a mouse and keyboard. These early PC games were also notoriously finnicky to install, and there was much less information ]… ]

    The first article on Den of Geek was The Best Computer Games of the 1990s, Ranked.

    Unforgotten, an ITV crime drama, features a brand-new guest cast that includes MyAnna Buring, Emmett J. Scanlan, Victoria Hamilton, and Damien Molony, along with a new historical murder that Sunny and her new ( ish ) boss Jess must solve.

    They join the returning cast of direct Sanjeev Bhaskar as DI Sunil &#8220, Sunny &#8221, Khan, Sinéad Keenan as DCI Jessica James, both of whose personal life took a pounding in the previous line. While grieving for his former colleague Cassie, who died suddenly in a car accident at the end of series four, Sunny &#8217, s relationship with his fiancée Sal ( Michelle Bonnard ) also ended. Sal lost a pregnancy and Sunny told her that he didn&#8217, t want to have any more children, but she moved out of their house. With his sons aside at school, Sunny then lives alone.

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

    Jessie started her new career in line five with a bad schedule after learning that her father had been having an affair with her girl. Her no-nonsense approach made her fight with Sunny and his still-grieving team, but by the end of the series, they &#8217, d reached a kind of friendship and realised that they didn&#8217, t stand as far apart in terms of professional values as they &#8217, d first thought.

    Sunny and Jess may be joined by Unforgotten patrons Jordan Long as DS Murray Boulting, Carolina Main as DC Fran Lingley, Hiten Patel as DC Patel, Pippa Nixon as DC Karen Willets, and Georgia Mackenzie as Dr. Leanne Balcombe, along with Andrew Lancel as Jess&#8217, partner Steve, and Kate Robbins as her mother Kate. Get out everything about the new cast of guests below:

    MyAnna Buring portrays Melinda Ricci.

    MYANNA BURING as Melinda Ricci

    Melinda is a journalist for Britannia News, Unforgotten&#8216, s right-wing GB News-style company, but does she really believe in the anger she&#8217, s spouting on Television? Her personal life has suffered a recent tragedy when fiancé Patrick ( Emmett Scanlan ) was paralysed in an accident. MyAnna Buring, a well-known experience, has appeared in the roles of Long Susan in BBC/Prime Video time crime crisis Ripper Street, The Witcher, and The Twilight Saga: Breaking Dawn, among others.

    Emmett Scanlan as Patrick

    EMMETT J SCANLAN as Patrick

    Patrick is Melinda&#8217, s fiancé and when we meet him, is in recovery following a severe injury that left his lower system paralysed. He&#8217, s played by Emmett J. Scanlan, seen recently in British crime crisis Kin, as Billy Grade in the last set of BBC gang drama Peaky Blinders, in ITV crime drama The Tower, and earlier, Sky thriller Gangs of London, horror-fantasy In the Flesh and cat-and-mouse detective drama The Fall.

    Maximilian Fairley as Martin” Marty” Johnson

    Maximillian Fairley as Marty Baines

    Marty, a young man with autism, tries to take care of his disabled mother Dot ( Michele Dotrice ), who lives in Deal on the Kent coast. He is isolated and pushed out of the city, but he finds himself looking for a sense of belonging and compassion in right-wing virtual societies. Maximilian Fairley, a new graduate from the Royal Central School of Speech and Drama, plays Marty. This is his first broadcast starring role because he has high-functioning autism and is hard of hearing.

    Michele Dotrice as Dot Johnson

    MICHELE DOTRICE as Dot Baines

    Dot Marty’s family, Dot, lives in a packed house on the Kent beach in chaos. She relies on her brother for meals and is unable to take care of herself, and the pair are obviously not coping also. She&#8217, s played by British acting former Michele Dotrice, who has a long and distinguished film and television job, and is cherished for the position of Betty Spencer in classic comedy Some Mothers Do &#8216, Ave &#8216, Em, as well as productions of Middlemarch, Vanity Fair, Les Miserables and many more.

    Elham Ehsas as Asif Syed

    ELHAM EHSAS as Asif Syed

    Asif is an Afghan who immigrated to the UK to avoid a life-threatening situation there and is currently residing in Barnstaple, Devon, where he is studying for his American citizenship exam. He&#8217, s played by Homeland, Young Wallander, Shantaram and The Agency comedian Elham Ehsas.

    Ahmad Sakhi as Hassan

    AHMAD SAKHI as Hassan

    Hassan is an Armenian person who travels to the UK without permission to avoid being persecuted and threatened with death. He&#8217, s played by Ahmad Sakhi, who&#8217, s late had tasks in Coronation Street, Malpractice, and The Island, and will immediately look in Anne Rice&#8217, s The Talamasca.

    Victoria Hamilton portrays Juliet Cooper

    VICTORIA HAMILTON as Juliet Cooper

    A student has lodged a complaint against her at a London school, and Juliet Cooper is the head of the department. She&#8217, s a bereaved wife and the mother of troubled teenage daughter Taylor ( Pixie Davies ). Juliet is played by Victoria Hamilton, a recognizable face on camera known for new jobs in Paramount + crime crisis The Crow Girl, Sky social drama COBRA, Netflix behemoth The Crown, in which she played the Queen Mother, as well as formerly in Lark Rise to Candleford and many, many more.

    Pixie Davies as Taylor Cooper

    PIXIE DAVIES as Taylor Cooper

    Following a household loss, Taylor Cooper is a teen having trouble with school. She&#8217, s the daughter of university lecturer Juliet ( Victoria Hamilton ) and is played by 18-year-old Pixie Davies, who&#8217, s been acting since the age of six and has starred on television in Humans, Utopia, The Secret of Crickley Hall, and on film in Mary Poppins Returns, Miss Peregrine&#8217, s Home for Peculiar Children among others.

    Even Appearing: Damien Molony

    The Brassic, The Split and GameFace artist, who came to prominence as centuries-old monster Hal in Being Human may also appear in Unsung set six in an as-yet-undisclosed position.

    Unforgotten series six premieres on ITV1 on February 9 and streams on ITVX.

    The first post Unforgotten Series 6 Cast: Meet the New Characters Joining Sunny and Jess appeared first on Den of Geek.

  • Unforgotten: Who’s the Ex-Police Detective Prisoner at the End of Episode One?

    Unforgotten: Who’s the Ex-Police Detective Prisoner at the End of Episode One?

    Warning: trailers for Unsung line six show one. Every Television crime crisis Unforgotten welcomes a new addition to the investigation for the year. By the time the credits roll on the finale, series regulars DI Khan ( Sanjeev Bhaskar ) and DCI James ( Sinéad Keenan, who took over from Nicola Walker’s DCI Stuart in series ]… ]

    The article Unremembered: Who’s the Ex-Police Detective Prisoner at the End of Episode One? primary appeared on Den of Geek.

    Unforgotten, an ITV crime drama, features a brand-new guest cast that includes MyAnna Buring, Emmett J. Scanlan, Victoria Hamilton, and Damien Molony, along with a new historical murder for Sunny and new ( ish ) boss Jess to solve.

    They join the returning cast of direct Sanjeev Bhaskar as DI Sunil &#8220, Sunny &#8221, Khan, Sinéad Keenan as DCI Jessica James, both of whose personal life took a pounding in the previous set. While grieving for his former colleague Cassie, who died suddenly in a car accident at the end of series four, Sunny &#8217, s relationship with his fiancée Sal ( Michelle Bonnard ) also ended. Sal lost a pregnancy and Sunny told her that he didn&#8217, t want to have any more children, but she moved out of their house. With his sons aside at school, Sunny then lives alone.

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

    Jessie started her new career in line five with a bad schedule after learning that her father had been having an affair with her girl. Her no-nonsense approach made her fight with Sunny and his still-grieving team, but by the end of the series, they &#8217, d reached a kind of friendship and realised that they didn&#8217, t walk as far apart in terms of professional values as they &#8217, d first thought.

    Sunny and Jess may be joined by Unforgotten patrons Jordan Long as DS Murray Boulting, Carolina Main as DC Fran Lingley, Hiten Patel as DC Patel, Pippa Nixon as DC Karen Willets, and Georgia Mackenzie as Dr. Leanne Balcombe, along with Andrew Lancel as Jess&#8217, father Steve, and Kate Robbins as her mother Kate. Above, learn everything about the new host cast:

    MyAnna Buring portrays Melinda Ricci.

    MYANNA BURING as Melinda Ricci

    Melinda is a journalist for Britannia News, Unforgotten&#8216, s right-wing GB News-style entity, but does she really believe in the anger she&#8217, s spouting on Television? Her personal life has suffered a recent tragedy when fiancé Patrick ( Emmett Scanlan ) was paralysed in an accident. MyAnna Buring, a well-known experience, has appeared in the roles of Long Susan in BBC/Prime Video time crime crisis Ripper Street, The Witcher, and The Twilight Saga: Breaking Dawn, among others.

    Emmett Scanlan as Patrick

    EMMETT J SCANLAN as Patrick

    Patrick is Melinda&#8217, s fiancé and when we meet him, is in recovery following a severe injury that left his lower system paralysed. He&#8217, s played by Emmett J. Scanlan, seen recently in British crime crisis Kin, as Billy Grade in the last set of BBC gang drama Peaky Blinders, in ITV crime drama The Tower, and earlier, Sky thriller Gangs of London, horror-fantasy In the Flesh and cat-and-mouse detective drama The Fall.

    Maximilian Fairley as Martin” Marty” Johnson

    Maximillian Fairley as Marty Baines

    Marty, a young man with autism, tries to take care of his disabled mother Dot ( Michele Dotrice ), who lives in Deal on the Kent coast. He is isolated and pushed out of town in his free time, looking for a sense of belonging and compassion in right-wing virtual communities. Maximilian Fairley, a new student of the Royal Central School of Speech and Drama, plays Marty. This is his first broadcast record because he has high functioning autism and is hard of hearing.

    Michele Dotrice as Dot Boone

    MICHELE DOTRICE as Dot Baines

    Dot Marty’s family, Dot, lives in a packed house on the Kent beach in chaos. She relies on her brother for foods, and the couple are obviously never coping well. She is able to take care of herself. She&#8217, s played by British acting former Michele Dotrice, who has a long and distinguished film and television job, and is cherished for the position of Betty Spencer in classic comedy Some Mothers Do &#8216, Ave &#8216, Em, as well as productions of Middlemarch, Vanity Fair, Les Miserables and many more.

    Elham Ehsas as Asif Syed

    ELHAM EHSAS as Asif Syed

    Asif, an Afghan who fled to the UK to leave a life-threatening situation in Afghanistan, is currently residing in Barnstaple, Devon, where he is studying for his American citizenship. He&#8217, s played by Homeland, Young Wallander, Shantaram and The Agency artist Elham Ehsas.

    Ahmad Sakhi as Hassan

    AHMAD SAKHI as Hassan

    Hassan is an Pashtun man who travels to the UK in unsafe, illegal fashion to avoid being subjected to harassment and death threats. He&#8217, s played by Ahmad Sakhi, who&#8217, s late had tasks in Coronation Street, Malpractice, and The Island, and will immediately look in Anne Rice&#8217, s The Talamasca.

    Juliet Cooper portrayed by Victoria Hamilton

    VICTORIA HAMILTON as Juliet Cooper

    A student has lodged a complaint against her at a London school, and Juliet Cooper is a history lecturer and head of department. She&#8217, s a bereaved wife and the mother of troubled teenage daughter Taylor ( Pixie Davies ). Juliet is played by Victoria Hamilton, a recognizable face on camera known for new jobs in Paramount + crime crisis The Crow Girl, Sky social movie COBRA, Netflix behemoth The Crown, in which she played the Queen Mother, as well as formerly in Lark Rise to Candleford and many, many more.

    Pixie Davies as Taylor Cooper

    PIXIE DAVIES as Taylor Cooper

    Taylor Cooper is a student who is having trouble with school because of a family loss. She&#8217, s the daughter of university lecturer Juliet ( Victoria Hamilton ) and is played by 18-year-old Pixie Davies, who&#8217, s been acting since the age of six and has starred on television in Humans, Utopia, The Secret of Crickley Hall, and on film in Mary Poppins Returns, Miss Peregrine&#8217, s Home for Peculiar Children among others.

    Even Appearing: Damien Molony

    The Brassic, The Split and GameFace artist, who came to prominence as centuries-old monster Hal in Being Human may also appear in Unsung set six in an as-yet-undisclosed position.

    Unforgotten series six premieres on ITV1 on February 9 and streams on ITVX.

    The first post Unforgotten Series 6 Cast: Meet the New Characters Joining Sunny and Jess appeared first on Den of Geek.

  • Unforgotten Series 6 Cast: Meet the New Characters Joining Sunny and Jess

    Unforgotten Series 6 Cast: Meet the New Characters Joining Sunny and Jess

    Unforgotten, an ITV crime drama, features a brand-new guest cast that includes MyAnna Buring, Emmett J. Scanlan, Victoria Hamilton, and Damien Molony, along with a new historical murder that Sunny and her new ( ish ) boss Jess must solve. They join the returning cast of lead Sanjeev Bhaskar as DI Sunil” Sunny” Khan, Sinéad Keenan as DCI Jessica James, ]…]

    The second post Unforgotten Series 6 Cast: Meet the New Characters Joining Sunny and Jess appeared second on Den of Geek.

    Unforgotten, an ITV crime drama, features a brand-new guest cast that includes MyAnna Buring, Emmett J. Scanlan, Victoria Hamilton, and Damien Molony, along with a new historical murder that Sunny and her new ( ish ) boss Jess must solve.

    They join the returning cast of direct Sanjeev Bhaskar as DI Sunil &#8220, Sunny &#8221, Khan, Sinéad Keenan as DCI Jessica James, both of whose personal life took a pounding in the previous set. While grieving for his former colleague Cassie, who died suddenly in a car accident at the end of series four, Sunny &#8217, s relationship with his fiancée Sal ( Michelle Bonnard ) also ended. Sal lost a pregnancy and Sunny told her that he didn&#8217, t want to have any more kids, but she moved out of their home. With his sons aside at school, Sunny then lives alone.

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

    Jessie discovered that her father had been having an affair with her sister while making a bad choice for her new career in line five. Her no-nonsense approach made her fight with Sunny and his still-grieving team, but by the end of the series, they &#8217, d reached a kind of friendship and realised that they didn&#8217, t walk as far apart in terms of professional values as they &#8217, d first thought.

    Sunny and Jess may be joined by Unforgotten patrons Jordan Long as DS Murray Boulting, Carolina Main as DC Fran Lingley, Hiten Patel as DC Patel, Pippa Nixon as DC Karen Willets, and Georgia Mackenzie as Dr. Leanne Balcombe, along with Andrew Lancel as Jess&#8217, partner Steve, and Kate Robbins as her mother Kate. Get out everything about the new cast of guests below:

    MyAnna Buring portrays Melinda Ricci.

    MYANNA BURING as Melinda Ricci

    Melinda is a journalist for Britannia News, Unforgotten&#8216, s right-wing GB News-style entity, but does she really believe in the anger she&#8217, s spouting on Television? Her personal life has suffered a recent tragedy when fiancé Patrick ( Emmett Scanlan ) was paralysed in an accident. MyAnna Buring, a well-known mouth, has appeared in the roles of Long Susan in BBC/Prime Video time crime crisis Ripper Street, Kill List, The Twilight Saga: Breaking Dawn, and others.

    Emmett Scanlan as Patrick

    EMMETT J SCANLAN as Patrick

    Patrick is Melinda&#8217, s fiancé and when we meet him, is in recovery following a severe injury that left his lower system paralysed. He&#8217, s played by Emmett J. Scanlan, seen recently in British crime crisis Kin, as Billy Grade in the last set of BBC gang drama Peaky Blinders, in ITV crime drama The Tower, and earlier, Sky thriller Gangs of London, horror-fantasy In the Flesh and cat-and-mouse detective drama The Fall.

    Maximilian Fairley as Martin” Marty” Johnson

    Maximillian Fairley as Marty Baines

    Marty, a young man with autism, tries to take care of his disabled mother Dot ( Michele Dotrice ), who lives in Deal on the Kent coast. He is isolated and pushed out of town in his free time, looking for kinship and belonging in right-wing virtual communities. Maximilian Fairley, a new graduate of the Royal Central School of Speech and Drama, plays Marty. This is his first broadcast record because he is hard of hearing and neurodiverse with high-functioning dementia.

    Michele Dotrice as Dot Johnson

    MICHELE DOTRICE as Dot Baines

    Dot Marty’s family, Dot, lives in a packed house on the Kent beach in chaos. She relies on her brother for meals and is unable to take care of herself, and the pair are obviously not coping also. She&#8217, s played by British acting former Michele Dotrice, who has a long and distinguished film and television job, and is cherished for the position of Betty Spencer in classic comedy Some Mothers Do &#8216, Ave &#8216, Em, as well as productions of Middlemarch, Vanity Fair, Les Miserables and many more.

    Elham Ehsas portrays Asif Syed

    ELHAM EHSAS as Asif Syed

    Asif, an Afghan who immigrated to the UK to escape a life-threatening situation in Afghanistan, is currently residing in Barnstaple, Devon, where he is studying for his British citizenship exam. He&#8217, s played by Homeland, Young Wallander, Shantaram and The Agency actor Elham Ehsas.

    Ahmad Sakhi as Hassan

    AHMAD SAKHI as Hassan

    Hassan is an Afghan man who travels dangerously illegally to the UK to avoid fear and death on a dangerous, illegal journey. He&#8217, s played by Ahmad Sakhi, who&#8217, s recently had roles in Coronation Street, Malpractice, and The Outpost, and will soon appear in Anne Rice&#8217, s The Talamasca.

    Victoria Hamilton portrays Juliet Cooper

    VICTORIA HAMILTON as Juliet Cooper

    A student has lodged a complaint against her at a London university, and Juliet Cooper is the head of the department. She&#8217, s a bereaved wife and the mother of troubled teenage daughter Taylor ( Pixie Davies ). Juliet is played by Victoria Hamilton, a familiar face on screen known for recent roles in Paramount + crime drama The Crow Girl, Sky political thriller COBRA, Netflix behemoth The Crown, in which she played the Queen Mother, as well as previously in Lark Rise to Candleford and many, many more.

    Pixie Davies as Taylor Cooper

    PIXIE DAVIES as Taylor Cooper

    Taylor Cooper is a teenager who is having trouble with school because of a family bereavement. She&#8217, s the daughter of university lecturer Juliet ( Victoria Hamilton ) and is played by 18-year-old Pixie Davies, who&#8217, s been acting since the age of six and has starred on television in Humans, Utopia, The Secret of Crickley Hall, and on film in Mary Poppins Returns, Miss Peregrine&#8217, s Home for Peculiar Children among others.

    Also Appearing: Damien Molony

    The Brassic, The Split and GameFace actor, who came to prominence as centuries-old vampire Hal in Being Human will also appear in Unforgotten series six in an as-yet-undisclosed role.

    Unforgotten series six premieres on ITV1 on February 9 and streams on ITVX.

    The second post Unforgotten Series 6 Cast: Meet the New Characters Joining Sunny and Jess appeared second 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 human faces. We just squinted past a LinkedIn post that claimed this site might be helpful “if you are developing a image and looking for a photo.”

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

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

    A step up, personalities

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

    The decontextualization of personalities

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

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

    People are assumed to be dynamic, according to people.

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

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

    Personas do not account for this variation in their attempt to reduce reality; instead, they present a consumer as a set of features. Like personality tests, personas seize people away from real existence. Even worse, individuals are labeled as” that kind of guy” with no means to practice their inherent mobility. This behavior defies stereotypes, diminishes variety, and doesn’t reveal reality.

    Personas rely on people, not the environment

    You’re designing for a environment, not an individual, in the real world. There are economic, political, and cultural factors to consider when a person lives in a home, a community, or an ecosystem. A pattern is not meant for a single customer. Instead, you create a product that is intended to be used by a certain 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 often make the same decision over and over again? Possibly you’re a dedicated vegan but also decide to buy some beef when your relatives visit. Your decisions, including your behavior, opinions, and statements, are not absolute but very 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, what frequently occurs is that you choose a fictional character to play with 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 but is not a real person, as stated in Shlomo Goltz’s introduction article on Smashing Magazine; rather, it is made up of observations from numerous people. The famous USA Air Force design planes were designed based on the average of 140 of their pilots ‘ physical dimensions, with not a single pilot actually fit within that average seat, is a well-known criticism of this aspect of personas.

    The same limitation applies to mental aspects of people. Have you ever heard a famous person say something 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. Because it lacks the underlying causes for and how that finding came about, the results of the analysis frequently fail to make sense. It’s unclear or even contradictory. It lacks any significance. And the persona doesn’t give you the full background of the person ( s ) to uncover this meaning: you would need to dive into the raw data for each single persona item to find it. What then is the persona’s usefulness?

    The validity of personas is deceiving.

    To a certain extent, designers realize that a persona is a lifeless average. To combat this, designers create and add “relatable” details to personas to make them appear to be real people. Nothing better explains the absurdity of this than a phrase from the Interaction Design Foundation,” Add a few fictional personal details to make the persona a realistic character.” In other words, you add non-realism in an attempt to create more realism. You purposefully understate the fact that” John Doe” is an abstract representation of research findings, but wouldn’t it be much more responsible to emphasize that John is only an abstraction? Let’s say something is artificial, and let’s say it’s that.

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

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

    Dynamic Selves: The alternative to personas

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

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

    In developing an alternative to personas, we aim to transform the standard design process to be context-based. Similar to how we previously dealt with people, contexts are generalizable and have patterns that we can identify. How can we identify these patterns, then? How do we ensure truly context-based design?

    Understand real people in a variety of settings

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

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

    1. Select the appropriate sample.

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

    In qualitative research, validity does not derive from quantity but from accurate sampling. You pick the people who best fit the “population” you’re designing for. 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 fifteen different situations, Susan is not necessary. Once you’ve seen her in a few different settings, you’ve grasped Susan’s general scheme of action. Not Susan as an atomic being but Susan in relation to the surrounding environment: how she might act, feel, and think in different situations.

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

    However, the question 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 take into account the company’s objectives and strategy, the current customer base, and/or a potential future target audience.

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

    2. Conduct your research

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

    To gain an in-depth understanding of attitudes and decision-making trade-offs, the research focus was not limited to the interviewee alone but deliberately included the whole family. Each interviewee would provide a story that would later become much more interesting and precise with the additions made by their spouses, partners, kids, or occasionally even pets. We also paid attention to the behaviors that came from having relationships with other important people ( such as coworkers or distant relatives ), as well as the relationships that came into being with them. This wide research focus allowed us to shape a vivid mental image of dynamic situations with multiple actors.

    It is crucial that the research’s scope 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 with several Dynamic Selves, each” Self” representing one of the circumstances you have examined throughout the research analysis. A quote serves as the foundation of each Dynamic Self, which is supported by a photo and a few relevant demographics that help to illustrate the larger context. The research findings themselves will show which demographics are relevant to show. The key demographics were family type, number and type of homes owned, economic status, and technological maturity in our case because our research focused on families and their way of life to understand their needs for thermal regulation. We also included the individual’s name and age, but they’re optional; they’ll help the stakeholders transition from personas and allow them to connect multiple actions and contexts to the same person.

    To capture exact quotes, interviews need to be video-recorded and notes need to be taken verbatim as much as possible. This is crucial to the completeness of each participant’s various selves. Photos of the setting and anonymized actors are necessary to create authentic selves in ethnographic research conducted in real life. Ideally, these photos should come directly from field research, but an evocative and representative image will work, too, as long as it’s realistic and depicts meaningful actions that you associate with your participants. One of our interviewees, for instance, shared a story of how he used to spend weekends with his family in his mountain home. Therefore, we depicted him taking a hike with his young daughter.

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

    4. Identify potential design challenges

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

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

    Benefits of Dynamic Selves

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

    Davide is a person we might have once referred to as a “tech enthusiast.” However, there are also those who love technology who have families or are single, who are wealthy or poor. Their motivations and priorities when deciding to purchase a new thermostat can be opposite according to these different frames.

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

    The Dynamic Selves approach aims to dismiss the conflicted dual purpose of personas—to summarize and empathize at the same time—by separating your research summary from the people you’re seeking to empathize with. This is crucial because scale affects how we feel empathy for people; the bigger the group, the smaller it is to feel empathy for others. We have the deepest compassion for people with whom we can directly relate.

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

    Another significant benefit of Dynamic Selves 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 check your designs every day and might prevent you from making shortcuts.

    And finally, real people in their specific contexts are a better basis for anecdotal storytelling and therefore are more effective in persuasion. Real research documentation is necessary to obtain this result. The circumstances of your design proposals resound in your mind when you encounter Alessandra. Noise, bad ergonomics, lack of light, you name it. I’m afraid that if we choose to use this functionality, she’ll find her life more complicated.

    Conclusion

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

    Design needs to be simplified, but not generalized. You have to look at the research elements that stand out: the sentences that captured your attention, the images that struck you, the sounds that linger. Avoid using those and use them to describe the person in all of their contexts. People and insights both come with a context, and they cannot be taken out of that context because it would detract from meaning.

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

  • Asynchronous Design Critique: Getting Feedback

    Asynchronous Design Critique: Getting Feedback

    ” Any feedback?” is perhaps one of the worst ways to ask for suggestions. It’s obscure and unfocused, and it doesn’t give us a sense of what we’re looking for. Great feedback begins sooner than we might anticipate: it begins with the 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 study. The best way to ask for feedback is also to build strong questions, just like we wouldn’t do any studies without the correct questions to get the insight we need.

    Design criticism 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 good research. Problem, generation, and evaluation. Let’s take a closer look at each of those.

    The query

    Being available to input is important, but we need to be specific about what we’re looking for. Any comments,” What do you think,” or” I’d love to hear your view” at the conclusion of a presentation are likely to generate a lot of divergent thoughts, 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? A number of elements are involved. One is that we don’t often consider asking as a part of the input approach. Another is how healthy it is to keep the issue open and assume that everyone else will agree. Another is that there are frequently no need to be that specific in nonprofessional conversations. In short, we tend to underestimate the importance of the issues, so we don’t work on improving them.

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

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

    The term” level” refers to each stage of the process, which is, in our case, the design phase. The kind of feedback changes as the consumer research moves forward to the final design. But within a single stage, one might also examine whether some assumptions are correct and whether there’s been a suitable language of the amassed input into updated designs as the job has evolved. The levels of consumer experience could serve as a starting point for possible questions. What are the project priorities, in your opinion? User requirements? Funnality? the glad Contact design? Data structures Interface pattern Navigation style? physical style Brand?

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

    • Features: Is it desired to automate accounts creation?
    • Interaction style: Take a look at the updated flowing and let me know if there are any steps or error 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?
    • User interface design: What do you think about the top-of-the-page problem counter, which makes sure you can see the following 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. Are there any ways to deal with this?
    • The bottom-right corner’s thick messages are clearly visible, but are they sufficient?

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

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

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

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

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

    Asking specific questions can completely change the quality of the feedback that you receive. People with less refined criticism will now be able to provide more actionable feedback, and even expert designers will appreciate the clarity and effectiveness gained from concentrating solely on what’s needed. 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’s probably not the most effective way to go about designing critiques, but even if I don’t want to be too prescriptive, it might work for some teams.

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

    Using iteration posts has a number of benefits:

      The layouter can review the feedback from each iteration and get ready for the next one by creating a rhythm in the design work.
    • It makes decisions visible for future review, and conversations are likewise always available.
    • It keeps track of how the design evolved over time.
    • Depending on the tool, it might also make it simpler to collect and act on feedback.

    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. To avoid having to search through information from multiple posts, the goal is to provide context and repeat what is necessary to complete each iteration post. The most recent iteration post will provide all I need to know about the most recent design.

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

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

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

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

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

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

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

    I 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 have. 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 describe a design as complete enough to be worked on, even if there might be some bits that still need more attention and in turn, more iterations would be required, 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, using a different approach is more effective: we can adopt a user-research mindset. Written feedback from teammates, stakeholders, or others can be treated as if it were the result of user interviews and surveys, and we can analyze it accordingly.

    Asynchronous feedback is particularly effective around these friction points because of this shift’s significant benefits:

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

    The first friction 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 of a problem with it. Sometimes, however, some solutions may require more in-depth discussions, and the number of responses can quickly rise, which can cause tension between trying to be a good team player by responding to everyone and attempting the next design iteration. This might be especially true if the person who’s replying is a stakeholder or someone directly involved in the project who we feel that we need to listen to. It’s human nature to try to accommodate those we care about, and we need to accept that this pressure is completely normal. When responding to all comments, it can be effective, but when we consider a design critique more like user research, we realize that we don’t need to respond to every comment, and there are alternatives in asynchronous spaces:

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

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

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

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

    The personal stake we might have in relation to the design could be the third friction point, which might cause us to feel defensive if the review turned out to be more of a discussion. Treating feedback as user research helps us create a healthy distance between the people giving us feedback and our ego ( because yes, even if we don’t want to admit it, it’s there ). In the end, putting everything in aggregate 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 designer who is in charge of the project. In the end, everyone has their area of specialization, and the designer has the most background and knowledge to make the best choice. And by listening to the feedback that you’ve received, you’re making sure that it’s also the best and most balanced decision.

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

  • Asynchronous Design Critique: Giving Feedback

    Asynchronous Design Critique: Giving Feedback

    One of the most successful soft skills we have at our disposal is opinions, in whatever form it takes, and whatever it may be called. It helps us collaborate to improve our designs while developing our own abilities and perspectives.

    Feedback is also one of the most underestimated equipment, and generally by assuming that we’re now great at it, we settle, forgetting that it’s a skill that can be trained, grown, and improved. Bad opinions can lead to conflict on projects, lower morale, and long-term, undermine trust and teamwork. Quality suggestions can have a revolutionary effect.

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

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

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

    The information

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

    This formula is typically used to provide feedback to people, but it also fits really well in a pattern criticism because it finally addresses one of the main inquiries that we work on: What? Where? Why? How? Imagine that you’re giving some comments about some pattern function that spans several screens, like an onboard movement: there are some pages shown, a stream blueprint, and an outline of the decisions made. You notice something that needs to be improved. You’ll have a mental model that can help you be more precise and effective if you keep the three components of the equation in mind.

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

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

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

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

    Impact is about the why. Just pointing out a UI element might sometimes be enough if the issue may be obvious, but more often than not, you should add an explanation of what you’re pointing out.

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

    The question approach is intended to give open guidance by encouraging the designer to think critically while receiving the feedback. Notably, Lara’s equation includes a second approach: request, which instead provides instructions on how to find a particular solution. While that’s a viable option for feedback in general, for design critiques, in my experience, defaulting to the question approach usually reaches the best solutions because designers are generally more comfortable in being given an open space to explore.

    For the question approach, the difference between the two can be demonstrated as an illustration:

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

    Or, for the request approach:

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

    In some situations, adding an additional reason why you think the suggestion is better might be helpful at this point.

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

    Choosing between the request and question approaches can occasionally be a matter of personal preference. I did rounds of anonymous feedback and reviewed feedback with other people before putting a lot of effort into improving it a while ago. After a few rounds of this work and a year later, I got a positive response: my feedback came across as effective and grounded. until I switched teams. Surprise surprise, one particular person gave me a lot of negative feedback. The reason is that I had previously tried not to be prescriptive in my advice—because the people who I was previously working with preferred the open-ended question format over the request style of suggestions. However, there was a member of this other team who preferred specific guidance. So I changed my feedback so that it included requests.

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

    No, this style of feedback is actually efficient because the length here is a byproduct of clarity, and spending time giving this kind of feedback can provide exactly enough information for a good fix. Additionally, it can reduce misunderstandings and back-and-forth conversations in the future, boosting overall collaboration’s effectiveness and efficiency beyond the single comment. Consider the example above where the feedback would be simply,” Let’s make sure that all screens have the same two forward and back buttons.” The designer receiving this feedback wouldn’t have much to go by, so they might just apply the change. In later iterations, the interface might change or new features might be introduced, and perhaps that change no longer makes sense. Without explaining the why, the designer might assume that the change is one of consistency, but what if it wasn’t? So there could now be an underlying concern that changing the buttons would be perceived as a regression.

    Yes, this type of feedback is not always effective because some comments don’t always need to be thorough, some may be obvious because of the team’s internal knowledge, which may lead to some explanations of the whys.

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

    The atmosphere

    The foundation of feedback is well-rounded content, but that’s not really enough. The soft skills of the person who’s providing the critique can multiply the likelihood that the feedback will be well received and understood. It has been demonstrated that only positive feedback can lead to lasting change in people, and tone alone can determine whether content is rejected or welcomed.

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

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

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

    Attitude is the equivalent of intent, and in the context of person-to-person feedback, it can be referred to as radical candor. Before writing, it’s important to make sure the person we’re writing will actually benefit them and improve the overall project. Sometimes it might be difficult to reflect on this because we might not want to admit our deep appreciation for that person. Hopefully that’s not the case, but that can happen, and that’s okay. How would I write if I really cared about them, aside from acknowledging and having that to help you make up for it? How can I stop being a passive tyrant? How can I be more constructive?

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

    I asked for some feedback on how I gave it a while back. I was given some sound advice, but I also got a surprise comment. They pointed out that when I wrote” Oh, ]… ]”, I made them feel stupid. That’s not what I meant to say! I just realized that I had been giving them feedback for months and that I had always made them feel foolish. I was horrified … but also thankful. I quickly changed the way I typed “oh” into my list of replaced words (your choice between aText, TextExpander, or others ), so that it was instantly deleted when I typed “oh.”

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

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

    The format

    Asynchronous feedback also has a significant inherent benefit: we can devote more time to making sure that the suggestions ‘ clarity of communication and actionability fulfill two main objectives.

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

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

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

    We often focus on the negatives, trying to outline all the things that could be done better. That’s obviously important, but it’s even more crucial to concentrate on the positives, especially if you saw improvement in the previous iteration. Although this may seem superfluous, it’s important to remember that design has a number of possible solutions to each problem. So pointing out that the design solution that was chosen is good and explaining why it’s good has two major benefits: it confirms that the approach taken was solid, and it helps to ground your negative feedback. Sharing positive feedback can help prevent regressions in the long run because those things will have been identified as crucial. Positive feedback can also help, as an added bonus, prevent impostor syndrome.

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

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

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

    Emojis have been a method I’ve personally used to enhance the bullet points in some situations. So a red square � � means that it’s something that I consider blocking, a yellow diamond � � is something that I can be convinced otherwise, but it seems to me that it should be changed, and a green circle � � is a detailed, positive confirmation. A blue spiral is also used for either something I’m uncertain about, an exploration, an open alternative, or just a note. However, I’d only use this strategy on teams where I’ve already established a high level of trust because it might turn out to be quite demoralizing if I deliver a lot of red squares and change how I communicate that.

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

    • 🔶 Navigation—I anticipate one to go forward and the other to go back when I see these two buttons. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.
    • Overall, I believe the page is strong, and this is a good candidate for our version 1. 1.0 release candidate.
    • � � Metrics—Good improvement in the buttons on the metrics area, the improved contrast and new focus style make them more accessible.
    • Button Style: Using the green accent in this context, which conveys that it is a positive action because green is typically seen as a confirmation color. Do we need to look for a different color?
    • 🔶Tiles—Given the number of items on the page, and the overall page hierarchy, it seems to me that the tiles shouldn’t be using the Subtitle 1 style but the Subtitle 2 style. This will help maintain consistency in the visual hierarchy.
    • Background: A light texture is effective, but I’m not sure if doing so will cause too much noise on this kind of page. What is the thinking in using that?

    What about using Figma or another design tool that enables in-place feedback to provide feedback directly? These are generally difficult to use because they conceal discussions and are harder to follow, but in the right setting, they can be very effective. Just make sure that each of the comments is separate so that it’s easier to match each discussion to a single task, similar to the idea of splitting mentioned above.

    Say the obvious, please. Sometimes we might feel that something is clearly right or wrong, and we don’t say it. Or sometimes we might have a doubt that we don’t express because the question might sound stupid. Say it, that’s fine. Don’t hold it back, though, because you might need to change the phrasing a little to make the reader feel more at ease. Good feedback is transparent, even when it may be obvious.

    Asynchronous feedback also has the benefit of automatically guiding decisions, according to writing. Why did we do this, especially in large projects? could be a question that pops up from time to time, and there’s nothing better than open, transparent discussions that can be reviewed at any time. I advise using software to prevent these discussions from being hidden after they have been resolved for this reason.

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

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