Blog

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 interesting activities. Yet my friends and I had movie ideas to make and sky in. But they never went any farther. However, I did end up working in user experience ( UI). Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer research is story. And you must show a compelling story to entice stakeholders, such as the product team and decision-makers, to learn more in order to get the most out of consumer research.

Think of your favourite film. It more than likely follows a three-act construction that’s frequently seen in movies: the installation, the conflict, 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. The issue begins in Act 2, which introduces the issue. Here, issues grow or get worse. And the solution is the third and final work. This is where the issues are resolved and the figures learn and change. This structure, in my opinion, is also a fantastic way to think about consumer research, and I think it can be particularly useful for explaining consumer research to others.

Use story as a framework for conducting research

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

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

Act one: installation

The fundamental research comes in handy because the layout is all about understanding the background. Basic research ( also called relational, discovery, or preliminary research ) helps you understand people and identify their problems. Just like in the movies, you’re learning about the difficulties customers face, what options are available, and how those challenges impact them. To do basic research, you may conduct situational 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 discusses the most effective anthropology, which can be as straightforward as spending 15 hours with a customer and asking them to” Walk me through your morning yesterday.” That’s it. Current that one ask. Opened up and listen to them for 15 days. Do everything in your power to keep yourself and your pursuits out of it. Bam, you’re doing ethnography”. According to Hall, “[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”.

This makes perfect sense to me. And I love that this makes consumer studies so visible. You can simply attract participants and carry out the recruitment process without having to create a lot of paperwork! This can offer a wealth of knowledge about your customers, and it’ll help you better understand them and what’s going on in their life. That’s exactly what work one is all about: understanding where people are coming from.

Maybe Spool talks about the importance of basic research and how it may type the bulk of your research. If you can supplement what you’ve heard in the fundamental studies by using any more user data that you can obtain, such as surveys or analytics, to make recommendations that may need to be investigated further, you might as well use those that can be drawn from those that you can obtain. Together, all this information creates a clearer picture of the state of things and all its 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 characters and support their success, much like in films. And maybe partners are now doing the same. Their business may lose money because users can’t finish particular tasks, which may be their love. Or probably they do connect with people ‘ problems. In either case, action one serves as your main strategy for piqueing interest and investment from 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 gains everyone—users, the goods, and partners. It’s similar to winning an Oscar for a film because it frequently results in a favorable and productive outcome for your item. And this can be an opportunity for participants to repeat this process with different products. The secret to this method is storytelling, and knowing how to tell a compelling story is the only way to entice participants to do more research.

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

Act two: fight

Act two is all about digging deeper into the issues that you identified in operate one. In order to evaluate a potential alternative ( such as a design ), you typically conduct vertical research, such as usability tests, to see if it addresses the problems you identified. The issues may include unfulfilled needs or problems with a circulation or procedure that’s tripping users away. Additional problems will arise in the course of action two of a film. 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:” You learn less and less as you add more and more users because you will keep seeing the same things over and over again… After the second user, you are wasting your time by constantly observing the similar findings but no 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 memorable and accessible to other stakeholders when presenting 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 tens of thousands of years, but remote testing can also be done using software like Microsoft Teams, Zoom, or other teleconferencing tools. This approach has become increasingly popular since the beginning of the pandemic, and it works well. You might consider in-person usability tests like watching a movie as opposed to remote testing like attending a play. There are advantages and disadvantages to each. Much more in-depth research is conducted on user experience. Stakeholders can experience the sessions with other stakeholders. You also get real-time feedback on what they’re seeing, including surprises, disagreements, and discussions about them. Much like going to a play, where audiences get to take in the stage, the costumes, the lighting, and the actors ‘ interactions, in-person research lets you see users up close, including their body language, how they interact with the moderator, and how the scene is set up.

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

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

You can ask real users questions to understand their thoughts and understanding of the solution as a result of usability testing, whether it is conducted remotely or in person. This can help you not only identify problems but also glean why they’re problems in the first place. You can also test your own ideas and determine whether they are true. 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. The excitement is in the second act, but there are also potential surprises in the third. 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 also frequently the only research technique that some stakeholders believe they ever need, and too frequently. In fact, if the designs that you’re evaluating in the usability test aren’t grounded in a solid understanding of your users ( foundational research ), there’s not much to be gained by doing usability testing in the first place. Because you’re narrowing the scope of what you’re receiving feedback on without understanding the needs of the users. As a result, there’s no way of knowing whether the designs might solve a problem that users have. In the context of a usability test, it’s only feedback on a particular design.

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

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

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 all members of the product team, including developers, UX experts, business analysts, delivery managers, product managers, and any other interested parties. It allows the whole team to hear users ‘ feedback together, ask questions, and discuss what’s possible within the project’s constraints. Additionally, it enables the UX design and research teams to clarify, suggest alternatives, or provide more context for their choices. So you can get everyone on the same page and get agreement on the way forward.

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

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

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

You can reinforce your recommendations with examples of things that competitors are doing that could address these issues or with examples where competitors are gaining an edge. Or they can be visual, like quick sketches of how a new design could look that solves a problem. These can help generate conversation and momentum. And this continues until the session is over when you’ve concluded everything by summarizing the key points and offering suggestions for a solution. 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, hoped, the motivation to take those steps!

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

Act one: You 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 encounter problems and difficulties, which they must overcome, and there is conflict and tension. In act two, researchers might use methods including usability testing, competitive benchmarking, and heuristics evaluation. Usability findings reports, UX strategy documents, usability guidelines, and best practices can be included in the output of these.

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

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

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

I’ve lost count of the times when promising ideas go from being useless in a few days to being useless after working as a solution designer for too long to explain.

Financial goods, which is my area of expertise, 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, you see this:

The perils of feature-first growth

It’s simple to get swept up in the enthusiasm of developing innovative features when you start developing a financial product from scratch or are migrating existing client journeys from papers or telephony channels to online bank or mobile apps. You might be thinking,” If I can only put one more thing that solves this particular person problem, they’ll appreciate me”! What happens, however, when you eventually encounter a roadblock caused by your safety team? don’t like it, right? When a battle-tested film isn’t as well-known as you anticipated or when it fails due to unforeseen difficulty?

The concept of Minimum Viable Product ( MVP ) is applied to this. Even if Jason Fried doesn’t usually refer to this concept, his book Getting Real and his radio Rework frequently discuss it. An MVP is a product that offers only sufficient value 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 include.

The issue with most funding 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. This implies that the priority is to provide as many features and functionalities as possible to satisfy the requirements and desires of competing inside sections as opposed to a distinct value statement that is focused on what people in the real world actually want. As a result, these products can very quickly became a mixed bag of misleading, related, and finally unhappy customer experiences—a feature salad, you might say.

The significance of the foundation

What is a better strategy, then? How can we create items that are reliable, user-friendly, and most importantly, stick?

The concept of “bedrock” comes into play here. Rock is the main feature of your item that really matters to customers. 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 servicing journeys in the world of retail bank, which is where I work. People only look at their existing account once every blue moon, but they do so daily. They sign up for a credit card every year or two, but they check their balance 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.

But how do you reach the foundation? By focusing on the” MVP” strategy, giving clarity the top priority, and working toward a distinct value proposition. This means avoiding unnecessary characteristics and putting your customers first, and adding real value.

It also requires some nerve, as your coworkers might not always agree on your eyesight at first. And dubiously, occasionally it can even suggest making it clear to customers that you won’t be coming to their house and making their breakfast. 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 financial goods

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

1. What trouble are you trying to solve first and foremost with a distinct “why”? Who is it for? Before beginning any project, 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 benefit, and work from that.
3. When it comes to financial items, clarity is often more important than complexity. Eliminate unwanted details and concentrate solely on what matters most.
4. Accept ongoing iteration as Bedrock is a powerful process rather than a fixed destination. Continuously collect customer feedback, improve your product, and work toward that foundational position.
5. Stop, look, and listen: Don’t just go through with testing your product as part of the delivery process; test it consistently in the field. Use it for yourself. Move the A/B testing. User opinions on Gatter. Talk to those who use it, and change things up correctly.

The core dilemma

Building towards rock implies sacrificing some short-term growth prospective in favor of long-term balance, which is an interesting paradox at play here. But the reward is worthwhile because products built with a focus on rock will outlive and surpass their rivals over time and provide users with long-term value.

How do you begin your quest for rock, then? Take it slowly. 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, make an obsessive effort because, whatever you think, Abraham Lincoln, Alan Kay, or Peter Drucker, you can’t deny it! The best way to foretell the future is to make it, he said.

Picture this: Two people are conversing in what appears to be the same talk about the same pattern issue in a conference room at your tech company. One is talking about whether the staff has the proper skills to handle it. The other is examining whether the solution truly addresses the user’s issue. Similar place, the same issue, and entirely different perspectives.

This is the lovely, sometimes messy fact of having both a Design Manager and a Guide Designer on the same group. And you’re asking the right question if you’re wondering how to make this job without creating confusion, coincide, or the feared” to some cooks” situation.

The conventional solution has been to create clear traces on an organizational chart. The Design Manager handles persons, the Lead Designer handles art. Problem solved, is that correct? Except for dream, clear org charts. In fact, both roles care greatly about crew health, style quality, and shipping great work.

When you start thinking of your style organization as a style organism, the magic happens when you embrace the coincide rather than fighting it.

A Healthy Design Team’s Biology

Here’s what I’ve learned from years of being on both sides of this formula: think of your design team as a living cell. The layout manager is guided by the group dynamics, emotional security, and career growth. The Lead Designer concentrates on the body ( the handiwork, the design standards, the hands-on projects that are delivered to users ).

But just like mind and body aren’t totally separate systems, but, also, do these tasks overlap in significant ways. Without working in harmony with one another, you didn’t have a good person. The technique is to recognize those overlaps and how to understand them gently.

When we look at how good team really function, three critical devices emerge. Each requires the collaboration of both jobs, but one must assume the lead role in maintaining that system sturdy.

The Nervous System: Citizens & Psychology

Major custodian: Design Manager
Supporting position: Guide Custom

The anxious system is all about mental health, comments, and signals. When this technique is good, information flows easily, people feel safe to take risks, and the staff may react quickly to new problems.

The primary caregiver is around, the Design Manager. They are keeping track of the team’s mental state, making sure feedback loops are good, and creating the environment for growth. They’re hosting job meetings, managing task, and making sure no single burns out.

However, the Lead Designer has a significant supporting position. They’re offering visual feedback on build development needs, identifying stagnant design skills in someone, and pointing out potential growth opportunities that the Design Manager might overlook.

Design Manager tends to:

• discussions about careers and career development
• emotional stability and dynamics of the team
• Job management and resource allocation
• Performance evaluations and opinions mechanisms
• Providing opportunities for learning

Direct Custom supports by:

• Providing craft-specific coaching for crew members
• identifying opportunities for growth and style talent gaps
• Giving design mentoring and assistance
• indicating when staff members are prepared for more challenging problems.

The Muscular System: Design & Execution

Major caregiver: Lead Designer
Supporting position: Design Manager

Power, cooperation, and skill development are the hallmarks of the skeletal system. When this technique is healthy, the team can do complicated design work with precision, maintain regular quality, and adjust their craft to fresh challenges.

The Lead Designer is in charge of everything here. They are establishing design standards, offering craft instruction, and making sure that shipping work meets the required standards. They’re the ones who can tell you if a design decision is sound or if we’re solving the right problem.

However, the Design Manager has a significant supporting role. They are making sure the team has the resources and support they need to perform their best work, including ensuring that an athlete receives adequate nutrition and time for recovery.

Lead Designer tends to:

• Definition of system requirements and design standards
• Feedback on design output that meets the required standards
• Experience direction for the product
• Design choices and product-wide alignment are important.
• advancement of craft and innovation

Design Manager supports by:

• ensuring that all members of the team are aware of and adopting design standards
• Confirming that the right course of action is being taken
• Supporting practices and systems that scale without bottlenecking
• facilitating team-wide design alignment
• Providing resources and removing obstacles to outstanding craft work

The Circulatory System: Strategy &amp, Flow

Both the lead designer and the design manager were caretakers.

The circulatory system is about how decisions, energy, and information flow through the team. When this system is healthy, strategic direction is clear, priorities are aligned, and the team can respond quickly to new opportunities or challenges.

This is the true partnership that occurs. Although both positions bring unique perspectives, keeping the circulation strong is a dual responsibility.

Lead Designer contributes:

• The product fulfills the user’s needs.
• overall experience and product quality
• Strategic design initiatives
• User requirements for each initiative are based on research.

Contributes the design manager:

• Communication to team and stakeholders
• Stakeholder management and alignment
• Team accountability across all levels
• Strategic business initiatives

Both parties work together:

• Co-creation of strategy and leadership
• Team goals and prioritization approach
• organizational structure decisions
• Success frameworks and measures

Keeping the Organism Healthy

Understanding that all three systems must work together is the key to making this partnership sing. A team will eventually lose their way despite excellent craftmanship and poor psychological security. A team with great culture but weak craft execution will ship mediocre work. A team that has both but poor strategic planning will concentrate on the wrong things.

Be Specific About the System You’re Defending.

When you’re in a meeting about a design problem, it helps to acknowledge which system you’re primarily focused on. Everyone has context for their input.” I’m thinking about this from a team capacity perspective” ( nervous system ) or” I’m looking at this through the lens of user needs” ( muscular system ).

It’s not about staying in your lane. It’s about being transparent as to which lens you’re using, so the other person knows how to best add their perspective.

Create Positive Feedback Loops

Which partnerships have created clear feedback loops between the systems in the most effective ways?

Nervous system signals to muscular system:” The team is struggling with confidence in their design skills” → Lead Designer provides more craft coaching and clearer standards.

The nervous system receives the message” The team’s craft skills are progressing more quickly than their project complexity.”

We’re seeing patterns in team health and craft development that suggest we need to adjust our strategic priorities, both systems say to the circulatory system.

Handle Handoffs Gracefully

When something switches from one system to another, this partnership’s most crucial moments occur. This might occur when a design standard ( muscular system ) needs to be implemented across the team ( nervous system ) or when a tactical initiative ( circulatory system ) requires specific craft execution ( muscular system ).

Make these transitions explicit. The new component standards have been defined. Can you give me some ideas on how to get the team up to speed?” or” We’ve agreed on this strategic direction. From here, I’ll concentrate on the specific user experience approach.

Stay curious and avoid being territorial.

The Design Manager who never thinks about craft, or the Lead Designer who never considers team dynamics, is like a doctor who only looks at one body system. Even when they aren’t the primary caretaker, great design leadership requires both people to be as concerned with the entire organism.

Rather than making assumptions, one must ask questions. ” What do you think about the team’s craft development in this area”? or” How do you think this is affecting team morale and workload”? keeps both viewpoints present in every choice.

When the Organism Gets Sick

This partnership has the potential to go wrong, even with clear roles. Here are the most typical failure modes I’ve seen:

System Isolation

The Design Manager ignores craft development and only concentrates on the nervous system. The Lead Designer ignores team dynamics and only concentrates on the muscular system. Both people retreat to their comfort zones and stop collaborating.

The signs: Mixed messages are sent to team members, poor morale is attained, and there are negative things.

Reconnect around common goals in the treatment. What are you both trying to achieve? It’s typically excellent design work that arrives on time from a capable team. Discover how both systems accomplish that goal.

Poor Circulation

There is no clear strategic direction, shifting priorities, or accepting responsibility for keeping information flowing.

The signs: Team members are unsure of their priorities, work is duplicated or dropped, and deadlines are missed.

The treatment: Explicitly assign responsibility for circulation. Who is communicating with whom? How frequently? What’s the feedback loop?

Autoimmune Response

One person feels threatened by the other’s skill set. The Design Manager thinks the Lead Designer is undermining their authority. The Design Manager is alleged to believe that the Lead Designer doesn’t understand craft.

The signs: defensive behavior, territorial disputes, team members sucked into the middle.

The treatment: Remember that you’re both caretakers of the same organism. The entire team suffers when one system fails. The team thrives when both systems are strong.

The Payoff

Yes, there is more communication required with this model. Yes, it requires that both parties be confident enough to assume full responsibility for team health. But the payoff is worth it: better decisions, stronger teams, and design work that’s both excellent and sustainable.

The best of both worlds can be found in the combination of strong people leadership and deep craft expertise. One person can help keep the team’s health when one is sick, on vacation, or overjoyed. When a decision requires both the people perspective and the craft perspective, you’ve got both right there in the room.

The framework has a balance, which is crucial. You can use the same system thinking to new challenges as your team grows. Need to launch a design system? Both the muscular system ( standards and implementation ), the nervous system (team adoption and change management ), and both have a tendency to circulate ( communication and stakeholder alignment ).

The End result

The relationship between a Design Manager and Lead Designer isn’t about dividing territories. It’s about multiplying impact. Magic occurs when both roles are aware that they are promoting various aspects of a healthy organism.

The mind and body work together. The team benefits from both strategic thinking and craftmanship. And most importantly, the work that is distributed to users benefits both sides.

So the next time you’re in that meeting room, wondering why two people are talking about the same problem from different angles, remember: you’re watching shared leadership in action. And if it’s functioning well, your design team’s mind and body will both become stronger.

In Colossal Biosciences ‘ novel offices and facilities, you can see and marvel at all its sights and wonders. Colossal proudly displays the footsteps of both species in [ …] as the Texas-based biotech company that broke the internet twice this spring, first with the revelation that they created “woolly rabbits” and then a resurrected version of the dire wolf.

The first article on Den of Geek was Colossal Biosciences Is Changing the Concept of Conservation and Red Wolves Forever.

Superman has a capable sorcerer’s gallery under his belt. You might just know this from comic book shows, where the Man of Steel alternates between Lex Luthor and General Zod, but aside from Batman, Spider-Man, and perhaps the X-Men, Kal-El has one of the top criminal schedules in comic book history.

So it’s interesting that writer-director James Gunn revealed in his wonder Wednesday statement about Superman 2 that the film is then entitled Man of Tomorrow and is on the verge of a July 9, 2027 release date, as well as that it looks like it might feature Nicholas Hoult‘s Lex Luthor and David Corenswet’s Clark Kent, although not as you might have expected to see the shaven evil genius.

In the following social media post, where Superman and Lex are seen side by side with the evil LuthorCorp CEO in some sort of mecha super-suit, and Superman leaning on his rival ‘ back while Jim Lee pencils a gathering of them. They appear to be working together, if we read the repercussions effectively. !

For the record, the picture is from 2025 and appears to be one Lee created specifically for Gunn’s news. If so, it heavily influenced by the suit Luthor wore in DCeased, a DC Comics event in which an alternate reality DC Universe is infected by a zombie-like virus created by the inhabitants of Apokolips ( remember them, Snyder fans? ). Metropolis is thus completely destroyed by the disease, which depresses Luthor so much that he teams up with Superman to save what is left of the rest of the world.

We do not believe James Gunn will end up in Metropolis, which is his only other Superman film, and instead we focus on some calamitous doom and gloom plot. This is no more the Adherence, is that correct?

However, it seems as though he is ripping off that story and others, where a love of Metropolis and other things will put Superman and Luthor in a detente and partnership state despite their basic animosity. Given how severe xenophobia and prejudice Hoult’s Luthor expressed toward refugee Superman in this earlier summer’s movie, it is humorous. One might even believe that the Person of Today’s big statement about being a great person got through to the selfish billionaire at the end of Superman if one wants to be fully guileless and “punk rock” in a Clark Kent sense.

However, it’s more likely that Clark don’t trust his, um, ancient friend too much like Charles Xavier in a 20th Century Fox X-Men video.

What danger may be severe enough to cause them to subscribe forces, according to the news? Perhaps even more arrogant and naught than the CEO of LuthorCorp?

Programs for Gunn’s DCU are changing quickly after Superman‘s relatively warm welcome, as evidenced by the news that Guy of Tomorrow is being fast tracked only two years after Superman and one month after Milly Alcock’s expected summer film Milly Alcock. The film’s visual debut for DC Universe exceeded$ 600 million worldwide, marking a first for a DC film in a while. That’s a far cry from some of DC’s pictures from the decade, but the negative impression those movies left in viewers appeared to indicate significant declines in the success of their sequels and follow-ups.

In two decades, we might be able to determine whether Superman and the greater DC Universe are on a different direction, as Batman Begins to The Dark Knight. Then if you’ll pardon us, it’s time to fire some Magnificent Crabjoys.

The second postSuperman 2: James Gunn hinted at Lex Luthor Rematch and Retitled Sequel launch date first appeared on Den of Geek.

28 Years After clues are included in this article. When 28 Times After came to an end this past summer, some people were genuinely perplexed. The final 90 or so hours of the Danny Boyle and Alex Garland sequel to their [ …] series come after watching a wistful and, as we would argue, beatific meditation on death and the bitter enjoyment in mortality.

The first episode of Den of Geek was titled 28 Times After: The Bone Temple Trailer Hints at the Creepier Role of Jimmy by JackO’Connell.

Superman has a capable sorcerer’s gallery to his credit. You might just know this from comic book shows, where the Man of Steel alternates between Lex Luthor and General Zod, but aside from Batman, Spider-Man, and perhaps the X-Men, Kal-El has one of the top criminal schedules in comic book history.

So it’s interesting that writer-director James Gunn revealed in his amazement Wednesday statement about Superman 2 that the film is then entitled Man of Tomorrow and is on the verge of a July 9, 2027 release date, as well as that it might not have been expected to feature the shaven evil genius.

In the following social media post, where Superman and Lex are seen side by side with the evil LuthorCorp CEO in some sort of mecha super-suit, and Superman leaning on his rival ‘ back while Jim Lee pencils a gathering of them. If we interpret the implications effectively, it appears as though they’re working together. !

For the record, the picture is from 2025 and appears to be one Lee created specifically for Gunn’s statement. If so, it &#8217 is heavily influenced by the suit Luthor wore in the 2019 DC Comics event, DCeased, where an alternate reality DC Universe is infected by a zombie-like virus created by the Apokolips ( remember them, Snyder fans? ). Metropolis is thus completely destroyed by the disease, which depresses Luthor so much that he teams up with Superman to save what is left of the rest of the world.

For the report, we do not believe James Gunn will end up destroying Metropolis and instead embark on some ominous doom and gloom plot in his next Superman film. Ah, I guess the Adherence is no longer there, straight?

However, it seems as though he is transferring that scene and other stories where Superman and Luthor may remain in a relationship and detente despite their shared enmity and passion of Metropolis. Given how aggressive xenophobia and hatred Hoult’s Luthor expressed toward refugee Superman in this earlier summer’s movie, it is humorous. One might even believe that the Person of Today’s big statement about being a great person got through to the selfish billionaire at the end of Superman if one wants to be fully guileless and “punk rock” in a Clark Kent sense.

However, it’s more likely that Clark don’t trust his, um, ancient friend too much like Charles Xavier in a 20th Century Fox X-Men film.

What potential menace could be so great that they would join forces, according to the statement? Perhaps even more useless and arrogant than the CEO of LuthorCorp?

Ideas for Gunn’s DCU are changing quickly after the relatively warm reception Superman received, especially with the information that Man of Monday is being fast tracked only two decades after Superman and one year after Milly Alcock’s planned summer film Milly Alcock. The film’s visual start for DC Universe exceeded$ 600 million globe, which is a first for a DC film in a while. That’s a far cry from some of DC’s pictures from the decade, but the negative impression those movies left in viewers appeared to indicate significant declines in the success of their sequels and follow-ups.

In two decades, therefore, we might be able to determine whether Superman and the greater DC Universe are on a different direction, as Batman Begins to The Dark Knight. If you’ll pardon us, it’s time to unleash some Magnificent Crabjoys.

The second postSuperman 2: James Gunn Hints at Lex Luthor Rematch and Retitled Sequel was published on Den of Geek.

The time of bothers has begun in Central Florida with next year’s grand entry of Halloween Horror Nights at Universal Studios Florida, despite the high temperatures of around 90 degrees Celsius. I attended the media day function, where I saw all 10 haunted houses, half of which were based on well-known franchises like Terrifier and Fallout.

What to Expect at Universal After Epic Universe: What to Expect from Halloween Horror Nights initially appeared on Den of Geek.

Superman has a capable sorcerer’s gallery to his credit. Although the Man of Steel faces alternating rounds between Lex Luthor and General Zod, you might not realize this until you just view comic book movies, but aside from Batman, Spider-Man, and perhaps the X-Men, Kal-El has one of the best villain rosters in comic book history.

So it’s interesting that writer-director James Gunn revealed in his wonder Wednesday statement about Superman 2 that the film is then entitled Man of Tomorrow and is on the verge of a July 9, 2027 release date, as well as that it looks like it might feature Nicholas Hoult‘s Lex Luthor and David Corenswet’s Clark Kent, although not as you might have expected to see the shaven evil genius.

In the following social media post, where the name and date are displayed, we see a Jim Lee penciled drawing of Superman and Lex standing next to the terrible LuthorCorp CEO in some sort of mecha super-suit, and Superman leaning on his rival ‘ back while Superman is holding a hammer. If we interpret the implications effectively, it appears as though they’re working together. !

For the record, the picture appears to have been created by Lee especially for Gunn’s statement in 2025. If so, it &#8217 is heavily influenced by the suit Luthor wore in the 2019 DC Comics event, DCeased, where an alternate reality DC Universe is infected by a zombie-like virus created by the Apokolips ( remember them, Snyder fans? ). Metropolis is thus completely destroyed by the influenza, which depresses Luthor so much that he teams up with Superman to save what is left of the rest of the world.

For the record, we do not believe James Gunn will kill Metropolis and instead embark on some calamitous doom and gloom story in his second Superman film. Ah, this is no longer the Adherence, isn’t it?

However, it does seem as though he is ripping off that story and others where Superman and Luthor will come into a position of detente and collaboration despite their public animosity and a love of Metropolis. Given how severe xenophobia and prejudice Hoult’s Luthor expressed toward refugee Superman in this earlier summer’s movie, it is humorous. At the conclusion of Superman, one might assume that the Man of Tomorrow’s large conversation about being a good person addressed the selfish billionaire.

However, it’s more likely that Clark don’t trust his, um, ancient friend too much like Charles Xavier in a 20th Century Fox X-Men video.

What danger may get bad enough to cause them to subscribe troops, according to the statement? Perhaps even more arrogant and naught than the CEO of LuthorCorp?

Programs for Gunn’s DCU are changing quickly after Superman‘s relatively warm welcome, as evidenced by the news that Guy of Tomorrow is being fast tracked only two years after Superman and one month after Milly Alcock’s expected summer film Milly Alcock. The film’s visual debut for DC Universe exceeded$ 600 million worldwide, marking a second for a DC film in a while. That’s a far cry from some of DC’s pictures from the decade, but the negative impression those movies left on viewers appeared to indicate significant declines in the success of their sequels and follow-ups.

In two decades, we might be able to determine whether Superman and the greater DC Universe are on a different direction, as Batman Begins to The Dark Knight. If you’ll pardon us, it’s time to unleash some Magnificent Crabjoys.

The second postSuperman 2: James Gunn Hints at Lex Luthor Rematch and Retitled Sequel was published on Den of Geek.

This article contains spoilers for Wednesday Season 2. That initial dance series from Wednesday’s next year has an extremely crafty quality. After screenwriters Alfred Gough and Miles Millar pleaded for months that they would not attempt to replicate the popular demand from the show’s first year, when Jenna Ortega’s eponymous character allegedly vanished across a room [ …]…

Den of Geek‘s first article Inside Wednesday Season 2: Going K-Pop with New Dances.

Superman has a capable sorcerer’s gallery under his belt. You might just know this from comic book shows, where the Man of Steel alternates between Lex Luthor and General Zod, but aside from Batman, Spider-Man, and perhaps the X-Men, Kal-El has one of the top criminal schedules in comic book history.

So it’s interesting that writer-director James Gunn revealed in his wonder Wednesday statement about Superman 2 that the film is then entitled Man of Tomorrow and is on the verge of a July 9, 2027 release date, as well as that it looks like it might feature Nicholas Hoult‘s Lex Luthor and David Corenswet’s Clark Kent, although not as you might have expected to see the shaven evil genius.

In the following social media post, where Superman and Lex are seen side by side with the evil LuthorCorp CEO in some sort of mecha super-suit, and Superman leaning on his rival ‘ back while Jim Lee pencils a gathering of them. They appear to be working together, if we read the repercussions properly. !

For the record, the photo is from 2025 and appears to be one Lee created specifically for Gunn’s news. If so, it &#8217 is heavily influenced by the suit Luthor wore in the 2019 DC Comics event, DCeased, where an alternate reality DC Universe is infected by a zombie-like virus created by the Apokolips ( remember them, Snyder fans? ). Metropolis is thus completely destroyed by the influenza, which depresses Luthor so much that he teams up with Superman to save what is left of the rest of the world.

For the record, we do not believe James Gunn will destroy Metropolis and instead embark on some calamitous doom and gloom story in his second Superman film. This is no more the Adherence, is that correct?

However, it seems as though he is transferring that scene and other stories where Superman and Luthor will remain in a relationship and detente despite their shared enmity and passion of Metropolis. Given how severe xenophobia and prejudice Hoult’s Luthor expressed toward refugee Superman in this earlier summer’s movie, it is humorous. At the conclusion of Superman, one might believe that the Man of Tomorrow’s large conversation about being a good person addressed the selfish billionaire.

… More good, though, is that Clark don’t underestimate his, um, old companion like Charles Xavier in a 20th Century Fox X-Men film.

What danger may be severe enough to cause them to subscribe forces, according to the news? Perhaps even more arrogant and naught than the CEO of LuthorCorp?

Ideas for Gunn’s DCU are changing quickly after the relatively warm reception Superman received, especially with the information that Man of Monday is being fast tracked only two decades after Superman and one year after Milly Alcock’s expected summer film debut. The DC Universe’s visual debut did indeed surpass$ 600 million globe, which is a second for a DC film in a while. That’s a far cry from the levels of some of DC’s movies from the decade, but the negative impression those movies left in viewers appeared to indicate significant declines in the success of their sequel and follow-ups.

In two decades, therefore, we might be able to determine whether Superman and the greater DC Universe are on a different direction, as Batman Begins to The Dark Knight. Then if you’ll pardon us, it’s time to fire some Magnificent Crabjoys.

The second postSuperman 2: James Gunn hinted at Lex Luthor Rematch and Retitled Sequel release meeting first appeared on Den of Geek.

This article contains spoilers for instance 5 of Alien: Earth. Was someone expecting the Fargo chairman to produce an unexpected Alien film deserving of Ridley Scott himself when Noah Hawley’s Alien: Earth slogs into its second third as the USCSS Maginot sailed toward Prodigy City? Despite being accused of both Scott’s Prometheus and Alien: Covenant,

Den of Geek‘s first blog: Alien: Earth Episode 5 Theory Hints at an Ancient Xenomorph Enemy.

Superman has a capable bandit’s exhibition under his belt. You might just know this from comic book shows, where the Man of Steel alternates between Lex Luthor and General Zod, but aside from Batman, Spider-Man, and perhaps the X-Men, Kal-El has one of the top criminal schedules in comic book history.

So it’s interesting that writer-director James Gunn revealed in his wonder Wednesday statement about Superman 2 that the film is then entitled Man of Tomorrow and is on the verge of a July 9, 2027 release date, as well as that it looks like it might feature Nicholas Hoult‘s Lex Luthor and David Corenswet’s Clark Kent, although not as you might have expected to see the shaven evil genius.

In the following social media post, where Superman and Lex are seen side by side with the evil LuthorCorp CEO in some sort of mecha super-suit, and Superman leaning on his rival ‘ back while Jim Lee pencils a gathering of them. They appear to be working together, if we read the repercussions effectively. !

For the record, the picture appears to have been created by Lee especially for Gunn’s statement in 2025. If so, it heavily influenced by the suit Luthor wore in DCeased, a DC Comics event in which an alternate reality DC Universe is infected by a zombie-like virus created by the inhabitants of Apokolips ( remember them, Snyder fans? ). Luthor and Superman team up as a result of Metropolis being completely destroyed by the disease, which saddens him so much that it makes him work with him to keep what is left of the world.

We do not believe James Gunn will end up in Metropolis, which is his only other Superman film, and instead we focus on some calamitous doom and gloom plot. Ah, I guess the Adherence is no longer there, straight?

However, it seems as though he is transferring that scene and other stories where Superman and Luthor will remain in a relationship and detente despite their shared enmity and passion of Metropolis. Given how severe xenophobia and hatred Hoult’s Luthor expressed toward refugee Superman in this earlier summer’s movie, it is humorous. At the conclusion of Superman, one might believe that the Man of Tomorrow’s large conversation about being a good person addressed the selfish billionaire.

… More good, though, is that Clark don’t underestimate his, um, old companion like Charles Xavier in a 20th Century Fox X-Men film.

What danger may get bad enough to cause them to subscribe troops, according to the statement? Perhaps even more useless and arrogant than the CEO of LuthorCorp?

Ideas for Gunn’s DCU are changing quickly after the relatively warm reception Superman received, especially with the information that Man of Monday is being fast tracked only two decades after Superman and one year after Milly Alcock’s expected summer film Milly Alcock. The DC Universe’s visual debut did certainly surpass$ 600 million globe, which is a second for a DC film in a while. That’s a far cry from some of DC’s movies from the decade, but the negative impression those movies left on viewers appeared to indicate significant declines in the success of their sequels and follow-ups.

In two decades, therefore, we might be able to determine whether Superman and the greater DC Universe are on a different direction, as Batman Begins to The Dark Knight. If you’ll pardon us, it’s time to fire some Magnificent Crabjoys right away.

The second postSuperman 2: James Gunn hinted at Lex Luthor Rematch and Retitled Sequel release meeting first appeared on Den of Geek.

Superman has a very strong bandit’s exhibition under his belt. You might just know this from comic book shows, where the Man of Steel alternates between Lex Luthor and General Zod, but aside from Batman, Spider-Man, and perhaps the X-Men, Kal-El has one of the top criminal schedules in comic book history. So]… ]

The second postSuperman 2: James Gunn hinted at Lex Luthor’s Rematch and launch date in Retitled Sequel was published on Den of Geek.

Superman has a capable bandit’s exhibition to his credit. You might just know this from comic book shows, where the Man of Steel alternates between Lex Luthor and General Zod, but aside from Batman, Spider-Man, and perhaps the X-Men, Kal-El has one of the top criminal schedules in comic book history.

So it’s interesting that writer-director James Gunn revealed in his wonder Wednesday statement about Superman 2 that the film is then entitled Man of Tomorrow and is on the verge of a July 9, 2027 release date, as well as that it looks like it might feature Nicholas Hoult‘s Lex Luthor and David Corenswet’s Clark Kent, although not as you might have expected to see the shaven evil genius.

A Jim Lee penciled drawing of Superman and Lex, the terrible LuthorCorp CEO in a mecha super-suit, and Superman leaning on his rival ‘ back in the following social article with the name and time. If the implications are understood effectively, it appears that they are teaming up. !

For the record, the picture is from 2025 and appears to be one Lee created specifically for Gunn’s statement. If so, it heavily influenced by the suit Luthor wore in the 2019 DC Comics event, DCeased, where an alternate reality DC Universe is infected by a zombie-like virus created by the inhabitants of Apokolips ( remember them, Snyder fans? ). Luthor and Superman team up as a result of Metropolis being completely destroyed by the disease, which saddens him so much that it makes him work with him to preserve what is left of the world.

For the record, we do not believe James Gunn will end up destroying Metropolis and instead embark on some ominous doom and gloom plot in his next Superman film. Ah, I guess the Adherence is no longer there, right?

However, it seems as though he is transferring that scene and other stories where Superman and Luthor will remain in a relationship and detente despite their shared anger and love of Metropolis. Given how severe xenophobia and hatred Hoult’s Luthor expressed toward refugee Superman in this earlier summer’s movie, it is humorous. At the conclusion of Superman, one might assume that the Man of Tomorrow’s large conversation about being a good person addressed the selfish billionaire.

However, it’s more likely that Clark don’t trust his, um, ancient friend too much like Charles Xavier in a 20th Century Fox X-Men film.

What danger may get bad enough to cause them to subscribe forces, according to the statement? Perhaps even more arrogant and vain than the CEO of LuthorCorp?

Programs for Gunn’s DCU are changing quickly after Superman‘s relatively warm welcome, as evidenced by the news that Guy of Tomorrow is being fast tracked only two years after Superman and one month after Milly Alcock’s expected summer film Milly Alcock. The film’s visual debut for DC Universe exceeded$ 600 million worldwide, marking a second for a DC film in a while. That’s a far cry from some of DC’s pictures from the decade, but the negative impression those movies left in viewers appeared to indicate significant declines in the success of their sequels and follow-ups.

In two decades, we might be able to determine whether Superman and the greater DC Universe are heading in a different direction, as Batman Begins to The Dark Knight. If you’ll pardon us, it’s time to unleash some Magnificent Crabjoys.

The second postSuperman 2: James Gunn hinted at Lex Luthor’s Rematch and launch date in Retitled Sequel was published on Den of Geek.

One of the most successful soft knowledge we have at our disposal is the ability to work together to improve our patterns while developing our own abilities and opinions, in whatever form it takes, and whatever it may be called.

Feedback is also one of the most underestimated equipment, and generally by assuming that we’re now great at it, we settle, forgetting that it’s a skill that can be trained, grown, and improved. Bad feedback can cause conflict in jobs, lower motivation, and negatively impact faith and teamwork over the long term. 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 isolated and distributed job settings?

We can find a long history of sequential comments on the web: 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. So it generally adheres to many of the principles with comments, but it also has some differences.

The information

The content of the feedback is the bedrock of every effective analysis, so where do we need to begin? There are many versions that you can use to design your information. 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 movement blueprint, and an outline of the decisions made. You notice a flaw in the situation. If you keep the three elements of the equation in mind, you’ll have a mental model that can help you be more precise and effective.

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

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

Observation for design feedback doesn’t just mean pointing out which part of the interface your feedback refers to, but it also refers to offering a perspective that’s as specific as possible. 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 one to go forward and the other to go back when I see these two buttons.

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

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

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

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

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

Or, for the request approach:

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

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

Choosing 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 a member of this other team who 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 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”. Since the designer receiving this feedback wouldn’t have much to go by, they might just make 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 equation above is intended to serve as a mnemonic to reflect and enhance the practice rather than a strict template for feedback. Even after years of active work on my critiques, I still from time to time go back to this formula and reflect on whether what I just wrote is effective.

The atmosphere

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 lasting 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. Over the years, I’ve tried to summarize the necessary soft skills in a formula that resembles the one for content: the receptivity equation.

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

The 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 live, it might still be relevant if the questioning raises a significant blocker that no one saw, but those concerns are much more likely to have to wait for a later revision. So in general, attune your feedback to the stage of the project. Early iteration? Iteration later? Polishing work in progress? Each of these needs varies. The right timing will make it more likely that your feedback will be well received.

Attitude is the equivalent of intent, and in the context of person-to-person feedback, it can be referred to as radical candor. 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. Although it’s possible, and that’s okay, it’s hoped not to be the case. Acknowledging and owning that can help you make up for that: how would I write if I really cared about them? How can I avoid being passive aggressive? What can I do to encourage constructive behavior?

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

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 situation by adding “oh” to my list of replaced words (your choice between aText, TextExpander, or others ) so that when I typed “oh,” it was immediately deleted.

Something to highlight because it’s quite frequent—especially in teams that have a strong group spirit—is that people tend to beat around the bush. It’s important to keep in mind that having a positive attitude doesn’t necessarily mean passing judgment on the feedback; rather, it simply means that 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. When I shared a comment with someone I knew,” How does this sound,”” How can I do it better,” or even” How would you have written it,” I discovered that the two versions had different meanings.

The format

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

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

In terms of clarity, start by grounding the critique that you’re about to give by providing context. This includes specifically describing where you’re coming from: do you 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 your feedback? Is the design iteration at a point where it would be okay to ship this, or are there major things that need to be addressed first?

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 consider 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 one to go forward and the other to go back when I see these two buttons. But this is the only screen where this happens, as before we just used a single button and an “×” to close. This seems to be breaking the consistency in the flow. Let’s make sure that all screens have the same two forward and back buttons so that users don’t get confused.
• � � Overall— I 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?
• Considering the number of items on the page and the overall page hierarchy, it seems to me that the tiles should use Subtitle 2 instead of Subtitle 1. This will keep the visual hierarchy more consistent.
• � � Background—Using a light texture works well, but I wonder whether it adds too much noise in this kind of page. What is the purpose of using that?

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

One final note: say the obvious. We don’t say something because we sometimes think it’s obvious that something is either good or wrong. 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, improving eight of the subjects ‘ observation, impact, question, timing, attitude, form, clarity, and actionability is a lot of work to put in all at once. One effective approach is to take them one by one: first identify the area that you lack the most (either from your perspective or from feedback from others ) and start there. Then the second, 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.