Dr. Marc Reynolds Performing Arts Studio

Sing Easier - Perform Like A Pro

drmarcreynolds

Stop Talking and Do It Now!

by Leave a Comment

Day 13 Topic 5

Ship Small • Ship Soon • Learn Faster

Artists love ideas. (Me too.) But careers move when ideas turn into artifacts—clips, emails, pages, programs, rehearsals, tickets. This finale is your activation ritual: how to go from “we should…” to “we shipped” at the micro level (practice/lessons), the room level (rehearsals), and the life level (projects). You now have a toolbox; this locks in the habit of using one tool at a time so improvement spirals upward. Let’s move.

Why It Matters

  • If–then planning works. Writing tiny “implementation intentions” (“If it’s 9:00, then I press record and sing 45 seconds”) measurably increases goal follow-through across dozens of studies. 
  • We chronically underestimate time. The planning fallacy makes us think “this won’t take long”—and then it does. Action + short deadlines beat optimistic talk. 
  • Bias toward action is a proven creative engine. Design programs (d.school/IDEO) hardwire “build–test–learn” so teams stop debating and start prototyping. We can, too. 
  • Loops > speeches. Lean/Agile’s build–measure–learn cycle wasn’t invented for singers, but it maps perfectly to repertoire, reels, and rehearsal plans. 

The Four Operating Rules

  1. If–Then the Start Make the first move automatic: “If the metronome turns on, then I sing the cut once.” (Implementation intentions drive action from cue → behavior.) 
  2. Two-Minute Rule If the next action takes ≤2 minutes (start camera, create doc, send “are you free?”), do it now. Don’t file it. Don’t workshop it. Do it. 
  3. One Variable Per Sprint Change exactly one thing per pass (tempo, breath plan, vowel). That’s deliberate practice, not loops of vague repetition. 
  4. Ship → Measure → Learn Every session ends with an artifact (clip, bar-by-bar markup, email sent). Review the artifact, adjust one variable, repeat. (Lean cycle.) 

Micro (Practice & Lessons): 12-Minute “Sing-Then-Fix” Loop

Timer: 12 minutes.

  1. Press Record (0:00–0:45). Perform one 30–45s cut—no warm-up spiral.
  2. Watch Once (0:45–2:00). Name one fix (breath at bar 9; consonants at button).
  3. Drill the Fix (2:00–6:00). Three tiny reps on that exact bar/gesture.
  4. Retake (6:00–7:00). Same cut, same key.
  5. Decide (7:00–8:00). Better? Y/N. If N, pick a smaller variable.
  6. Log It (8:00–10:00). One line in your “Ship Log” (variable, result).
  7. If–Then for Tomorrow (10:00–12:00). Write the next micro-plan now.

Deliberate practice = specific goal + feedback + repetition + refinement. Rinse. (Yes, this beats “running it again” every time.) 

If–Then templates (steal):

  • “If I put the phone on the stand, then I hit record and sing 45 seconds.” 
  • “If I miss the breath at bar 9, then I isolate it three times and retake.”
  • “If I open my calendar, then I block 12 minutes for tomorrow’s loop.”

Meso (Rehearsals): Talk-to-Sing Ratio = 1:3

  • Default: 30–60s notes → 2–3 minutes of doing.
  • SBAR for changes (fast headline, two options), then check-back and run it. Save the discourse for after you’ve tried something once. (You already know SBAR/check-backs—use them as the doing accelerator.) 
  • One tweak per pass. If it’s not better, revert. If it is, keep and move.

Room If–Then:

  • “If notes exceed 60s, then we sing the new version once before more talk.”
  • “If we give the same note twice, then we book a 5-minute seam rehearsal.”

Macro (Projects): Make a Prototype the First Hour

  • Website: Publish a one-screen hero (promise + 45-sec reel + CTA). Iterate later. 
  • EPK: One Google Doc with short bio, 2 photos, 2 links, contact. Pretty can wait. 
  • Show: Lock a living-room date, then build backward. (Rights check if public.)
  • Social: Post the first clip of your six-post series today; wire to your booking link. (Retention teaches you what to fix next.) 

Prototyping mantra: “Make it tangible by noon.” Design practice calls this a bias toward action—because tangible beats theoretical. 

The Tools (print these)

A) “Now Card” (fits in your case)

  • Next visible artifact: (e.g., 45-sec “Opener” cut)
  • Constraint: (one variable)
  • Timer: (12 minutes)
  • If–Then: (cue → behavior)

B) Ship Log (one line per session)

Date | Artifact | One variable | Better? (Y/N) | Next If–Then

C) Action Ladder (when stuck)

  • 2-minute start: what can I do right now? (hit record / create doc / email) 
  • 12-minute loop: one variable, one retake
  • 24-hour ship: publish/send one artifact (clip, ask, page)

Common Mistakes (and Quick Fixes)

  • Endless table reads of your own ideas. Fix: prototype the idea in 10 minutes (clip, sketch staging, one-page). 
  • “Let’s plan the plan.” Fix: write an If–Then and start the smallest step now. 
  • Five fixes at once. Fix: one variable per pass—deliberate practice, not chaos. 
  • Optimism about time. Fix: halve scope, not sleep; log real times to fight the planning fallacy. 

Pro Tips

  • Prototype anything. A program can be a Google Doc; a set can be chair tape; a reel can be three jump-cuts. (IDEO/d.school say: prototype early, rough, cheap.) 
  • Name your sprint. “Button at 1:12,” “Breath at bar 9,” “Hero above-the-fold.” Clear targets, faster wins.
  • Borrow Lean eyes. What’s the smallest artifact that earns useful feedback today? 
  • Celebrate micro-wins. Post “Shipped: [artifact]” in your notes; momentum compounds.

Assignments (Ship This Week)

  1. 12-Minute Daily (5 days): run the sing-then-fix loop; log one artifact/day. (One variable per pass.) 
  2. 48-Hour Ship: choose ONE:
    • Publish a 45-sec opener clip (bio links wired to Request Availability).
    • Stand up a one-screen homepage (promise + reel + CTA). 
    • Email one conductor/artistic planner with a 45-sec reel ask.
  3. If–Then Plan: Write three if–then statements (practice, rehearsal, project) and tape them where you work. 

Remember: work begets work. The people who ship get feedback, get better, and get booked.

References & Further Reading — Topic 13.5 (Action & Execution)

You’ve got the tools. The difference now is using them today. Sing the cut. Post the clip. Send the email. Book the room. Then do it again tomorrow—one small ship at a time.

Synergy vs. Implosion

by Leave a Comment

Day 13 Topic 4

Systems That Make Teams Sing (and Keep Them From Snapping)

You’ve got the people, the piece, the room. Why do some projects snowball into joy and others… detonate? The difference is systems: how parts meet, how information moves, and how risks get caught early. Today we’ll install five simple levers you can run on any show—opera, MT, or a scrappy DIY—and a dashboard to spot trouble before it explodes.

Why It Matters

  • Teams with psychological safety learn faster and perform better—full stop. Systematic practices are how you keep that safety under pressure. 
  • Most groups fall into coordination neglect: everyone perfects their silo, nobody owns the seams. Fix the handoffs, not just the tasks. 
  • Faultlines (cast vs. crew, pros vs. students) split rooms into quiet camps if you don’t bridge them on purpose. Name them; cross them. 
  • Debriefs work. A meta-analysis shows they boost team effectiveness roughly 20–25% on average. Make them tiny and routine. 

The Five Levers (plug-and-play)

1) Interface Specs (the “Definition of Done” for every handoff)

For each seam—Music → Staging, Staging → SM, SM → Crew, Marketing → FOH—write a 3-line spec and tape it up:

  • Format: what the receiver gets (e.g., “PDF score v3 with cuts circled and timings,” “.xlsx prop list,” “1080p .mp4 labeled ‘Title_Take#_1m12s’”).
  • Quality bar: objective check (“button lands at 1:12 ± 2s,” “prop table photo attached”).
  • Owner & due: who delivers, by when.

Example: Music → Staging: “Mozart duet cut v3 • button 1:12 ± 2s • MD by Thu 5pm.”

This kills “I thought you had it” faster than any pep talk.

2) Integration Rehearsals (protect the seams)

Schedule short sessions where disciplines meet: tempi vs. traffic, cue lights vs. sightlines, late seating vs. blocking. Change one variable per pass, then log one decision. This is the antidote to coordination neglect. 

3) Capacity & Pace Board (keep ambition honest)

One page on the wall (or a shared doc):

  • Committed this week (realistic, not fantasy).
  • WIP limit (max three active items per person/role).
  • Slack (buffer for fixes).

If asks exceed capacity, cut scope, don’t cut sleep. (Backstage adrenaline ≠ sustainable plan.)

4) Escalation Ladder (decide without drama)

Post the ladder; use it when stuck:

  • Level 1: owners talk for 10 minutes.
  • Level 2: A/B test 2 options for 5 minutes; tie-breaker (Producer/Director) decides.
  • Level 3: defer or redesign; log the trade-off.

Close the loop with a check-back: “Received: Version B, slower button, trying at 7:10.” (Yes, closed-loop confirmations reduce misses.) 

5) Faultline Bridges (keep subgroups from hardening)

List likely splits (cast/crew, day-job/night-job, experience level). For each:

  • Bridge pair: two humans from different sides meet 10 minutes weekly.
  • Rotate first voice: vary who speaks first in notes.

This turns “we/they” into “we.” 

Early-Warning Dashboard (check daily)

  • ≥2 handoff misses today → write/clarify the Interface Spec.
  • Same note repeats 3 days → run an Integration Rehearsal.
  • Slack <10% of schedule → cut scope on the Capacity Board.
  • Two decisions >48h old → invoke Escalation Ladder.
  • “We/they” language heard → activate a Faultline Bridge.

Tools & Templates (drop these into your show folder)

A) Interface Spec (one per seam)

  • From → To:
  • Deliverable format:
  • Quality bar:
  • Owner / Due:
  • Acceptance check (how receiver confirms “done”):

B) Integration Map

HandoffRiskOwnerTest we’ll runDate
Music→StagingButton feels rushedMDA/B two tempi in run 2Thu

C) Capacity & Pace Board

Columns: Committed • In Progress (WIP 3) • Blocked • Done • Slack. Review Mondays; prune mid-week.

D) Escalation Card

“L1 owners 10’ → L2 A/B + tie-break 5’ → L3 defer/redesign. Log it.”

E) Faultline Bridges

Potential splitBridge pairFirst-voice rotationCheck-in

How to Practice (15 minutes total)

  1. Mark your seams (5’) Circle every handoff on the schedule. Write one Interface Spec for the scariest seam.
  2. Run one Integration Rehearsal (5’) Change one variable; decide one thing; log it.
  3. Capacity reality check (5’) Set WIP limits (max 3). Trim the list until the board fits humans, not heroes.

Common Implosion Patterns (and the fix)

  • Perfect solos, messy ensemble → Interface Specs + Integration Rehearsals.
  • Everyone “busy,” nothing finished → WIP limits on the Capacity Board.
  • Decisions stall → Escalation Ladder with time boxes + check-backs. 
  • Subgroups hoard info → Faultline Bridges with rotated first voice. 

Pro Tips

  • Name the risk, not the person. “Button timing unclear,” not “they’re late.”
  • Schedule the seams. Handoffs go on the calendar like scenes.
  • Debrief on rails. 5 minutes: Keep / Change / Next—then move. (The data says debriefs pay off.) 
  • Version discipline. Dates in filenames; one “current” folder; archive the rest.

Assignments (ship this week)

  1. Publish your Escalation Ladder in the rehearsal space and the company Slack.
  2. Write three Interface Specs for your riskiest handoffs; get written acceptance criteria from receivers.
  3. Schedule two Integration Rehearsals (15 minutes each) before the next full run.
  4. Stand up a Capacity & Pace Board with WIP limits and one slack block per person.

References & Further Reading

Run the levers, watch the room speed up, and keep your projects far from the detonation line.

Collaborative Mindset

by Leave a Comment

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)

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

Collaborative Rhetoric

by Leave a Comment

Day 13 Topic 3

Speak So People Can Work With You (And Want To Again)

Great collaborators don’t just sing well—they talk well. Notes, asks, emails, DMs, room resets… your words either speed the room up or sand it down. Today we turn “awesome to work with” into repeatable scripts and research-backed frameworks you can run under pressure—so you protect the art, the timeline, and the relationships.

Why It Matters

  • Psychological safety (people feel safe to risk, ask, err) is the #1 predictor of team effectiveness—Google’s Project Aristotle and Edmondson’s research both flag it. That starts with how you frame and respond in the room. 
  • Your messages should be clear, scannable, and actionable. Classic communication structures (Minto’s Pyramid/SCQA) make your asks faster to process. 
  • Feedback is a skill. SBI (Situation–Behavior–Impact) keeps it specific and humane; SBAR and closed-loop “check-backs” keep teams aligned when things move fast. 
  • Great listeners aren’t silent—they ask questions that help the other person think. (Yes, that’s research.) 

The Toolkit (use these in rehearsal, email, and chat)

1) Frame with SCQA (answer first), then details

Use when you email, text, or speak to start a decision.

  • Situation: current state
  • Complication: what’s changed / constraint
  • Question: the choice in front of us
  • Answer: your recommendation (bold/underline it), then reasons

“Call time is 6:30 (S). Piano can’t access the pit (C). Can we move warm-up? (Q) Answer: warm-up onstage at 6:10; ensemble call 6:00 to spike. I’ll post signage. (Risers in by 5:50.)”

Faster reading, faster yes’s. 

2) Deliver notes with 

SBI

 (then ask one question)

  • Situation (“In the Act I trio run…”)
  • Behavior (“you cut off the pianist’s cue on bar 9…”)
  • Impact (“the ensemble drifted and we lost the button.”)
  • Ask (optional): “What would help you hit that cue?” Clear, specific, kind. (It also de-personalizes conflict.) 

3) Brief fast with 

SBAR

 (and close the loop)

When stakes or speed are high: Situation, Background, Assessment, Recommendation—then get a check-back (“copy / repeating back”) so nothing drops.

“S: House opens in 9. B: Power dropped in the lobby. A: Lights restored, crew testing. R: Hold curtain 5. SM, confirm?”

“Confirm: holding 5.” 

4) Listen like a pro (the “trampoline” move)

Reflect back the essence, then ask a clarifier: “So you’re hearing the fermata sag because my breath resets late—did I get that right?” That combo (reflect + question) is what great listeners do. 

5) De-escalate with 

NVC micro-formula

When feelings spike, speak in four beats: Observation → Feeling → Need → Request.

“When we skip breaks (obs), I feel fried (feel). I need 5 minutes to reset (need). Could we pause after this take? (request)”

This keeps blame out and options open. 

6) Use “Yes, and…”—but not as a muzzle

“Yes, and…” invites building; don’t let it steamroll real constraints. Use it to generate options, then switch to SBAR to decide. (Even HBR notes the limits.) 

Scripts You Can Steal (Opera • MT • Directors)

Asking for a change (singer → director/MD)

“SCQA: We’re clean through Letter C; the audience sits low house right (S). The joke’s dying behind the column (C). Could we angle ⅛ out on the punchline (Q)? Rec: I’ll plant left of spike 3 so lights still catch the face (A).”

Giving a musical note (MD → singer)

“SBI: In the 2nd pass at 54, you entered ahead of the pickup; we lost the ensemble. Ask: Want a louder count-in or a hand cue?”

Resetting schedule (director → cast)

“SBAR: S: Painter delayed. B: Deck is wet. A: Unsafe to spike tonight. R: Dance call first at 6; spacing moved to 7. Please reply ‘received’ so we know you’ve got it.” (Check-backs = fewer misses.) 

Pushing back respectfully (singer → team)

“NVC: When the key changed at call, I felt anxious; I need a minute to mark the passaggio. Could we try it once at tempo with the new breath plan?”

Room Culture: Make It Safe, Fast, and Kind

  • Name the norm: “Questions beat guessing; check-backs beat silence.” You’re building psychological safety on purpose. 
  • WWWWH-before-H: Who, What, Where, When, Why—then “How.” (Frame first; tactics second.)
  • One idea per note. Don’t stack three changes on a breath.
  • Close loops. If someone asks you to do X, repeat back the X you’ll do and by when. (TeamSTEPPS calls this “closed-loop.”) 

Common Mistakes (and Fixes)

  • Vague asks. Fix: SCQA with a clear Answer up top. 
  • Personal critiques. Fix: SBI (behavior, not identity) + one question. 
  • Open-loop chaos. Fix: SBAR + check-backs for any time-sensitive change. 
  • Performative “Yes, and…” Fix: brainstorm with it, decide with SBAR. 
  • Listening = waiting to talk. Fix: reflect + question (“Did I get that right?”). 

Pro Tips

  • Pin your formats (SCQA/SBI/SBAR) to the wall of your rehearsal space.
  • Batch your notes: 3 bullets max per pass—save the rest for the next round.
  • Temper the room: A 30-second breath + water break after hard scenes gives better takes than a rushed third try.
  • Write once, reuse: Save your best emails/scripts as templates.

How to Practice (15-Minute Drills)

  1. SCQA Speed Round (5 min). Take three messy Slack/DMs you sent this month. Rewrite each as SCQA with a bold Answer line.
  2. SBI Mirror (5 min). Pair up; give one “note” each using SBI; partner paraphrases (“So you’re asking me to ___ because ___; got it?”).
  3. SBAR Hot Potato (5 min). Stage manager hands a change; cast repeats with check-back (“Received: holding 5 / moving to spike 2”). Aim for zero ambiguity. 

Assignments (Ship This Week)

  • Make a one-page “Rhetoric Card.” Top: SCQA. Middle: SBI. Bottom: SBAR + sample check-back phrases. Tape it in your case.
  • Template three emails you send a lot: (1) ask for availability, (2) notes recap after run, (3) schedule change. Use SCQA. 
  • Run one rehearsal using check-backs. Count how many fewer “Wait, what are we doing?” moments you hear. 

References & Further Reading (Topic 13.2 — Collaborative Rhetoric)

You don’t need fancier vocabulary; you need faster clarity and safer rooms. Run the formats. Close the loops. Ask one good question. Then sing the paint off the walls.

Making Collaborative Projects Work (How to Do Business with Friends and Stay Friends)

by Leave a Comment

Day 13 Topic 1

You’re a singer—and a collaborator. That means you work with pianists, directors, conductors, composers, producers, presenters, and…friends. Today we’ll turn “Let’s put on a show!” into a repeatable system: clear roles, written terms, sane timelines, and kind feedback. The goal? Ship art together and want to do it again. Work begets work!

Why it matters

  • Clarity protects friendships. Model contracts exist for a reason; drafting simple agreements early prevents “but I thought…” drama later. (Dramatists Guild offers collaboration agreements for authors and devised theater teams.) 
  • Music rights differ by context. Background/non-dramatic uses (e.g., most recitals) are covered by venue PRO licenses (ASCAP/BMI). Staged operas/musicals = grand rights you negotiate directly with the publisher (e.g., Boosey & Hawkes). Even a concert performance can trigger grand rights depending on scope. 
  • Professional cadence matters. Short, time-boxed check-ins and a simple roles matrix (RACI) keep creative projects moving without micromanagement. 
  • Psychological safety drives teams. Google’s Project Aristotle (and follow-ups) highlight psychological safety as a key factor in team effectiveness; feedback models like SBI (Situation-Behavior-Impact) keep notes specific and humane. 

Your Collaboration Playbook (step-by-step)

1) Kickoff (60 minutes, cameras on if remote)

  • Purpose & promise: What are we making and for whom?
  • Success criteria: What “shipped” looks like (date, venue, runtime, audience size/goal).
  • Roles snapshot: Who’s Responsible, Accountable, Consulted, Informed (RACI) for music, staging, marketing, money, venue, rights. (Keep this to one page.) 

2) Write it down (light-weight, friendly)

  • MOU (Memorandum of Understanding) or Collaboration Agreement covering: scope, timeline, $$, IP/recording, crediting, decision rules, exit/replace plan, dispute path. (Use an MOU template or a model collaboration agreement as a starting point.) 
  • Money splits: Flat fees first; if profit share, define recoup → split waterfall.
  • Composing/arranging? Use a split sheet to document percentage ownership (adds to 100%). 

3) Cadence & hygiene

  • Weekly 15-minute standup (What shipped? What’s next? Any blockers?). Time-box it. 
  • Shared tracker: one sheet with tasks, owners, due dates, and status colors.
  • File naming & links: one cloud folder; version with dates.

4) Rehearsal etiquette (mini-code)

  • Be early, scores marked, tempi decided. Give your pianist clean music in advance; mark cuts/fermatas; lead tempo with breath/first line. 
  • Breaks are real. Union CBAs often require rest after ~90 minutes; treat that as a humane baseline even if you’re non-union. (Specific terms vary by contract/company—see AGMA examples.) 

5) Feedback that doesn’t bruise

  • Use SBI: Situation (“in the trio run-through”), Behavior (“cut off the pianist’s cue”), Impact (“ensemble slid out of sync”). Then ask for their read. 
  • Keep notes specific, actionable, and kind. Save taste debates for after you meet the brief.

6) Rights & permissions (don’t wing it)

  • Public vs. private: If the event is public or ticketed, the venue typically needs a PRO license for non-dramatic music. 
  • Grand rights: Staged opera/musical (even “in concert” in many cases) → negotiate with the publisher. Don’t assume a PRO covers it. 
  • Public domain: PD repertoire = simpler, but verify status for your jurisdiction. (When unsure, ask a VLA.) 

7) Close the loop (post-mortem = pre-launch for next time)

  • One page: what worked, what to change, what to repeat.
  • Send “Thanks + takeaway + clip” to hosts/press/guests within 24 hours—then log contacts. Work begets work.

Minimal Docs (copy, paste, customize)

A) One-Page MOU (skeleton)

  • Parties & purpose (project name, dates, venue).
  • Scope & deliverables (runtime, forces, two deliverables each).
  • Timeline (rehearsals, tech, show).
  • Money (budget owner, expenses, recoup order, profit split %, payment dates).
  • Rights/recording (who owns video/photos; how usage is licensed).
  • Credits (exact billing; order; how to list in programs/web).
  • Decision rule (tie-break: director/producer/majority vote).
  • Exit/replace (how a collaborator can step out, notice, replacements).
  • Dispute path (cool-down → mediator → walk-away). (Use NEFA/Creative Work Fund MOU notes as a checklist; adapt to your context.) 

B) Micro-RACI (example)

TaskRACI
Rights & repertoireProducerProducerMusic DirectorAll
Rehearsal planMDDirectorPianistCast
Budget & paymentsProducerProducerAllAll
Marketing/pressMarketing LeadProducerDirectorCast
Recording/photographyProducerProducerDirectorAll
(R=does the work, A=decision owner, C=consulted, I=informed) 

C) Split Sheet (for co-writing/arranging)

  • Work title, collaborators, emails.
  • Writer % totals = 100%.
  • Publishing share (if any).
  • Signatures & date. (Use ASCAP/Songtrust templates as references.) 

Not legal advice. When stakes rise, run your doc past Volunteer Lawyers for the Arts or a local arts attorney. 

Common mistakes (and fixes)

  • Handshakes only. Fix: a one-page MOU with dates, dollars, and decision rules. 
  • Fuzzy roles. Fix: 5-row RACI so everyone knows who decides and who executes. 
  • Avoided feedback. Fix: SBI once per rehearsal block; keep it behavior-based. 
  • Rights blind spots. Fix: PROs for non-dramatic uses; publishers for opera/musical grand rights (often even “in concert”). 
  • Rehearsal fatigue. Fix: Protect breaks (aim for ≤90 minutes without one, mirroring union norms). 

Pro tips

  • Decide the tie-breaker on day one. “Producer breaks ties after hearing Director/MD.”
  • Name the show. A title makes marketing, files, and grants easier.
  • Track goodwill. Note who helped; send thanks + tag them in the recap.
  • License photos & video. Put it in the MOU (credit line, where/how you may post).
  • Quarterly collaborator list. Keep a living doc of pianists, venues, videographers, and directors who were great to work with.

Assignments (ship this week)

  1. Host a 45-minute kickoff for your next DIY program. Fill the one-page MOU and micro-RACI.
  2. Schedule 3 weekly 15-minute standups between now and the show; put them on calendars now. 
  3. Create & sign a split sheet if anyone is arranging/composing with you. 
  4. Rights check: confirm PD or request a quote from the publisher if grand rights apply. 

References & Further Reading (Topic 13.1 — Collaboration)

Model agreements & MOUs

Rights & licensing

Team habits

Rehearsal etiquette & norms

Artist-support organizations

Start with kindness and clarity. Put the deal in writing, protect the rehearsal room, and give feedback like a pro. That’s how you build ensembles that like working together—and keep calling you back.