The intro chapter recovered the storytelling vocabulary. The boundary-conditions chapter established what an operation is as a unit and named the input script boundary condition that governs what the participant performs against. This chapter establishes the foundation that boundary condition rests on. Before any orchestrator can author what a participant will perform against, the orchestrator has to decide what the participants are assumed to already know. The decision is the baseline of mutual understanding. When the baseline is held honestly, the work flows. When the baseline is held dishonestly — when the orchestrator assumes the participants know things they have not been told — the work breaks down, and the breakdown is the orchestrator's failure.
Where Orchestration Begins
A grade school teacher is running a group project. Four students per group. Each group is to research a country, assemble a poster about it, and present what they learned to the class on Friday. The teacher has explained the project to the class and given each student an assignment sheet to take home. The sheet says what the project is, when it is due, what it has to include, and how the groups will be graded. The teacher has assigned the groups and named one student in each group as the leader. During the week, the teacher walks among the groups during class time, listens to what they are working on, and steps in when one group is going off track or when two students are stuck. On Friday, each group presents in turn. The teacher asks questions, the class asks questions, and the groups submit their posters for grading.
A home improvement store instructor is running a Saturday morning class on installing ceramic floor tile. Twelve homeowners have signed up, all of them thinking about tiling a bathroom or kitchen floor themselves and have come to learn how. The instructor knows that none of them have done this work before. The instructor has prepared a printed handout that goes to every homeowner when they arrive, covering the steps of a basic tile installation from start to finish. The instructor has prepared a demonstration to do at the front of the room on a sample subfloor, showing each step as the homeowners follow along on their handouts. The instructor has set up six work stations around the room, each with its own small mock-up subfloor, a bag of tile, a bucket, a notched trowel, spacers, and a sponge. After the demonstration, the homeowners will pair up at the stations and try the steps themselves. The instructor has an assistant who moves between the stations during the hands-on portion, helping anyone who is stuck and answering questions. The instructor's job during the hands-on portion is to watch the room, step in where the assistant signals that a station needs more help, and bring everyone back together at the end to talk about what they did and what they will need to think about when they try this in their own homes. By the end of the morning, every homeowner has laid a small section of tile, has held the tools, and has a handout they can take home that walks through the steps in the order they just practiced.
A volunteer coordinator is running a disaster-recovery effort. A flood has hit the town. Hundreds of volunteers have arrived from across the region wanting to help. The coordinator has set up a staging area in the parking lot of the high school, where volunteers sign in, get assigned to a team, and receive a briefing for the work their team is doing that day. Some teams are clearing debris from yards. Some are tearing out wet drywall in flooded houses. Some are running supplies between the staging area and the worksites. Each briefing tells the team where they are going, what they are doing when they get there, what tools and supplies have been provided, who their team leader is, and what to do if something unexpected comes up. Throughout the day, team leaders radio status back to the staging area. The coordinator watches what is coming in, redirects teams when conditions change, and handles the requests that the team leaders cannot resolve on their own. By the end of the day, the worksites are in a better state than they were that morning, and the coordinator notes what happened so tomorrow's effort can build on what was learned.
Three pictures, three settings. A classroom, teaching a new skill/trade, a disaster site. Students, homeowners, volunteers. A school week, a Saturday morning, a single day after a flood. In each case, one person has taken responsibility for the larger goal, has decided how the work needs to be divided, has given instructions to the people who will do each part, and has stayed available to handle what comes up while the work is in progress. In each case, the people doing the work are different from each other and have not been working together long enough to develop their own private way of communicating. In each case, the orchestrator's instructions are how the work gets coordinated. The instructions are the medium that holds the effort together.
This is what orchestration is, in any setting where coordinated work happens. Someone has to give the instructions. Someone has to receive them and act on them. The instructions have to be clear enough for the receivers to act on without the orchestrator being there to clarify every step. The orchestrator's job is to make sure the instructions actually do that work.
A reader who has not led a team in any formal sense has still done this work. Anyone who has asked another person for help has orchestrated a group of one. Anyone who has been part of a group where a floor needed sweeping and there was only one broom has watched orchestration happen in real time — someone notices that three people standing around while one person sweeps is wasted effort, and improvises something. One person grabs a dustpan, another starts moving chairs, another takes the trash out. Nobody appointed an orchestrator. The inefficiency was visible, and the group rearranged itself. This happens constantly in everyday life, and it almost never gets named as orchestration, because the discipline is operating below the surface where people would think to call it that.
The medium that carries the communication is not what the orchestration depends on. The teacher explains the project out loud and sends home a sheet with the details. The tile instructor talks through each step at the front of the room while the homeowners follow along on a printed handout. The volunteer coordinator gives a briefing at the staging area and the team carries printed instructions with them to the worksite. The principle holds when the participants are nowhere near the orchestrator and the communication has to travel to reach them. A dispatcher gives a responder their assignment over a two-way radio. A site supervisor sends the day's punch list to the crew by text message. A manager walks a remote employee through a project on the phone. A regulator publishes new compliance requirements by email to every affected company. The form varies with the setting, the participants, and what serves the work. What does not vary is that the participants take in what the orchestrator authored and form their understanding from it. The input script is what the orchestrator authored. The medium is only what carried it.
Baseline of Mutual Understanding
Before any of the three orchestrators can give a single instruction, they have to make a judgment about who they are giving instructions to. They have to estimate what the participants receiving the instructions can reasonably be expected to know. That estimate is the baseline of mutual understanding. It is the line below which the orchestrator explains things and above which the orchestrator does not.
The teacher's baseline is what a sixth-grader in the class knows: students who can follow instructions at a particular level, who have done group work and presentations before in this classroom, but who have not yet been taught how to research a country independently. The tile instructor's baseline is what an adult homeowner with no prior tile experience knows: people who can follow instructions, can read a tape measure, and have walked across tile floors, but who have never held a notched trowel and do not know what thin-set is. The volunteer coordinator's baseline is the lowest of the three: any adult who can follow instructions in English, with no shared training, no shared vocabulary, and no prior experience of disaster work assumed. Three different baselines, calibrated to three different sets of participants, each chosen deliberately by the orchestrator who set it.
The orchestrator does not know with certainty what the participants in front of them know. The orchestrator makes an informed estimate of what people in this position can reasonably be expected to know, sets the baseline at that estimate, and gives instructions calibrated to it. When the estimate is good — when the typical participant in this position does in fact know what the orchestrator expected — the instructions have the highest probability of being understood by the participants who receive them. They take in the instructions, recognize what is being asked, and act. The orchestrator is not reading minds. The orchestrator is making the best estimate available about the kind of person the instructions are being given to.
When the estimate is off — when the orchestrator has set the baseline higher than the participants actually meet, or has assumed something a typical participant in this position would not actually know — the instructions do not land. The participants encounter something they do not understand, and either guess at what was meant, or stop and ask for clarification, or proceed without understanding and do the wrong thing. The gap is between what the orchestrator estimated and the participants' ability to understand. The orchestrator put the gap there by setting the baseline above what a typical participant could meet.
The breakdown is the orchestrator's failure. If the teacher's assignment uses a term the students have not been taught, the projects come back worse than they could have been, and the failure is the teacher's. If the tile instructor's instructions use a word like thin-set without explaining it, the homeowners get stuck or guess wrong, and the failure is the instructor's. If the coordinator's briefing assumes the volunteers know how to handle something they have never encountered before, the work goes badly or someone gets hurt, and the failure is the coordinator's. In every case the orchestrator estimated higher than the actual participants could meet, and the orchestrator owns that the estimate was off. The blame for breakdowns of communication runs upward, toward the one who gave the instructions, not downward toward the people trying to act on them.
This principle is not the orchestrator's burden alone. It is the orchestrator's discipline. Working orchestrators understand it. The teacher who has been teaching sixth-graders for ten years has internalized the calibration to the point where it does not require conscious thought most of the time. The tile instructor who has run this Saturday morning class many times knows where homeowners get confused and addresses those points before they hit them. The volunteer coordinator who has run disaster recoveries before knows that volunteers arrive without shared training and gives instructions accordingly. The discipline becomes second nature with practice. What the principle names is the standard the practice is held to. An orchestrator who has not yet developed the discipline can still hold themselves to the standard by attending to the baseline deliberately, the way an experienced orchestrator attends to it instinctively.
The principle also names what fails when communication breaks down. Communication does not break down because the participants were not paying attention, or were not motivated, or did not care. Most of the time, communication breaks down because the orchestrator's estimate of what the participants knew was higher than what they actually knew. The orchestrator's first move when something has gone wrong is not to ask what the participants did. It is to ask where the estimate missed — what the orchestrator expected the participants to know that they turned out not to know. The answer to that question is almost always where the breakdown started.
Including Prerequisite Context in Input Scripts
The boundary-conditions chapter established what an input script is and what it can contain. Among the things an input script can contain is context — the background information the participant needs in order to do the work. This is where the baseline of mutual understanding becomes practical. The orchestrator who has chosen a baseline below what the instructions actually require has to make up the difference somewhere. The place where the difference gets made up is the context section of the input script.
The teacher's assignment for the group project does not just say “research a country and make a poster.” It tells the students where in the library to look. It describes what good engagement with a country looks like — not just the basic facts, but something interesting the group found out and wants the class to know. It includes a picture of a strong project from a previous year so the students have a sense of what the work can look like. It names the standards the presentation will be judged against. The assignment is mostly context; the actual instruction is short. The context around the instruction is what makes the instruction possible to act on at the baseline the teacher has chosen.
The tile instructor's handout does not just say “install the tile.” It identifies each tool and what it is for. It explains what thin-set is and how to tell when it is mixed to the right consistency. It walks through how to plan the layout, spread the thin-set, set the tile, and use spacers. It says what to do when a tile cracks or a measurement turns out wrong. The handout is mostly context; the actual instruction is short. The context around the instruction is what makes the instruction possible to act on at the baseline the instructor has chosen.
The volunteer coordinator's briefing for the drywall removal team is mostly context. The team is going to a specific address. The briefing explains how to get there, what the homeowners have asked the team to be careful about, how to tell wet drywall from drywall that can stay, and how to check for live electrical before opening up a wall. It tells the team that they will encounter situations the briefing did not anticipate, that they are trusted to use their judgment, and that calling the staging area for help is always the right move when they are unsure. The instruction itself is short: remove the wet drywall, take care of the people who live there, call if you need us. The briefing is almost entirely context, because the baseline the coordinator chose is so low that almost everything about the work has to be explained.
The pattern across the three is consistent. The lower the baseline, the more context the input script has to carry. The higher the baseline, the less context is needed, because more of what the participant needs to know is already in them when they receive the script. The orchestrator who chooses a low baseline accepts the work of including more context. The orchestrator who chooses a high baseline accepts the consequence that the script will only work for participants who actually meet the higher baseline. Either choice is legitimate, depending on who the participants are. What is not legitimate is choosing a high baseline and then handing the script to participants who do not actually meet it. That is the move that produces breakdowns of communication, and the orchestrator who made that move owns the breakdown.
This is how input scripts hold up across the range of participants the orchestrator might hand them to. A script that includes its own prerequisite context can be acted on by anyone who meets the baseline the script declared. A script that depends on assumptions the orchestrator never made explicit can only be acted on by participants who happen to share the orchestrator's unspoken assumptions. The first kind of script travels. The second kind only works in the orchestrator's own head and breaks down anywhere outside it.
The Foundation
The baseline of mutual understanding is the foundation. Without it, no orchestration works — not in classrooms, not in skill or trade classes, not at disaster sites, not anywhere coordinated work happens. With it held honestly, orchestration can scale from a teacher with twenty-eight students to a coordinator with hundreds of volunteers to anything larger than that. The principle does not change with scale. The orchestrator's responsibility for the baseline is the same in every case.
The foundation has a name. The participants share a protocol, and the protocol is human language. The protocol is what every input script is written in, and what every participant in coordinated work has been honoring whether or not the honoring was ever named.
The series itself is an input script for its readers, and it has been authored under the principle the chapter has now named. The series declared its baseline at the start: someone who has led coordinated work in any setting — a manager, a coach, a teacher, a coordinator, a parent, a director, an instructor, anyone responsible for instructions that other people act on. The series assumes that baseline and operates within it. The patient build-up of concepts across the chapters, the working through of examples before the abstractions are named, the careful definition of terms the framework depends on — these are the prerequisite context the series carries with it, the same context section a teacher's assignment or a tile instructor's handout or a volunteer coordinator's briefing carries with it, sized to the baseline the script declared. Anywhere the series has slipped above the baseline is a failure the authors own, and the reader is invited to catch it.