Collaborative Mindset

Day 13 Topic 2

Be the Teammate Everyone Rehires

Mindset first (Topic 13.2), then language (Topic 13.3), then mechanics (Topic 13.4). You’re not just a voice—you’re a team sport. Great collaborators make rooms safer, faster, and better. That’s not fluff; teams with psychological safety learn more and perform better, and it starts with how you think about the work and each other. 

---

Why It Matters

• Safety → performance. When people feel safe to risk questions and mistakes, teams learn faster and deliver more. (Edmondson’s field study; Google’s Project Aristotle.) 
• Not all conflict helps. Meta-analysis: relationship conflict reliably hurts performance and satisfaction; unmanaged “task conflict” isn’t the magic many think it is. Keep heat low and specific. 
• Mindsets compound. A growth mindset (skills can be developed) supports persistence and better learning behaviors under challenge. Use it to approach notes and reps. 
• Debriefs work. Proper team debriefs boost effectiveness by ~20–25% on average. Rituals matter. 

---

The Collaborative Mindset (7 principles you can run)

1. Owner, not talent. You co-own outcomes: pacing, clarity, vibe. Owners surface risks early and propose options. (You’ll script this in Topic 13.2.)
2. Psychological safety is a practice. Normalize questions, tiny experiments, and “I don’t know yet.” Name what you’re trying; invite counterpoints. 
3. Assume good data, not good intentions. Start with what you saw/heard before motives. It lowers defensiveness (see SBI in 13.2).
4. Prefer clarity over victory. Your goal is the best story, not to be right.
5. Task ≠ relationship. Debate choices (tempo, cut, beat) without labeling people. If it tilts personal, pause. (The data says relationship conflict drags teams.) 
6. Tiny loops beat big speeches. 30-second check-backs (“So: breath at bar 9, button at 12—got it?”) save hours later; this is standard “closed-loop” team practice. 
7. Reflect on purpose. Short debriefs after runs improve the next one. Keep them structured and brief. 

---

Working Agreement (15 minutes, day one)

Print this, fill it together. It becomes your micro-constitution.

• Our promise: What audience experience are we creating in one sentence?
• Feedback norms: “We use SBI; one note per pass; we ask, ‘What would help?’”
• Decision rule: Who breaks ties (Producer/Director/MD)?
• Conflict path: Task first; if heat rises, 3-minute reset → facilitator → postpone. (Protects against relationship conflict spirals.) 
• Comms cadence: 15-minute weekly standup; 24-hour reply window; check-backs on all changes. 
• Debrief ritual: 5 minutes: What worked / What to change / What to repeat. (Yes, debriefs improve performance.) 

---

Two High-Leverage Rituals

A) Premortem

 (before you start) — 10 minutes

Prompt: “It’s opening night and… the project failed. What went wrong?” Everyone writes 3 reasons; cluster them; assign owners and mitigations. Premortems reduce overconfidence and surface blind spots while building shared mental models. 

B) Debrief

 (after runs) — 5 minutes, max

• One sentence each: Keep / Change / Next Step.
• SM/MD captures one change to test on the next pass. Meta-analyses show facilitated debriefs significantly raise performance; keep it tight and routine. 

---

Self-Talk Scripts (use these in your head)

• Before notes: “Skills grow with reps. What can I try differently on the next pass?” (Growth mindset in action.) 
• When corrected: “Thank you—so the target is X at bar 9; trying it now.” (Closed loop.) 
• When you disagree: “I might be wrong—can we A/B the tempo for 60 seconds?” (Curiosity over certainty; quick experiment.)
• When you’re stuck: “What’s the smallest variable to change?” (Deliberate practice is targeted, not random.) 

---

How to Practice (short drills)

1. Premortem Lightning (solo, 5 min). List three ways your part could fail (memory, breath, cue). Write one mitigation each. Run it by the team. 
2. Debrief Reps (pair, 5 min). After a cut, each says Keep/Change/Next in 20 seconds. Switch. (Builds speed + safety.) 
3. Conflict Filter (group, 5 min). Sort a heated issue into Task vs Relationship. If it’s drifting personal, pause and rewrite the note as a task choice. 

---

Common Mistakes (and fixes)

• Waiting to “feel safe.” Safety is built by behaviors (questions, check-backs, kind specificity), not vibes. Start doing them. 
• My-way certainty. Fix: A/B test; decide by what serves the audience promise.
• Debrief sprawl. Fix: time-box to 5 minutes and capture one change. 
• Calling it “personality clash.” Fix: name the task disagreement; remove labels; choose an experiment. 

---

Pro Tips

• Green/Yellow/Red check-in at call: one word each; adjust asks accordingly. (Builds safety + shared mental model.) 
• Name the north star each day (“Clarity over volume,” “Text before tone”). Keeps alignment tight.
• Save one win per day in the group chat. Momentum is fuel.
• Rotate a 2-minute “teach.” Let a teammate demo a trick (breath plan, count-in). Spreads skill, spreads ownership. (Deliberate practice is targeted and shared.) 

---

Assignments (ship this week)

1. Write your Working Agreement with your current team (feedback norms, decision rule, debrief ritual). Pin it in the folder.
2. Run one premortem before your next rehearsal block; assign owners to the top three risks. 
3. Debrief every run for a week using Keep/Change/Next; measure time to “next clean pass.” Aim for shorter, better loops. 

---

References & Further Reading (Topic 13.3 — Collaborative Mindset)

• Google re:Work — Project Aristotle (team effectiveness; psychological safety) https://rework.withgoogle.com/en/guides/understanding-team-effectiveness ; quick-start actions: https://rework.withgoogle.com/intl/en/guides/understanding-team-effectiveness 
• Edmondson, A. (1999). Psychological Safety and Learning Behavior in Work Teams. PDF: https://web.mit.edu/curhan/www/docs/Articles/15341_Readings/Group_Performance/Edmondson%20Psychological%20safety.pdf ; Alt: https://dash.harvard.edu/entities/publication/13a7b031-0fdd-45ec-a7e0-2b80e2bc679f 
• De Dreu, C. K. W., & Weingart, L. R. (2003). Task vs. Relationship Conflict — Meta-analysis. PDF: https://web.mit.edu/curhan/www/docs/Articles/15341_Readings/Negotiation_and_Conflict_Management/De_Dreu_Weingart_Task-conflict_Meta-analysis.pdf 
• Blackwell, L., Trzesniewski, K., & Dweck, C. (2007). Growth Mindset & Achievement. Abstract: https://srcd.onlinelibrary.wiley.com/doi/abs/10.1111/j.1467-8624.2007.00995.x 
• Tannenbaum, S. I., & Cerasoli, C. P. (2013). Do Team and Individual Debriefs Enhance Performance? (Meta-analysis). PubMed: https://pubmed.ncbi.nlm.nih.gov/23516804/ ; PDF brief: https://cebma.org/assets/Uploads/Tannenbaum-Cerasoli.pdf 
• DeChurch, L. A., & Mesmer-Magnus, J. R. (2010). Shared Team Mental Models — Meta-analysis. PDF: https://atlas.northwestern.edu/papers/sharedTeam.pdf 
• Klein, G. (2007). Performing a Project Premortem (HBR). https://hbr.org/2007/09/performing-a-project-premortem ; overview: https://www.gary-klein.com/premortem 

Mindset first. Then rhetoric. Then logistics. That’s how you make rooms that sing—and want you back.