SPEAKER_1: Alright, so last lecture we established that AI-powered predictive loops can anticipate problems before users even file a complaint—which is a remarkable technical capability. But I keep coming back to something: what good is a sophisticated loop if the team running it isn't actually willing to act on what it surfaces? SPEAKER_2: That's exactly the gap most teams don't see until it's too late. You can have the fastest loop, the cleanest signal, the most predictive AI—and still stall out if the culture underneath it punishes the people who act on uncomfortable findings. The technology is the engine. Culture is the fuel. SPEAKER_1: So let's ground this. What percentage of organizations have actually built what researchers call a failure-tolerant culture—one where acting on difficult feedback is genuinely safe? SPEAKER_2: The numbers are sobering. Studies consistently put it below 30%. Most organizations say they value learning from failure, but their actual incentive structures punish it. That gap between stated values and lived behavior is where feedback loops go to die. SPEAKER_1: Why is that gap so persistent? Because it seems like every leadership team knows the right answer when asked. SPEAKER_2: Ego. And I mean that structurally, not as a character flaw. When a feedback loop surfaces that a decision was wrong, someone has to own that. In cultures where status is tied to being right, that moment becomes threatening. So the signal gets rationalized away, reframed, or quietly buried. The loop ran—it just ran into a wall of self-protection. SPEAKER_1: So ego is a bigger barrier than technology. That's a strong claim. How does psychological safety actually change that dynamic mechanically? SPEAKER_2: Psychological safety—Amy Edmondson's term—is the shared belief that the team won't punish you for speaking up, flagging a failure, or challenging a direction. When it's present, people surface weak signals early, before they compound. When it's absent, those signals get suppressed until they become crises. The feedback loop depends on humans being willing to transmit honest information, and fear shuts that transmission down. SPEAKER_1: That connects to something from Ron Ritchhart's work on cultures of thinking—he identified eight cultural forces that shape whether learning actually happens in an organization. How do those map onto a product team? SPEAKER_2: Almost directly. Ritchhart's eight forces are expectations, language, time, modeling, opportunities, routines, interactions, and environment. In a product context: expectations set whether the team is optimizing for shipping fast or understanding deeply. Language shapes whether failure is called a 'miss' or a 'learning event'—that's not semantics, it's culture. And time is a statement of values—if retrospectives get cut when sprints run long, the organization is telling the team what it actually prioritizes. SPEAKER_1: The language point is interesting. Can you give a concrete example of how language moves—Ritchhart's phrase—actually shift behavior on a product team? SPEAKER_2: Sure. A team that uses the language of thinking—'what's our hypothesis here?' instead of 'what are we building?'—frames every sprint as an experiment. That framing makes it legitimate to say the experiment failed. A team that uses the language of delivery—'did we ship it?'—makes failure feel like incompetence. Same outcome, completely different cultural signal. SPEAKER_1: And modeling—that's on leadership, right? The idea that leaders have to visibly demonstrate the behavior they want. SPEAKER_2: Ritchhart calls it dispositional apprenticeship. Leaders model thinking by sharing their own uncertainty out loud—think-alouds, sharing when they were wrong, making their reasoning visible. If a VP never says 'I got that call wrong, here's what I learned,' the team learns that admitting error is career risk. Modeling isn't a soft cultural gesture. It's the primary mechanism by which norms propagate. SPEAKER_1: So what's the common misconception about failure that keeps teams stuck? Because most people would say they understand failure is part of iteration. SPEAKER_2: The misconception is that tolerating failure means accepting it passively. Real failure tolerance means treating every failure as structured data—what Ritchhart calls mistakes as opportunities to learn. That requires documentation, reflection, and a deliberate process for extracting the insight. Teams that say 'we're okay with failure' but run no retrospective are just tolerating waste, not learning from it. SPEAKER_1: Routines come up a lot in Ritchhart's framework too—thinking routines as scaffolding. How does that translate for someone building an iteration culture? SPEAKER_2: Routines make thinking visible and repeatable. In product terms: a weekly signal review, a structured retrospective format, a documented decision log. These aren't bureaucracy—they're the patterns that allow independent thinking to happen without requiring a heroic individual to drive it every time. The loop becomes institutional, not personal. SPEAKER_1: And what about the environment force? That one feels more abstract. SPEAKER_2: Ritchhart's point is that environment shapes how people spend time, relate to each other, and grapple with ideas. A physical or digital workspace that makes feedback visible—shared dashboards, open retrospective notes, public roadmaps—signals that iteration is the norm. An environment where data lives in siloed reports signals the opposite. The space itself encodes the culture. SPEAKER_1: What are the actual risks for teams that skip this? Because I think some listeners might hear 'culture' and think it's the soft stuff that comes after the real work. SPEAKER_2: The risk is compounding in the wrong direction. Without a learning culture, feedback loops surface signals that get ignored, rationalized, or acted on too slowly. The loop runs but produces no adaptation. Over time, the product drifts from the market, the team loses confidence in the process, and eventually stops investing in the loop at all. It's not a soft risk—it's the mechanism by which technically capable teams produce stagnant products. SPEAKER_1: So for Elvis and everyone working through this course—what's the one structural shift that actually builds this culture rather than just declaring it? SPEAKER_2: Stop one unhelpful practice before adding a new one. Ritchhart is explicit: enculturation requires removing what contradicts the new story, not just layering new rituals on top of old norms. If the team runs retrospectives but still penalizes the person who flags the failure, the retrospective is theater. The feedback loop is only as strong as the culture that supports it—and that culture is built by what leadership stops tolerating, not just what it starts celebrating.