Quote: 'You Can't Debug a Human'
A leadership podcast argues that the technical skills that make great developers "actively work against them when leading people." The host, Aleksandra Lemańska, stresses that debugging code is fundamentally different from managing human relationships, urging a shift from technical fixes to building trust and psychological safety.
The concept of psychological safety, as defined by Harvard Business School professor Amy Edmondson, is a core component of Google's research on high-performing teams. Their "Project Aristotle" identified it as the single most crucial driver of team success, more so than individual skills or experience. This is because it fosters an environment where team members feel safe to take interpersonal risks, such as admitting mistakes or offering unconventional ideas without fear of retribution. Quantifiable business outcomes are directly linked to the presence of psychological safety. A Gallup study found that organizations with high levels of psychological safety see 12% higher productivity and 27% lower turnover. Furthermore, these organizations can experience a 21% increase in profitability. For engineering teams specifically, a culture of psychological safety is positively correlated with improved software delivery performance and organizational success. In fast-paced environments like Netflix, a culture of "context, not control" is emphasized to empower engineering teams. This involves providing engineers with the necessary information and context to make their own decisions, fostering a sense of ownership and responsibility. This approach aligns with the principles of psychological safety, as it builds trust and encourages proactive problem-solving. To cultivate this environment, some tech leaders have adopted frameworks like "Radical Candor," developed by former Google and Apple executive Kim Scott. This framework advocates for a combination of caring personally and challenging directly, aiming to provide feedback that is both constructive and empathetic. The goal is to build strong relationships where direct feedback is seen as a tool for growth, not a personal attack. The transition from a hands-on developer to a manager of people requires a fundamental shift in mindset. Instead of focusing on individual technical contributions, the emphasis moves to empowering the team, fostering collaboration, and ensuring clear communication. This involves moving away from simply "debugging" problems and towards building a resilient and high-performing team culture.
