Creative Comment: Navigating the Crossroads

Meanwhile, every stakeholder arrives armed with their own metrics, priorities, and constraints.

So how do design teams avoid the trap of either solving everyone else’s problems at the expense of the design considerations or being reduced to simply “making things look good”?

The reality is, that is often the role of design: to sit at the cross-functional crossroads and find a solution that works.

.

1. Collaborate not compromise

   Collaboration and compromise are often treated as interchangeable concepts, but they produce very different outcomes.

   Compromise frequently leaves both sides partially dissatisfied, with each giving up something important. Collaboration, on the other hand, combines expertise to create solutions neither side could have reached independently. In simple terms: compromise can feel like 1 + 1 = 0.5, while collaboration creates opportunities for 1 + 1 = 3.

   The key to collaboration is consistently re-centering discussions around a shared objective: the success of the project.

   When design quality is compromised, it is not only the design team that loses. The overall product experience suffers. Likewise, when technical feasibility, legal considerations, marketing objectives, or operational constraints are ignored, the product itself becomes weaker.

   Framing conversations around shared outcomes changes the nature of trade-off discussions. Instead of functions competing to have their priorities win, each discipline contributes its expertise toward a common goal.

   .

2. Seek out the value brought by others

   As a designer, you are not just working for everyone else, they are also working for you. Use their knowledge to your advantage.

   Rather than waiting for technical or legal constraints to surface late in the process, or risk partners sidelining design completely, involve partners intentionally and early. Use their expertise to improve the design itself.

   For example, a design team might establish the overall information architecture and interaction hierarchy while collaborating closely with legal stakeholders to shape how sensitive content is presented within that structure. Design leads the experience vision while incorporating specialized expertise where it matters most.

   Similarly, designers are often presented with rough mockups, slide decks, or “designs” created outside the design team. Instead of dismissing these artifacts, effective designers use them as opportunities to uncover the underlying problem being communicated. The goal is not to defend ownership of design work, but to understand intent and evolve the idea through a stronger design process.

   This approach helps cross-functional partners feel heard while also demonstrating the unique value design contributes: the ability to synthesize problems, identify patterns, and transform fragmented ideas into cohesive experiences.

   .

3. …While being clear about the value of design

   Part of the challenge design teams face is that good design can appear effortless from the outside. The “magic” is visible, but the systems behind it often are not.

   To make the value of design more visible, actively document the principles, processes, and systems that guide the team’s work. Strong outcomes are rarely the result of instinct alone. They come from a combination of research, design expertise, established principles, iteration, and structured decision-making.

   No two design teams will operate in exactly the same way — a flexibility which both helps design flourish and makes it seem “fluffy”. However, a team that has documented processes, shared principles, and established design systems for their unique scenario has at least a baseline for productive conversations.

   This allows teams to evaluate changes constructively rather than debating every decision from scratch. More importantly, they help organizations understand that effective design is not arbitrary — it is intentional, repeatable, and strategically grounded.

   .

4. Translate your language

   Finally, none of these things is possible without effective communication.

   This is not something that can be done independently as a designer or a design team. All cross-functional partners need to be on board.

   That requires translating design language into terms that other disciplines already understand.

   Designers do not need to become experts in every field, but they do need to understand how design decisions connect to broader organizational goals. Visual consistency can be framed in terms of brand recognition and customer trust. Information architecture and navigational clarity can be tied to conversion rates, engagement metrics, or support reduction. Design system decisions can be aligned with engineering efficiency and scalability.

   When teams understand how design contributes to their goals—not just aesthetic outcomes—design becomes easier to advocate for and collaborate around.

   .

None of these approaches guarantees perfect cross-functional relationships or flawless outcomes. However, much like the design process itself, consistently applying them moves teams closer to a stronger and better version of the working model.

You might also find that, at the end of the day, everyone likes feeling valued and own part of a successful outcome, and by reaching out to your partners first and collaborating with them on the idea, you have been establishing rapport and getting buy in along the way to help make the next iteration of your collaboration even better.