---
id: ins_criticize-in-public
operator: Jeetu Patel
operator_role: Chief Product Officer and President, Cisco
source_url: https://www.lennysnewsletter.com/p/ai-is-critical-for-humanitys-survival
source_type: podcast
source_title: Jeetu Patel — Turning Cisco AI-first — Lenny's Podcast
source_date: 2026-04-28
captured_date: 2026-05-01
domain: [leadership]
lifecycle: [process-cadence]
maturity: applied
artifact_class: framework
score: { originality: 4, specificity: 3, evidence: 3, transferability: 4, source: 5 }
tier: B
related: []
raw_ref: raw/podcasts/jeetu-patel--cisco-ai-first-transformation--2026-04-28.md
---

# Establish enough trust to critique and debate in public, not "praise public, criticize private"

## Claim
The default management orthodoxy "praise in public, criticize in private" produces a culture where real disagreement is hidden. Replace it with: build enough trust on the team that critique and debate happen in public. Public critique under sufficient trust accelerates learning across the team; private critique compresses learning to the two people in the room.

## Mechanism
Trust is the precondition. With it, a public critique reads as engaged collaboration; without it, the same critique reads as humiliation. The work is in building the trust upstream, through psychological safety, named values, demonstrated leadership, so that critique can be public when it lands. Once it can, the team learns 10x faster because every disagreement is a teaching moment for everyone in earshot.

## Conditions
Holds when:
- The team has built genuine trust through repeated low-stakes interactions.
- The leader models accepting public critique themselves.

Fails when:
- The trust isn't actually there. Public critique then is harm.
- The framework gets used as cover for shaming weaker performers in front of the team.

## Evidence
> "Every management book will tell you praise in public, criticize in private. I fundamentally disagree. What you have to do is establish enough trust among the team so that you are comfortable critiquing and debating in public."

Jeetu's authority for this: 30K direct/indirect reports at Cisco. Pattern persists at scale.

· Jeetu Patel on Lenny's Podcast, 2026-04-28

## Signals
- Disagreements happen in standing meetings, not in side DMs.
- Junior team members critique senior decisions in the same room as everyone else.
- Post-meeting drama drops because the disagreements happened in the meeting.

## Counter-evidence
Most teams don't have the trust to make this work. Applying the rule without the trust foundation produces broken people, not better learning. The rule is correct under specific cultural conditions, not universal.

## Cross-references
- (decision-quality and trust-related cards across operators)