Change is anything that makes tomorrow different from today.
That's the whole definition. It doesn't require a project plan, an executive sponsor, or a name like "Transformation 2027." It doesn't need to be big to count. A new manager is a change. A shift in team structure is a change. A merger is a change. So is a new expense system nobody asked for.
If you're waiting for something to feel big enough to call it change, you're missing most of what's already reshaping how people work.
The scale of a change and its impact on the people living through it are two different things. A 90-day software rollout can unsettle someone's sense of competence as much as a company-wide restructuring. A new leader with a different communication style can shake someone's sense of belonging more than a rebrand ever will. Change lands on people. They experience it in proportion to what it costs them personally: their routines, their relationships, their sense of control.
That's the part that gets missed when we sort change into "big" and "small." We tend to scale our response to the size of the initiative. Big transformation, big communication plan, dedicated change lead, executive sponsor. New tool, new policy, a two-line announcement and a training video. The person receiving that two-line announcement doesn't know it's supposed to be small. They just know something they relied on is now different, and nobody explained why, what it means for them, or what happens next.
So here's a question worth sitting with. When you think about the changes moving through your organization right now, big and small, are you approaching them any differently because of their size? Should you be?
Here's what matters more than scale: asking the same questions no matter the size of the change.
What needs to be different, and why now? Who gains, who loses, and who's left uncertain? Are the leaders closest to this ready to have real conversations about it, not just deliver a message? How will people make sense of this over time, not just hear about it once?
Those questions apply to a reorg. They apply to a new team member or new tool. The scale changes. The questions don't.
We built a tool that walks through exactly this: the Change Enablement by Design Canvas. It's free and it runs the same way whether you point it at a massive transformation or a change so small you almost didn't think to plan for it at all.
Download it. Pick a change that's happening on your team right now, whatever size it is. Run it through the canvas. See what you notice.
