Quote: Shift Managers From 'When' to 'What'
A recent insight for engineering leaders argues for a fundamental shift in management style. Instead of asking "When will this be done?", managers should be asking "What do you need to ship well?" The change in framing is meant to foster a culture of empowerment and ownership rather than one driven by deadline pressure.
This management philosophy is a core tenet of books like "An Elegant Puzzle" by Will Larson, which views engineering management as a series of complex problems to be solved with a human-centric approach. The goal is to maximize a team's technical leverage by strategically making decisions about team size, structure, and processes, rather than just focusing on deadlines. This approach also emphasizes proactively managing technical debt to ensure long-term sustainability. The transition from a senior individual contributor to an engineering manager requires a fundamental shift in how success is measured. It moves from solving complex technical problems and influencing architecture to focusing on team performance, communication, and the development and retention of engineers. This change often means giving up deep, focused time on technical work in favor of being highly available to the team and other stakeholders. For platform engineering teams, this "what do you need" approach directly impacts developer experience (DX). Success is measured not by lines of code, but by metrics that reflect reduced friction for developers, such as lead time for changes, deployment frequency, and developer satisfaction. According to Gartner's 2024 research, 68% of organizations with platform teams find it difficult to quantify their impact, highlighting the need for metrics beyond traditional ones. The rise of AI is intensifying the need for this supportive management style, as platform teams are now under pressure to operationalize AI capabilities securely and at scale. This includes managing new infrastructure like GPUs, ensuring AI model observability for accuracy and drift, and handling the escalating costs of AI workloads. The focus shifts to enabling developers to safely experiment with and consume AI as a platform service. This shift also changes how API platforms are built and measured, with a greater emphasis on AI-driven observability. Instead of just monitoring for uptime, modern platforms use machine learning for smart anomaly detection and predictive analysis to identify potential issues before they impact users. AI is also being used to automate test script generation, optimize API performance by identifying bottlenecks, and even predict future API workflows. For developers interacting with these platforms, the experience is paramount. Developer relations (DevRel) plays a crucial role in gathering feedback and fostering a community. High-quality documentation, clear API design, and a smooth developer journey are key metrics for a successful platform. This user-centric view helps platform teams build tools that developers will actually adopt and advocate for. The financial markets are also taking note of companies that successfully leverage AI and platform strategies. Organizations with mature platform engineering practices have been shown to achieve 30-40% lower infrastructure costs per developer. As AI becomes more integrated into core business operations, the ability to efficiently scale these technologies will be a key differentiator for companies and a point of interest for investors. Ultimately, whether on a technical or management track, the focus is on enabling teams to deliver value. For a staff+ engineer, this means influencing technical strategy and architecture to improve the developer experience. For a manager, it means creating an environment where the team has what they need to succeed, shifting the conversation from "when" to "what."
