HR's Role in Change Management for Small Business
What HR does during change, who does it when there is no HR department, which change models scale down, and a one page plan for a small team.
HR's Role in Change Management
The five responsibilities the HR function carries during organizational change, who picks each of them up in a company that does not have one, why change fatigue arrives earlier at small scale rather than later, which of the famous models actually scale down, what the most quoted failure statistic in the field is really worth, and a one page plan for a team of five to a hundred
Every article on this subject answers the same question: what does the HR function do during organizational change. They answer it well, and they list the same five or six responsibilities, and they illustrate them with a merger or an enterprise system rollout.
If you run a company of twenty people, there is no HR function. That does not remove the five responsibilities. It means they get distributed by accident, and the one that gets dropped is whichever nobody happened to pick up, which is a worse outcome than any methodology choice you might make.
So this guide answers a different question: which of HR's change responsibilities survive when there is no HR, who takes each one, and what actually changes about the practice at fifteen people rather than fifteen hundred. It covers why change fatigue is often worse at small scale rather than better, which of the famous models scale down and which do not, what the most quoted statistic in the field is really worth, the legal layer that no change model mentions and nobody in a small business is watching, and a one page plan you can fill in this afternoon. I build the people and records side of this at FirstHR.
What the Role Is
Change management is the work of getting people to actually adopt a decision that has already been made. HR's role in it is the half that operates on people rather than on the plan.
The distinction worth holding is between the decision and the adoption. Deciding to move to a new system, reorganize reporting lines, or rewrite a policy is usually the easy half and gets most of the attention. The hard half is that three months later people are either working the new way or quietly working the old one, and almost nothing about that outcome is determined by the quality of the original decision.
That is why this is a people problem rather than a project problem, and why it lands in the HR column at organizations that have one. It is also why it does not stop being that work simply because your company has no HR column.
When There Is No HR
Most US employers have no HR department at all, and the guidance written for this topic almost universally assumes one. Reassigning the work rather than skipping it is the entire practical problem.
Scale is worth stating plainly. Federal business size statistics place the overwhelming majority of US employer firms in the smallest bands, and occupational data counts roughly 944,300 human resources specialists across the entire economy. The arithmetic means the typical company reading a guide about what HR should do during change does not employ anyone to whom that guidance applies.
| Responsibility | Who does it at 500 people | Who must do it at 20 | What happens if nobody does |
|---|---|---|---|
| Readiness and capacity check | HR business partner with an assessment | The founder, by asking three people honestly | The change lands on a team already at capacity and both fail |
| Communication and translation | Internal comms plus HR | Whoever is running the change, in person first | People invent an explanation, and it is usually worse than the real one |
| Capability building | L&D function | The most competent user, given time to teach | Resistance appears that is really a skills gap |
| Legal and contractual mechanics | HR with legal counsel | Named explicitly, often with outside help | The expensive failure, and the one nobody sees coming |
| Thirty day adoption check | HR, with a survey | Whoever ran it, by watching what people do | The change quietly reverts and nobody notices for a quarter |
The fourth row is the one to act on first. Four of the five can be absorbed by whoever is driving the change, because they are extensions of running the business well. The legal layer is different in kind: it requires knowing that an obligation exists, and a person who does not know it exists will not discover it by being conscientious.
The Five Responsibilities
These are the same five that every enterprise guide lists. What changes at small scale is not the list but the form each takes.
The second one carries a specific technique worth naming. The gap between a company reason and an individual consequence is where most communication fails: leadership announces that the business is consolidating tooling, and eleven people hear a sentence that contains no information about their own week. The translation step is asking, for each person, what is different about their Monday, and saying that sentence to them.
The third is worth taking seriously because it is so often misread. When someone pushes back on a new process, the instinct is to treat it as attitude. Providing the training first and seeing whether the objection survives costs an hour and settles the question, and in my experience it settles it in favor of the skills explanation more often than not.
Communication Examples: What the Announcement Actually Says
A change gets communicated three times to three audiences, and the fourth conversation is the one that checks it landed. The table below is what each of those sounds like on a single change, moving expense approvals out of a shared spreadsheet and into a system.
| Who hears it and when | What the message has to carry | An example line |
|---|---|---|
| The people most affected, individually, before anyone else | The individual consequence, the loss, and an ask | From the fifteenth, approvals move into the new system. Your Thursday spreadsheet stops and you approve from your phone instead. You lose the running total you built, so tell me what replaces it. |
| The team, in the room, after those conversations | The business reason, the date, and what is not changing | We are moving approvals into one system on the fifteenth, because four days to approve an invoice is costing us work. Nothing changes about who approves what, or about anyone's spend limit. |
| Everyone, in writing, the same day | The dates, the first steps, and where questions go | What changes on the fifteenth, what to do the first time you use it, who to ask when it does not work, and the date the old spreadsheet closes. |
| Week four, in the one to one | A check on behavior, not a reminder | Show me how you did the last one. Where did it get slow? |
None of these is written to be admired. The pattern is a date, a consequence for the person in front of you, and one thing they can do or ask next. A message without those is a broadcast, and people are well practiced at ignoring broadcasts.
The plan version of the same thing is a communication log, and the sheet in the download pack further down is built for it: one row per audience, with the date, the channel, who delivered it, what got asked, and what you still owe an answer on.
The Change Readiness Assessment, Scaled Down
A change readiness assessment asks one question in several forms: if we start this on Monday, what in the business breaks. At enterprise scale it arrives as a survey instrument with a scoring model behind it. At twenty people it is a twenty minute conversation with the three or four people whose week the change actually rewrites.
| The question to ask | What a worrying answer sounds like | What it changes about the plan |
|---|---|---|
| What else is already in flight? | A list of four things, two of which nobody has finished | Something gets paused before this starts |
| Who is already at capacity? | The same name comes up from three different people | That person does not also own the rollout |
| Does everyone affected have the skill already? | One person can do it and they are the busiest person here | Training moves ahead of the go-live date |
| Has a similar change stuck before? | We tried this two years ago and it faded out | Find what reverted it, because that thing is still here |
| Who gains, and who only absorbs the cost? | The people doing the extra work get nothing back | Say so out loud rather than pretending it is even |
| Is the deadline real? | It has to be done this month, and the reason trails off | Test whether the date came from the business or from a slide |
Impact analysis is the other half, and at this size it is a list of names rather than a matrix of roles. Go down the affected people one at a time and record what changes for each, how large it is, and who tells them. The exercise almost always surfaces one person nobody had thought about. Written down, that list is your change impact assessment, and the impact map sheet in the pack further down is the form it takes.
Change Fatigue
Change fatigue is the standard warning in this literature, and the standard framing gets small businesses backwards. The usual claim is that enterprises suffer it because they run many initiatives; the implication is that a small company, running fewer, is safer. Often the opposite is true per person.
The enterprise research is real and worth citing. According to Harvard Business Review, reporting Gartner research, the average employee experienced ten planned enterprise changes in 2022, up from two in 2016, while willingness to support enterprise change collapsed to 43 percent from 74 percent over the same period.
Here is why the small business version is worse than it looks. A formally labeled initiative at a large company usually touches one department. In a company of twenty, virtually every change touches everyone: a new tool, a new process, a new manager, a client win that reshapes the week, a departure that redistributes three people's work. None of it is labeled as change, none of it appears on anyone's initiative count, and all of it consumes the same finite capacity to adapt.
| Large organization | Company of twenty | |
|---|---|---|
| Changes formally labeled as initiatives | Many, and counted | Almost none, and none counted |
| Share of staff touched by a typical change | One department | Everyone |
| Unlabeled change from hiring and departures | Absorbed by scale | Redistributes real work every time |
| Who notices the accumulation | A change function tracking a portfolio | Nobody, because none of it looks like a program |
| Recovery time between changes | Sometimes designed in | Rarely, because the next thing is already urgent |
| Where fatigue first appears | Survey scores | One person quietly disengaging |
The practical response is not to change less. It is to notice that change capacity is finite and to say out loud what is being paused when something new starts. A plan that adds a change without naming what stops is spending capacity nobody has budgeted, and the effect shows up as burnout or as a quiet reversion rather than as an objection.
The Models, Plainly
Four frameworks recur across everything written on this topic. They are worth knowing, and none of them needs to be adopted as a methodology by a company of twenty.
| Model | What it is genuinely good for | Where it breaks at small scale | Worth using? |
|---|---|---|---|
| Unfreeze, change, refreeze | Reminding you that the new way must be made settled | Nothing, it is small enough to survive | Yes, especially the third stage |
| The eight step process | Structuring a large multi-year transformation | Coalitions and vision cascades assume layers you do not have | Borrow the sequencing idea, skip the apparatus |
| Five stage individual model | Diagnosing exactly where one person is stuck | Nothing, and it improves at small scale | Yes, this is the one to actually use |
| Transition curve | Setting expectations about a temporary dip | It is descriptive, so it produces no actions | Yes, as a communication tool only |
The third row is the recommendation. Awareness, desire, knowledge, ability, reinforcement operates on individuals, and at fifteen people you can genuinely walk the list for each person by name. Doing so tends to produce a specific and surprising finding: the people you assumed were resisting are usually split between one who never heard the reasoning and one who cannot yet do the thing, and those need opposite responses.
Lean Change Management and Nudge Theory
Two other names come up often enough to be worth a sentence each. Lean change management borrows from agile and lean startup practice: rather than a plan with phases, you run a loop of insights, options, and small experiments, and let the result of each experiment decide what comes next. For a team that already works in short cycles, that shape is familiar.
Nudge theory comes out of behavioral economics and argues that redesigning the choice beats announcing the policy. Make the new way the default, put it where the old habit used to live, and take a step out of it. This is the cheapest instrument a small business has: when the new form is the only form on the shared drive, nobody needs persuading.
Force Field Analysis: A Worked Example
A force field analysis sets the forces pushing a change forward beside the forces holding the current way in place, and then works on the second list. It comes from the same researcher as unfreeze, change, refreeze, and it is the smallest instrument here: two columns, twenty minutes, one page.
Here it is on an ordinary small business change, moving expense approvals out of a shared spreadsheet and into a system.
| Force | Which way it pushes | Strength | What to do with it |
|---|---|---|---|
| Approvals currently take four days | Toward the change | Strong | Lead the announcement with it, since it is the part people already feel |
| The person who asked for it runs finance | Toward the change | Medium | Have them explain the reason instead of you |
| Nobody has used the new form yet | Against the change | Strong | Train before go-live. This is the first restraint to remove |
| The old spreadsheet still works and is open all day | Against the change | Strong | Close the old route on a named date |
| Two people lose a workaround they built themselves | Against the change | Medium | Name the loss out loud and ask what replaces it |
| Month end falls in week two of the rollout | Against the change | Medium | Move the go-live rather than argue with the calendar |
The instinct is to add weight on the left: more reasons, a better announcement, more enthusiasm from you. Pushing harder while the restraints are still standing produces tension rather than movement. Removing one restraining force, closing the old route or running the training, moves more than any argument you can make.
The 70 Percent Claim
Almost every article on this subject opens with the assertion that around 70 percent of change initiatives fail. It is worth knowing how thin that number is before you plan around it.
The figure traces to observations about large corporate transformations published in the 1990s rather than to a controlled study, and it has been questioned repeatedly since, both for its provenance and for the precision it implies. Different sources put the failure rate anywhere from half to nearly eighty percent, using different definitions of failure, different populations, and in several cases no stated methodology at all.
None of this means change is easy. It means the honest version of the warning is qualitative: organizational changes fail at adoption more often than at decision, the failure is usually quiet rather than dramatic, and the mechanism is that people revert when nothing holds the new way in place. That is a more useful thing to know than a percentage with no methodology behind it.
A One Page Plan
A change plan for a team of five to a hundred fits on one page. If it does not, the change is either too large to run at once or not yet understood well enough to start. The six steps below are the change management checklist that sits underneath the page, in the order they have to happen.
The plan names the people; three sheets behind it are where the per-person detail actually gets recorded. The impact map carries a what they lose column, which generic templates omit and which does more predictive work than anything else on the sheet. The communication log exists because in a small business the sequence is the message: who heard it first is itself information, and reconstructing that afterward is impossible. The readiness sheet is filled twice, once before and once at thirty days, which is what converts the follow-up from an intention into a document.
| A | B | C | D | E | F | G | H | I | |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Person | Role | What changes for them | Impact level | What they gain | What they lose | Skill or tool needed | Told by whom | Told on |
| 2 | Example team member | Approvals move to a new system | Medium | Faster approvals | A familiar workflow | 30 min walkthrough | |||
| 3 | |||||||||
| 4 | |||||||||
| 5 | |||||||||
| 6 | |||||||||
| 7 | |||||||||
| 8 | |||||||||
| 9 |
Change Management Metrics
Change management metrics are adoption metrics: how many people are doing the new thing, how quickly they got there, and whether it is still true a month after the announcement. At twenty people you can observe all three directly rather than surveying for them.
| What to measure | How to get it at twenty people | What a bad number looks like |
|---|---|---|
| Adoption rate | Count by name who used the new process this week | High in week one, lower in week five |
| Speed of adoption | Days from go-live until the last person uses it unprompted | Someone is still on the old route after a month |
| Workarounds in use | Ask what people do when the new way is inconvenient | A parallel spreadsheet exists and nobody mentioned it |
| Whether each person can state what changed | Ask in a one to one, in their own words | You get the company rationale back, not their own task |
| Support load | Count the questions you are still answering in week four | The same question keeps arriving, so the instruction was wrong |
| The business outcome you expected | The one number the change was meant to move | Nobody wrote it down before the change started |
Two rules keep this honest. Write the expected number down before the change starts, because a target invented afterward is always met. And measure behavior rather than sentiment: asking whether people like the new system produces a politeness score, while counting who used it on Thursday produces a fact.
That preference runs through HR metrics generally. The countable ones outlive the ones that need a survey, and in a company of twenty most of them are available just by looking.
Handling Resistance
Three completely different situations present identically as resistance, and treating them the same way is the most common error in this area.
| What it looks like | What it might actually be | How to tell | What to do |
|---|---|---|---|
| Repeated questions about why | Missing information, or a rationale that was never given | They cannot restate the reason in their own words | Explain again, and check whether the reason is actually good |
| Agreement in the room, old behavior afterward | A capability gap they will not name | Ask them to do the task with you watching | Train, and the resistance usually disappears |
| Specific detailed objections | A genuine problem you do not know about | The objection contains information you did not have | Listen. They may be right, and this is the valuable case |
| Silence | Either acceptance or complete disengagement | Ask them individually rather than in the group | Depends entirely on which one it is, so find out |
| Public agreement plus private complaint | A view they do not feel safe stating openly | It reaches you second hand | Fix the safety problem, not the person |
The third row is the one worth protecting. In a small business the person with a detailed objection is frequently the person closest to the work, and their objection is the cheapest form of consulting you will ever receive. A culture where that lands as obstruction rather than as information is expensive in ways that never appear on a list, which is the practical argument for psychological safety as an operating condition rather than a value on a wall.
The fifth row is a signal rather than a problem to solve directly. When disagreement reaches you second hand, the disagreement is not the issue. The routing is. That usually resolves through the ordinary machinery of one to one conversations rather than through anything change specific.
The Legal Layer
No change management model mentions this, and in a company without an HR function nobody is watching for it. Four categories cover most of what a small business will encounter.
| Category | When it applies | What to check |
|---|---|---|
| Notice of changed terms | Role, schedule, or reporting changes | Several states require written notice of changes to terms of employment |
| Pay changes | Any change to rate, structure, or frequency | Advance notice is generally required before a change takes effect, and the rules are state specific |
| Reductions and separations | Any reduction, however small | Final pay timing rules vary by state, and advance notification obligations attach above certain headcount and layoff-size thresholds |
| Policy and handbook changes | Any rewrite that changes what is expected | Distribution and a dated acknowledgment record for each employee |
| Classification changes | Moving someone between exempt and nonexempt, or employee and contractor | The change has to be defensible on the facts, not just agreed |
| Benefit changes | Any change to what is offered or who is eligible | Notice requirements and plan documentation, and this one usually needs help |
The third row deserves specific attention because it is where a small business is most likely to be surprised. Reductions carry final pay deadlines that differ substantially between states, and above defined thresholds there are advance notification requirements with real consequences for missing them.
The fourth row is the quiet one. A policy rewrite is a change like any other, and the thing that makes it defensible later is a dated acknowledgment from each person rather than the quality of the policy itself. Keeping those acknowledgments attached to the employee record rather than in an email thread is what makes the question answerable in a minute instead of a week.
Changes You Will Face
The literature illustrates change management with mergers and enterprise transformations. Here is the actual list for a company of five to a hundred, with what tends to go wrong in each.
| The change | What people actually fear | The step most often skipped |
|---|---|---|
| First HR or payroll system | Being measured in a way they were not before | Explaining what the system will and will not track |
| First layer of managers | Losing direct access to the founder | Telling people what the founder will still be involved in |
| Moving from remote to hybrid, or back | A change to their life, not their job | Acknowledging that this one is genuinely a loss for some people |
| A significant client win | Their week changing without being asked | Naming what is being paused to make room |
| A key person leaving | Their work landing on the remaining team | Deciding explicitly what is dropped rather than redistributed |
| Rewriting policies or the handbook | That something is being tightened without being said | Stating plainly what is new versus what is being written down for the first time |
| Reorganizing who reports to whom | Status, and whether this precedes something worse | Saying what is not changing, especially about jobs |
| A pay or benefits change | Whether they are worse off | Individual conversations before the group announcement |
The middle column is the useful one. In each case the stated objection is rarely the real one, and the real one is almost always about consequence to the individual rather than merit of the decision. The first row is worth a note since it is the change I see handled worst: introducing a system that records what people do reads as surveillance unless somebody says explicitly what it is for.
Incremental, Transitional, and Transformational Change
Organizational change comes in three sizes, and the sorting is worth doing because each size fails somewhere different. Incremental change adjusts something that already exists, such as a new form or a moved deadline. Transitional change replaces one defined state with another on a date: a new payroll system, a new reporting line.
Nearly everything in the table above is transitional, which is the most tractable of the three because there is a before, an after, and a day it happens. Transformational change is rarer and alters what the business is: moving from projects to a subscription, opening a second location, going from founder-led selling to a team that sells.
The difference that matters is what holds each one in place. A transitional change needs a date and a closed old route. A transformational one needs the same message repeated over quarters and visible decisions that match it, which is why it behaves far more like culture change than like a system rollout.
Changes That Behave Differently
Three kinds of change break the general pattern enough to need their own handling: technology rollouts, AI adoption, and culture. Each one fails in a specific place, and knowing which of the three you are running tells you where the effort should go.
Technology and Digital Transformation
Technology change management fails at the process layer rather than the software layer. Buying the system is the small decision. The large one is that the new tool assumes a way of working, and if the old process keeps running beside it, people will stay on the old process because it still works.
So the tool rollout and business process change management are one project, not two. Write the current process down step by step before go-live, mark the steps the system removes, and set the date the old route closes. A digital transformation that never closes the old route leaves you with two systems and reporting from both that disagrees.
The other half is capability. Pick one person to learn the tool properly and teach it, instead of sending a login link to everybody at once. Choosing HR technology is a separate conversation from rolling it out, and the rollout is where small companies lose the value they already paid for.
AI Adoption
AI change management is mostly a fear conversation, and pretending otherwise wastes the first month. When you introduce a tool that writes, summarizes, or screens, people hear a question about whether their job survives it. If nobody answers that question, they answer it themselves, and quiet non-adoption is what their answer looks like.
Say what the tool is for, say what it will not be used for, and be specific about whether a person reviews the output before it counts. Then name what the saved time is going toward. AI in HR work follows the same rule as any other system: an announcement that skips the individual consequence gets filled in with the worst available guess.
Culture Change
Culture change management is the slowest of the three, because culture is not something you switch on a date. What people call culture is accumulated evidence of what gets rewarded, tolerated, and ignored. Changing it means changing visible decisions, repeatedly, until the evidence turns over.
The practical version is to pick one behavior, define what it looks like in a specific situation, and hold the first hard case in public. The moment somebody senior is asked to follow the new norm is the moment it becomes real to everyone watching.
Embracing change is not a trait a team either has or lacks. It is the residue of previous changes that were handled well, which is the real argument for doing the small ones properly. Company culture moves on a year horizon while a system rollout moves on a month, and running both at the same tempo is how each of them stalls.
Common Mistakes
The failures are consistent and most of them are sequencing errors rather than judgment errors.
| Mistake | Why it happens | The fix |
|---|---|---|
| Announcing to the group before telling those most affected | It feels efficient and even-handed | Most affected first, individually, from the decision maker |
| Explaining the business reason and stopping | The reason is the part leadership has thought about | Translate it into what is different about each person's Monday |
| Treating a capability gap as an attitude problem | Reluctance and inability look identical | Provide the training and see whether the objection survives |
| Adding a change without pausing anything | Everything feels urgent | Name what stops. Change capacity is finite and small teams have less |
| Skipping the refreeze | The change feels finished once it is announced | Something has to hold the new way in place or it reverts quietly |
| No thirty day check | Nobody schedules the boring part | Put a date and a name in the calendar during planning |
| Leaving the legal owner unnamed | Nothing about the change seems legal | Name one anyway. This is the omission with the highest cost |
| Planning around a 70 percent failure rate | Every article opens with it | Use your own history with your own last three changes |
| Copying an enterprise methodology wholesale | It looks rigorous | Take the individual diagnosis and the refreeze idea; leave the apparatus |
The first row causes more damage than any other and costs nothing to avoid. A person who learns in a group meeting that their role is changing has been told two things: the change, and that they were not worth a conversation. The second one is what they remember, and it colors how they receive everything you announce afterward.
None of this requires an HR department, a methodology, or a consultant. It requires a page, five named owners, a sequence, and a date thirty days out. That is genuinely the small business version, and executed properly it outperforms most of what large organizations manage with far more machinery.
Frequently Asked Questions
What is HR's role in change management?
HR carries five responsibilities during organizational change: assessing whether the organization can absorb it, communicating what is changing and what it means for each person, building the capability the change requires, handling the legal and contractual mechanics, and checking thirty days later whether the change actually landed. In a large organization these sit with a dedicated function. In a company without one they do not disappear, they get distributed by accident, which is why naming an owner for each before the change starts matters more than any methodology.
Who handles change management in a company with no HR department?
The owner or an operations lead, usually without the work being named as change management. The practical approach is to take the five responsibilities and assign each to a person before the change begins. Four of them can sit with whoever is running the change. The fifth, the legal and contractual layer, is the one nobody else in the business will pick up, and it is also the one with the highest cost of being missed, so it deserves an explicit owner even if that owner is an outside adviser.
Why is change management important in HR?
Because most organizational changes fail at adoption rather than at decision. The decision to move to a new system, restructure a team, or rewrite a policy is usually straightforward; getting people to actually work differently afterward is not. The HR contribution is the part that operates on people rather than on the plan: whether the team has capacity, whether each person understands what changes for them, whether they have the skills, and whether the new way is still in place a month later.
What change management models does HR use?
Four recur. The unfreeze, change, refreeze model is the simplest and its third stage, making the new way settled, is the one businesses skip. The eight step process is built for large organizations and several of its steps collapse into a single conversation at small scale. The five stage individual model of awareness, desire, knowledge, ability, and reinforcement is the most portable to a small team because it operates on one person at a time. The transition curve describes an expected dip in performance rather than prescribing action.
Is it true that 70 percent of change initiatives fail?
That figure is repeated everywhere and rests on much weaker evidence than its ubiquity suggests. It traces back to observations about large corporate transformations in the 1990s rather than to a controlled study, and researchers have repeatedly questioned both its provenance and its precision. Treat it as a rhetorical device rather than a planning input. A small business planning around a supposed 70 percent failure rate is calibrating to a number that was never measured in organizations resembling its own.
How do you handle resistance to change?
Start by distinguishing the three things that look identical from the outside. Someone may lack information, in which case the fix is communication. They may lack capability, in which case the fix is training and the resistance evaporates once they can do the thing. Or they may have a genuine objection based on knowledge you do not have, in which case the fix is listening, because the objection may be correct. Treating all three as attitude problems is the most common and most expensive error.
Does a small business experience more or less change fatigue than a large one?
Often more per person, which is the opposite of what people assume. Research on enterprise change counts formal initiatives, and a large organization's change typically touches one department at a time. In a company of twenty, almost every change touches everyone: a new tool, a new process, a new manager, a new client that reshapes the week. The individual exposure is higher even though the number of formally labeled initiatives is lower, and nobody is tracking it because none of it looks like a program.
What legal steps does HR need to cover during a change?
It depends on the change, and the categories to check are notice, pay, documentation, and thresholds. Role or schedule changes may require written notice in some states. Pay changes generally require advance notice before they take effect. Reductions carry final pay timing rules that vary by state and, above certain headcount and layoff-size thresholds, advance notification requirements. Policy rewrites need acknowledgment records. None of this appears in any change management model, and in a small business nobody is watching for it by default.
How do you know whether a change actually worked?
Look thirty days later at behavior rather than at sentiment. Are people using the new system or quietly still using the old one? Has the new approval step become routine or is it being worked around? Can each affected person still describe what changed for them? A change that has quietly reverted looks exactly like a change that succeeded if you only measure whether it was announced, which is why the follow-up date belongs in the plan from the start.