Building Trust with Engineering Teams

Why Trust Is Hard to Build

Engineers have often experienced managers who:

• Add meetings and process without understanding the cost
• Report metrics that misrepresent the team's work
• Make commitments to stakeholders without consulting the team
• Prioritise optics over substance
• Don't understand (or respect) technical complexity

This history means you start with a trust deficit. Trust is earned through consistent behaviour over time — not through a single conversation or a well-crafted slide deck.

The Trust Equation

Trust = (Credibility + Reliability + Intimacy) ÷ Self-Orientation

• Credibility: Do you understand the work well enough to have informed conversations?
• Reliability: Do you follow through on commitments consistently?
• Intimacy: Do team members feel safe being honest with you?
• Self-Orientation: Are you serving the team's interests or your own career?

High self-orientation (using the team's work to look good, taking credit, optimising for your metrics) destroys trust faster than anything else.

Earning Credibility

You don't need to write code. But you need to understand enough to:

• Ask intelligent questions about technical decisions
• Recognise when estimates are reasonable vs when they're sandbagged or over-optimistic
• Understand why technical debt matters and advocate for its repayment
• Speak about the team's work accurately to stakeholders
• Know the difference between a deployment and a release, a bug and a feature request, a refactor and a rewrite

How to build technical credibility:

• Attend architecture discussions (listen, ask questions, don't prescribe)
• Read post-mortems and understand the technical root causes
• Ask engineers to explain their work — genuine curiosity builds rapport
• Learn the team's tech stack at a conceptual level (not implementation detail)
• Never pretend to understand something you don't — engineers detect this instantly

Demonstrating Reliability

Reliability is the simplest trust-builder: do what you say you'll do, every time.

• If you say you'll escalate a blocker, escalate it today — not next week
• If you commit to protecting sprint scope, actually protect it when stakeholders push
• If you promise to get a decision by Friday, get it by Friday (or communicate why you can't)
• If you say "I'll look into that," follow up within 24 hours — even if the answer is "still working on it"

Small, consistent follow-through builds trust faster than grand gestures. One broken promise undoes ten kept ones.

Building Intimacy (Psychological Safety)

Engineers need to feel safe telling you the truth — especially bad news:

• "This estimate is wrong — it's going to take twice as long"
• "I'm stuck and don't know how to solve this"
• "The architecture decision we made 6 months ago was a mistake"
• "I'm burning out and need help"

Create safety by:

• Never punishing honesty (even when the news is bad)
• Sharing your own uncertainties and mistakes
• Keeping confidential conversations confidential
• Defending the team publicly when they're criticised unfairly
• Giving credit to the team, taking blame yourself

Reducing Self-Orientation

The fastest way to lose engineering trust is to be perceived as self-serving:

Trust-destroying behaviours:

• Taking credit for the team's work in leadership meetings
• Reporting metrics that make you look good but misrepresent reality
• Adding process that serves your reporting needs but slows the team
• Making commitments to stakeholders without consulting the team first
• Prioritising your career progression over the team's wellbeing

Trust-building behaviours:

• Publicly attributing success to the team by name
• Removing process that doesn't serve the team (even if it serves you)
• Asking "what do you need from me?" more than "what's the status?"
• Shielding the team from organisational noise and politics
• Advocating for the team's needs (tooling, hiring, training) even when it's politically difficult

Practical Trust-Building Actions

Week 1-4: Listen and Learn

• Have 1:1 conversations with every team member (not about status — about them)
• Ask: "What's the biggest impediment to your work that nobody's fixing?"
• Ask: "What did previous managers do that frustrated you?"
• Ask: "What would make your daily work better?"
• Don't promise to fix everything — just listen and take notes

Month 2-3: Deliver Quick Wins

• Pick the 2-3 most commonly mentioned impediments and fix them
• Communicate what you did and why: "You told me X was a problem. Here's what I did about it."
• These don't need to be big — removing one unnecessary meeting, getting one tool approved, or resolving one long-standing blocker demonstrates that you listen and act

Month 3+: Sustain and Deepen

• Maintain consistent behaviour (reliability compounds)
• Gradually increase the team's autonomy as trust grows
• Share more context about organisational decisions (transparency builds trust)
• Involve the team in decisions that affect them (not just inform them after)
• Celebrate their wins publicly and consistently

Measuring Trust (Indirectly)

Trust is hard to measure directly, but you can observe its presence or absence:

High trust indicators:

• Team raises problems early (before they're crises)
• Engineers push back on unrealistic commitments (they feel safe saying no)
• Team shares honest estimates (not sandbagged or over-optimistic)
• People volunteer for difficult work (they trust the environment is fair)
• Feedback flows in both directions (team gives you feedback too)

Low trust indicators:

• Problems are hidden until they're unavoidable
• The team agrees to everything in meetings but doesn't deliver
• Estimates are consistently padded with large buffers
• Information flows through formal channels only (never informal)
• Team members leave without warning (they didn't feel safe raising concerns)

Trust takes months to build and moments to destroy. Invest in it daily through small, consistent actions. It's the foundation everything else depends on.

---

Download the [Sprint Health Check template](/templates) to track team health indicators that reflect trust levels.