Blog

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

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

But you can ensure that your group has packed its carriers 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.

We refer to it as prepersonalization.

Behind the song

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

We’re used to seeing the polished final outcome of a personalization have. A personal have had to be conceived, budgeted, and prioritized 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 customisation wagers? How do you design regular interactions that didn’t journey up users or—worse—breed mistrust? We’ve discovered that several budgeted programs initially needed one or more workshops to join key stakeholders and domestic customers of the technology to justify their continuing investments. Make it count.

We’ve closely monitored the same evolution with our consumers, from major software to young companies. In our experience with working on small and large personalization work, 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.

Successful seminars consistently distinguish successful future endeavors from ineffective ones, saving many hours of time, resources, and overall well-being in the process.

A personalization training involves a protracted work of testing and function development. It’s never a technical load switch-flip. It’s ideal managed as a delay that usually evolves through three actions:

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

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

Set the timer for your kitchen.

How long does it take to cook up a prepersonalization workshop? The evaluation activities that we suggest include can last for a number of weeks ( and frequently do ). For the core workshop, we recommend aiming for two to three days. Details on the essential first-day activities are included in a summary of our broad approach.

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 company. A connected experience, in our parlance, is any UX requiring the orchestration of multiple systems of record on the backend. This might be a marketing-automation platform combined with a content-management system. It could be a digital-asset manager combined with a customer-data platform.

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

The table must be set up for this. 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 break down connected experiences into five categories in our cards: 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 deliver right now and what you want to deliver in the future.

Next, have your team plot each idea on the following 2×2 grid, which lays out the four enduring arguments for a personalized experience. This is 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 ensuring data and privacy is a major challenge too much? Do you have content metadata needs that you have to address? ( We’re pretty sure you do; it’s just a matter of acknowledging the magnitude of that need and finding a solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six intractable behaviors that prevent progress.

Effectively collaborating and managing expectations is critical to your success. Consider the potential obstacles to your progress 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? Good, you’re all set to go on.

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. They give you a variety of options for how your organization can conduct its activities because of their broad and potent capabilities. This presents the question: Where do you begin when you’re configuring a connected experience?

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

Over the course of the workshop, the final menu of the prioritized backlog will be created. 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.

Recipes have ingredients in them, and those recipes have ingredients.

Verify your ingredients

Like a good product manager, you’ll make sure you have everything you need to make your desired interaction ( or that you can figure out what needs to be added to your pantry ) and that you validate with the right stakeholders present. These 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.

Not just discovering requirements, it is. Documenting your personalizations as a series of if-then statements lets the team:

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

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 your 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 offer 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 we still come across 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 when a new user registers 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 sometimes this process comes together more effectively by cocreating the recipes themselves, so a good preworkshop activity might be to think about what these cards might be for your organization. Start with a set of blank cards, and begin labeling and grouping them through the design process, eventually distilling them to a refined subset of highly useful candidate cards.

The later stages of the workshop could be characterized as moving from focusing on a cookbook to a more nuanced customer-journey mapping. Individual” cooks” will pitch their recipes to the team, using a common jobs-to-be-done format so that measurability and results are baked in, and from there, the resulting collection will be prioritized for finished design and delivery to production.

Architecture must be improved to produce better kitchens.

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

A team overfitting: they aren’t designing with their best data, is what causes personalization to become a laugh line. 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 withstand the heat without a doubt.

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach will produce the necessary concentration and intention for success. So banish the dream kitchen. Instead, head to the test kitchen to save time, preserve job security, and avoid imagining the creative concepts that come from the doers in your organization. There are meals to serve and mouths to feed.

This organizational framework gives you a fighting chance at long-term success as well as solid ground. Wiring up your information layer isn’t an overnight affair. However, if you use the same cookbook and the same recipes, you’ll have solid ground for success. 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.

I’ve been fascinated by movies since I was a child. I loved the heroes and the excitement—but most of all the stories. I aspired to be an artist. And I believed that I’d get to do the things that Indiana Jones did and go on fascinating experiences. Perhaps my friends and I had movie ideas to make and sun in. But they never went any farther. However, I did end up in the user experience ( UX) field. Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer research is story. And you must tell a compelling story to entice stakeholders, such as the product team and decision-makers, to learn more in order to get the most out of consumer research.

Think of your favourite film. It more than likely follows a three-act narrative construction: the installation, the turmoil, and the resolution. The second act shows what exists now, and it helps you get to know the characters and the challenges and problems that they face. Act two sets the scene for the fight and introduces the activity. Here, difficulties grow or get worse. The solution is the third and final work. This is where the issues are resolved and the figures learn and change. This architecture, in my opinion, is also a fantastic way to think about consumer research, and it might be particularly useful for introducing 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 expenses 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 might lead to some clubs getting in the way, but it’s too easy to overlook the real issues facing users. To be user-centered, this is something we really avoid. Design is enhanced by consumer research. It keeps it on record, pointing to problems and opportunities. You can keep back of your competition by being aware of the problems with your goods and fixing them.

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 customer research.

Act one: installation

The basic research comes in handy because the layout is all about understanding the background. Basic research ( also called conceptual, discovery, or preliminary research ) helps you understand people and identify their problems. You’re learning about the problems 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 problems and opportunities. It doesn’t need to get a great investment in time or money.

Erika Hall writes about the most effective anthropology, which can be as straightforward as spending 15 hours with a customer and asking them to” Walk me through your morning yesterday.” That’s it. Give that one demand. Locked 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 definitely 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”.

I think this makes sense. 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. Understanding where people are coming from is what action one is really all about.

Maybe Spool talks about the importance of basic research and how it may type the bulk of your research. If you can complement what you’ve heard in the basic studies by using any more user data that you can obtain, such as surveys or analytics, or if you can identify areas that need more investigation. Together, all this information creates a clearer picture of the state of things and all its inadequacies. 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 figures and support their success, much like in the movies. And finally participants are now doing the same. Their business may lose money because users can’t finish specific tasks, which may be their love. Or probably they do connect with people ‘ problems. In either case, action 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 item team become more user-centric. This rewards everyone—users, the goods, and partners. It’s similar to winning an Oscar for a film; it frequently results in a favorable reception and success for your item. And this can be an opportunity for participants to repeat this process with different products. Knowing how to show a good story is the only way to convince partners to worry about doing more research, and story is the key to this method.

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

Act two: issue

Act two is all about digging deeper into the problems that you identified in operate one. This typically involves conducting vertical study, such as accessibility tests, where you evaluate a potential solution ( such as a design ) 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 off. More issues may come up in the process, much like in action two of a movie. It’s here that you learn more about the figures as they grow and develop through this action.

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 interpret in-person usability tests as a form of theater watching as opposed to remote testing. There are advantages and disadvantages to each. Usability research in person is a much more extensive experience. Stakeholders can experience the sessions with other stakeholders. Additionally, you’ll also hear their reactions in real-time, including surprises, disagreements, and discussions of what they’re seeing. Much like going to a play, where audiences get to take in the stage, the costumes, the lighting, and the actors ‘ interactions, in-person research lets you see users up close, including their body language, how they interact with the moderator, and how the scene is set up.

If conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may be very different from one another. You can 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 run as researchers, but this can occasionally improve your understanding of users. Meeting users where they are can provide clues to the external forces that could be affecting how they use your product. In-person usability tests add a level of detail that remote usability tests frequently lack.

That’s not to say that the “movies” —remote sessions—aren’t a good option. A wider audience can be reached through 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 done 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. Sometimes, participants will say unexpected things that alter the way you look at them, which can lead to unexpected turns in the story.

Unfortunately, user research is sometimes seen as expendable. Usability testing is frequently the only method of research that some stakeholders believe they ever need, and it’s too frequently the case. 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 just 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, whereas the first two acts are about understanding the context and the tensions that can compel stakeholders to act. 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 the entire product team, including developers, UX experts, business analysts, delivery managers, product managers, and any other interested parties who have a say in the coming development. 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 decisions. So you can get everyone on the same page and get agreement on the way forward.

This act is primarily told through 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 provide the stakeholders with 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 of a good story:

Act one: You meet the protagonists ( the users ) and the antagonists ( the problems affecting users ). The plot begins here. 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.

Act two: Next, there’s character development. The protagonists face 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 is the audience, as well. But the most important thing is to get the story right and to use storytelling to tell users ‘ stories through research. By the end, the parties should leave with a goal and an eagerness to address the product’s flaws.

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

As a solution developer for too many years, I can’t recall how many times I’ve seen promising ideas go from being heroes in a few weeks to being useless within months.

Financial goods, which is the industry in which I work, are no exception. It’s tempting to put as many features at the ceiling as possible and hope someone sticks because people’s true, hard-earned money is on the line, user expectations are high, and a crammed market. However, this strategy is a formula for disaster. Why? How’s why:

The perils of feature-first creation

It’s easy to get swept up in the enthusiasm of developing innovative features when you start developing a financial product from scratch or are migrating existing user journeys from papers or telephony channels to online bank or mobile applications. You might be thinking,” If I can only put one more thing that solves this particular person problem, they’ll enjoy me”! But what happens if you eventually encounter a roadblock as a result of your security team’s negligence? don’t like it? When a difficult-fought film fails to win over viewers or fails owing to unanticipated difficulty?

The concept of Minimum Viable Product ( MVP ) comes into play in this context. Even if Jason Fried doesn’t usually refer to this concept, his book Getting Real and his audio Redo frequently discuss it. An MVP is a product that offers only enough significance to your users to keep them interested, but not so much that it becomes difficult to keep up. Although the idea seems simple, it requires a razor-sharp eye, a brutal edge, and the courage to stand up for your position because” the Columbo Effect” makes it easy to fall for something when one always says” just one more thing …” to add.

The issue with most fund apps is that they frequently turn out to be reflections of the company’s internal politics rather than an experience created exclusively for the customer. Instead of offering a distinct value statement that is focused on what people in the real world want, the focus should be on delivering as some features and functionalities as possible to satisfy the needs and wants of competing inside sections. These products may therefore quickly become a muddled mess of confusing, related, and finally unlovable client experiences—a feature salad, you might say.

The significance of the foundation

What is a better strategy, then? How may we create products that are user-friendly, firm, and, most importantly, stick?

The concept of “bedrock” comes into play in this context. The mainstay of your product is really important to people, and Bedrock is that. It’s the fundamental building block that creates price and maintains relevance over time.

The rock has got to be in and around the standard cleaning journeys in the world of retail bank, which is where I work. People only look at their existing accounts once every blue sky, but they do so daily. They sign up for a credit card every year or two, but they check their stability and pay their bill at least once a quarter.

The key is in identifying the main tasks that individuals want to complete and therefore persistently striving to make them simple, reliable, and trustworthy.

How can you reach the foundation, though? By focusing on the” MVP” strategy, giving convenience precedence, and working incrementally toward a clear value proposition. This means avoiding unnecessary functions and putting your customers first, and adding real value.

It also requires having some nerve, as your coworkers might not always agree with you immediately. And in some cases, it might even mean making it clear to clients that you won’t be coming over to their home and prepare their meal. Sometimes you may need to use the sporadic “opinionated user interface design” ( i .e. clunky workaround for edge cases ) to test a concept or to give yourself some room to work on something more crucial stuff.

Functional methods for creating reliable economic items

What are the main learnings I’ve made from my own research and practice, then?

1. What issue are you attempting to resolve first, and why? Whom? Before beginning any construction, make sure your goal is completely clear. Make certain it also aligns with the goals of your business.
2. Avoid the temptation to put too many features at once and focus on getting that right first. Choose one that actually adds price, and work from that.
3. Give clarity the precedence it deserves over difficulty when it comes to financial products. Eliminate unwanted details and concentrate solely on what matters most.
4. Accept constant iteration: Bedrock is not a fixed destination; it is a dynamic process. Continuously collect customer feedback, improve your product, and work toward that foundational position.
5. Halt, look, and listen: You don’t just have to test your product during the delivery process; you must also test it frequently in the field. Use it for yourself. Move the A/B checks. User opinions on Gatter. Talk to those who use it, and change things up correctly.

The core dilemma

This is an intriguing conundrum: sacrificing some of the potential for short-term progress in favor of long-term stability is at play. But the reward is worthwhile: products built with a focus on core will outlive and surpass their rivals over time and provide users with long-term value.

How do you begin your quest for core, then? Get it gradually. Start by identifying the underlying factors that your customers actually care about. Focus on developing and improving a second, potent have that delivers real value. And most importantly, check constantly because, whatever you think, Abraham Lincoln, Alan Kay, or Peter Drucker are all in the same boat! The best way to foretell the future is to make it, he said.

Warning: contains trailers for time 9 of winter 6 of The Handmaid’s Tale. Suicide is the penalty for crime? Wharton, you got that right. Thanks to Joseph Lawrence, an economist, loving parents, freedom warrior, and part-time James Bond, the income of the commanders ‘ sins were a glittering fire of a dying in” Execution.” Talk about [ …] laying low the…

On Den of Geek, the second publish The Handmaid’s Tale Season 6 Episode 9 Review: Execution appeared.

Jurassic World Rebirth, the upcoming film, is aware that we have already seen it all. The movie makes no recompense for its position in film history as the eighth picture in a company that dates back more than 30 years. The most recent Resurrection teaser, like the first trailer that was released months earlier, includes numerous references to the Steven Spielberg film and Michael Crichton book that served as its inspiration, such as red flares and a raft scene from Spielberg&#8217, Spielberg&#8217’s 1993 adaptation of Jurassic Park.

The most recent trailer also includes a mutated dino that draws inspiration from Star Wars and other sci-fi films.

The story of the new film is described in the trailer’s majority, which is Colin Trevorrow‘s primary Jurassic World film since the first one was released with 2022&#8217. A team of scientists, including one played by Wicked striking Jonathan Bailey, travel to a key area where researchers experimented with new reptile forms as actors Scarlett Johansson and Mahershala Ali take on the role of travelers. The warning becomes even stronger when accompanied by photos of well-known raptors like the T-Rex. &#8220, They left the worst people below, &#8221, utters Johansson&#8217, s Zora Bennett.

We see flashes of some of those brand-new, altered dinosaurs between images of high-adventure locations and heroes rappelling down cliffs or riding thrilling rivers. A flock of brachiosaurs are present, with much snake-like feathers whizzing through the grass. A pachycephalosaurus-pterodactylus hybrid is slamming its nose against a car; it &#8217. There is even a child triceratops that has been modified for the highest toy sales beauty.

However, the trailer’s most popular character, who both opens and closes the video, is the spotlight. In February, director Gareth Edwards teased this new dinosaur after starting the particular effects-driven indie Monsters and moving on to work on Godzilla and The Creator. Edwards mentioned the creature’s forces in a Vanity Fair interview, saying,” Some Rancor went in there, some H. R. Giger went in it, a small T. Rex went in there.”

The truck makes it obvious that Star Wars is influencing. A well-worn sci-fi film theme about a lab disaster leaving one employee stranded inside the scene opens. His paralyzed colleagues must see as the professor pleading for his career before being suffocated by the monster he helped to create.

We can see a sizable number of strong, broken teeth through the smoke and the red lighting. The creature extends its enormous hands toward the scholar, implying a level of intelligence and potential previously unobserved among dinosaurs. It emerges from the plants again toward the trailer’s conclusion. Its thick head and sharp eyes, which direct its prey, are visible it.

These hints reveal the forces that Edwards describes. The professor is grabbed by the creature in the same way that the Gamorrean Guard was grabbed by the Rancor in Transfer of the Jedi. The more knock on the mind resembles the nearly helmet-like helmet Giger gave the extract in Alien. And it makes sense that Edwards had resurrect Jurassic World from the ranks of the film monster greats by establishing his own ancestor in the heritage of sci-fi film.

Will all of these sources contribute to a thrilling film? When Jurassic World Rebirth transports us to the extraordinary area, we’ll had to wait until the summer for that response.

On July 2, 2025, Jurassic World: Reincarnation crashes into venues.

Den of Geek‘s New Jurassic World Resurrection Video features a Star Wars-inspired mutated dinosaur first appeared.

The most notable feature of the Mission: Impossible films ‘ Christopher McQuarrie time may have been their authenticity. Since 2015’s Mission: Impossible – Rogue Nation, Mission films have been informed by the IMF characters onscreen, led by the unwavering Ethan Hunt ( Tom ), aside from a renewed emphasis on Buster Keaton-like daredevil stunt work.

The article Why Tom Cruise Named Her” Grace” appeared first on Den of Geek. Mission: Impossible – Hayley Atwell Shows Why.

Jurassic World Rebirth, the upcoming film, is aware that we have already seen it all. The movie makes no recompense for its position in film history as the eighth picture in a company that dates back more than 30 years. The most recent Resurrection teaser, like the first trailer that was released months previously, includes numerous references to the Steven Spielberg film and Michael Crichton book that served as its inspiration, such as red flares and a raft scene from Spielberg&#8217, the 1993 adaptation of Jurassic Park.

The most recent video also includes a mutated dino that draws inspiration from Star Wars and other sci-fi films.

The story of the new film is described in the majority of the trailer, which is Colin Trevorrow‘s second film since the initial Jurassic World trilogy was completed with 2022&#8217, Jurassic World Dominion. A team of scientists, including Wicked striking Jonathan Bailey, travel to a key area where researchers experimented with new reptile forms as actors Scarlett Johansson and Mahershala Ali take on the role of travelers. The warning becomes even stronger when the familiar dinos like the T-Rex are accompanied by the film &#8220, They left the worst ones here, &#8221, intones Johansson&#8217, s Zora Bennett.

We see flashes of some of those fresh, altered dinosaurs in between pictures of high-adventure areas, with heroes rappelling down a mountain or riding a rousing river. A flock of brachiosaurs can be found there, with much snake-like feathers whizzing through the grass. A pachycephalosaurus-pterodactylus hybrid is slamming its nose against a car; it &#8217. There is even a girl triceratops that has been modified for the highest toy sales beauty.

However, the trailer’s most popular character, who both opens and closes the video, is the spotlight. In February, director Gareth Edwards teased this new dinosaur after starting the particular effects-driven indie Monsters and moving on to work on Godzilla and The Creator. Edwards mentioned the creature’s forces in a Vanity Fair interview, saying,” Some Rancor went in it, some H. R. Giger went in it, a small T. Rex went in there.”

The truck makes it obvious that Star Wars is in there. A well-worn sci-fi video cliche about a lab disaster leaving one employee stranded inside the scene opens. His paralyzed colleagues must see as the scholar pleading for his career before being suffocated by the monster he helped to create.

We can see a sizable number of strong, broken teeth through the smoke and the red lighting. The creature extends its enormous hands toward the professor, implying a level of intelligence and potential previously unobserved among dinosaurs. It emerges from the trees again toward the close of the truck. Its thick head and sharp eyes, which direct its victim, can be seen there.

These flashes reveal the effects Edwards describes. In Return of the Jedi, the lion catches the professor in the same way that the Gamorrean Watch was taken by the Rancor. The more knock on the mind resembles the nearly helmet-like protect Giger gave the extract in Alien. And it makes sense that Edwards had resurrect Jurassic World from the shadow of the dragon film genre.

Does this dialogue contribute to a thrilling film? When Jurassic World Rebirth transports us to the extraordinary beach, we’ll had to wait until the summer for that response.

On July 2, 2025, Jurassic World: Reincarnation crashes into venues.

The second article New Jurassic World Rebirth Trailer Features a Star Wars-inspired mutated dinosaur first appeared on Den of Geek.

Jurassic World Rebirth, the upcoming film, makes it clear that it has already been seen. The movie makes no recompense for its position in film history as the eighth movie in a company that dates back more than 30 years. The newest Rebirth teaser features a lot of call-backs to the [ …] [like the first trailer released months ago ] ] […]

Den of Geek‘s New Jurassic World Resurrection Video features a Star Wars-inspired mutated dinosaur first appeared.

Jurassic World Rebirth, the upcoming film, is aware that we have already seen it all. The movie makes no recompense for its position in film history as the eighth movie in a company that dates back more than 30 years. The most recent Resurrection teaser, like the first trailer that was released months previously, includes numerous references to the Steven Spielberg film and Michael Crichton book that served as its inspiration, such as red flares and a raft scene from Spielberg&#8217, Spielberg&#8217’s 1993 adaptation of Jurassic Park.

The most recent trailer also includes a mutated rex that draws inspiration from the story of sci-fi films, including Star Wars.

The story of the new film is described in the majority of the trailer, which is Colin Trevorrow‘s second film since the original Jurassic World trilogy was completed with 2022&#8217, Jurassic World Dominion. A team of scientists, including one played by Wicked striking Jonathan Bailey, travel to a key area where researchers experimented with new reptile forms as actors Scarlett Johansson and Mahershala Ali take on the role of travelers. The alert becomes even stronger when the pictures of well-known dinos like the T-Rex are accompanied by photos of familiar faces like the T-Rex.

We see flashes of some of those brand-new, altered dinosaurs between images of high-adventure locations and heroes rappelling down cliffs or riding thrilling rivers. There are a herd of brachiosaurs, with much snake-like tail whipping through the foliage. A pachycephalosaurus and pterodactylus combination is slamming its head against a car, and there&#8217. There is even a child triceratops that has been modified for the highest toy sales beauty.

However, the trailer’s most popular character, who both opens and closes the video, is the highlight. Gareth Edwards, the producer behind the independent monsters that were based on special effects and went on to make Godzilla and The Creator, teased this novel reptile back in February. Edwards mentioned the creature’s forces in a Vanity Fair interview, saying,” Some Rancor went in there, some H. R. Giger went in it, a small T. Rex went in there.”

The Star Wars influence is obvious in the truck. A well-worn sci-fi film theme about a lab disaster leaving one employee trapped inside opens the tape. The scientist may see as his paralyzed colleagues, who are unable to assist, plead for their lives before being consumed by the demon he helped to create.

We can see a sizable number of strong, curved teeth through the smoke and the red lighting. The professor is shown a level of intelligence and potential previously unobserved in dinosaurs when the creature extends its giant hand toward him. It appears once more, emerging from the trees toward the close of the video. Its thick head and sharp eyes, which direct its prey, are visible it.

From these glances, we may discern the influences Edwards describes. The professor is grabbed by the lion in Return of the Jedi, much like the Gamorrean Guard was grabbed by the Rancor. The xenomorph’s mind has an additional bump that reminds one of the nearly helmet-like protect Giger gave the extract in Alien. And it makes sense that Edwards had resurrect Jurassic World from the shadow of the dragon film genre.

Will all of these links contribute to a thrilling film? When Jurassic World Rebirth transports us to the extraordinary area, we’ll had to wait until the summer for that response.

On July 2, 2025, Jurassic World: Reincarnation crashes into venues.

Den of Geek‘s New Jurassic World Resurrection Video features a Star Wars-inspired mutated dinosaur first appeared.

When senior figure professional Neal McDonough showed his writing partners the first draft of his most recent film, The Last Rodeo, to hear him tell it, shocked them. Where did this originate? his companions inquired. You write about challenging people and Lee Marvin. Your champions are those! Despite how astonished the]…]

Neal McDonough appeared primary on Den of Geek, discussing his roles in The Last Rodeo, Star Trek, and Captain America.

Jurassic World Rebirth, the upcoming film, is aware of how it all has happened before. The movie makes no recompense for its position in film history as the eighth movie in a company that dates back more than 30 years. The most recent Resurrection teaser, like the first trailer that was released months previously, includes numerous references to the Steven Spielberg film and Michael Crichton book that served as its inspiration, such as red flares and a raft scene from Spielberg&#8217, the 1993 adaptation of Jurassic Park.

A mutated dino that draws inspiration from Star Wars and other sci-fi films is also featured in the most recent video, though.

The storyline of the new film is described in the trailer’s majority, which is Colin Trevorrow‘s first Jurassic World film since the first one was released with 2022&#8217. A team of scientists, including one played by Wicked striking Jonathan Bailey, travels to a key area where researchers experimented with new reptile forms as actors Scarlett Johansson and Mahershala Ali take on the role of travelers. The alert becomes even stronger when the pictures of well-known dinos like the T-Rex are accompanied by photos of familiar faces like the T-Rex.

We see flashes of some of those fresh, mutated dinosaurs in between pictures of high-adventure areas, with heroes rappelling down a mountain or riding a thrilling river. A flock of brachiosaurs can be found there, with much snake-like feathers whizzing through the grass. A pachycephalosaurus-pterodactylus hybrid is slamming its nose against a car; it &#8217. There is even a child triceratops that has been modified for the highest gadget sales beauty.

However, the trailer’s highly anticipated thing who opens and closes the video is its star. In February, director Gareth Edwards teased this new dinosaur after starting the particular effects-driven indie Monsters and moving on to work on Godzilla and The Creator. Edwards mentioned the creature’s forces in a Vanity Fair interview, saying,” Some Rancor went in it, some H. R. Giger went in it, a small T. Rex went in there.”

The truck makes it obvious that Star Wars is in there. A well-worn sci-fi film theme about a lab disaster leaving one employee stranded inside the scene opens. His coworkers, who are unable to assist, must see as the professor pleading for his life before being suffocated by the monster he helped to create.

We can see a sizable number of strong, curved teeth through the smoke and the red lighting. The scholar is shown a level of intelligence and potential previously unobserved in dinosaurs when the creature extends its giant hand toward him. It emerges from the trees again toward the close of the truck. Its thick head and sharp eyes, which direct its prey, are visible it.

These glances reveal the effects Edwards describes. In Return of the Jedi, the lion catches the professor in the same way that the Gamorrean Watch was taken by the Rancor. The more knock on the mind resembles the nearly helmet-like protect Giger gave the extract in Alien. And it makes sense that Edwards had resurrect Jurassic World from the ranks of the film monster greats by establishing his own ancestor in the heritage of sci-fi film.

Does this dialogue contribute to a thrilling film? When Jurassic World Rebirth transports us to the extraordinary area, we’ll had to wait until the summer for that response.

On July 2, 2025, Jurassic World: Resurrection crashes into theaters.

The second postNew Jurassic World Resurrection Video features a Star Wars-inspired mutated dinosaur first appeared on Den of Geek.

But what on earth is a passionate burnout?

Envision a person determined to do it all. She is homeschooling two wonderful children while simultaneously working remotely with her husband. She has a demanding customer fill at work—all of whom she loves. She wakes up early to get some movement in ( or frequently catch up on work ), prepares dinner while the kids are having breakfast, and works while positioning herself near the end of her “fourth grade” to watch as she balances clients, tasks, and budgets. Sound like a bit? Yet with a supportive group both at home and at work, it is.

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

She instantly KNOWS what she must do! She really Would MORE.

This is a difficult and dangerous period. Know the reasons? Because when she doesn’t end that new purpose, that storyline will get worse. She instantly starts failing. She isn’t doing much. SHE is not enough. She’ll discover more she may do because she might neglect, or perhaps her home. She doesn’t nap as much, proceed because much, all in the attempts to do more. Not succeeds in any objective target despite constantly trying to prove herself to herself. Always feeling “enough”.

But, yeah, that’s what zealous burnout looks like for me. It doesn’t develop over in some grand gesture, but it does rather develop gradually over the course of several weeks and months. My burning out process looks like speeding up, hardly a man losing focus. I move up and up and up, and therefore I simply quit.

I am the one who was

It’s interesting the things that shape us. Through the camera of my own childhood, I witnessed the battles, sacrifices, and concerns of someone who had to make it all work without having much. I was happy that my mom was so competent and my dad sympathetic, I never went without and also got an extra here or there.

Growing up, I didn’t feel shame when my mom gave me food postcards; in fact, I would have likely sparked debates about the subject, orally eviscerating anyone who dared to criticize the disabled person who was attempting to ensure all of our needs were met with so little. As a child, I watched the way the worry of not making those ends meet impacted persons I love. As the non-disabled people in my home, I did take on many of the real things because I was” the one who was” make our lives a little easier. I soon realized that putting more of myself into it was linked to fears or confusion; I am the one who does. I learned first that when something frightens me, I can double down and work harder to make it better. I am capable of taking on the issue. When individuals have seen this in me as an adult, I’ve been told I seem brave, but make no mistake, I’m not. If I seem courageous, it’s because this conduct was forged from other people’s worries.

And here I am, more than 30 years later, also feeling the urge to aimlessly force myself forward when faced with daunting tasks in front of me, assuming that I am the one who is and consequently does. I find myself driven to show that I may make things happen if I work longer hours, take on more responsibility, and do more.

Because I have seen how powerful a fiscally challenged person can be, I don’t think they are failures because they are pulled down by that flood. I really get that I have been privileged to be able to prevent many of the problems that were current in my children. That said, I am also” the one who can” who feels she does, so if I were faced with not having enough to make ends meet for my own family, I do see myself as having failed. Despite my best efforts and education, the majority of this is due to good fortune. I will, however, allow myself the arrogance of saying I have been careful with my choices to have encouraged that luck. My sense of identity comes from the notion that I am” the one who can” and feel compelled to accomplish the most. I can choose to stop, and with some quite literal cold water splashed in my face, I’ve made the choice to before. But that choosing to stop is not my go-to, I move forward, driven by a fear that is so a part of me that I barely notice it’s there until I’m feeling utterly worn away.

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

The dangerous invisibility of zealous burnout

A lot of work environments see the extra hours, extra effort, and overall focused commitment as an asset ( and sometimes that’s all it is ). They see someone attempting to overcome obstacles, not a person who is ensnared in fear. Many well-meaning organizations have safeguards in place to protect their teams from burnout. However, in situations like this, those alarms don’t always ring, and some organization members are surprised and depressed when the inevitable stop happens. And sometimes maybe even betrayed.

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

Women and burnout

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

Despite this, women are still more likely than their male counterparts to burn out, especially in these COVID stressful times. Mothers in the workplace feel the pressure to do all the “mom” things while giving 110 %. Mothers not in the workplace feel they need to do more to” justify” their lack of traditional employment. Women who are not mothers frequently feel the need to do even more because they don’t feel the pressure that comes with being a mother. It’s vicious and systemic and so a part of our culture that we’re often not even aware of the enormity of the pressures we put on ourselves and each other.

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

According to what I’ve read, this connection between work stress and health is more dangerous for women than it is for their non-female counterparts.

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

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

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

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

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

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

Do you have a plan to stop feeling this way? If something has an exit route with a pause button if it is only temporary and you have to push through it.
defined end.

Take the time to listen to your friend in the same way. Be honest, allow yourself to be uncomfortable, and break the thought cycles that prevent you from healing.

So now what?

Although what I just described is a different path to burnout, it is still burnout. There are well-established approaches to working through burnout:

• Get enough sleep.
• Eat healthy.
• Work out.
• Go outside.
• Take a break.
• Practice self-care in general.

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

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

I have come up with a few things that I do when I start to feel like I’m going into a zealous burnout to help me remember the airline attendant advice to put the mask on yourself first.

Cook an elaborate meal for someone!

Okay, since I’m a “food-focused” person, I’ve always been a fan of cooking for people. There are countless tales in my home of someone walking into the kitchen and turning right around and walking out when they noticed I was” chopping angrily”. But it’s more than that, and you should give it a try. Seriously. It’s the perfect go-to if you don’t feel worthy of taking time for yourself—do it for someone else. Because the majority of us work in a digital world, cooking can pique your interest and make you feel present in the moment in all your ways. It can break you out of your head and help you gain a better perspective. In my house, I’ve been known to pick a place on the map and cook food that comes from wherever that is ( thank you, Pinterest ). Because it’s not what I was raised making, I enjoy making Indian food because the smells are warm and the bread only needs a small amount of kneading to keep my hands busy. And in the end, we all win!

Vent like a sniveling jerk.

Be careful with this one!

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

When that is required, turn to a trusted friend and give yourself some pure verbal diarrhea by expressing all your concerns. You need to trust this friend not to judge, to see your pain, and, most importantly, to tell you to remove your cranium from your own rectal cavity. Seriously, it’s about getting a reality check here! One of the things I admire most about my husband is how he can simplify things down to their simplest bits, despite often after the fact. ” We’re spending our lives together, of course you’re going to disappoint me from time to time, so get over it” has been his way of speaking his dedication, love, and acceptance of me—and I could not be more grateful. Of course, it also required that I take my head out of that rectal cavity. So, again, usually those moments are appreciated in hindsight.

Pick up a book!

There are many books out there that are more like people sharing their stories and how they’ve come to find greater balance than they are self-help. Maybe you’ll find something that speaks to you. Among the titles that have stood out to me are:

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

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

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

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

Give yourself a break.

You are never going to be perfect—hell, it would be boring if you were. It’s OK to be broken and flawed. It’s human nature to be depressed, anxious, and tired. It’s OK to not do it all. You can’t be brave without being imperfect, which is terrifying.

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

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

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

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

Does this sound familiar?

If this sounds familiar, you’re not just going to know about it. Don’t let your negative self-talk tell you that you “even burn out wrong”. It is not improper. Even if rooted in fear like my own drivers, I believe that this need to do more comes from a place of love, determination, motivation, and other wonderful attributes that make you the amazing person you are. We’re going to be OK, ya know. The lives that come before us might never have the same meaning as the one we’re striving for, which is acceptable because the only way to judge is in the mirror when we stop and look around.

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

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

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

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 opinions can lead to conflict in projects, lower morale, and long-term, undermine trust and teamwork. Quality comments 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 comments be adjusted for rural and distributed job settings?

On the web, we may find a long history of sequential suggestions: code was written and discussed on mailing lists since the beginning of open source. 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. It generally shares many of the concepts with suggestions, but it also has some differences.

The information

The content of the feedback is the basis of every effective criticism, so where do we need to begin? There are many versions that you can use to design your content. The one that I personally like best—because it’s obvious and actionable—is this one from Lara Hogan.

This calculation, which is typically used to provide feedback to users, even fits really well in a design critique because it finally addresses one of the main issues that we address: What? Where? Why? How? Imagine that you’re giving some comments about some pattern function that spans several screens, like an onboard movement: there are some pages shown, a stream blueprint, and an outline of the decisions made. You notice a flaw in the situation. 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 fair 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 general feedback, in my experience, going back to the question approach typically leads to the best solutions because designers are generally more at ease with having an open space to experiment with.

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. Surprise surprise, my next round of criticism from a specific person wasn’t very positive. The reason is that I had previously tried not to be prescriptive in my advice—because the people who I was previously working with preferred the open-ended question format over the request style of suggestions. However, there was one person in this other team who now preferred specific guidance. So I 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. The designer might assume that the change is about consistency without the explanation, 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.

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

The tone

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 that of the content 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 time when feedback occurs is known as timing. 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 on sale, it might still be relevant if the questioning raises a significant blocker that no one saw, but those concerns are much more likely to have to wait for a later revision. So in general, attune your feedback to the stage of the project. 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. Before writing, it’s important to make sure the person we’re writing will actually benefit them and improve the overall project. 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? How can I 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: some words might cause particular reactions, some non-native speakers might not understand all the nuances of some sentences, and other times our brains might be different and we might perceive the world differently. Neurodiversity must be taken into account. Whatever the reason, it’s important to review not just what we write but how.

A few years back, I was asking for some feedback on how I give feedback. I was given some sound advice, but I also got a surprise comment. They pointed out that when I wrote” Oh, ]… ]”, I made them feel stupid. That wasn’t my intention at all! I 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 spelling mistake 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 you give it constructive and respectful feedback, whether it be difficult or positive. 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. Let’s try to think about some factors that might be helpful to consider, as there are many ways to accomplish this, and context is of course a factor.

In terms of clarity, start by grounding the critique that you’re about to give by providing context. This includes specifically describing where you’re coming from: do you have a thorough understanding of the project, or is this your first time seeing it? Are you coming from a high-level perspective, or are you figuring out the details? Are there regressions? Which user’s point of view are you addressing when offering 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 background information on the project, 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 improvement that could be made. 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 keep in mind that design is a field with hundreds of possible solutions to each problem. So pointing out that the design solution that was chosen is good and explaining why it’s good has two major benefits: it confirms that the approach taken was solid, and it helps to ground your negative feedback. 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. There is a significant difference between a critique of a design that is already in good shape and one that isn’t quite there yet.

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 also think about breaking up the feedback into sections or even across multiple comments if it is longer. 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 the impact could be quite demoralizing if I had to deliver a lot of red squares, and I’d change how I’d communicate that a little.

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 gives the impression that it’s a positive action because green is typically seen as a confirmation color. Do we need to explore a different color?
• Tiles—It seems to me that the tiles should use the Subtitle 2 style rather than the Subtitle 1 style given the number of items on the page and the overall page hierarchy. 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 good or bad about something, so we don’t say it. Or sometimes we might have a doubt that we don’t express because the question might sound stupid. Say it, that’s fine. 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.

Another benefit of asynchronous feedback is that written feedback automatically monitors decisions. 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 eight areas, including observation, impact, question, timing, attitude, form, clarity, and actionability, is a lot of work 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.

” Any reply”? is perhaps one of the worst ways to ask for opinions. It’s obscure and unfocused, and it doesn’t give us a sense of what we’re looking for. Getting good opinions starts sooner than we might hope: it starts with the demand.

When we realize that receiving input can be seen as a form of pattern analysis, it might seem counterintuitive to begin the process with a question. In the same way that we wouldn’t perform any studies without the correct questions to get the insight that we need, the best way to ask for feedback is also to build strong issues.

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

And suddenly, as with any great research, we need to review what we got up, get to the base of its perspectives, and take activity. Iteration, evaluation, and problem. This look at each of those.

The query

Being available to input is important, but we need to be specific about what we’re looking for. Any comments,” What do you think,” or” I’d love to hear your mind” at the conclusion of a presentation are likely to garner a lot of different ideas, or worse, to make everyone follow the lead of the first speaker. And next… we get frustrated because vague issues like those can change a high-level moves review into folks rather commenting on the borders of buttons. Which theme may be significant, so it might be difficult to get the team to choose the one you wanted to concentrate on.

But how do we get into this scenario? It’s a combination of various aspects. One is that we don’t often consider asking as a part of the input method. Another is how healthy it is to assume that everyone else will agree with the problem and leave it alone. Another is that in nonprofessional debate, there’s usually no need to be that exact. In summary, we tend to undervalue the value of the issues, and we don’t make any improvements to them.

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

There isn’t a second best way to ask for opinions. It simply needs to be certain, and sensitivity can take several shapes. The period than depth model for design critique has been a particularly helpful tool for my coaching.

” Stage” refers to each of the steps of the process—in our event, the design process. The type of input changes as the customer research moves on to the final design. But within a single stage, one might also examine whether some assumptions are correct and whether there’s been a suitable language of the amassed input into updated designs as the job has evolved. The layers of user experience could serve as a starting point for potential questions. What do you want to know: Project objectives? user requirements? Functionality? the content Interaction design? a system of information architecture UI design? design of navigation Visual design? Branding?

Here’re a few example questions that are precise and to the point that refer to different layers:

• Functionality: Is it desirable to automate account creation?
• Interaction design: Take a look through the updated flow and let me know whether you see any steps or error states that I might’ve missed.
• Information architecture: This page contains two competing pieces of information. Is the structure effective in communicating them both?
• User interface design: What do you think about the top-of-the-page error counter, which makes sure you can see the next error even when the error is outside the viewport?
• Navigation design: From research, we identified these second-level navigation items, but once you’re on the page, the list feels too long and hard to navigate. Exist any recommendations for resolving this?
• Visual design: Are the sticky notifications in the bottom-right corner visible enough?

The other axis of specificity is determined by how far you’d like to go with the information being presented. For example, we might have introduced a new end-to-end flow, but there was a specific view that you found particularly challenging and you’d like a detailed review of that. This can be especially helpful when switching between iterations because it’s crucial to highlight the changes made.

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

A quick fix is to get rid of the generic qualifiers from questions like “good”, “well,” “nice,” “bad,” “okay,” and” cool.” For example, asking,” When the block opens and the buttons appear, is this interaction good”? is possible to appear specific, but the “good” qualifier can be found in an even better question,” When the block opens and the buttons appear, is it clear what the next action is?”

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

Sometimes the project is particularly broad, and some areas may have already been thoroughly explored. In these situations, it might be useful to explicitly say that some parts are already locked in and aren’t open to feedback. Although it’s not something I’d recommend in general, I’ve found it helpful in avoiding getting back into rabbit holes like those that could lead to even more refinement if what’s important right now isn’t.

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

The iteration

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

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

There are many benefits to using iteration posts:

• It creates a rhythm in the design work so that the designer can review feedback from each iteration and prepare for the next.
• Decisions are always available, and conversations are also made accessible for future review.
• It creates a record of how the design changed over time.
• Depending on the tool, it might also make it simpler to collect and act on feedback.

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

I don’t think there’s a standard format for iteration posts. However, there are a few high-level components that make sense to include as a baseline:

1. The goal
2. The layout
3. The list of changes
4. The querys

Each project is likely to have a goal, and hopefully it’s something that’s already been summarized in a single sentence somewhere else, such as the client brief, the product manager’s outline, or the project owner’s request. Therefore, I would repeat this in every iteration post, literally copy and pasting it. The idea is to provide context and to repeat what’s essential to make each iteration post complete so that there’s no need to find information spread across multiple posts. The most recent iteration post will have everything I need if I want to know about the most recent design.

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

The design is then the actual series of information-architecture outlines, diagrams, flows, maps, wireframes, screens, visuals, and any other kind of design work that’s been done. In essence, it’s any design work. For the final stages of work, I prefer the term blueprint to emphasize that I’ll be showing full flows instead of individual screens to make it easier to understand the bigger picture.

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

For an efficient discussion, you should also include a bullet list of the changes from the previous iteration to let people focus on what’s new, which can be especially useful for larger pieces of work where keeping track, iteration after iteration, could become a challenge.

Finally, as mentioned earlier, a list of the questions must be included in order to help you guide the design critique in the desired direction. Doing this as a numbered list can also help make it easier to refer to each question by its number.

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

I want to highlight that even if these iteration posts are written and conceived as checkpoints, by no means do they need to be exhaustive. A post might be a draft, just a concept to start a discussion, or it might be a cumulative list of all the features that have been added over the course of each iteration until the full picture is achieved.

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

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

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

The review

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

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

1. It removes the pressure to reply to everyone.
2. It lessens the annoyance of snoop-by comments.
3. It lessens our personal stake.

The first friction point is having to feel pressured to respond to each and every comment. Sometimes we write the iteration post, and we get replies from our team. It’s just a few of them, it’s simple, and there isn’t much to worry about. But other times, some solutions might require more in-depth discussions, and the amount of replies can quickly increase, which can create a tension between trying to be a good team player by replying to everyone and doing the next design iteration. This might be especially true if the respondent is a stakeholder or a person who is directly involved in the project and whom we feel we need to speak with. We need to accept that this pressure is absolutely normal, and it’s human nature to try to accommodate people who we care about. When responding to all comments, it can be effective, but when we consider a design critique more like user research, we realize that we don’t need to respond to every comment, and there are alternatives in asynchronous spaces:

One is to let the next iteration speak for itself. The response is received when the design changes and a follow-up iteration is made. You might tag all the people who were involved in the previous discussion, but even that’s a choice, not a requirement.
• Another tactic is to formally acknowledge each comment in a brief response, such as” Understood. Thank you”,” Good points— I’ll review”, or” Thanks. In the upcoming iteration, I’ll include these. In some cases, this could also be just a single top-level comment along the lines of” Thanks for all the feedback everyone—the next iteration is coming soon”!
• Another option is to quickly summarize the comments before moving on. Depending on your workflow, this can be particularly useful as it can provide a simplified checklist that you can then use for the next iteration.

The swoop-by comment, which is the kind of feedback that comes from a member of a team or non-project who might not be aware of the context, restrictions, decisions, or requirements, or of the discussions from earlier iterations, is the second friction point. On their side, there’s something that one can hope that they might learn: they could start to acknowledge that they’re doing this and they could be more conscious in outlining where they’re coming from. Swoop-by comments frequently prompt the simple thought,” We’ve already discussed this,” and it can be frustrating to have to keep saying the same thing over and over.

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

Swoop-by commenting can still be useful for two reasons: first, they might point out something that isn’t clear, and second, they might have the power to represent a user’s first impression of the design. Sure, you’ll still be frustrated, but that might at least help in dealing with it.

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

Always remember that while you need to listen to stakeholders, project owners, and specific advice, you don’t have to accept every piece of feedback. You must examine it and come up with a rationale for your choice, but sometimes “no” is the best choice.

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

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