Museums are highly collaborative organizations. Exhibits, programs, special projects, and institutional initiatives often require input from several departments, outside experts, volunteers, or community partners. Somewhere along the way, however, almost every one of these groups seems to become a committee. An exhibit is being developed, so an exhibit committee is created. A new program is under consideration, so a program committee forms. A project encounters a problem, and a committee is assembled to resolve it.
In many cases, the group is not really functioning as a committee at all. It may be a project team, working group, task force, or planning group. The distinction can seem minor, but within a nonprofit organization, terminology often communicates authority, responsibility, and accountability. Museum professionals should be more deliberate about the words we use to describe the groups we create.
A committee is more than a group of people appointed by someone in authority. It is a recognized body within the organization, created for a defined area of responsibility and given an established role in the institution’s governance or operations. Its purpose, membership, responsibilities, reporting relationship, and authority should be clear, and its work is generally documented through minutes, reports, or other institutional records. Those expectations may be established through bylaws, policy, a committee charter, written guidelines, or another formal directive.
This is most obvious at the Board level. Board committees are generally established to address defined areas of governance responsibility and to assist the Board in carrying out its work. They often have designated membership, written charges or charters, reporting expectations, and clear limits on what they may decide or recommend.
Committees can also exist within an organization’s internal operating structure, but the same principle applies. A museum might maintain a Safety Committee, Emergency Preparedness Committee, or another standing body responsible for a continuing institutional function. In those cases, the group exists because the organization has intentionally created it as part of its structure, not simply because several employees were asked to work together.
That distinction matters because the act of assigning people to a task does not by itself make the group a committee. If a CEO asks several staff members to develop a new program, review an exhibit concept, or solve a temporary problem, the group may be important and may even meet regularly, but it is more likely functioning as a project team, working group, or task force.
One of the clearest examples is a phrase heard frequently in organizations: “The committee decided.” That statement immediately raises an important question: did the group actually have the authority to decide?
A group may have been assembled to research an issue, develop options, coordinate work, or make recommendations. Those responsibilities do not necessarily include final decision-making authority. When an informal group is casually labeled a committee, the distinction between recommendation and approval can become less clear. This becomes especially important in museums, where decisions may involve collections, finances, institutional policy, public programming, major expenditures, or other areas in which authority has already been assigned through governance documents, policies, or the organizational structure.
The problem is not simply one of wording. If the name of a group implies more authority than it actually possesses, staff and other participants may be unclear about where decisions belong. A recommendation can begin to sound like an approval, or a collaborative discussion can be treated as though it produced an institutional decision.
Exhibitions provide a useful example because they require extensive collaboration. A museum developing an exhibition may bring together staff from Curatorial, Collections, Education, Exhibits, Marketing, Development, and other areas. The group may meet regularly for months and make countless decisions about content, interpretation, design, objects, schedules, and visitor experience.
None of that automatically makes the group a committee. In many museums, “exhibit project team” would be a more accurate description because the group exists to complete a defined project, has assigned responsibilities and a timeline, and may dissolve when the exhibition is complete.
A formal Exhibitions Committee would be something different. It might have an ongoing institutional role in reviewing proposals, setting priorities, establishing standards, or making recommendations to leadership or the Board. Its responsibility would extend beyond one exhibition and would be recognized within the museum’s organizational structure.
Both structures can be useful. The issue is not which one sounds more important, but which one accurately describes the work being done and the authority the group has been given.
Museums have other terms available when a formal committee is unnecessary. A task force is generally temporary and created to address a specific issue. A working group may research a problem, develop procedures, or prepare recommendations. A project team is usually organized around defined deliverables and a timeline, while an advisory group provides expertise or perspective without necessarily holding decision-making authority.
These terms do not diminish the importance of the work. In many cases, they make the role of the group easier to understand. Part of the reason organizations default to the word committee may be that it sounds established and official. A planning committee can seem more substantial than a planning group, and a project committee may sound more authoritative than a project team.
But legitimacy should come from the structure behind the work, not from the title placed on the group. If a group has no clearly defined purpose, membership, reporting relationship, or authority, calling it a committee does not make the organization more formal. It may simply create confusion about what the group is expected to do and where its responsibilities begin and end.
Museums often have several layers of responsibility operating at the same time. Boards govern, executive leadership manages, department heads oversee operational areas, and professional staff exercise authority within their fields of responsibility. Volunteers, consultants, advisers, donors, and outside partners may also contribute to institutional work without having formal decision-making authority.
Collections work can add another layer, with formal Collections Committees, accession and deaccession procedures, loan approvals, and Board responsibilities established through policy. Within that environment, loosely creating additional “committees” can make reporting relationships more difficult to understand. Recommendations may be mistaken for approvals, staff may be uncertain about who has the final say, and participants may assume a level of authority the institution never intended to give them.
When a museum brings people together to work on an issue, the first question does not need to be, “Who should be on the committee?” A better question is what kind of group the institution actually needs and what role that group is expected to play.
If the work is temporary, project-based, advisory, or focused on developing recommendations, there may be a more accurate term. If the organization truly intends to establish a committee, then its purpose, membership, authority, reporting relationship, and documentation should be clearly defined from the beginning.
Museum professionals spend considerable time developing policies, procedures, organizational charts, and governance documents to establish responsibility. We should bring the same care to the language we use when creating groups within our institutions. Not every group needs to be a committee. Sometimes it simply needs a clear purpose, the right people, and a name that accurately describes what they have been asked to do.
Originally published on LinkedIn on August 7, 2026. Read the original article on LinkedIn.
Related insights: The Systems Beneath the Work · Good Organizations Do Not Run on Memory
