Building Trust With a New Team as a Designer

Starting somewhere new is a strange position for a designer. You probably have more experience and better instincts than you're able to show in the first few weeks. The context you're missing makes you slower. The relationships you haven't built yet make it harder to get things done.

Trust isn't built by demonstrating capability in isolation. It's built through a series of smaller interactions that accumulate over time into a shared understanding of who you are and how you work.

Here's how to build it faster without forcing it.

Listen more than you talk in the first few weeks

New designers often feel pressure to demonstrate value immediately. They show up with ideas, challenge existing decisions, and propose changes before they fully understand the context.

This usually backfires. Not because the ideas are bad, but because they signal that the person hasn't taken the time to understand the situation first. To the people who have been there longer, it reads as overconfidence at best and disrespect at worst.

The first few weeks are for listening and asking questions, not for having the right answers. Ask about how decisions get made, what's been tried before, what the biggest pain points are. People almost always trust someone more after they've felt heard by them.

Deliver something small, reliably

One of the fastest ways to build trust is to say you'll do something and then do it. This sounds obvious, but a lot of new joiners are so focused on making a good impression with big work that they underestimate the impact of consistent follow-through on smaller things.

If you say you'll send something by Thursday, send it by Thursday. If you say you'll look into something and come back with a recommendation, come back with a recommendation. Small commitments kept consistently signal reliability more effectively than any impressive piece of work.

Get to know the engineers and PMs as people

Trust in cross-functional teams runs through relationships, not just competence. The PM who trusts your design judgment probably also knows something about how you think, what you care about, and what your working style is like.

In your first few weeks, invest in getting to know the people you'll work most closely with, not as professional contacts but as people. Ask what they're working on that's exciting or frustrating. Pay attention to what they're under pressure about. Bring something useful to them, even if it's outside your immediate brief.

These conversations pay dividends over the full length of your time on the team.

Be transparent about what you don't know

New joiners who pretend to know things they don't create problems later. It's almost always better to say "I don't know, but I'll find out" than to give a confident answer that turns out to be wrong.

In design specifically, saying "I don't have enough context yet to make a call on this, can you walk me through the constraints?" is a mark of good judgment, not weakness. The people who've been there longer know you're new. They're watching to see whether you know what you don't know.

Show your thinking, not just your output

A new designer who shares finished work without explanation leaves the team guessing about how they got there. A new designer who shares their reasoning, "I went this direction because I thought the bigger problem was X, and I wanted to test whether Y would help with that", gives people something to respond to.

This is about trust because it makes your decision-making legible. People can see what you're optimising for. They can give better feedback. And if they disagree with your reasoning, they can address that specifically rather than just criticising the output.

Earn the right to challenge things

At some point you will have ideas about how things could work better. You'll notice decisions that look wrong from the outside, processes that seem inefficient, assumptions that might not hold.

The timing of when you raise these things matters. In the first month, challenges to existing ways of working land poorly, regardless of merit, because you haven't yet shown you understand why things are the way they are.

After you've delivered a few things well and built some relationships, the same observations carry more weight. "Having spent two months on this, I've noticed something about the way we're handling X that I wanted to raise" lands completely differently than raising the same thing on your second week.

The substance of your challenge might be identical. The trust you've built is what determines whether anyone can hear it.