Collaboration vs. Cooperation in Toxic Workplaces: How Siloed Departments Block Shared Work

In academic libraries and higher education, the words collaboration and cooperation are often used interchangeably. On the surface, both suggest that people are working together. But in toxic workplaces, especially those marked by siloed units, strained relationships, unclear authority, or uneven workloads, the difference between the two matters deeply.

Cooperation is often transactional. One department provides information when asked. A colleague attends a meeting but does not engage. A unit agrees not to interfere with another unit’s work. People remain polite, responsive, and technically helpful, but the work stays divided. Cooperation can keep the institution functioning, but it does not necessarily build trust, shared ownership, or meaningful change.

Collaboration asks for more. It requires shared purpose, mutual accountability, transparency, and a willingness to shape the work together. Collaboration is not simply being in the same room or copying another department on an email. It is the practice of building something together that no single person, unit, or department could create as effectively alone.

But here is the important distinction: collaboration is not possible when one unit refuses to cooperate.

Cooperation is not the same as collaboration, but it is the minimum condition that makes collaboration possible. If one department withholds information, ignores communication, blocks access, delays decisions, refuses to clarify responsibilities, or does not participate in good faith, then the problem is not simply that the workplace needs “better collaboration.” The problem is that the organization lacks the accountability required for even basic cooperation.

In healthy organizations, cooperation and collaboration can coexist. Cooperation helps with logistics. Collaboration drives innovation. But in toxic workplaces, cooperation is often mistaken for collaboration because it feels safer. People share just enough information to avoid conflict. Departments protect their territory. Leaders praise “teamwork” while rewarding individual control. Employees learn that staying in their lane is less risky than crossing boundaries to solve shared problems.

The result is a workplace where everyone is busy, but few people are truly working together.

How Siloed Units Confuse Cooperation with Collaboration

Silos often develop when departments or units are under-resourced, overextended, or operating in survival mode. People become protective of their time, authority, information, and expertise. This is understandable, especially in workplaces where trust has been damaged.

In these environments, cooperation may look like responding to requests but not helping shape the project, sharing data without discussing what the data means, attending meetings without participating in decision-making, completing assigned tasks without understanding the larger purpose, avoiding disagreement to maintain surface-level peace, or saying “yes” publicly while withholding support privately.

These behaviors may keep work moving, but they do not create shared investment. They can also reinforce inequity. In many academic libraries, collaborative work often falls on the same people: those who are relationally skilled, newer to the organization, committed to student success, or already carrying invisible labor connected to diversity, equity, inclusion, mentoring, or emotional support.

When organizations confuse cooperation with collaboration, they may celebrate the appearance of teamwork while ignoring the unequal labor required to sustain it.

Collaboration Cannot Happen Without Basic Cooperation

It is important to be honest about one uncomfortable reality: collaboration is not possible when one unit refuses to cooperate.

A workplace cannot move toward shared purpose, mutual accountability, or collective problem-solving if one department withholds information, ignores communication, blocks access, delays decisions, or refuses to participate in good faith.

In toxic workplaces, leaders often respond to this breakdown by asking everyone to “collaborate better.” But this framing can unintentionally place responsibility on the people who are already trying to make the work succeed. If one unit is consistently responsive, transparent, and solutions-oriented while another unit refuses even basic cooperation, the problem is not a lack of collaboration. The problem is a lack of accountability.

This distinction matters because collaborative language can be misused to obscure obstruction. A unit that refuses to answer emails, share needed data, attend planning meetings, clarify processes, or honor agreed-upon timelines is not simply “working differently.” It is preventing the conditions necessary for shared work.

In these situations, the goal should not be to force collaboration. The first goal should be to restore basic cooperation.

That means naming minimum expectations: timely communication, access to necessary information, clarity about roles and responsibilities, participation in required decisions, respect for agreed-upon timelines, transparency about constraints, and accountability when inaction harms students, faculty, staff, or institutional goals.

Only after those expectations are met can deeper collaboration become possible.

This is especially important in siloed academic workplaces, where one unit’s refusal to cooperate can create cascading harm. Students may receive inconsistent support. Faculty may be sent from office to office. Library workers may be expected to compensate for another department’s lack of communication. Staff morale may decline because the burden of “being collaborative” falls disproportionately on those who are already acting in good faith.

A solutions-oriented approach begins by refusing to romanticize collaboration. Collaboration is not a personality trait, a committee assignment, or a slogan in a strategic plan. It is a working relationship built on trust, reciprocity, and shared responsibility. When reciprocity is absent, leaders must first address the cooperation problem.

The question should not be, “How can we make everyone collaborate?”

The better question is, “What basic cooperative behaviors are required for this work to move forward, and who is responsible for ensuring they happen?”

This shift protects employees from being blamed for a broken process they did not create. It also helps organizations move from vague appeals to teamwork toward concrete expectations for professional conduct.

When “No” Becomes a Form of Control

One of the more complicated dynamics in siloed workplaces occurs when a unit leader is conflict-averse, fearful, or uncomfortable with ambiguity. In these situations, the leader may say “no” not because the request is unreasonable, but because “no” gives them a sense of control.

This kind of refusal can be difficult to address because it may not appear openly hostile. The person may frame their resistance as caution, process, workload management, policy compliance, or concern for quality. Sometimes those concerns are legitimate. But when every request becomes too risky, every shared project becomes too complicated, and every decision is delayed or blocked, “no” stops being a boundary and becomes a barrier.

Fear-based refusal often shows up in predictable ways. A unit head may decline participation before fully understanding the request. They may ask for more information repeatedly without moving toward a decision. They may avoid meetings where disagreement might occur. They may insist that their unit cannot participate unless they control the entire process. They may say they support collaboration in theory, but reject every practical step that would make collaboration possible.

In these cases, it is important to separate the emotion from the impact. The fear may be understandable, but the organizational impact still needs to be addressed.

A solutions-oriented response begins with curiosity, but it cannot end there. Leaders and colleagues can ask: What concern is driving the “no”? What risk does this person believe they are avoiding? What information, structure, or support would make participation feel possible? Is the refusal connected to workload, authority, trust, past harm, or fear of accountability?

These questions can create space for a more honest conversation. But if the answer remains “no” without a clear reason, timeline, alternative, or path forward, the issue becomes one of accountability.

A helpful distinction is the difference between a grounded “no” and a controlling “no.”

A grounded “no” explains the reason, names the constraint, and offers an alternative when possible. For example: “We cannot take this on this month because of staffing shortages, but we can revisit it in March,” or “We cannot manage the whole project, but we can provide the data and review the final language.”

A controlling “no” shuts down the conversation without creating a path forward. It may sound like: “That will not work,” “We do not do that,” “This is not our responsibility,” or “I am not comfortable with that,” without further explanation, compromise, or accountability.

The goal is not to punish people for being cautious. The goal is to prevent fear from becoming a veto over shared institutional work.

When a unit head uses “no” to control the situation, the response should shift from persuasion to clarity. Instead of trying endlessly to convince them, leaders can ask for specific conditions:

“What would need to be true for your unit to participate?”

“What part of this request is not possible?”

“Is your concern about capacity, authority, timing, policy, or risk?”

“What alternative do you propose that still meets the institutional need?”

“What decision can we make today, and what decision needs to be escalated?”

These questions move the conversation away from personality and toward responsibility. They also make it harder for avoidance to hide behind vague refusal.

If the refusal continues, documentation becomes important. Not as a weapon, but as a way to clarify the pattern. What was requested? Why was it needed? What answer was given? What impact did the refusal have on students, faculty, staff, or institutional goals? What alternatives were offered?

In toxic workplaces, the most cooperative people are often pressured to absorb the consequences of someone else’s fear. They are asked to be patient, flexible, understanding, and diplomatic while the person blocking the work faces few consequences. This dynamic is not sustainable.

Empathy matters, but empathy cannot mean allowing one person’s discomfort to control the work of an entire organization.

A healthier approach is to acknowledge the fear while still requiring movement. For example: “I understand that this feels risky, and we can build in checkpoints. But we still need a decision by Friday because the delay is affecting students.” Or: “I hear that your unit is concerned about scope. Let’s define the limits of your involvement, but opting out entirely is not workable for this project.”

This kind of response balances care with accountability. It does not shame the conflict-averse leader, but it also does not allow avoidance to become the operating model.

The central question becomes: How do we reduce unnecessary fear while preventing fear from becoming institutional obstruction?

That question is especially important in academic libraries and higher education, where shared work often depends on cross-unit relationships. When one leader repeatedly says “no” to maintain control, collaboration becomes impossible. The organization must then decide whether it values shared work enough to address the behavior directly.

Collaboration requires trust, but it also requires courage. When fear drives decision-making, leaders need to create enough structure to make participation safer and enough accountability to ensure that refusal does not become the default.

Why Collaboration Feels Risky in Toxic Workplaces

Collaboration requires vulnerability. It asks people to share unfinished ideas, admit what they do not know, negotiate priorities, and sometimes give up control. In a toxic workplace, these behaviors can feel dangerous.

If employees have experienced blame, exclusion, retaliation, favoritism, or dismissive leadership, they may reasonably avoid deeper collaboration. They may ask themselves: Will my idea be dismissed or taken by someone else? Will this project create more work without recognition? Will I be blamed if something goes wrong? Will another unit use this collaboration to control the outcome? Will speaking honestly damage my relationships or reputation?

These questions are not signs of resistance. They are signs that the organization has not built the trust necessary for collaboration.

This is why leaders and colleagues should not demand collaboration without first addressing workplace conditions. Collaboration cannot be forced through a committee charge, a strategic plan, or a meeting invitation. It has to be made possible through trust, clarity, accountability, and shared benefit.

A Solutions-Oriented Shift: From Forced Collaboration to Conditions for Collaboration

The goal is not to shame people for operating in silos. In many toxic workplaces, silos are a coping mechanism. The goal is to create conditions in which people can safely move from guarded cooperation to meaningful collaboration.

A useful starting point is to distinguish between three levels of working together.

Coordination means aligning schedules, processes, or tasks.

Cooperation means helping one another complete separate goals.

Collaboration means creating shared goals, shared ownership, and shared outcomes.

Not every project requires collaboration. Sometimes coordination is enough. Sometimes cooperation is appropriate. But when the work affects students, faculty, access, equity, service quality, workplace culture, or institutional change, collaboration is often necessary.

The problem is not that every interaction must become collaborative. The problem is when institutions claim collaboration while only supporting coordination or cooperation.

Practical Strategies for Moving from Silos to Shared Work

1. Name the Type of Work Required

   Before launching a project, name what kind of working relationship is actually needed. Are we coordinating, cooperating, or collaborating?
   

   This simple question can reduce frustration. If a department only needs another unit to provide data, that is cooperation. If multiple departments need to design a student support initiative together, that is collaboration. Naming the difference prevents people from overpromising, underparticipating, or misunderstanding their role.
   

   A practical meeting question might be: “Are we asking each unit to contribute a piece, or are we asking everyone to help shape the direction?”

   That distinction matters.

2. Establish Minimum Cooperative Behaviors First

   Before expecting collaboration, organizations need to establish the basic behaviors that allow work to move forward. These expectations should not be vague. They should be concrete, observable, and connected to the work.

   For example, a unit participating in a shared initiative should be expected to respond within an agreed-upon timeframe, send someone with decision-making knowledge to meetings, share necessary information, identify constraints honestly, and follow through on assigned responsibilities.

   If these behaviors do not occur, leaders should not ask the more cooperative unit to simply “try harder.” That only rewards obstruction and increases burnout.

   Instead, leaders should ask: What agreement was not honored? What information is being withheld? What decision is being delayed? Who has the authority to resolve this?

   Collaboration cannot be built on avoidance. Basic cooperation has to be named, expected, and supported.
   

3. Build Shared Purpose Before Assigning Tasks

   Toxic workplaces often rush to tasks because tasks feel safer than values, purpose, or conflict. But collaboration requires a shared understanding of why the work matters.

   
   

   Before assigning responsibilities, take time to clarify the shared purpose. For academic libraries, this might mean connecting the work to student success, equitable access, information literacy, faculty support, retention, a sense of belonging, or the institutional mission.

   A shared purpose does not eliminate disagreement, but it gives people a reason to stay engaged when the work becomes complicated.

   Instead of beginning with, “Who will do what?” begin with, “What are we trying to improve, and for whom?

4. Make Labor Visible

   One of the fastest ways collaboration becomes toxic is when labor is uneven or invisible. Some people plan, facilitate, document, communicate, repair relationships, and follow up, while others simply attend meetings or approve decisions.
   

   To prevent this, name the labor involved. Project management, emotional labor, communication, assessment, documentation, accessibility review, student outreach, and conflict management are all forms of work.
   

   A collaborative project should include a visible labor map. Who is responsible for decisions? Who is doing the communication? Who is gathering feedback? Who is documenting outcomes? Who has the authority to remove barriers?
   

   When labor is visible, it becomes easier to distribute it fairly.
   

5. Create Psychological Safety Through Process, Not Personality

   In toxic workplaces, collaboration often depends on individual personalities. If people like each other, the work moves forward. If they do not, the work stalls.

   Healthy collaboration should not depend entirely on personal chemistry. It should be supported by clear processes.

   
   

   This includes agendas, shared notes, decision-making norms, timelines, role clarity, and mechanisms for raising concerns. These structures may seem basic, but they are especially important in workplaces where trust is fragile.

   
   

   Psychological safety is not created by asking people to “be positive.” It is created when people know how decisions will be made, how disagreements will be handled, and how their contributions will be respected.

6. Address Conflict as Information

   Siloed workplaces often treat conflict as a threat. But conflict can provide important information about unclear expectations, competing priorities, resource constraints, or past harm.

   The goal is not to eliminate conflict. The goal is to make conflict usable.

   When disagreement emerges, leaders and colleagues can ask: What is this conflict telling us about the work? Is there a resource issue we have not named? Are roles unclear? Is one unit being asked to absorb too much labor? Is there a history here that needs to be acknowledged? Are we avoiding a decision that someone needs to make?

   This approach shifts conflict from personal blame to organizational learning.
   

7. Build Feedback Loops

   Collaboration should include feedback loops before, during, and after the work. Too often, departments collaborate on a project, complete it, and move on without discussing what worked, what caused harm, or what should change.
   

   Feedback loops help prevent the same patterns from repeating. They also create opportunities for repair.
   

   A simple structure can help: What helped the collaboration work? What made the collaboration harder? Was the labor distributed fairly? Were decisions transparent? Who was missing from the conversation? What should we change next time?
   

   This makes collaboration a learning practice rather than a performance of teamwork.
   

8. Protect Boundaries While Building Bridges

   Collaboration does not mean unlimited availability. It does not mean saying yes to every request. It does not mean absorbing another department’s dysfunction in the name of being helpful.

   
   

   In toxic workplaces, boundaries are essential. Strong collaboration requires clear boundaries around time, scope, decision-making, and responsibility.

   
   

   A boundary might sound like: “We can contribute to the planning conversation, but we do not have the capacity to manage the full project.” Or: “We can share the data, but we need to be part of the interpretation before decisions are made.”

   
   

   Boundaries do not prevent collaboration. They make sustainable collaboration possible.
   

9. Move from Persuasion to Escalation When Needed

   When a unit repeatedly refuses to cooperate, it is tempting to keep persuading, softening, reframing, or trying to find the perfect way to ask. This can become exhausting, especially for employees who are already acting in good faith.

   
   

   There comes a point when persuasion is no longer the right strategy. If the refusal is affecting students, faculty, staff, compliance, access, service quality, or institutional goals, the issue may need to be escalated.

   Escalation does not have to be dramatic or punitive. It can be framed around impact and decision-making. For example: “We have not been able to move forward because we do not have the necessary information. This is now affecting the timeline, so we need a decision about how to proceed.”

   The goal is not to win a conflict. The goal is to prevent avoidance from becoming the default operating structure.

   
   

The Role of Library Leaders

Library leaders have an important role in distinguishing cooperation from collaboration. They can model transparency, name power dynamics, distribute labor fairly, and resist the temptation to call every cross-unit interaction collaborative.

Leaders can also protect employees from performative collaboration. When a project lacks shared ownership, adequate resources, or clarity in decision-making, leaders should not pretend that enthusiasm will solve the problem.

A solutions-oriented leader might ask: Do we have the right people at the table? Are we asking for collaboration after decisions have already been made? Is this project creating uncompensated or unrecognized labor? Are we inviting input or merely seeking approval? What authority do participants actually have? How will we acknowledge contributions?

Just as importantly, leaders need to intervene when one unit’s refusal to cooperate harms others. Asking cooperative employees to compensate for an uncooperative department is not collaboration. It is a displacement of responsibility.

Leadership requires clearly naming the breakdown: “This work cannot move forward because the necessary information has not been provided,” or “The timeline is at risk because the agreed-upon decision has not been made.”

This kind of clarity is not punitive. It is accountable. It prevents toxic dynamics from being hidden behind vague language about teamwork, collegiality, or collaboration.

Moving from Silos to Shared Work

Silos do not disappear because someone announces a new initiative. They weaken when people experience trustworthy patterns over time. Those patterns include clear communication, shared credit, honest feedback, fair labor distribution, and accountability when harm occurs.

In academic libraries, this work is especially important because libraries often sit at the intersection of students, faculty, staff, technology, access, research, teaching, and institutional mission. Libraries are natural bridge-builders, but that role should not require library workers to compensate for every institutional dysfunction.

The difference between cooperation and collaboration is not just semantic. It is cultural.

Cooperation can help people survive a toxic workplace. Collaboration, when supported by trust and accountability, can help transform it. But collaboration cannot exist without basic cooperation.

The path forward is not to demand more teamwork from the people already trying to make broken systems function. The path forward is to define the minimum behaviors required for cooperation, hold units accountable when those expectations are not met, and then build the trust, structure, and shared purpose necessary for real collaboration.

This also means recognizing when refusal is rooted in fear. A conflict-averse leader may say “no” to feel safe, avoid uncertainty, or maintain control. But fear cannot be allowed to become an institutional obstruction. The humane response is to reduce unnecessary fear while still requiring movement, clarity, and accountability.

In siloed organizations, collaboration begins with a simple but powerful shift: stop asking people to merely help each other complete separate agendas, stop blaming the most cooperative people when collaboration fails, and start creating the conditions where shared work is honest, equitable, accountable, and sustainable.