# cutler-teams-dont-escalate-leaders-linkedin-2025-10-03

## Veille

Why teams don't escalate problems, organizational barriers, overcommitment pressure, career risks, leadership actions - John Cutler LinkedIn

## Titre Article

Why Teams Don't Escalate (and What Leaders Can Do About It)

## Date

2025-10-03

## URL

https://www.linkedin.com/pulse/why-teams-dont-escalate-what-leaders-can-do-john-cutler-bfpdc/

## Keywords

escalation dysfunction, organizational barriers, overcommitment culture, career risk, priority conflict, complexity compression, political stakes, WIP limits, trip-wires, scope reduction, leadership accountability, normalize escalation, protecting capacity, team dynamics, dependency management

## Authors

John Cutler (Head of Product @Dotwork, ex-Amplitude)

## Ton

**Profile:** Conversational-Professional | Second-person diagnostic | Analytical-Educational | Intermediate-Expert

Cutler adopts a direct style addressing leaders ("you receive opposite story") blending analytical rigor with accessible field language. Systematic enumeration structure (8 barriers, 10 levers) reveals a systems thinker. Empathetic diagnostic tone acknowledging human complexity ("not malice/subterfuge but because humans"). Memorable phrases ("Lost in details," "Cascade down-the-chain") crystallize organizational patterns. Assumed technical vocabulary (trip-wires, WIP limits, enabling constraints) targets an audience of product leaders/engineering managers. Typical LinkedIn thought leadership from a senior practitioner sharing battle-tested insights without academic formality.

## Pense-betes

- **Central paradox**: informal feedback is full of problems (overload, conflicting priorities, dependencies) but leaders hear nothing when they ask "How can I help?"
- **3 minutes is not enough**: complex problems don't condense into a 3-minute summary — distortion/oversimplification is guaranteed
- **Missing people**: solving it requires all stakeholders + their managers + a CEO for tie-breaking → political stakes explode
- **Career cost**: PMs/Engineering Managers think asking for help = personal failure, promotion risk
- **Protecting one's own priorities**: teams keep a low profile to avoid having THEIR priorities questioned under scrutiny
- **Overcommitment pressure**: saying "yes" has literally no immediate downside (ambition/alignment), saying "no" = immediate political risk (resistant/not a team player)
- **Deferred costs**: overcommitment → costs (slipped timelines, hidden burnout, demoralization) arrive late and are absorbed by the teams, not by those who made the commitments
- **Down-the-chain cascade**: every small problem amplified VP → Director → Manager
- **2023–2025 context**: layoffs, changing strategies, AI threat/promise, profitability vs. innovation pressures → idealized rules no longer apply
- **Baseline assumption**: start from the principle that (1) information doesn't circulate, (2) teams are overcommitted, not out of malice but humanity + uncertainty/complexity
- **Automatic trip-wires**: trigger escalations automatically (>N team-weeks of effort, >N days in progress, >N teams involved, complexity >N score)
- **Immediate demonstration**: when an escalation is triggered, leadership MUST reduce scope/shift priorities/provide cover in that same meeting (otherwise escalation = a trap)
- **Celebrate the "no"**: publicly asking "What did you say no to?" and celebrating the answer in front of peers normalizes protecting capacity over optimism theater
- **Recurring lightweight forums**: default weekly sync to surface nuance without judgment, avoids one-shot compression
- **Pre-alignment**: small coalition of stakeholders before the "big room meeting" to avoid collapsing into "find a way to do everything"
- **Shared visible boards**: cross-group priority boards/dependency maps externalize the conversation, trade-offs feel less like a direct threat to a team's roadmap

## RésuméDe400mots

**A Fundamental Organizational Paradox**

John Cutler, Head of Product at Dotwork, diagnoses a critical organizational paradox observed in October 2025: formal/informal feedback channels overflow with distress signals (overwhelmed teams, conflicting priorities, high WIP, blocking dependencies). Yet when leaders offer help, they receive the opposite story: teams have everything under control, nothing to escalate. This gap reveals a deep systemic dysfunction, not an individual failure.

**Eight Structural Barriers Preventing Escalation**

**(1) Impossible compression**: complex problems do not condense into the 3-minute summary leaders demand. Compression invariably distorts/oversimplifies. It is often impossible to pinpoint "the problem" — you know things are perpetually slipping, the team keeps taking on more than it can manage, but it's not as clear-cut as "stop X → Y will go 2x faster." Opening a Pandora's box.

**(2) Missing people in the room**: responding appropriately requires all involved parties + their managers + advocates for competing priorities + potentially the CEO as tie-breaker. First challenge: getting everyone together. Second challenge (or because of it): political stakes explode. Typical action items become "teams go figure out how to do everything + propose where to cut scope."

**(3) Lost in details**: leaders lacking deep context start asking trade-off questions, pros/cons of cutbacks, scope-testing pressure. Normal questions but they trigger a cascade of work for teams. You want to say "choose between X and Y, full stop" but the natural flow of conversation falls into the trap of "can we somehow say yes to both?"

**(4) Career risk**: PMs/Engineering Managers learn that push-back is part of the job. Asking for help is perceived as dropping the ball. Even if a leader offers help, a potential career cost is perceived.

**(5) Protecting one's own priorities**: a team reporting to product group A but working for group B. Promotion is based on work done for A. Counterintuitively, teams keep a low profile to avoid having THEIR priorities questioned. Extra scrutiny = liability.

**(6) Skill**: framing succinctly so that experienced/influential leaders can act = a skill. Dancing around problems on this list without burnout or being put through the wringer, ending up with zero shifted commitments = a skill. The trap of minutiae versus irrelevant details. Flipside: very experienced people covertly shift priorities without escalating, knowing better than to do so openly but avoiding it because of the problems mentioned above.

**(7) Overcommitment pressure**: saying "yes" has literally no immediate downside — it looks ambitious, optimistic, aligned. Costs (slipped timelines, hidden burnout, demoralization) arrive late, absorbed by the teams doing the work, not by those who set the commitments. Conversely, push-back carries immediate risks (being seen as resistant, not a team player, forcing leaders to make prioritization decisions they'd rather avoid). Overcommitment is the politically safe option even if it buries the team.

**(8) Hierarchical cascade**: compounding down the chain, VP → Directors → Managers. A small problem is amplified exponentially.

**2023–2025 Context: Idealized Rules Are Obsolete**

Recent years: layoffs, shifting strategies, the AI bounty/threat, a less-than-rosy macro picture, extreme opposing pressures between profitability and innovation. Idealized normal rules do not apply. Even in the best of times, they never fully applied. Now, absolutely not. Uncertainty and complexity practically guarantee that teams won't escalate "normally."

**Critical Baseline Assumption**

Leaders must start from the principle that: **(1) information does not travel**, **(2) teams are probably overcommitted**. Not out of malice or subterfuge but because people are human. When you add uncertainty/complexity, it's a near-guarantee teams won't escalate "normally."

**Concrete Leadership Actions (10 Levers)**

**Recurring lightweight forums**: a default standing weekly sync where nuance surfaces without judgment, "no perfect answer required." Avoids one-shot compression.

**Pre-alignment**: a small coalition of stakeholders before the big-room meeting. Share a draft framing of trade-offs so the conversation doesn't collapse into "find a way to do everything."

**Normalize escalation**: reframe it as a leadership responsibility, not a failure. Leaders model this by publicly thanking someone who raises an issue instead of rewarding "heroic silence."

**Shared visible boards**: priority boards/dependency maps across groups. Externalizes the conversation so trade-offs feel less like a direct threat to a team's roadmap.

**Upfront enabling constraints**: WIP limits, batch-size limits, SLAs for reactive work. Removes in-the-moment pressure because a team can point to an agreed constraint instead of justifying trade-offs politically on an ad hoc basis.

**Automatic trip-wires**: automatic escalation removes the burden of political courage. Examples: >N team-weeks of effort → escalate to leadership for re-scoping; an item in progress >N days → triggers a review of blockers/scope cuts; >N teams involved → escalate to a portfolio-level dependency forum; complexity score >N → requires senior sign-off before continuing.

**Immediate demonstration**: when a team triggers an escalation, leadership must demonstrably reduce scope/shift priorities/provide cover in that same meeting. Even small or symbolic changes show that escalation is a lever, not a trap.

**Celebrating "no"**: at every planning forum, praise/spotlight teams or managers who reduced scope before overcommitting. A leadership reflex of asking "What did you say no to?" and celebrating the answer in front of peers. Over the long term, this normalizes the idea that professional credibility comes from protecting capacity and making clear trade-offs, not from optimism theater.

**Systemic Lesson**

The problem is not a failure of individual courage but a system design that rewards overcommitment and punishes transparency. The solution requires leaders to redesign incentives/structures so that escalation becomes the path of least resistance rather than an act of political courage.

## GrapheDeConnaissance

- John Cutler —publie→ Why Teams Don't Escalate (DOCUMENT, 0.99)
- John Cutler —travaille_chez→ Dotwork (ORGANISATION, 0.97)
- John Cutler —affirme_que→ les équipes n'escaladent pas les problèmes bloquants (AFFIRMATION, 0.98)
- pression surengagement —soutient→ dire oui (CONCEPT, 0.95)
- risque carrière —réduit→ escalation (CONCEPT, 0.94)
- compression 3 minutes —réduit→ fidélité des problèmes complexes (CONCEPT, 0.92)
- enjeux politiques —s_oppose_à→ résolution collective (CONCEPT, 0.9)
- cascade hiérarchique —permet→ amplification des dysfonctionnements (CONCEPT, 0.89)
- trip-wires automatiques —remplace→ courage politique (CONCEPT, 0.88)
- John Cutler —recommande→ démonstration immédiate de réduction de scope (METHODOLOGIE, 0.9)
- WIP limits —réduit→ escalation (CONCEPT, 0.85)
- contexte 2023-2025 —s_oppose_à→ escalation (CONCEPT, 0.87)
- John Cutler —recommande→ forums légers récurrents (METHODOLOGIE, 0.93)
- pression surengagement —permet→ coûts différés absorbés par les équipes (CONCEPT, 0.91)
- célébration du refus —soutient→ protection de capacité (CONCEPT, 0.86)

---
Canonical: https://www.thekb.eu/en/fiches/cutler-teams-dont-escalate-leaders-linkedin-2025-10-03/