Category: Blog

I’ve been fascinated by movies since I was a child. I loved the figures and the excitement—but most of all the reports. I aspired to be an artist. And I believed that I’d get to do the things that Indiana Jones did and go on exciting activities. I also came up with concept films that my friends and I could create and sun in. But they never went any farther. However, I did end up working in user experience ( UI). Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer research is story. And you must show a compelling story to entice stakeholders, such as the product team and decision-makers, to learn more in order to get the most out of consumer research.

Think of your favourite film. It more than likely follows a three-act construction that’s frequently seen in movies: the layout, the conflict, and the resolution. The second act shows what exists now, and it helps you get to understand the characters and the challenges and problems that they face. Act two sets the scene for the fight and introduces the activity. Here, issues grow or get worse. The decision is the third and final action. This is where the issues are resolved and the figures learn and change. This structure, in my opinion, is also a fantastic way to think about customer research, and it might be particularly useful for explaining user research to others.

Use story as a framework for conducting analysis

It’s sad to say, but many have come to see studies as being dispensable. Research is typically one of the first things to go when finances or deadlines are tight. Instead of investing in study, some goods professionals rely on manufacturers or—worse—their personal judgment to make the “right” options for users based on their experience or accepted best practices. That may lead some groups, but that approach can so easily miss the chance to solve people ‘ real issues. To be user-centered, this is something we really avoid. User study improves pattern. It keeps it on record, pointing to problems and opportunities. Being aware of the problems with your goods and taking action can help you be ahead of your competition.

In the three-act structure, each action corresponds to a part of the process, and each part is important to telling the whole story. Let’s take a look at the various functions and how they relate to consumer study.

Act one: layout

Fundamental analysis comes in handy because the layout is all about comprehending the background. Basic research ( also called conceptual, discovery, or preliminary research ) helps you understand people and identify their problems. You’re learning about the difficulties people face now, what options are available, and how those challenges impact them, just like in the films. To do basic research, you may conduct cultural inquiries or journal studies ( or both! ), which may assist you in identifying both prospects and problems. It doesn’t need to get a great investment in time or money.

Erika Hall discusses the most effective anthropology, which can be as straightforward as spending 15 hours with a customer and asking them to” Walk me through your morning yesterday.” That’s it. Give that one ask. Opened up and listen to them for 15 days. Do everything in your power to keep yourself and your pursuits out of it. Bam, you’re doing ethnography”. Hall predicts that “[This ] will likely prove quite fascinating. In the very unlikely event that you didn’t learn anything new or helpful, carry on with increased confidence in your way”.

This makes sense to me in all its entirety. And I love that this makes consumer studies so visible. You don’t need to make a lot of paperwork; you can only attract people and do it! This can offer a wealth of knowledge about your customers, and it’ll help you better understand them and what’s going on in their life. That’s exactly what work one is all about: understanding where people are coming from.

Maybe Spool talks about the importance of basic research and how it may type the bulk of your research. If you can supplement what you’ve heard in the basic studies by using any more user data that you can obtain, such as surveys or analytics, to make recommendations that may need to be investigated further, you might as well use those that can be drawn from those that you can obtain. Together, all this information creates a clearer picture of the state of things and all its deficiencies. And that’s the start of a gripping tale. It’s the place in the story where you realize that the principal characters—or the people in this case—are facing issues that they need to conquer. This is where you begin to develop compassion for the characters and support their success, much like in films. And finally participants are now doing the same. Their concern may be with their company, which could be losing money because consumers are unable to complete specific tasks. Or probably they do connect with customers ‘ problems. In either case, work one serves as your main strategy to pique the interest and interest of the participants.

When partners begin to understand the value of basic research, that is open doors to more opportunities that involve users in the decision-making approach. And that can help goods team become more user-centric. This gains everyone—users, the goods, and partners. It’s similar to winning an Oscar in terms of filmmaking because it frequently results in your goods receiving good reviews and success. And this can be an opportunity for participants to repeat this process with different products. The secret to this method is storytelling, and knowing how to tell a compelling story is the only way to entice partners to do more research.

This brings us to work two, where you incrementally examine a design or idea to see whether it addresses the problems.

Act two: fight

Act two is all about digging deeper into the issues that you identified in operate one. In order to evaluate a potential solution ( such as a design ), you typically conduct vertical research, such as usability tests, to see if it addresses the problems you identified. The issues may include unfulfilled needs or problems with a circulation or procedure that’s tripping users away. More problems will come up in the process, much like in the second action of a film. It’s here that you learn more about the figures as they grow and develop through this work.

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

There are parallels with storytelling here too, if you try to tell a story with too many characters, the plot may get lost. With fewer participants, each user’s struggles will be more easily recalled and shared with other parties when discussing the research. This can help convey the issues that need to be addressed while also highlighting the value of doing the research in the first place.

Usability tests have been conducted in person for decades, but you can also do them remotely using software like Microsoft Teams, Zoom, or other teleconferencing software. This approach has become increasingly popular since the beginning of the pandemic, and it works well. You might consider in-person usability tests like attending a play and remote sessions as more of a movie watching experience. There are advantages and disadvantages to each. Much more in-depth research is conducted on user experience. Stakeholders can experience the sessions with other stakeholders. You also get real-time feedback on what they’re seeing, including surprises, disagreements, and discussions about them. Much like going to a play, where audiences get to take in the stage, the costumes, the lighting, and the actors ‘ interactions, in-person research lets you see users up close, including their body language, how they interact with the moderator, and how the scene is set up.

If conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may be very different from one another. You can take usability testing into the field by creating a replica of the space where users interact with the product and then conduct your research there. Or you can meet users at their location to conduct your research. With either option, you get to see how things work in context, things come up that wouldn’t have in a lab environment—and conversion can shift in entirely different directions. You have less control over how these sessions end as researchers, but this can occasionally help you understand users even better. Meeting users where they are can provide clues to the external forces that could be affecting how they use your product. In-person usability tests add a level of detail that remote usability tests frequently lack.

That’s not to say that the “movies” —remote sessions—aren’t a good option. A wider audience can be obtained from remote sessions. They allow a lot more stakeholders to be involved in the research and to see what’s going on. Additionally, they make access to a much wider user base geographically. But with any remote session there is the potential of time wasted if participants can’t log in or get their microphone working.

You can ask real users questions to understand their thoughts and understanding of the solution as a result of usability testing, whether it is conducted remotely or in person. This can help you not only identify problems but also glean why they’re problems in the first place. Additionally, you can test your own hypotheses and determine whether your reasoning is correct. By the end of the sessions, you’ll have a much clearer picture of how usable the designs are and whether they work for their intended purposes. Act two is where the excitement is at the heart of the narrative, but there are also potential surprises. This is equally true of usability tests. Unexpected things that are said by participants frequently alter how you view things, and these unexpected developments in the story can lead to unexpected turns in your perception.

Unfortunately, user research is sometimes seen as expendable. Usability testing is also frequently the only research technique that some stakeholders believe they ever need, and too frequently. In fact, if the designs that you’re evaluating in the usability test aren’t grounded in a solid understanding of your users ( foundational research ), there’s not much to be gained by doing usability testing in the first place. Because you narrow down the subject matter of your feedback without understanding the needs of the users. As a result, there’s no way of knowing whether the designs might solve a problem that users have. In the context of a usability test, it’s only feedback on a particular design.

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

In act two, stakeholders will—hopefully—get to watch the story unfold in the user sessions, which creates the conflict and tension in the current design by surfacing their highs and lows. And in turn, this can encourage stakeholders to take action on the issues raised.

Act three: resolution

The third act is about resolving the issues from the first two acts, while the first two acts are about understanding the background and the tensions that can compel stakeholders to take action. While it’s important to have an audience for the first two acts, it’s crucial that they stick around for the final act. That includes all members of the product team, including developers, UX experts, business analysts, delivery managers, product managers, and any other interested parties. It allows the whole team to hear users ‘ feedback together, ask questions, and discuss what’s possible within the project’s constraints. Additionally, it enables the UX design and research teams to clarify, suggest alternatives, or provide more context for their choices. So you can get everyone on the same page and get agreement on the way forward.

This act is primarily told in voiceover with some audience participation. The researcher is the narrator, who paints a picture of the issues and what the future of the product could look like given the things that the team has learned. They offer the stakeholders their suggestions and suggestions for how to create this vision.

Nancy Duarte in the Harvard Business Review offers an approach to structuring presentations that follow a persuasive story. The most effective presenters employ the same methods as great storytellers: By reaffirming the status quo and then revealing a better way, they create a conflict that needs to be resolved, writes Duarte. ” That tension helps them persuade the audience to adopt a new mindset or behave differently”.

This type of structure aligns well with research results, and particularly results from usability tests. It provides proof for “what is “—the issues you’ve identified. And “what could be “—your recommendations on how to address them. And so forth.

You can reinforce your recommendations with examples of things that competitors are doing that could address these issues or with examples where competitors are gaining an edge. Or they can be as visual as quick sketches of a potential solution to a problem. These can help generate conversation and momentum. And this continues until the session is over, when you’ve concluded by bridging the gaps and offering suggestions for improvement. This is the part where you reiterate the main themes or problems and what they mean for the product—the denouement of the story. This stage provides stakeholders with the next steps, and hopefully, the motivation to take those steps as well!

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

Act one: You meet the protagonists ( the users ) and the antagonists ( the problems affecting users ). This is the plot’s beginning. In act one, researchers might use methods including contextual inquiry, ethnography, diary studies, surveys, and analytics. These techniques can produce personas, empathy maps, user journeys, and analytics dashboards as output.

Act two: Next, there’s character development. The protagonists encounter problems and difficulties, which they must overcome, and there is conflict and tension. In act two, researchers might use methods including usability testing, competitive benchmarking, and heuristics evaluation. Usability findings reports, UX strategy documents, usability guidelines, and best practices can be included in the output of these.

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

The researcher performs a number of tasks: they are the producer, the director, and the storyteller. The participants have a small role, but they are significant characters ( in the research ). And the audience are the stakeholders. But the most important thing is to get the story right and to use storytelling to tell users ‘ stories through research. In the end, the parties should leave with a goal and an eagerness to fix the product’s flaws.

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

The personalization space is real, between the dream of getting it right and the fear of it going wrong ( like when we encounter “persofails” in the spirit of a company that regularly asks regular people to buy more toilet seats ). It’s an particularly confusing place to be a modern professional without a map, a map, or a strategy.

Because successful personalization is so dependent on each group’s skill, technology, and market position, there are no Lonely Planet and some tour guides for those of you who want to personalize.

But you can ensure that your group has packed its bags rationally.

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

It’s known as prepersonalization.

Behind the audio

Take into account Spotify’s DJ element, which debuted this year.

We’re used to seeing the polished final outcome of a personalization function. 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. Before any customisation have goes live in your product or service, it lives amid a delay of valuable ideas for expressing consumer experiences more automatically.

How do you decide where to position personalization wagers? How do you design regular interactions that didn’t journey up users or—worse—breed mistrust? We’ve discovered that several budgeted programs second required one or more workshops to join key stakeholders and domestic customers of the technology in order to justify their continuing investments. Make it count.

We’ve witnessed the same evolution up near with our clients, from big tech to burgeoning companies. In our encounters with working on small and large customisation efforts, a program’s best monitor record—and its capacity to weather tough questions, work steadily toward shared answers, and manage its design and engineering efforts—turns on how successfully these prepersonalization activities play out.

Effective workshops consistently distinguish successful future endeavors from unsuccessful ones, saving countless hours of time, resources, and overall well-being in the process.

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

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

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

Set the timer for the kitchen.

How long does it take to cook up a prepersonalization workshop? The evaluation activities that we suggest including can ( and frequently do ) last for weeks. For the core workshop, we recommend aiming for two to three days. Here’s a summary of our more general approach as well as information on the crucial first-day activities.

The full arc of the wider workshop is threefold:

Kickstart: This specifies the terms of your engagement as you concentrate on both your team’s and your team’s readiness and drive.
1. Plan your work: This is the heart of the card-based workshop activities where you specify a plan of attack and the scope of work.
2. Work your plan: This stage essentially entails creating a competitive environment in which team members can individually present their own pilots that each contain a proof-of-concept project, its business case, and its operating model.

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

Kickstart: Apt your appetite

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

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

It’s all about setting the tone. What are the possible paths for the practice in your organization? Here’s a long-form primer and a strategic framework for a broader 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. Size your own build here. This will help to draw attention to the benefits of ongoing investment as well as the difference between what you currently offer and what you intend to offer in the future.

Next, have your team plot each idea on the following 2×2 grid, which lays out the four enduring arguments for a personalized experience. This is 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 decide where they would like to place your company’s emphasis on your product or service. Naturally, you can’t prioritize all of them. Here, the goal is to show how various departments may view their own benefits from the effort, which can vary 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 your customer journey well documented? Will data and privacy protection be a significant challenge? Do you have content metadata needs that you have to address? ( We’re pretty sure you do; it’s just a matter of recognizing the need’s magnitude and its solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six intractable behaviors that prevent progress.

Effectively collaborating and managing expectations is critical to your success. Consider the potential obstacles to your advancement in the future. Press the participants to name specific steps to overcome or mitigate those barriers in your organization. According to research, personalization initiatives face a number of common obstacles.

At this point, you’ve hopefully discussed sample interactions, emphasized a key area of benefit, and flagged key gaps? You’re all set to go on, good.

Hit that 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. Their capabilities are broad and potent, and they give you a variety of ways to organize your company. This presents the question: Where do you begin when you’re configuring a connected experience?

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

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

The dishes will be made from recipes, which have predetermined ingredients.

Verify your ingredients

You’ll ensure that you have everything you need to create your desired interaction ( or that you can determine what needs to be added to your pantry like a good product manager ) and that you have validated with the right stakeholders present. These ingredients include the audience that you’re targeting, content and design elements, the context for the interaction, and your measure for how it’ll come together.

This doesn’t just involve identifying requirements. Documenting your personalizations as a series of if-then statements lets the team:

1. compare findings to a common strategy 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.

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

Create a recipe.

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

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

Five years ago, we created these cards and card categories. We regularly play-test their fit with conference audiences and clients. 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. Nurture personalization: When a guest or an unknown visitor interacts with a product title, a banner or alert bar appears that makes it easier for them to encounter a related title they may want to read, saving them time.
2. Welcome automation: An email is sent to a newly registered user to highlight the breadth of the content catalog and convert them to happy subscribers.
3. Winback automation: Before their subscription lapses or after a recent failed renewal, a user is sent an email that gives them a promotional offer to suggest that they reconsider renewing or to remind them to renew.

We’ve also found that cocreating the recipes themselves can sometimes be the most effective way to start brainstorming 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, which shift from focusing on cookbooks to focusing on customers, might seem more nuanced. Individual” cooks” will pitch their recipes to the team, using a common jobs-to-be-done format so that measurability and results are baked in, and from there, the resulting collection will be prioritized for finished design and delivery to production.

Better architecture is required for better kitchens.

Simplifying a customer experience is a complicated effort for those who are inside delivering it. 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“.

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

You can’t stand the heat, in fact…

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a deliberate and cooperative approach will produce the desired outcome. So banish the dream kitchen. Instead, head to the test kitchen to burn off the fantastical ideas that the doers in your organization have in store for time, to preserve job satisfaction and security, and to avoid unnecessary distractions. There are meals to serve and mouths to feed.

This framework of the workshop gives you a strong chance at long-term success as well as solid ground. Wiring up your information layer isn’t an overnight affair. However, you’ll have solid ground for success if you use the same cookbook and the same recipes. We designed these activities to make your organization’s needs concrete and clear, long before the hazards pile up.

Although there are associated costs associated with purchasing this kind of technology and product design, your time well spent is on sizing up and confronting your unique situation and digital skills. Don’t squander it. The pudding is the proof, as they say.

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 development of internet requirements

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 improved server-side software, the first period of internet programs started with content-management techniques (especially those used in blogs like Blogger, Grey Matter, Movable Type, and WordPress ) In the mid-2000s, AJAX opened gates for sequential interaction between the front end and back close. Pages was now revise their content without having to reload it. A grain of Script frameworks like Prototype, YUI, and ruby arose to aid developers develop more credible client-side conversation across browsers that had wildly varying levels of standards support. Techniques like photo replacement enable skilled manufacturers and designers to use fonts of their choosing. And technology like Flash made it possible to include movies, sports, and even more engagement.

The economy was reenergized by these new tools, requirements, and methods in many ways. Web style flourished as manufacturers and designers explored more different styles and designs. However, we also depend on numerous tricks. Early CSS was a huge improvement over table-based layouts when it came to basic layout and text styling, but its limitations at the time meant that designers and developers still relied heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds for the appearance of full-length columns (among other hacks ). All kinds of nested floats or absolute positioning ( or both ) were necessary for complicated layouts. Display and photo substitute for specialty styles was a great start toward varying the designs from the big five, but both tricks introduced convenience and efficiency issues. And JavaScript libraries made it simple for anyone to add a dash of interaction to pages, even at the expense of double, even quadrupling, the download size of basic websites.

The web as software platform

The balance between the front end and the back end continued to improve, leading to the development of the current web application era. 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. Along with these tools, there were additional options, such as collaborative build automation, collaborative version control, and shared package libraries. What was once primarily an environment for linked documents became a realm of infinite possibilities.

Mobile devices increased in their capabilities as well, and they gave us access to the internet in our pockets at the same time. Mobile apps and responsive design opened up opportunities for new interactions anywhere and any time.

This fusion of potent mobile devices and potent development tools contributed to the growth of social media and other centralized tools for user interaction and consumption. As it became easier and more common to connect with others directly on Twitter, Facebook, and even Slack, the desire for hosted personal sites waned. Social media provided connections on a global scale, with both positive and negative outcomes.

Want a much more extensive history of how we got here, with some other takes on ways that we can improve? ” Of Time and the Web” was written by Jeremy Keith. Or check out the” Web Design History Timeline” at the Web Design Museum. A fun tour through” Internet Artifacts” is also provided by Neal Agarwal.

Where we are now

It seems like we’ve reached yet another significant turning point in recent years. As social-media platforms fracture and wane, there’s been a growing interest in owning our own content again. There are many different ways to create a website, from the tried-and-true classic of hosting plain HTML files to static site generators to content management systems of all varieties. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. The IndieWeb‘s Webmentions, RSS, ActivityPub, and other tools can assist with this, but they’re still largely underdeveloped and difficult to use for the less geeky. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.

Especially with efforts like Interop, browser support for CSS, JavaScript, and other standards like web components has increased. New technologies gain support across the board in a fraction of the time that they used to. I frequently find out about a new feature and check its browser support only to discover that its coverage has already exceeded 80 %. Nowadays, the barrier to using newer techniques often isn’t browser support but simply the limits of how quickly designers and developers can learn what’s available and how to adopt it.

We can now prototype almost any idea with just a few commands and a few lines of code. All the tools that we now have available make it easier than ever to start something new. However, as we upgrade and maintain these frameworks, we eventually pay the upfront costs that these frameworks may initially save in terms of our technical debt.

If we rely on third-party frameworks, adopting new standards can sometimes take longer since we may have to wait for those frameworks to adopt those standards. These frameworks, which previously made it easier to adopt new techniques sooner, have since evolved into obstacles. These same frameworks often come with performance costs too, forcing users to wait for scripts to load before they can read or interact with pages. And frequently, when scripts fail ( whether due to poor code, network problems, or other environmental factors ), users are left with blank or broken pages.

Where do we go from here?

Hacks of today help to shape standards for the future. 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 choose not to replace them. So what can we do to create the future we want for the web?

Build for the long haul. Optimize for performance, for accessibility, and for the user. weigh the costs of those user-friendly tools. They may make your job a little easier today, but how do they affect everything else? What is the price to the users? To future developers? to the adoption of standards? Sometimes the convenience may be worth it. Sometimes it’s just a hack that you’ve gotten used to. And sometimes it’s holding you back from even better options.

Start with standards. Standards continue to evolve over time, but browsers have done a remarkably good job of continuing to support older standards. Not all third-party frameworks are the same. Sites built with even the hackiest of HTML from the’ 90s still work just fine today. The same can’t always be said of websites created with frameworks even after a few years.

Design with care. Consider the effects of each choice, whether your craft is code, pixels, or processes. The convenience of many a modern tool comes at the cost of not always understanding the underlying decisions that have led to its design and not always considering the impact that those decisions can have. Use the time saved by modern tools to think more carefully and make decisions with care rather than rushing to “move fast and break things”

Always be learning. If you constantly learn, you also develop. 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! The ultimate experiment is this web that we’ve created. It’s the single largest human endeavor in history, and yet each of us can create our own pocket within it. Be brave and try something new. Build a playground for ideas. Create absurd experiments in your own crazy science lab. Start your own small business. There has never been a place where we have more room to be creative, take risks, and discover our potential.

Share and amplify. As you play, experiment, and learn, share what has 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 ahead and create a masterpiece.

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 incorporate our values into the products we produce, and let’s improve the world for everyone. Create that thing that only you are uniquely qualified to make. Then, share it, improve it, re-create it, or create something new. Learn. Make. Share. Grow. Rinse and repeat. Everything will change whenever you believe you have mastered the web.

I’d like you to consider this a “yes … and” piece to complement Joe’s post. I’m just trying to contradict what he’s saying, but I’m just trying to give some context to initiatives and opportunities where AI can make a difference for people with disabilities. To be clear, I’m not saying that there aren’t real challenges or pressing problems with AI that need to be addressed; there are, and we’ve needed to address them, like, yesterday; instead, I want to take a moment to talk about what’s possible so that we can get it one day.

Other words

Joe’s article spends a lot of time examining how computer vision versions can create other words. He raises a lot of valid points about the state of the world right now. And while computer-vision concepts continue to improve in the quality and complexity of information in their information, their benefits aren’t wonderful. He argues to be accurate that the state of image research is currently very poor, especially for some graphic types, in large part due to the 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 ( should probably have descriptions ) and those that are purely decorative ( couldn’t possibly need a description ) either. However, I still think there’s possible in this area.

As Joe points out, alt text publishing via human-in-the-loop should be a given. And if AI can intervene and provide a starting point for alt text, even if the quick reads,” What is this BS?” That’s certainly correct at all … Let me try to offer a starting point— I think that’s a win.

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

While complex images—like graphs and charts—are challenging to describe in any sort of succinct way ( even for humans ), the image example shared in the GPT4 announcement points to an interesting opportunity as well. Let’s say you came across a map that was simply the description of the chart’s title 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. ) If your website knew that that picture was a pie graph ( because an ship model concluded this ), imagine a world where people could ask questions like these about the creative:

• Would more people use smartphones or other types of phones?
• How many more?
• Is there a group of people that don’t fall into either of these pots?
• That number, how some?

For a moment, the chance to learn more about graphics and data in this way could be innovative for people who are blind and low vision as well as for those with various types of color blindness, cognitive impairments, and other issues. Putting aside the experiences of large language model ( LLM) hallucinations. It could also be useful in educational contexts to help people who can see these charts, as is, to understand the data in the charts.

What if you could ask your browser to make a complicated chart simpler? What if you demanded that the line graph be isolated into just one line? What if you could ask your browser to transpose the colors of the different lines to work better for form of color blindness you have? What if you demanded that it switch colors in favor of patterns? That seems like a possibility given the chat-based interfaces and our current ability to manipulate images in today’s AI tools.

Now imagine a purpose-built model that could extract the information from that chart and convert it to another format. Perhaps it could convert that pie chart (or, better yet, a series of pie charts ) into more usable ( and useful ) formats, like spreadsheets, for instance. That would be incredible!

Matching algorithms

When Safiya Umoja Noble chose to put her book Algorithms of Oppression, she hit the nail on the head. Although her book focused on the ways that search engines can foster racism, I believe it’s equally true that all computer models have the potential to foster conflict, prejudice, and intolerance. Whether it’s Twitter always showing you the latest tweet from a bored billionaire, YouTube sending us into a Q-hole, or Instagram warping our ideas of what natural bodies look like, we know that poorly authored and maintained algorithms are incredibly harmful. Many of these are the result of a lack of diversity in the people who create and build them. However, when these platforms are built with inclusive features in mind, there is 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 takes into account each work environment, communication strategies for each job, and other factors. Mentra made the decision to change the script when it came to traditional employment websites because it was run by neurodivergent people. They use their algorithm to propose available candidates to companies, who can then connect with job seekers that they are interested in, reducing the emotional and physical labor on the job-seeker side of things.

When more people with disabilities are involved in developing algorithms, this can lower the likelihood that these algorithms will harm their communities. Diverse teams are crucial because of this.

Imagine that a social media company’s recommendation engine was tuned to analyze who you’re following and if it was tuned to prioritize follow recommendations for people who talked about similar things but who were different in some key ways from your existing sphere of influence. For instance, if you followed a group of nondisabled white male academics who spoke about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also speak about AI. If you followed its advice, you might be able to understand what is happening in the AI field more fully and nuancedly. 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 assist people with disabilities

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

Voice preservation You might have heard about the voice-preserve offerings from Microsoft, Acapela, or others, or have seen the VALL-E paper or Apple’s Global Accessibility Awareness Day announcement. It’s possible to train an AI model to replicate your voice, which can be a tremendous boon for people who have ALS ( Lou Gehrig’s disease ) or motor-neuron disease or other medical conditions that can lead to an inability to talk. We need to approach this tech responsibly because it has the potential to have a truly transformative impact, which is why it can also be used to create audio deepfakes.
• Voice recognition. Researchers like those in the Speech Accessibility Project are paying people with disabilities for their help in collecting recordings of people with atypical speech. As I type, they are currently hiring people with Parkinson’s and related conditions, and they intend to expand this list as the project develops. More people with disabilities will be able to use voice assistants, dictation software, and voice-response services as a result of this research, which will lead to more inclusive data sets that enable them to use their computers and other devices more effectively and with just their voices.
• Text transformation. The most recent generation of LLMs is quite capable of changing existing text without giving off hallucinations. This is incredibly empowering for those who have cognitive disabilities and who may benefit from text summaries, simplified versions, or even text that has been prepared for Bionic Reading.

The importance of diverse teams and data

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

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

Want a non-binary language model? You may be able to use existing data sets to build a filter that can intercept and remediate ableist language before it reaches readers. Despite this, AI models won’t soon replace human copy editors when it comes to sensitivity reading.

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 doubts about how dangerous AI will be for people today, tomorrow, and for the rest of the world. However, I also think we should acknowledge this and make thoughtful, thoughtful, and intentional changes to 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 supporting the development of this article, Ashley Bischoff for providing me with invaluable editorial support, and of course, Joe Dolson for the prompt.

I have a creative side. Alchemy is what I do. It is a puzzle. Instead of letting it get done by me, I do it.

I have a creative side. This brand is never appropriate for all creatives. No everyone see themselves in this manner. Some innovative individuals incorporate technology into their work. That is the way they are, and I take that into account. Perhaps I even have a small envy for them. However, my thinking and being are unique.

It distracts you to apologize and qualify in progress. That’s what my mind does to destroy me. I’ll leave it alone for today. I may come back later to make amends and define. After I’ve said what I originally said. which is difficult enough.

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

Sometimes it does. 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 thought just comes along and it is the best plan and you know it is the best idea.

Sometimes I just keep working until the thought strikes me. Maybe it arrives right away, but I don’t remind people for three days. Often I blurt out the plan so quickly that I didn’t stop myself. like a child who discovered a prize in a box of Cracker Jacks. Maybe I get away with this. Yes, that is the best idea, but maybe others disagree. The majority of the time, they don’t, and I regret that joy has faded.

Passion should only be saved for the meet, when it matters. not the informal gathering that two different gatherings precede that appointment. Nothing understands why we hold these gatherings. We keep saying we’re getting rid of them, but we keep discovering new ways to get them. They occasionally also excel. But occasionally they are a hindrance to the actual job. Depending on what you do and where you do it, the ratio between when conferences are valuable and when they are a sad distraction vary. And who you are and how you go about doing it. I’ll go back and forth once more. I have a creative side. That is the style.

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

Don’t inquire about the procedure. I have a creative side.

I have a creative side. I have no control over my goals. And I have no power over my best tips.

I can nail ahead, fill in the blanks, or use graphics or information, which occasionally works. Often going for a walk is what I can do. There is a Eureka, which has nothing to do with boiling pots and sizzling oil, and I may be making dinner. I frequently have a 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 imagination, in my opinion, comes from that other planet. The one that we enter in goals, and possibly before and after death. But writers should be asking this, and I am not one of them. I have a creative side. And it’s for philosophers to build massive soldiers in their imaginative world that they claim to be true. But that is yet another diversion. And a sad one. Possibly on a much bigger issue than whether or not I am creative. But that’s not how I came around, though.

Often the outcome is mitigation. And suffering. Do you know the actor who is tortured by the cliché? Even when the artist attempts to create a soft drink song, a callback in a worn-out sitcom, or a budget request, that noun is accurate.

Some individuals who detest being called artistic perhaps been closeted artists, but that’s between them and their gods. No offence here, that’s meant. Your assertions are also accurate. My needs are own, though.

Artists acknowledge their work.

Disadvantages know cons, just like real rappers recognize true rappers, just like queers recognize queers. People have a lot of regard for artists. We respect, follow, and nearly deify the excellent ones. Of course, it is dreadful to revere any person. We’ve been given a warning. Better is what we are. We are aware that people are simply people. Because they are clay, like us, they squabble, they are depressed, they regret making the most important decisions, they are weak and hungry, they can be cruel, and they can be as ridiculous as we can. But. But. However, they produce this incredible issue. They give birth to something that may not exist without them and did not exist before them. They are the inspirations ‘ parents. And since it’s only lying there, I suppose I should add that they are the inventor’s mother. Ba ho backside! Okay, that’s all done. Continue.

Creatives denigrate our personal small accomplishments because they are compared to those of the great ones. Wonderful video I‘m not Miyazaki, though. That is glory right then. That is brilliance straight out of the mouth of God. This meagre much creation that I made? It essentially fell off the turnip truck’s again. And the carrots weren’t actually new.

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

I have a creative side. I haven’t worked in advertising in 30 years, but my previous artistic managers have been the ones who make my decisions. They are correct to do that. When it really matters, my brain goes flat because I am too stupid and complacent. There is no treatment for innovative mania.

I have a creative side. Every project I create has a goal that makes Indiana Jones appear older and snoring in a balcony head. The more I pursue my creative endeavors, the faster I progress in my work, and the more I slog through loops and gaze blankly before beginning that task.

I can move ten times more quickly than those who aren’t imaginative, those who have just been creative for a short while, and those who have just had a short time of creative work. Only that I work twice as quickly as they do, putting the work away, just before I do it, When I put my mind to it, I am so confident in my ability to do a great career. I have an addiction to the delay hurry. The climb also terrifies me.

I don’t create anything.

I have a creative side. Never a performer. Though as a boy, I had a dream that I would one day become that. Some of us criticize our abilities and like our own accomplishments because we are not Michelangelos and Warhols. At least we aren’t in elections, which is narcissism.

I have a creative side. Despite my belief in reason and science, my decisions are based on my own senses. and accept both the successes and the calamities that come with them.

I have a creative side. Every term I’ve said these may irritate another artists who have different viewpoints. Ask two artists a problem and find three opinions. No matter how we does think about it, our debate, our passion for it, and our responsibility to our own truth, at least in my opinion, are the best indications that we are creative.

I have a creative side. I lament my lack of taste in the areas of human knowledge that I know quite little, that is to say about everything. And I put my ego before everything else in the areas that are most important to me, 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. Actually, no. Because living is so difficult to handle when you really look at it.

I have a creative side. I think that when I’m gone, some of the good parts of me will stay in the head of at least one additional person, just like a family does.

Working frees me from worrying about my job.

I have a creative side. I worry that my little product will disappear unexpectedly.

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

I have a creative side. I think method is the most amazing secret. I think so strongly that I am actually foolish enough to post an essay I wrote into a tiny machine without having to go through or edit it. I swear I didn’t accomplish this frequently. 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 believe I said it correctly.

This article contains spoilers for Yellowjackets season 3 episode 3. Yellowjackets has always been a show of collective symbolism. The forest speaks to the girls on the team, and the audience is left to listen and wonder what it all means. From the mysterious symbol in the first season to the sounds bellowing out of […]

The post Yellowjackets Season 3 Episode 3 Explained: The Fox, The Man With No Eyes, and The Phone Number appeared first on Den of Geek.

This article contains spoilers for Yellowjackets season 3 episode 3.

Yellowjackets has always been a show of collective symbolism. The forest speaks to the girls on the team, and the audience is left to listen and wonder what it all means. From the mysterious symbol in the first season to the sounds bellowing out of the trees at the beginning of this season, watching this show has been similar to deconstructing all of the colors and objects in a novel during a college English capstone course. 

The latest episode, “Them’s the Brakes,” ups the stakes for the season and introduces a plethora of new symbols while giving more hints about older ones. From the Sopranos-esque dream sequence at the end of the episode to the creepy ice cream shop Van (Lauren Ambrose) and Tai (Tawny Cypress) investigate, it’s time to decipher what exactly is going on in Yellowjackets right now. Let’s get to it!

The Sopranos’ Big Pussy Makes an Appearance

The main storyline in this episode is the girls’ discovery that Coach Scott (Steven Krueger) is alive and hiding in a cave after Mari (Alexa Barajas) returns from an encounter with him in the previous episode. Assuming he burned the cabin down at the end of the second season, the girls are thirsty for answers and an insatiable desire for revenge. 

Shauna (Sophie Nélisse), Van (Liv Hewson), and Akhila (Nia Sondaya) are almost to Coach Scott’s location when they seemingly disappear into a dream-like trance that fans will be familiar with in construct if they enjoyed older HBO classics like The Sopranos and Six Feet Under. They say that dreams are a window into a character’s inner being, but most of what happens in these scenes feels outlandish and hallucinatory. 

Shauna dreams of interacting with her stillborn baby and Van is trapped inside the burning cabin. Akilah’s night in the forest includes a run-in with a talking llama that is voiced by Sopranos actor Vincent Pastore (the actor who played Big Pussy). Diehard fans will probably remember Pussy talking to Tony Soprano (James Gandolfini) in a dream sequence as a fish. Perhaps the llama is a representation of the girls’ guilt for their misdoings so far such as cannibalism. The creators of Yellowjackets might just be hinting at their characters’ psyches through the legendary mob drama of the 2000s. 

Who Is “The Man With No Eyes”? 

“The Man with No Eyes” has been in the show for its entirety, but this spooky dude has only shown up in Tai’s storyline so far. We finally find out where the man originated from when Tai and Van are relaxing on the couch one night and a classic ice cream commercial comes on for Ozzie’s Homemade Ice Cream Parlor. 

Tai is shaken by the revelation that so many of her deathly fears and associations with morbidity have come from something she had forgotten from her childhood. She immediately takes Van to the abandoned ice cream shop to investigate, but the bigger reveal is how the sinister figure might just be haunting the entire team going back to their days stuck in the wilderness.

Viewers were led to believe that the man was only significant to her up to this point, but the dream sequence at the end with Shauna, Van, and Akhila introduces the frightening figure into their subconsciousness, too. The man is stalking the teens outside of a classroom in their dreams. I certainly wonder why the man was only in Tai’s mind so far if the other girls are dreaming about him now? 

Much of the ambiguity in the show has revolved around the mysteries of the forest. Is the wilderness actually supernatural or is it all in the girls’ heads? The source of the eyeless man being an ice cream mascot does more to convince me that maybe the symbol means something different to every character. 

Just because the ice cream shop is where Tai’s encounter was with the Man with No Eyes doesn’t mean her teammates saw it there first. Fans will need to be creative and solve the puzzles on their own for the time being. The only certainty is that this man is a forebear of hopelessness and bad fortune for the Yellowjackets. 

What Does the Fox mean?

Instead of learning more about the Man with No Eyes, Tai and Van find a fox inside of the dilapidated ice cream building. There hasn’t been any reference to a fox yet in the series, so it’s yet another mysterious symbol being introduced before we have answers to the meaning of the other ones. Astute literary readers and young Millenials who chanted “Swiper, No swiping” at their TVs during the days of watching Dora the Explorer will know that foxes usually represent theft, deceit, and slyness. 

I wonder if both the fox and the Man with No Eyes are connected as one complete symbol of the way the wilderness continues to steal the well being of the Yellowjackets even decades after their return to civilization. The present timeline meanders around most of the time, but the one certainty is that these women will not let their pasts die. The trauma of the forest is a thief of the present. 

Try Calling the Ice Cream Shop Phone Number

During the commercial for Ozzie’s there is a phone number that comes up on the screen to call the ice cream shop. Knowing that fans love nothing more than interactive Easter eggs, it would be a huge letdown if nothing was on the other end of the line in real life. Like any curious viewer, I called (732) 858-5242 to find out what this place is all about. 

The phone call flips back and forth between a cheerful voice and a haunting, depressing one. Ice cream flavors, lots of static, and encouragement to call back later are included in the call. The Reddit superfans have plenty of thoughts on what the phone call means and whether we can learn anything about the Man with No Eyes, the ice cream shop, or the fates of the characters through the phone. There is nothing inherently creepy about an ice cream shop, so the significance of these symbols of references are once again probably just figments of Tai’s imagination. Hopefully the writers explore this further and even update the phone call for the fans throughout the rest of the season.

The first three episodes of Yellowjackets season 3 are available to stream on Paramount+ now. New episodes will premiere Fridays on Paramount+ and Sundays at 8 p.m. ET on Showtime.

The post Yellowjackets Season 3 Episode 3 Explained: The Fox, The Man With No Eyes, and The Phone Number appeared first on Den of Geek.

Have the evil people eventually won? James Bond appears to have been bested by a bald person with far too much energy after years of battling megalomaniacs who have plans on the planet. No, no Blofeld. Jeff Bezos, whose business Amazon has only acquired all the James Bond franchise’s artistic freedom. That might be [ …].

The second post James Bond needed a change, but Amazon Isn’t It appeared on Den of Geek.

Spoilers appear in this season three of Yellowjackets season 3.

Yellowjackets has always been a social imagery show. The audience is left to watch the jungle speak and wonder what it all means while the ladies on the staff are speaking to the forest. Watching this present has been related to deconstructing all of the colors and objects in a book during a school English thesis program, from the strange image in the first season to the sounds bellowing out of the trees at the beginning of this season.

The most recent episode,” Them’s the Brakes,” raises the stakes for the entire time while also introducing a number of brand-new symbols and shedding more light on the more well-known ones. It’s time to understand what is actually happening in Yellowjackets right now, from the Sopranos-esque dream sequence at the end of the episode to the spooky ice cream shop Van ( Lauren Ambrose ) and Tai ( Tawny Cypress ) investigate. Let’s get to the point!

Great Pussy from The Sopranos appears in movies

After Mari ( Alexa Barajas ) returns from an encounter with him in the previous episode, the girls discover that Coach Scott ( Steven Krueger ) is still alive and hiding in a cave. The girls have an unquenchable desire for retribution and are lusty for answers if he destroyed the house at the end of the following season. &nbsp,

Fans who enjoyed earlier HBO classics like The Sopranos and Six Feet Under will be familiar with Shauna ( Sophie Nélisse ), Van ( Liv Hewson ), and Akhila ( Nia Sondaya ) are almost to Coach Scott’s location when they ostensibly disappear into a dream-like trance. Although they claim that desires give a character a glimpse into their inner self, the majority of what occurs in these moments is obscene and hallucinogenic.

Van is stranded inside the burning house, but Shauna has aspirations about speaking with her stillborn child. A talking llama is voiced by Sopranos actor Vincent Pastore ( who also acted in the role of Big Pussy ) during Akilah’s night in the forest. In a dream sequence as a fish, Pussy likely recalls talking to Tony Soprano ( James Gandolfini ). The goat might represent the female ‘ guilt over their past crimes, including cannibalism. The famous mob drama of the 2000s may have made some hints about the characters ‘ minds by the Yellowjackets designers. &nbsp,

The Man With No Vision: Who Is He? &nbsp,

Although the entire series has been a part of the show, Tai’s narrative has just recently featured this spooky dude. When Tai and Van are lying on the couch one day and a basic ice cream business for Ozzie’s Homemade Ice Cream Parlor comes on, we eventually learn where the man came from. &nbsp,

Tai is shocked to learn that so many of her childhood memories and associations with mortality stem from events that she had forgotten. Van is taken to the abandoned ice cream shop by her, but what’s more intriguing is how the sinister figure may become haunting the whole crew as they travel through the forest.

The fantasy series at the end with Shauna, Van, and Akhila introduced the terrifying find into their soul, too, leading people to believe that the man was only important to her up to this point. In their goals, the person is following the teenagers outside of a class. If the other ladies are dreaming about him right now, then why the guy was only in Tai’s head so much? &nbsp,

The treasures of the jungle have played a significant role in the show’s confusion. Is the wilderness actually supernatural, or is it all in the girls ‘ minds? The fact that the classic person is an ice cream mascot is more convincing to me than just that. &nbsp,

Simply because Tai’s encounter with the Man with No Eyes took place at the ice cream shop doesn’t imply her colleagues saw it there initially. For the time being, followers will need to be creative and attempt to solve the mysteries on their own. The only thing that is certain is that this guy is a predecessor of despair and awful wealth for the Yellowjackets. &nbsp,

What does the Fox represent?

Tai and Van discover a wolf inside the crumbling ice cream creating to learn more about the Man with No Vision. Since there hasn’t been any wolf references in the sequence, we must wait until we know what the other ones mean. Astute intellectual users and fresh Youngsters who chanted” Swiper, No tapping” at their TVs while watching Dora the Explorer will be aware that rabbits typically represent fraud, deceit, and mischievousness. &nbsp,

I wonder if the Man with No Eyes and the Fox are related as a single, complete representation of how the wilderness continues to rob the Yellowjackets ‘ well-being decades after their return to civilization. The current timeline varies a lot of the time, but there is a certain certainty between these women that they will never let their histories fade. The forest trauma is a thief of the here and now. &nbsp,

Try Making a Phone Call to the Ice Cream Shop

A phone number for the ice cream shop appears on the screen during the Ozzie’s commercial. It would be a huge letdown if there was nothing on the other end of the line in real life, given that fans are only interested in interactive Easter eggs. I called ( 732 ) 858-5242 to find out what this place is all about, just like any curious viewer.

The voice in the phone call oscillates between a cheerful tone and a depressing, haunting voice. The call contains ice cream flavors, a lot of static, and advice to call back later. The Reddit superfans have a lot of ideas for what the phone call means and whether the characters ‘ fates can be learned from the ice cream shop, the Man with No Eyes, or through the phone. The significance of these references is once again likely just figments of Tai’s imagination because there is nothing inherently eerie about an ice cream shop. Hopefully the writers continue to research this and update the fans ‘ phone calls throughout the season.

The first three episodes of Yellowjackets season three are now streamable on Paramount+. New episodes will be available on Showtime on Fridays on Paramount + and on Sundays at 8 p.m. ET on Showtime.

The first post on Den of Geek was Yellowjackets Season 3 Episode 3 Explained: The Fox, The Man With No Eyes, and The Phone Number.

At the end of the time, Kathleen Kennedy is apparently leaving Lucasfilm. Multiple industry trades have confirmed the story after it was reported by Puck News ‘ Matt Belloni earlier today, with Variety reporting that she intends to fully retire when her contract comes to an end [ …] despite the fact that the news isn’t official.

Kathleen Kennedy’s Legacy Is More Than Just Star Wars second appeared on Den of Geek.

This essay contains year three of Yellowjackets year 3 show 3 clues.

Yellowjackets has always been a social imagery show. The audience is left to watch the jungle speak and wonder what it all means while the ladies on the staff are speaking to the forest. Watching this display is like deconstructing every color and object in a book during a college English culmination course, from the strange symbol in the first season to the sounds coming from the trees at the beginning of the first season.

The most recent episode,” Them’s the Brakes,” raises the stakes for the year and adds a lot of fresh symbols while providing more hints about the more recent ones. It’s time to understand what is actually happening in Yellowjackets right now, from the Sopranos-esque dream sequence at the end of the episode to the spooky ice cream shop Van ( Lauren Ambrose ) and Tai ( Tawny Cypress ) investigate. Let’s get to the point!

Great Pussy from The Sopranos appears in movies

After Mari ( Alexa Barajas ) returns from an encounter with him in the previous episode, the girls discover that Coach Scott ( Steven Krueger ) is still alive and hiding in a cave. The girls are tenacious for answers and have an unquenchable desire for retribution after he destroyed the house at the end of the following season. &nbsp,

Shauna ( Sophie Nélisse ), Van ( Liv Hewson ), and Akhila ( Nia Sondaya ) are almost to Coach Scott’s time when they ostensibly vanish into a dreamlike trance, which fans will be familiar with from the start if they enjoyed the older HBO classics The Sopranos and Six Feet Under. Although some claim that a writer’s goals provide a glimpse into their inner self, the majority of what occurs in these scenes evokes hallucinations and alienation.

Van is stranded inside the burning room, but Shauna has dreams about speaking with her stillborn child. A talking llama that was voiced by Sopranos actor Vincent Pastore ( the actor who played Big Pussy ) is the subject of Akilah’s night in the forest. In a dream sequence as a fish, Pussy likely recalls talking to Tony Soprano ( James Gandolfini ). The goat might represent the female ‘ guilt over their past crimes, including cannibalism. The famous crowd drama of the 2000s may have made a few hints about the psyches of their characters, according to the Yellowjackets creators. &nbsp,

The Man With No Vision: Who Is He? &nbsp,

Although” The Man with No Vision” has been a part of the show for the entire runtime, Tai’s narrative has so far only featured this spooky dude. When Tai and Van are unwinding on the sofa one day and witness a common ice cream advertisement for Ozzie’s Homemade Ice Cream Parlor, we eventually learn where the man came from. &nbsp,

Tai is shocked to learn that so many of her childhood memories and associations with illness stem from events that she had forgotten. She takes Van to the abandoned ice cream shop to look for him, but the bigger picture is how the sinister number might just be haunting the whole crew who spent their days trapped in the forest.

The fantasy series at the end with Shauna, Van, and Akhila introduced the terrifying find into their soul, too, leading people to believe that the man was only important to her up to this point. In their goals, the person is following the teenagers outside of a class. If the other women are currently dreaming about him, then why was the man in Tai’s head only for a short while? &nbsp,

The treasures of the jungle have played a significant role in the show’s confusion. Is the forest actually supernatural, or is it all just the female ‘ imagination? The fact that the classic man is an ice cream mascot is a source of inspiration helps me understand that perhaps the symbol has a different meaning for each character. &nbsp,

The Man with No Vision was a confrontation between Tai and the Ice Cream Shop, but that doesn’t mean her colleagues saw it first. For the time being, followers will need to be creative and attempt to solve the mysteries on their own. The only thing that is certain is that this person is a predecessor of despair and poor wealth for the Yellowjackets. &nbsp,

What is the Fox’s purpose?

Tai and Van discover a wolf inside the crumbling ice cream creating rather than learning more about the Male with No Vision. Since there hasn’t been any wolf references in the series, it’s just another enigmatic sign that’s being introduced before we can determine what the other ones mean. Astute readers of books and Youngsters who chanted” Swiper, No tapping” at televisions while watching Dora the Explorer will be aware that rabbits typically represent deceit, sleight, and mischievousness. &nbsp,

I wonder if the wolf and the Man with No Eye are related as a single perfect representation of how the wilderness continues to rob the Yellowjackets ‘ well-being even years after their return to society. Most of the time, the current timetable veers, but there is one thing certain about these women’s resolve to put an end to their histories. The forest stress is a criminal of the here and now. &nbsp,

Consider Making a Phone Call to the Ice Cream Shop

A phone number appears on the screen during the Ozzie’s business, which calls the ice cream shop. It would be a big setback if everything was on the other end of the line in real life, given that fans are only interested in engaging Easter eggs. I called ( 732 ) 858-5242 to find out what this place is all about, just like any curious viewer.

A cheerful tone and a sad, haunting words alternate throughout the phone call. The phone contains ice cream flavors, a lot of dynamic, and instructions to call again later. The Reddit superfans have a lot of ideas for what the phone call means and whether the figures ‘ destinies can be learned from the ice cream shop, the Man with No Eye, or the Man with No Eye through the phone. The value of these references is once more likely simply figments of Tai’s imagination because nothing about an ice cream shop is essentially spooky. Finally, the authors will continue to research this and revise the viewers ‘ phone calls throughout the season.

The second three incidents of Yellowjackets year three are now streamable on Paramount+. New episodes will be available on Showtime on Fridays on Paramount + and on Sundays at 8 p.m. ET on Showtime.

The first article on Den of Geek was Yellowjackets Season 3 Episode 3 Explained: The Fox, The Man With No Vision, and The Phone Number.

We agree: the computer-generated eyes could be a great match for personas—but not for the function you might think. Ironically, the website highlights the core issue of this very common design method: the person ( a ) does not exist. Individuals are purposefully made, just like in the pictures. Data is taken out of natural surroundings and recombined into an isolated teaser that’s detached from reality.

But, curiously enough, people are characters who can be used as a source of inspiration for structures in the real world.

Personas: A activity up

Most companies have created, used, or come across characteristics at least once in their career. According to their content” Personas- A Simple Introduction,” the Interaction Design Foundation defines a page as “fictional figures that you create based upon your research to represent the various consumer forms that might use your company, product, website, or brand. In their most complete expression, personas typically consist of a name, profile picture, quotes, demographics, goals, needs, behavior in relation to a certain service/product, emotions, and motivations ( for example, see Creative Companion’s Persona Core Poster ). The aim of personas is to “make the research relateable, ]and ] easy to communicate, digest, reference, and apply to product and service development,” according to design firm Designit.

The decontextualization of characteristics

Personas are popular because they make “dry” research data more practical, more persons. However, this method limits the writer’s ability to interpret the data in a way that excludes the content from their specific contexts. As a result, characteristics don’t identify critical factors that make you understand their decision-making process or allow you to connect to people ‘ thoughts and behavior, they lack tales. You are aware of the character’s behavior, but you are unaware of why. You end up with representations of people that are actually less persons.

This “decontextualization” we see in names happens in four manner, which we’ll explain below.

People believe that people are fluid.

Although many companies still try to box in their employees and customers with outdated personality tests ( referring to you, Myers-Briggs ), here’s a painfully obvious truth: people are not a fixed set of features. You decide how you act, feel, think, and action based on your feelings. You appear specific to different people, you may operate enjoyable to some, hard to others. And you change your mind all the time about options you’ve taken.

Current psychologists agree that how people act and make decisions ultimately depends on a combination of history and culture, despite the fact that people usually act in accordance with particular patterns. The context—the environment, the result of other people, your thoughts, the whole narrative that led up to a situation—determines the kind of person you are in each specific time.

In an effort to reduce fact, personas present a customer as a predetermined set of features, but do so without taking into account this variability. Like personality tests, personalities seize people away from real existence. Even worse, persons are reduced to a company and categorized as” that kind of person” with no means to discipline their natural freedom. This attitude reduces selection, reinforces stereotypes, and doesn’t show reality.

Personas rely on individuals, not the setting

In the real world, you’re writing content for a condition, not an object. Each individual lives in a group, a cluster, an wildlife, where there are environmental, social, and social factors you need to consider. A design is never meant for a single user. Otherwise, you create a product that is meant to appeal to a certain number of people. Personas, however, show the client alone rather than establish how the customer relates to the environment.

Do you constantly make the same choice? Maybe you’re a dedicated veggie but even decide to buy some meat when your household are coming across. As they depend on various circumstances and characteristics, your decisions—and habits, ideas, and comments —are no complete but exceedingly cultural. The persona that “represents” you doesn’t take into account this interdependence because it doesn’t explain the circumstances under which you make your decisions. It doesn’t provide a rationale of why you act the way you do. People practice the well-known attribution error, which states that too frequently they attribute behavior by others 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? However, what frequently happens is that you take a hypothetical character and based on that fiction decide how this character may deal with a particular situation. Given that you haven’t even fully investigated and comprehended the current context of the people you want to represent, how could you possibly comprehend how someone you want to represent behaves in new circumstances?

Personas are meaningless averages

According to Shlomo Goltz’s introduction article on Smashing Magazine, a persona is depicted as a specific person but is not a real person; rather, it is a composite of numerous observations made by different people. A well-known critique to this aspect of personas is that the average person does not exist, as per the famous example of the USA Air Force designing planes based on the average of 140 of their pilots ‘ physical dimensions and not a single pilot actually fitting within that average seat.

The same limitation applies to mental aspects of people. Have you ever heard a famous person say something disparagingly about how they “got what I said”? They used my words, but I didn’t mean it like that”. The celebrity’s statement was literally reported, but the reporter failed to explain the context and how the non-verbal expressions were used. As a result, the intended meaning was lost. You do the same when you create personas: you collect somebody’s statement ( or goal, or need, or emotion ), of which the meaning can only be understood if you provide its own specific context, yet report it as an isolated finding.

However, personas go one step further, combining a decontextualized finding with a different decontextualized finding. The resulting set of findings often does not make sense: it’s unclear, or even contrasting, because it lacks the underlying reasons on why and how that finding has arisen. There is no significance to it. 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 usefulness of the persona?

The validity of personas can be deceiving.

To a certain extent, designers realize that a persona is a lifeless average. To overcome this, designers create and add “relative” details to personas to make them resemble actual people. Nothing captures the absurdity of this better than a sentence by 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 merely an abstraction? If something is artificial, let’s present it as such.

Designers create new context to create ( their own ) meaning after acknowledging that people’s personalities are fixed, ignored the importance of their environment, and hidden meaning by joining isolated, non-generalizable findings. In doing so, as with everything they create, they introduce a host of biases. As phrased by Designit, as designers we can” contextualize ] the persona ] based on our reality and experience. We establish trustworthy connections with people. This practice reinforces stereotypes, doesn’t reflect real-world diversity, and gets further away from people’s actual reality with every detail added.

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

Dynamic Selves: The alternative to personas

If we shouldn’t use personas, what should we do instead?

Designit suggested using mindsets as opposed to 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 stay away from focusing solely on one person’s way of life. Unfortunately, while being a step in the right direction, this proposal doesn’t take into account that people are part of an environment that determines their personality, their behavior, and, yes, their mindset. Therefore, Mindsets are also not absolute but change in regard to the situation. Is the question still unanswered as to what factors lead to a particular mindset?

Another alternative comes from Margaret P., author of the article” Kill Your Personas“, who has argued for replacing personas with persona spectrums that consist of a range of user abilities. A visual impairment could be permanent ( blindness ), temporary ( recovery from eye surgery ), or situational (screen glare ). Persona spectrums are highly useful for more inclusive and context-based design, as they’re based on the understanding that the context is the pattern, not the personality. Their limitation, however, is that they have a very functional take on users that misses the relatability of a real person taken from within a spectrum.

By developing an alternative to personas, we want to change the traditional design process to be context-based. Contexts are generalizable and have patterns that we can identify, just like we tried to do previously with people. Then, how do we discover these patterns? How do we ensure truly context-based design?

Understand real individuals in multiple contexts

Nothing can be more inspiring and relatable than reality. Therefore, we have to understand real individuals in their multi-faceted contexts, and use this understanding to fuel our design. We define our dynamic selves as how we define them.

Let’s take a look at what the approach looks like, based on an example of how one of us applied it in a recent project that researched habits of Italians 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. Choose the right sample

When we debate personas, we frequently get slammed for asking,” Where are you going to find a single person who encapsulates all the information from one of these advanced personas?” The answer is simple: you don’t have to. You don’t need to have information about many people for your insights to be deep and meaningful.

Accuracy is more important in qualitative research from accurate sampling than quantity. You select the people that best represent the “population” you’re designing for. If you choose this sample wisely and have a thorough 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.

Similarly, you don’t need to understand Susan in fifteen different contexts. You’ve come to understand Susan’s reaction to various circumstances once you’ve seen her in a few different settings. Not Susan as an atomic being but Susan in relation to the surrounding environment: how she might act, feel, and think in different situations.

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

However, the question persists: How do you select a representative sample? First of all, you have to consider what’s the target audience of the product or service you are designing: it might be useful to look at the company’s goals and strategy, the current customer base, and/or a possible future target audience.

In our example project, we were putting together an application for those who already have smart thermostats. In the future, everyone could have a smart thermostat in their house. Right now, though, only early adopters own one. To create a sizable sample, we had to understand the causes of the development of these early adopters. We therefore recruited by asking people why they had a smart thermostat and how they got it. There were those who had chosen to purchase it, those who had influenced the decisions of others, and those who had discovered it in their homes. So we selected representatives of these three situations, from different age groups and geographical locations, with an equal balance of tech savvy and non-tech savvy participants.

2. Conduct your research

After having chosen and recruited your sample, conduct your research using ethnographic methodologies. Because of this, your qualitative data will be enriched with examples and anecdotes. In our example project, given COVID-19 restrictions, we converted an in-house ethnographic research effort into remote family interviews, conducted from home and accompanied by diary studies.

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 add their spouses, husbands, children, or sporadically even pets to make their stories much more intriguing and precise. We also focused on the relationships with other meaningful people ( such as colleagues or distant family ) and all the behaviors that resulted from those relationships. This extensive field of study enabled us to develop a vivid mental image of dynamic situations involving multiple actors.

It’s essential that the scope of the research remains broad enough to be able to include all possible actors. Therefore, it normally works best to define broad research areas with macro questions. Interviews should be conducted semi-structured, with follow-up inquiries that cover subjects the interviewee has blatantly mentioned. This open-minded “plan to be surprised” will yield the most insightful findings. When we inquired about how his family controlled the house temperature, one of our participants responded,” My wife uses WhatsApp instead, and she has not installed the thermostat’s app.” If she wants to turn on the heater and she is not home, she will text me. I am her thermostat”.

3. Analysis: Create the Dynamic Selves

You begin by presenting each individual as a” Self,” representing one of the circumstances you have examined throughout the analysis of your research. The core of each Dynamic Self is a quote, which comes supported by a photo and a few relevant demographics that illustrate the wider context. The research findings themselves will show which demographics are relevant to show. Because our research focused on families and their way of life to understand their needs for thermal regulation, the key demographics were family type, number and type of homes owned, economic status, and technological maturity in our case. ( We also included the individual’s name and age, but they’re optional—we included them to ease the stakeholders ‘ transition from personas and be able to connect multiple actions and contexts to the same person ).

To capture precise quotations, interviews must be taped on video and verbatim whenever possible. This is essential to the truthfulness of the several Selves of each participant. In the case of real-life ethnographic research, photos of the context and anonymized actors are essential to build realistic Selves. Direct from field research should be used to take these photos, but also an evocative and representative image may do. However, these photos should be realistic and accurately depicting meaningful actions that you associate with your participants. For example, one of our interviewees told us about his mountain home where he used to spend every weekend with his family. We therefore depicted him hiking 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. Each card displayed a situation, represented by a quote and a unique photo. Each participant had a series of self-portraits.

4. Identify innovative applications

Once you have collected all main quotes from the interview transcripts and diaries, and laid them all down as Self cards, you will see patterns emerge. These patterns will highlight the opportunity areas for new product creation, new functionalities, and new services—for new design.

In our example project, there was a particularly fascinating insight regarding the topic of humidity. We realized that people don’t know what humidity is and why it is important to monitor it for health: an environment that’s too dry or too wet can cause respiratory problems or worsen existing ones. This made it clear that our client had a significant opportunity to provide training for users about the concept and practice as a health advisor.

Benefits of Dynamic Selves

When you use the Dynamic Selves approach in your research, you start to notice unique social relations, peculiar situations real people face and the actions that follow, and that people are surrounded by changing environments. Davide, one of the participants in our thermostat project, is described as a boyfriend, dog lover, and tech nut.

Davide is an individual we might have once reduced to a persona called” tech enthusiast”. There are also those who enjoy technology who are wealthy or poor, have families or are single, and who love technology. Their motivations and priorities when deciding to purchase a new thermostat can be opposite according to these different frames.

Once you have understood Davide in multiple situations, and for each situation have understood in sufficient depth the underlying reasons for his behavior, you’re able to generalize how he would act in another situation. You can use your understanding of him to infer what he would think and do in the circumstances ( or scenarios ) you create.

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

If you take a real person as inspiration for your design, you no longer need to create an artificial character. No more developing novel plot devices to “understand” the character, no more implausible biases. It’s simply how this person is in real life. In fact, because we all know these characters don’t really exist, personas quickly turn into nothing more than a name in our priority guides and prototype screens.

Another powerful benefit of the Dynamic Selves approach is that it raises the stakes of your work: if you mess up your design, someone real, a person you and the team know and have met, is going to feel the consequences. It might stop you from taking shortcuts and will remind you to conduct daily checks on your designs.

Finally, real people in their specific contexts provide a stronger foundation for anecdotal storytelling and increase persuasion effectiveness. Documentation of real research is essential in achieving this result. By giving more weight and urgency, it supports your design arguments:” When I met Alessandra, the circumstances of her workplace struck me. Noise, bad ergonomics, lack of light, you name it. If we go for this functionality, I’m afraid we’re going to add complexity to her life”.

Conclusion

Designit stated in an article on Mindsets that “design thinking tools provide a shortcut to deal with reality’s complexities, but this process of simplification can occasionally flatten out people’s lives into a few general characteristics.” ” Unfortunately, personas have been culprits in a crime of oversimplification. They disregard the complexity of the decision-making processes of our users and disregard how submerged they are in their surroundings are.

Design needs simplification but not generalization. You have to look at the research elements that stand out: the sentences that captured your attention, the images that struck you, the sounds that linger. Avoid using those, instead using them to express the person in each of their situations. Both insights and people come with a context, they cannot be cut from that context because it would remove meaning.

In its messy, surprising, and unquantifiable beauty, design needs to break away from fiction and turn to reality as our guide and inspiration.

One of the most successful soft skills we have at our disposal is feedback, 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 feedback can lead to conflict in projects, lower confidence, and long-term, undermine trust and teamwork. Quality opinions can be a revolutionary force.

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

A long history of sequential opinions can be found online: code was written and discussed on mailing lists before becoming an open source standard. Currently, engineers engage on pull calls, developers post in their favourite design tools, project managers and sprint masters exchange ideas on tickets, and so on.

Design analysis is often the label used for a type of input that’s provided to make our job better, jointly. So it generally adheres to many of the principles with comments, but it also has some differences.

The material

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

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

A comment that appears to be acceptable at first glance could be included in some feedback, as it only appears to partially fulfill the requirements. But does it?

Not confident about the keys ‘ patterns and hierarchy—it feels off. May you alter them?

Observation for style feedback doesn’t really mean pointing out which part of the software your input refers to, but it also refers to offering a viewpoint that’s as specific as possible. Do you offer the user’s viewpoint? Your expert perspective? A business perspective? From the perspective of the project manager? A first-time user’s perspective?

I anticipate that one of these two buttons will go forward and the other will go back when I see them.

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 that one of these two buttons will go forward and the other will go back when I see them. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow.

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

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

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

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

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

Choosing the question approach or the request approach can also at times be a matter of personal preference. I spent a while working on improving my feedback, conducting anonymous feedback reviews and sharing feedback with others. After a few rounds of this work and a year later, I got a positive response: my feedback came across as effective and grounded. Until I changed teams. Quite unexpected, my next round of criticism from one particular person wasn’t very positive. The reason is that I had previously tried not to be prescriptive in my advice—because the people who I was previously working with preferred the open-ended question format over the request style of suggestions. However, there was a person in this other team who had always preferred specific guidance. So I adapted my feedback for them to include requests.

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

No, this kind of feedback is effective because the length is a byproduct of clarity, and giving this kind of feedback can provide precisely enough information for a sound fix. Also if we zoom out, it can reduce future back-and-forth conversations and misunderstandings, improving the overall efficiency and effectiveness of collaboration beyond the single comment. Imagine that in the example above the feedback were instead just,” Let’s make sure that all screens have the same two forward and back buttons”. The designer receiving this feedback wouldn’t have much to go by, so they might just implement the change. In later iterations, the interface might change or they might introduce new features—and maybe that change might not make sense anymore. Without 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 style of feedback is not always efficient because the points in some comments don’t always need to be exhaustive, sometimes because certain changes may be obvious (” The font used doesn’t follow our guidelines” ) and sometimes because the team may have a lot of internal knowledge such that some of the whys may be implied.

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

The atmosphere

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

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

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

The term “timing” describes the moment when the feedback occurs. To-the-point feedback doesn’t have much hope of being well received if it’s given at the wrong time. When a new feature’s entire high-level information architecture is about to go live, it might still be relevant if the questioning raises a significant blocker that no one saw, but those concerns are much more likely to have to wait for a later revision. So in general, attune your feedback to the stage of the project. Early iteration? Iteration later? Polishing work in progress? Each of these needs varies. The right timing will make it more likely that your feedback will be well received.

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

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

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

Something to highlight because it’s quite frequent—especially in teams that have a strong group spirit—is that people tend to beat around the bush. It’s important to keep in mind that having a positive attitude doesn’t necessarily mean passing judgment on the feedback; rather, it simply means that even when you give difficult, or difficult feedback, you do so in a way that’s respectful and constructive. The nicest thing that you can do for someone is to help them grow.

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

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 meet two main objectives.

Let’s imagine that someone shared a design iteration for a project. You are reviewing it and leaving a comment. There are many ways to 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 know the project well, or do you just see it for the first time? Are you coming from a high-level perspective, or are you figuring out the details? Are there regressions? Which user’s point of view do you consider when providing feedback? Is the design iteration at a point where it would be okay to ship this, or are there major things that need to be addressed first?

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

We frequently concentrate on the negatives and attempt to list every possible improvement. That’s of course important, but it’s just as important—if not more—to focus on the positives, especially if you saw progress from the previous iteration. 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. In the longer term, sharing positive feedback can help prevent regressions on things that are going well because those things will have been highlighted as important. Positive feedback can also help, as an added bonus, prevent impostor syndrome.

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

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

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

One approach that I’ve personally used effectively in some contexts is to enhance the bullet points with four markers using emojis. A red square indicates that it is something I consider blocking, a yellow diamond indicates that it needs to be changed, and a green circle provides a thorough, positive confirmation. I also use a blue spiral � � for either something that I’m not sure about, an exploration, an open alternative, or just a note. 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 I’d have to reframe how I’d 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 that one of these two buttons will go forward and the other will go back when I see them. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.
• � � Overall— I think the page is solid, and this is good enough to be our release candidate for a version 1.0.
• � � Metrics—Good improvement in the buttons on the metrics area, the improved contrast and new focus style make them more accessible.
• Button Style: Using the green accent in this context, which conveys that it is a positive action because green is typically seen as a confirmation color. Do we need to explore a different color?
• Considering the number of items on the page and the overall page hierarchy, it seems to me that the tiles should use Subtitle 2 instead of Subtitle 1. This will keep the visual hierarchy more consistent.
• � � Background—Using a light texture works well, but I wonder whether it adds too much noise in this kind of page. What is the purpose of using that?

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

One final note: say the obvious. 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. You might have to reword it a little bit to make the reader feel more comfortable, but don’t hold it back. Good feedback is transparent, even when it may be obvious.

Asynchronous feedback also has the benefit of automatically guiding decisions, according to writing. Especially in large projects,” Why did we do this”? there’s nothing better than open, transparent discussions that can be reviewed at any time, and this could be a question that arises from time to time. For this reason, I recommend using software that saves these discussions, without hiding them once they are resolved.

Content, tone, and format. Although each of these subjects offers a useful model, focusing on improving eight of the subjects ‘ focus points, including observation, impact, question, timing, attitude, form, clarity, and actionability, is a lot of work to complete at once. One effective approach is to take them one by one: first identify the area that you lack the most (either from your perspective or from feedback from others ) and start there. Then the second, 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 Brie Anne Demkiw and Mike Shelton for reviewing the first draft of this article.