Improve interdepartmental communication by reducing silos, clarifying shared goals, and building trust across public sector teams.
Article Highlights
Interdepartmental communication is the exchange of information, decisions, and context among public sector teams that share responsibility for serving the community. Agencies strengthen it by aligning departments around a shared outcome, explaining why decisions are made, choosing the right channel, translating specialized language, and building trust before conflict occurs.
Consider a familiar situation. HR develops a unified hiring process to create consistency. An operational leader sees the new steps and worries they will make an already difficult hiring situation harder. HR then wonders why departments are not following a process that took time to build. Both groups want qualified people in critical roles. What’s missing is the conversation connecting policy requirements with operational reality.
That conversation can be hard to prioritize when everyone already feels overloaded. Patrol sees calls stacking up. Dispatch sees calls waiting that officers may not know about. HR sees vacancies, burnout, and recruitment and retention pressures. Leaders see budgets, meetings, and the next urgent decision. People are not necessarily selfish or resistant; they are carrying the stress they can see most clearly from where they sit.
Better communication should not become one more initiative on a full plate. It should reduce the assumptions and repeated misunderstandings that make the existing workload heavier. That’s why cross functional communication is more than adding the right people to an email or meeting. It requires teams to understand one another’s goals, constraints, authority, and role in the shared mission.
In Season 1, Episode 1 of the Public Voices by NEOGOV podcast, hosts Doug and Nicole draw on decades of public sector leadership experience to describe the “curse of knowledge”: people can become so immersed in their own work that they lose sight of the equally real pressures around them.
Interdepartmental conflict is often a systems problem when teams share the same public-service outcome but work through unclear handoffs, competing pressures, or incomplete context. Common signs include:
These patterns do not prove that employees are unwilling to cooperate. They often show that the process makes cooperation harder than it should be. Friction can grow from flawed systems and unclear objectives rather than ill will between employees.
Dispatch and patrol offer a clear example. Dispatch sees calls holding and needs units to clear. Patrol sees the situation in front of them and knows the work cannot always be resolved quickly. Each group experiences legitimate pressure the other cannot fully see. Friction grows when either side assumes its view is the whole picture.
Assumptions can persist for years when no one verifies them. In the episode, Nicole reflected on a time when a newly promoted fire chief walked into serious investigation issues on his first day and asked HR what he should do. HR explained his options but clarified that the decision belonged to him as chief. He was surprised: throughout his career, previous chiefs had said HR made those decisions.
One conversation exposed a misunderstanding that had been passed through the organization for years. More context did not make the situation easy, but it changed how the chief understood his authority and HR’s role.
“Focus on the problem, not the person.”
– Nicole Carlson, Host of Public Voices by NEOGOV
Instead of asking who is at fault, teams can examine the handoff, policy, workflow, missing information, or unverified assumption creating the friction. People are less likely to become defensive when the goal is to improve a process rather than prove that a colleague is the problem.
For leaders asking how to improve communication between departments, the answer is to make cross-department coordination a repeatable operating practice. Start by aligning teams around a shared outcome, explaining why decisions are made, matching the communication channel to the issue, translating specialized language, and building relationships before conflict occurs.
Let’s expand on how to implement these five practices below.
Before rolling out a change, explain the problem it is intended to solve, the requirements shaping it, and the outcome the agency needs. Then ask the employees affected how it will play out in daily operations.
“HR said so,” “the city manager said so,” or “that is the process” may establish authority, but those explanations do not create understanding. They can also make a new requirement feel like one more task added without regard for the work already underway.
A real conversation may uncover a small adjustment that preserves policy or consistency without creating unnecessary work. Interdepartmental cooperation becomes more likely when people understand the reason for a decision and can explain its operational impact.
Rather than guaranteeing everyone gets a preferred outcome, the goal is to move from “Why is this department doing this to us?” to “What are we trying to accomplish, and how can we get there together?”
Email and messaging tools are useful for routine information, documentation, and straightforward coordination. They are less reliable when a topic is sensitive, complex, or already creating tension.
Tone is easy to misread because recipients bring their own experiences and stress to the message. When the stakes are high, move the issue into a real-time conversation, ideally in person.
Follow with a written summary of the decision, owners, and next steps. Good cross-functional communication is not about choosing one channel for everything, but choosing the channel that gives the issue the best chance of being understood.
Public agencies are full of specialized language: codes, funding restrictions, technical abbreviations, policy requirements, and operational shorthand. Within a department, that language saves time. Across departments, it can create distance.
Budget season makes this especially visible. Police, fire, records, public works, engineering, and other teams may all be advocating for the same limited dollars. Each understands the consequences if its own request is not funded. It may not know that another team is trying to keep a water treatment plant operating or meet another essential community need.
Support functions such as HR and finance can help translate those realities, but translation must go both ways. Operational departments need plain-language explanations of restrictions and requirements. Support teams need to understand how policies and resource decisions affect service delivery.
Clear interdepartmental communication requires translation, not just transmission. Explain the constraint, connect it to the shared outcome, avoid unexplained acronyms, and make it safe to ask questions.
An organizational chart shows reporting lines. It does not show whether the people who depend on one another trust each other enough to raise a concern early, ask for help, or challenge an assumption.
The podcast episode’s point is simple: People work across silos through trust.
Interdepartmental collaboration improves when employees understand one another’s work before a conflict, budget request, or emergency forces them together. Those relationships make it easier to ask a question instead of assigning a motive.
They also help leaders hear what may be hiding underneath a familiar joke. A records supervisor might say patrol “gets everything.” The comment could be banter. It could also mean patrol staffing has grown while records staffing has not, leaving the records team to absorb more volume.
Rather than dismissing the comment or defending the decision, ask: “Tell me more. What does that look like to you?” The employee may be missing context, or the concern may be valid. Either way, listening helps uncover the operational reality.
Sometimes the message underneath is simple: My work is not visible. My team is not valued. Our role in the mission doesn’t seem to matter. That is worth hearing.
Choose someone in a different department, unit, shift, or part of the agency whom you do not routinely talk with. Ask for 20 minutes of their time and pose one question:
“What is one thing you wish everyone else in the agency knew about your job?”
Then listen.
Let the first goal be understanding rather than immediately solving the problem or explaining your own side. Ask what makes the work difficult, what others commonly misunderstand, and what the person takes pride in.
The person asking gains a clearer view of the organization. The person answering is reminded that their work is worth understanding. Over time, this habit can strengthen interdepartmental cooperation by replacing assumptions with real context.
Hosts Doug and Nicole suggest doing this once a month. It does not require a new committee or formal initiative—just curiosity, a small block of time, and a willingness to see the agency from somewhere else.
Sustainable interdepartmental collaboration cannot depend on individual goodwill alone. Agencies also need structures that make communication easier to repeat.
Bring affected departments into process design before decisions are final. Clarify who advises, who decides, who carries out the work, and who needs to understand the outcome. When resources are limited, explain where funding went and why, and use workforce data to support budget needs where appropriate. When employees raise a valid concern, close the loop—even when the answer is not immediate.
A records team may need more staff after the current budget is approved. A useful response is not a promise the agency can’t keep—it’s an acknowledgment of the concern, a clear next step, and a plan to prepare for the next budget cycle. That tells employees they are working toward something with the organization rather than sending concerns into a void.
Strong interdepartmental communication doesn’t eliminate disagreement. Public servants will still advocate for their teams, protect critical operations, and compete for limited resources. Better workplace communication makes those disagreements more informed, less personal, and more connected to the shared mission.
It also reminds employees that their work matters. People may not disengage because of one joke or one difficult email. The deeper risk is allowing them to believe their role no longer matters to the mission they came to serve.
Better interdepartmental communication can start with one conversation. And while one conversation won’t eliminate every silo, it can replace one assumption with understanding, uncover a concern that has gone unheard, and help a colleague feel seen.
Listen to the full Public Voices by NEOGOV episode, “Why Don’t Departments Talk? How to Fix Cross-Functional Communication,” for more insights on cross-functional communication in public safety, HR, budgeting, and agency leadership. Then take the 20-minute challenge back to your agency: meet with someone outside your usual circle, ask what they wish others understood about their job, and keep the conversation going.
Tune into Public Voices wherever you get your podcasts to hear more from Doug Shoemaker, retired Chief of Police, and Nicole Carlson, former HR leader. Each week, they draw on their 30+ years of combined experience to share unique insights that can help your agency navigate the things that often go unspoken.
🎥 YouTube: https://www.youtube.com/@NEOGOVTV/podcasts
🎙️ Spotify: https://open.spotify.com/show/0XkpuFAcQudgA8ApV4EsDR
🎧Apple: https://podcasts.apple.com/us/podcast/public-voices-by-neogov/id1896768980