8  Module 6: Implementation and Sustainability (40 minutes)

Facilitator: Mónica Muñoz Torres (Bridge Center)

8.1 Learning Objectives

By the end of this module, participants will be able to:

  1. Explain the Knowing-Doing Gap and describe why behavior change in institutional settings requires more than understanding a concept.
  2. Design a Micro-Pilot: a low-stakes, zero-budget, two-week experiment targeting one specific friction point in their team’s work.
  3. Define a measurable success criterion for their Micro-Pilot.
  4. Anticipate resistance to their pilot and identify at least one champion and one structural fix to address it.

8.2 Module Overview

Every training program faces the same problem: participants leave energized, return to their regular environment, and within weeks the new insights have no effect on how they actually work. This is not a failure of motivation or memory. It is the Knowing-Doing Gap — a well-documented phenomenon in organizational research where the knowledge of what to do fails to translate into actually doing it, because the conditions under which we act (busy, stressed, under competing pressures) are so different from the conditions under which we learned (calm, reflective, open to new ideas).

This final module is designed as a bridge across that gap. Rather than leaving with a general intention to “collaborate better,” participants leave with a specific, testable experiment: a two-week Micro-Pilot targeting one friction point, with a defined success metric, a named champion, and a structural fix for the most likely failure mode. The Micro-Pilot framing is deliberate — calling something a “pilot” rather than a “policy” dramatically lowers the social and institutional resistance to trying it. A pilot is hypothesis; it can be revised or abandoned. A policy is a commitment. Framing implementation as experimentation is not just rhetorical softening — it is accurate: you are genuinely trying something to see if it works in your specific context.

8.3 Participant Background Reading

Participants are encouraged to review the following before the session. Each takes 15–20 minutes.

  • Pfeffer, J., & Sutton, R. I. (2000). The Knowing-Doing Gap: How Smart Companies Turn Knowledge into Action. Harvard Business School Press. The source of the “Knowing-Doing Gap” concept referenced in this module. Before the session, read the Introduction or Chapter 1, which establishes the core insight: the biggest obstacle to performance is not knowing what to do — it is doing it. Full text may require library access; many libraries have it as an ebook. A summary is sufficient if the full text is unavailable.

  • Gollwitzer, P. M. (1999). “Implementation Intentions: Strong Effects of Simple Plans.” American Psychologist, 54(7), 493–503. The psychological research behind why the Micro-Pilot format works: people who specify when, where, and how they will carry out an intention (“When X happens, I will do Y”) are dramatically more likely to follow through than people who just form a general intention. Read the abstract and the first 2 pages of the paper — the core finding is accessible and directly applicable to the activity design.

8.4 Instructor Notes

8.4.1 Conceptual Background

The cold state / hot state distinction. The module introduces the metaphor of “cold” (reflective, rational) versus “hot” (stressed, reactive) states for decision-making. This framing draws on dual-process psychology — the idea that humans make decisions differently under stress than under reflection. The practical implication for behavior change is that interventions designed in cold-state conditions often fail in hot-state conditions, not because the person doesn’t want to change, but because the intervention requires cognitive resources (deliberate attention, working memory, willingness to deviate from default) that are not available when stress is high. The Micro-Pilot addresses this by building in structural supports — checklists, defaults, pre-committed actions — that work even when the person is running on autopilot.

Implementation intentions. Gollwitzer’s research on implementation intentions shows that the simple act of specifying “When situation X arises, I will do Y” increases follow-through on intentions by an average of about 2–3x compared to simply intending to act. The Micro-Pilot format operationalizes this: Step 1 defines the trigger situation (the friction point), Step 2 defines the action (the pilot), and Step 3 defines how you’ll know it worked. This is not coincidental — the activity is designed to produce an implementation intention, not just a general plan.

The Pilot Method and resistance. Reframing a change as a “pilot” or “experiment” is one of the most effective strategies for reducing institutional resistance, for several reasons: - It lowers the perceived cost of being wrong (a failed experiment is data, not a failure) - It creates a natural review point (the 2-week mark) that legitimizes revisiting the change - It decouples the person from the idea — “we tried something and it didn’t work” rather than “I was wrong” - It converts skeptics from blockers into participants (a skeptic can be invited to observe the pilot and assess the results)

Common Micro-Pilot mistakes. Help participants avoid these patterns: - Too big: “We will redesign our lab’s authorship policy” is a policy, not a pilot. A pilot targets one specific behavior in one specific context. - Too vague: “We will communicate better” has no metric. A pilot has a defined, observable success criterion. - Permission-dependent: “I will ask my PI to change how we run lab meetings” is not zero-permission. A pilot is something the participant can start unilaterally — asking for permission is itself a change, and permission might not come. - No metric: Without a success criterion, there is no experiment — just a hope. The metric doesn’t have to be sophisticated; “Did the meeting end on time?” counts.

Facilitating the Skeptic/Champion exercise. The Reality Check is often the most revealing part of the module. When a partner voices the skeptical response, participants frequently discover that the main obstacle is not external resistance but their own uncertainty about whether the change is worth the social capital it costs. This is worth surfacing gently: “What would it take for you to feel confident enough to try this?”

8.4.2 Key Concepts

  • Knowing-Doing Gap: The well-documented phenomenon in which people who know what they should do nevertheless fail to do it, because situational pressures, habits, and organizational defaults override deliberate intention.
  • Cold state vs. hot state: A distinction between the reflective, low-pressure conditions in which people form intentions (cold) and the stressed, high-pressure conditions in which they must act on them (hot). Behavior change interventions must account for hot-state conditions to be effective.
  • Implementation intention: A specific plan of the form “When situation X arises, I will do Y” — shown in psychological research to dramatically increase follow-through compared to general intentions.
  • Micro-Pilot: A structured, low-stakes, time-bounded experiment targeting one specific behavior change. Must require zero budget and zero permission to start, and must have a defined success metric.
  • Resistance: Skepticism or pushback toward a proposed change. Reframed in this module not as obstruction but as information — resistance often surfaces real constraints or concerns that improve the design of the pilot.
  • Champion: A person within the team or organization who supports the pilot and can provide encouragement, resources, or legitimacy when resistance arises.
  • Structural fix: A concrete mechanism (checklist, template, default, calendar reminder) that makes the desired behavior easier to perform, especially in hot-state conditions.

8.5 Content Block: The Monday Morning Protocol (5 minutes)

The goal is for participants to leave not just with a plan, but with a designed experiment to introduce one team science practice to their lab.

8.5.1 The Hook (The Implementation Challenge) (5 minutes)

  • Facilitator: “We know that 90% of training is lost without implementation support. Your labs are busy, stressed, and resistant to change. We aren’t going to overhaul your lab culture overnight. We are going to run a scientific experiment on your team’s process.”
  • Concept: Briefly introduce the Knowing-Doing Gap and Resistance as natural forces to be navigated, not fought. Recognize that understanding the source of resistance often presents a gift, resulting in a better approach.
Concept The Trap The Strategy
The Knowing-Doing Gap Assuming that learning information automatically leads to behavior change. Design for unfavorable conditions, the “Hot State”: Create checklists and defaults that work when you are stressed and busy.
Resistance Viewing skepticism as “being difficult” or “anti-collaboration.” The Pilot Method: Lower the stakes. Don’t ask for a permanent change; ask for a temporary experiment.

Food for thought: We have spent 5 modules learning what to do. But research shows there is a ‘Valley of Death’ between learning a concept and applying it. This is the Knowing-Doing Gap (attributed to Jeff Pfeffer and Bob Sutton, 2000). In this workshop, you are currently in a ‘cold’ state—you are calm, rational, and reflective. Next Monday morning, you will return to a ‘hot’ state—stressed, rushing for grant deadlines, and managing complex personalities. From an overly simplistic point of view, the Knowing-Doing gap happens because we try to apply ‘cold’ logic to ‘hot’ situations without a bridge. Today, our workshop is about building that bridge.

8.6 Activity 6: The Monday Morning Protocol (35 minutes)

8.6.1 The Design Sprint (Start Small & Measurement) (20 minutes)

  • Step 1: Select the Variable (5 mins): Participants pick one friction point from Modules 1-5 (e.g., “Meetings go overtime,” “Data is hard to find,” “Unclear authorship”).
  • Step 2: Design the Micro-Pilot (10 mins): Instead of a “policy,” they design a 2-week pilot. (Constraint: It must require zero budget and zero permission to start (e.g., “I will send an agenda 24 hours before my next update meeting,” not “We will change how the whole lab meets”).)
  • Step 3: Define the Metric (5 mins): How will they know it worked? (e.g., “Meeting ended 5 mins early,” “PI replied to email within 24 hours”). This covers the Measurement block.

8.6.2 The Reality Check (Scaling Thoughtfully) (10 minutes)

  • Peer Consulting (10 mins): Pairs swap plans. The partner plays the role of the Skeptic/System (e.g., a busy PI or cynical post-doc). They identify one reason the pilot will fail.
  • The proposer must identify one Champion (who will support this?) and one Structural Fix (template, checklist) to address the skeptic. This covers the Scaling block.

8.6.3 Debrief & Commitment (5 minutes)

  • Ask 2-3 volunteers to share their Micro-Pilot.
  • Facilitator Closing: Sustainability isn’t about giant leaps; it’s about successful pilots that get scaled because they work.

Module Materials