Paging Charity! Engineering Leaders: Avoid Bond Villainy
This article, drawing from Charity Majors' insights, guides engineering leaders on how to avoid authoritarian pitfalls. It stresses that true leadership is about winning at business through effective operation, not just people management, while fostering humane values. Aspiring directors must cultivate business acumen and build high-performing teams by driving continuous improvement, ultimately earning their leadership privilege through excellence.

Our industry often paradoxically elevates authoritarian leadership models despite espousing collaboration. This can make new engineering managers, keen to foster different values, feel like they're fighting an uphill battle. How can leaders navigate this landscape, promote humane practices, and avoid the "Bond villain" archetype that sometimes emerges from intense hero worship? Charity Majors, a recognized alternative voice, offers valuable insights, asserting that true influence comes from business success combined with empathetic, effective operation.
The Allure of the Anti-Hero and the Problem with Mythology
It's easy to look at the business press and feel that the worst authoritarian leaders are put on pedestals. However, Majors argues that we don't necessarily celebrate sociopathy, but rather cultivate it through a phenomenon of hero worship. The reality is that over 90% of venture-backed startups fail, making the few winners exceptions. Society, craving heroes, then retrospectively crafts elaborate mythologies around these individuals. This often flattens the contributions of hundreds or thousands of employees, attributing all success to a single, often male, founder. This unhealthy veneration can transform leaders, as seen with figures like Elon Musk, into the very "Bond villains" we criticize, post-facto.
Winning at Business: The Foremost Responsibility
The fundamental lesson for any leader—manager, director, VP, C-level, or staff+ individual contributor—is to win at business. This isn't just a corporate cliché; it's the bedrock responsibility. It involves grappling with crucial strategic questions:
- Are we developing the right product or service?
- Who is our target audience, and how do we reach them effectively?
- Do we understand user needs and their willingness to pay?
- What is our competitive landscape, and how do we differentiate?
- What are the strengths and weaknesses of our product from a user perspective?
Leaders must become a beacon of context and clarity for their teams, translating overarching strategy into meaningful, actionable goals. If you genuinely want your values, such as collaboration and empathy, to permeate the industry, the most impactful approach is to succeed conspicuously, making your model one that others aspire to emulate.
Beyond Just "People Management": Diagnosing the Real Issues
Many engineers transition into management driven by a desire to create a better environment than they experienced. They aim to protect their teams' autonomy, prevent micromanagement, and prioritize well-being. While these are noble sentiments, focusing solely on employees' subjective experiences—their feelings, motivation, and work-life balance—is often a misdiagnosis.
Feelings are often outputs and trailing indicators, whereas effective management focuses on inputs. Problems like constant rework, lack of autonomy, or shifting priorities are rarely due to a manager's direct micromanagement or a personal failing. More often, they stem from deeper, systemic business issues:
- Lack of Product-Market Fit: Leading to continuous changes in product direction and redoing discovery work.
- Organizational Misalignment: Engineering not being aligned with other departments (e.g., sales) on priorities.
- Conflicting Leadership Directives: Different leaders issuing contradictory demands, causing teams to repeatedly pivot.
- Absence of Clear Decision-Making: Unclear processes for who makes decisions, what criteria are involved, who the stakeholders are, or even if a decision has been finalized.
The real challenge isn't just managing people's feelings; it's diagnosing and addressing these underlying structural weaknesses that inevitably impact team morale and productivity.
The Humane Operator: A Powerful Combination
While authoritarian tactics might yield short-term gains, Majors firmly believes that humane, empathetic, and compassionate leaders ultimately build superior businesses. Such leaders foster an environment where people feel agency, autonomy, creative inspiration, and an emotional connection to the mission and their colleagues. These are indeed powerful motivators for peak performance.
However, it's crucial to understand that simply being a kind and caring human being does not automatically equate to being adept at running a business. It's entirely possible to be empathetic yet a sloppy operator. The most effective leaders embody both traits: they are kind, caring individuals and highly skilled business operators. Leaders who are poor operators, even with good intentions, will struggle to sustain success.
Climbing the Ladder: From Manager to Director
For engineering managers aspiring to director roles, the advice is clear: focus intensely on learning the business. While engineers typically enjoy building technical systems and managers love leading teams, the business aspect often represents a significant gap in their experience. Director-level roles are inherently scarcer, and internal promotion is often the most viable path.
To advance, leaders must move beyond merely being a "back-patter in chief." While managers often advocate zealously for their teams, true leadership involves fostering a "restless hunger for improvement." Executives seek managers who can cultivate high-performing teams—groups that individuals will fondly remember for the rest of their careers. This requires systems thinking, courage to make tough decisions, and unwavering credibility, not just cheerleading.
Earning the Right to Lead
The most painful experiences in an engineer's career—projects cancelled, teams re-orged, layoffs, or cultural destruction—are often blamed on individual managers. While sometimes warranted, these events are frequently symptoms of deeper business fragilities. The example of Twitter, with its vast workforce and established culture prior to its tumultuous acquisition, serves as a stark reminder. Its leaders had ample time to ensure its business sustainability but ultimately failed to do so, opening the door for external, often disruptive, intervention.
Leadership is a privilege earned through consistent excellence in running the business. Managers and their teams must set high standards for efficiency and operational quality. If we fail to proactively secure our position by building and operating a strong, viable business, that privilege will inevitably be revoked, and the necessary changes will be imposed upon us.
FAQ
Q: Charity Majors emphasizes "winning at business" as a core leadership responsibility. What are some technical or strategic aspects engineering managers should focus on to achieve this?
A: Engineering managers should delve into understanding product-market fit, user acquisition and retention strategies, competitive analysis, and financial implications of technical decisions. This includes actively participating in defining product strategy, understanding key performance indicators (KPIs) beyond just engineering metrics, and ensuring team efforts directly contribute to revenue or cost efficiency. They need to understand the strategic "why" behind feature requests and technical roadmaps.
Q: The article mentions that issues like micromanagement or constant re-work are often symptoms of deeper business problems. Can you provide a more technical example of such a problem and its managerial solution?
A: A technical example could be a team constantly re-architecting components or redoing discovery work for features. This might seem like micromanagement or lack of autonomy, but the deeper business problem could be an unclear product vision or an inability to achieve product-market fit. The managerial solution isn't just to grant more autonomy, but to diagnose the lack of clarity in product requirements or market understanding. This involves collaborating with product leadership to establish a stable, validated product roadmap, clearly define decision-making processes for feature prioritization, and ensure stakeholders are aligned on the problem being solved before engineering begins implementation.
Q: How does a manager practically foster a "restless hunger for improvement" in a team, as opposed to just cheerleading, especially when aiming for a director role?
A: Fostering a "restless hunger for improvement" involves setting ambitious but achievable performance benchmarks, encouraging critical self-assessment and retrospectives that focus on systemic improvements, and promoting a culture of continuous learning and skill development. Practically, this means moving beyond celebrating small wins to challenging the team to optimize processes, reduce technical debt, improve system reliability, and deliver higher impact. It also involves providing constructive, data-driven feedback, creating opportunities for team members to lead initiatives for change, and demonstrating a personal commitment to improvement, thus setting the pace through action and expectation, not just praise.
Related articles
Vim in the AI Era: Evolving Workflows for Developers
The landscape of software development is undergoing a profound transformation, largely driven by the rapid advancements in artificial intelligence. For many seasoned developers, this shift has prompted a re-evaluation
Beyond the Agent Harness: Crafting Robust AI Systems for Enterprise
The world of AI development is rapidly evolving, with a growing focus on autonomous agents capable of performing complex tasks. As developers, many of us have explored various agent "harnesses" – frameworks designed to
IaC's Next Frontier: Human Expertise After AI Takes the Wheel
AI is set to revolutionize Infrastructure as Code (IaC) by automating code generation and deployment, shifting the developer role from direct authors to architects and validators. While this promises increased agility, it highlights critical needs for robust guardrails and policy-as-code. Deep systems knowledge remains crucial for human oversight, validation, and complex problem-solving in this evolving landscape.
Box Survey: AI Leaders Outperform Peers by Mastering Content
A Box survey of 1,640 IT decision-makers reveals a rapid surge in enterprise AI maturity, with leading-edge companies achieving significantly higher ROI. Key factors driving this success include robust content access, formal governance frameworks, and flexible multi-model platforms, distinguishing high performers from those with ad hoc AI approaches.
Building a Browser-Based PDF OCR to Text Converter with JS
This article guides developers through building a browser-based PDF OCR to Text converter using JavaScript. It explains the problem of unsearchable scanned PDFs, details how client-side OCR works with PDF.js and Tesseract.js, and covers implementation steps for document upload, page preview, configurable OCR settings, text extraction, and progress tracking. The solution emphasizes privacy and performance by processing documents locally in the browser.
Taking Charge: A Developer's Guide to Online Privacy
As developers, we understand data, but often overlook our own digital footprints. This article offers practical strategies to reclaim online privacy, covering everything from auditing your presence and fortifying security to leveraging privacy-focused tools and staying informed about emerging threats. Learn to navigate the data economy with intention and build healthier digital habits.




