Before You Change a Policy: Questions Worth Asking

Someone raises a concern. A process isn’t working. Something happened that nobody wants happening again.

The response? Change the policy.

Sometimes that’s exactly what’s needed. But before we add another requirement, tighten a deadline, or insert “at the discretion of administration,” we should ask a few questions.

Because adding a paragraph is easy. Making sure it solves the problem takes more work.

I bring an operations mindset to policy review. I want to know what we’re trying to fix, what the evidence tells us, and what happens when the new rule meets an actual human being.

Here’s where I start.

1. What problem are we trying to solve?

“We need to update the policy” is a task. What prompted it?

What is happening? Who is affected? How often does it happen? What evidence do we have?

And if the answer is “Well, there was this one situation,” let’s examine that situation before writing a rule for everyone.

One frustrating incident deserves attention. Whether it warrants a permanent policy change is another question.

2. Is the problem in the policy, the process, or the implementation?

You can rewrite a policy all day and still have the same problem on Monday.

Maybe the language is unclear. Maybe staff interpret it differently. Maybe nobody has the time, training, or resources to follow it.

Or maybe the policy already addresses the issue, but the process for carrying it out is a mystery.

Find the breakdown. Then choose the fix.

3. Who needs to be involved?

If we’re changing a policy that affects families, employees, students, or customers, we should probably talk to them.

Preferably before the vote.

The people using a process often know exactly where it gets complicated. So do the staff trying to administer it.

Ask what works, what creates difficulty, and what the proposed change would mean for them. A conference room can offer a useful perspective. It rarely offers every perspective.

4. Does the policy account for different circumstances?

Putting everyone in the same category makes the spreadsheet easier. Does it make the response appropriate?

Two people can miss the same deadline for entirely different reasons. One misunderstood the instructions. Another couldn’t obtain the required documentation. Another had an emergency.

The policy needs enough structure to support consistency and enough judgment to account for relevant differences.

“Same response for everyone” deserves a closer look.

5. What barriers could the change create?

Read the requirements from the other side of the desk.

Can someone obtain that documentation? Take time off for that meeting? Navigate that portal? Understand the notice? Meet the deadline?

“Just submit the form” can involve several phone calls, a fee, a transportation problem, and a week of waiting.

If a requirement is essential, explain why and plan for foreseeable obstacles. If it adds work without adding value, why are we keeping it?

6. What alternatives have we considered?

Before choosing the new rule, put a few options on the table.

Could clearer instructions help? An earlier conversation? A simpler form? Better staff training? A targeted change to the existing process?

Compare the options using agreed-upon criteria: effectiveness, accessibility, cost, workload, and consistency.

“We’ve always done it this way” belongs in the history section. It needs more support to earn a place in the recommendation.

7. Is the proposed change complete and consistent?

That new paragraph has neighbors.

Does it conflict with another policy? Leave out an important exception? Use a term nobody has defined? Assign responsibility to a department that hasn’t been consulted?

Review it against current requirements, related procedures, and the organization’s stated purpose. Get specialized review where needed and document how questions were resolved.

People should be able to follow the instructions without conducting their own investigation.

8. What could go wrong when this is implemented?

This is a practical question. Ask it while there’s still time to change the draft.

What happens if someone cannot comply? If staff disagree about an exception? If a notice goes unanswered? If the person responsible is unavailable?

And when we add “at our discretion,” what guides that discretion? Who documents the decision? How can someone raise a concern?

Flexibility can be useful. People still need to understand how decisions are made.

9. What will people need to use the policy?

The policy passed. Now someone has to make it work.

Who updates the forms? Trains staff? Explains the change? Answers questions? Handles the situation nobody anticipated?

Assign those responsibilities and give people the tools and time to carry them out.

Uploading a PDF is a publishing step. There’s usually a little more on the implementation list.

10. How will we know whether the change worked?

Decide what success looks like before the policy takes effect.

What should improve? What information will we review? Are we checking outcomes, access, workload, and consistency?

Set a review date. Gather feedback. Be willing to revise the approach.

If the new process generates more letters, meetings, and paperwork, we’ve established that people are busy. We still need to establish that the problem is getting resolved.

Policy changes deserve a clear explanation of the problem, the evidence, the alternatives, and the implementation plan.

Before we add another rule, let’s make sure we can explain what it will accomplish.

And then check whether it actually does.