Most job descriptions focus on visible work. We talk about research, strategy, prototyping, design systems, and 0 ->1 facilitation because those activities produce artifacts we can point to. But after enough years working on products and teams, I’m convinced that a surprising amount of design happens somewhere else. It happens in difficult conversations, in moments of misunderstanding, and in the small interactions that determine whether people trust one another enough to solve problems together:

• A stakeholder is frustrated but can’t explain why, and only gives empty corporate feedback (more recently, also includes “AI-pilled” feedback)
• A teammate feels unheard during a planning discussion
• A user describes a painful experience that doesn’t fit neatly into a requirements document

Design is often described as problem solving, but less attention is paid to the work required to keep problems solvable. Much of that work is relational rather than technical, and much of it happens in conversations rather than artifacts; we just tend to notice the artifacts because they’re visible, but the relationships underneath the artifacts are what make the work possible in the first place.

For this series, we’ll refer to all of this as invisible relationship work.

The Work Behind the Work

A common misconception about design is that our job is primarily creating things. While that’s certainly part of it, much of the work involves helping people work together well enough to create those things in the first place. Designers often sit between groups that have different goals, incentives, expertise, and vocabulary. We move between customers and businesses, engineers and executives, and what people say they want and what they actually need.

Because of that position, we’re often working through relationships as much as interfaces. When trust is strong, communication is clear, and expectations are aligned, projects tend to move forward with surprisingly little friction. When those conditions break down, even straightforward decisions can become difficult. The challenge is that maintaining those conditions is rarely treated as work, even though many experienced practitioners spend a significant portion of their time doing exactly that.

Over time, I’ve noticed that most invisible relationship work tends to show up in four forms. They overlap frequently, and the same conversation may involve all four at once, but distinguishing them can make it easier to understand what’s actually happening beneath the surface.

Interpretation

People rarely communicate as clearly as we’d like, especially when they’re dealing with uncertainty.

A stakeholder says, “This doesn’t feel right.” A user says, “I hate this feature.” A teammate says, “I’m not sure this is going to work.” On the surface, those statements sound like feedback, but they’re often signals pointing toward something deeper: a concern about risk, a missing piece of context, or a problem the person hasn’t fully articulated yet.

Much of design involves helping people make sense of their own thoughts. Research interviews, stakeholder conversations, usability testing, and workshops all depend on our ability to recognize that the first thing someone says is not always the complete story. The work is not simply collecting opinions. It’s interpreting incomplete information and helping people express what they already know but don’t yet have the words for.

Emotional Regulation

Interpretation becomes much harder when emotions enter the picture, and design work creates plenty of opportunities for that to happen. Projects encounter setbacks. Stakeholders criticize proposals. Teams disagree about priorities. Users react negatively to decisions that seemed reasonable when they were made. None of this is unusual, but it does create moments where our immediate reaction can determine whether a conversation becomes productive or adversarial.

Emotional regulation is often misunderstood as staying calm or suppressing feelings. In practice, it’s closer to creating enough space between a reaction and a response that curiosity remains possible. When someone dismisses months of work in thirty seconds, the challenge is not pretending the frustration doesn’t exist. The challenge is understanding whether responding from that frustration will improve the situation. Sometimes the most valuable thing we can do is remain engaged long enough to understand what is actually driving the disagreement.

Relationship Maintenance

Trust has a tendency to feel permanent right up until the moment it isn’t.

Most working relationships are built through small interactions that seem insignificant at the time: clarifying misunderstandings, following up after tense meetings, sharing context before decisions are made, and occasionally repairing mistakes. Because these activities happen incrementally, it’s easy to underestimate their importance until a relationship starts to deteriorate.

This is one reason healthy teams often appear effortless from the outside. What looks like smooth collaboration is usually supported by a steady stream of maintenance work happening in the background. Someone is resolving confusion before it becomes conflict. Someone is making sure information reaches the people who need it. Someone is helping different perspectives coexist long enough for a solution to emerge. The work becomes visible only when it stops happening.

Power Navigation

Every organization contains differences in authority, influence, incentives, and responsibility, and those differences shape how people behave.

A disagreement with a peer feels different from a disagreement with an executive sponsor. Feedback from a customer carries different implications than feedback from a teammate. Understanding those differences doesn’t require becoming political or manipulative, but it does require acknowledging that power influences conversations whether we talk about it or not.

I’ve found that many workplace conflicts become easier to understand once power and incentives enter the analysis. A director pushing back on a proposal may not be defending a personal preference so much as protecting a commitment they’re accountable for to leadership. What looks like resistance from an engineering lead may be concern about risk, especially when someone will be responsible for the consequences if a decision goes poorly. Even apparent overreactions often make more sense once you understand the pressures surrounding them, like deadlines, budgets, regulatory requirements, team dynamics, customer commitments, or promises made in meetings you weren’t in.

This doesn’t excuse poor behavior, but it often clarifies it. When we focus exclusively on personalities, we tend to miss the systems shaping how those personalities surface, because people generally behave in ways that make sense given their incentives, responsibilities, and constraints, even when those behaviors create friction for others. A stakeholder who seems inflexible may be protecting a quarterly goal. An executive who appears dismissive may be juggling competing priorities across the organization. A product manager who keeps raising objections may be carrying commitments made to customers that the rest of the team can’t see. The more we understand the context surrounding a decision, the easier it becomes to respond thoughtfully, build better relationships, and address the underlying problem rather than arguing about its symptoms.

Why This Work Matters

The interesting thing about invisible relationship work is that people tend to notice it only when it’s absent. We notice when trust breaks down, when communication fails, when teams become dysfunctional, or when stakeholders stop listening to one another. We rarely notice the dozens of small interventions that prevented those outcomes from happening in the first place.

This creates a strange paradox. Some of the most important work in organizations is also the hardest to see. The best facilitators, managers, designers, researchers, and leaders often make difficult interactions feel easy, which can make their contributions appear smaller than they really are. In reality, they’ve usually spent years learning how to interpret signals, regulate reactions, maintain relationships, and navigate power dynamics without drawing attention to themselves.

A Series About Relationships

This series explores three places where designers commonly perform invisible relationship work. In Part 1, we’ll look at stakeholders and power: how designers absorb ambiguity, build trust, and navigate competing priorities. In Part 2, we’ll look at coworkers and reciprocity: the often-unseen work required to keep teams healthy and collaborative. In Part 3, we’ll look at users and responsibility: what empathy is for, where its limits are, and how designers can care deeply without carrying everything.

1. Part 1: Stakeholders and Power
   Question: How do you work productively with people who can change the direction of your work?
   How designers absorb ambiguity, translate concerns, and maintain trust with people who influence priorities, resources, and decisions.
2. Part 2: Coworkers and Reciprocity
   Question: How do teams share the work of keeping collaboration healthy?
   How teams depend on invisible work during onboarding, mediation, coordination, documentation, mentoring, and emotional support.
3. Part 3: Users and Boundaries
   Question: What do we owe the people we design for?
   Responsibility without self-sacrifice.