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.
Related Insights
When leading a function outside your expertise (e.g., a comms leader managing BDRs), success depends on hiring a great functional leader. Your role becomes asking them to explain concepts simply until you understand, trusting their expertise, and advocating for their needs, rather than trying to become the expert yourself.
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.
A leader's value isn't being the expert in every marketing function. It's identifying a critical problem, even one they don't fully understand, and taking ownership to push it forward. This often means acting as a project manager: booking the meeting, getting the right people in the room, and driving action items.
Superhuman's CTO credits a non-tech role managing submarine maintenance with teaching him to lead without technical legitimacy. By being forced to put his ego aside and drive change by asking fundamental questions, he learned to influence people far smarter in their domain.
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.
Technical audiences are "human lie detectors." To build trust, don't lead with a sales pitch. Instead, ask insightful questions about their stack and pain points to prove you understand their world. This curiosity earns you the credibility needed to offer solutions and advice.
A common leadership trap is feeling the need to be the smartest person with all the answers. The more leveraged skill is ensuring the organization focuses on solving the right problem. As Einstein noted, defining the question correctly is the majority of the work toward the solution.
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.
To create a future-ready organization, leaders must start with humility and publicly state, "I don't know." This dismantles the "Hippo" (Highest Paid Person's Opinion) culture, where everyone waits for the boss's judgment. It empowers everyone to contribute ideas by signaling that past success doesn't guarantee future survival.
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.
