UX design doesn't happen in isolation.

At most organisations, designers sit inside a broader team structure - sometimes a small cross-functional group, sometimes a larger product organisation - and the quality of the work they produce is shaped significantly by how well they understand the roles around them. Knowing what each function does, what they need from design, and where the natural points of friction lie is one of the less-discussed but more practically useful things a designer can develop early in their career.

Development and engineering

Engineers are the people who turn design files into working software.

Understanding this relationship at a technical level - even at a basic level - tends to make designers considerably more effective. Knowing what is trivial to implement and what is expensive, which interactions create technical debt and which are handled by existing components, and how to frame design decisions in terms that translate into implementation decisions: all of this affects how designs fare when they cross into the development phase.

The relationship also runs the other way. Developers are frequently first to spot when a designed interaction is inconsistent with an adjacent screen, or when two separate design decisions will create a conflict that neither designer considered individually.

Treating engineering as a downstream recipient of completed design, rather than as a working partner throughout, tends to produce more rework and less good final product.

Creative design

Creative designers and UX designers often share visual sensibility but work toward different ends.

Where UX design focuses on how users move through and interact with a product, creative design focuses on how a brand presents itself - through advertising, social media, brand guidelines, visual identity, and external communications. The two disciplines overlap most strongly when brand design decisions (colour systems, typography, iconography) need to be translated into the constraints of product design.

The relationship is most productive when there is a shared visual language that both functions have input into - typically through a design system that encodes brand decisions in terms that product designers can directly apply.

Without that shared foundation, the two teams can drift apart in ways that become visible to users as inconsistency between marketing materials and product experience.

Product owner and product manager

The product owner and product manager roles vary in definition across organisations, but both tend to sit at the intersection of user needs, business goals, and delivery constraints.

They translate stakeholder priorities into product requirements, maintain and prioritise the backlog, and hold the question "what are we building and why?" across the entire team.

For a UX designer, this relationship is one of the most consequential. The PM or PO typically controls which problems get prioritised and what constraints apply to the solution space; the designer's job is to bring user insight and design craft to bear within that frame.

When the relationship works well, they are effectively co-owners of the product's direction: the PM brings the business context, the designer brings the user context, and together they make better decisions than either would alone. When it doesn't work well, design becomes a service that executes briefs rather than a partner that shapes them.

Quality assurance

QA's role is to close the gap between the intended experience and the built experience.

They test implemented features against design specifications, identify inconsistencies between what was designed and what was delivered, and catch edge cases that neither design nor development anticipated. This makes them, in a real sense, the last line of defence for the user experience before a feature reaches users.

The relationship between UX and QA is more valuable when designers have invested in clear, detailed design specifications - explicit states for every interactive element, defined edge case behaviour, annotated flows that make the intended experience legible without requiring interpretation.

Ambiguous designs produce ambiguous implementations, and QA catches some but not all of those ambiguities. The tighter the design handoff, the better the QA outcome tends to be.

Scrum master

The scrum master's primary responsibility is the health of the team's process.

They facilitate the ceremonies of agile development - sprint planning, stand-ups, retrospectives, sprint reviews - and work to remove blockers that slow the team down. They are less focused on the substance of what's being built than on the conditions under which the team builds it.

UX designers interact with scrum masters most in the context of planning: how design work gets estimated, how design cycles relate to development sprints, and how research and exploration time gets accounted for in a sprint-based system.

Getting design appropriately represented in the planning process - rather than having it absorbed into sprint work without its own lead time - is often a negotiation that benefits from a scrum master who understands how design fits into the flow.

UX research

UX research is the function closest to UX design in both orientation and method, and in many organisations the two are either combined in a single role or work together on a daily basis.

Where design focuses on creating solutions, research focuses on understanding the problem - through user interviews, usability testing, diary studies, surveys, contextual inquiry, and a range of other methods depending on what needs to be known.

The value of a strong research function is that it gives design decisions an empirical foundation rather than a primarily intuitive one. When a designer is uncertain whether an approach will work, a researcher can design a study to find out. When a feature ships and produces unexpected behaviour, research can determine why.

The disciplines are most effective when they are genuinely integrated - when research questions arise from design uncertainty, and design decisions respond to research findings - rather than when research is treated as a phase that precedes design and then ends.

Other UX designers

Working with other designers on the same product requires something that design school doesn't always teach: the ability to hold your own preferences loosely.

When two experienced designers are working on adjacent parts of the same product, they will sometimes make different decisions for the same problem. Resolving those differences well - through discussion, through testing, through shared principles rather than through seniority or force of personality - is one of the more important collaborative skills in the discipline.

The most productive design collaborations tend to share a clear agreement on the principles that govern product decisions, so that disagreements can be resolved by reference to those principles rather than by personal taste.

They also tend to have established norms for giving and receiving critique: specific, grounded in user needs and design principles, and oriented toward improving the work rather than defending or undermining the designer. That environment, when it exists, is one of the better places to grow as a practitioner.