12 Competencies of UX Design No. 11: Collaborating and Critiquing for Growth

Effective UX design teams succeed not just because they work together, but because of how they work together. Collaboration built on psychological safety, shared language, and a genuine critique culture is what separates good UX teams from great ones. This is the eleventh installment in our series on the 12 Competencies of UX Design.

What Does Collaboration in UX Design Actually Look Like?

Think about how Amish and Mennonite communities in the U.S. and Canada have been raising barns since the 18th century. No machinery, no vehicles, no electricity. Just ropes, small tools, and their own two hands. And yet, an entire barn can go up in as little as 10 hours.

They pull it off through a combination of engineering and teamwork that most modern organizations would envy. In the weeks before a barn raising, community members gather supplies, assign duties, and establish a clear plan so that the day of construction goes off without a hitch. Every person knows their role. Every role serves the shared goal.

The most effective UX teams work exactly the same way.

Mere teamwork isn't enough. What really matters is how a team works together, and how collaborating and critiquing for growth plays a crucial role in user experience success.

What Is the "Collaboration Sweet Spot" for UX Teams?

The collaboration sweet spot is the intersection of three qualities: patience, pragmatism, and flexibility. Teams that operate here communicate closely, discuss solutions together, and work incrementally rather than in isolation.

Before getting there, it helps to ask:

• Why work together instead of independently?
• How do you collaborate throughout the design process?
• How often do you give and receive feedback on work?
• How can you make the solution even better?
• What can you learn from this and apply to future designs?

Why Does Patience Matter in UX Collaboration?

UX design, especially at the enterprise level, is complex and iterative. It requires many small but meaningful improvements over a long period of time rather than trying to make something "perfect" on the first pass.

Even in the best circumstances, it's easy for individuals to get impatient and want sweeping changes, or to accept the first best guess just to get to the finish line faster. Experienced UX professionals know that the only constant in user experience is change, and that "success" today may look nothing like it will in just a few months' time. Testing and iteration with users turns your hypothesis into a solution. Patience with a project, with coworkers, and with the design process is crucial for any UX team.

Why Does Pragmatism Matter in UX Collaboration?

Most professionals have heard the term "minimum viable product." At Drawbackwards, we say Minimum Valuable Product, where the fewest features necessary, paired with a high degree of quality and value, solve the primary problem for your primary market.

Creating a minimum valuable product requires everyone on a UX team to share an understanding of what makes an experience valuable in the first place. Developers need to understand what matters to designers and users. Designers need to know which technical trade-offs developers consider crucial. This kind of deep empathy is what pragmatism looks like in practice.

UX teams that get this right align behind what "valuable" looks like for a user, and then they're willing to kill their darlings, their personal ideas and favorite patterns, and find a new path to achieve that goal.

Why Does Flexibility Matter in UX Collaboration?

Many designers who have been in the field for a decade or more came from a traditional fine arts or graphic design background. That background sometimes shows up in solutions based on aesthetics, layout, and print typography traditions rather than the fluid nature of the screens, devices, interaction points, and channels that serve as today's canvas.

Traditional graphic designers are often trained to deliver solutions that demonstrate personal artistic execution versus serving the needs of users first. The result? Hidden navigation, decorative labels, or clever visual devices arranged more for layout purity than user success. Developers face similar pulls, whether toward ultra-clean code or toward overweight frameworks that reduce short-term risk and production time.

Collaborative teams have to be willing and able to adapt their approach to the needs of the user, and to invite other team members to identify how to do things better. That kind of consensus-building requires both open-mindedness and flexibility from every individual on the team.

How Do You Improve Design Collaboration on a UX Team?

Since collaboration is at the core of user experience success, here are a few ways to help it flourish.

Create a Sense of Psychological Safety

Over two years, Google studied some of their most effective teams to understand what made them so successful. Among more obvious factors like dependability and structure, one important factor stood out: psychological safety.

"It's unnerving to feel like you're in an environment where everything you do or say is under a microscope," one article about the study reads. "But imagine a situation in which everyone is safe to take risks, voice their opinions, and ask judgment-free questions. A culture where managers provide air cover and create safe zones so employees can let down their guard."

That's psychological safety, and it is the bedrock of collaboration. Without it, team members are unlikely to voice their concerns, thoughts, and opinions in a way that will benefit the team and the final product.

Establish a Shared Language

UX teams are usually diverse. Designers, developers, researchers, and strategists all come from different disciplines, and they may also span a wide range of experience levels. Sometimes the only way to empower teams to communicate more effectively is to establish a shared language that everyone, regardless of their background and experience, can understand.

Exercises like card sorting and mind-mapping can be a great tool to build a shared lexicon, as can simply asking team members to shadow one another. Fostering empathy between distinct teams is the key to better communication.

Embrace Brainstorming (or Design Thinking Exercises)

Brainstorming, though we may want to consider calling these exercises closer to design thinking, can be a powerful way to collect and compare many different solutions, and identify which ideas have the most potential. Psychological safety plays a big part here, since brainstorming requires everyone in a room to feel comfortable both offering their ideas and having those ideas discussed in an open setting.

There are plenty of creative brainstorming techniques that promote both open communication and psychological safety:

Start With the Worst First. A counterintuitive but surprisingly effective approach is to start by coming up with bad ideas rather than good ones. This tactic sets the bar low enough to invite ideas, and also helps team members get aligned behind what constitutes a "bad" solution. For example: "Where do you want to go for lunch?" How about McDonald's! "OK, now where do we want to go for lunch?"

Ask "Why?" Five Times. Sometimes referred to simply as the "toddler approach," asking why is a helpful way to get to the root of how a solution solves a problem. Doing it five times ensures that you can clearly see if and how a particular idea supports a shared vision of success. And it can uncover the deeper reason why or why not to do something.

Bubbles Over Balloons. This idea was first shared in a talk about backward thinking for Creative Mornings. Balloons pop on accident, balloons are held tightly and are considered precious. Bubbles pop all the time, freely, by design. By thinking of new ideas as bubbles rather than balloons, team members can better build upon great ideas without holding onto solutions that may not serve a particular user's needs. Tee up an exercise to "blow as many bubbles as you can" and see what happens with that freedom to create, knowing most will fail.

Make Feedback and Critique Exciting

Feedback and critique is a crucial element of the design thinking process, but that doesn't mean it's done well all or even most of the time. For many creatives, the prospect of having their work "critiqued" is enough to send a cold shiver down their spine. That's because in many working environments, critiques are still seen as inherently negative.

The key to unlocking your team's creative potential is to make critiques an exciting opportunity for learning and growth. Just ask Jared Spool, who writes: "A well-done critique is a way to step away from the specifics of the design process and better understand how to create great designs. We do this by starting with the current design and asking 'What is it we're really trying to do here?' and 'How close are we to doing it?'"

To make critique exciting rather than scary, shift your approach from "What feedback can we give or receive about this work?" to "What can each of us learn from the work this designer has done?" This way, even the most profound UX disagreements can be solved without losing sight of the end goal.

Creating Design Success Through Teamwork

Collaboration can be scary. Many people hesitate to do it for fear of wasting time, going over budget, or getting pushback on their ideas. These are completely normal concerns, but the pros of collaboration usually far outweigh the cons. Though collaboration may take more time at the beginning, it saves time and budget in rework later on.

This is why collaboration, teamwork, and an ability to "play nice with others" is so crucial to UX design success. Without it, valuable ideas and perspectives get lost in the shuffle of office politics, big egos, and the underserved needs of a user. Collaboration takes patience, pragmatism, and flexibility on the part of every team member, but the hard work that goes into it always pays off.

Frequently Asked Questions

What does collaboration mean in UX design? In UX design, collaboration means different team members, designers, developers, researchers, and strategists, each contributing their unique expertise toward a shared vision of user success. It's not just working in the same room. It's how responsibilities are divided, how feedback flows, and how decisions get made together.

What is a Minimum Valuable Product and how is it different from a Minimum Viable Product? A Minimum Valuable Product delivers the fewest features necessary alongside a high degree of quality and value to solve the primary problem for your primary market. Where a Minimum Viable Product focuses on viability, a Minimum Valuable Product asks: does this actually deliver value to the user?

How do you give feedback on UX design work without it feeling negative? Reframe the critique from "what's wrong with this?" to "what can we learn from this?" That shift in framing, paired with a psychologically safe environment, turns critique into a growth opportunity rather than a judgment call.

Why is psychological safety important for design teams? Without psychological safety, team members won't voice concerns, challenge bad ideas, or share half-formed thoughts that could become great ones. Google's research identified it as one of the most important factors in team effectiveness. It's the foundation everything else is built on.

What brainstorming techniques work best for UX teams? Three that work particularly well are: starting with the worst idea first to lower the stakes and invite participation; asking "why?" five times to get to the real root of a problem; and treating new ideas as bubbles rather than balloons, something to generate freely and let go of easily, rather than something precious to protect.