Joining as a new tech lead for an existing team, the speaker built trust by forbidding himself from giving direct orders or rejecting designs. He instead embedded with teams and used strategic questioning to guide them, helping them arrive at the right conclusions while respecting their expertise.
Related Insights
When entering a new domain, don't feign expertise. Build trust faster by openly admitting "I don't know" and explicitly leaning on stakeholders for their subject matter knowledge. This positions you as a partner who values their expertise, rather than an outsider imposing solutions.
Individual contributors are rewarded for having answers and sharing their expertise. To succeed as a leader, one must fundamentally change their approach. The job becomes about empowering others by asking insightful questions and actively listening, a diametrically opposed skillset that is difficult to adopt.
Instead of solving problems brought by their team, effective leaders empower them by shifting ownership. After listening to an issue, the immediate next step is to ask the team to propose a viable solution. This builds their problem-solving and decision-making capabilities.
In your first 90 days, resist the urge to be the expert. Instead, conduct a "listening tour" by treating the organization as a product you're researching. Ask questions to understand how work gets done, what success looks like, and what challenges exist at a systemic level.
A great tech lead provides a safety net without micromanaging. The analogy is a driving instructor who starts with their hands near a second steering wheel, ready to intervene, but gradually backs off as trust builds with the student. This approach gives engineers freedom to grow while ensuring the project stays on track.
When managing former peers, expect to be tested. A direct report challenged the speaker with a hypothetical scenario to see if he would jump to conclusions or seek to understand the full context first. Passing this test built immediate trust by showing he wouldn't abuse his new authority.
New leaders must transition from being the expert to being a coach. This involves letting your team struggle and even fail. Ask open-ended questions like, "When have you faced something similar before?" to build their problem-solving skills instead of simply giving them the solution.
When leading functions outside your core expertise (e.g., product leading tech and data), credibility cannot come from having answers. Instead, it's built by consistently asking open-ended questions to deeply understand the team's challenges. This approach prevents solutionizing and fosters trust.
Many leaders, particularly in technical fields, mistakenly believe their role is to provide all the answers. This approach disempowers teams and creates a bottleneck. Shifting from advising to coaching unlocks a team's problem-solving potential and allows leaders to scale their impact.
Instead of faking expertise, openly admitting ignorance about technical details builds trust and empowers specialists. This allows you to focus on the 'what' and 'why' of the user experience, giving engineers and designers the autonomy to own the 'how', which fosters a more collaborative and effective environment.
