hebel. today · 10 November 202640 / 74

Career · Leadership in Tech

When managers stop providing answers

The case for coaching. Elina Kazantseva, who led coaching training for managers at Amazon, observes that leaders often fall into the 'advice monster' trap by providing quick solutions to team problems, which inadvertently trains…

The case for coaching. Elina Kazantseva, who led coaching training for managers at Amazon, observes that leaders often fall into the 'advice monster' trap by providing quick solutions to team problems, which inadvertently trains engineers to stop thinking for themselves (Alex Ponomarev from Thriving In Engineering). When managers supply immediate answers, they relieve temporary pressure but create a cycle of dependency where team members return with the same expectation for every subsequent blocker. Richard Hughes-Jones, an executive coach, notes that technical leaders are wired to provide answers to succeed, yet at higher levels, pretending to have all the answers is counterproductive in an environment defined by ambiguity (Refactoring).

The case for directive clarity. Some argue that the fundamentals of management, such as setting standards and holding people accountable, remain unchanged despite the rise of new tools (Andrew Barban Practical tools, insights…). Leaders like the executive at Docusign maintain that clear guardrails are essential, requiring human review and quality gates before any AI-generated code is merged into the system (Nick Lucchesi from The New Stack). This approach emphasizes that while coaching is valuable, certain situations demand explicit direction to ensure safety and operational reliability, as demonstrated by Docusign’s requirement that no agent can take an irreversible action without human approval.

The synthesis. Both approaches prioritize the team’s long-term capability, whether through designing safe-to-fail experiments to build autonomy or establishing rigid guardrails to manage risk. The most effective leaders identify which problems require a coaching intervention to foster thinking and which require a directive standard to maintain production integrity.

Try today · 30 min

Design one safe-to-fail experiment for a current team bottleneck.

Identify a small, reversible action that allows your team to gather data on a problem without impacting the final production outcome.

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. Alex Ponomarev, Thriving In Engineering on hebel. → ✎ Written by a personElina Kazantseva details the advice monster pattern where managers create dependency by providing quick answers rather than fostering team thinking.

  2. Nick Lucchesi, The New Stack on hebel. → ✎ Written by a personDocusign engineering explains their AI operating model, specifically the use of human-in-the-loop guardrails for autonomous coding agents.

  3. Refactoring on hebel. →Luca Rossi discusses the shift from providing answers to designing safe-to-fail experiments with executive coach Richard Hughes-Jones.

  4. Andrew Barban Practical tools, insights… on hebel. →Andrew Barban outlines management fundamentals that persist despite the evolution of technology and the myth of the hero CEO.

More in Career

Protecting the creative core from digital drift

Glean shifts product metrics from feature volume to organizational intelligence

Niche communities beat general networking

Build reputation through quiet reliability or aggressive digital curation

T-shaped expertise versus problem-focused repositioning

Leadership in Tech yesterday

Identifying systemic incentives to improve team output

Sign in to Hebel first

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