Earning Trust in the First Two Weeks
A forward-deployed consultant is a stranger given deep access to a team's work. Everything that follows depends on how quickly that stranger becomes someone the team is glad is there. The first two weeks decide it.
When you embed with a new team, you arrive carrying a quiet contradiction. On paper you’re the expert they hired. In the room you’re an outsider who doesn’t yet know their systems, their people, their history, or their unwritten rules. The team is watching — usually politely, sometimes warily — to find out which you’ll turn out to be: a help or a disruption.
The first two weeks are where that gets decided, and I’ve come to treat them as their own distinct phase of the work, with trust as the actual deliverable. The code can wait a little. The standing cannot.
Trust is built by small, visible usefulness
The mistake I see — and made — is trying to earn trust by demonstrating brilliance: the sweeping insight, the impressive architecture sketched on day two. It almost never works, because the team can’t yet evaluate it and it reads as the outsider showing off. Trust is built the opposite way: through small, concrete usefulness delivered early and visibly.
- Ship something tiny but real in the first few days. Not the solution — a genuine small help. Fix the flaky thing everyone’s annoyed by. Answer a question that was stuck. Make one person’s week slightly easier. Competence demonstrated beats competence asserted, every time.
- Learn names and respect the existing work. The team built what exists under constraints you don’t yet understand. Treating their work with curiosity rather than judgment — “why is this done this way?” instead of “this is wrong” — signals that you’re there to help, not to grade.
- Be the person who does what they said they’d do. Reliability in small things is the fastest trust-builder there is. If you said you’d send the summary by Thursday, send it Wednesday. Clients rarely remember your cleverest idea; they always remember whether they could count on you.
Credibility and warmth, together
The teams that came to trust me fastest got two things from me early and at the same time: evidence I was competent, and evidence I was actually on their side. Either alone falls short. Competence without warmth reads as a mercenary who’ll optimize for themselves. Warmth without competence is pleasant and useless. Both together — someone clearly skilled who clearly cares about your outcome — is what makes a team relax and let you in.
The caring part can’t be performed; teams see through it instantly. It comes from genuinely adopting their goal as yours for the duration. Their deadline is your deadline. Their definition of success is the one you’re working toward. When a team senses that your incentives have truly aligned with theirs, the wariness drops and the real collaboration starts.
Navigating the person who didn’t want you there
Not everyone is glad you’ve arrived. Often there’s someone — frequently a strong engineer — who experiences an outside consultant as an implicit judgment on their work, and who has real reason to be skeptical of parachuted-in experts. Winning that person over matters more than almost anyone else’s approval, because their trust is the hardest-won and the most telling.
I try to do it by making them an ally rather than an audience: asking their advice early and genuinely, crediting their existing work, and being transparent that I’m not there to replace them but to help the team get a result they’ll own after I leave. The multiplier mindset matters enormously here — the moment a skeptical engineer realizes you’re trying to make them stronger, not make yourself indispensable, the dynamic usually turns.
Why this phase is worth the patience
It can feel inefficient to spend early days on usefulness and relationship rather than charging at the core problem. It isn’t. Trust is the medium through which all the later work flows. A team that trusts you tells you the truth about the data, lets you make the call on the hard tradeoff, and adopts what you build. A team that doesn’t will quietly route around you, and the best solution in the world dies on contact with that.
Earn the trust first, and everything afterward gets easier. Skip it, and nothing afterward quite works. In the next essay I’ll turn to one of the clearest expressions of trustworthiness there is, and one of the hardest for a consultant to practice: knowing when, and how, to say no.