# Readers Theatre

Participants take assigned speaking roles to read a short script aloud using vocal expression instead of memorization, costumes, or staging. The group then analyzes the themes, dynamics, or process reflected in the text.

**Time:** 25 minutes. UWT suggested 25-minute duration; source lists medium time band without fixed minute breakdowns.
**People:** 4 to 24. Parallel reading groups of 4 to 6 people, or one cast reading while the rest observe as audience.

## Choose this exercise

**Purpose:** Perform an expressive cold read of a shared text to examine workplace themes or team dynamics without stage production.
**Use it when:** Use during a training session or team workshop when exploring interpersonal dynamics, communication habits, or historical scenarios through low-pressure role reading.
**Skip it when:** Skip when participants are uncomfortable reading aloud in front of peers, when English literacy levels vary sharply, or when the team needs to draft concrete action plans immediately.

## Materials and tools

- One printed copy of the selected script per participant
- Highlighter pens for marking individual speaking parts
- Chairs arranged in a semi-circle or small circles

## Before participants arrive

1. Select a 2 to 3 page script with 4 to 6 speaking parts. If using the provided sample script, print enough copies for every participant.
2. Arrange room chairs into reading circles or a front line facing an audience area.
3. Place highlighters and script copies on chairs before the session begins.

## Say this to open

Today we are doing Readers Theatre. There is no stage blocking, memorization, or costume work. Our focus is purely vocal expression. Each person reads their assigned lines directly from the script. If you prefer not to read aloud today, you can serve as the stage manager or observe as an active audience member.

## How to run it

### 1. Introduce format and assign roles (4 minutes)

Explain the mechanics using the opening script. Divide groups into 4 to 6 members each. Distribute scripts. Ask each group to divide the speaking roles. Ensure anyone who prefers not to read takes the stage directions role or acts as an observer.

### 2. Highlight and silent review (4 minutes)

Give participants 4 minutes to silently read the piece and highlight their assigned character's dialogue. Encourage them to note tone cues, emotional shifts, and speaking pace.

### 3. Vocal read-through (10 minutes)

Groups perform their read-through concurrently in separate corners, or one designated group reads while others listen. Readers speak clearly using vocal variety, volume, and pacing to convey meaning without standing or moving around.

### 4. Debrief and analysis (7 minutes)

Bring the full room together. Facilitate a discussion using the debrief questions. Take 2 or 3 participant comments per prompt.


## Debrief questions

- Which character dynamics or tensions stood out most during the vocal reading?
- How did vocal pacing and tone change the way you interpreted the dialogue compared to silent reading?
- What parallels do you see between the interactions in the script and our actual working rhythms?

**Finished output:** A completed vocal reading of a dramatic or comedic scene followed by shared observations on communication dynamics.

## Remote

Distribute digital script PDFs or shared document links beforehand. Form breakout rooms of 4 to 6 participants. Each participant assigns a role and highlights their lines in their digital copy. Characters unmute and read aloud while keeping cameras on for facial expression. Return to the main room for debriefing via voice and chat.

## Hybrid

Pair in-person readers together in a physical circle with microphones or place remote members into all-remote breakout rooms. For a whole-room performance, seat in-person readers facing the room camera and assign one or two virtual readers distinct parts on the conference room audio.

## Access and participation choices

- Provide large-print copies or send scripts in advance for screen reader use.
- Offer non-speaking roles such as Stage Direction reader, timekeeper, or active observer without requiring explanation.

## If the session gets stuck

**A participant reads very quietly or stumbles over text.**

Remind the room before starting that this is an informal cold read, not an audition. Advise readers to take pauses freely.

**A group has fewer members than speaking roles.**

Assign non-overlapping characters to a single reader as noted in source guidance, or omit minor narrator lines.


## Terms used here

- Cold Read: Reading a script aloud with little or no advance rehearsal.
- Blocking: The precise physical movement and positioning of actors on a stage.

## Participant material: Sample Script: The Project Handover

CHARACTERS:
- JORDAN: Project Manager, anxious about schedule.
- SAM: Lead Developer, focused on technical stability.
- MORGAN: Client Lead, focused on user requirements.
- NARRATOR: Reads scene context and stage directions.

[SCENE START]

NARRATOR: Tuesday morning, conference room B. Jordan stands by a whiteboard filled with crossed-out dates. Sam sips coffee, staring at a laptop. Morgan enters with a thick binder.

MORGAN: I reviewed the draft specifications. We need three additions before launch next Friday.

JORDAN: Friday? Morgan, we agreed Friday was our freeze date. Nothing new goes in after tomorrow noon.

SAM: (Without looking up) If we touch the database schema now, the migration will break. Friday launch is a non-starter if you add those three items.

MORGAN: The client demo is next Tuesday. Showing a platform without account exports will lose the account.

JORDAN: (Takes a breath) Let's stop. Sam, what happens if we build exports as a standalone script instead of integrating it into the core UI?

SAM: It is still messy, but it isolates the risk. We would need four extra hours of testing on Thursday.

MORGAN: Can users run it?

SAM: It will work, but it will not look pretty.

JORDAN: Then here is the trade-off. We ship the core system on Friday, run exports manually for Tuesday demo, and release the polished UI next sprint. Can we all stand behind that?

NARRATOR: A long pause. Morgan closes the binder. Sam taps three keys on the keyboard.

MORGAN: Agreed, provided I get the test output by Thursday at five.

SAM: Deal. Do not send me any new feature requests before then.

[SCENE END]

## Sources and adaptation

Observed in Teampedia as Readers Theatre, a community theatrical reading format adapted for team building, reflection, and educational discussions.

Retained core Readers Theatre mechanic from Teampedia: reading from scripts using voice alone without costumes, sets, or blocking; accommodating smaller groups by doubling non-overlapping roles; structured debrief on themes and process. UWT provided a 25-minute timing structure, concrete parallel group rules, non-speaking support roles, and an original sample script for workplace teams.

[Teampedia](https://www.teampedia.net/wiki/Readers_Theatre)

Current run sheet: https://unitedwetransform.com/exercises/readers-theatre/