Why Diverse Voices Belong in Policy Development

Including diverse voices in policy development means involving the people who live a policy every day, clinicians, BTs, billing, and operations staff, before and while you write it, not just after. Policies built with staff rather than only for them stay grounded in real workflows, catch compliance risk earlier, and roll out with far less friction.

You've just finished updating your documentation policy. It's airtight. Compliant, organized, defensible. You've dotted every "i," cited every requirement, and built in all the right safeguards.

You hit send feeling pretty satisfied.

A week later, your BTs are frustrated, your billing team is confused, and staff are quietly building workarounds.

What went wrong?

Sometimes the problem isn't the policy. It's who helped write it.

Policies written for staff but not with them often look perfect on paper and fall apart in practice.

A policy's real purpose isn't to control. It's to guide. It's the roadmap your organization uses to balance compliance requirements, operational realities, and the shared mission of delivering excellent care. When the people who live that balance every day help shape it, the result holds up.

Including diverse voices, from clinicians to billing teams to operations staff, turns policies from rulebooks into practical tools that connect people to their purpose.

Why does including diverse voices in policy development matter?

Involving staff from different roles matters because each role sees the work, and the risk, from an angle leadership can't see alone. When the people who carry out a policy help write it, the policy matches how work actually happens, surfaces problems before rollout, and earns the buy-in that makes it stick. Here's how that plays out.

It keeps policies grounded in reality

Frontline and administrative staff live the policies we write. Their insight keeps procedures matched to the actual flow of work, not the imagined version on paper.

When a BT or billing specialist can say, "That's not how it actually happens," leadership gets to fix the problem before rollout instead of after frustration builds.

It helps catch risk early

Each role sees compliance risk from a different angle.

A behavior analyst may notice documentation issues that threaten clinical integrity. A billing coordinator might spot an audit exposure the same afternoon. Bring those perspectives together, and policy development becomes an early risk-detection system. Knowing which of those risks to prioritize is its own skill, one we break down in how to know what to audit.

It strengthens trust and culture

Inviting input signals respect. It says compliance isn't only a leadership job. It's a shared organizational function.

When staff help shape the rules that guide their work, they support those rules far more readily. That's the same dynamic that carries compliance through every stage of the employee lifecycle.

It supports equity and retention

Policies that ignore the realities of direct care can quietly create inequities or burnout.

Bringing in frontline voices early helps prevent those unintended consequences. It reinforces a culture where staff feel heard and valued.

It makes implementation smoother

People support what they help create.

When a policy reflects the collective wisdom of the organization, rollout feels less like an executive order and more like a team effort.

How do you include diverse voices in policy development?

Building an inclusive compliance culture doesn't require a complete overhaul. Small, intentional changes to your process make a real difference. Start with your next policy review, or the next new policy you develop.

Solicit feedback early

Gather input before you draft. Consider:

• Hosting informal listening sessions
• Sending brief surveys or running short interviews
• Asking simple questions like "What works well?" and "What's confusing?"

Some organizations also run policy perception audits to surface barriers or unintended consequences. Sharing redlined drafts and collecting feedback through supervisors or liaisons brings even more voices into the room.

Include staff in the development process

Cross-functional policy committees offer a simple way to fold in multiple perspectives. Consider representatives from:

• Clinical teams
• Operations
• HR
• Billing

Some organizations open nominations for committee spots and rotate membership over time, so new perspectives keep shaping the process. Compliance leadership may hold final authority over policy language, and staff contributions still reveal operational realities leadership alone would miss.

Establish ongoing policy practices

Sustainable inclusion grows through routine. Organizations may choose to:

• Designate policy champions who communicate the purpose and importance of each policy
• Appoint policy managers who serve as internal experts on implementation
• Schedule annual policy review weeks inside the compliance calendar
• Offer short trainings on how staff can give useful feedback
• Keep a simple suggestion box for operational ideas, separate from the formal compliance concern reporting system

These practices reinforce that policy development is an ongoing conversation, not a one-time event.

How do you manage expectations in collaborative policy development?

Set the expectation up front that including diverse voices doesn't mean every idea lands in the final draft. This is where leadership communication earns its keep.

Clear communication about the decision, and the reasoning behind it, shapes how staff experience the outcome. When people understand how a decision got made, they feel respected even when their suggestion didn't make the cut.

Communicating policy decisions effectively

A few practices help leaders share final decisions well.

Acknowledge the process. Name the input that shaped the policy, and thank the people who contributed.

Lead with the "why." Frame a policy through its purpose rather than just announcing the rule.

Instead of: "Starting next week, staff may not text client information."

Try: "To protect confidentiality and meet HIPAA standards, we're moving client communication to a secure platform."

Understanding the purpose makes compliance feel mission-driven rather than punitive.

Clarify what's required versus what's flexible. Explain which elements come from regulations or payer requirements and which reflect internal operational choices. Transparency builds credibility.

Use multiple channels. Policy changes land better when shared several ways: email summaries, team huddles, quick-reference materials, or Q&A sessions.

Keep the feedback loop open. Remind staff that policies evolve, and that their ongoing feedback keeps shaping improvements.

Bringing it back to mission

Policies are the scaffolding of your organization. They hold up the mission. But scaffolding built without the people who walk on it every day won't hold for long.

Including diverse voices in policy development isn't just a compliance best practice. It reflects the core values of ABA: collaboration, respect, and a commitment to quality care. Federal guidance points the same direction. The HHS Office of Inspector General's General Compliance Program Guidance ties an effective compliance program to open lines of communication, so staff can raise concerns and shape how the work gets done.

When policies are written together, they do more than set rules. They build systems that sustain your mission, protect your clients, and support the people who make the work possible.

One question is worth asking the next time your organization updates a policy: who's missing from the conversation?

The answer often tells you as much about how the policy will work as the policy itself.

If your organization is still finding its footing here, knowing where to start makes the first step easier.

Frequently asked questions

What does it mean to include diverse voices in policy development? It means involving staff from different roles, clinicians, BTs, billing, operations, and HR, in shaping a policy before and during drafting, not just handing them the finished rule. These are the people who carry out the policy daily, so their input keeps it grounded in how work actually happens.

Why should ABA agencies involve staff in writing policies? Because staff involvement produces policies that work in practice. Frontline and administrative staff catch mismatches between the written procedure and the real workflow, spot compliance and audit risks from their own vantage point, and support rules they helped create. The result rolls out with less confusion and fewer workarounds.

Who should be part of an ABA policy development committee? A cross-functional committee that represents the roles a policy touches: clinical teams, operations, HR, and billing. Some agencies open nominations and rotate membership over time so fresh perspectives keep shaping the process. Compliance leadership can still hold final authority over the policy language.

How do you handle staff feedback that doesn't make it into a policy? Communicate the decision and the reasoning behind it. Acknowledge the input, lead with the purpose of the policy, and clarify which parts are required by regulation or payers versus internal choices. People feel respected when they understand how a decision got made, even when their suggestion wasn't adopted.

Does inclusive policy development support compliance? Yes. Involving diverse voices turns policy development into an early risk-detection system and strengthens the culture of shared responsibility that regulators expect. HHS-OIG's compliance program guidance links an effective program to open communication and staff who can raise concerns, which is exactly what collaborative policy development builds.

If your organization has ever rolled out a policy that looked strong on paper but struggled in practice, this is a good moment to pause and reflect on how your policies actually get developed, and who's part of that process.

Building policies that work in real life isn't just about getting the language right. It's about creating a process that consistently brings together the perspectives needed to balance compliance requirements, operational realities, and staff experience.

That kind of process doesn't happen automatically.

The ABA Compliance Collective is built for ABA leaders and compliance professionals working through exactly these challenges. Inside, you'll find practical guidance, shared experience, and ongoing support to help you strengthen policy development, improve implementation, and build systems that hold up in day-to-day operations, not just on paper.

If you want to create policies your team can actually use, understand, and support, you can learn more about the Collective here.