Who Decides What? A Practical Decision-Rights Framework for Arts Programs

Strong arts programs do not usually break down because people lack talent, commitment, or ideas. They break down when responsibility, authority, and communication are misaligned. A teacher thinks a coordinator is making the decision. A coordinator believes the director has already approved it. A director assumes a campus administrator owns the operational call. Everyone is working, but the system has never made clear who decides what.

For arts leaders, this becomes especially visible because the work crosses instructional leadership, performances, exhibitions, facilities, budgets, student pathways, communications, partnerships, and campus operations. The solution is not more meetings. The solution is clearer decision rights.

Decision rights are different from job descriptions

A job description tells people the territory of a role. Decision rights tell them what happens when actual work moves through that territory. Who can decide? Who must be consulted? Who executes? Who needs to know? Who can stop the process when safety, policy, budget, or instructional quality is at risk?

This distinction matters in arts organizations because many decisions are shared by design. A theatre teacher may own artistic choices, while a coordinator owns event logistics, a director owns program standards, and a principal owns campus operations. None of those roles is inherently in conflict. Conflict appears when the handoff between them is undefined.

A five-part decision model for arts programs

I use five questions to make recurring work visible: What is the decision? Who recommends? Who decides? Who executes? Who must be informed? This is intentionally simpler than building a large responsibility matrix for every task. The goal is to create enough structure that people can act without repeatedly renegotiating authority.

1. Define the decision, not just the activity

“Plan the concert” is an activity. It contains several decisions: repertoire, student participation, date, venue, technical needs, budget, audience communication, ticketing, supervision, and final approval. If the team treats all of that as one task, ownership becomes muddy. Break recurring work into the decisions that actually require judgment.

2. Separate recommendation from approval

The person closest to the work should often make the recommendation. That does not mean the same person holds final approval. A teacher may recommend an event date based on the instructional sequence. A coordinator may check conflicts and logistics. A director may confirm alignment with the broader arts calendar. Campus administration may approve use of the facility. The process respects expertise without pretending every role has the same authority.

3. Give execution a named owner

Once a decision is made, one person needs to own movement. “The department” is not an owner. “Arts team” is not an owner. Naming the execution owner does not mean that person performs every task. It means that person is accountable for seeing the workflow through, delegating pieces, identifying blockers, and closing the loop.

4. Build communication into the workflow

Communication should not depend on someone remembering who might care. Define the notification points. For example: after an event is approved, the coordinator receives the operational handoff; facilities receives confirmed requirements; communications receives the public information; teachers receive student-impact information; leadership receives exceptions or unresolved risks. The communication pathway becomes part of the system rather than an act of courtesy.

5. Create an escalation rule

Healthy systems make room for disagreement without turning every disagreement into a political event. Establish what gets escalated and why. Safety concerns, policy conflicts, unapproved spending, significant calendar disruption, student access issues, and decisions outside a role’s authority should have a clear escalation path. Preference alone usually should not.

What this looks like in practice

Consider a school arts festival. The artistic team proposes the program and student participation. The coordinator owns the production timeline and cross-campus logistics. The arts director confirms program alignment, resource priorities, and system-wide conflicts. Campus administration approves site-specific operational conditions. Facilities owns physical readiness within its scope. Communications publishes only after the event information is confirmed. Each role contributes, but the team no longer has to guess where one role ends and another begins.

The same model can be used for auditions, exhibitions, guest artists, field trips, equipment purchases, curriculum changes, performance approvals, fundraising requests, and partnerships. The specific decision-maker may change. The architecture does not.

A 15-minute protocol for your next team meeting

Choose one recurring process that causes friction. Write the process at the top of a page. Under it, list the five to eight decisions embedded in that process. For each decision, name the recommender, final decision-maker, execution owner, and people who must be informed. Then identify the one condition that would trigger escalation. Do not solve every possible exception. Build the normal pathway first.

If the exercise produces three people who all believe they are the final decision-maker, you have found a governance problem. If nobody owns execution, you have found an accountability gap. If everyone must be consulted on everything, you have found a speed problem. If people learn about decisions only after implementation, you have found a communication-design problem.

Clarity is not control

Arts educators are rightly protective of professional judgment and creative autonomy. Clear decision rights should protect that autonomy, not flatten it. The purpose is to keep operational ambiguity from consuming the time and trust that should be spent on students, instruction, and creative work.

A strong arts leadership system makes it possible to answer a simple question at any point in a project: Who owns the next decision? When that answer is visible, teams spend less energy interpreting roles and more energy doing the work those roles were created to support.