hebel. today · 11 November 20264 / 73

Career · Leadership in Tech

Engineering managers shift from process routers to context providers

Context over control. Marc Randolph, co-founder of Netflix, focuses on aligning team assumptions about budget, timeline, and quality rather than managing individual decisions. When a team member makes a call that differs from his…

Context over control. Marc Randolph, co-founder of Netflix, focuses on aligning team assumptions about budget, timeline, and quality rather than managing individual decisions. When a team member makes a call that differs from his own, he asks what information he failed to provide. This approach builds organizational resilience by ensuring engineers possess the context to make sound choices independently (Marc Randolph's Substack).

Systems-level bottleneck management. Tarik Guney, a Principal Software Engineering Manager at Microsoft, identifies bottlenecks by monitoring leading indicators like process efficiency and developer productivity. He treats delays and distorted feedback as signals that the team is optimizing the wrong constraints. By focusing on these indicators, he catches preventable mistakes before they escalate into unmanageable issues (Gregor Ojstersek from Engineering Leadership).

Feedback through inquiry. Leaders at medical institutions use the Ask-Tell-Ask sequence to address annoying behaviors without damaging relationships (Admired Leadership Field Notes). A manager invites the employee to share their perspective first, presents a specific observation, and then asks for a response. This method allows the individual to reach their own conclusion about the behavior while ensuring they hear the necessary feedback.

Managing the AI shift. AI coding tools increase pull request volume by a factor of three, exposing existing gaps in delegation and review skills (The Good Boss, The Good Boss). Engineering managers who rely on manual process routing to justify their roles face higher risks of displacement as organizations flatten structures (Mirek Stanek from Practical Engineering Management). Success requires mastering human-centric dynamics like psychological safety and clear expectation setting, which remain outside the scope of automated agents (Mirek Stanek from Practical Engineering Management).

  • Managers should document accomplishments in a brag document, including specific outcomes like a 30 percent reduction in failed payments, to shape management perception (IEEE Spectrum).
  • Interviewers for engineering manager roles test for fast diagnosis and clear, written expectations when handling low performers within a four-to-eight-week window (AI Engineering Insider).

Try today · 15 min

Address one persistent, minor team annoyance using the Ask-Tell-Ask sequence.

Identify a specific behavior that grates on you, then schedule a brief check-in to ask the person how they feel that behavior is landing with the team.

You need

  • A specific, observed behavior
  • A neutral, open-ended question

Steps

  1. Ask the person for their view on the situation.
  2. Listen to their response without interrupting.
  3. Share your specific observation of the behavior.
  4. Ask for their perspective on the impact of that behavior.
  5. Agree on a path forward together.

One email instead of your newsletter pile.

Forward the newsletters you already get (a Gmail filter does it) and tell Hebel your goals. Every morning it reads them with 20,000 others and sends one short email, with one small thing to do today. Fewer emails, not more. Free during beta.

Start my paper →
LinkedIn X

Sources

  1. Marc Randolph's Substack on hebel. →Marc Randolph details how aligning on high-level goals allows managers to delegate decisions effectively.

  2. Gregor Ojstersek, Engineering Leadership on hebel. → ✎ Written by a personTarik Guney explains how to identify system constraints by monitoring leading indicators of developer productivity.

  3. Admired Leadership Field Notes on hebel. →The Ask-Tell-Ask sequence provides a structured method for delivering feedback on irritating behaviors.

  4. The Good Boss on hebel. →Gaurav Jain connects the rise of AI coding tools to the necessity of strong management fundamentals.

  5. Mirek Stanek, Practical Engineering Management on hebel. → ✎ Written by a personMirek Stanek provides data on the trend of flattening management structures and the risks for hands-off leaders.

  6. IEEE Spectrum on hebel. →A guide on using brag documents to make individual contributions visible to management during reviews.

  7. AI Engineering Insider on hebel. →

More in Career

Shift your professional identity from roles to problems

Amazon and Webflow shift from AI output volume to customer-centric outcomes

Closing the gap between your expertise and your visual identity

Turn your personal archive into a connection engine

Sequoia and Travis Kalanick reveal the new math of focus

Leadership in Tech yesterday

When managers stop providing answers

Sign in to Hebel first

Likes, your collection and done Hebel need an account. We email you a six digit code; no password.