Engineering leaders urged to abandon command-and-control for autonomy-driven models

A recent article published on the Practical Engineering Management platform argues that engineering leadership must shift from a traditional command-and-control hierarchy to a 'Leader-Leader' approach. The piece contends that while technical excellence is essential for promotion, it becomes a liability in management roles when it leads to micromanagement. The author suggests that this oversight creates 'learned helplessness' within teams, where engineers stop thinking critically and wait for instructions, effectively turning leaders into bottlenecks.

Drawing heavily on the experiences of former U.S. Navy Captain David Marquet and his book 'Turn The Ship Around', the article details how Marquet transformed the USS Santa Fe from the worst-performing submarine in the fleet to a top-performing unit. The core of this transformation was empowering crew members to state their intentions rather than seeking permission. The article proposes adopting 'intent-driven' language, such as replacing 'Can I...' with 'I intend to...', to foster autonomy and critical thinking among engineering staff.

The argument is bolstered by data from Google’s Project Oxygen, an internal study on effective management. The article notes that 'technical expertise' ranks last among the traits of effective managers in Google’s findings. Instead, traits such as coaching, empowering teams, and creating an inclusive environment are prioritised. The author emphasises that while technical skills are necessary, they are not sufficient; the true differentiator for leaders is the ability to develop and empower others.

To implement this shift, the article recommends banning permission-seeking language in technical discussions and replacing it with clarifying questions. Leaders are advised to establish clear guardrails, such as architecture principles and non-functional requirements, rather than acting as checkpoints for every decision. The author shares a personal anecdote about a team given autonomy to decide on Friday deployments, supported by robust telemetry, feature flags, and automated testing, which allowed them to operate independently without compromising stability.

The piece also highlights the importance of visible thinking processes, comparing them to the evaluation methods in System Design interviews. By verbalising their troubleshooting mental models, senior engineers can create shared understanding and learning opportunities that silent expertise cannot. The article concludes that leaders must normalise phrases like 'I don't know, let's find out' and conduct blameless postmortems to build a culture of continuous learning, ultimately multiplying their impact by creating future leaders rather than just delivering code.