When you step into engineering management for the first time, the trust you have with your team does not follow automatically from your title. It has to be built, and it can break faster than you expect. The trust equation, developed by David Maister and his colleagues, provides a clear framework to understand what drives trust and where you might be losing it. The equation is simple: Trust = (Credibility + Reliability + Intimacy) / Self-Orientation. Each of these four components matters, and when one of them is low, trust suffers. As a new engineering manager, focusing on all four gives you a structured way to earn trust deliberately.

Understanding the Four Components

Before you can apply the equation, you need to know what each term means in the context of engineering management. Credibility is about what you say. It includes your technical knowledge, your ability to speak accurately about the work, and your honesty when you do not know something. Reliability is about what you do. It means keeping promises, following through on commitments, and being consistent in your actions. Intimacy is about how safe people feel with you. It refers to the emotional closeness and psychological safety that allows team members to share concerns without fear. Self-Orientation is the denominator. It measures how much you focus on your own interests rather than the team’s. A high self-orientation reduces trust even if the numerator is strong.

Building Credibility as a New Manager

Credibility does not require you to be the smartest engineer in the room. It does require you to be truthful about your knowledge. When you do not know something, say so plainly and commit to finding out. Your team will trust you more for admitting gaps than for pretending to have answers. Another key move is to demonstrate that you understand the context of the work. Ask thoughtful questions about the codebase, the system architecture, and the tradeoffs the team faces. This shows that you care enough to learn. Avoid overstating your experience or making promises about technical solutions you cannot deliver. Credibility erodes quickly when your words do not match reality.

One practical habit is to prepare for one-on-ones by reviewing recent commits, ticket updates, or incidents. When you show up informed, you signal that you value the conversation. If you are new to the domain, invest time in reading documentation, attending technical meetings, and asking senior engineers to walk you through the system. Credibility also grows when you give credit to others. A manager who consistently highlights the team’s achievements rather than their own earns more trust in the long run.

Demonstrating Reliability Through Consistency

Reliability is built one small commitment at a time. In your first weeks, make only promises you are certain you can keep. When you say you will review a pull request by end of day, do it. When you agree to follow up on a question, do not let it slip. For a new manager, even missed tiny promises signal that you are not dependable. Over time, these micro-actions create a pattern that the team can count on.

Set up a system to track your commitments. Use a simple to-do list, a note in your calendar, or a lightweight project management tool. The goal is to never let a follow-up fall through the cracks. Also, be reliable in your availability. Hold your office hours or one-on-ones at the same time each week. Cancel only when absolutely necessary. Predictability in your schedule builds confidence that you are there for the team. If something goes wrong and you cannot deliver on a promise, communicate early. Apologize, explain briefly, and reset expectations. This preserves reliability because you are still acting responsibly.

Increasing Intimacy to Create Psychological Safety

Intimacy in the trust equation does not mean becoming best friends with everyone. It means creating a climate where team members feel safe to be vulnerable. They should be able to tell you about a mistake, a disagreement, or a personal challenge without worrying about consequences. This is especially hard for new managers because the power dynamic can stifle openness. You must intentionally lower the barrier.

Start by modeling vulnerability yourself. Share something you are learning or struggling with. Admit when you made a call that did not work out. When the team sees you acting human, they are more likely to reciprocate. In one-on-ones, ask open-ended questions about how they are feeling about the work, not just what they are working on. Listen without jumping to solutions. Sometimes the most intimate thing you can do is simply hold space for someone to speak.

Another effective practice is to establish a no-blame culture around incidents. When something goes wrong, focus on the system and the process, not the individual. Ask “what can we learn?” instead of “whose fault was it?” This directly increases intimacy because team members learn that they can surface problems without being punished. Be careful not to violate confidentiality. If someone shares a personal concern, do not discuss it with others without permission. Protecting their privacy builds deep trust.

Reducing Self-Orientation: Putting the Team First

The denominator of the trust equation often derails new managers. Self-Orientation is the perception that you are acting in your own interest rather than the team’s. Common signs include interrupting team members, making decisions without consultation, taking credit for the team’s work, or pushing your own agenda during sprint planning. Even well-intentioned actions can appear self-oriented if you do not communicate your reasoning.

To lower self-orientation, make your decision-making process transparent. When you have to choose between two options, explain the tradeoffs and state explicitly that you are considering the team’s needs. Ask for input before finalizing. If you cannot incorporate feedback, explain why. A simple phrase like “I am making this call because I believe it helps us ship faster, but I want to hear if I am missing something” shows that you are not acting from ego. Another habit is to celebrate the team’s successes publicly and take responsibility for failures privately. When a project goes well, point to the engineers who made it happen. When something goes wrong, say “I should have caught that” or “we need to improve our process” rather than deflecting.

Watch out for subtle self-oriented behaviors like checking your phone during a team member’s presentation, finishing their sentences, or jumping in with your own story. These small actions signal that you are more interested in yourself than in them. Practice active listening and let others speak fully before responding. Over time, your team will notice that you put their concerns ahead of your own agenda.

Common Trust Traps for New Managers

Even when you know the equation, certain situations can trip you up. One trap is trying to prove your technical worth too aggressively. You might be tempted to rewrite code or override design decisions to show you still have hands-on skills. This can backfire because it signals that you do not trust the team’s expertise. Instead, use your technical knowledge to ask good questions and support their decisions, not to override them.

Another trap is overcorrecting from a former manager’s style. If your predecessor was too hands-off, you might become overly controlling. If they were too micromanaging, you might swing too far to laissez-faire. The team needs consistency, not a reaction. Take time to observe what is working before making changes. Trust is built on steady, predictable behavior, not on dramatic shifts.

A third trap is neglecting to build trust with stakeholders outside your team. Product managers, peer managers, and your own manager need to trust you as well. Apply the same equation. Demonstrate credibility by understanding the product roadmap. Show reliability by responding to their requests on time. Build intimacy by having informal chats. And keep your self-orientation low by aligning with the broader organization’s goals, not just your team’s.

Recovering Trust When You Make a Mistake

No manager is perfect. You will inevitably break a promise, say something careless, or make a decision that erodes trust. The recovery process follows the same equation. First, acknowledge the mistake openly (credibility). Describe what you will do to fix it and follow through (reliability). Listen to how the team was affected without getting defensive (intimacy). And explain that your failure was not because you prioritized yourself, but because you missed something (low self-orientation). A sincere apology that addresses all four components rebuilds trust faster than pretending nothing happened.

For example, if you missed a deadline you promised to hit, say: “I said I would have the budget plan ready by Friday and I did not. That is on me. I understimated how long the data would take to collect. Here is what I am doing to get it done by Monday, and I will keep you updated. I am sorry for the delay and for the stress it caused.” Then actually deliver on Monday. This recovery strengthens trust because it shows you are accountable.

Finally, remember that trust is built over time through repeated interactions. The trust equation gives you a systematic way to check where you stand. If you sense that trust is low, examine each component. Is your credibility intact? Are you following through? Do people feel safe around you? Are you coming across as self-centered? Adjust accordingly. As a new engineering manager, your first few months set the foundation for your entire tenure. Use this framework to build that foundation deliberately and watch your influence grow.