5 Things to Do Before Rolling Out a New Policy

So, you think you're ready to roll out that new policy across your organization.

Did your stomach twist a little when I said that? That quiet voice wondering if it’ll land the wrong way or set off a storm of questions? Totally normal. Especially when “compliance” feels like the only shield between you and potential chaos.

But let’s be honest. Compliance is supposed to be helpful. Not a way to dodge discomfort or keep people quiet.

Before you give that policy the green light, let’s make sure you’re using compliance for what it’s meant for.

By the end of this post, that pit-in-your-stomach feeling will be long gone.

This one seems like a no-brainer, but I’ve seen it happen more than I care to admit.

Someone throws out, “We can’t do that, it’s a compliance issue,” when… it isn’t.

Not everything is a legal line in the sand. Sometimes it’s just a habit. Or fear. Or someone trying to avoid conflict by pointing to policy.

Don’t let vague rules run your team. Make sure you understand what’s truly required and where you have space to lead.

The more you know, the more confident you’ll feel making decisions that serve both your people and your mission.

Here’s where things get real.

What is this policy or rule supposed to protect?

Your people? Your values? Equity? Safety?

Write it down. Seriously. Make a short list of the top things you want your policies to support.

Then take a look at what you’ve got. If your rules aren’t helping you live out your values, that’s the problem, not your people.

You don’t have to be a policy expert. You just need to be clear about what matters and build from there.

Top tip: If you’ve got policies sitting in a folder that haven’t been touched in two years, it might be time to blow the dust off and ask if it still serves your team

I know this one’s uncomfortable, but stay with me.

Sometimes, when we’re stretched thin or burned out, it’s easier to point to policy than it is to make a hard decision.
But that “because it’s the rule” answer? People see through it. And it chips away at trust.

Ask yourself:

You don’t need to have all the answers. But you do need to be honest.

Here’s what helps:

This is the one that gets missed the most.

You roll out a new policy. You think it’s clear. But to your team, it feels random or even punitive.
Not because of what it says. But because you didn’t explain why it matters.

I worked with a leader once who updated the time off policy to make things more consistent. But she didn’t tell her team the reason behind it.

So they assumed it was about control. And the whole thing backfired.

Once she gave context and tied it back to fairness and flexibility, things changed. People got it. They supported it.

Don’t let silence do the talking. Even a quick explanation builds trust and lowers resistance.

You don’t have to run every decision by the whole staff. But if you’re building something that affects people’s day-to-day work, talk to the people who will live with it.

Ask your managers what’s working. What’s confusing. What’s being quietly worked around.
That’s where the real insights live.

Going it alone might seem faster, but it usually means you end up backpedaling.
Let your team help you get it right the first time.

Tip: If your people don’t feel comfortable being honest with you, that’s not a policy issue. That’s a culture one. And it’s fixable.