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.