Maintaining technical fluency as a manager

Technical leaders often lose their connection to the codebase as their responsibilities shift toward team coordination and strategy (Fish Food for Thought). This loss of currency is not a deliberate choice but a consequence of a schedule filled with meetings and administrative tasks. Maintaining a grasp of the work is essential, as it allows a leader to judge whether a plan is realistic or if a team has drifted away from technical constraints (Fish Food for Thought). While some argue that intent-based leadership renders deep technical knowledge unnecessary, a leader who cannot distinguish between a successful outcome and a lucky failure lacks the ability to guide their team effectively. The goal for any manager is to remain close enough to the work to ask the right questions, rather than becoming a distant authority figure who relies on status updates alone.

“The job is making the people around you better, and Ojstersek gets specific about how, from spec-driven workflows to scripts for managing up.”

Engineering Leadership

Artificial intelligence offers a new way to bridge the gap between management and technical execution without requiring a full day of coding. Executives and managers now use AI to build prototypes or walk through system architectures in minutes, a task that previously took weeks or required disturbing engineers. This capability acts as a simulator for leaders, allowing them to stay qualified on the technical systems they oversee without taking a seat from the team. By querying data directly or reviewing pull requests with the help of an AI model, a manager can verify the quality of the work and provide informed feedback. This shift enables leaders to stay current on the technical details while continuing to focus on their primary role of multiplying the team's total output (Engineering Leadership).

To sustain this involvement, leaders must move beyond status updates in their daily routines. Effective managers designate time for hands-on activities, such as querying data, sitting in on support shifts, or reading code, and they track these hours to ensure they do not disappear under the pressure of the calendar. This practice prevents the slide into micromanagement, as it shifts the focus from checking on people to understanding the work itself (Thriving In Engineering). By treating technical currency as a professional responsibility, a manager ensures they remain a valuable resource for their team rather than a bottleneck (High-Impact Engineering). This approach fosters a culture of trust, where engineers know their manager understands the challenges they face and can offer support when it is needed most.