3.1 - Earning respect without administrative power

When you transition from an Architect or Senior Engineer to an Engineering Manager, you might expect your team to automatically follow your lead because of your new title. However, engineers are inherently skeptical of authority. They do not respect titles; they respect competence, empathy, and logic.

As a Tech-Led Coach, your goal is to build natural authority. You want your team to follow your direction not because you are their "boss", but because they trust your technical judgment and know you have their best interests in mind.

---

The myth of administrative power

Administrative power is the ability to fire, hire, promote, or assign tasks. Relying on this power is the fastest way to destroy psychological safety. If you have to say, "Because I am the manager, and I said so," you have already lost the team.

Instead, you must lead through influence. Influence is earned by demonstrating that you deeply understand the system, the code, and the daily struggles of the engineers writing it.

Step 1: Technical empathy over technical dictatorship

Many new EMs make the mistake of using their technical background to micromanage. They review every line of code, dictate exact architectural choices, and crush the autonomy of their developers.

To build trust, you must shift from a "dictator" to an "enabler":

• Ask, Don't Tell: Instead of saying, "Use a Redis cache here," ask, "What happens to the database load if traffic spikes 10x? How should we protect it?"
• Get Your Hands Dirty (Occasionally): Do not take the critical path features, but take on the painful tasks. Fix annoying bugs, update CI/CD pipelines, or refactor legacy code that everyone hates. This shows you are still in the trenches with them.
• Protect Their Time: Use your authority to shield the team from unnecessary meetings and vague product requirements. When engineers see you fighting for their focus, their respect for you multiplies.

Step 2: The art of active technical listening

Engineers respect leaders who listen. When an engineer complains about a slow deployment pipeline or a messy codebase, they are giving you a roadmap to earn their trust.

flowchart LR
    A[Listen to Frustration] --> B[Understand the Technical Root Cause]
    B --> C[Remove the Blocker]
    C --> D[Earn Trust]
    D -->|Strengthens| A

When someone brings a problem:

1. Do not dismiss it as "just tech debt". Validate their frustration.
2. Translate the technical pain into business risk so you can secure the time needed to fix it.
3. Follow through. Trust is built on delivered promises, no matter how small.

---

🎯 Self-Reflection for You

1. When was the last time you asked your team for their opinion on an architectural decision, rather than just giving them the answer?
2. Are you using your technical background to control how the code is written, or to remove the roadblocks stopping your team from writing it well?

If you are struggling to balance your technical authority with your new management responsibilities, let's explore practical strategies to build natural leadership in a virtual coffee chat.