PTENES
MODULE 1.5 Fundamentals Track

🧭 The Role of Leadership

The leader as gardener of culture: what leaders do—or fail to do—that helps innovation thrive or wither.

6
Topics
~35
Minutes
Inter
Level
📚
Reading

Detailed content

1

🌿 Leader as Gardener, Not Hero

For decades, the corporate imagination celebrated the hero leader: the one who arrives with ready-made answers, saves the company at a critical moment, and carries the burden of transformation alone. In the context of innovation, this figure is not only ineffective — it is actively destructive. When the leader monopolizes solutions, the team learns to wait for permission instead of experimenting.

The gardener metaphor, popularized by Stanley McChrystal in Team of Teams (2015), amplified by Ed Catmull (Pixar) and Satya Nadella (Microsoft), reverses the logic: the leader prepares the soil, removes rocks, provides light and water—but doesn’t force the plant to grow. They create the conditions for talent to flourish without micromanaging every branch.

HERO LEADER LEADER Centralized decisions — bottleneck GARDENER LEADER LEADER Distributed autonomy—a resilient network

✓ What Gardeners Do

  • Create conditions for ideas to take root
  • Remove bureaucratic obstacles from the way
  • Ask questions instead of giving orders
  • Celebrate attempts, even those that fail
  • Share credit and amplify team voices

✗ What Heroes Do (and Destroy)

  • Monopolize decisions and solutions
  • Build a cult of personality around themselves
  • Punish mistakes instead of learning from them
  • Require agreement instead of critical debate
  • Create dependency that leaves things paralyzed in their absence

💡 Research Finding

A Gallup study (2023) of 122 thousand teams showed that a direct manager’s behavior accounts for 70% of the variance in employee engagement — more than any corporate policy or financial benefit. The gardener or the hero is literally the team environment.

2

🟢 Behaviors That Create Psychological Safety

Amy Edmondson, professor at Harvard Business School, coined the term psychological safety in the 1990s while studying medical teams: teams where nurses reported more mistakes were actually better — because the environment allowed people to speak openly. His book The Fearless Organization (2018) systematized how leaders create or destroy this safety day by day.

The 4 Foundational Behaviors (Edmondson, 2018)

A

Frame the work as a learning problem

Frame tasks as uncertain territories that require collaboration—not as execution of a fixed plan. Phrases like "We need everyone’s perspective to get this right" signal that contributions are welcome.

B

Recognize your own fallibility

Leaders who say “I could be wrong—correct me if you see something I don’t” make room for constructive dissent. Satya Nadella applied this systematically when he took over Microsoft in 2014, reversing a culture of silos and fear.

C

Be accessible and receptive

Body language, availability, and reactions to feedback shape the team’s “emotional climate.” A leader who interrupts, looks at their phone during meetings, or retaliates against criticism signals that speaking up is risky.

D

Respond productively to failure

A leader's response to the first mistake defines the culture for years to come. Investigating causes, learning from them, and protecting those who made mistakes in good faith are clear signs that it's safe to experiment.

📊 Project Aristotle — Google (2016)

Google analyzed 180 internal teams over 2 years. The number one factor that distinguished high-performing teams? Psychological safety. Not individual talent, resources, or seniority mix. Teams where people felt they could take risks without humiliation delivered more, innovated more, and retained talent longer.

3

🤝 Model Vulnerability and Admit Your Own Mistakes

Brené Brown, a researcher at the University of Houston, spent two decades studying courage and leadership. Her most counterintuitive conclusion: vulnerability is not weakness — it's the starting point for courage and innovation. Leaders who admit uncertainty and mistakes show their team that it is safe to do the same. The opposite—the leader who never makes mistakes and never changes their mind—creates a culture of pretense.

✓ Authentic Vulnerability Practices

  • "I made a mistake in that decision—here's what I learned"
  • Share dilemmas out loud before deciding
  • Explicitly and regularly asking for feedback from direct reports
  • Change your public position when the data changes
  • Acknowledge when you don't know the answer

✗ Signs of a Culture of Pretending

  • Leader who never revisits past decisions
  • Meetings where everyone agrees with the boss
  • Mistakes that “disappear” without documented learning
  • A Culture of “Not Bringing Problems Without Solutions”
  • 360 feedback with questions no one answers honestly

Pixar is one of the most documented cases of structural vulnerability in leadership. Ed Catmull created the Braintrust — meetings where directors presented unfinished versions of films for brutally honest criticism from colleagues. The rule: feedback is not binding. The director isn’t required to follow any suggestion. But they needs listen. Result: 14 consecutive films with scores above 97% on Rotten Tomatoes between 1995 and 2010.

💡 The Trust Paradox

Research by Zenger and Folkman (Harvard Business Review, 2019) involving more than 87,000 leaders showed that admitting mistakes increases the perception of competence and trust—not diminished. The behavior leaders fear most (appearing infallible = being respected) is exactly what erodes credibility over time.

4

🔒 Protecting the Space: Time, Resources, and Room to Experiment

Innovation doesn't happen in the gaps between operations — it needs explicit, allocated, protected space. The leader's role here is twofold: open this space e defend it against the day-to-day urgencies. Without active protection, operations will always devour experimentation. The tyranny of the urgent kills the important.

⌛

Allocated time

Google's "20% time" generated Gmail, Google Maps, and Google News. 3M has reserved 15% of engineers' time for their own projects since 1948 — the origin of Post-it.

💰

Protected budget

Amazon has “two-pizza teams” with their own budgets. Jeff Bezos blocked cuts to long-term projects even under pressure from quarterly results—AWS was born that way in 2003.

🛠

Experiment infrastructure

Netflix has a "chaos engineering" culture—teams have the autonomy to take production systems down to test resilience. The leader protects this practice against the impulse to eliminate risk.

The concept of organizational ambidexterity (O'Reilly and Tushman, 2004) formalizes this: companies need to operate two engines simultaneously — exploitation (optimize what exists) and exploration (invent what comes next). The leader is the only one who can allocate resources between the two without letting operations destroy exploration.

How to protect the space in practice

✓ Block recurring time on the calendar for exploratory projects — not “when there’s time left”
✓ Create innovation metrics separate from operational metrics
✓ Say “no” to requests that encroach on the experimentation space
✓ Tell the team the space is sacred — and keep that promise
5

❓ From Giving Answers to Asking Questions

Michael Marquardt, in Leading with Questions (2014), argues that the deepest transition a leader can make is to stop being the person with answers and become the person with questions. This isn’t weakness—it’s the recognition that in complex and uncertain environments, leaders rarely have access to all the relevant information. The right questions unlock the team’s distributed knowledge.

✗ The Leader Who Gives Answers

  • "The solution is to do X."
  • "We've tried this before. It doesn't work."
  • "Leave it to me; I'll take care of it."
  • “You need to focus on X.”

✓ Leader Who Asks Questions

  • "What do you think caused this?"
  • "What haven't we tried yet?"
  • "What would you need to solve this?"
  • "If there were no constraints, what would you do?"

The technique of conversational coaching — where the leader suppresses the urge to give answers and keeps the question open longer — is one of the hardest skills to learn because it goes against the instinct of someone who reached the top by being the person with the answers. Edgar Schein called this humble inquiry: the practice of asking genuine questions out of real curiosity, not as a manipulative technique.

💡 Golden Questions for Innovation

"Why have we always done it this way?"
"What does the customer really want—not what did they ask for?"
"If we failed, what would be the most likely cause?"
"What would a startup do in this situation?"
6

⚠️ Pitfalls: Micromanagement, the HiPPO Effect, and Killing Ideas Out of Fear

Even well-intentioned leaders destroy innovation without realizing it. The three most documented traps are micromanagement, the HiPPO effect, and the reflex to kill ideas out of discomfort. Each works differently, but the result is the same: the team learns that innovating is risky and stops trying.

🔍 Trap 1: Micromanagement

Micromanagement doesn't come from malice — it comes from anxiety. A micromanaging leader fears the team will make mistakes and, in trying to prevent them, eliminates precisely the autonomy that drives innovation. Gallup studies show that micromanaged employees are 28% less likely to propose new ideas.

Signs of Micromanagement

  • → Asks for updates multiple times a day
  • → Reviews every detail before approving
  • → Doesn't delegate visibly simple decisions
  • → Redoes the team's work "the right way"

Antidote

  • ✓ Set clear OKRs and let teams decide how
  • ✓ Agree on checkpoints instead of continuous status updates
  • ✓ Tolerate an Outcome That’s 80% of the Ideal
  • ✓ Recognize Your Own Fear as a Source of the Problem

🐘 Trap 2: HiPPO Effect

HiPPO = Highest Paid Person's Opinion. The effect occurs when the opinion of someone with a higher title or salary automatically wins any debate, regardless of data or evidence. Jeff Bezos named HiPPO one of the biggest enemies of innovation at Amazon—and created the “work backwards from the customer” culture as a systematic antidote.

How HiPPO Kills Innovation

PHASE 1
Leader speaks up early in the discussion
PHASE 2
The team converges on the boss’s opinion
PHASE 3
Disagreements are suppressed—groupthink

Solution: The Leader speaks last. Let the team share their perspectives before revealing your own opinion.

🚫 Trap 3: Killing Ideas Out of Fear

Phrases that sound harmless but systematically destroy innovation — what Clayton Christensen called "the innovator's dilemma at the management layer". Every time a leader uses one of these "idea killers," the team records the signal: isn’t worth the risk here.

"We've always done it this way"
"It's not the right time"
"We've tried before and it didn't work"
"This will never get approved up there"
"Too risky right now"
“You don’t understand how complex this is”

💡 Golden Rule: The Leader Who Speaks First Kills Diversity of Opinion

Jeff Bezos, Reed Hastings (Netflix), and Steve Jobs during his second period at Apple share a practice: in important decisions, the leader structures the debate, asks questions, and speaks last. This is not passivity—it is discipline. The leader who stays quiet to listen is the most powerful of all.

Module 1.5 Summary

✓ The gardener-leader creates the conditions for innovation to flourish—they don’t carry the solution alone
✓ Psychological safety (Edmondson) is the #1 factor in innovative teams — built through specific leader behaviors
✓ Modeling vulnerability and publicly admitting mistakes increases—not diminishes—a leader’s credibility
✓ Without protected space (time, budget, autonomy), operations always devour experimentation
✓ Questions unlock distributed knowledge — giving answers creates dependency and inhibits initiative
✓ Micromanagement, the HiPPO effect, and “idea killers” silently destroy innovation—even without intending to

Next Module:

1.6 - Common Barriers