On Engineering Leadership: Remove Ambiguity
"Engineering leadership is about removing ambiguity and creating clarity—every sprint, every quarter." This advice comes from a discussion with leaders at Slack, LinkedIn, and Salesforce, who noted that high-performing teams maintain velocity through clear documentation and blameless post-mortems.
"You're not steering the team. You're riding a rocket—you just need to point it in the right direction," is a core philosophy of seasoned tech leader Jim Meyer, who has held engineering leadership roles at Slack, Salesforce, and LinkedIn. This approach emphasizes that a leader's primary role is to provide clear alignment and context so the team can move quickly and autonomously. This leadership style hinges on creating clarity to empower teams. When everyone understands the desired outcomes, they can own the mission and move with velocity. Ambiguity, in contrast, creates silent power struggles and slows down execution as team members hesitate or work at cross-purposes. One of the most potent tools for removing ambiguity is robust documentation. Clear, accessible documentation serves as a single source of truth, reducing misunderstandings and ensuring everyone is aligned. This is especially critical as engineering organizations scale, a lesson Meyer learned during LinkedIn's hypergrowth phases. Blameless post-mortems are another key practice for fostering a culture of clarity and continuous improvement. By focusing on systemic causes rather than individual fault, teams can openly analyze failures and learn from them without fear. This psychological safety encourages honest communication and a collective commitment to improving systems and processes. The concept extends to managing technical debt, which Jim Meyer frames as "swiping the credit card of your team's future productivity." This metaphor creates a clear understanding of the trade-offs involved. Acknowledging and planning for this "debt" removes ambiguity about future engineering capacity and priorities. For remote and hybrid teams, Meyer advocates for planning rituals as if everyone is remote to ensure equal participation. Using tools like a "stack" in chat to manage conversations creates clear communication channels and ensures all voices are heard, reducing the ambiguity that can arise in distributed environments. Ultimately, a leader's role is to establish and reinforce a culture that values clarity. Meyer emphasizes the need for explicit, shared values from the beginning, because as a company grows, these values become the default operating system. A culture that defaults to transparency and clear communication is a culture built for speed.
