Leadership Principles
In fast-changing tech environments, Command-and-Control structures fail: too many decisions, too little expertise at the top. Modern leadership shifts decision-making authority to where the knowledge actually lives.
Good leaders in IT organizations are Enablers: they remove obstacles, set the strategic frame, and model personal accountability.
Anti-Patterns: Why Control Doesn't Scale
- Decision backlog: When every technical detail decision has to cross a leader's desk, they become the bottleneck.
- Demotivation: Highly skilled engineers lose interest when they're just executing instructions instead of solving problems on their own.
- Wrong calls: Leaders often no longer have the deep technical insight to pick the best solution at the detail level.
Principles
- Lead with Context: Communicate the "why" (strategy, customer value, urgency) and leave the "how" (technology, implementation) to the teams.
- Extreme Ownership: Every team member takes full responsibility for their area — from idea to production.
- Transparency as default: Information flows asynchronously and is accessible to everyone. This reduces tribal knowledge and enables informed decisions at every level.
- Hire for Trust: Hire people you trust, then give them the space to justify that trust. Micromanagement is a symptom of missing trust or a hiring mistake.
- Decentralized Decision Making: Complex decisions are made at the edges. Only strategic course-setting stays with central leadership.
The Manager Loop vs. Engineer Loop
Managers focus on optimizing the environment (structures, budgets, stakeholders), while engineers focus on optimizing the product. Leadership is the bridge that keeps both loops in sync.
FAQ
Don't we lose control if we stop giving detailed instructions?
We lose the illusion of control, but gain real steering capability. Through clear metrics (e.g., DORA metrics) and regular check-ins, we steer by outcomes — not by activity.
How do we ensure quality doesn't drop without direct oversight?
Quality is ensured through automated processes (CI/CD, code reviews) and clear architectural guidelines (Tech Radar) — not through manual control.
Reference Guide
- Turn the Ship Around!: L. David Marquet describes the "Leader-Leader" model in contrast to the "Leader-Follower" model. David Marquet
- The Manager's Path: Camille Fournier on the development of technical leaders. Camille Fournier
- Netflix Culture Memo: The original document on "Context not Control". Netflix Jobs